Skip to content
Snippets Groups Projects
  1. Jul 04, 2016
  2. Jun 27, 2016
  3. Jun 19, 2016
  4. Apr 15, 2016
  5. Apr 01, 2016
  6. Mar 24, 2016
  7. Jan 14, 2016
  8. Dec 18, 2015
  9. Nov 05, 2015
  10. Oct 13, 2015
  11. Aug 21, 2015
  12. Aug 19, 2015
  13. Jun 22, 2015
  14. Jun 12, 2015
  15. Jun 10, 2015
    • Stefan Froehlich's avatar
      Task #6559 Added a calibrate stand alone node script that directly calls... · 99f60d9c
      Stefan Froehlich authored
      Task #6559 Added a calibrate stand alone node script that directly calls bbs-reducer and not the calibrate-stand-alone shell script. This way bbs-reducer gets called by the pipeline infrastructure and not as a subprocess called by a different mechanism. Also the order of the arguments should not matter anymore when they are given as parset arguments (long options).
      99f60d9c
  16. May 08, 2015
  17. May 04, 2015
  18. Apr 17, 2015
  19. Mar 26, 2015
  20. Mar 23, 2015
  21. Mar 09, 2015
  22. Feb 25, 2015
  23. Feb 20, 2015
    • Stefan Froehlich's avatar
      Task #6559 Next iteration: executable-args recipe handles multiple input... · a8bcc6ef
      Stefan Froehlich authored
      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.
      a8bcc6ef
  24. Feb 19, 2015
  25. Feb 06, 2015
    • Stefan Froehlich's avatar
      Task #6559 First experiments with a casapy recipe. Works in basic form for now... · 124d9f81
      Stefan Froehlich authored
      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.
      124d9f81
  26. Feb 03, 2015
  27. Jan 16, 2015
    • Stefan Froehlich's avatar
      Task #6559 This is the third iteration. Introducing loops and additional... · abefff6c
      Stefan Froehlich authored
      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.
      abefff6c
  28. Dec 08, 2014
  29. Nov 28, 2014
  30. Nov 21, 2014
  31. Nov 07, 2014
  32. Nov 06, 2014
  33. Oct 29, 2014
    • Stefan Froehlich's avatar
      Task #6559 An attempt for generic processing a pipeline defined by parsets.... · 3db6ad00
      Stefan Froehlich authored
      Task #6559 An attempt for generic processing a pipeline defined by parsets. Worked backwards from the dppp scripts. The node script still has patch parsets routines.
      For the moment this can only handle some basic stuff. Chain recipes that as only input get a mapfile and a parset and throw some "plugins" inbetween. The plugins have to be given some thought. Are they useful/needed? Need templates/interfaces? etc
      Should all recipes be required to handle mapfiles/MS?
      The go() method in the pipeline scripts are only required to set a name for the pipeline. Moved this functionality to the baserecipe to avoid redundancies. Now only the pipeline_logic has to be reimplemented.
      We need standard/templates for recipes so they can be used in a unified way by pipeline scripts.
      3db6ad00
Loading