v1.4.1

• Improved logic for determining the type of data for spectral blocks. I have sufficient data to verify that the spectral type codes repeat for 2-channel, 3-channel and 4-channel measurements. This implies there are 32 unique spectral type codes. Now, multi-channel spectral types will automatically be labeled as such (previously, each unique combination of spectral type and number of channels were added manually).
• Added label and data key for "Match" spectral data type (type code:22)
• Now correctly parses data series that have some skipped spectra during acquisition (e.g. take 10 measurements, skip 5, take 10 measurements). These files are now successfully parsed (previously caused a parsing error and were not accessible). The store_table attribute in the DataSeries object can be used to determine the saved spectra indices (list of start, stop tuples). For example, the above example would return: [(1, 10), (16, 25)]