[jsdl-wg] Param Sweep : artf6148 : Matching output with sweep indexes?
geoff
geoff.williams at comlab.ox.ac.uk
Mon Aug 11 09:11:54 CDT 2008
Hi folks,
As per the artifact I've been trying to think of a way to have the
ability to indicate that 'n' distinct jsdl jobs have been created by a
sweep but have not been able to define a means of doing so. The
principal stumbling block, I believe, is that the job number is
effectively a calculated value derived from processing a jsdl sweep
element hierarchy and so cannot be defined within such a hierarchy.
The nearest (but flawed) potential solution I considered was specifying
the use of a reserved word/token within a jsdl document or input
template file e.g.
<jsdl-posix:Argument>outputDir/@jsdlJobNumber@</jsdl-posix:Argument>
such that a JSDL consumer would substitute the respective jsdlJobNumber
during sweep processing. One flaw at least would be the requirement for
coordination by anybody creating a JSDL document, and also a JSDL
consumer, in the use of XPath functions such as substring() e.g.
..
<jsdl-posix:Argument>outputDir/@jsdlJobNumber@/example/</jsdl-posix:Argument>
..
<sweep:Sweep>
<sweep:Assignment>
<sweep:DocumentNode>
substring(/*//jsdl-posix:Argument[1], 19)
</sweep:DocumentNode>
<sweep:LoopInteger start="1" end="100" />
</sweep:Assignment>
</sweep:Sweep>
Anybody aiming to have the LoopInteger value appended to the argument
string during processing needs to ignore the length of the
@jsdlJobNumber@ character sequence during JSDL specification. Similarly
the JSDL processor needs to be aware of the need to make two value
substitutions into the Argument during processing.
gef
More information about the jsdl-wg
mailing list