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

Warning: pulse time ouside window for NSB pixels #269

Open
FrancaCassol opened this issue Jan 22, 2020 · 4 comments
Open

Warning: pulse time ouside window for NSB pixels #269

FrancaCassol opened this issue Jan 22, 2020 · 4 comments

Comments

@FrancaCassol
Copy link
Collaborator

Hi,
since the charge extractor finds the pulse time by weighting the sample time with its charge, in the case of NSB pixels the charge can be negative and this gives strange pulse times. There is a ctapipe a PR from @watsonjj to exclude negative samples from the calculation cta-observatory/ctapipe#1143, till then we will have some pixels with time outside the expected window (but this should mainly concern pixels without signal)

@moralejo
Copy link
Collaborator

moralejo commented Jan 22, 2020 via email

@vuillaut
Copy link
Member

It's not pending, the issue has been addressed and the PR accepted long ago. It will be integrated in lstchain with the next release of ctapipe.
But that should not be a concern after cleaning (and the timing parameters are computed on cleaned images).

@FrancaCassol
Copy link
Collaborator Author

Hi @vuillaut,

It's not pending, the issue has been addressed and the PR accepted long ago. It will be integrated in lstchain with the next release of ctapipe.

you are right, I overlooked it. Perhaps we should slowly start to updated the ctapipe_master branch so to be ready to move to the new ctapipe release when available

But that should not be a concern after cleaning (and the timing parameters are computed on cleaned images).

My comment was related to the pulse time per pixel, which is calculated by the charge extractor at the calibration level before the cleaning

@moralejo
Copy link
Collaborator

moralejo commented Jan 23, 2020 via email

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

3 participants