This is CASA eMERLIN pipeline to calibrate data from the e-MERLIN array. Please fork the repository before making any changes and read the Coding Practices page in the wiki. Please add issues with the pipeline in the issues tab.
To be implemented:
Write a default_parameters file with all the internal parameters used by the pipeline, so the user can change any particular value without needing to modify the pipeline code. For example if they need to change the solint on some gaincal step.
There are two options:
1 - Give the option to use a different parameters file that the user can locally have in the working directory, for example. This requires a selectable option to use or not that file.
2 - The parameters file will always be inside the CASA_eMERLIN_pipeline directory and will be unique (not selectable) and the user will have to modify it there.
I prefer option 2 because that avoids having different parameter files, which makes everything ambiguous. That option means that the user will need an specific pipeline for that project (instead of a global "installation"), but I think that is the standard current approach and what we should recommend, because the pipeline is small and this way it is easy to keep track of what version/modification was used for each observation.
jmoldon
commented
5 years ago
To be implemented: Write a default_parameters file with all the internal parameters used by the pipeline, so the user can change any particular value without needing to modify the pipeline code. For example if they need to change the solint on some gaincal step.
There are two options: 1 - Give the option to use a different parameters file that the user can locally have in the working directory, for example. This requires a selectable option to use or not that file. 2 - The parameters file will always be inside the CASA_eMERLIN_pipeline directory and will be unique (not selectable) and the user will have to modify it there.
I prefer option 2 because that avoids having different parameter files, which makes everything ambiguous. That option means that the user will need an specific pipeline for that project (instead of a global "installation"), but I think that is the standard current approach and what we should recommend, because the pipeline is small and this way it is easy to keep track of what version/modification was used for each observation.