This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Helicorder not showing new data with FDSN data source #323
Labels
Comments
@rumachan You are correct... it appears reverting that change fixes this issue. I'm attaching a version with that change reverted so you can confirm. Or do you get the heap error again? |
@himmetgencer Please open a separate ticket for SeedLink issue. |
Thanks for answer, I've created new ticket for seedlink issue. Have a nice day... |
@rumachan Ok, I will revert that one change and put it into next release. As for the warning, my thought is that the channel it referenced was not available for some reason. It seems to be fine at the moment (no warning, data coming in for OTVZ HHZ) |
Thank you @dnorgaard-usgs |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have noticed that with our FDSN data source that helicorders are not showing new data. When a user opens the helicorder, the data all display, but as time progresses the new data (that since the helicorder was opened) does not show. However, if the user clicks in the 'empty' part of the helicorder, the zoom window shows data.
This behaviour has been noted by users using both Windows and Linux OSs. I have copies of most versions back to 2.8.3 and have observed that the problem does not occur until version 2.8.7. In the following you can see that ver 2.8.3 and 2.8.6 have helicorders that are updating, but all versions since 2.8.7 have the problem described.
Our FDSN data source in this situation is http://service-nrt.geonet.org.nz/fdsnws/dataselect/1/query for Dataselect and http://service-nrt.geonet.org.nz/fdsnws/station/1/query for Station. This is an open FDSN server you you can try to reproduce this problem.
I wonder if the fix for this bug #182, which coincidentally for was for me, has introduced this problem?
Thank you.
The text was updated successfully, but these errors were encountered: