I used the GeigerLog 1.5 Pre 48 version for this.
Thanks for this new thread!
I finally picked up a K40 source at the grocery store No Salt Brand.
I performed a log using 62 grams in a thin zip bag placing the 600+ face down on the bag see images for details.
The Poisson was better than most of my previous ones.
I set the log time to 2 seconds I think this may have helped with my slower PC.
Please find files attached.
Bob
While the Poisson is better, I am not convinced. Look at the pic. I drew a little "worm" under each of the Poissons for CPM and CPS. Both could support the notion that there is too much consistency in the residuals. Those should be random wiggles around zero. The CPS is mostly less sensitive to this, and even that shows it. Not a firm conclusion, but still suspicious.
Another problem: next pic shows the variable Temp, which in this GeigerLog configuration holds the drift of the counters clock. All clocks of all GMC counters are really bad. They typically are drifting by 1 sec per hour. But look at you data: your GMC-600+ clock is drifting by 8 sec per hour! E I G H T seconds.
This is by far the record. I'd say this device is broken!
The clock is reset to correct time by GeigerLog every 30 min (can be configured in config file). But once you disconnect from GeigerLog and are offline, the bad clock is fully active, and your history is significantly impacted!
OK this setup used GeigerLog v1.5.0pre49 on my slow PC unfortunately. I am using my faster one for another project at the moment.
Sample is a approx: 22mmx32mm x5mm thick broken piece of uranium oxide glazed Fiestaware.
Raw count rate Approx 16k CPM with no shielding except for the plastic Zip bag the sample was in, film thickness was measured at .0508mm converted from .002" on a micrometer.
600+ was placed sensor side down with the sample in the center of the GM pancake window.
See photos for reference. Sample rate was set to 2 seconds NO FET and Tube deadtime disabled.
I let it run overnight and into the morning checking the Poisson several times and noting as the sample size (number of records) increased the Poisson improved even with the known and unknown design flaws of the 600+ and my slow PC.
Bob
I forgot to mention for the above when I installed this version I forgot to perform the auto install of the packages. After the data run I performed the auto install and it did update some of the packages.
For this lack of foresight I apologize.
Bob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually, I have not, because I did not get a notification. Strange. But perhaps you were editing an old post? This does NOT trigger a notification.
Yes, Poisson looks ok. One suggestion: for the time course show only a single trace, like only CPM (preferred) or only CPS. Showing them together squeezes them and one cannot see details (though here aren't any, I looked at the data).
But what on earth happened to the clock? Is that the "repaired" device? The Temp trace shows a start at 26 sec and ends at 4154 sec after 14.5 h runtime. This is not the old, bad 8sec/h drift, but it now is 285sec/hour! Almost 2hours per day! WTF???
You need to do a real closeup, and then see that the time jumps by 1 sec every 7 sec, see pic!
No Sir this is my device prior to me sending it in and you informing me about the clock issue.
I’m scheduled to receive my repaired device today hopefully.
Bob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used the GeigerLog 1.5 Pre 48 version for this.
Thanks for this new thread!
I finally picked up a K40 source at the grocery store No Salt Brand.
I performed a log using 62 grams in a thin zip bag placing the 600+ face down on the bag see images for details.
The Poisson was better than most of my previous ones.
I set the log time to 2 seconds I think this may have helped with my slower PC.
Please find files attached.
Bob
Well done!
While the Poisson is better, I am not convinced. Look at the pic. I drew a little "worm" under each of the Poissons for CPM and CPS. Both could support the notion that there is too much consistency in the residuals. Those should be random wiggles around zero. The CPS is mostly less sensitive to this, and even that shows it. Not a firm conclusion, but still suspicious.
Another problem: next pic shows the variable Temp, which in this GeigerLog configuration holds the drift of the counters clock. All clocks of all GMC counters are really bad. They typically are drifting by 1 sec per hour. But look at you data: your GMC-600+ clock is drifting by 8 sec per hour! E I G H T seconds.
This is by far the record. I'd say this device is broken!
The clock is reset to correct time by GeigerLog every 30 min (can be configured in config file). But once you disconnect from GeigerLog and are offline, the bad clock is fully active, and your history is significantly impacted!
Last edit: ullix 2023-07-20
OK this setup used GeigerLog v1.5.0pre49 on my slow PC unfortunately. I am using my faster one for another project at the moment.
Sample is a approx: 22mmx32mm x5mm thick broken piece of uranium oxide glazed Fiestaware.
Raw count rate Approx 16k CPM with no shielding except for the plastic Zip bag the sample was in, film thickness was measured at .0508mm converted from .002" on a micrometer.
600+ was placed sensor side down with the sample in the center of the GM pancake window.
See photos for reference. Sample rate was set to 2 seconds NO FET and Tube deadtime disabled.
I let it run overnight and into the morning checking the Poisson several times and noting as the sample size (number of records) increased the Poisson improved even with the known and unknown design flaws of the 600+ and my slow PC.
Bob
I forgot to mention for the above when I installed this version I forgot to perform the auto install of the packages. After the data run I performed the auto install and it did update some of the packages.
For this lack of foresight I apologize.
Bob
Ullix have you see my above post? My best Poisson yet with 1.5 Pre 49 version.
Bob
Actually, I have not, because I did not get a notification. Strange. But perhaps you were editing an old post? This does NOT trigger a notification.
Yes, Poisson looks ok. One suggestion: for the time course show only a single trace, like only CPM (preferred) or only CPS. Showing them together squeezes them and one cannot see details (though here aren't any, I looked at the data).
But what on earth happened to the clock? Is that the "repaired" device? The Temp trace shows a start at 26 sec and ends at 4154 sec after 14.5 h runtime. This is not the old, bad 8sec/h drift, but it now is 285sec/hour! Almost 2hours per day! WTF???
You need to do a real closeup, and then see that the time jumps by 1 sec every 7 sec, see pic!
Last edit: ullix 2023-07-29
No Sir this is my device prior to me sending it in and you informing me about the clock issue.
I’m scheduled to receive my repaired device today hopefully.
Bob