Consider interpreting naming conventions from the Nexus format #61
Description
See https://manual.nexusformat.org/datarules.html?highlight=uncertainties#rules-for-storing-data-items-in-nexus-files, specifically the "Reserved suffixes", e.g., _mask is something we could handle:
Reserved suffixes
When naming a field, NeXus has reserved certain suffixes to the names
so that a specific meaning may be attached. Consider a field named DATASET,
the following table lists the suffixes reserved by NeXus.
| suffix | reference | meaning |
|---|---|---|
| _end | NXtransformations | end points of the motions that start with DATASET |
| _errors | NXdata | uncertainties (a.k.a., errors) |
| _increment_set | NXtransformations | intended average range through which the corresponding axis moves during the exposure of a frame |
| _indices | NXdata | Integer array that defines the indices of the signal field which need to be used in the DATASET in order to reference the corresponding axis value |
| _mask | Field containing a signal mask, where 0 means the pixel is not masked. If required, bit masks are defined in NXdetector pixel_mask. | |
| _set | target values | Target value of DATASET |
| _weights | divide DATASET by these weights [4] |