joshduran / brukeropus Goto Github PK

These are all multi-channel measurements (e.g. sm-2ch, a-2ch, sm-3ch, rf-4ch) codes. Current version parses the data and assigns matching data status blocks properly, but without readable codes (e.g. sm_33, _36, sm_65, rf_97).

Update the constants and methods for getting data keys to use friendly keys for these codes.

Example files posted in other issues:

spectral-cockpit/opusreader2#67

wincowgerDEV/OpenSpecy-package#118

qedsoftware/brukeropusreader#17

Some files will have duplicate data and data status block pairs within the file. One reason could be when "make compatible scalar" option is selected in OPUS.

Currently duplicate data is ignored, but instead an effort should be made to identify the matching data status block between the duplicate entries.

Issue first posted here: stuart-cls/python-opusfc-dist#13

brukeropus fails to import whenever brukeropus.control.Opus fails to import. This will impact any non-windows users (OPUS control only supported by windows) as well as any specialized configurations for which DDE imports fail to initialize.

For these cases, the Opus class should simply not be imported so that OPUS file reading still functions as expected.