Simulation-Decomposition / Simulation-Decomposition/simdec-python
Separate repo for Dashboard?
Open
Nobody has claimed this yet.
dashboard
- Dominant language
- Python
- Stars
- 31
- Forks
- 2
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 2
Description
Should we separate the dashboard from SimDec-Python itself?
As we discuss adding more capabilities such as a sampler dashboard or a more general SA app, maybe it would make more sense to cleanly separate the code and scope.
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. Review the repository structure and the dashboard's current scope, then use the issue discussion to determine whether a separate repository is warranted; done means documenting and implementing an agreed repository boundary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100