Skip to content

OHB current k-index is last observed from up to 3 hours ago and not the current time's estimate #36

@kr8x

Description

@kr8x

hamclock has the last historical value as current - however this is of type 'observed'. The current time is always in the next 3 hour period as estimated.
For the best estimate of what k-index is currently, that is to say 'right now', the first estimated value should be used.

See example below of script script that analysed Fetching json data as well as the daily data and 3 hour at 3/16 20:53, that current time would have been in the 18-21 bin.

csi and ohb return 2.33 which is part of the15-18 bin and is the last observed value.
'Current' k-index, not the last observed k-index, would be in the 18-21 estimate and should have been 3.33

dave@victus:~/ohb/allfiles/kindex$ ./samplejson.bash 2603162052 '3-16 (15|18)'
kindex csi
2.33
kindex ohb
2.33
daily
2026 03 16 -1 3 3 2 2 3 2-1-1 -1 2 2 2 4 6 4-1-1 14 3.00 3.00 2.00 2.00 3.33 2.33 -1.00 -1.00
3 day forecast
NOAA Kp index forecast 16 Mar - 18 Mar
Mar 16 Mar 17 Mar 18
00-03UT 3.67 2.67 2.67
03-06UT 3.67 3.00 2.33
06-09UT 3.00 2.33 2.00
09-12UT 2.33 2.00 1.33
12-15UT 2.00 2.00 1.67
15-18UT 2.67 2.00 2.00
18-21UT 3.00 2.33 2.33
21-00UT 3.00 2.67 2.67
json forecast
"2026-03-16 15:00:00",
"2.33",
"observed",
null
],

"2026-03-16 18:00:00",
"3.33",
"estimated",
null

],

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions