Log File Stats

[Richard Wood]

My latest record #32643 statistics shows a 72CPM Max count that is not in the record.  The max I find in the average record is 53.  Advice appreciated

Log File Stats
72	CPM, max
32	CPM, mean
12	CPM, min
0.22	µSv/h, max
0.10	µSv/h, mean
0.04	µSv/h, min
4.20	µSv, total dose
33.3	km, total
5	kph, max
0	kph, min
101	m, max alt.
27	m, min alt.
4.5	hours
3273	lines

[Richard Wood]

It look like the false record was created on the server side record, before the meter had time to capture a full minutes worth of data. ?

[Mat Schaffer]

Nick, I'm seeing this in the JS viewer but not in the DB (at least in the bgeigie_logs table).

I know the api deployment is a bit behind still, so maybe we're just missing a bugfix?

irb(main):006:0> BgeigieImport.find(32643).bgeigie_logs.map(&:cpm).sort.last

=> 53

-Mat

matschaffer.com

[Richard Wood]

Is there any update on this?  I did not see it in the dev bug / issues list but have not checked back in a while or I missed it.

Would this impact data sharing users, do we ever get access to what those other groups do with this data?

[Mat Schaffer]

I pulled this up on the tilemap as well and it shows the same 72CPM point

http://safecast.org/tilemap/?y=45.548866&x=-122.558593&z=21&l=0&m=0&logids=32643

What I can't make sense of is why this line is showing up as 72CPM

$BNRDD,3023,2017-11-18T21:03:55Z,41,6,60,A,4532.9330,N,12233.5156,W,62.70,A,4,303*65

Nick, can you cross check this? According to https://github.com/Safecast/bGeigieNanoKit/wiki/Operations-Manual#data-log it seems like it should be showing 41CPM but you know the parse/render a lot better than I do.

-Mat

matschaffer.com

[Kalin KOZHUHAROV (Safecast)]

On Mon, Jan 8, 2018 at 2:46 PM, Mat Schaffer <m...@schaffer.me> wrote:
> I pulled this up on the tilemap as well and it shows the same 72CPM point
>
> http://safecast.org/tilemap/?y=45.548866&x=-122.558593&z=21&l=0&m=0&logids=32643
>
> What I can't make sense of is why this line is showing up as 72CPM
>
> $BNRDD,3023,2017-11-18T21:03:55Z,41,6,60,A,4532.9330,N,12233.5156,W,62.70,A,4,303*65
>

See the "...Z,41,6,60..."?
That 6 is "counts-in-5s-interval", so 6*5/60=72CPM ("instant CPM") as
opposed to 41 average over-the-last-1min-CPM.

I guess there was a threshold where display switches from one to the
other, but I don't remember details.

Kalin.

[Mat Schaffer]

Ah! Thanks, Kalin. Totally forgot about that feature. 

Now that we’re using Nick’s viewer I guess it’s time to think about adjusting the api reported cpm as well. 

Sort of wondering if the threshold is a little low given this thread though. 

--

-Mat

matschaffer.com

[Richard Wood]

Thanks all, after looking more into the background of the system and data and with your great feedback I understand more to where the data in the display panel comes from.  I was more focused on one minute averages from these meters, and stationary readings but that moving data thing adds a whole new layer of thought. 
Great work, much appreciated.

[Mat Schaffer]

👍

--

-Mat

matschaffer.com