ddf-pipeline
ddf-pipeline copied to clipboard
mhardcastle
LOFAR pipeline using killms/ddfacet
We attempt to recognise bad facets by the errors in the astrometry derived from PanStarrs. Presently we use a criteria of 0.5" and if the error exceeds this then during...
Presently thresholds (thresh_isl=3.0, thresh_pix=4.0) are hardcoded. We can of course make this optional (for the deep fields we thought to use thresh_isl=3.0, thresh_pix=4.0 but for LoTSS we thought to perhaps...
Presently the subtract-sources script simply has solution type =AP hard coded. We process some galactic fields with solution type=P. Ideally the subtract-sources script would read the solution type from the...
In offsets.py we attempt to match with Panstarrs to derive offsets per facet after removing extended sources from the LOFAR catalogues. Current filtering in master branch is very crude (filter=(lofar['E_RA']*3600.0)
Check the DR3 field in the database in the mosaic script.
Where we don't have common beams, or circular beams, we agreed to convolve to a common circular beam of 9 x 9 arcsec. We can use off the shelf solutions...
Hi, I have just downloaded the ddf-pipeline from the master branch and built the singularity, but I got this numpy incompatibility error at the starting of the pipeline. ``` pipeline.py...
Related to issue #351 we need to redo the astrometric corrections as previously poor quality corrections have been applied. Going back to the uv-data for redoing the corrections is prohibitively...
Hey, Anyone remember our reasoning for using o['apply_sols'][6] for the bootstrap step (this is the same as the final calibration so generally 'AP'). Wouldn't be better off and safer again...