Incorporate ChannelWorm2 into Docker
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 244
- PR merge metrics
- No merged PRs in 30d
Description
We should figure out what the aims are of having ChannelWorm2 as part of this image. As it stands, ChannelWorm2 is a standalone project with static data and some code. Having it as part of the Docker image may be useful so that people have the data and the parameter fitting scripts to work with, but otherwise, it is not directly needed for producing simulation output.
@slarson @rgerkin @mwatts15 @pgleeson
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the repository's main Dockerfile and determine the intended role of ChannelWorm2 in the image. Clarify whether the image should include its static data and parameter-fitting scripts, then define completion around an agreed purpose and corresponding image contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100