Duckietown Challenges | Home | Challenges | Submissions |
multi step, with IPFS support
These are the metrics defined:
passed-step1
1 if the submission passed the first step.
passed-step2
1 if the submission passed the second step.
No dependencies
At the beginning execute step step1
.
If step step1
has result success, then execute step step2
.
If step step1
has result failed, then declare the submission FAILED
.
If step step1
has result error, then declare the submission ERROR
.
If step step2
has result success, then declare the submission SUCCESS
.
If step step2
has result failed, then declare the submission FAILED
.
If step step2
has result error, then declare the submission ERROR
.
step1
Timeout 100.0
In this first step, we run the container step1-evaluator
and the
solution container.
This is the Docker Compose configuration skeleton:
version: '3' services: solution: image: SUBMISSION_CONTAINER environment: {} step1-evaluator: image: docker.io/andreacensi/duckietown-challenges@sha256:6ec0f198e113cb366dc24bb8e8706f572a76877380297f31bd288a7481bddde3 environment: {}
The text SUBMISSION_CONTAINER
will be replaced with the user containter.
IPFS mountpoint /ipfs available | 1 |
step2
Timeout 100.0
In the second step, we only run a second container called step2-evaluator
.
This is the Docker Compose configuration skeleton:
version: '3' services: step2-evaluator: image: docker.io/andreacensi/duckietown-challenges@sha256:6ec0f198e113cb366dc24bb8e8706f572a76877380297f31bd288a7481bddde3 environment: {}
The text SUBMISSION_CONTAINER
will be replaced with the user containter.
IPFS mountpoint /ipfs available | 1 |