Task #6559 python plugins as node script. they can return a dict that gets saved by the master script as mapfile and can be used as input for later steps.

Task #6559 small update changing the automatic naming of results. names were too long and now only contain the last stepname the data went through.

Task #6559 Update from march busy week. Functionality for extreme peeling preparation and bug fixes.

Task #6559 Next iteration: executable-args recipe handles multiple input mapfiles with inputkeys for the including files. parameter for individual processes per node. the master recipe handles the executable_args and executable_casa noderecipes. casa now has individual tmpdirs as working dir which enables multiple instances on one node. changes in genericpipeline so that more than one occurence of outputreference can be replaced.

Task #6559 First experiments with a casapy recipe. Works in basic form for now but with workarounds for proper return values to the pipeline. casapy does not seem to return in a usual way. when there is an error the pipeline does not recognize the process has finished. without the encapsuleting in a shell script even a successful run does not return. Needs more checking and a cleaner way of calling. Maybe integrate casa python classes to the Lofar install? Loops: Nested loops work. Breaking a loop only works for one full cycle. Outputdictionaries you reference with step.output.stepval are now always for the last call of that step.

Task #6559 overhaul of the executable_* recipes. The arg one now covers all argument based calls and calls with saved parsets on the node side.

Task #6559 This is the third iteration. Introducing loops and additional recipes for executables in general. Both not 100% finisehd. Loops work but more work has to be done concerning in/output of the steps within the loop. Loops are pipeline steps themself which hold a list of steps they add to the pipeline run. If not using a fixed number of iterations one step in the loop should be a break condition step. This step specifies in its output if the loop should break and the pipeline continue its work. The parsetonly recipe now handles dppp and awimager steps. For patching the parset on node level in/output keywords have to given in the step control section.