...
- Run in sandbox
- Values: TRUE/FALSE
- Defines if application could be run in any directory or in specified one ("sandbox")
- Default value: FALSE
- Sandbox lifetime
- Values: "Actor execution", "Workflow execution"
- Defines if sandbox directory should be accessible only for given execution of particular actor ("Actor execution") or during the whole run of the workflow ("Workflow execution")
- Default value: "Actor execution"
- Clean up sandbox
- Values: TRUE/FALSE
- Determines if content of checkbox should be cleaned up before
- Every execution of the actor (if lifetime is set to "Actor execution")
- First execution of the actor in workflow (if lifetime is set to "Workflow execution")
- Default value: TRUE
Warning If an option "Clean up sandbox" is selected, it deletes the whole content of directory
- Sandbox directory path
- Text field
- Empty field:
- Default value: <SANDBOX_ROOT>/<UNIQUE_ACTOR_INSTANCE_NAME>_<PROCESS_ID>
- name is unique to given instance of an actor, in case if there are several instances of one actor in WF
- name is unique to given instance of a running Kepler, in case if there are several instances of Keplers' running in parallel
- User specified value
- It may be only relative to <SANDBOX_ROOT> - a directory with user specified name will be created under <SANDBOX_ROOT> (if not exists)
- FC2K performs no action on provided name (i.e. it is used "as it is" without any changes to make it unique etc.)
- User specified name may contain system environment variables
Info Directory within <SANDBOX_ROOT> could be a link to any other existing directory. It allows to use directories from the outside of sandbox to be used. (Please do this responsible - potential risk of data lost if an option "Clean up sandbox" or "Delete sandbox" is selected.
- Delete sandbox
- Values: TRUE/FALSE
- Determines if sandbox dir should be cleared:
- when actor finishes (in case if lifetime is set to "Actor execution")
- when workflow finishes in case if lifetime is set to "Workflow execution")
- Default value: TRUE
'Dummy' actors
When porting a workflow to a new platform, or to a new data-version, it often happens that some subset of the actors are not immediately available in the new environment. Rather than build a new workflow with these actors removed, and then have to re-build the workflow as and when actors become available, it would be good if a tool or procedure were available to temporarily replace the missing actors with a generic dummy actor which would:
- act as if had the same number and types of input and output ports as the missing actor
- stop gracefully if ever activated
FC2K settings
Actor generation:
- user will not have to provide library containing physics code (but (s)he may to)
- all other actor data has to be specified (as it were a "regular" actor)
- no C/F wrappers will be generated (only Java code)
Runtime actions:
- user code will be not called (actually eferything will be handled by Java actor, without calling wrappers, etc, etc)
- output values: default (primitive types), empty arrays, NULLs (IDSes)
- diagnostic info will be returned : (status: ERROR, msg: "Actor <name> should not be called")
Replacing by "regular" actor:
- User opens FC2K actor.xml project
- Checkbox "Create 'dummy' actor" should be unchecked
- User specifies libraries with physics code
- regenerate an actor
- Fully functional "regular" actor is crreated