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

Rename "*_flux" fields to "*_instFlux" in SourceCatalogs

    XMLWordPrintable

Details

    • Story
    • Status: Done
    • Resolution: Done
    • None
    • afw
    • 8
    • AP F18-3, AP F18-4
    • Alert Production

    Description

      This is the implementation ticket for RFC-322. The implementation is as follows:

      • Rename all of our *Flux_flux/*Flux_fluxSigma table fields to *Flux_instFlux*Flux_instFluxSigma to hold the post-ISR counts.
      • Add *Flux_flux and *Flux_mag fields for the post-calibrated flux (in Maggies) and magnitudes.
        *Rename the InstFlux slot to GaussianFlux, and remove the InstMag slot.
      • Add associated documentation to the above.
      • Pass these changes on to the relevant database groups to update e.g. cat.

      Implementing this will wait until Calib is removed from the stack and replaced by PhotoCalib (not yet scheduled, but likely within the next couple months).

      Attachments

        Issue Links

          Activity

            rowen Russell Owen added a comment -

            My guess is this should be version 3, especially since there were old "instFlux" fields (though by a different name?), but jbosch may have a more informed option.

            rowen Russell Owen added a comment - My guess is this should be version 3, especially since there were old "instFlux" fields (though by a different name?), but jbosch may have a more informed option.
            jbosch Jim Bosch added a comment -

            If in doubt, increment the version.  Integers are cheap.

            jbosch Jim Bosch added a comment - If in doubt, increment the version.  Integers are cheap.
            Parejkoj John Parejko added a comment - - edited New run with schema version 3 defined: https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/28663/pipeline

            The work as described here is now merged, and I've made a Community post about it.

            wmwood-vasey: I hear your concerns about documentation and tutorials. I'll take a look at the dev guide and other such docs tomorrow, and I'll see what I can do about the tutorials as well, but I make no promises about those or other jupyter notebooks. My changes should allow backward compatibility with the old schemas, so things should continue to at least work.

            Parejkoj John Parejko added a comment - The work as described here is now merged, and I've made a Community post about it. wmwood-vasey : I hear your concerns about documentation and tutorials. I'll take a look at the dev guide and other such docs tomorrow, and I'll see what I can do about the tutorials as well, but I make no promises about those or other jupyter notebooks. My changes should allow backward compatibility with the old schemas, so things should continue to at least work.

            :+1:

            Great, thanks Parejkoj
            Community Post looks good and helpful.
            Thanks, everyone, for versioning the schema!

            wmwood-vasey Michael Wood-Vasey added a comment - :+1: Great, thanks Parejkoj Community Post looks good and helpful. Thanks, everyone, for versioning the schema!

            People

              Parejkoj John Parejko
              Parejkoj John Parejko
              Russell Owen
              Jim Bosch, John Parejko, John Swinbank, Maria Patterson [X] (Inactive), Michael Wood-Vasey, Russell Owen, Simon Krughoff (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.