Project

General

Profile

Actions
Copy link

Bug #5426

closed

workflow lsid changes when running from command line

Added by Daniel Crawl over 13 years ago. Updated over 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Daniel Crawl
Category:
core
Target version:
2.4.0
Start date:
06/20/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5426

Description

There are two problems that occur when running a workflow from the command line and specifying a non-default parameter value.

The first is that the revision is always incremented if the parameter value is the same:

./kepler.sh -runwf -nogui -x 4 ~/KeplerData/paramx.xml

WF LSID is urn:lsid:kepler-project.org/ns/:6018:25:2

./kepler.sh -runwf -nogui -x 4 ~/KeplerData/paramx.xml

WF LSID is urn:lsid:kepler-project.org/ns/:6018:25:3

The second is that if .kepler and KeplerData/modules/core/coreDB do not exist, a new LSID is used:

./kepler.sh -runwf -nogui -x 4 ~/KeplerData/paramx.xml

WF LSID is urn:lsid:kepler-project.org/ns/:6020:1:1

For desktop use, .kepler and KeplerData usually do not get deleted, but when executing on a cluster, these directories are not always available. This causes problems for provenance, e.g., the same workflow run on 10 different nodes will be identified as 10 different workflows instead of 10 runs of the same workflow.

Files

paramx.xml (23.6 KB) paramx.xml Daniel Crawl, 06/20/2011 11:20 AM
Actions
Copy link

Also available in: Atom PDF