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

Include R0V generation in OSA chain #298

Open
contrera opened this issue Jul 24, 2024 · 3 comments
Open

Include R0V generation in OSA chain #298

contrera opened this issue Jul 24, 2024 · 3 comments

Comments

@contrera
Copy link
Collaborator

Right now (summer 2024), R0V creation is done manually by the people at UAH, demanding a large amount of human work and introducing a bottleneck in the processing. We should consider the possibility of automatizing it.

In addition, AFAIK, no test is done that results are reproduced after R0V creation. Some automatic test on a subsample of data or a few variables would help to detect errors in R0V generation.

@morcuended
Copy link
Member

I'm not familiar with the latest script for performing DVR. Is the one in #272 still being used? I guess it should be similar to the one for running gain selection.

@moralejo
Copy link

As for checks, you are right @contrera, they were done to validate on specific runs to validate the software, but there is no regular check.
Basically it would be enough to check that
(1) interleaved events have all pixels and both gains
(2) shower events have all pixels that survived cleaning (those can be retrieved from the subrun-wise DL1 files, which contain the pixel masks), and of course just 1 gain (not sure if such a check is performed on R0G already)

@morcuended
Copy link
Member

Plus the checks that jobs have been finished successfully and the number of files is consistent

(1) interleaved events have all pixels and both gains
(2) shower events have all pixels that survived cleaning (those can be retrieved from the subrun-wise DL1 files, which contain the pixel masks), and of course just 1 gain (not sure if such a check is performed on R0G already)

I think these checks should be implemented in lstchain and called here

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