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

Deprecate obs_lsstSim

    XMLWordPrintable

    Details

    • Type: RFC
    • Status: Adopted
    • Resolution: Unresolved
    • Component/s: DM
    • Labels:
      None

      Description

      Robert Lupton and Merlin Fisher-Levine have put a lot of work into obs_lsstCam (soon to be obs_lsst) to bring together all the camera descriptions for data that looks like LSST data: test stand, imsim, and phosim.

      Since this package is taking over the responsibilities once served by obs_lsstSim, that package will be removed once obs_lsstCam is operational. Any activities currently using obs_lsstSim should consider switching to using obs_lsstCam as soon as is reasonable (assuming this RFC is accepted).

      There will be another RFC to officially add obs_lsst and remove obs_lsstSim.

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment -

            Simon Krughoff can you create the tickets described above and adopt this RFC please?

            Show
            tjenness Tim Jenness added a comment - Simon Krughoff can you create the tickets described above and adopt this RFC please?
            Hide
            krughoff Simon Krughoff added a comment -

            OK, but I think the we should probably hold off on doing the re-ingestion and reprocessing until RFC-571 is resolved.

            Show
            krughoff Simon Krughoff added a comment - OK, but I think the we should probably hold off on doing the re-ingestion and reprocessing until RFC-571 is resolved.
            Hide
            tjenness Tim Jenness added a comment -

            Creating the implementation tickets and adopting this RFC, including adding RFC-571 as a blocker, is the correct process. You don't have to keep this RFC in proposed state (which currently results in the CCB looking at it every week).

            Show
            tjenness Tim Jenness added a comment - Creating the implementation tickets and adopting this RFC, including adding RFC-571 as a blocker, is the correct process. You don't have to keep this RFC in proposed state (which currently results in the CCB looking at it every week).
            Hide
            krughoff Simon Krughoff added a comment -

            I understand. That was my plan.

            Show
            krughoff Simon Krughoff added a comment - I understand. That was my plan.
            Hide
            krughoff Simon Krughoff added a comment -

            Adopting with the added implementation tickets.

            Show
            krughoff Simon Krughoff added a comment - Adopting with the added implementation tickets.

              People

              Assignee:
              krughoff Simon Krughoff
              Reporter:
              krughoff Simon Krughoff
              Watchers:
              John Parejko, John Swinbank, Kian-Tat Lim, Merlin Fisher-Levine, Robert Lupton, Scott Daniel, Simon Krughoff, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Planned End: