-
Notifications
You must be signed in to change notification settings - Fork 2
Description
I am trying to run an obsid and it keeps erroring on beam related stuff. Every time I fix something and re-run it spends a lot of time saving out the initial visibilities. I've tried setting the checkpointing options in the yaml but they don't work as I'd expect. I would like it to only do a step if that step has not already succeeded. So I tried setting all the checkpoint options to true, but that gave me errors. So I backed off and just tried setting the obs-checkpoint option to true, since it seemed like saving the visibilities out was associated with the obs checkpoint. But that errors too with:
2025-10-21 10:06:16 - INFO:
Logging and configuration file created and copied to here: /Users/bryna/Projects/Physics/data_files/pyfhd_testing/2013_golden/pyfhd_test/pyfhd_2025_10_21_10_06_16
2025-10-21 10:06:16 - INFO:
No beam file was set, PyFHD will calculate the beam.
2025-10-21 10:06:16 - INFO:
Input validated, starting PyFHD run now
2025-10-21 10:06:16 - ERROR:
An error occurred in PyFHD: cannot access local variable 'obs' where it is not associated with a value
Exiting PyFHD.
Traceback (most recent call last):
File "/Users/bryna/Projects/Physics/PyFHD/PyFHD/pyfhd.py", line 268, in main
psf = create_psf(obs, pyfhd_config, logger)
^^^
UnboundLocalError: cannot access local variable 'obs' where it is not associated with a value
2025-10-21 10:06:16 - INFO:
PyFHD Run Unsuccessful for 1061316296
How are the checkpoint options supposed to be used? Can I only set them to true if there's been a fully successful run already?
Metadata
Metadata
Assignees
Labels
No labels