David Rafferty (625b4983) at 28 Mar 09:00
Remove merge remnants in docstring
David Rafferty (d4a7c051) at 28 Mar 08:36
Merge branch 'master' into RAP-566_improve_photometry_check
... and 2 more commits
This MR improves the photometry measurements by adding comparisons of the derived flux densities to those of the NVSS and LoTSS surveys (in addition to the existing comparison to the TGSS survey). See RAP-566 for details.
David Rafferty (0e8e36ed) at 28 Mar 08:26
... and 3 more commits
David Rafferty (ca7fbe2a) at 28 Mar 08:25
David Rafferty (5a1354f6) at 28 Mar 08:25
Improve astrometry determination
This MR improves the astrometry determination done during the imaging workflow by using the Pan-STARRS catalog as a reference instead of the TGSS catalog (see RAP-567 for details). Plots of the astrometry offsets are now made, and a json file with the offset values is generated for later use (to correct the offsets -- note that no astrometry corrections are done as yet).
No, that's not possible at the moment, but could definitely be added if it's needed (in fact, it used to be possible to do a tec
or scalar
solve in place of the scalarphase
one).
Done.
OK, I tried some experiments and I now understand the reasons for the values -- they are basically needed to ensure that there's enough space for the "Dec" label on the y axis to appear correctly (the Dec coordinates values can be very long, so we need a lot of space for them plus the label). I added some additional comments to make this clear.
David Rafferty (098dee77) at 28 Mar 07:55
Add more info to comments
David Rafferty (ba930527) at 27 Mar 12:17
Add more info to doc
OK, thanks, that sounds reasonable -- in fact, I now see that there are a lot of other attributes defined there already. I added the missing ones.
David Rafferty (ffdf201b) at 25 Mar 13:28
Add defaults for some attributes
No, unfortunately there's no option for that yet. I think it could naturally be done as part of the work for #28, and I've noted that in the associated Jira ticket.
Good suggestion. At the moment it's not possible to specify the facet layout, but I think it's definitely something we should add. I made Jira issue RAP-625 to track the work.
That's right -- you can specify "LOTSS" for that option to make it use a LoTSS sky model to start.
I wonder as well how much the starting model affects things. For some fields (or facets), a poor model might cause it to start off so wrongly that it can't correct itself during selfcal. The suggestion in #27 might make such issues a lot less of a problem.
Hi Tim -- thanks for the suggestion. It's a very good idea and is something we are definitely planning (see RAP-212 for the related Jira issue).
David Rafferty (8208886e) at 20 Mar 10:17
Tweak text/formatting