You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/examples-in-five-safes-tes/5s-tes-messages.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,12 +8,12 @@ title: Five Safes TES messages
8
8
9
9
<divclass="tip">
10
10
11
-
The information included here is not essential, but can help you understand what's going under the hood of tools like [the wizards](examples-in-five-safes-tes/submission-layer-wizards)
11
+
The information included here is not essential, but can help you understand what's going under the hood of tools like [the wizards](/wizard-examples/submission-layer-wizards)
12
12
13
13
</div>
14
14
15
15
The reference documentation for TES messages specifies the standard for [creating a task](https://ga4gh.github.io/task-execution-schemas/docs/#tag/TaskService/operation/CreateTask).
16
-
5s-TES accepts this format, but some fields are treated differently because of how the [submission layer](examples-in-five-safes-tes#submission-layer) processes messages before they're sent to a TES engine.
16
+
5s-TES accepts this format, but some fields are treated differently because of how the [submission layer](/examples-in-five-safes-tes#submission-layer) processes messages before they're sent to a TES engine.
Five safes TES can run arbitrary containers, as long as the TRE can and will run them. This means that any analysis can be performed on a TRE.
9
+
10
+
In order to do this, you have to prepare a containerised version of the software you want to run. Typically, this may be a script such as python or R code, but can be any language or any tool. We do not currently support languages or tools which require external connections, such as to licence servers.
11
+
12
+
To containerise a script or tool in this way, the software must be executable from the command line. Arguments can be passed in at runtime using the TES messages. The command line arguments will be used in the `command` section of the `executors` in the TES message. A script will have access to input data passed in through the TES message (through mounted filepaths specified in the inputs, if any) and output data by writing files to the output path specified in the outputs section of the TES message. We recommend using /inputs and /outputs where possible.
13
+
14
+
The following is a list of environment variables which are used by Five Safes TES. This is primarily of interest as it outlines the names of the variables required for a connection string to the database, which is likely to be required to connect the container to the database. These variables will overwrite any that are passed through the TES message, as they are added by the submission layer.
15
+
```
16
+
"Any"
17
+
"CATALOG"
18
+
"SCHEMA"
19
+
"myapi2"
20
+
"myapikey"
21
+
"postgresDatabase"
22
+
"postgresPassword"
23
+
"postgresPort"
24
+
"postgresSchema"
25
+
"postgresServer"
26
+
"postgresUsername"
27
+
"submissionId"
28
+
"test"
29
+
"trinoPassword"
30
+
"trinoURL"
31
+
"trinoUsername"
32
+
```
33
+
34
+
Once your script or tool is ready, it must be built into a [docker container.](https://docs.docker.com/get-started/docker-concepts/building-images/writing-a-dockerfile/) The container also should be published so it can be accessed by the TRE. A simple way to publish to an accessible location is using [github.](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry?utm_source=chatgpt.com)
35
+
36
+
TREs can then approve and copy the container locally, to be usable on request (through a TES message). This means you can then submit a TES message to run the new image on the TRE.
These pages walk through the submission-layer wizards in the Five Safes TES web application: choosing a wizard, filling in TES details, and submitting a task.
10
+
11
+
Use the links in the sidebar for step-by-step topics, or start with [Submission layer wizards](wizard-examples/submission-layer-wizards).
Copy file name to clipboardExpand all lines: src/wizard-examples/Bunny visualisations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ title: Visualising Bunny Outputs
7
7
This tutorial can be run as a Jupyter notebook in the [5s-TES notebooks repository](https://github.com/Health-Informatics-UoN/5s-TES-notebooks/tree/main/OMOP-metadata), which also contains the utilities used to visualise OMOP metadata.
8
8
9
9
There are two examples of outputs from a Bunny distribution query included in the test data.
10
-
This kind of data can be obtained from Five Safes TES (5STES) by submitting a TES message, which can be created by using the [custom image wizard](submission-layer-wizards#custom-image):
10
+
This kind of data can be obtained from Five Safes TES (5STES) by submitting a TES message, which can be created by using the [custom image wizard](/wizard-examples/submission-layer-wizards#custom-image):
11
11

Copy file name to clipboardExpand all lines: src/wizard-examples/aggregating-statistics.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ The outputs from TES tasks can be easily used to calculate basic statistics.
12
12
This example will use summary statistics from a dataset in the OMOP common data model.
13
13
There is a container which, given a SQL query that filters an OMOP table by your criteria, will calculate the necessary summary statistics for your final analysis.
14
14
15
-
This example data was collected using the [Custom Image wizard](submission-layer-wizards#custom-image) in the submission layer with these settings changed from default:
15
+
This example data was collected using the [Custom Image wizard](/wizard-examples/submission-layer-wizards#custom-image) in the submission layer with these settings changed from default:
0 commit comments