Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TSourceCalibration Segmentation Violation #1416

Open
samanthalange opened this issue May 22, 2024 · 0 comments
Open

TSourceCalibration Segmentation Violation #1416

samanthalange opened this issue May 22, 2024 · 0 comments

Comments

@samanthalange
Copy link

samanthalange commented May 22, 2024

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 23c8da0 (HEAD -> main, origin/main, origin/HEAD)
Merge: 291d66d ff19576
Author: Vinzenz Bildstein [email protected]
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant