Data ModelIcon indicating the project type

Data Model

Uploaded image for project: 'Data Model'
  1. Data Model
  2. DAMD-24

Add pfsSimObject module

    Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Normal
    • Resolution: Unresolved
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      2DDRP-2019 H, 2DDRP-2019 I

      Description

      We need a pfsSimObject module. Proposed changes from existing datamodel.txt are currently only:

      1. Definitely add a LINETBL HDU, with at least lambda, amplitude, width, name columns.
      2. Possibly drop FLUX image, since the reference data are in the FLUXTBL HDU. But FLUX could be useful for quick identification or for some users. In any case, assert that FLUXTBL is definitive.

        Attachments

          Issue Links

          relates to

          Task - A task that needs to be done. INFRA-208 Create repo for simulated spectra, etc.

          • Normal - Normal priorities
          • Open

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            cloomis cloomis added a comment -

            This has changed significantly, partly from discussions on the associated INFRA-208 and partly from what Sean Johnson has been doing. Please look at the current `datamodel.txt` and comment.

            1. Dropped FLUXTBL HDU, kept FLUX, added LAM.  Yes, FLUXTBL instead of (LAM, FLUX) appears to be a better match to `pfsObject` files, but we don't need any of the other FLUXTBL columns. So go for a simple structure.
            2. Dropped all the sky and observation info in both the file name and the content.

            Questions:

            1. Do we want to require any additional header cards (Z, other properties, some name)?
            2. Do we want to apply any constraints on the resolution?
            Show
            cloomis cloomis added a comment - This has changed significantly, partly from discussions on the associated INFRA-208 and partly from what Sean Johnson has been doing. Please look at the current `datamodel.txt` and comment. Dropped FLUXTBL HDU, kept FLUX, added LAM.  Yes, FLUXTBL instead of (LAM, FLUX) appears to be a better match to `pfsObject` files, but we don't need any of the other FLUXTBL columns. So go for a simple structure. Dropped all the sky and observation info in both the file name and the content. Questions: Do we want to require any additional header cards (Z, other properties, some name)? Do we want to apply any constraints on the resolution?
            Hide
            Permalink
            price price added a comment -

            I think the only thing to consider beyond what we have now is whether we want to add emission lines in a table. I suggest that we defer this until that becomes necessary.

            Show
            price price added a comment - I think the only thing to consider beyond what we have now is whether we want to add emission lines in a table. I suggest that we defer this until that becomes necessary.

              People

              • Assignee:
                price price
                Reporter:
                cloomis cloomis
              • Votes:
                0 Vote for this issue
                Watchers:
                Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: