hi, Some notes following the JSDL-WG session 1. It was generally agreed that sweeping over values defined within input files should be 'in scope' of the JSDL parameter sweep extensions. However, needs some more clarification. Two different / opposing options were discussed which determine whether sweeping over values within input files is in scope or out of scope of the JSDL Sweep extensions: Option 1) out of scope All input files should be generated 'up-front' and staged to the working dir (or to different JSDL file systems) by 'some other process'. This would mean the Sweep extensions could be used as they currently exist (i.e. by sweeping over the name/location of the existing generated files). In this scenario however, the JSDL-Sweep extensions would *not* have any use in defining the parametric values that are substituted into the input files (e.g. via loops/value lists). If this is preferred, then this would have to be clearly stated within the JSDL documentation, and I would also argue that sweeping over values within input files would then be 'out of scope' of the JSDL parameter sweep extensions. Option 2) in scope The JSDL Sweep document *should* be used to define the values of parametric variables that are substituted into the input files (e.g. via loops/value lists). In this scenario, sweeping over values in input files would be in scope' of the Sweep extensions. If this is preferred, then it appeared that the use of the ${placeholder} variables that exist within the input files and referred to in the JSDL Sweep document could be applied. How a JSDL sweep document names/reference the input files needs clarification (e.g. abstract extension points akin to the loop/value functions?). regards, dave ------------------------ Dr David Meredith STFC - eScience Centre Grid Technology Group Daresbury Laboratory Warrington Cheshire WA4 4AD Tel: 01925 603762(Direct Line) email: d.j.meredith@dl.ac.uk