Hi all,
I did some further developments on the "Baseline Correction" module.
This is not yet completely "crash tested" (specially regarding the
compatibility of what I made with the "batch mode" system). But still
working quite well. And it might be a good candidate for integration in
the tru
own in the export value instead and
then also implemented for all the other data types to show if it is a STRING,
INT … ?
Best,
Thomas
From: Tomas Pluskal [mailto:plus...@oist.jp]
Sent: 1. november 2014 09:12
To: Developer discussion
Subject: Re: [Mzmine-devel] Peak list export
Hi Thomas,
12
To: Developer discussion
Subject: Re: [Mzmine-devel] Peak list export
Hi Thomas,
We are using the SQL export function in our lab, so I would prefer if the
current functionality is not broken. However, feel free to extend the
functionality - e.g. by adding an option to export all peaks in th
Hi Thomas,
We are using the SQL export function in our lab, so I would prefer if the
current functionality is not broken. However, feel free to extend the
functionality - e.g. by adding an option to export all peaks in the row.
Best regards,
Tomas
On Oct 31, 2014, at 19:12, TFRD (Thomas Fran
I have been looking into the sql export function of MZmine and would like to
discuss the implementation - it seems that the sql export function is different
than the csv export.
The issue is that when exporting data from an aligned peak list, the values in
mz, rt, peak height and peak area are
