Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-394

As part of Wcs->SkyWcs do not attempt to read old WCS in CoaddInfo tables

    Details

    • Type: RFC
    • Status: Withdrawn
    • Resolution: Done
    • Component/s: DM
    • Labels:
      None

      Description

      CoaddInfo tables in coadds provide information about the exposures included in the coadd. It will be difficult for the new SkyWcs code to read the Wcs from those tables for old coadds, and I propose to not do it. We can still determine the input exposures and get the Wcs directly from them.

      Just to make it clear: we will be able to read Wcs from old Exposures. This only affects the ability to read the Wcs component of the CoaddInfo table for coadds.

        Attachments

          Issue Links

            Activity

            Hide
            jbosch Jim Bosch added a comment -

            Note that this will also affect our ability to read CoaddPsfs from old Exposures. I don't personally think that's a dealbreaker, but I think it is a bigger loss than the CoaddInfo tables.

            Show
            jbosch Jim Bosch added a comment - Note that this will also affect our ability to read CoaddPsfs from old Exposures . I don't personally think that's a dealbreaker, but I think it is a bigger loss than the CoaddInfo tables.
            Hide
            rhl Robert Lupton added a comment -

            Hmm. I think it's too late to drop support for WCS information in data products. This is an especial problem for HSC users, of course, but I'm afraid that I think that this matters enough that we need to provide backwards compatibility.

            One reason is that we need to be able to compare files from before and after the change; another is that we need to be sure that we are building files that are backwards-compatible whenever we change things in LSST processing of real LSST data, and this is a chance to practise.

            Show
            rhl Robert Lupton added a comment - Hmm. I think it's too late to drop support for WCS information in data products. This is an especial problem for HSC users, of course, but I'm afraid that I think that this matters enough that we need to provide backwards compatibility. One reason is that we need to be able to compare files from before and after the change; another is that we need to be sure that we are building files that are backwards-compatible whenever we change things in LSST processing of real LSST data, and this is a chance to practise.
            Hide
            tjenness Tim Jenness added a comment -

            Russell Owen I moved the end date from 2019 to 2017.

            Show
            tjenness Tim Jenness added a comment - Russell Owen I moved the end date from 2019 to 2017.
            Hide
            rowen Russell Owen added a comment -

            I will withdraw this and attempt to read old WCS. However, if it proves too difficult I'll push back.

            Show
            rowen Russell Owen added a comment - I will withdraw this and attempt to read old WCS. However, if it proves too difficult I'll push back.

              People

              • Assignee:
                rowen Russell Owen
                Reporter:
                rowen Russell Owen
                Watchers:
                Jim Bosch, John Swinbank, Robert Lupton, Russell Owen, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Planned End:

                  Summary Panel