Collision Energy Ramp
Plan collision-energy ramp with caller-supplied slope, intercept, and cap.
Description
A collision-energy ramp applies a linear m/z rule and clips its results to an allowed range.
A collision-energy ramp applies a linear m/z rule and clips its results to an allowed range. The ramp coefficients are supplied rather than fitted.1
Plan collision-energy ramp with caller-supplied slope, intercept, and cap.
When to use Collision Energy Ramp
Use this tool to plan collision-energy ramp with caller-supplied slope, intercept, and cap.
Prepare the measured profile, formula counts, upstream model outputs or caller-defined reference criteria requested. Keep paired entries aligned and units, sample basis and preprocessing consistent.
How to use Collision Energy Ramp and understand its results
- Prepare the measured profile, formula counts, upstream model outputs or caller-defined reference criteria requested. Keep paired entries aligned and units, sample basis and preprocessing consistent.
- Enter mzValues, interceptEv, slopeEvPerMz, maximumEv using the field table and calculation rules, then run the tool.
- Read collisionEnergiesEv, cappedCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| mzValues | Mz values | list of number | Required |
| interceptEv | Intercept ev | number | Required |
| slopeEvPerMz | Slope ev per mz | number | Required |
| maximumEv | Maximum ev | number | Required |
Enter nonnegative m/z values, finite signed slope/intercept and nonnegative cap. Empty lists are allowed. Return energies and count of raw values strictly above the upper cap; values clipped at zero are not counted.
raw=intercept+slope×mz; energy=min(maximum,max(0,raw)) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| collisionEnergiesEv | Collision energies ev | list of number |
| cappedCount | Capped count | number |
{
"input": {
"mzValues": [
100,
200
],
"interceptEv": 10,
"slopeEvPerMz": 0.1,
"maximumEv": 25
},
"output": {
"collisionEnergiesEv": [
20,
25
],
"cappedCount": 1
}
} Limitations and assumptions
Instrument units and fragmentation suitability are not validated.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use DDA Cycle Budget: Calculate top-N DDA scan-cycle time and remaining budget. For a complementary task, use Neutral Loss Matcher: Match product-ion neutral losses against caller-provided diagnostic differences.
References
-
Collision Energy Ramp — tool.io
Similar or alternative tools
- DDA Cycle Budget
Calculate top-N DDA scan-cycle time and remaining budget.
- Neutral Loss Matcher
Match product-ion neutral losses against caller-provided diagnostic differences.