-
Notifications
You must be signed in to change notification settings - Fork 4
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
Implementing generic analysis methods inside detectorlib #75
Open
juanangp
wants to merge
16
commits into
master
Choose a base branch
from
signal-ana
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 5 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
9a817d4
Implementing generic signal processing functions inside detectorlib
juanangp 3458ff1
Merge branch 'master' of github.com:rest-for-physics/detectorlib into…
juanangp c4ae874
Implementing generic signal processing methods inside detectorlib
juanangp dcf6d3b
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] fc30468
Adding protection at TRestDetectorSignal::Sort() in case both vectors…
juanangp 9c910cf
Reverting Sort function since it is buggy in new implementation
juanangp 42bbebf
Addressing bug which made the pipeline fail
juanangp 5156e0e
Addressing bugs
juanangp c6de5fc
Addressing pipeline failure, although the functions should be doing t…
juanangp dd34dae
Removing baseline related methods
juanangp 87f8460
Renaming TRestSignalAnalysis to TRestPulseShapeAnalysis
juanangp cad751e
Merge branch 'master' into signal-ana
juanangp 29175e5
Merge branch 'master' into signal-ana
juanangp 8ca222a
Merge branch 'master' into signal-ana
juanangp 474dd4a
Merge branch 'master' into signal-ana
juanangp 299a050
Merge branch 'master' into signal-ana
juanangp File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me it makes no sense to have a baseline at the detector signal level. This is a stage where we have already applied data reduction. And in the best case reduced our waveforms into physical times and amplitudes.
It was kind of first approach to take all points from raw to detector signal. But we should move towards a reconstruction that reduces the data.
I understand the issue with
short_t
precision in rawlib, that's why I think having astd::vector <float_t>
or evenstd::vector <double>
implemented insideTRestRawSignal
would solve this problem, so it this vector is not empty it means a process has filled it, and then processing will continue atfloat_t
ordouble_t
levels.That way you leave also all time-signal processing routines contained within rawlib, which was one of the duties of the raw library. To compile all those codes used for time signal processing into a single entity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These functions can be indeed deleted, however I don't know if it is a good idea to define a
std::vector <float_t>
insiderawlib
since it could be misleading. Which data is supposse to hold? Data with baseline substracted, points over threshold or smoothed data?There are as well signal processing functions that can be used in other context, e.g. tripleMax, GausFit and many others are currently implemented inside
detectorlib
(actually tripleMax was duplicated inside rawlib). But in principle one could try to perform a gaussian fit to aTRestRawSignalEvent
.I believe that to make a generic class or namespace inside framework for signal analysis or processing is the way to go...