Workflow for optical throughput with muons

Summary

Need to add workflows for the UC regarding optical throughput with muons. I suggest postponing the implementation of UC-120-2.1 "Compute absolute optical throughput" until we are sure how optical throughput measurements from different methods should be combined - in current level B requirements it is not fully clear.

Up to now, I will create a workflow for the UC-120-2.2 "Optical throughput via muon rings analysis". As templates, I will use already created atmospheric profile workflows.

What is the expected correct behavior?

How optical throughput with muons workflow should work:

1. The throughput_calibrator tool is launched with input arguments:

• file with events
• file with configurational parameters

2. Result: optical throughput is calculated and stored in DB.

Open question

Here is raised one important question regarding the config file, because each type of telescope will have different configurable parameters for better quality cuts on muons (e.g. min_pixels, ImageExtractor type, etc). Therefore we need to implement either:

• one initial input config file with paths to distinct config files for each type of camera, and then the pipeline will check camera type and upload the appropriate config file during running;
• one config file for all cameras (as now), and new dedicated method in MuonCalibrator will override required values concerning particular telescope/camera type;