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

Reading Analag Traces from RawFiles #61

Open
BerndMaier opened this issue Jul 27, 2020 · 7 comments
Open

Reading Analag Traces from RawFiles #61

BerndMaier opened this issue Jul 27, 2020 · 7 comments
Assignees
Labels
enhancement New feature or request

Comments

@BerndMaier
Copy link

Hi there,

2 of our instruments have their LC Systems (Thermo Vanquish) directly connected through Xcalibur, with the MassSpecs (QE HF & HFX), within one system.

The LC traces (UV, Column Temp, Pump pressure etc.) are written as analog traces to the MS rawfile.

Is there a possibility to read these analog traces with rawDiag - just as the TIC trace ?

xcalibur_hfx

Thank you very much,
Bernd

@tobiasko
Copy link
Collaborator

Hi Bernd,

I think we haven't tried this so far, but according to the RawFileReader documentation it is possible to read data streams coming from other detectors types than MS.

We need to check your data.

Best,
Tobi

@tobiasko tobiasko added the enhancement New feature or request label Jul 27, 2020
@BerndMaier
Copy link
Author

Thank you very much - just added a File where we recorded UV to the Raw Files

@tobiasko
Copy link
Collaborator

@cpanse Could you try to implement a function that wraps the example C# code for Instrument (detector) List shown in UsingRawFileReader as well as Getting detector details???

@tobiasko
Copy link
Collaborator

Regarding analog traces: I checked a raw file that we recorded on a Exploris 480 with both A/D inputs enabled. We feed two signals from our LCs into these ports. Using the following code you can already access the recordings and plot as a function of time:

> autoQC01 <- read.raw(file = "20200730_001_autoQC01.raw", rawDiag = FALSE)
system2 is writting to tempfile  C:\Users\TOBIAS~1.FGC\AppData\Local\Temp\2\RtmpWcTL9L\file1b682c1c1f3tsv ...
unlinking C:\Users\TOBIAS~1.FGC\AppData\Local\Temp\2\RtmpWcTL9L\file1b682c1c1f3tsv ...
> xyplot(AnalogInAV ~ StartTime, data = autoQC01)

image

I am not sure if all Thermo systems log using AnalogInAV and AnalogInBV. The same data should be shown in Freestyle when you display a Chromatogram Range for the detector MS Trending.

@tobiasko
Copy link
Collaborator

Your analog traces seem to be empty:

> HFX_with_UV <- read.raw(file = "HFX_with_UV.raw", rawDiag = FALSE)
system2 is writting to tempfile  C:\Users\TOBIAS~1.FGC\AppData\Local\Temp\2\RtmpWcTL9L\file1b68321f3cb2tsv ...
unlinking C:\Users\TOBIAS~1.FGC\AppData\Local\Temp\2\RtmpWcTL9L\file1b68321f3cb2tsv ...
> summary(HFX_with_UV$AnalogInput1V)
   Min. 1st Qu.  Median    Mean 3rd Qu.    Max. 
      0       0       0       0       0       0 

@tobiasko
Copy link
Collaborator

Most likely your LC-related data is logged as additional instrument. Currently, we don't have a function that allows accessing other instruments, but we will check if a code extension is possible.

@BerndMaier
Copy link
Author

Thank you very much for checking

Would be a really nice option - as to date Thermo itself has no option to quickly extract the UV traces in an automated way.

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

No branches or pull requests

3 participants