-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing backend #48
Comments
Hi, thanks for reporting back and providing an example. However, the example does not work for me out of the box. I modified the example to be straight cut&pasteable to reproduce, but did not get an error, and instead successfully wrote out a MassBank record:
Maybe the package versions are important, I might not have updated mine in a while, my So, I'll need to be able to reproduce the error to help fixing it.
|
Actually, the expected workflow would be that you have a any And please, do not directly access slots within a backend/Spectra. Use |
Oh great I got it to work as you say Johannes, thanks for the help! |
I want to convert a Spectra object to MassBank-Backend object
From the documentation:
"Changing to a backend is only supported if that backend has a data
parameter in its backendInitialize method and if supportsSetBackend
returns TRUE for that backend"
supportsSetBackend does return true but
backendInitialize for MsBackendMassbank does not have a data parameter.
Returns:
My current workaround is to load the example Massbank file, change the variables under spectraData, and then export again.
It seems to work initially, do you see any problems with doing it this way?
The text was updated successfully, but these errors were encountered: