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

Changes for adding Cameras beyond LSTCam and NectarCam #29

Merged
merged 2 commits into from Nov 15, 2019
Merged

Changes for adding Cameras beyond LSTCam and NectarCam #29

merged 2 commits into from Nov 15, 2019

Conversation

tstolarczyk
Copy link
Contributor

New config file to test beyond LSTCam and NectarCam cameras based on prod3b files

…tion) - This corrects wrong values for LST and MST-Nectar - Iteration numbers are printed up to 10 events, and then every 10 events (if debug=True)
@tstolarczyk tstolarczyk changed the title Config file for testing more cameras Changes for adding Cameras beyond LSTCam and NectarCam Nov 8, 2019
@HealthyPear HealthyPear requested review from vuillaut and removed request for vuillaut November 12, 2019 10:05
thresholds: # picture, boundary
- LSTCam: [6, 3]
- NectarCam: [8, 4] # TBC
- FlashCam: [0,0]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

won't that accept all pixels? Later, it's set to [8,4], so should at least be consistent.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I agree, otherwise, the two cleanings will not be equivalent as it is now (even though we don't know for sure if they should). Regarding their precise values, I don't think is important for the moment since they can be changed anyway by the user.

ievt+=1
if (debug):
if (ievt< 10) or (ievt%10==0) : print(ievt)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps it is better to put the increment inside the conditional block, so we avoid to do it also when debug is False

thresholds: # picture, boundary
- LSTCam: [6, 3]
- NectarCam: [8, 4] # TBC
- FlashCam: [0,0]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I agree, otherwise, the two cleanings will not be equivalent as it is now (even though we don't know for sure if they should). Regarding their precise values, I don't think is important for the moment since they can be changed anyway by the user.

@HealthyPear HealthyPear merged commit 3ab17d9 into cta-observatory:master Nov 15, 2019
@HealthyPear HealthyPear added the enhancement New feature or request label Oct 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants