Clay,
I've extracted the group_ion_radiation entries from the uRadMon driver
and copied them to /user/extensions.py (which itself is from
weewx-4.6.0)
If you save your copy and replace it with the attachment, then place
the following stanza wherever it's needed (under whatever skin you're
using i
Hi Clay,
The original UradMon A3 (https://www.uradmonitor.com/) had, along with
various other environment sensors, a gieger counter that registered in
cpm.
I've recently updated the driver
(https://github.com/glennmckechnie/weewx-uradmon) for it to return
microSieverts/hour rather than its defaul
"'Cameron D' via weewx-development"
writes:
> " ionizing_radiation " would be an obvious and unambiguous choice.
I guess there are two observations, one is counts/s and the other some
estimate of uSv/s. But given the weewx approach, I think it makes
sense to let the input device attempt to es
" ionizing_radiation " would be an obvious and unambiguous choice.
I'd be reluctant to rely on the uSv/hour value, unless you know the
source. The Geiger-Muller tube electronics looks like it is just reporting
ionisation events per second, with no measure of the energy. Any
"calibration factor
Clay Jackson writes:
> Here's one a bit "off the wall" - I happen to live near Hanford, WA (2nd
> largest radiation cleanup site in the world, behind Chernobyl) and I'm also
> interested in "Space Weather". So, when mightyohm (www.mightyohm.com) put
> their Geiger counter on sale last year,
Here's one a bit "off the wall" - I happen to live near Hanford, WA (2nd
largest radiation cleanup site in the world, behind Chernobyl) and I'm also
interested in "Space Weather". So, when mightyohm (www.mightyohm.com) put
their Geiger counter on sale last year, I snapped one up. I have it
co
