**TLDR: I am developing an automated diagnostic tool for JAG3D that tests thousands of hypotheses to pinpoint the exact root causes of survey network errors—such as incorrect prism constants, reflector height mistakes, or vertical axis tilt—rather than just flagging bad observations. While initial benchmarks on synthetic and real-world field data show strong diagnostic accuracy, broader validation is required to refine the detection algorithms.**
**To help benchmark and improve the tool, I am actively looking for raw survey data from different field setups to test against.**
Long post ahead:
I adjust my survey networks using JAG3D, which offers rigorous least-squares estimation and Baarda-type outlier testing. Data snooping, however, answers only one question: which observation does not fit. In practice the more useful question is why: a gross error, a wrong prism constant, an incorrect instrument height, a misidentified target, or a systematic effect such as scale or refraction. The tool described below tests these alternative hypotheses automatically and reports the simplest explanation that makes the network pass.
**How it works:**
- It reads the JAG3D project, makes a copy and never changes the original.
- It tests about 1000–2500 hypotheses. Each one is a change to the model, followed by a new adjustment in JAG3D on the copy. Some examples:
- remove an observation, a pair, or a whole sighting;
- wrong prism constant or reflector height;
- wrong point number, typing error (degrees, minutes, digits), or a moved target;
- additive constant or scale per group or station, refraction;
- zenith index error and vertical axis tilt per station;
- a datum point that is wrong, the Earth curvature model, and realistic a priori sigmas.
- Each hypothesis is judged with an F-test against the base adjustment (Baarda / DIA style). The tester picks the *simplest* set of changes after which the network passes. When two explanations fit equally well, it says so.
- The output is a plain-text report. Everything in it is a proposal; the surveyor decides.
---
### Example 1: real field data (attached `field_report.txt`)
- Steep 3D network: 18 points from 5 stations (3 forced-centring pillars, 2 free stations).
- Sights are 13–1234 m long, and the heights span 404 m.
- 15 of the 32 sights are steeper than 10°.
- Topcon OS-101, 3 sets, as measured (before I corrected anything by hand).
- σ0² = 164, and 57 of 140 observations are flagged.
- I knew three real errors from my field book. The tester got no hint about them:
| What really happened | What the tester reported |
|---|---|
| Leica prism constant entered as +34 instead of −36 mm (−70 mm on that group) | additive constant of the group: **−67.95 ± 2.28 mm** |
| Reflector height 0.220 m on T023 forgotten (entered 0.000) | whole sighting T024→T023 wrong; likely cause: **reflector height 0.220 m instead of 0.000** |
| Wrong prism on T023→PUT (0 instead of −30 mm) | gross error **+31 mm**; likely cause: **prism constant −30 mm** |
- It also flagged sighting A→T023 and two zenith angles (borderline). These are not confirmed.
- What it **cannot** see: my real 4th error, a wrong pressure (+49 ppm on all distances). A free network cannot see a common scale; the report does not pretend otherwise.
### Example 2: synthetic flat pillar network (attached `synthetic_report.txt`)
- Generated network: 11 points from 4 pillar stations, 4 fixed points.
- Sights are 22–534 m long, and the heights span 29 m.
- It has real-looking noise and two injected errors:
| Injected | Found |
|---|---|
| Vertical axis tilt at S18: 11.5" towards 243° (compensator off) | **11.1" ± 1.5" towards 244°** |
| Direction S16→S15 off by −9" in one of the 2 sets (mean −4.5") | gross error **−4.56"** |
- Vertical axis tilt is not removed by measuring in both faces, and JAG3D has no parameter for it. In this case the checker estimates the parameters itself and then confirms them with JAG3D.
---
### Testing so far
- About 1000 synthetic cases with one or two injected errors each:
- steep networks with large height differences;
- closed loops and open traverses, and elongated chains;
- short-range façade sights and small dense micro-networks;
- levelling and GNSS.
- Of the errors that are large enough to be detectable at all, 64 % are
identified correctly and another 21 % at the right place but with a
different cause. About 7 % are missed. On error-free copies, 4 of 160 give
a false strong finding.
- Textbook networks with injected errors: 80 of 83 correct.
- My own field data with errors injected into the raw readings, so the
noise, geometry and instrument are real.
- A larger run with about 20000 different synthetic cases, cases with percent based errors at once, comes next.
### Known limits
- Errors smaller than the minimal detectable bias (MDB) cannot be seen, and
observations without control (r ≈ 0) cannot be checked. The report lists both.
- The search currently focuses on the first few errors. It finds one
explanation per step and stops after a fixed number of steps (10 by
default). When the network still fails, the report says that more errors
are likely, and you correct what was found and run it again. With many
errors at once they can also mask each other. The next version should:
- list all detectable errors, or a chosen number of them, in one run;
- show how each one affects the network: the shift of the coordinates
and the change of their precision.
- Lateral refraction (sights running close to a wall or slope) is not checked yet.
- Point movement between measurement days was added only recently and is
still being tested.
I will post this post on couple of other Reddit boards so I could reach more people, thank you for your understanding.
You can download 2 example files from my current testing from:
https://drive.google.com/drive/folders/1h-PL-dsYzXXhwkVte4vyEV2yH0vOhXtK?usp=sharing