search

Quasars / orange-spectroscopy

Other
52 stars 58 forks source link

Agilent BSP files: self.info can be read wrongly #303

Open markotoplak opened 5 years ago

markotoplak commented 5 years ago

The following excerpt from self.info shows how it was read for a family of files. 

 'Rapid Stingray': {'\x19': '\x19',
                    '\x1e': '\x1e',
                    '\x1f': '\x1f',
                    ' ': 'TriggeredStart',
                    '%': '%',
                    '0': 'Total spectra to collect',
                    '1': 'Mosaic Tiles Y',
                    '128': 'Mosaic Tiles X',
                    '128 x 128 Lancer MCT': 'FPA Camera Number',
                    '2': 'Accessory Name',
raul-freitas commented 1 year ago

@markotoplak, @borondics and @stuart-cls, guys how are you? Is there a solution implemented in Orange-Quasar able to open .BSP files? Sorry I missed the history on this...

stuart-cls commented 1 year ago

@raul-freitas nice to hear from you! I'm doing well.

The .bsp file support is very minimal and hacky, just enough to get the information out needed to load the imaging data. It doesn't support loading spectra from them.

In principle further support could be added, but I'm not planning to do it. The export function from ResPro into a more user-friendly format works for our users.

If someone is interested in doing the work, I'd be happy to incorporate it. I track the ResPro file format support at https://github.com/stuart-cls/python-agilent-file-formats

raul-freitas commented 1 year ago

Hello @stuart-cls, nice to hear from you too! Thank you so much for the info! Indeed we are looking for a solution to load and handle single point spectra. I will contact my colleagues here and see what they think about the ResPro possibilities!