You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We observe some unexpected content (i.e. not relevant to the request) in the response to queries to our availability service. From a few quick cross-checks to other endpoiNts this behaviour seems to be more general, indicating a problem with the software rather the of our specific node.
The first impression is that the query selection is not doing exactly what is expected or requested by the user.
Examing the following day's response or looking into WFcatalog, the original source of availability, these "negative timespan" entries are generated from timespans found in this following day.
From the WFcatalog, output of the relevant information:
#Network Station Location Channel Quality SampleRate Earliest Latest
CH VDR HGE D 200.0 2024-08-22T12:50:00.000000Z 2024-08-22T12:46:04.915000Z
CH VDR HGE D 200.0 2024-08-26T10:26:34.915000Z 2024-08-26T11:46:00.000000Z
It has the latest before the earliest.
"Earliest" on the first line is wrong, it is the requested start time, but there is no data at that time.
"Latest" is also wrong, it is the correct latest data available for that day, but ends before the requested start time.
Summary
We observe some unexpected content (i.e. not relevant to the request) in the response to queries to our availability service. From a few quick cross-checks to other endpoiNts this behaviour seems to be more general, indicating a problem with the software rather the of our specific node.
The first impression is that the query selection is not doing exactly what is expected or requested by the user.
Evidence, by one example
Preliminary analisis
There are actually two different cases of lines which could be considered useless:
A different view of the same (last value is the segment length):
Examing the following day's response or looking into WFcatalog, the original source of availability, these "negative timespan" entries are generated from timespans found in this following day.
From the WFcatalog, output of the relevant information:
Possible solution
Correct query in order to not return timespans which are not relevant to the requested time span, avoid also the non informative zero lenth timespans.
The text was updated successfully, but these errors were encountered: