Skip to content

Commit

Permalink
Updates based on the new release of COMPSs 2.3 and changes to the con…
Browse files Browse the repository at this point in the history
…figs provided by the VRE
  • Loading branch information
markmcdowall committed Jul 12, 2018
1 parent eafb674 commit e598884
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 1 deletion.
9 changes: 8 additions & 1 deletion docs/coding_standards.rst
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Language and Versions
---------------------

- Python 2.7
- Python 3.5
- Python 3.6

Installation Method
-------------------
Expand Down Expand Up @@ -89,9 +89,13 @@ git repository should include:
<module>/
__init__.py
...
scripts/
travis/
<travis_test_scripts>.sh
tests/
data/
test_<function_name>.py
.travisci.yml
LICENSE
README.md
requirements.txt
Expand Down Expand Up @@ -250,6 +254,9 @@ that the environment is clean ready for the next test case to run. This could
mean that some files will get generated multiple times, but these should be
smalls sample datasets.

To avoid the use of too many datasets and provide function level testing Mock
should be used.

The following options should be used to test code:

.. code-block:: none
Expand Down
10 changes: 10 additions & 0 deletions docs/howto/howto_config.rst
Original file line number Diff line number Diff line change
Expand Up @@ -186,9 +186,17 @@ Defines the configurations required for by the pipeline including parameters tha
"name": "project",
"value": "run001"
},
{
"name": "execution",
"value": "/../run001"
},
{
"name": "description",
"value": null
},
{
"name": "<tool_argument>"
"value": "<value_from_form>"
}
],
"output_files": [
Expand All @@ -211,6 +219,8 @@ Defines the configurations required for by the pipeline including parameters tha
]
}
In the arguments there are 2 sets (project and execution) that will always be present and are provided by the VRE at the point of submission of the to the tool. These are the name of the project that has been given in the VRE and is defined by the user. The second is the execution path, this is the location for where the input files are located and can be used as the working directory for the tool. The other parameters in the arguments list are from form elements based on what parameters the tool requires from the user at run time.


input_file_metadata.json
^^^^^^^^^^^^^^^^^^^^^^^^
Expand Down

0 comments on commit e598884

Please sign in to comment.