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
Previously, some of the ViMMS internals were moved to mass-spec-utils so they could be used as a separate, lighter-weight library. Unfortunately, that repository is no longer maintained. Additionally, there is a fragmentation of relevant utilities between this repo and mass-spec-utils. For example, mass-spec-utils provides MZMLFile, a wrapper around pymzml which allows .mzMLs to be read in. But ViMMS provides an MZMLWriter which instead uses psims to write .mzML files. ViMMS is therefore using two different utilities to read and write .mzML files.
We should try to either:
Return the mass-spec-utils code to ViMMS and make it internally consistent within ViMMS.
Fork the mass-spec-utils code and then either merge it with the existing repository or publish it as a new package. Existing code should be moved from ViMMS and the new package made internally consistent.
The text was updated successfully, but these errors were encountered:
Previously, some of the ViMMS internals were moved to mass-spec-utils so they could be used as a separate, lighter-weight library. Unfortunately, that repository is no longer maintained. Additionally, there is a fragmentation of relevant utilities between this repo and mass-spec-utils. For example,
mass-spec-utils
provides MZMLFile, a wrapper aroundpymzml
which allows .mzMLs to be read in. But ViMMS provides an MZMLWriter which instead usespsims
to write .mzML files. ViMMS is therefore using two different utilities to read and write .mzML files.We should try to either:
mass-spec-utils
code to ViMMS and make it internally consistent within ViMMS.mass-spec-utils
code and then either merge it with the existing repository or publish it as a new package. Existing code should be moved from ViMMS and the new package made internally consistent.The text was updated successfully, but these errors were encountered: