At the end of a typical challenge on Synapse, all participating users and teams will be asked to provide a writeup on their submission(s). The writeup should include details such as methodologies, external data sources (if any), and source code and/or Docker images. Participants and teams will submit their writeups as Synapse projects.
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Get the 7-digit Evaluation evaluation ID as it will later be needed in Step 9. |
...
Line Number | TODO | Motivation |
|---|---|---|
31 | Update | This will identify the Synapse team that are the organizers for the Challengechallenge. |
45 | Update | This will check that the participant/team did not submit the Challenge challenge site as their writeup. |
47-50 | Uncomment. | Lines 49-50 checks that the writeup Project project is AT LEAST accessible to the Organizers organizers team (as defined by Line 31). Lines 47-48 checks the writeup is accessible to anyone on the web. |
...
Test Case | Workflow Configurations | Expected Outcome |
|---|---|---|
Submitting the Challenge site |
| |
Submitting a private Synapse project | Lines 49-50 is used (writeup should be accessible to the Organizers team) |
|
Submitting a private Synapse project | Lines 47-48 is used (writeup should be publicly accessible) |
|
Submitting a Private Synapse project that is shared with the Organizers team | Lines 49-50 is used (writeup should be accessible to the Organizers team) |
|
Submitting a Private Synapse project that is shared with the Organizers team | Lines 47-48 is used (writeup should be publicly accessible) |
|
Submitting a public Synapse project | Lines 47-48 and/or lines 49-50 are used |
|
Once you are satisfied that the writeup workflow is to your expectations, remember to open the queue to the challenge participants!
You can do so by updating its sharing settings so that the participants team has Can submit permissions.
...