Closed bittremieux closed 2 years ago
Side note: maybe we should just use the MassIVE ProXi interface instead? Would there any efficiency issues with that?
Nvm, the MassIVE ProXi response doesn't even contain precursor mass or charge. Seems like pretty essential information about a spectrum. 🤔
Possibly the same as #102.
This USI (mzspec:MSV000080918:SS279_RH9_01_7628.mzML:scan:2629) works now, so it must have been fixed on the MassIVE side.
Some MSV USIs are not correctly found on MassIVE, with MassIVE returning a 500 error code. However, they do seem to work using the MassIVE native USI service. I'm not sure what's wrong with our code.
Example:
mzspec:MSV000080918:SS279_RH9_01_7628.mzML:scan:2629