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

Remove gen2 support from obs_lsst

    XMLWordPrintable

Details

    • 3
    • Architecture
    • No

    Description

      The commissioning team have now fully transitioned to gen3 for LATISS and ComCam and DP0.2 demonstrated that imSim data has no problems with gen3. It is therefore time to remove gen2 support from obs_lsst.

      Attachments

        Issue Links

          Activity

            tjenness Tim Jenness added a comment -

            I'm trying to see what is needed to switch the camera/butler/mapper tests in obs_base over to gen3 (by experimenting with obs_lsst). That should help with some of the 2->3 migration.

            cc/ Parejkoj

            tjenness Tim Jenness added a comment - I'm trying to see what is needed to switch the camera/butler/mapper tests in obs_base over to gen3 (by experimenting with obs_lsst). That should help with some of the 2->3 migration. cc/ Parejkoj
            tjenness Tim Jenness added a comment -

            Parejkoj would you like to look at this?

            I fixed all the obs_base gen2 butler tests to work for gen3 but now I'm not sure it was really worth the effort since it seems that obs_lsst is the only place that used them.

            It's likely that I could have deleted the tests without any change in test coverage but I wasn't really sure what they did until I started to look in detail. Mostly they are testing that day_obs/seq_num/name_in_raft/raft shorthand works for these instruments which we could probably move over to the generic ingest tests. The mapper tests are simply ignored. obs_lsst does not run any algorithmic tests.

            If you think I should delete the obs_base tests.py and test_latiss.py, test_imsim.py etc that's fine. I'm no longer convinced they do anything that the gen3 tests don't already test.

            tjenness Tim Jenness added a comment - Parejkoj would you like to look at this? I fixed all the obs_base gen2 butler tests to work for gen3 but now I'm not sure it was really worth the effort since it seems that obs_lsst is the only place that used them. It's likely that I could have deleted the tests without any change in test coverage but I wasn't really sure what they did until I started to look in detail. Mostly they are testing that day_obs/seq_num/name_in_raft/raft shorthand works for these instruments which we could probably move over to the generic ingest tests. The mapper tests are simply ignored. obs_lsst does not run any algorithmic tests. If you think I should delete the obs_base tests.py and test_latiss.py, test_imsim.py etc that's fine. I'm no longer convinced they do anything that the gen3 tests don't already test.
            jbosch Jim Bosch added a comment -

            I've reviewed the daf_butler PR.

            jbosch Jim Bosch added a comment - I've reviewed the daf_butler PR.
            tjenness Tim Jenness added a comment -

            Jenkins passed (lsst_distrib, lsst_ci + ci_imsim).

            tjenness Tim Jenness added a comment - Jenkins passed (lsst_distrib, lsst_ci + ci_imsim).

            Thanks for the cleanups and replies. We can assess just how much of this test infrastructure we can remove when we fully remove gen2.

            Parejkoj John Parejko added a comment - Thanks for the cleanups and replies. We can assess just how much of this test infrastructure we can remove when we fully remove gen2.

            backport request is for the single astropy5.1 commit on daf_butler. 

            yusra Yusra AlSayyad added a comment - backport request is for the single astropy5.1 commit on daf_butler. 

            People

              tjenness Tim Jenness
              tjenness Tim Jenness
              John Parejko
              Eli Rykoff, Jim Bosch, John Parejko, Merlin Fisher-Levine, Tim Jenness, Yusra AlSayyad
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.