RINEX Data
Identifying what your RINEX data contains will greatly help your workflow.
Several RINEX formats exist and they all contain a lot of different data.
Quite often, the operation you intend to do is not exactly feasible and requires a slight parameter adjustment.
For example, let's say you're interested in performing something in one portion of the day, like solving navigation equations,
but the vehicles or Constellation you selected is almost out of sight. It is important to be able to determine that condition so you can pick up
different vehicles: it would then help the solver converge.
Other examples are typical hardware (receiver) issues, for some reason the signal quality is degrading and you should either inject another RINEX (from a different receiver) or avoid that portion of the day.
All of these conditions are complex and vary a lot.
Although our interface is quite efficient and verbose, sometimes verbosity does not help.
You may simply encounter situations that have never been faced or tested !
The best thing is to open an Issue on Github or drop a message on Discord (see the front page).
In any case, typical scenarios (like bad SNR) end up in typical "errors" that you will rapidly spot if you start using these tools regularly.
