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

Standardize aliases on Gen 2 Exposure get

    XMLWordPrintable

    Details

      Description

      RFC-730 proposes a new filter system that will support only standardized names for each band or filter, but no aliases. While new aliases will no longer be introduced after DM-27167, old files may still use them in Gen 2 (Gen 3 will internally ensure that all names are standardized). To ensure that algorithmic code can safely assume standardized names in FilterLabel regardless of whether an input Exposure was loaded from Gen 2 or Gen 3, standardize the filter names in an Exposure when loading them from Gen 2.

      Note that there is no standardization problem when using Filter; the problem will only emerge after Exposure starts using FilterLabel as the primary API.

        Attachments

          Issue Links

            Activity

            Hide
            krzys Krzysztof Findeisen added a comment -

            There may also need to be standardization of filter names inside catalogs, but this is a trickier problem because catalogs are free to have any schema, and it's not always obvious which field is a filter (let alone disambiguating between different instruments). See DM-27167 for discussion.

            Show
            krzys Krzysztof Findeisen added a comment - There may also need to be standardization of filter names inside catalogs, but this is a trickier problem because catalogs are free to have any schema, and it's not always obvious which field is a filter (let alone disambiguating between different instruments). See DM-27167 for discussion.

              People

              Assignee:
              krzys Krzysztof Findeisen
              Reporter:
              krzys Krzysztof Findeisen
              Reviewers:
              Eli Rykoff
              Watchers:
              Eli Rykoff, Krzysztof Findeisen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.