Separate repo for Dashboard?

Open
#21 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data-visualization

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.

Description

dashboard

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.

Dominant language
Python
Stars
31
Forks
2
Avg merge
4d 18h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Simulation-Decomposition/simdec-python

All issues in Simulation-Decomposition/simdec-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.