You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
STIX observations and visibilities are associated with axis-aligned metadata that cannot be treated as a coordinate, at least not by WCS. This is because they do not represent a strictly monotonic sampling of a coordinate space. An example is detector label, "e.g. "3c, 4a,..." etc. Such metadata is not necessarily numeric and any ordering is valid.
Despite this, such metadata needs to be tracked and altered through certain operations, e.g. slicing and rebinning, in order for it to remain a faithful reflection of the data. ndcube PR #455 introduces a sliceable metadata class that performs this for slicing. However, for rebinning, axis-awareness for metadata is simply dropped as, in the generalised world of ndcube, handling this scenario is not well-defined.
This issue proposes that a STIXVisMeta that inherents from ndcube.Meta and VisMeta in xrayvision, and a STIXMeta for metadata associated with STIX observations. Extra functionality should be added to handle STIX-specific metadata during the rebinning process.
As part of this discussion, this issue should catalogue all the axis-aligned STIX metadata that is specific to observations, visibilities and both that can also be treated during rebinning, e.g. detector label.
Both (STIXMetaBase)
detector label
pixel label
...?
STIXMeta
exposure/integation time
STIXVisMeta
...?
The text was updated successfully, but these errors were encountered:
STIX observations and visibilities are associated with axis-aligned metadata that cannot be treated as a coordinate, at least not by WCS. This is because they do not represent a strictly monotonic sampling of a coordinate space. An example is detector label, "e.g.
"3c, 4a,..."
etc. Such metadata is not necessarily numeric and any ordering is valid.Despite this, such metadata needs to be tracked and altered through certain operations, e.g. slicing and rebinning, in order for it to remain a faithful reflection of the data. ndcube PR #455 introduces a sliceable metadata class that performs this for slicing. However, for rebinning, axis-awareness for metadata is simply dropped as, in the generalised world of
ndcube
, handling this scenario is not well-defined.This issue proposes that a
STIXVisMeta
that inherents from ndcube.Meta andVisMeta
inxrayvision
, and aSTIXMeta
for metadata associated with STIX observations. Extra functionality should be added to handle STIX-specific metadata during the rebinning process.As part of this discussion, this issue should catalogue all the axis-aligned STIX metadata that is specific to observations, visibilities and both that can also be treated during rebinning, e.g. detector label.
Both (
STIXMetaBase
)STIXMeta
STIXVisMeta
The text was updated successfully, but these errors were encountered: