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
Currently, when a user wants to use tiled on a dataset of LabVIEW files, they can configure an adapter that creates a tree with two distinct main branches: one branch called unnormalized that will contain the data of the files as it is (also referred to as raw data), the other branch is named normalized and it represents a filtered version of the original data that follows the XAS Data Interchange Format (XDI) (https://github.com/XraySpectroscopy/XAS-Data-Interchange/blob/master/specification/dictionary.md#defined-items-in-the-column-namespace).
These two versions of the same dataset created some confusion for some scientists and after a thorough discussion, it was decided to reorganize the tree with a more optimal format. The new approach will create a single tree with all the data and the column names that qualify as part of the XDI standard will be renamed, if necessary. Also, the adapter will save the information about conversion in a section of the metadata. This information could be a dictionary linking the old column name with the new column name.
The text was updated successfully, but these errors were encountered:
Currently, when a user wants to use tiled on a dataset of LabVIEW files, they can configure an adapter that creates a tree with two distinct main branches: one branch called
unnormalized
that will contain the data of the files as it is (also referred to as raw data), the other branch is namednormalized
and it represents a filtered version of the original data that follows the XAS Data Interchange Format (XDI) (https://github.com/XraySpectroscopy/XAS-Data-Interchange/blob/master/specification/dictionary.md#defined-items-in-the-column-namespace).These two versions of the same dataset created some confusion for some scientists and after a thorough discussion, it was decided to reorganize the tree with a more optimal format. The new approach will create a single tree with all the data and the column names that qualify as part of the XDI standard will be renamed, if necessary. Also, the adapter will save the information about conversion in a section of the metadata. This information could be a dictionary linking the old column name with the new column name.
The text was updated successfully, but these errors were encountered: