Check observation quality
Score a RINEX file with Crux before you spend processing time on it.
When to use this
Before processing, after a field session, or when a client delivers data. A quality check catches gaps, multipath, and cycle slips while a re-observation is still cheap.
Steps
- Open Crux from the dashboard and upload one or more observation files (RINEX 2 or 3; compressed files are handled automatically).
- Pick an analysis mode: Fast for a quick score, Flash or Full for deeper multi-GNSS analysis, or TEQC for the classic report format. Each mode has its own per-observation-file credit rate: Fast is the cheapest and Full the dearest; the pricing page lists them. All four are on the Free plan.
- Start the analysis and watch progress live; typical files finish in minutes.
- Read the results: overall score, per-indicator breakdown, and per-satellite detail.
- Export to CSV or Excel, or click Share to send a read-only report link to a client or colleague.
Reading the score
The composite score summarizes completeness, cycle slips, multipath, and signal strength. Treat anything flagged in the breakdown as a reason to inspect before processing, not as an automatic rejection: short baselines and kinematic work tolerate more than long static sessions.
No account yet?
Crux runs on our servers, so a report needs a free account: create one, upload the file, and the full breakdown comes back with no card and no trial limit.
Refund boundaries
| What happened | Credit outcome |
|---|---|
| Credit-hold positioning runs: reported platform, engine or output-validation failure. | The held credits are released when the failure is settled, including reported engine failures after compute starts. |
| Legacy charged runs: recognized infrastructure failure such as dispatch, missing stored file, ephemeris download, engine startup, internal error, or unusable analysis output. | Automatically credited back in full. |
| Legacy charged runs: the positioning engine explicitly rejects the input before its first compute binary starts. | Automatically credited back in full. |
| Legacy charged runs: compute started but the data could not be solved, or the failure is not on the refundable-code list. | Charged. Running the engine consumes compute even without a usable result. |
| Credit-hold positioning runs: user cancellation before or after the recorded engine-start marker. | Before the marker: release the hold. After the marker: charge it. The marker is set before executor entry, so waiting for an engine slot can already count as started. |
Legacy automatic credit reconciliation runs every 10 minutes for tasks submitted within the current UTC calendar month. A legacy task that fails after its submission month ends is outside that refund window. Credit-hold positioning runs use their own settlement path instead.
This table describes quality-check and precise-positioning task credits, not subscription or cash refunds. A failure count is not a refund receipt; consult your credit ledger for the settled amount. Other or unclassified failures are not proof that your data was at fault.