Jitter-Rejection Budget
Calculate fast-steering-mirror jitter rejection and margin against a caller requirement.
Description
Jitter rejection uses an amplitude-ratio dB convention.
Jitter rejection uses an amplitude-ratio dB convention. A caller requirement defines the signed performance margin.1
Calculate fast-steering-mirror jitter rejection and margin against a caller requirement.
When to use Jitter-Rejection Budget
Use this tool to calculate fast-steering-mirror jitter rejection and margin against a caller requirement.
Prepare the optical measurements, geometry, fitted coefficients or caller-selected thresholds requested. Confirm wavelength, radius/diameter, pulse-width, angle and unit conventions before running the calculation.
How to use Jitter-Rejection Budget and understand its results
- Prepare the optical measurements, geometry, fitted coefficients or caller-selected thresholds requested. Confirm wavelength, radius/diameter, pulse-width, angle and unit conventions before running the calculation.
- Enter openLoopJitter, residualJitter, requiredRejectionDb using the field table and calculation rules, then run the tool.
- Read rejectionDb, marginDb, meetsRequirement. 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 |
|---|---|---|---|
| openLoopJitter | Open-loop jitter (angle) | number; minimum: 0 | Required |
| residualJitter | Residual jitter (angle) | number; minimum: 0 | Required |
| requiredRejectionDb | Required rejection (dB) | number; minimum: 0 | Required |
Enter positive jitter measurements on the same basis and nonnegative required dB. Return rejection, margin and inclusive gate.
rejectionDb=20log10(openLoop/residual); margin=rejection−required Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| rejectionDb | Measured jitter rejection (dB) | number; minimum: 0 |
| marginDb | Rejection margin (dB) | number |
| meetsRequirement | Meets requirement | boolean |
{
"input": {
"openLoopJitter": 100,
"residualJitter": 10,
"requiredRejectionDb": 15
},
"output": {
"rejectionDb": 20,
"marginDb": 5,
"meetsRequirement": true
}
} Limitations and assumptions
No frequency-domain control response, bandwidth or independence of noise sources is evaluated.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Tracker Error Budget: Combine independent laser-tracker error components by root-sum-square. For a complementary task, use Galvo Grid Error: Summarize radial positioning error from a galvo calibration grid.
References
-
Jitter-Rejection Budget — tool.io
Similar or alternative tools
- Tracker Error Budget
Combine independent laser-tracker error components by root-sum-square.
- Galvo Grid Error
Summarize radial positioning error from a galvo calibration grid.