[kepler-dev] [Bug 3186] New: - commit RExpression code changes, but leave actor open
bugzilla-daemon@ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Tue Mar 25 17:18:05 PDT 2008
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3186
Summary: commit RExpression code changes, but leave actor open
Product: Kepler
Version: 1.0.0beta3
Platform: All
OS/Version: All
Status: NEW
Keywords: evaluate, kruger
Severity: normal
Priority: P2
Component: actors
AssignedTo: berkley at nceas.ucsb.edu
ReportedBy: drury at nceas.ucsb.edu
QAContact: kepler-dev at ecoinformatics.org
R-script development within an RExpression actor can get pretty tedious. For
example, when you add a line of code and want to test its effects, you push the
RExpression actor "commit" button and this closes the RExpression actor. You
can then run the workflow. Then, to make the next small change, you re-open
the RExpression actor, alter the code, push "commit", etc. I have repeated
this procedure 741 times in a single day (yes, I counted :). It would be
REALLY nice if, when the text within the R-code window of the RExpression actor
changed, the "submit" button would become activated (i.e., not grayed out).
Then, when an analyist has added the next bit of code, they can just push
submit and "run" the workflow. In other words, "submit" does not close the
RExpression actor, but does make R-code changes visible to the workflow. Is
this possible with Kepler?
More information about the Kepler-dev
mailing list