Project

General

Profile

Actions

Bug #2960

closed

Change RExpression actor to use meaningful graphic file output names

Added by ben leinfelder over 16 years ago. Updated over 15 years ago.

Status:
Resolved
Priority:
Normal
Category:
actors
Target version:
Start date:
09/11/2007
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2960

Description

Possibilities include:
-nested workflow.composite_actor.actor.incremental_number naming
-use a similar approach to above, but somehow track subsequent runs of the workflow (like versioning 1.1, 1.2, 1.3 would indicate three different runs of the same workflow/actor)
-have user set prefix for output object (either as parameter or port) in the actor
-create new output directory (likely timestamp) for each workflow execution to group output files.

probably end up using a combination of the choices here.
directory + actor_name being a likely candidate

Actions #1

Updated by Dan Higgins over 16 years ago

Graphics file name of RExpession actor is now the actor name plus an integer (instead of user name). (Dan Higgins)

Actions #2

Updated by ben leinfelder about 16 years ago

By using getFullName() rather than getName() we can get the nested naming mentioned in the original comments for this bug. A workflow with an RExpression actor inside a CompositeActor would generate files named something like:
Workflow_name.CompositeActor_name.RExpression_name1.pdf
Workflow_name.CompositeActor_name.RExpression_name2.pdf
...
Workflow_name.CompositeActor_name.RExpression_nameN.pdf

This still does not address tracking multiple runs of the same workflow, but it does allow easy sorting of the output files for complex workflows and also distinguishes the output of separate workflows.

note: not committed to cvs yet

Actions #3

Updated by ben leinfelder almost 16 years ago

During the follow up meeting, we decided to use the following approach for the R expression file output:
For each run, a new "run" folder will be created and the output from actors in that run will be deposited in that directory. here's an example:
run one:
$KEPLER/tmp/run1/myRActor1.pdf
$KEPLER/tmp/run1/myRActor2.pdf
$KEPLER/tmp/run1/myRActor3.pdf
run two:
$KEPLER/tmp/run2/myRActor1.pdf
$KEPLER/tmp/run2/myRActor2.pdf
$KEPLER/tmp/run2/myRActor3.pdf
etc....

Actions #4

Updated by ben leinfelder over 15 years ago

added a WorkflowExecutionListener that keeps track of currently executing workflows and provides the R Expression actor with a mechanism for constructing subdirectories for the output of the given workflow run.
Subdirectories use the naming convention:
<workflow name>_<millisecond timestamp>

Actions #5

Updated by Redmine Admin almost 11 years ago

Original Bugzilla ID was 2960

Actions

Also available in: Atom PDF