...
This section is intended to talk about the types of concepts that the Ontology needs to capture. We will break this into two parts: general framework concepts (e.g. result) and eAIRS specific (e.g. mesh). We don't anticipate any changes to the DatasetBean class that is provided as part edu.uiuc.ncsa.cet.bean plug-in.
General Framework Metadata
What we need to capture:
- Is this dataset a result or output dataset?
- Is this dataset an input dataset?
eAIRS Metadata
What we need to capture:
- Is this dataset an eAirs mesh?
- Is this dataset an eAirs input file
- Result files: coefhist.rlt, error.rlt, result.rlt, time.rlt, cp.rlt, force_com.rlt, result.vtk. We should capture enough information to know what each of these files represent as far as outputs.
Mime types of the files that are outputs from the eAIRS workflow
- .rlt
- .vtk
WorkflowBean & WorkflowStepBean
...
Code Block | ||||
---|---|---|---|---|
| ||||
<workflow-builder name="eAIRS-Single" experimentId="singleCFDWorkflow" eventLevel="DEBUG"> <!-- <global-resource>grid-abe.ncsa.teragrid.org</global-resource> --> <global-resource></global-resource> <scheduling> <profile name="batch"> <property name="submissionType"> <value>batch</value> </property> </profile> </scheduling> <execution> <profile name="mesh0"> <property name="RESULT_LOC"> <value>some-file-uri</value> </property> <property name="executable"> <value>some-file-uri</value> </property> <property name="meshType"> <value>some-file-uri</value> </property> <property name="inputParam"> <value>some-file-uri</value> </property> </profile> </execution> <graph> <execute name="compute0"> <scheduler-constraints>batch</scheduler-constraints> <execute-profiles>mesh0</execute-profiles> <payload>2DComp</payload> </execute> </graph> <scripts> <payload name="2DComp" type="elf"> <elf> <serial-scripts> <ogrescript> <echo message="Result location = file:${RESULT_LOC}/${service.job.name} result directory is file:${runtime.dir}/result, copy target is file:${RESULT_LOC}/${service.job.name}"/> <simple-process execution-dir="${runtime.dir}" out-file="cfd.out" > <command-line>${executable} -mesh ${meshType} -param ${inputParam}</command-line> <!-- <command-line>${runtime.dir}/2D_Comp-2.0 -mesh ${meshType} -param ${inputParam}</command-line> --> </simple-process> <mkdir> <uri>file:${RESULT_LOC}/${service.job.name}</uri> </mkdir> <copy sourceDir="file:${runtime.dir}/result" target="file:${RESULT_LOC}/${service.job.name}"/> </ogrescript> </serial-scripts> </elf> </payload> </scripts> </workflow-builder> |
Metadata Requirements
General Framework Metadata
What we need to capture:
- Is this dataset a result or output dataset?
- Is this dataset an input dataset?
eAIRS Metadata
What we need to capture:
- Is this dataset an eAirs mesh?
- Is this dataset an eAirs input file
- Result files: coefhist.rlt, error.rlt, result.rlt, time.rlt, cp.rlt, force_com.rlt, result.vtk. We should capture enough information to know what each of these files represent as far as outputs.
Mime types of the files that are outputs from the eAIRS workflow
- .rlt
- .vtk
Service Manager
...
RMI Service Registry View
...