GRIFFINCollaboration / GRSISort

A lean, mean, sorting machine.
MIT License
21 stars 54 forks source link

TSourceCalibration Segmentation Violation #1416

Open samanthalange opened 4 months ago

samanthalange commented 4 months ago

ErrorReport.sh HOSTNAME = samantha-XPS-9320 SYSTEM = Linux OS = Ubuntu VER = 22.04 GRSISYS = /home/samantha/GRSISort ROOTSYS = ROOT Version = 6.30.04

Computer and Path to File that failed:

GRSISort Branch = main

commit 23c8da0a7e0991a7146831fbd227cba22996f30a (HEAD -> main, origin/main, origin/HEAD) Merge: 291d66df ff195768 Author: Vinzenz Bildstein vbildste@uoguelph.ca Date: Mon Feb 5 17:12:29 2024 -0500

Merge pull request #1383 from VinzenzBildstein/main

Added missed source file for TUserSettings

Describe the bug I'm having an issue when I run TSourceCalibration for multiple sources where I cannot get to the page that shows the results of the different sources combined. When I accept all the results for each of my sources I am stuck on the loading screen for the combined results page and get the following segmentation violation:

Screenshot from 2024-05-22 11-36-59 Screenshot from 2024-05-22 11-37-09

Screenshot from 2024-05-22 11-46-30

To Reproduce

This occurs specifically after I get another segmentation violation. I often zoom into the histograms when trying to fit the peaks. Sometimes I accidentally click on the line of the histogram while my cursor is hovering over it. This turns the histogram into a default with error bars and I get the segmentation violation shown below. Even if I get my histogram to return to a lined histogram, when I accept all my results for the individual sources, I am stuck on the loading page and receive the segmentation violation shown above.

Screenshot from 2024-05-22 11-39-22

Screenshot from 2024-05-22 11-39-48

Screenshot from 2024-05-22 11-35-54 Screenshot from 2024-05-22 11-36-07

Expected behavior What I expect is that after finding the peaks for each of the sources and accepting all, I should be directed to the combined results page where I can finish my calibration.

Additional context This is quite stange as I'm not sure why the first segmentation violation would lead to the second one. To avoid getting this issue moving forward, I will be logging my axes instead of zooming in to avoid accidentally clicking on the lines of the histogram.