Lidar Geometry Comparison
Compare monostatic and bistatic lidar path lengths and delay.
Description
Lidar path comparison adds transmitter and receiver legs for bistatic geometry.
Lidar path comparison adds transmitter and receiver legs for bistatic geometry. The monostatic reference uses twice the transmitter-to-target leg.1
Compare monostatic and bistatic lidar path lengths and delay.
When to use Lidar Geometry Comparison
Use this tool to compare monostatic and bistatic lidar path lengths and delay.
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 Lidar Geometry Comparison 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 transmitterToTargetMeters, targetToReceiverMeters using the field table and calculation rules, then run the tool.
- Read monostaticPathMeters, bistaticPathMeters, pathDifferenceMeters, bistaticDelaySeconds. 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 |
|---|---|---|---|
| transmitterToTargetMeters | Transmitter-to-target distance (m) | number; minimum: 0 | Required |
| targetToReceiverMeters | Target-to-receiver distance (m) | number; minimum: 0 | Required |
Enter nonnegative leg distances in meters. Return both paths, signed bi-minus-mono difference and bistatic delay seconds.
mono=2TxRange; bi=TxRange+RxRange; delay=bi/c Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| monostaticPathMeters | Equivalent monostatic path (m) | number; minimum: 0 |
| bistaticPathMeters | Bistatic path (m) | number; minimum: 0 |
| pathDifferenceMeters | Bistatic minus monostatic path (m) | number |
| bistaticDelaySeconds | Bistatic propagation delay (s) | number; minimum: 0 |
{
"input": {
"transmitterToTargetMeters": 100,
"targetToReceiverMeters": 120
},
"output": {
"monostaticPathMeters": 200,
"bistaticPathMeters": 220,
"pathDifferenceMeters": 20,
"bistaticDelaySeconds": 7.338410094359345e-7
}
}Limitations and assumptions
No coordinate geometry, refractive index or moving-target correction is calculated.
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.
Alternative or Complementary methods
Use Lunar-Ranging Precision: Convert round-trip timing uncertainty into one-way lunar-ranging distance uncertainty. For a complementary task, use FMCW Lidar Range and Velocity: Calculate ideal FMCW lidar range and radial velocity from separated beat frequencies.
References
-
Lidar Geometry Comparison — tool.io
Similar or alternative tools
- Lunar-Ranging Precision
Convert round-trip timing uncertainty into one-way lunar-ranging distance uncertainty.
- FMCW Lidar Range and Velocity
Calculate ideal FMCW lidar range and radial velocity from separated beat frequencies.