PaulHancock / MWA-fast-image-transients

Code and notes for the data reduction and analysis of fast image transients observed with the MWA
Other
5 stars 3 forks source link

dl_obs not creating metafits/obs_cotter not finding metafits #14

Closed gemmaanderson closed 6 years ago

gemmaanderson commented 6 years ago

I have been trying to process the calibrator observation (3C444) 1207606224

obs_dl breaks chain. It says it makes the metafits file but it did not appear in the processing directory:

> less dl_1207606224.e2476659
--2018-05-09 14:11:36--  http://mwa-metadata01.pawsey.org.au/metadata/fits?obs_id=1207606224&min_bad_dipoles=2
Resolving mwa-metadata01.pawsey.org.au (mwa-metadata01.pawsey.org.au)... 146.118.87.249
Connecting to mwa-metadata01.pawsey.org.au (mwa-metadata01.pawsey.org.au)|146.118.87.249|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 48960 (48K) [image/fits]
Saving to: ‘1207606224_metafits.fits’

     0K .......... .......... .......... .......... .......   100% 20.2M=0.002s

2018-05-09 14:11:38 (20.2 MB/s) - ‘1207606224_metafits.fits’ saved [48960/48960]

/var/spool/slurm/job2476659/slurm_script: line 72: syntax error near unexpected token `fi'
/var/spool/slurm/job2476659/slurm_script: line 72: `fi'
slurmstepd: error: Exceeded step memory limit at some point.

obs_cotter gives the following error:

> less cotter_1207606224.e4313899
An unhandled exception occured while running Cotter:
Cannot open file 1207606224_metafits.fits. CFitsio reported an error while accessing fits files. Status = 104: could not open the named file. Error message stack: failed to find or open the following file: (ffopen). 1207606224_metafits.fits.
+ test_fail 255
+ [[ 255 != 0 ]]
+ cd /astro/mwasci/phancock/D0009/
++ date +%s
+ python bin/track_task.py fail --jobid=4313899 --finish_time=1525852520
+ exit 255
PaulHancock commented 6 years ago

The issue seems to be that the metafits file was being placed in the wrong directory. It was being placed into /processing instead of /processing/obsid.

This has been fixed.