Hi Bryan,
it does indeed help - I will be making better input validation for that
part of the interface. In fact, it's already on the list for 0.1.4. ;-)
If you want to save a log file, you should use -D logfile.txt - whereas -d
gives you console logging. I don't think traceback messages like the one
you posted here get saved to the log file, though, so it's better for me to
get your console log in crash cases like this.
Thank you very much! And I hope you try out 0.1.3 as well ;-)
--
Rune / 5Q5R
On Wed, 16 Oct 2019 at 15:51, bryburns via Groups.Io <bryburns=
[email protected]> wrote:
Rune,
I have noticed that you save the "Calibration standards" information in
the ".ini" file for nanoVNA-Saver. Great idea. I also observe that after
loading the information from the ".ini" file you still have to click
"Apply" on the Calibration window for the new values to be used even though
you can see them on the "Calibration" form. It seems to me that when the
user clicks "Load" to pick a set of stored "Calibration standards" that you
should "Apply" them automatically and not require the user to click
"Apply." Just a thought.
I started nanoVNA-Saver 0.1.2 in a command window using
"nanovna-saver.v0.1.2.exe -d testlog.txt" Here is the last several lines
on the screen after the crash when changing values on the Calibration form
in the "Calibration standards" box.
2019-10-16 07:38:41,567 - NanoVNASaver.SweepWorker - DEBUG - Sending
"updated" signal
2019-10-16 07:38:41,567 - NanoVNASaver.SweepWorker - DEBUG - Resetting
NanoVNA sweep to full range: 50000 to 900000016
2019-10-16 07:38:41,636 - NanoVNASaver.SweepWorker - DEBUG - Sending
"finished" signal
2019-10-16 07:38:54,382 - NanoVNASaver.Calibration - DEBUG - Loading
calibration no 0
2019-10-16 07:38:54,383 - NanoVNASaver.Calibration - INFO - Loading:
HighOrderForBNC
Traceback (most recent call last):
File "NanoVNASaver\Calibration.py", line 447, in calculate
ValueError: could not convert string to float:
The log file I specified after -d did not get saved.
I hope this helps you find the issue that caused the crash.
--
Bryan, WA5VAH
