Gnssrefl

Latest version: v3.11.0

Safety actively analyzes 723717 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 30

3.6.6

added debug option to remove the try in gnssir_cl.py - because that
makes it really hard to know why your run is crashing. If you set debug to
T, you will have more information.

optional savearcs option to gnssir: writeout plain text files of
elevation angle and detrended snr
using savearcs option. This is bare bones ... not really ready for prime time

fixed bug in daily_avg for people that try to analyze sites with no results. it now
politely exits for this case.

added peak 2 noise to subdaily summary plot

added gnssir output that tells you to use the (new) debug option in error situations.

exits when people try to use illegal refraction models in gnssir_input

added warning for people that don't input legal elevation angle lists to gnssir_input

added documentation for quickplt so people can look at raw SNR data.

added subdaily option to allow different required amplitude values for different frequencies.
It uses frequency list in the json to set the order of those amplitudes.

3.6.5

July 29, 2024

Various minor changes.

Updated nmea2snr ultra orbit choices : first tries GFZ and then Wuhan (wum2)

Felipe Nievinski improved how the NMEA files are accessed in nmea2snr.
Uses a temporary file location which is deleted after use.

3.6.4

July 22, 2024

I added a final plot to subdaily. Doesn't have the spline in it. Uses a line instead
of a symbol. But otherwise it isn't new information.

I added a simple file for a priori lat lon and ellipsoidal height values.
It should be located in $REFL_CODE/llh_local.txt. and the values should simply
be 4 ch station name lat lon height. NO COMMAS between then, simply spaces.
comment lines are allowed if preceded by percent sign. I would prefer station names to be
lowercase, but it allows and checks uppercase.
This kind of file would be particularly useful for NMEA people as it allows you to
store your a priori receiver coordinates and don't have to worry about it being
overwritten if you change your analysis strategy.

3.6.3

July 19, 2024

added option in rinex3_snr to correct illegal filenames that Earthscope is distributing
to the world. it assumes they used rinex 2.11 filename but filled it with Rinex 3 data.
and used upper case instead of lower case.

Am trying to add version number to print out to all major codes in gnssrefl.

3.6.2

July 17, 2024

There was a bug in the RINEX3 to RINEX2 conversion code.
This should be fixed - and the code is less silly now. I think.
Thanks to Drew Lindow for finding this bug.

deleted gnssrefl/data/gpt_1wA.pickle. I do not think it is used.

3.6.1

Versions 3.6.0 and 3.6.1 are about the same. I had some issues with the version tags.

July 15, 2024

Daily Lomb Scargle results are sorted in time instead of frequency.

Fixed bug in rinex3_snr (inputs changed)

You can access 1-sec RINEX3 GNET archive data if you have
an account and the utility lftp installed.

Allow snr choice to be stored in the gnssir_input json. For now you have
to add it to the json by
hand, but I am happy to accept a PR that adds it explicitly. If
you do that, you want to make sure that the downstream code (gnssir) can
still change the snr choice on the command line. Right now it assumes
if it finds a snr value in the json, it should use it.

Page 4 of 30

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.