<commit_before><html>
	<head>
		<title>Peak detection - ADAP Chromatogram builder</title>
		<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
		<link rel="stylesheet" type="text/css" href="/net/sf/mzmine/desktop/impl/helpsystem/HelpStyles.css">
    </head>

<body>

<h1>Chromatogram builder</h1>

<h2>Description</h2>

<p>
The ADAP Chromatogram builder takes mass lists generated for each MS scan (see Mass detection) and builds a chromatogram for each mass that can be detected continuously over the scans.
Later, these chromatograms may be deconvoluted into individual peaks by the Deconvolution module.
</p>

<p>
ADAP chromatogram construction works from the largest intensity data point in the entire data file down
to the smallest.  The reasoning is that it is beneficial to begin EICs with
larger intensity data points since their m/z values tend to be more accurate. The chromatogram building steps are as follows:
</p>

We define &epsilon; to be the mass tolerance parameter m/z.
<ol>
	<li> Take all the data points in a data file, sort them by their intensities,
	and remove those points (mostly noise) below a certain intensity threshold.</li>

	<li> Starting with the most intense data point, the first EIC is created.</li>

	<li> For this EIC, establish an immutable $m/z$ range that is the data point's
		m/z plus or minus &epsilon; where &epsilon; is specified by the user. </li>

	<li> The next data point, which will be the next most intense, is added to an
	existing EIC if its $m/z$ value falls within its m/z range.</li>

	<li> If the next data point does not fall within an EICs m/z range, a new EIC is
	created. New EICs are only created if the point meets the minimum start intensity
	requirement set by the user. </li>

	<li> An $m/z$ range for a new EIC is created the same way as in step (3) except the boundaries
	will be adjusted to avoid overlapping with pre-existing EICs. As an example consider an
	existing EIC with m/z range (100.000,100.020) for &epsilon;=0.01. If the new EIC is
	initialized with a data point having an m/z value of 100.025, then this new EIC will
	have a m/z range set to be (100.020,100.035) rather than (100.015, 100.035).</li><commit_msg>minor help file fix<commit_after><html>
	<head>
		<title>Peak detection - ADAP Chromatogram builder</title>
		<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
		<link rel="stylesheet" type="text/css" href="/net/sf/mzmine/desktop/impl/helpsystem/HelpStyles.css">
    </head>

<body>

<h1>Chromatogram builder</h1>

<h2>Description</h2>

<p>
The ADAP Chromatogram builder takes mass lists generated for each MS scan (see Mass detection) and builds a chromatogram for each mass that can be detected continuously over the scans.
Later, these chromatograms may be deconvoluted into individual peaks by the Deconvolution module.
</p>

<p>
ADAP chromatogram construction works from the largest intensity data point in the entire data file down
to the smallest.  The reasoning is that it is beneficial to begin EICs with
larger intensity data points since their m/z values tend to be more accurate. The chromatogram building steps are as follows:
</p>

We define &epsilon; to be the mass tolerance parameter m/z.
<ol>
	<li> Take all the data points in a data file, sort them by their intensities,
	and remove those points (mostly noise) below a certain intensity threshold.</li>

	<li> Starting with the most intense data point, the first EIC is created.</li>

	<li> For this EIC, establish an immutable m/z range that is the data point's
		m/z plus or minus &epsilon; where &epsilon; is specified by the user. </li>

	<li> The next data point, which will be the next most intense, is added to an
	existing EIC if its m/z value falls within its m/z range.</li>

	<li> If the next data point does not fall within an EICs m/z range, a new EIC is
	created. New EICs are only created if the point meets the minimum start intensity
	requirement set by the user. </li>

	<li> An m/z range for a new EIC is created the same way as in step (3) except the boundaries
	will be adjusted to avoid overlapping with pre-existing EICs. As an example consider an
	existing EIC with m/z range (100.000,100.020) for &epsilon;=0.01. If the new EIC is
	initialized with a data point having an m/z value of 100.025, then this new EIC will
	have a m/z range set to be (100.020,100.035) rather than (100.015, 100.035).</li>
{'fraction_non_alphanumeric': 0.07998192498870312, 'fraction_numerical': 0.023045639403524627, 'mean_word_length': 4.065217391304348, 'pattern_counts': {'":': 0, '<': 61, '<?xml version=': 0, '>': 61, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2375537', 'n_tokens_mistral': 1418, 'n_tokens_neox': 1300, 'n_words': 670}