Skip to content

implement oid= for cutting multiple cubes #67

Description

@teuben

The oid= keyword to give an extra id, should implement the __OID appendage to the obsnum. This way multiple configurations can be used for e.g. a __wide sample to query the sanity of waterfall for SEQ, and for implementing multiple spectral lines.

The current reason for speeding this issue up is the DM-2 project, where two lines in bank=0 are present, so we would run this with oid=__C18O and oid=__13CO

This should also trigger a solution for #31 as doing multiple lines by hacking the vlsr= is not ideal and creates bad meta-data in the final FITS cube.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions