For all interested:
I solved the problem using the "peakML" java library which is
contained in the open source project "mzMatch" (http://sourceforge.net/
projects/mzmatch/)
It includes a Thermo raw-file parser which makes use of Thermo .dlls
(so works only under windows). This parser provides access to all
kinds of information contained in the raw files, including noise
information.

Stefan

On 22 Jan., 18:52, Matthew Chambers <[email protected]>
wrote:
> ProteoWizard's Thermo reader doesn't pull out S/N either. It wouldn't be
> hard to add; making it optional is the tricky part in our framework.
>
> -Matt
>
> Natalie Tasman wrote:
> > Hi Stefan,
>
> > ReAdW doesn't output specific noise information.  You might want to try
> > asking the ProteoWizard team on their newsgroup:
>
> > proteowizard-support mailing list
>
> > [email protected]
> >https://lists.sourceforge.net/lists/listinfo/proteowizard-support
>
> > -Natalie
>
> > On 1/22/10 9:17 AM, Stefan Reckow wrote:
>
> >> Hello!
> >> I need to access the noise information contained in .raw files coming
> >> from a Thermo LTQ-Orbitrap. Usually we convert those files to mzXML
> >> using ReAdW.
> >> However, after (successful) conversion with the latest ReAdW version
> >> (4.3.1) to mzXML (version 3.1), I could not find any noise info. This
> >> latest mzXML scheme supports the new "contentType" "S/N", which I
> >> expected to contain the noise info. For each scan the mzXML file only
> >> contains "m/z-int" content like in previous versions.
>
> >> The raw file has been created with Xcalibur 2.5.5 and obviously
> >> contains noise information, since it can be displayed in Qual Browser.
>
> >> Does anybody know, whether the contentType "S/N" is supported by
> >> ReAdW, at all? Or any other way to get signal/noise info from the raw
> >> data?
>
> >> Thanks a lot,
> >> Stefan
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"spctools-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/spctools-discuss?hl=en.

Reply via email to