opengammaproject / gamma-mca Goto Github PK

With a large number of accumulated points, for example ~ 1 million on my low-end PC, it takes a long time to render the time series plot. The displayed "cps" number may be relative to active plotting time and not wall-clock time, so the first reported value for cps immediately after closing the time series graph to return to the spectrum graph may be very large, for example 10x or more larger than the typical value.
Subsequent display of the time series plot shows this spuriously large number as a real data point, while it may be an artifact of available CPU time and not a deviation in true count rate. This could be some unavoidable consequence of the code being a browser plugin (?) The two high outlier data points visible in the plot below were caused by this effect. It does not occur in a plot if the "Show Evolution" button is never used.

Dobrý den,
při volbě set mode geiger jsou na seriový port zasílány jen samé 0.
Při volbě energy je vše v pořádku.
děkuji

First; great project, and I don't know if this is an issue or simply working as intended.

I built OpenGammaDetector PCB Rev 4.0, changing the layout to remove the two inner ground-plane layers, and cut off the mechanical-support-only part of the PCB to reduce cost. Even on a 2-layer PCB, the circuit seems to work, testing with one SiPM at Vbias = 29.1 V using a random chunk of plastic scintillator. I adjusted the threshold pot R8 for what looked reasonable on the scope. I dragged and dropped the code file https://github.com/OpenGammaProject/Open-Gamma-Detector/blob/main/software/ogd_pico-4.0.3.uf2 onto the Pico.

I do not yet have a I2C display attached to the board, but at first impression the hardware and Pico code works perfectly. It is connected via USB to a Mint Linux box running Gamma MCA Version 2023-12-30 with all controls in the "Settings" tab left at default; I did not enable a time limit to acquisition. I did not do any calibration. I put a chunk of ore on the scintillator and saw a count rate near 2800 cps, sometimes exceeding 3000. I left it to run 9 hours overnight.
In the morning I could see from the activity LED on the board that it was still counting, but the app reported count rate was 0 cps, showing Spectrum: 74781924 cts 09:22:27 so I wonder, did it stop accumulating due to some memory limit in the app? I don't even know what to expect from a plastic scintillator material, I'm told it is not useful for spectroscopy, but I suppose the spectrum looks plausible. Also shown is a short run with 547 cps count rate, using a 0.25 uCi Cs-137 source.
I was able to save the data, clear the spectrum, click "Record" and the app works OK again, showing the expected count rate.

Using serial console in Gamma MCA, connecting to the serial interface of the Open Gamma Detector is not working for me.
Pico shows up correctly in the Port menu and spectrum recording also works just fine via the serial interface of Gamma MCA.
Of course, connecting to the serial interface of Open Gamma Detector via Arduino IDE works.
Am I missing something here?
Many thanks in advance!

Hi
A new version installed today (2023/07/23) and I am not able to load a CSV file. I use the semicolon as the delimiter in the file and have set the semicolon as delimiter in the settings of the program.

I recorded a short spectrum, saved it as histogram and found that the saved file does not use delimiters, but separates the entries by new line charcters. So I replaced the semicolons in my spectrum file with new line characters and the import worked.
Is there a setting that I missed when importing semicolon-delimited CSV files?

Hallo Phoenix 1747

i would like to ask ,is there any Possibility to create a real OFFLINE APP which could be executed as .EXE. The Gamma MCA (and also the i would say OFFLINE Subfunction) is coupled on Restrictions concerning Browser Version and Types. So if you not fulfill all Requirements very exactly you have unfortunately no Chance for a good read out of the USB connected Hardware. I have a MAC OS Chrome 103 Version which should normally support your MCA .......but it doesent (some Zertificat Troubles from Chrome)

Thank you

Steffen

Just found out that you can inject HTML and JS into the website using malicious custom isotope lists that contain code in the JSON data. This means that any custom list could hijack Gamma MCA with little to no user input aside from actually confirming the URL.

These two lines especially use the innerHTML property without cleaning or checking any input:

https://github.com/Open-Gamma-Project/Gamma-MCA/blob/049c8d5df6793e0d0af6b23c6e04527bccdd922f/assets/js/main.js#L562
https://github.com/Open-Gamma-Project/Gamma-MCA/blob/049c8d5df6793e0d0af6b23c6e04527bccdd922f/assets/js/main.js#L567

I made a quick JSON list that injects such code to test and confirm it:

https://gist.github.com/Phoenix1747/6f400c583c2fe607281dd700c72dcb93

When using the "histogram" mode for serial devices sometimes the received count rate drops to 0 until the next refresh. If you increase the plot refresh time, then this effect will be averaged out and approach about 70-80% of the actual count rate.

It looks like possibly every 2-3 refreshes, there are no received counts and therefore the cps drops to 0 too. It is somewhat random, though. Maybe this is a problem with the Open Gamma Detectors I am using here. It would be extremely helpful if someone can reproduce this issue on their side as well. 👍

I don't know why this happens, using the default "chron mode" everything is fine. This might also be a problem with the Web Serial API if the received data is too large, but I don't think so, honestly. Maybe it's also a problem with the serial options. But probably it's just something in the code...

Hi,

Firstly, I want to extend my congratulations on the exceptional work done here. This tool serves as a fantastic interface for open-source or DIY gamma spectrometers.

I have tested the Chrome-based version of the software and found it performs efficiently in chronological mode. However, I encountered an issue in histogram mode: the plot fails to refresh with the arrival of new data.

I've provided the settings I'm utilizing below. Notably, the serial data stream is accurately displayed in the console.

As a tester, I am using an esp32 with the following code (Arduino IDE 2.2.1):

uint16_t spectrum_1[256];
String spectrumStr;

void setup() {
  Serial.begin(9600);
  for (uint16_t i = 0; i < 256; i++) {
    spectrum_1[i] = 1;
  }

}

void loop() {
  spectrumStr = "";
  for (uint16_t i = 0; i < 256; i++) {
    //Serial.print(spectrum_1[i]); Serial.print(";");
    spectrumStr += "1";
    spectrumStr += ";";
  }
  Serial.println(spectrumStr);
  delay(3000);
}

The stream of 1s is correctly shown in the console, but the plot and cts do not reflect this. What am I missing?

Thanks for your support,
Andrea

Hello,
when selecting set mode geiger, only 0 are sent to the serial port.
When choosing energy, everything is fine.
Thank you