ImperialCollegeLondon / ImperialCollegeLondon/SWMManywhere
non-validation design metrics
Open
Nobody has claimed this yet.
feature
metric
- Dominant language
- Python
- Stars
- 51
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Adding global feasibility, cost and depth to metrics would be easy and sensible.
Contributor guide
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
No files, tests, or entry points are named in the issue. First locate the existing metrics implementation and review how validation metrics are defined before deciding how global feasibility, cost, and depth should be specified. Done should include an agreed design and those three metrics being available in the relevant metrics output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100