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
brukeropusreader appears to no longer be maintained. In addition, it does not use a complete parsing of the OPUS file directory to extract the various data/param blocks.
Describe the solution you'd like
I recently published an open-source python package for reading Bruker OPUS files. It uses a more complete algorithm for extracting and accurately categorizing the data/param blocks in an OPUS file. Rather than trying to maintain a fork of brukeropusreader yourselves, you might find it useful to adopt my package instead:
Instead of a modified dictionary, my package returns a custom OPUSFile class. It has all the same data as the modified dictionary (and more), but obviously uses different syntax for accessing that data. I am considering writing a compatibility function for returning a modified dictionary that mimics the brukeropusreader output. This wouldn't be as full featured as my OPUSFile class, but it would make switching packages more or less trivial to start (change import statement and dependencies). If that is of interest to you, let me know.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
brukeropusreader appears to no longer be maintained. In addition, it does not use a complete parsing of the OPUS file directory to extract the various data/param blocks.
Describe the solution you'd like
I recently published an open-source python package for reading Bruker OPUS files. It uses a more complete algorithm for extracting and accurately categorizing the data/param blocks in an OPUS file. Rather than trying to maintain a fork of brukeropusreader yourselves, you might find it useful to adopt my package instead:
https://github.com/joshduran/brukeropus
Describe alternatives you've considered
Instead of a modified dictionary, my package returns a custom OPUSFile class. It has all the same data as the modified dictionary (and more), but obviously uses different syntax for accessing that data. I am considering writing a compatibility function for returning a modified dictionary that mimics the brukeropusreader output. This wouldn't be as full featured as my OPUSFile class, but it would make switching packages more or less trivial to start (change import statement and dependencies). If that is of interest to you, let me know.
Additional context
No response
The text was updated successfully, but these errors were encountered: