-s parameter fails to convert scan data
See original GitHub issueHi, the -s parameter introduced after the discussion in #99 does not work in the latest version 1.3.4. (I have not tested previous releases so I don’t know if it worked in the past and got broken at some point)
A simple test: I use a 15MB .raw file called a.raw.
After running ThermoRawFileParser.exe -i a.raw
I get a complete mzML file a.mzML with comparable size (~10 MB).
When I run ThermoRawFileParser.exe -s -i a.raw > a.mzML
the output file is tiny (~3 KB) and contains only the mzML header but no scan data.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to Fix the Parameter Is Incorrect on External Hard ...
Fix 1: Perform a Quick Scan Check; Fix 2: Run CHKDSK; Fix 3: Run SFC Scan ... Part 2: Recover Data from Hard...
Read more >The Parameter Is Incorrect on External Hard Drive [6+ Tips]
Do you get the 'The parameter is incorrect' error message and cannot access your external hard drive, USB drive, or SD memory card?...
Read more >Touchstone Data File Repair Utility
Solution. Please try this script first: Importing S-Parameter Data . The utility described here is a program that you will need to download...
Read more >How to Fix “The Parameter is Incorrect” Error on External Hard ...
Free download Recoverit data recovery: https://bit.ly/2vUwhTg This video will introduce 3 practical methods on how to fix “The Parameter is ...
Read more >Scattering parameters
Scattering parameters or S-parameters describe the electrical behavior of linear electrical networks when undergoing various steady state stimuli by ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi Tomas, thank you for reporting. The cause of the error is likely because since 1.3.3 the default output format is indexed mzML, it is not possible to index piped output and thus TRFP crashes (
I am actually surprised it does not spit any error or exceptionit does not throw any error since the logging is silenced in piped output). In future,-s
should imply regular mzML, as quick work around, please, try using-f=1
(regular mzML)Closed in 410ff006b2592f95c7227af2418e281b3a79a35a. STDOUT (
-s
) always forces plain mzML instead of indexed mzML