GeigerLog.bat -dvw devel trace

GeigerLog.bat -dvw devel

quote:

---

Originally posted by ullix

It is not really helping.

The stats window is coded for a size of H1100xH750. Displays today have a size of 1920x1080, so there should be ample space. But height-wise it should fit even on the minimal size supported by GeigerLog.

What is your screen size in pixels? Are you using any any OS-specific overall screen enlargement?

You see the scrollbar on the right side of the stats window. So you can shift the content up and down and see everything there is.

To enlarge or shrank the size of the text-fonts you can also do: press and hold the CTRL-key, and turn the mouse wheel as desired.

I'll make the window smaller in the next release, but it is on the brink of becoming inconvenient!

Next releases are pre-releases, and you find them here:
https://sourceforge.net/p/geigerlog/discussion/devel2/


Always take the last one available, but be aware that there may be bugs.

---

quote:

---

Originally posted by ullix

Yeah, this should not happen.

I don't see it on my test systems. Can you please point out again where it occurs, and I will work on a fix.

---

quote:

---

his setup guide is for those who'd like to use their mobile smartphones to access Ullix’s GeigerLog Web Monitors. Specifically, these instructions demonstrate how to remotely access data from your GQ Electronics (GQE) GMC Geiger-counter via the GeigerLog software installed on a cloud based webserver, while connected to a public cellular or Wi-Fi network or other non-private wide area network (WAN).

---

quote:

---

Originally posted by ullix

Wow, digging deep into the much loved Poisson statistics!

I figured my answer would need some attachments, which I couldn't post here, so I started an answer on the GeigerLog site under the heading:

GeigerLog as Doomsday Predictor
https://sourceforge.net/p/geigerlog/discussion/general/thread/2eee6dd990/

While this heading may not be fully serious, the content should be!

I think this quote reflects the most important restriction to do any Poisson-statistice-educated setting of alarm levels:

quote:

---

... with a maximum of one false alarm per month on average.

---

which implies that you have to bite the bullet in defining how much nuisance you want to bear by understanding the nature of the statistics of radioactive decay.

Download data and spreadsheet to experiment with yourself.

P.S. one request: please avoid the "Reply with Quote" button in this forum whenever possible. This really blows up the thread for mostly no advantage. To quote single pieces from comments, which you may need for good reference, you can always use the "Insert Quote" button in the editor.

---

quote:

---

In your experience, what would be the easiest way to get and use Geiger map data in the exact csv form that Geigerlog requires?

---

#  Index,        DateTime,      CPM,      CPS
   0, 2019-01-11 19:32:14,      181,        6
   1, 2019-01-11 19:32:18,      197,        3

"2023-05-16 20:48:40","14","12.97","0.09","45.314234","-75.9219635"
"2023-05-16 20:38:37","16","12.97","0.10","45.314234","-75.9219635"
"2023-05-16 20:28:35","11","12.97","0.07","45.314234","-75.9219635"

#  Index,        DateTime,      CPM,      CPS
   0, 2019-01-11 19:32:14,      181,        6
   1, 2019-01-11 19:32:18,      197,        3

quote:

---

Originally posted by ullix

I also believed to see a periodicity in the time course, which made me add the FFT option. Nope, nothing, just plain statistics!

Well, this isn't true: take a light sensitive tube and measure for a couple of days - and then you have it!

---

quote:

---

... with a maximum of one false alarm per month on average.

---

quote:

---

Originally posted by Damien68

the cumulative curve is very interesting.
consider the following problem, to make an alarm that is triggered in the event of an abnormal increase in the CPM rate:

- if for example I have an average CMP of 13.3CPM,
- if I wish to have the highest possible sensitivity but with a maximum of one false alarm per 2 month on average.

I am not specialized in statistics but I think that my reasoning must be good, the goal is to define a CPM max threshold to trigger an alarm:

-> an average of one false alarm per 2 month would be equivalent to saying that the cumulative probability during a month of having all the CPMs below the defined threshold would be 0.5, this is not strictly exact because we can have also several false alarms in the same month, but because the probalility are very low we can consider this as an good approximation.

-> we consider that we observe a value of CPM every minute and during a month we will therefore have 30.5*24*60 samples = 43920 CPM samples.

-> because the CPM values are all uncorrelated, the probability that all CPM values are below the threshold is equal to the discrete probability of obtaining this condition powered by the number of samples.

=> the overall probability of not triggering an alarm during a month is therefore according to the assumptions: 0.5

=> the discrete probability for each sample of CPM that it is lower than the Max threshold must therefore be 0.5^(1/43920) = 0.9999842

=> by using the black Geigerlog curve (or more by using its formula) we can then define the CPM Max threshold corresponding to the cumulate of (0.9999842 * Npopulate).

Ullix, is that correct?

EDIT: using GeigerLog's formula of the cumulative curve for previous calculations, there is certainly a simplification by Npopulate to be made.
Suggest a Max threshold of CPM according to criterias could be a new feature in GeigerLog.

---

quote:

---

Originally posted by ullix

Are you looking for a Cumulative Distribution function? Here is one on user data, background recording In Japan with a GMC600 Geiger counter.

In black is the Cumulative Poisson function.

---

quote:

---

Originally posted by ullix

@Steve: I have a hunch of what you are trying to achieve, and I think it is already present in the 1.5 series of GeigerLog. The currently latest pre-release (#30) is available at: https://sourceforge.net/p/geigerlog/discussion/general/thread/beafedc7b1/?page=4#c2ed

The formula interpreter has made big steps forward. Activate the "Formula Device" with variable "Pressure", and in the configuration file, section "[ValueFormula]" enter "Press = EXPONENTIAL(100)" (the pre-release 30 has all this already).

Then start GeigerLog with:

python geigerlog nopoisson

This will create an Exponential Function for the time-differences in ms between two successive count events at CPS=100. This is the base for a true Poisson function for an average CPS=100.

This is the result:



In the bottom part I (mis-)used the "Histogram with Poisson Plot" graph to show this distribution. It is NOT Poissonian, of course, it is exponential! To not become confused with the red lines of an attempted Poisson plot, the "nopoisson" command takes care of removing it.

For CPS=100 the average time between 2 counts is 10.0 ms. And you see the average of this exponential distribution is close with 9.92 ms for 2139 counts.

You can do this for other count rates as well, and add probabilities. But once you have gotten that far, you will realize that you don't need GeigerLog, nor Poisson, but only a few exp() functions in an Excel sheet ;-).

---

python geigerlog nopoisson

quote:

---

Originally posted by ullix

GeigerLog is Open Source, so you are welcome to scavenge it for parts :-)

You'll find the Poisson stuff in file

gstat_poisson.py

.

---

gstat_poisson.py

quote:

---

Originally posted by ullix

Welcome back, and thanks for the good words.

Notice that an evaluation of GeigerLog 1.5.0 is ongoing. You find the lastest pre-releases in this topic:
https://sourceforge.net/p/geigerlog/discussion/general/thread/beafedc7b1/
Begin searching the posts from the end for the latest pre-release. It is already very stable. As of this moment latest version is pre25, but this may change soon.

---

quote:

---

Originally posted by ullix

You are invited and encouraged to take part in the evaluation of upcoming GeigerLog 1.5.

Whatever you have as counter, I2C device, Raspberry Pi computer can help. The latest GMC-300X counters are one center of attention.

It happens here:
https://sourceforge.net/p/geigerlog/discussion/general/thread/beafedc7b1/

The latest pre-release of GeigerLog is available for download.

---

python -m pip install -U soundfile

quote:

---

Originally posted by ullix

@vyzbick: Please, please, please: shrink your pics to a maximum width of near 800 pixel! Everything becomes awfully hard to read with such giant pics!

I suggest: first do a Factory Reset, and then use GeigerLog and create a bug report file as described in the GeigerLog manual chapter "Problems, Bugs, and Bug Reports" and post file on Sourceforge Discussions:

https://sourceforge.net/p/geigerlog/discussion/general/

Registering at Sourceforge makes it easier, but you can post without it. The your post goes into moderation.

---

quote:

---

Originally posted by ullix

Hi Vance,
I need info on what your problem actually is.

Please, follow the steps outlined in the GeigerLog manual, chapter "Problems, Bugs, and Bug Reports".

---

quote:

---

Originally posted by ullix
You better use the original and the translated version side-by-side.

---

quote:

---

Originally posted by mimichris

As you corrected the sentence by removing the "en"

---

python -V

cd c:\geigerlog

....
16.681 gdev_wificlient.py
16.449 gdev_wifiserver.py
 2.440 geigerlog
...

python geigerlog

quote:

---

Installation of GeigerLog
It is suggested to place GeigerLog directly under c:\. Unzip the content of geigerlog-vXYZ.zip file to c:\. This will have created the folder c:\geigerlog with the required content.

Start GeigerLog from a Command Prompt window with:
python3 c:\geigerlog\geigerlog

More conveniently, create a shortcut to the file geigerlog in your geigerlog folder and place the shortcut on your desktop. Then open the shortcut’s properties and change its Target to:
python3 c:\geigerlog\geigerlog

Every time you click the shortcut, a Command Prompt window will open and GeigerLog will be started from there. Output from GeigerLog will go into this command window, but in addition always also into the program log file geigerlog.proglog in the data directory of GeigerLog.

If you don’t want this extra Command Prompt window, then edit the shortcut’s Target to:
python3w c:\geigerlog\geigerlog

Note the ‘w’! Remember to replace ‘python3’ with whatever your system requires; the ‘python3w’ might be a simple ‘pythonw’!

---

quote:

---

Originally posted by ullix

A major overhaul behind the scenes, but the user of just a GMC counter will barely notice the difference. The last stop before the 1.0 release.

The Windows installation, though, has gotten much, much simpler with the support of the very latest Python and graphic toolkit; details in the manual.

All available for download at the GeigerLog site at SourceForge: https://sourceforge.net/projects/geigerlog/

Image Insert:

175426 bytes

GeigerLog now supports multiple new devices, including I2C based sensors, more IoT devices, LabJack.

Of particular interest to Geiger aficionados will be the new support for audio-click signals from counters to collect CPS and CPM data, making classic counters, low cost counters, as well as the latest semiconductor counters available for handling and recording with GeigerLog. And all devices can be connected at the same time.

As the GMC counters offer both a digital output, as well as an audio-click output, they are a nice target to validate the AudioCounter performance of GeigerLog. Here an example for a GMC-300E+ counter, blue is digital connection, red is audio connection. No difference:

Image Insert:

115136 bytes

More thorough presentation and discussion in this article: GeigerLog-AudioCounter-Support https://sourceforge.net/projects/geigerlog/files/Articles/GeigerLog-AudioCounter-Support-v2.0.pdf/download


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Finally the GeigerLog Version 1.0 has just been released. See at the usual place:

https://sourceforge.net/projects/geigerlog/

---

quote:

---

Originally posted by ullix

GeigerLog has been awarded the SourceForge "Community Choice" for reaching the milestone of 10.000 downloads!
Given this niche application, this is a nice achievement! Thanks for your support.

---

quote:

---

Originally posted by ullix

Steven, sorry for the confusion. You have seen this right. Files under testing are for special purposes/users, and not for general use. Unfortunately, Sourceforge does not allow me to hide any files from general access. I have now deleted those files.

The latest files are always on this main page: https://sourceforge.net/projects/geigerlog/files/

Latest version is in "geigerlog-v1.3.0.zip".

---

quote:

---

Originally posted by ullix

Steven, sorry for the confusion. You have seen this right. Files under testing are for special purposes/users, and not for general use. Unfortunately, Sourceforge does not allow me to hide any files from general access. I have now deleted those files.

The latest files are always on this main page: https://sourceforge.net/projects/geigerlog/files/

Latest version is in "geigerlog-v1.3.0.zip".

---

quote:

---

Originally posted by ullix

Using Raspi as a GeigerLog WiFiServer Device Version 2.0

I have already reported on the WiFiEnabling of a GMC-300 counter (with no native WiFi) with the version 1.0 (http://www.gqelectronicsllc.com/forum/topic.asp?TOPIC_ID=9836)

But this version 2.0 is a major update to this previous version, establishing a prominent role for the Raspi as a data hub. So I think.

This version not only supports the GMC counter (slightly updated), but now also the use of I2C devices (shown with an LM75B sensor), and the use of pulse counting via Raspi Hardware Interrupt, done with the CAJOE counter as Demo. Took some fiddling with the hardware, but ...

All works well!

Download from the Raspi section https://sourceforge.net/projects/geigerlog/files/Raspi/

---

quote:

---

Originally posted by ullix

quote:

---

Did I do something wrong?

---

Apparently so. The first line of the geigerlog.cfg file, to which the error message refers, has become distorted. It has to look like this:

## geigerlog.cfg - The GeigerLog configuration file

However, before you try to correct anything:

If you can rule out that you yourself were the cause of this distortion, did you by any chance use Windows' Notepad or Wordpad program for the edits?

Microsoft's programs often have the undesirable "feature" to insist on changing all line endings to "Windows Style". The programs mentioned are notorious for this.

Never, ever use Notepad or Wordpad for editing any software files!

Instead, as an editor use "Notepad++", or, my preference, use "Geany". Both are well behaved, open source, non-Microsoft programs.

Don't try to correct the existing, ruined config file; download a new one, and work on this.

---

quote:

---

Did I do something wrong?

---

## geigerlog.cfg - The GeigerLog configuration file