I've deployed a spectrum analyzer at the West Yellowstone site to perform detection and filter-based spectral analysis for radioisotopes from Radon and Thoron decay (natural uranium progenies). This will allow us to more accurately determine any influence on our survey data from the Ludlum and Thermo-Scientific instruments currently used there.

Thank you to station operator "Emerald Eye" for piquing my interest in this additional study.

For instrument information and method see the added station information for West Yellowstone in the first post of this thread.

I will be updating the top post with daily measurements from this instrument.

FWIW, in my spare time I'm farting around with creating a little Geiger-counter program that can listen to your favorite counter by a direct audio connection and then perform the usual functions of a Geiger counter – display rates at high-medium-low response damping, averages over several different time periods, display in CPM and in µSv/h via a user-supplied conversion factor.

I'm just in the early design phase, deciding how to arrange controls and displays; working out algorithms; and arguing with Netbeans about everything.

This in Java, so is cross-platform; Windows, Mac, Linux.

I post this asking for suggestions for high-priority features beyond those mentioned. * Log file will be rev 2. Need to decide what to log first. * Is actual audio recording desirable? Another version 2 feature. As far as I can guess, maybe for later analysis of timing between pulses and so possibly some preliminary identification of likely radio-isotopes. But that can be accomplished other ways.

FWIW, in my spare time I'm farting around with creating a little Geiger-counter program that can listen to your favorite counter by a direct audio connection and then perform the usual functions of a Geiger counter – display rates at high-medium-low response damping, averages over several different time periods, display in CPM and in µSv/h via a user-supplied conversion factor.

I'm just in the early design phase, deciding how to arrange controls and displays; working out algorithms; and arguing with Netbeans about everything.

This in Java, so is cross-platform; Windows, Mac, Linux.

I post this asking for suggestions for high-priority features beyond those mentioned. * Log file will be rev 2. Need to decide what to log first. * Is actual audio recording desirable? Another version 2 feature. As far as I can guess, maybe for later analysis of timing between pulses and so possibly some preliminary identification of likely radio-isotopes. But that can be accomplished other ways.

Quoting: Nuke Skywalker

Java! B-E-A-utiful. I'll give this some thought and feedback.

I think audio recording probably won't be necessary since it's only used to drive the audio pipeline, but an option to pass-thru the audio would be good for those directly jacked in compared to those using a mic for indirect audio pickup.

Also, perhaps eventually a way to create, save and load profiles for different detection instruments (or their parameters rather) would be handy.

I am also working on some software to record and count clicks from my meter. Right now I've got a cron job on my Linux server logging raw audio every 15 minutes, but I have to count the clicks manually or estimate based on the analog meter. I am also thinking about a direct electrical coupling to the audio input, because the acoustic coupling picks up some background noise.

Basically, I am going to create a C program that will open WAV files, perform a high-pass filter, and then level/duration detect to identify each individual click. Since I've already got a couple weeks of audio, I'll go back and process the older data for the record. Once I get it all working, I'll post it to the web.

Currently, readings here in the north metro Atlanta area are holding steady at about 17 clicks per minute.

FWIW, in my spare time I'm farting around with creating a little Geiger-counter program that can listen to your favorite counter by a direct audio connection and then perform the usual functions of a Geiger counter – display rates at high-medium-low response damping, averages over several different time periods, display in CPM and in µSv/h via a user-supplied conversion factor.

I'm just in the early design phase, deciding how to arrange controls and displays; working out algorithms; and arguing with Netbeans about everything.

This in Java, so is cross-platform; Windows, Mac, Linux.

I post this asking for suggestions for high-priority features beyond those mentioned. * Log file will be rev 2. Need to decide what to log first. * Is actual audio recording desirable? Another version 2 feature. As far as I can guess, maybe for later analysis of timing between pulses and so possibly some preliminary identification of likely radio-isotopes. But that can be accomplished other ways.

too bad people arent putting DMS coordinates to these readings. It could be mapped, if they were. I got the software to project points and software to display them with my extensive archive of thematic maps...

I post this asking for suggestions for high-priority features beyond those mentioned.

Quoting: Nuke Skywalker

Dump the data set(s) to a flat file, preferably XML which will allow me to port those values ala carte into an overlay for the webcam(s). If you want to keep it light, maybe just the Standard Mean of CPM.

I am also working on some software to record and count clicks from my meter. Right now I've got a cron job on my Linux server logging raw audio every 15 minutes, but I have to count the clicks manually or estimate based on the analog meter. I am also thinking about a direct electrical coupling to the audio input, because the acoustic coupling picks up some background noise.

Basically, I am going to create a C program that will open WAV files, perform a high-pass filter, and then level/duration detect to identify each individual click. Since I've already got a couple weeks of audio, I'll go back and process the older data for the record. Once I get it all working, I'll post it to the web.

Currently, readings here in the north metro Atlanta area are holding steady at about 17 clicks per minute.

Quoting: CDV 1124145

Man I don't know how I missed your post, sorry! Anyways, cool! Sounds like you're on your way. I'm tempted to blow the dust off eclipse and pull down beta's from SVN if you guys need help testing.

FWIW, in my spare time I'm farting around with creating a little Geiger-counter program that can listen to your favorite counter by a direct audio connection and then perform the usual functions of a Geiger counter – display rates at high-medium-low response damping, averages over several different time periods, display in CPM and in µSv/h via a user-supplied conversion factor.

I'm just in the early design phase, deciding how to arrange controls and displays; working out algorithms; and arguing with Netbeans about everything.

This in Java, so is cross-platform; Windows, Mac, Linux.

I post this asking for suggestions for high-priority features beyond those mentioned. * Log file will be rev 2. Need to decide what to log first. * Is actual audio recording desirable? Another version 2 feature. As far as I can guess, maybe for later analysis of timing between pulses and so possibly some preliminary identification of likely radio-isotopes. But that can be accomplished other ways.