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
To my knowledge, it uses a more complete algorithm for reliably reading OPUS files than brukeropusreader. Also, it is not clear that brukeropusreader is still being maintained:
If there is interest in switching, I could assist if needed. My package returns a custom OPUSFile class rather than a simple dictionary, but all the information (and more) is there. One thing I have been considering is writing a compatibility function for reading an opus file and returning the same dict format that brukeropusreader returns. It wouldn't have all the features of my OPUSFile class, but it would make transitioning relatively trivial for projects that already use brukeropusreader. Let me know if you are interested.
The text was updated successfully, but these errors were encountered:
I have recently released an open-source package that can read Bruker OPUS files called
brukeropus
:https://github.com/joshduran/brukeropus
To my knowledge, it uses a more complete algorithm for reliably reading OPUS files than
brukeropusreader
. Also, it is not clear thatbrukeropusreader
is still being maintained:qedsoftware/brukeropusreader#23
If there is interest in switching, I could assist if needed. My package returns a custom
OPUSFile
class rather than a simple dictionary, but all the information (and more) is there. One thing I have been considering is writing a compatibility function for reading an opus file and returning the same dict format thatbrukeropusreader
returns. It wouldn't have all the features of myOPUSFile
class, but it would make transitioning relatively trivial for projects that already usebrukeropusreader
. Let me know if you are interested.The text was updated successfully, but these errors were encountered: