Vladimir Gorshkov

Hi @wdwvt1, thank you for the investigation. From what you reported, it looks like Agilent creates a new so-called *device* in the raw file, since there are only several types...

File received. Some good news, I think all the data you want is "visible" without any special packages added to the system. It has to be obtained in a significantly...

Hi @keesh-elucid, thank you for your interest in TRFP. The honest (and unfortunate) answer is that there are certainly no plans to implement all MSConvert filters. While some simple filters,...

To the best of my knowledge, some filtering is supported out of the box, for example, slicing by scan or time (`--filter "scanNumber xx-xx"`, `--filter "scanTime xx-xx"` in msconvert notation),...

Hi @soerendip, thank you for using ThermoRawFileParser. Your suggestion is to put a folder inside of release zip, instead of individual files. Did I get it right?

Hi @nielshulstaert is it worth considering moving format options into sub-commands? I.e. similarly to **xic** and **query** we introduce **mzml**, **mgf**, and **parquet** options to switch the format and substitute...

Hi @rmflight, this kind of processing is not yet implemented in TRFP. Some sort of averaging is available from the RAW-reading library. I have never touched it though, and, thus,...

Hi @rolivella, that is an long lasting issue, see #23 and #95 In short, the bottleneck is writing the mzML file (and index); this process essentially *has* to be single-threaded....

This seems to be a duplicate of #178.

@xjasg thanks for the explanation. I will merge this PR into next release branch.