Page 1 of 1

graphs and raw data not fitting

Posted: Wed Apr 01, 2009 5:13 pm
by wfpost
Yesterday I saw a brief steep peak around 22:00 with my indoor sensor connected to the RMS300.
I was looking through the raw data and couldn´t find anything wrong with it.

Two things came to my mind:

1. The glitch seems to be caused by the th1-min data, which I cannot look trough in meteohub GUI (see graphs) th1-max does not show the glitch

2. In total it seems the raw data and the graph drawn do not correspond with each other for all data.
e.g. the raw data for 21:00 showing a temp of 18.9 but the graph displaying 19.8 :dry:
(see first plot below)
I already started a recomputation, didn´t change anything.
20090331210038 th1 189 47 0074
20090331210121 th1 189 47 0074
20090331210204 th1 188 47 0073
20090331210247 th1 188 47 0073
...
20090331234528 th1 169 49 0061
20090331234611 th1 169 49 0061
20090331234654 th1 169 49 0061
20090331234737 th1 169 49 0061
20090331234820 th1 169 49 0061
20090331234903 th1 169 49 0061
20090331234946 th1 169 49 0061
20090331235029 th1 169 49 0061
20090331235112 th1 169 49 0061
20090331235155 th1 169 49 0061
20090331235238 th1 169 49 0061
20090331235321 th1 168 49 0060
20090331235404 th1 168 49 0060
20090331235530 th1 168 49 0060
20090331235613 th1 168 49 0060
20090331235656 th1 168 49 0060
20090331235822 th1 168 49 0060
20090331235905 th1 168 49 0060
Image
Image
Image
Image

raw data for spoke th1 period:
attached [file name=th1_raw.txt size=7648]http://www.meteohub.de/joomla/images/fb ... h1_raw.txt[/file]

Re:graphs and raw data not fitting

Posted: Wed Apr 01, 2009 6:08 pm
by skyewright
wfpost wrote:Yesterday I saw a brief steep peak around 22:00 with my indoor sensor connected to the RMS300.
I was looking through the raw data and couldn´t find anything wrong with it.
You've probably already taken this into account, but just in case not I'll mention that the "raw" data is stored with UTC based timestamps.

How does your local time compare to UTC at present?

Re:graphs and raw data not fitting

Posted: Wed Apr 01, 2009 9:27 pm
by wfpost
thanks for your hint.
no I forgot about the timestamps being in UTC :silly:

looking again through the raw data I found the glitch.

20090331195233 th1 198 47 0082
20090331195316 th1 198 47 0082
20090331195359 th1 198 47 0082
20090331195442 th1 198 47 0082
20090331195500 th1 -203 91 -214
20090331195525 th1 198 47 0082
20090331195608 th1 198 47 0082
20090331195651 th1 198 47 0082

Cheers for the help ...