PipelineRunner parameter flag

[Kate Alpert]

Hi all,

I am having trouble using PipelineRunner (both 1.5 and 1.6) with a -parameter basedir=$TMPDIR argument.  The "Param Value Pair" is set properly "Param Value Pair basedir=/home/me/tmp", however, I immediately receive the following error:

"org.nrg.pipeline.exception.PipelineEngineException: Couldn't resolve ^/Pipeline/parameters/parameter[name='basedir']/values/unique/text()^ XPath Expression for step[1]".

Any ideas?

Thanks,

Kate

[Mohana Ramaratnam]

Hi Kate,

Could you please send me the pipeline xml and also the pipeline log file.

PS: I am looking into the Notification issue using PipelineRunner.

Mohana

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at http://groups.google.com/group/xnat_discussion?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Mohana Ramaratnam]

Hi Kate,

I wonder what the person who wrote the pipeline code was thinking. PipelineRunner will either take a parameter file or all parameters using -parameter NAME=VALUE, it cannt handle both. This ability is there in XNATpipelineLauncher, but was not reflected in PipelineRunner.

I will modify the code of PipelineRunner to accept both, until then, please set all input arguments using one of the two - parameter file or -parameter NAME=VALUE.

Mohana

On Wed, Feb 27, 2013 at 10:42 PM, Kate Alpert <kathryn...@gmail.com> wrote:

--

[Kate Alpert]

Wonderful, Mohana, thanks!

[Kate]

Hi Mohana,

For PipelineRunner 1.5, it seems that the -parameter NAME=VALUE cannot handle a VALUE with a space - e.g., -parameter reconopts="-all -qcache".  Is this correct?  If so, any recommendations for how best to get around this?  Perhaps a writing a custom class like StringUtils?

Thanks very much,
Kate

[Kate]

Update: I figured out a work-around using commas and PIPELINE_LOOPVALUE.