-
Notifications
You must be signed in to change notification settings - Fork 11
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
Problems reading Meta Data from QExactive HF / HFX Instruments #60
Comments
Hi Bernd, so the MS instruments connected to the Vanquish LCs use Xcalibur & LCDevices or is the LC integration SII-based? Are the UV, column temp, pump pressure traces really going through the D/A converter of the MS? There is only two analog inputs available on the HF and the HF-X. We use the analog inputs to record the LC system pressure and %B, but we use 3rd party hardware (Waters LCs). I thought the Vanquish communication is SII-based and digital using the ethernet connection. Anyway: In the context of the raw file each detector generates an instrument stream. Analog detectors can also have channels (shared time axis), if the detector uses the same sampling rate. We would need to check what exactly is returned by your files (stream & instrument structure). |
Yes, that looks like SII for Xcalibur. Hmmmm. Ok. So, all our LC-MS combinations use Xcalibur & LCDevices, so we have zero experience with this way of recording data into raw files. I expect that SII generates separate data streams for UV, column temp, pump pressure,... but we need to check your files. I think our current code only uses detectors of the type |
btw: When checking raw files use Freestyle. Qualbrowser is outdated. I am not even sure if it uses RawFileReader dlls internally! |
Yeah, we are switching to FreeStyle - but old habbits ;) But the installed Thermo Software shouldn't affect rawDiag and the functions ? I really would be quite happy in accessing the data from read.raw.info as Sample Name, Column Name etc. would be really useful for our Dashboards. Thanks again, |
@cpanse The raw files are available at |
Hi Bernd, I checked your file, but can't reproduce your error message:
Could it be that your |
Matrix products: default locale: attached base packages: other attached packages: loaded via a namespace (and not attached): |
same for the HF-X file:
|
|
What you can see is that the |
What do you get when executing:
??? |
The same error ... rawfile <- file.path(path.package(package = 'rawDiag'), 'extdata', 'sample.raw')
But with other instruments
$
|
That you can not process the package example data is pretty strange. I am having the feeling your error is not connected to specific files. What do you get:
|
Hmmm...currently I have no idea how to proceed, especially because I can not reproduce your error on my system. Maybe @cpanse can help!? |
Thanks for the efforts. I try to find a none Windows System to test. But at least here on 3 independent Windows machines I have the same problem. Just saw that the beginning of the function
Makes a difference for mono (whatever this is) Thank you very much again |
Yes, there is a difference. On Windows you just need to have the MS .NET framework installed. According to planet orbitrap you should have >4.5.1 Mono is the open source .NET implementation needed on MacOS to use the RawFileReader dlls. I hope at some point RawFileReader will be using .NETcore, but Thermo hasn't been the most progressive company in the past when it comes to software development. |
Finally! On a Windows system I get the error too:
|
@cpanse Don't we have a unit test for |
Ok, it is good that the Error is reproducible on the developer side, too. Have so much bad experience with MassSpecs doing crazy things ... until Thermo or Waters is on site and everything is back to normal... until they leave. |
I guess we will have a fix soon. I can't really tell you what is going wrong on Windows, but now we can follow the problem. :-) |
I discovered something:
Reading from the current working directory is fine, using a rel. path fails. |
Unfortunatelly not here - also no difference between network and local drive or R version R 3.6.3 // 4.0.2 setwd("I://Users/maierb5/Transfer/")
setwd("C://Users/xxxx/Downloads/")
|
@BerndMaier Can you give it a try using R(> 4.0)
|
|
Works like a charm - Thank you very much I saw that you changed the structure of the Output to 1 big list - is this intentional - will stay this way for future releases ? If the additional info from #62 added to this list i would be totally in heaven :) rawfile <- "I://Users/maierb5/Transfer/HFX_with_UV.raw"
$ $ $Operator $ $Description $ $ $ $ $ $Units $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ |
First, thanks for your amazing package.
I have an issue with our newer instruments.
RawDiag 0.0.34 returns an Error when Using read.raw.info
( > QE_HFX_Meta <- read.raw.info(QE_HFX)
Error in !silent : invalid argument type )
With one QExactive HF and one QExactive HFX Instrument.
Other Instruments (Fusion, Velos, EMR, UHMR and another QE HF) work fine.
Both instruments also control their Thermo Vanquish LC Systems through Xcalibur.
All other instruments have separate computers to control the LC.
So maybe this causes a difference in data structure of the *.raw Files, as the traces (UV, Column Temp, Pump Preassure) are added as analog traces.
Thank you very much,
Bernd
The text was updated successfully, but these errors were encountered: