Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-6350

Generate camera description at build time

    XMLWordPrintable

Details

    • 3
    • Alert Production F16 - 8, Alert Production F16 - 9, Alert Production F16 - 10
    • Alert Production

    Description

      Camera geometry used to be defined using PAF (policy) files, which are now deprecated. As part of the transition to the refactored camera geometry scheme, scripts were introduced to convert from the PAF files to the new camera geometry configuration scheme which uses FITS files and a python file to describe the camera. These scripts are still part of the obs_* packages, and some people rely on them for making changes to the camera description. On the other hand, the generated FITS files and python file are also first-class members of the obs_* packages. This means that we have two sources of the same information, which is dangerous.

      For obs_lsstSim, obs_decam, obs_cfht and obs_sdss, we want these scripts to be the primary source of information. This means we should delete the generated files, and create them at build time. We should also standardise the name of the script used to generate these.

      Attachments

        Issue Links

          Activity

            No work has yet been logged on this issue.

            People

              Parejkoj John Parejko
              price Paul Price
              John Parejko, John Swinbank, Paul Price, Simon Krughoff (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.