[kepler-dev] [Bug 5426] New: workflow lsid changes when running from command line

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5426

           Summary: workflow lsid changes when running from command line
           Product: Kepler
           Version: 2.1.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: core
        AssignedTo: david.v.welker at gmail.com
        ReportedBy: crawl at sdsc.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


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.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.