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: README.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,9 @@ Our template supports both the "submit data" and "submit code" submission styles
13
13
<your code>
14
14
```
15
15
16
-
, where /solution/solution.csv is the output your algorithm generates on the provisional test set. The format of this file will be described in the challenge specification.
17
-
/code contains a dockerized version of your system that will be used to reproduce your results in a well defined, standardized way. This folder must contain a Dockerfile that will be used to build a docker container that will host your system during final testing. How you organize the rest of the contents of the /code folder is up to you, as long as it satisfies the requirements listed below in the Final testing section.
16
+
The /solution/solution.csv is the output your algorithm generates on the provisional test set. The format of this file will be described in the challenge specification.
17
+
18
+
The /code directory should contain a dockerized version of your system that will be used to reproduce your results in a well defined, standardized way. This folder must contain a Dockerfile that will be used to build a docker container that will host your system during final testing. How you organize the rest of the contents of the /code folder is up to you, as long as it satisfies the requirements listed below in the Final testing section.
18
19
19
20
#### Notes:
20
21
During provisional testing only your solution.csv file will be used for scoring, however the tester tool will verify that your submission file confirms to the required format. This means that at least the /code/Dockerfile must be present from day 1, even if it doesn't describe any meaningful system to be built. However, we recommend that you keep working on the dockerized version of your code as the challenge progresses, especially if you are at or close to a prize winning rank on the provisional leaderboard.
@@ -43,13 +44,13 @@ The tester tool will unpack your submission, and the
43
44
```
44
45
docker build -t <id> .
45
46
```
46
-
command will be used to build your docker image (the final \`.\` is significant), where <id> is your TopCoder handle.
47
+
command will be used to build your docker image (the final '.' is significant), where <id> is your TopCoder handle.
47
48
The build process must run out of the box, i.e. it should download and install all necessary 3rd party dependencies, either download from internet or copy from the unpacked submission all necessary external data files, your model files, etc.
48
49
Your container will be started by the
49
50
```
50
51
docker run -v <local_data_path>:/data:ro -v <local_writable_area_path>:/wdata -it <id>
51
52
```
52
-
command (single line), where the -v parameter mounts the contest\`s data to the container\`s /data folder. This means that all the raw contest data will be available for your container within the /data folder. Note that your container will have read only access to the /data folder. You can store large temporary files in the /wdata folder.
53
+
command (single line), where the -v parameter mounts the contest's data to the container's /data folder. This means that all the raw contest data will be available for your container within the /data folder. Note that your container will have read only access to the /data folder. You can store large temporary files in the /wdata folder.
53
54
54
55
To validate the template file supplied with this repo. You can execute the following command:
55
56
```
@@ -65,7 +66,7 @@ As its first step train.sh must delete the self-created models shipped with your
65
66
66
67
Some algorithms may not need any training at all. It is a valid option to leave train.sh empty, but the file must exist nevertheless.
67
68
68
-
Training should be possible to do with working with only the contest\`s own training data and publicly available external data. This means that this script should do all the preprocessing and training steps that are necessary to reproduce your complete training work flow.
69
+
Training should be possible to do with working with only the contest's own training data and publicly available external data. This means that this script should do all the preprocessing and training steps that are necessary to reproduce your complete training work flow.
69
70
70
71
A sample call to your training script (single line):
0 commit comments