Cloudlog
Cloudlog copied to clipboard
magicbug
"Undefined" error on Distances Worked page
On the latest station_logbooks branch, I get an "undefined" red error message when trying to plot the following bands on the Distances Worked page:
80m 40m 30m 20m 17m 15m 10m 6m
I've tried another installation with the same version of the station_logbooks branch and don't see any errors. Any idea what would make one work and the other not? I'm thinking it may be some bad distance data or gridsquares?
I've fixed several bugs in station_logbooks regarding this, but obviously issues exists. Without having access to the installation, it's a wild guess.
Do you have several station locations? Are the gridsquares set the same in both installations?
I'll take another look at the code, but at this point, it's difficult to know what to look for.
I do have several station locations (quite a few, due to Parks on the Air activations.) Those gridsquares are different, so maybe that's the issue? Now that I think about it, those are the bands I've used while mobile...
That should not be the problem. The code is looping through the station locations in the defined logbook, and using the defined grid for those contacts.
Are the installations equal? Have you checked that the grids are valid, and no typo?
Installations are equal – although I have nearly 10K QSOs in the database, I sorted through gridsquares to spot check for anything odd. Everything seems to be pretty typical.
That said, there could be bad data in there – I'm not sure how to check 10K gridsquare fields to make sure valid. Is there a way to just throw out any gridsquares that don't result in a distance measurement when using that plotting mechanism?
I've got similar issue with Distances worked that it errors too with undefined.
Some validation might solve it, could run it against the qra library and see if I can be converted back to lat/long if not bin or store it in an array and log an error
That's the thing. The code is validating both the station location and the qso gridsquare.
I tried to provoke an error in the qso and/or in the station location, and it was no problem here, so it's quite difficult to guess what the error might be.
I'll try see if i can find whats barfing on my end could be something obvious
It seems to only do it on certain QSOs as I can narrow it down to a satellite qso subset! thus maybe something I can spot