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

            price Paul Price added a comment -

            Building the camera description for LSST requires a GainFile and phosimVersion. The latter appears to be just some string, but the GainFile is real content, but not present in obs_lsstSim.

            price Paul Price added a comment - Building the camera description for LSST requires a GainFile and phosimVersion . The latter appears to be just some string, but the GainFile is real content, but not present in obs_lsstSim.

            Parejkoj, can you confirm you're working on this? If so, we'll need to move it to an appropriate epic in 02C.03.

            swinbank John Swinbank added a comment - Parejkoj , can you confirm you're working on this? If so, we'll need to move it to an appropriate epic in 02C.03.
            Parejkoj John Parejko added a comment -

            Yes, I'm just starting this (and its sibling, DM-6349).

            Parejkoj John Parejko added a comment - Yes, I'm just starting this (and its sibling, DM-6349 ).

            Thanks. Switching team to AP and epic to DM-5691, which looks plausible — Parejkoj or krughoff, please feel free to refile as you see fit.

            swinbank John Swinbank added a comment - Thanks. Switching team to AP and epic to DM-5691 , which looks plausible — Parejkoj or krughoff , please feel free to refile as you see fit.

            Good enough. Sorry for not switching it before.

            krughoff Simon Krughoff (Inactive) added a comment - Good enough. Sorry for not switching it before.

            I think this is pretty obsolete now — see also comments on DM-6349 — so I'm closing as won't fix.

            swinbank John Swinbank added a comment - I think this is pretty obsolete now — see also comments on DM-6349 — so I'm closing as won't fix.

            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.