Posts: 9
Threads: 1
Joined: 2019-02-25
2021-08-31, 16:19
(This post was last modified: 2021-08-31, 16:21 by Szutek.)
Hello,
Statistics page for a couple of weeks now
( https://www.blitzortung.org/en/station_list.php)
displays stored highest hourly results instead of last hour's results.
Is this an intended change?
Peter
Posts: 1,807
Threads: 63
Joined: 2013-07-23
2021-08-31, 17:38
(This post was last modified: 2021-08-31, 17:42 by cutty.)
(2021-08-31, 16:19)Szutek Wrote: Hello,
Statistics page for a couple of weeks now
(https://www.blitzortung.org/en/station_list.php)
displays stored highest hourly results instead of last hour's results.
Is this an intended change?
Peter Default "sort" is by "counter_used" (USED) column, "descending" ... which will always show stations / region with the highest 'used' count.
On some chosen page selections, or specific sort request, an "orphan" database from August 19th has a higher USED count then the current 'real-time' database, so the table, erroneously, lists those 'orphan' numbers ahead of others. They can be distinguised by the "last signal" date of "August 19", and usually a server name of "whateverRegionName 2" instead of ""whateverRegionName 1"
Issue is a tough one, but Egon's continuing to look at it, as far as I know,.
Additional info, and a hint, at this post, on the Operator's Internal forum:
https://forum.blitzortung.org/showthread...3#pid24203
Posts: 899
Threads: 55
Joined: 2012-06-26
(2021-08-31, 17:38)cutty Wrote: (2021-08-31, 16:19)Szutek Wrote: Hello,
Statistics page for a couple of weeks now
(https://www.blitzortung.org/en/station_list.php)
displays stored highest hourly results instead of last hour's results.
Is this an intended change?
Peter Default "sort" is by "counter_used" (USED) column, "descending" ... which will always show stations / region with the highest 'used' count.
On some chosen page selections, or specific sort request, an "orphan" database from August 19th has a higher USED count then the current 'real-time' database, so the table, erroneously, lists those 'orphan' numbers ahead of others. They can be distinguised by the "last signal" date of "August 19", and usually a server name of "whateverRegionName 2" instead of ""whateverRegionName 1"
Issue is a tough one, but Egon's continuing to look at it, as far as I know,.
Additional info, and a hint, at this post, on the Operator's Internal forum:
https://forum.blitzortung.org/showthread...3#pid24203
Dear Cutty,
your comments did not leave me alone. I added a "current only" option. With this obtion, only stations are listed that were active in the last two hours.
/Egon
Posts: 9
Threads: 1
Joined: 2019-02-25
2021-10-05, 14:21
(This post was last modified: 2021-10-05, 14:22 by Szutek.)
Dear Egon, Cutty,
Adding "current only" option eliminated sorting problems.
However, another problem arose when the statistics were broken down into REGIONS.
Just try it: stations are not sorted by region.
By the way: where was the boundary between EUROPE 1, 2 and 3 established?
Regards,
Peter
Posts: 1,807
Threads: 63
Joined: 2013-07-23
2021-10-05, 17:09
(This post was last modified: 2021-10-05, 17:24 by cutty.)
(2021-10-05, 14:21)Szutek Wrote: Dear Egon, Cutty,
Adding "current only" option eliminated sorting problems.
However, another problem arose when the statistics were broken down into REGIONS.
Just try it: stations are not sorted by region.
By the way: where was the boundary between EUROPE 1, 2 and 3 established?
Regards,
Peter
This is going be confusing. The ' regions' column is technically a ' server reference name' presently. Though it MAY / DOES have to do with geographic 'regional' locations of strokes. This is presently under refinement and evaluation. That DOES NOT necessarily refer to the 'geographic location' of a station! The geographic station location of the STATION is under "Country" column.
'Select' box (top) by geographic regions, then when you do a station or count sort, it should only show stations related to strokes information on that 'region' from 'select' (country, province, etc). As we show strike totals the 'region' on the lists can be confusing, and NOT exactly agree with our 'mind set'. It's currently probably 'best' to think of ' Regions' in the table column, as ' server', rather than 'geography'. Again, use the ' select' box to select a ' geographic' region for station listing of ANY physical stations in that 'area' and which 'server(s)' their signals are evaluated ( Regions column). Those numbers WILL NOT be 'strokes' for that 'narrow' region where the station resides. They will be for the 'parent' 'Server Region' or regions, where those strokes are 'scored'...
Originally, there was only ONE 'region' in the "Regions" column named 'Europe'. All stations reported there. That's where all the stations were processed. All the stations then WERE in Europe, and the signals were pretty much all Europe... there was no real 'boundary' in all likelhood. Then things started growing ....Here came North America, which included South America, Caribbean, etc.. Then Oceania, ... etc.
I notice as this is written, my stations are currently reporting to 4 servers... 2 are the IBOD Blitzortung servers, the others probably test and eval.
Mike
|