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.
...
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.
...
where syn123 is the synID to the MaterializedView created in Step 3. Optionally include aliases and/or clauses to the query if desired, e.g. exclude certain columns such as archived_writeup. Click on the Preview button in the top-left corner to preview the prospective leaderboard, e.g.
...
| Info |
|---|
When using this widget, aliases must be assigned with the quotation marks ( |
6. Click Save once you are satisfied with the final leaderboard.
...