Extra Non-Data Point

GComeau · February 22, 2018, 01:56:22 PM

Hi Everyone,

We are having an issue with WISKI, it is adding a future point into WISKI (a half hour a head) with no data. See attached photo.

Has anyone run into this? If so, how did you fix it?

Thanks,

Gage

@JanNoyes @SteveWKISTERS @cmcguire

cmcguire · February 22, 2018, 02:08:37 PM

Is the 'Write a missing value after the last imported value' checked on the 01.Original import agent? What timeseries is the screenshot from?

GComeau · February 23, 2018, 11:42:16 AM

The time series is from the original import agent, it seems based on what Dave said from Quinte that this is something to do with the latest update. Im gonna fiddle around with this and see if i can fix it.

cmcguire · February 23, 2018, 11:47:55 AM

This isn't happening for us so it should be fixable. What site/time series are you working on?

GComeau · February 23, 2018, 11:55:27 AM

It is happening to two of our sites, Mayhew Creek and Shelter Valley Creek. The data comes through fine through the DPC, but for some reason when it goes to our website and is posted there, it keeps showing 0 even though it polled. The reason being that there is an extra or future value.

The write missing value after data point is not checked in any of these agents.

cmcguire · February 23, 2018, 02:31:05 PM

Weird how it happens to HG but not VB at Mayhew. I thought it might be the agent's equidistant settings but when I use your agent settings with one of our sites I can't get the missing value to show up.

GComeau · May 02, 2018, 11:38:03 AM

Hey Chris (@cmcguire), were you able to find a fix to this or anything? Ill keep trying to play around with it and see if i can get it to work.

cmcguire · May 03, 2018, 09:41:48 AM

The Mayhew Creek near Trenton data is in SODA at 5 minute intervals but your WISKI agent is set up for 1/2 hour intervals. Try switching the 'Interval count:' to 300. I don't have permission to play around with it. Any luck?

News:

Extra Non-Data Point