Skip to content
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

msconvert.exe: The ignoreUnknownInstrumentError true/false assignment is backwards when a config file is used #214

Open
austinkeller opened this issue Sep 8, 2018 · 0 comments

Comments

@austinkeller
Copy link
Contributor

This is a really minor issue but I wanted to document it. Adding the --ignoreUnknownInstrumentError flag on the command line bypasses the error as expected. I would expect when using a config file that adding a line of ignoreUnknownInstrumentError=true would give the same behavior. However, I need to add ignoreUnknownInstrumentError=false instead.

Contents of my config file:

zlib=true
mz64=true
inten64=true
simAsSpectra=true
ignoreUnknownInstrumentError=false
filter="peakPicking vendor msLevel=1-2"

Using ProteoWizard 3.0.18250.994311be0

I noticed in the code there is a line that is used to flip the logic for use with the unknownInstrumentIsError variable when using the command line flag.

// negate unknownInstrumentIsError value since command-line parameter (ignoreUnknownInstrumentError) and the Config parameters use inverse semantics
config.unknownInstrumentIsError = !config.unknownInstrumentIsError;

I didn't see an obvious way to fix this without breaking the command line flag logic, so I'm leaving this here for later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant