subject:"\[weewx\-user\] When did the blast wave of the eruption \"hit\" your station\? \- extract your data"

Also, I found a bug in calculating the smooth (spline fit) curve which is 
removed to highlight the eruption events. Added display of the points used 
to calculate the fitted curve.

On Saturday, January 22, 2022 at 4:32:47 p.m. UTC-4 morr...@gmail.com wrote:

> Forgot that, thanks for the reminder. Added now.
>
> On Saturday, January 22, 2022 at 4:22:51 p.m. UTC-4 storm...@gmail.com 
> wrote:
>
>> Nice work (Morrowwn  thanks!).  If you have any nulls in the data during 
>> the selected timeframe, change the query to read:  (Cameron D thanks!)
>>
>> *query = "select datetime, barometer from archive where datetime > %.0f 
>> and datetime < %.0f and barometer is not null order by dateTime;" % 
>> (start_time, stop_time)*
>>
>>
>>
>>
>> [image: hunga_tonga.png]
>>
>> If you want the bars closer to the rise and falls of the events, need to 
>> adjust the speed of sound slightly.
>> On Saturday, January 22, 2022 at 2:37:09 PM UTC-5 pmcg...@gmail.com 
>> wrote:
>>
>>> WOW!  This is some interesting data, here is my location in Northern 
>>> Utah.  Looks like the reverse may be a little off in calculation but this 
>>> made it easy to find instead of hunting through the data.
>>>
>>> Great Work!
>>> [image: hunga_tonga.png]
>>> On Saturday, January 22, 2022 at 12:16:45 PM UTC-7 morr...@gmail.com 
>>> wrote:
>>>
 Did an update to my script at: 
 https://github.com/morrowwm/weewx_tonga_browse

 Mostly incorporating additions from Cameron (thanks!)

 All parameters you likely want to set are near the top of the script.

1. support for mysql (untested, I don't have a mysql based weewx 
installation)
2. calculation and display of all three initial arrival, arrival 
from opposite direction, and second arrival after one trip around the 
 globe
3. highlighting of the three events with grey bars
4. cubic spline curve fit of raw data and use of that fit to remove 
the base pressure variations. The new smoothing_hours parameter can be 
 used 
to control how close the fit is. 
5. changed the display of data to highlight the extracted events 
and subdue the original data, other cosmetic changes

 I had a data outage about 26 hours after the event, we're quite a 
 distance from Tonga, plus a major storm was clearing out in our area. So 
 not obviously anything unusual happened.

 Some scientist might be interested in the arrival times of all this 
 data, though.
 [image: hunga_tonga.png]

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/986683ea-1046-4cb4-9aa4-2a41797c7303n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

Forgot that, thanks for the reminder. Added now.

On Saturday, January 22, 2022 at 4:22:51 p.m. UTC-4 storm...@gmail.com 
wrote:

> Nice work (Morrowwn  thanks!).  If you have any nulls in the data during 
> the selected timeframe, change the query to read:  (Cameron D thanks!)
>
> *query = "select datetime, barometer from archive where datetime > %.0f 
> and datetime < %.0f and barometer is not null order by dateTime;" % 
> (start_time, stop_time)*
>
>
>
>
> [image: hunga_tonga.png]
>
> If you want the bars closer to the rise and falls of the events, need to 
> adjust the speed of sound slightly.
> On Saturday, January 22, 2022 at 2:37:09 PM UTC-5 pmcg...@gmail.com wrote:
>
>> WOW!  This is some interesting data, here is my location in Northern 
>> Utah.  Looks like the reverse may be a little off in calculation but this 
>> made it easy to find instead of hunting through the data.
>>
>> Great Work!
>> [image: hunga_tonga.png]
>> On Saturday, January 22, 2022 at 12:16:45 PM UTC-7 morr...@gmail.com 
>> wrote:
>>
>>> Did an update to my script at: 
>>> https://github.com/morrowwm/weewx_tonga_browse
>>>
>>> Mostly incorporating additions from Cameron (thanks!)
>>>
>>> All parameters you likely want to set are near the top of the script.
>>>
>>>1. support for mysql (untested, I don't have a mysql based weewx 
>>>installation)
>>>2. calculation and display of all three initial arrival, arrival 
>>>from opposite direction, and second arrival after one trip around the 
>>> globe
>>>3. highlighting of the three events with grey bars
>>>4. cubic spline curve fit of raw data and use of that fit to remove 
>>>the base pressure variations. The new smoothing_hours parameter can be 
>>> used 
>>>to control how close the fit is. 
>>>5. changed the display of data to highlight the extracted events and 
>>>subdue the original data, other cosmetic changes
>>>
>>> I had a data outage about 26 hours after the event, we're quite a 
>>> distance from Tonga, plus a major storm was clearing out in our area. So 
>>> not obviously anything unusual happened.
>>>
>>> Some scientist might be interested in the arrival times of all this 
>>> data, though.
>>> [image: hunga_tonga.png]
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fb0fd561-2540-43bc-a1d9-1edf12ec74e9n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

2022-01-22 Thread storm...@gmail.com

Nice work (Morrowwn  thanks!).  If you have any nulls in the data during 
the selected timeframe, change the query to read:  (Cameron D thanks!)

*query = "select datetime, barometer from archive where datetime > %.0f and 
datetime < %.0f and barometer is not null order by dateTime;" % 
(start_time, stop_time)*




[image: hunga_tonga.png]

If you want the bars closer to the rise and falls of the events, need to 
adjust the speed of sound slightly.
On Saturday, January 22, 2022 at 2:37:09 PM UTC-5 pmcg...@gmail.com wrote:

> WOW!  This is some interesting data, here is my location in Northern 
> Utah.  Looks like the reverse may be a little off in calculation but this 
> made it easy to find instead of hunting through the data.
>
> Great Work!
> [image: hunga_tonga.png]
> On Saturday, January 22, 2022 at 12:16:45 PM UTC-7 morr...@gmail.com 
> wrote:
>
>> Did an update to my script at: 
>> https://github.com/morrowwm/weewx_tonga_browse
>>
>> Mostly incorporating additions from Cameron (thanks!)
>>
>> All parameters you likely want to set are near the top of the script.
>>
>>1. support for mysql (untested, I don't have a mysql based weewx 
>>installation)
>>2. calculation and display of all three initial arrival, arrival from 
>>opposite direction, and second arrival after one trip around the globe
>>3. highlighting of the three events with grey bars
>>4. cubic spline curve fit of raw data and use of that fit to remove 
>>the base pressure variations. The new smoothing_hours parameter can be 
>> used 
>>to control how close the fit is. 
>>5. changed the display of data to highlight the extracted events and 
>>subdue the original data, other cosmetic changes
>>
>> I had a data outage about 26 hours after the event, we're quite a 
>> distance from Tonga, plus a major storm was clearing out in our area. So 
>> not obviously anything unusual happened.
>>
>> Some scientist might be interested in the arrival times of all this data, 
>> though.
>> [image: hunga_tonga.png]
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/80a10960-7af0-44ec-9fd8-bb0a9cf74e55n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

The curve fit (solid black line) isn't matching your data (turquoise dots) 
really well. Try reducing smoothing_hours to maybe 12, or 6. 

The true model to estimate arrival times accurately is probably a lot more 
complicated than time = distance / constant_velocity. 

On Saturday, January 22, 2022 at 3:37:09 p.m. UTC-4 pmcg...@gmail.com wrote:

> WOW!  This is some interesting data, here is my location in Northern 
> Utah.  Looks like the reverse may be a little off in calculation but this 
> made it easy to find instead of hunting through the data.
>
> Great Work!
> [image: hunga_tonga.png]
> On Saturday, January 22, 2022 at 12:16:45 PM UTC-7 morr...@gmail.com 
> wrote:
>
>> Did an update to my script at: 
>> https://github.com/morrowwm/weewx_tonga_browse
>>
>> Mostly incorporating additions from Cameron (thanks!)
>>
>> All parameters you likely want to set are near the top of the script.
>>
>>1. support for mysql (untested, I don't have a mysql based weewx 
>>installation)
>>2. calculation and display of all three initial arrival, arrival from 
>>opposite direction, and second arrival after one trip around the globe
>>3. highlighting of the three events with grey bars
>>4. cubic spline curve fit of raw data and use of that fit to remove 
>>the base pressure variations. The new smoothing_hours parameter can be 
>> used 
>>to control how close the fit is. 
>>5. changed the display of data to highlight the extracted events and 
>>subdue the original data, other cosmetic changes
>>
>> I had a data outage about 26 hours after the event, we're quite a 
>> distance from Tonga, plus a major storm was clearing out in our area. So 
>> not obviously anything unusual happened.
>>
>> Some scientist might be interested in the arrival times of all this data, 
>> though.
>> [image: hunga_tonga.png]
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5d379045-e055-4643-afd0-2693aac5133fn%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

2022-01-22 Thread pmcg...@gmail.com

WOW!  This is some interesting data, here is my location in Northern Utah.  
Looks like the reverse may be a little off in calculation but this made it 
easy to find instead of hunting through the data.

Great Work!
[image: hunga_tonga.png]
On Saturday, January 22, 2022 at 12:16:45 PM UTC-7 morr...@gmail.com wrote:

> Did an update to my script at: 
> https://github.com/morrowwm/weewx_tonga_browse
>
> Mostly incorporating additions from Cameron (thanks!)
>
> All parameters you likely want to set are near the top of the script.
>
>1. support for mysql (untested, I don't have a mysql based weewx 
>installation)
>2. calculation and display of all three initial arrival, arrival from 
>opposite direction, and second arrival after one trip around the globe
>3. highlighting of the three events with grey bars
>4. cubic spline curve fit of raw data and use of that fit to remove 
>the base pressure variations. The new smoothing_hours parameter can be 
> used 
>to control how close the fit is. 
>5. changed the display of data to highlight the extracted events and 
>subdue the original data, other cosmetic changes
>
> I had a data outage about 26 hours after the event, we're quite a distance 
> from Tonga, plus a major storm was clearing out in our area. So not 
> obviously anything unusual happened.
>
> Some scientist might be interested in the arrival times of all this data, 
> though.
> [image: hunga_tonga.png]
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9e6a893a-c4d2-4975-81c3-7835e5372073n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

Did an update to my script 
at: https://github.com/morrowwm/weewx_tonga_browse

Mostly incorporating additions from Cameron (thanks!)

All parameters you likely want to set are near the top of the script.

   1. support for mysql (untested, I don't have a mysql based weewx 
   installation)
   2. calculation and display of all three initial arrival, arrival from 
   opposite direction, and second arrival after one trip around the globe
   3. highlighting of the three events with grey bars
   4. cubic spline curve fit of raw data and use of that fit to remove the 
   base pressure variations. The new smoothing_hours parameter can be used to 
   control how close the fit is. 
   5. changed the display of data to highlight the extracted events and 
   subdue the original data, other cosmetic changes

I had a data outage about 26 hours after the event, we're quite a distance 
from Tonga, plus a major storm was clearing out in our area. So not 
obviously anything unusual happened.

Some scientist might be interested in the arrival times of all this data, 
though.
[image: hunga_tonga.png]

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6e11ab35-5a24-4357-a90f-905706abe03cn%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

2022-01-21 Thread Ted Frohling

Thanks very much for the new python script. It works.

The other three files looked great as well.

They were all for Tucson, AZ, USA

ted

On 1/20/22 6:12 PM, 'Cameron D' via weewx-user wrote:

yes, definitely looks like there is no data.
I have attached another version of mine, in which the trend line is
disabled by default, but I suspect that would just delay the
inevitable and it would crash trying to do the plot.

I also fixed up a few plotting errors in my code to do with the
mysteries (to me) of layer ordering.
I also had a background bar showing either side of expected arrival -
in this version I have now changed that to start at the expected
arrival and stop 1 hour later.

On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu wrote:

Hello,
Not being a programmer, I probably shouldn't have messed with
this, but being curious...

I tried the code posted on github as well as the one by Cameron D.
In both cases I got the following error:
```
root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py
[file from Cameron D]

distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15
09:52:39)
opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
second time around pulse arrival at 1642385471 (2022-01-16
21:11:10)
Traceback (most recent call last):
File "./tonga.py", line 178, in
plot_burst( cursor, arrival_time, hour_span, "primary" )
File "./tonga.py", line 54, in plot_burst
coeff = np.polyfit(xdata, ydata, background_order )
File "<__array_function__ internals>", line 180, in polyfit
File
"/usr/local/lib/python3.8/dist-packages/numpy/lib/polynomial.py",
line 638, in polyfit
raise TypeError("expected non-empty vector for x")
TypeError: expected non-empty vector for x
```
I added my lat/lon information but may have missed something else
I need to change. Python modules were installed as directed. Copy
of weewx.sdb is in the same directory as the program.
Thanks.
Bob
On Wednesday, January 19, 2022 at 10:32:49 AM UTC-5
morr...@gmail.com wrote:

On Wednesday, January 19, 2022 at 12:42:04 a.m. UTC-4 Cameron
D wrote:

* as you get closer to the equator, tidal changes
dominate the baseline in that timescale - I tried
higher order polynomials, but they are next to useless.

I also had little luck with higher order polynomials to remove
the general trend.

I've put the script here:
https://github.com/morrowwm/weewx_tonga_browse

--
You received this message because you are subscribed to the Google
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/71655988-a5d6-4771-bb56-12fa455f24f2n%40googlegroups.com
.

--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/f667e702-0e2d-61a7-1e18-74bc6916ecb3%40gmail.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

2022-01-21 Thread paul.ba...@gmail.com

Hello,
I did a little experience using LOWESS (also called  LOESS in some places) 
with success I think. In my experience it is the best method I tried over 
the years.
This non parametric local smoothing exists for many lingages including 
Fortran (which I used...), C, Python, R etc.
It use three parameters: a smoothing factor, adjusted between 0 and 1. You 
have to experiment to find the best according to your problem. In my case 
.03 was good.. the second is the number of iterations, 1 to...; I adopted 
2, the doc says any larger number will not change antthing; the last one is 
a speed-up factor; I choose 0 (= No Speed-Up). With 3639 data points, the 
processing time is barely seen (10 years old Intel i3770 processor). 

The upper pannel represent the original data in blue and the smoothed one 
on red.
The lower pannel represent the difference between the original data and the 
smoothed one.
The time (T) is given in days, starting at 0:00:00 UTC on January 15th. The 
last point is at 24:00:00 on January 18th.
The vertical axis is in mbar. My altitude is 410 meters.

The first and second pulses are very clearely visible. There are a few 
other signals needing interpretation...  Also noticable is the smoother 
signal before the first spike compared to the rest of the data.
Have a nice week-end, Paul
Le Friday, January 21, 2022 à 4:38:59 PM UTC+1, bgra...@umw.edu a écrit :

> Thanks all, bad copy of weewx.sdb. All is well.
>
> On Thursday, January 20, 2022 at 5:25:50 PM UTC-5 morr...@gmail.com wrote:
>
>> It looks like you retrieved no data. It calculated decent looking arrival 
>> times, so no problem with the change you made?
>>
>> Try just a query for data spanning the first arrival. From a shell prompt:
>>
>> sqlite3 weewx.sdb "select datetime, barometer from archive where datetime 
>> > 1642258360-10 and datetime < 1642258360+10 order by dateTime;"
>>
>>
>> On Thursday, January 20, 2022 at 1:29:36 p.m. UTC-4 bgra...@umw.edu 
>> wrote:
>>
>>> I tried the code posted on github as well as the one by Cameron D. In 
>>> both cases I got the following error:
>>> ```
>>> root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
>>> from Cameron D]
>>>
>>> distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
>>> 09:52:39)
>>>   opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
>>>   second time around pulse arrival at 1642385471 (2022-01-16 
>>> 21:11:10)
>>> Traceback (most recent call last):
>>>   File "./tonga.py", line 178, in 
>>> plot_burst( cursor, arrival_time, hour_span, "primary" )
>>>   File "./tonga.py", line 54, in plot_burst
>>> coeff = np.polyfit(xdata, ydata, background_order )
>>>   File "<__array_function__ internals>", line 180, in polyfit
>>>   File "/usr/local/lib/python3.8/dist-packages/numpy/lib/polynomial.py", 
>>> line 638, in polyfit
>>> raise TypeError("expected non-empty vector for x")
>>> TypeError: expected non-empty vector for x
>>> ```
>>> I added my lat/lon information but may have missed something else I need 
>>> to change. Python modules were installed as directed. Copy of weewx.sdb is 
>>> in the same directory as the program.
>>> Thanks.
>>> Bob
>>> On Wednesday, January 19, 2022 at 10:32:49 AM UTC-5 morr...@gmail.com 
>>> wrote:
>>>
 On Wednesday, January 19, 2022 at 12:42:04 a.m. UTC-4 Cameron D wrote:

>
>- as you get closer to the equator, tidal changes dominate the 
>baseline in that timescale - I tried higher order polynomials, but 
> they are 
>next to useless.
>
> I also had little luck with higher order polynomials to remove the 
 general trend.

 I've put the script here: 
 https://github.com/morrowwm/weewx_tonga_browse

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b0bbb6da-9267-4aa2-a6de-c3c089c2d5dan%40googlegroups.com.

Tonga-1.pdf
Description: Adobe PDF document

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

2022-01-21 Thread bgra...@umw.edu

Thanks all, bad copy of weewx.sdb. All is well.

On Thursday, January 20, 2022 at 5:25:50 PM UTC-5 morr...@gmail.com wrote:

> It looks like you retrieved no data. It calculated decent looking arrival 
> times, so no problem with the change you made?
>
> Try just a query for data spanning the first arrival. From a shell prompt:
>
> sqlite3 weewx.sdb "select datetime, barometer from archive where datetime 
> > 1642258360-10 and datetime < 1642258360+10 order by dateTime;"
>
>
> On Thursday, January 20, 2022 at 1:29:36 p.m. UTC-4 bgra...@umw.edu wrote:
>
>> I tried the code posted on github as well as the one by Cameron D. In 
>> both cases I got the following error:
>> ```
>> root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
>> from Cameron D]
>>
>> distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
>> 09:52:39)
>>   opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
>>   second time around pulse arrival at 1642385471 (2022-01-16 21:11:10)
>> Traceback (most recent call last):
>>   File "./tonga.py", line 178, in 
>> plot_burst( cursor, arrival_time, hour_span, "primary" )
>>   File "./tonga.py", line 54, in plot_burst
>> coeff = np.polyfit(xdata, ydata, background_order )
>>   File "<__array_function__ internals>", line 180, in polyfit
>>   File "/usr/local/lib/python3.8/dist-packages/numpy/lib/polynomial.py", 
>> line 638, in polyfit
>> raise TypeError("expected non-empty vector for x")
>> TypeError: expected non-empty vector for x
>> ```
>> I added my lat/lon information but may have missed something else I need 
>> to change. Python modules were installed as directed. Copy of weewx.sdb is 
>> in the same directory as the program.
>> Thanks.
>> Bob
>> On Wednesday, January 19, 2022 at 10:32:49 AM UTC-5 morr...@gmail.com 
>> wrote:
>>
>>> On Wednesday, January 19, 2022 at 12:42:04 a.m. UTC-4 Cameron D wrote:
>>>

- as you get closer to the equator, tidal changes dominate the 
baseline in that timescale - I tried higher order polynomials, but they 
 are 
next to useless.

 I also had little luck with higher order polynomials to remove the 
>>> general trend.
>>>
>>> I've put the script here: https://github.com/morrowwm/weewx_tonga_browse
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/27166f36-0ac5-43aa-a41d-abd2afe267f3n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

I don't understand the physics of it. As per the last few postings the 
speed of sound may be variable enough to show up here.

I would just tinker with the speed of sound parameter and see if you can 
make all peaks look sensible. At least you have data at a good frequency.



On Friday, 21 January 2022 at 4:21:36 pm UTC+10 ti...@skybase.net wrote:

> Hi Cameron,
>
> Beut! - that worked a treat - thanks :)
>
> I've also noticed that the return pulse highlight appears to be off, see 
> pic below. Or is it meant to be like that ?
>
> thanks
>
> Tim
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/700bfa67-e531-4906-85d0-2ef9c9f88206n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

I assume your DB is storing in US units - mine is metricWX (I knew one day 
it would be useful to have done that!)
One easy way is to modify the queries yourself - where the  query (2 
queries in my code)  specifies "barometer", replace with 
"barometer * 33.8639 as barometer"

On Friday, 21 January 2022 at 3:36:31 pm UTC+10 ti...@skybase.net wrote:

> Hi all,
>
> The script works well on my data but the pressure readout is in inHg 
> rather than hPa. 
>
> Can an option be inserted to have hPa computed before plotting ?
>
> thanks
>
> Tim
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a6b52952-3ace-4a2c-91f6-b71d5611b7cdn%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

If I recall looking @ MADIS 15 minute data, it least for me, the pressure 
of the opposite wave did drop a some before the major spike. After changing 
the colors on the charts, it aligns with the first drop in pressure.

On Thursday, January 20, 2022 at 11:28:41 PM UTC-5 Cameron D wrote:

> There are certainly uncertainties in the barometric data timings. My 
> system is probably a worst case - it only reports a value every 15 minutes, 
> and I don't know if that is an average of the previous 15 minutes or just a 
> snapshot reading at the transition time. So for me 20 minutes is within the 
> uncertainty.
> Also, I don't know if it is expected, but the  pulses that travelled 
> further show only the negative part, which comes after the positive. So 
> there is extra lag in that.
>
> I derived a speed by fitting data to Australian bureau charts, and they 
> only show 30 minute samples, so my speed is hardly definitive.  I would 
> expect it to vary a bit around the globe.  The average speed I derived from 
> the first peak alone was 0.30 m/s, so that is either an indicator of the 
> uncertainty in the fitting or that the average speed increased as it 
> progressed.
> On Friday, 21 January 2022 at 2:05:49 pm UTC+10 storm...@gmail.com wrote:
>
>> Yes, the image files are being produced. Only thing I noticed was the 
>> arrival time for the opposite pulse is off by approx. 20 minutes according 
>> to the actual PWS data, this could be due to the wave speeding up or 
>> slowing down as it made its way around the globe.  Right now I'm using your 
>> default settings.
>>
>> On Thursday, January 20, 2022 at 10:40:36 PM UTC-5 Cameron D wrote:
>>
>>> the RankWarning is just a warning, you should still have image files 
>>> produced.  I expect the polyfit it just ignores higher order terms and just 
>>> returns a quadratic.
>>>
>>> That is because the polynomial is a poor representation of the 
>>> background, and the spline fit works better, if you get the parameters 
>>> correct.
>>>
>>> Initially you are better just to view the results without trend 
>>> removal.  If the peaks  do not stand out then  background removal is 
>>> unlikely to help much.
>>> Also, with my code,  make sure you start with oversampling set to 1. 
>>> Only adjust it if you see a stair-step effect.
>>>
>>> On Friday, 21 January 2022 at 1:09:28 pm UTC+10 storm...@gmail.com 
>>> wrote:
>>>
 Modified the query and added the print statement as suggested 
 by Cameron D and here are the results:

 *Morrowwn Script:*

 raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
 distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
 10:47:08)
 select datetime, barometer from archive where datetime > 1642172400 and 
 datetime < 1642693629 order by dateTime;
 Traceback (most recent call last):
   File "tonga_barometer.py", line 47, in 
 coeff = np.polyfit(xdata, ydata, 2)
   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
 590, in polyfit
 y = NX.asarray(y) + 0.0
 TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'


 *Cameron D Script*:

 raspberrypi:~/Desktop/Tonga $ python3 tonga_baro.py
 distance to eruption 12255.7 km arrival at 1642258384 (2022-01-15 
 09:53:04)
   opposite pulse arrival at 1642306911 (2022-01-15 23:21:50)
   second time around pulse arrival at 1642383509 (2022-01-16 
 20:38:29)
 query returned 96 data points
 query returned 96 data points
 query returned 95 data points
 tonga_baro.py:108: RankWarning: Polyfit may be poorly conditioned
   coeff = np.polyfit(xdata, ydata, 5 )

 Note: LAT/Long and speed of sound are identical in both scripts.
 On Thursday, January 20, 2022 at 9:27:13 PM UTC-5 Cameron D wrote:

> and add a debug printout for how many result lines there are after ...
> result = cursor.fetchall()
> add the line:
> 
> *print( "query returned {} data points".format(len(result)))*
>
> On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:
>
>> To eliminate NULL data points use a query like:
>> select datetime, barometer from archive where datetime > 1642172400 
>> and datetime < 1642693629* and barometer is not null *order by 
>> dateTime;
>>  You could add the part in bold into the query in the python script.
>>
>> Of course, if they are all null...
>>
>> On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com 
>> wrote:
>>
>>> Download the latest script from 
>>> https://github.com/morrowwm/weewx_tonga_browse. Beside installing 
>>> the Python Modules Vince stated above, I needed to also install  
>>> python3-scipy. I do have data between 1642172400 and 1642693629; 
>>> except for a couple "null" in that time period.   So when I run the 
>>> script, 
>>> I get the following

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

There are certainly uncertainties in the barometric data timings. My system 
is probably a worst case - it only reports a value every 15 minutes, and I 
don't know if that is an average of the previous 15 minutes or just a 
snapshot reading at the transition time. So for me 20 minutes is within the 
uncertainty.
Also, I don't know if it is expected, but the  pulses that travelled 
further show only the negative part, which comes after the positive. So 
there is extra lag in that.

I derived a speed by fitting data to Australian bureau charts, and they 
only show 30 minute samples, so my speed is hardly definitive.  I would 
expect it to vary a bit around the globe.  The average speed I derived from 
the first peak alone was 0.30 m/s, so that is either an indicator of the 
uncertainty in the fitting or that the average speed increased as it 
progressed.
On Friday, 21 January 2022 at 2:05:49 pm UTC+10 storm...@gmail.com wrote:

> Yes, the image files are being produced. Only thing I noticed was the 
> arrival time for the opposite pulse is off by approx. 20 minutes according 
> to the actual PWS data, this could be due to the wave speeding up or 
> slowing down as it made its way around the globe.  Right now I'm using your 
> default settings.
>
> On Thursday, January 20, 2022 at 10:40:36 PM UTC-5 Cameron D wrote:
>
>> the RankWarning is just a warning, you should still have image files 
>> produced.  I expect the polyfit it just ignores higher order terms and just 
>> returns a quadratic.
>>
>> That is because the polynomial is a poor representation of the 
>> background, and the spline fit works better, if you get the parameters 
>> correct.
>>
>> Initially you are better just to view the results without trend removal.  
>> If the peaks  do not stand out then  background removal is unlikely to help 
>> much.
>> Also, with my code,  make sure you start with oversampling set to 1. Only 
>> adjust it if you see a stair-step effect.
>>
>> On Friday, 21 January 2022 at 1:09:28 pm UTC+10 storm...@gmail.com wrote:
>>
>>> Modified the query and added the print statement as suggested by Cameron 
>>> D and here are the results:
>>>
>>> *Morrowwn Script:*
>>>
>>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>>> 10:47:08)
>>> select datetime, barometer from archive where datetime > 1642172400 and 
>>> datetime < 1642693629 order by dateTime;
>>> Traceback (most recent call last):
>>>   File "tonga_barometer.py", line 47, in 
>>> coeff = np.polyfit(xdata, ydata, 2)
>>>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
>>> 590, in polyfit
>>> y = NX.asarray(y) + 0.0
>>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>>>
>>>
>>> *Cameron D Script*:
>>>
>>> raspberrypi:~/Desktop/Tonga $ python3 tonga_baro.py
>>> distance to eruption 12255.7 km arrival at 1642258384 (2022-01-15 
>>> 09:53:04)
>>>   opposite pulse arrival at 1642306911 (2022-01-15 23:21:50)
>>>   second time around pulse arrival at 1642383509 (2022-01-16 
>>> 20:38:29)
>>> query returned 96 data points
>>> query returned 96 data points
>>> query returned 95 data points
>>> tonga_baro.py:108: RankWarning: Polyfit may be poorly conditioned
>>>   coeff = np.polyfit(xdata, ydata, 5 )
>>>
>>> Note: LAT/Long and speed of sound are identical in both scripts.
>>> On Thursday, January 20, 2022 at 9:27:13 PM UTC-5 Cameron D wrote:
>>>
 and add a debug printout for how many result lines there are after ...
 result = cursor.fetchall()
 add the line:
 
 *print( "query returned {} data points".format(len(result)))*

 On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:

> To eliminate NULL data points use a query like:
> select datetime, barometer from archive where datetime > 1642172400 
> and datetime < 1642693629* and barometer is not null *order by 
> dateTime;
>  You could add the part in bold into the query in the python script.
>
> Of course, if they are all null...
>
> On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com 
> wrote:
>
>> Download the latest script from 
>> https://github.com/morrowwm/weewx_tonga_browse. Beside installing 
>> the Python Modules Vince stated above, I needed to also install  
>> python3-scipy. I do have data between 1642172400 and 1642693629; 
>> except for a couple "null" in that time period.   So when I run the 
>> script, 
>> I get the following error.
>>
>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>> 10:47:08)
>> select datetime, barometer from archive where datetime > 1642172400 
>> and datetime < 1642693629 order by dateTime;
>> Traceback (most recent call last):
>>   File "tonga_barometer.py", line 47, in 
>> coeff =

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

Yes, the image files are being produced. Only thing I noticed was the 
arrival time for the opposite pulse is off by approx. 20 minutes according 
to the actual PWS data, this could be due to the wave speeding up or 
slowing down as it made its way around the globe.  Right now I'm using your 
default settings.

On Thursday, January 20, 2022 at 10:40:36 PM UTC-5 Cameron D wrote:

> the RankWarning is just a warning, you should still have image files 
> produced.  I expect the polyfit it just ignores higher order terms and just 
> returns a quadratic.
>
> That is because the polynomial is a poor representation of the background, 
> and the spline fit works better, if you get the parameters correct.
>
> Initially you are better just to view the results without trend removal.  
> If the peaks  do not stand out then  background removal is unlikely to help 
> much.
> Also, with my code,  make sure you start with oversampling set to 1. Only 
> adjust it if you see a stair-step effect.
>
> On Friday, 21 January 2022 at 1:09:28 pm UTC+10 storm...@gmail.com wrote:
>
>> Modified the query and added the print statement as suggested by Cameron 
>> D and here are the results:
>>
>> *Morrowwn Script:*
>>
>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>> 10:47:08)
>> select datetime, barometer from archive where datetime > 1642172400 and 
>> datetime < 1642693629 order by dateTime;
>> Traceback (most recent call last):
>>   File "tonga_barometer.py", line 47, in 
>> coeff = np.polyfit(xdata, ydata, 2)
>>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
>> 590, in polyfit
>> y = NX.asarray(y) + 0.0
>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>>
>>
>> *Cameron D Script*:
>>
>> raspberrypi:~/Desktop/Tonga $ python3 tonga_baro.py
>> distance to eruption 12255.7 km arrival at 1642258384 (2022-01-15 
>> 09:53:04)
>>   opposite pulse arrival at 1642306911 (2022-01-15 23:21:50)
>>   second time around pulse arrival at 1642383509 (2022-01-16 20:38:29)
>> query returned 96 data points
>> query returned 96 data points
>> query returned 95 data points
>> tonga_baro.py:108: RankWarning: Polyfit may be poorly conditioned
>>   coeff = np.polyfit(xdata, ydata, 5 )
>>
>> Note: LAT/Long and speed of sound are identical in both scripts.
>> On Thursday, January 20, 2022 at 9:27:13 PM UTC-5 Cameron D wrote:
>>
>>> and add a debug printout for how many result lines there are after ...
>>> result = cursor.fetchall()
>>> add the line:
>>> 
>>> *print( "query returned {} data points".format(len(result)))*
>>>
>>> On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:
>>>
 To eliminate NULL data points use a query like:
 select datetime, barometer from archive where datetime > 1642172400 and 
 datetime < 1642693629* and barometer is not null *order by dateTime;
  You could add the part in bold into the query in the python script.

 Of course, if they are all null...

 On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com 
 wrote:

> Download the latest script from 
> https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
> Python Modules Vince stated above, I needed to also install  
> python3-scipy. I do have data between 1642172400 and 1642693629; 
> except for a couple "null" in that time period.   So when I run the 
> script, 
> I get the following error.
>
> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
> 10:47:08)
> select datetime, barometer from archive where datetime > 1642172400 
> and datetime < 1642693629 order by dateTime;
> Traceback (most recent call last):
>   File "tonga_barometer.py", line 47, in 
> coeff = np.polyfit(xdata, ydata, 2)
>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
> 590, in polyfit
> y = NX.asarray(y) + 0.0
> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>
> There should be a way to check for "null" data within the time period.
> On Thursday, January 20, 2022 at 8:12:55 PM UTC-5 Cameron D wrote:
>
>> yes, definitely looks like there is no data.
>> I have attached another version of mine, in which the trend line is 
>> disabled by default, but I suspect that would just delay the inevitable 
>> and 
>> it would crash trying to do the plot.
>>
>> I also fixed up a few plotting errors in my code to do with the 
>> mysteries (to me) of layer ordering.
>> I also had a background bar showing either side of expected arrival - 
>> in this version I have now changed that to start at the expected arrival 
>> and stop 1 hour later.
>>
>> On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu 
>>

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

the RankWarning is just a warning, you should still have image files 
produced.  I expect the polyfit it just ignores higher order terms and just 
returns a quadratic.

That is because the polynomial is a poor representation of the background, 
and the spline fit works better, if you get the parameters correct.

Initially you are better just to view the results without trend removal.  
If the peaks  do not stand out then  background removal is unlikely to help 
much.
Also, with my code,  make sure you start with oversampling set to 1. Only 
adjust it if you see a stair-step effect.

On Friday, 21 January 2022 at 1:09:28 pm UTC+10 storm...@gmail.com wrote:

> Modified the query and added the print statement as suggested by Cameron D 
> and here are the results:
>
> *Morrowwn Script:*
>
> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 10:47:08)
> select datetime, barometer from archive where datetime > 1642172400 and 
> datetime < 1642693629 order by dateTime;
> Traceback (most recent call last):
>   File "tonga_barometer.py", line 47, in 
> coeff = np.polyfit(xdata, ydata, 2)
>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 590, 
> in polyfit
> y = NX.asarray(y) + 0.0
> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>
>
> *Cameron D Script*:
>
> raspberrypi:~/Desktop/Tonga $ python3 tonga_baro.py
> distance to eruption 12255.7 km arrival at 1642258384 (2022-01-15 09:53:04)
>   opposite pulse arrival at 1642306911 (2022-01-15 23:21:50)
>   second time around pulse arrival at 1642383509 (2022-01-16 20:38:29)
> query returned 96 data points
> query returned 96 data points
> query returned 95 data points
> tonga_baro.py:108: RankWarning: Polyfit may be poorly conditioned
>   coeff = np.polyfit(xdata, ydata, 5 )
>
> Note: LAT/Long and speed of sound are identical in both scripts.
> On Thursday, January 20, 2022 at 9:27:13 PM UTC-5 Cameron D wrote:
>
>> and add a debug printout for how many result lines there are after ...
>> result = cursor.fetchall()
>> add the line:
>> 
>> *print( "query returned {} data points".format(len(result)))*
>>
>> On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:
>>
>>> To eliminate NULL data points use a query like:
>>> select datetime, barometer from archive where datetime > 1642172400 and 
>>> datetime < 1642693629* and barometer is not null *order by dateTime;
>>>  You could add the part in bold into the query in the python script.
>>>
>>> Of course, if they are all null...
>>>
>>> On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com 
>>> wrote:
>>>
 Download the latest script from 
 https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
 Python Modules Vince stated above, I needed to also install  
 python3-scipy. I do have data between 1642172400 and 1642693629; 
 except for a couple "null" in that time period.   So when I run the 
 script, 
 I get the following error.

 raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
 distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
 10:47:08)
 select datetime, barometer from archive where datetime > 1642172400 and 
 datetime < 1642693629 order by dateTime;
 Traceback (most recent call last):
   File "tonga_barometer.py", line 47, in 
 coeff = np.polyfit(xdata, ydata, 2)
   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
 590, in polyfit
 y = NX.asarray(y) + 0.0
 TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'

 There should be a way to check for "null" data within the time period.
 On Thursday, January 20, 2022 at 8:12:55 PM UTC-5 Cameron D wrote:

> yes, definitely looks like there is no data.
> I have attached another version of mine, in which the trend line is 
> disabled by default, but I suspect that would just delay the inevitable 
> and 
> it would crash trying to do the plot.
>
> I also fixed up a few plotting errors in my code to do with the 
> mysteries (to me) of layer ordering.
> I also had a background bar showing either side of expected arrival - 
> in this version I have now changed that to start at the expected arrival 
> and stop 1 hour later.
>
> On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu wrote:
>
>> Hello,
>> Not being a programmer, I probably shouldn't have messed with this, 
>> but being curious...
>>
>> I tried the code posted on github as well as the one by Cameron D. In 
>> both cases I got the following error:
>> ```
>> root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
>> from Cameron D]
>>
>> distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
>> 09:52:39)
>>   opposite pulse arrival at

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

Modified the query and added the print statement as suggested by Cameron D 
and here are the results:

*Morrowwn Script:*

raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 10:47:08)
select datetime, barometer from archive where datetime > 1642172400 and 
datetime < 1642693629 order by dateTime;
Traceback (most recent call last):
  File "tonga_barometer.py", line 47, in 
coeff = np.polyfit(xdata, ydata, 2)
  File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 590, 
in polyfit
y = NX.asarray(y) + 0.0
TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'


*Cameron D Script*:

raspberrypi:~/Desktop/Tonga $ python3 tonga_baro.py
distance to eruption 12255.7 km arrival at 1642258384 (2022-01-15 09:53:04)
  opposite pulse arrival at 1642306911 (2022-01-15 23:21:50)
  second time around pulse arrival at 1642383509 (2022-01-16 20:38:29)
query returned 96 data points
query returned 96 data points
query returned 95 data points
tonga_baro.py:108: RankWarning: Polyfit may be poorly conditioned
  coeff = np.polyfit(xdata, ydata, 5 )

Note: LAT/Long and speed of sound are identical in both scripts.
On Thursday, January 20, 2022 at 9:27:13 PM UTC-5 Cameron D wrote:

> and add a debug printout for how many result lines there are after ...
> result = cursor.fetchall()
> add the line:
> 
> *print( "query returned {} data points".format(len(result)))*
>
> On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:
>
>> To eliminate NULL data points use a query like:
>> select datetime, barometer from archive where datetime > 1642172400 and 
>> datetime < 1642693629* and barometer is not null *order by dateTime;
>>  You could add the part in bold into the query in the python script.
>>
>> Of course, if they are all null...
>>
>> On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com 
>> wrote:
>>
>>> Download the latest script from 
>>> https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
>>> Python Modules Vince stated above, I needed to also install  
>>> python3-scipy. I do have data between 1642172400 and 1642693629; except 
>>> for a couple "null" in that time period.   So when I run the script, I get 
>>> the following error.
>>>
>>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>>> 10:47:08)
>>> select datetime, barometer from archive where datetime > 1642172400 and 
>>> datetime < 1642693629 order by dateTime;
>>> Traceback (most recent call last):
>>>   File "tonga_barometer.py", line 47, in 
>>> coeff = np.polyfit(xdata, ydata, 2)
>>>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
>>> 590, in polyfit
>>> y = NX.asarray(y) + 0.0
>>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>>>
>>> There should be a way to check for "null" data within the time period.
>>> On Thursday, January 20, 2022 at 8:12:55 PM UTC-5 Cameron D wrote:
>>>
 yes, definitely looks like there is no data.
 I have attached another version of mine, in which the trend line is 
 disabled by default, but I suspect that would just delay the inevitable 
 and 
 it would crash trying to do the plot.

 I also fixed up a few plotting errors in my code to do with the 
 mysteries (to me) of layer ordering.
 I also had a background bar showing either side of expected arrival - 
 in this version I have now changed that to start at the expected arrival 
 and stop 1 hour later.

 On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu wrote:

> Hello,
> Not being a programmer, I probably shouldn't have messed with this, 
> but being curious...
>
> I tried the code posted on github as well as the one by Cameron D. In 
> both cases I got the following error:
> ```
> root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
> from Cameron D]
>
> distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
> 09:52:39)
>   opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
>   second time around pulse arrival at 1642385471 (2022-01-16 
> 21:11:10)
> Traceback (most recent call last):
>   File "./tonga.py", line 178, in 
> plot_burst( cursor, arrival_time, hour_span, "primary" )
>   File "./tonga.py", line 54, in plot_burst
> coeff = np.polyfit(xdata, ydata, background_order )
>   File "<__array_function__ internals>", line 180, in polyfit
>   File 
> "/usr/local/lib/python3.8/dist-packages/numpy/lib/polynomial.py", line 
> 638, 
> in polyfit
> raise TypeError("expected non-empty vector for x")
> TypeError: expected non-empty vector for x
> ```
> I added my lat/lon information but may have missed something else I 
> need to change. Python

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

and add a debug printout for how many result lines there are after ...
result = cursor.fetchall()
add the line:

*print( "query returned {} data points".format(len(result)))*

On Friday, 21 January 2022 at 12:21:59 pm UTC+10 Cameron D wrote:

> To eliminate NULL data points use a query like:
> select datetime, barometer from archive where datetime > 1642172400 and 
> datetime < 1642693629* and barometer is not null *order by dateTime;
>  You could add the part in bold into the query in the python script.
>
> Of course, if they are all null...
>
> On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com wrote:
>
>> Download the latest script from 
>> https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
>> Python Modules Vince stated above, I needed to also install  
>> python3-scipy. I do have data between 1642172400 and 1642693629; except 
>> for a couple "null" in that time period.   So when I run the script, I get 
>> the following error.
>>
>> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
>> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 
>> 10:47:08)
>> select datetime, barometer from archive where datetime > 1642172400 and 
>> datetime < 1642693629 order by dateTime;
>> Traceback (most recent call last):
>>   File "tonga_barometer.py", line 47, in 
>> coeff = np.polyfit(xdata, ydata, 2)
>>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 
>> 590, in polyfit
>> y = NX.asarray(y) + 0.0
>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>>
>> There should be a way to check for "null" data within the time period.
>> On Thursday, January 20, 2022 at 8:12:55 PM UTC-5 Cameron D wrote:
>>
>>> yes, definitely looks like there is no data.
>>> I have attached another version of mine, in which the trend line is 
>>> disabled by default, but I suspect that would just delay the inevitable and 
>>> it would crash trying to do the plot.
>>>
>>> I also fixed up a few plotting errors in my code to do with the 
>>> mysteries (to me) of layer ordering.
>>> I also had a background bar showing either side of expected arrival - in 
>>> this version I have now changed that to start at the expected arrival and 
>>> stop 1 hour later.
>>>
>>> On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu wrote:
>>>
 Hello,
 Not being a programmer, I probably shouldn't have messed with this, but 
 being curious...

 I tried the code posted on github as well as the one by Cameron D. In 
 both cases I got the following error:
 ```
 root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
 from Cameron D]

 distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
 09:52:39)
   opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
   second time around pulse arrival at 1642385471 (2022-01-16 
 21:11:10)
 Traceback (most recent call last):
   File "./tonga.py", line 178, in 
 plot_burst( cursor, arrival_time, hour_span, "primary" )
   File "./tonga.py", line 54, in plot_burst
 coeff = np.polyfit(xdata, ydata, background_order )
   File "<__array_function__ internals>", line 180, in polyfit
   File 
 "/usr/local/lib/python3.8/dist-packages/numpy/lib/polynomial.py", line 
 638, 
 in polyfit
 raise TypeError("expected non-empty vector for x")
 TypeError: expected non-empty vector for x
 ```
 I added my lat/lon information but may have missed something else I 
 need to change. Python modules were installed as directed. Copy of 
 weewx.sdb is in the same directory as the program.
 Thanks.
 Bob
 On Wednesday, January 19, 2022 at 10:32:49 AM UTC-5 morr...@gmail.com 
 wrote:

> On Wednesday, January 19, 2022 at 12:42:04 a.m. UTC-4 Cameron D wrote:
>
>>
>>- as you get closer to the equator, tidal changes dominate the 
>>baseline in that timescale - I tried higher order polynomials, but 
>> they are 
>>next to useless.
>>
>> I also had little luck with higher order polynomials to remove the 
> general trend.
>
> I've put the script here: 
> https://github.com/morrowwm/weewx_tonga_browse
>


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/29f6da88-32e8-488c-ba98-348ca63c893cn%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

To eliminate NULL data points use a query like:
select datetime, barometer from archive where datetime > 1642172400 and 
datetime < 1642693629* and barometer is not null *order by dateTime;
 You could add the part in bold into the query in the python script.

Of course, if they are all null...

On Friday, 21 January 2022 at 12:14:44 pm UTC+10 storm...@gmail.com wrote:

> Download the latest script from 
> https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
> Python Modules Vince stated above, I needed to also install  
> python3-scipy. I do have data between 1642172400 and 1642693629; except 
> for a couple "null" in that time period.   So when I run the script, I get 
> the following error.
>
> raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
> distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 10:47:08)
> select datetime, barometer from archive where datetime > 1642172400 and 
> datetime < 1642693629 order by dateTime;
> Traceback (most recent call last):
>   File "tonga_barometer.py", line 47, in 
> coeff = np.polyfit(xdata, ydata, 2)
>   File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 590, 
> in polyfit
> y = NX.asarray(y) + 0.0
> TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'
>
> There should be a way to check for "null" data within the time period.
> On Thursday, January 20, 2022 at 8:12:55 PM UTC-5 Cameron D wrote:
>
>> yes, definitely looks like there is no data.
>> I have attached another version of mine, in which the trend line is 
>> disabled by default, but I suspect that would just delay the inevitable and 
>> it would crash trying to do the plot.
>>
>> I also fixed up a few plotting errors in my code to do with the mysteries 
>> (to me) of layer ordering.
>> I also had a background bar showing either side of expected arrival - in 
>> this version I have now changed that to start at the expected arrival and 
>> stop 1 hour later.
>>
>> On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu wrote:
>>
>>> Hello,
>>> Not being a programmer, I probably shouldn't have messed with this, but 
>>> being curious...
>>>
>>> I tried the code posted on github as well as the one by Cameron D. In 
>>> both cases I got the following error:
>>> ```
>>> root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
>>> from Cameron D]
>>>
>>> distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
>>> 09:52:39)
>>>   opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
>>>   second time around pulse arrival at 1642385471 (2022-01-16 
>>> 21:11:10)
>>> Traceback (most recent call last):
>>>   File "./tonga.py", line 178, in 
>>> plot_burst( cursor, arrival_time, hour_span, "primary" )
>>>   File "./tonga.py", line 54, in plot_burst
>>> coeff = np.polyfit(xdata, ydata, background_order )
>>>   File "<__array_function__ internals>", line 180, in polyfit
>>>   File "/usr/local/lib/python3.8/dist-packages/numpy/lib/polynomial.py", 
>>> line 638, in polyfit
>>> raise TypeError("expected non-empty vector for x")
>>> TypeError: expected non-empty vector for x
>>> ```
>>> I added my lat/lon information but may have missed something else I need 
>>> to change. Python modules were installed as directed. Copy of weewx.sdb is 
>>> in the same directory as the program.
>>> Thanks.
>>> Bob
>>> On Wednesday, January 19, 2022 at 10:32:49 AM UTC-5 morr...@gmail.com 
>>> wrote:
>>>
 On Wednesday, January 19, 2022 at 12:42:04 a.m. UTC-4 Cameron D wrote:

>
>- as you get closer to the equator, tidal changes dominate the 
>baseline in that timescale - I tried higher order polynomials, but 
> they are 
>next to useless.
>
> I also had little luck with higher order polynomials to remove the 
 general trend.

 I've put the script here: 
 https://github.com/morrowwm/weewx_tonga_browse

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b6f1a858-e46f-4cf0-9b43-e09b1c7a3e98n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data

Download the latest script from 
https://github.com/morrowwm/weewx_tonga_browse. Beside installing the 
Python Modules Vince stated above, I needed to also install  python3-scipy. I 
do have data between 1642172400 and 1642693629; except for a couple "null" 
in that time period.   So when I run the script, I get the following error.

raspberrypi:~/Desktop/Tonga $ python3 tonga_barometer.py
distance to eruption 13293.9 km arrival at 1642261629 (2022-01-15 10:47:08)
select datetime, barometer from archive where datetime > 1642172400 and 
datetime < 1642693629 order by dateTime;
Traceback (most recent call last):
  File "tonga_barometer.py", line 47, in 
coeff = np.polyfit(xdata, ydata, 2)
  File "/usr/lib/python3/dist-packages/numpy/lib/polynomial.py", line 590, 
in polyfit
y = NX.asarray(y) + 0.0
TypeError: unsupported operand type(s) for +: 'NoneType' and 'float'

There should be a way to check for "null" data within the time period.
On Thursday, January 20, 2022 at 8:12:55 PM UTC-5 Cameron D wrote:

> yes, definitely looks like there is no data.
> I have attached another version of mine, in which the trend line is 
> disabled by default, but I suspect that would just delay the inevitable and 
> it would crash trying to do the plot.
>
> I also fixed up a few plotting errors in my code to do with the mysteries 
> (to me) of layer ordering.
> I also had a background bar showing either side of expected arrival - in 
> this version I have now changed that to start at the expected arrival and 
> stop 1 hour later.
>
> On Friday, 21 January 2022 at 3:29:36 am UTC+10 bgra...@umw.edu wrote:
>
>> Hello,
>> Not being a programmer, I probably shouldn't have messed with this, but 
>> being curious...
>>
>> I tried the code posted on github as well as the one by Cameron D. In 
>> both cases I got the following error:
>> ```
>> root@n4mrv:/home/bg/weewx_tonga_browse-main# python3 ./tonga.py   [file 
>> from Cameron D]
>>
>> distance to eruption 12056.6 km arrival at 1642258360 (2022-01-15 
>> 09:52:39)
>>   opposite pulse arrival at 1642308921 (2022-01-15 23:55:21)
>>   second time around pulse arrival at 1642385471 (2022-01-16 21:11:10)
>> Traceback (most recent call last):
>>   File "./tonga.py", line 178, in 
>> plot_burst( cursor, arrival_time, hour_span, "primary" )
>>   File "./tonga.py", line 54, in plot_burst
>> coeff = np.polyfit(xdata, ydata, background_order )
>>   File "<__array_function__ internals>", line 180, in polyfit
>>   File "/usr/local/lib/python3.8/dist-packages/numpy/lib/polynomial.py", 
>> line 638, in polyfit
>> raise TypeError("expected non-empty vector for x")
>> TypeError: expected non-empty vector for x
>> ```
>> I added my lat/lon information but may have missed something else I need 
>> to change. Python modules were installed as directed. Copy of weewx.sdb is 
>> in the same directory as the program.
>> Thanks.
>> Bob
>> On Wednesday, January 19, 2022 at 10:32:49 AM UTC-5 morr...@gmail.com 
>> wrote:
>>
>>> On Wednesday, January 19, 2022 at 12:42:04 a.m. UTC-4 Cameron D wrote:
>>>

- as you get closer to the equator, tidal changes dominate the 
baseline in that timescale - I tried higher order polynomials, but they 
 are 
next to useless.

 I also had little luck with higher order polynomials to remove the 
>>> general trend.
>>>
>>> I've put the script here: https://github.com/morrowwm/weewx_tonga_browse
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/21baed8f-5d82-4657-9227-c354eb95169en%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station? - extract your data