-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add optional LST stereo trigger requirement #131
Merged
HealthyPear
merged 12 commits into
cta-observatory:master
from
HealthyPear:feature_add-LST-stereo-trigger-option
May 12, 2021
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
6ecb0b6
add LST_stereo mode to the analysis configuration file
HealthyPear 0fb975a
update event_preparer accordingly
HealthyPear edd137b
Set LST_stereo to True if not specified in the configuration file
HealthyPear 22304dc
not_LST_triggered_telescopes to non_LST_triggered_telecopes
HealthyPear e76abf2
Update documentation
HealthyPear bda9593
Remove section proposal for improvement
HealthyPear da24201
Merge branch 'master' into feature_add-LST-stereo-trigger-option
HealthyPear 8bbda29
Add concentration dict to stub event in case of bad_LST_stereo
HealthyPear b9a19b6
Update from master and solve merge conflicts
HealthyPear 390d744
Use sets for triggered telescopes with data
HealthyPear be46eb9
Fix bug and improve debug printed information
HealthyPear 4d4a6b5
Merge branch 'master' into feature_add-LST-stereo-trigger-option
HealthyPear 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
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
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.
I think this is not needed: just set every telescope in triggers_LSTs to 0 - it doesn't matter if it was true before.
What should
good_for_reco
be in the end? a variable-length list of tel_ids? or a boolean array of tel indices? Right now it is a dict, but it seems you encode both the tels with data, and which ones pass the cuts in it at the same time, which is why it is confusing. I'd suggest just storing those separately if you need both. In ctapipe, we automatically convert telescope lists into boolean arrays so they can be stored in the hdf5 output without using var-length arrays (SubarrayDescription provides a method for that:)If it's a boolean mask like that, you can get rid of this explicit loop and just use array indexing or set subtraction:
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.
This way you remove this explicit loop entirely
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.
good_for_reco is not a boolean mask, but a dictionary where the keys are tel_ids (only the ones related to that particular event) and the values are 1 if the cleaned+parametrized image passed all quality cuts, 0 otherwise.
It is then written to file
honestly, I would avoid trying to make this more fancier now considering that soon it will all disappear, unless it it clear that there is a bug due to how I wrote it
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.
so basically what is happening here is that I set the value to 0 only if the image passed the quality cuts (otherwise it is already been set to 0) thus I "remove" the single-LST image by not using it later for shower geometry reconstruction, but since I need to process it up to DL1b for the benchmarking I still need to know (via my dictionary of labels "good_for_reco") if it would have been used in other circumstances
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.
ok, if this is not meant to be long-term code, fine. This was just so that you could write out the used telescope pattern as we do in ctapipe, but maybe that is not needed since we will soon move to ctapipe's version.
I was more thinking about doing it right here, so we can just move the code to ctapipe later.