Skip to content

Commit 9c36f6e

Browse files
authored
[feat] readme updates (#6)
* clarify instructions in readme * add more details to the readme
1 parent 9901de1 commit 9c36f6e

File tree

2 files changed

+63
-5
lines changed

2 files changed

+63
-5
lines changed

README.md

Lines changed: 62 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,65 @@
1-
# Data-to-Model Workflow Template
1+
<div align="center">
2+
<h1>
3+
Data-to-Model Challenge Infrastructure Template
4+
</h1>
25

3-
This repository provides a ready-to-use template for setting up a
4-
data2model workflow to be used with a challenge hosted on Synapse.
6+
<h3>
7+
Ready-to-use workflow template for evaluating prediction files submitted on
8+
<a href="https://www.synapse.org" title="Synapse.org">Synapse.org</a>
9+
</h3>
510

6-
→ See also: [SynapseWorkflowOrchestrator](https://github.com/Sage-Bionetworks/SynapseWorkflowOrchestrator)
11+
<br/>
712

13+
<img
14+
alt="GitHub release (latest by date)"
15+
src="https://img.shields.io/github/release/sage-bionetworks-challenges/data-to-model-challenge-workflow?label=latest%20release&display_name=release&style=flat-square">
16+
<img
17+
alt="GitHub Release Date"
18+
src="https://img.shields.io/github/release-date/sage-bionetworks-challenges/data-to-model-challenge-workflow?style=flat-square&color=green">
19+
<img
20+
alt="GitHub"
21+
src="https://img.shields.io/github/license/sage-bionetworks-challenges/data-to-model-challenge-workflow?style=flat-square&color=orange">
22+
</div>
23+
24+
25+
### 💡 Should You Use This Template?
26+
27+
The data-to-model (d2m) workflow is typically used when participants are
28+
able to download the challenge data, train their model locally, and submit
29+
their predictions file for evaluation against the hidden groundtruth data.
30+
31+
### 🚀 Quick Start
32+
33+
* **Customize evaluation logic:** modify the scoring and validation scripts
34+
within the `evaluation` folder
35+
* **Configure workflow:** adapt `workflow.cwl` (and `writeup-workflow.cwl`,
36+
if applicable) to define the inputs and steps specific to your challenge
37+
* **Test your changes:** use [`cwltool`](https://github.com/common-workflow-language/cwltool)
38+
to test your CWL scripts within the `steps` folder
39+
40+
---
41+
42+
### Technical Details & Resources
43+
44+
#### Repository structure
45+
46+
This template provides all necessary components for a full challenge pipeline:
47+
48+
```
49+
.
50+
├── evaluation // core scoring and validation scripts
51+
├── README.md
52+
├── steps // individual CWL scripts (called by the main workflow CWL)
53+
├── workflow.cwl // CWL workflow for evaluating submissions
54+
└── writeup-workflow.cwl // CWL workflow to validate and archive writeup submissions
55+
```
56+
57+
#### Resource docs
58+
59+
This workflow uses CWL, Docker, and the SynapseWorkflowOrchestrator to run
60+
the challenge pipeline. For more information on how to utilize these tools,
61+
see their docs below:
62+
63+
* CWL: https://www.commonwl.org/user_guide/
64+
* Docker: https://docs.docker.com/get-started/
65+
* SynapseWorkflowOrchestrator: https://github.com/Sage-Bionetworks/SynapseWorkflowOrchestrator

evaluation/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,4 @@ Once your changes are ready, create a new release in your repo. This will trigge
66
the action to build and deploy this Docker image into your repo as a package.
77

88
Final steps would be to copy the image name into your "validate.cwl" and "score.cwl"
9-
under hints.DockerRequirement.dockerPull.
9+
scripts under `hints.DockerRequirement.dockerPull`.

0 commit comments

Comments
 (0)