Skip to content

logs

Jump to bottom
Guillaume W. Bres edited this page Jul 2, 2024 · 3 revisions

RUST_LOG and embedded logger

We use the rust logger to generate meaningful logs.
The logs by default are streamed to stdout but it can easily be redirected to a file.
The logger is controled by the $RUST_LOG environment variable and is set by default to info.

You can either define it for that very run:

RUST_LOG=trace rinex-cli -f test_resources/NAV/V2/amel010.21g -i

or export it to the sensitivity you want.

Important basic traces

When invoking the applications, the typical initial traces give important information:

  • files that were successfully loaded
  • files that we failed to load and the reason why (badly formed RINEX?)
  • whether a local position (geodetic marker) is defined in the context or not. This is typically present in Observation or Navigation RINEX files. Having such information gives a predefined geodetic marker for the position solver for example

In the following example, a single file was loaded and it does contain a geodetic marker. We did not specify a workspace, therefore a local folder was created (and it succeeded).

./target/release/rinex-cli -f test_resources/CRNX/V3/ESBC00DNK_R_20201770000_01D_30S_MO.crx.gz -i -a

[2023-12-27T12:27:24Z TRACE rinex::context] loaded observations "test_resources/CRNX/V3/ESBC00DNK_R_20201770000_01D_30S_MO.crx.gz"
[2023-12-27T12:27:24Z INFO  rinex_cli::cli] session workspace is "WORKSPACE/ESBC00DNK_R_20201770000_01D_30S_MO"
[2023-12-27T12:27:24Z INFO  rinex_cli::cli] position defined in dataset: (3582105.291, 532589.7313, 5232754.8054) [ECEF] (lat=0.96855°, lon=0.14760°
Clone this wiki locally