Request: limiting depth and drawn elements
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- data-visualization
Research direction
The payload names no source files, tests or entry points, so the first step is to find the tree view and diagram rendering code in the repository and the standard filter conditions the issue refers to. The request needs a design decision first: how depth limits and per-element include or exclude selection should be expressed, and whether a non-standard extension is acceptable. The linked syside depth attribute is the reference point. Done means a maintainer-agreed design, not a patch.
Written by the indexing model from the issue text.
Description
Currently tree view shows full containment tree of exposed elements. Filter conditions as per standard and pilot implementation affect only root nodes and as I understood are quite limited (e.g. cannot express depth).
Yet, when there are more than two levels of decomposition, tree diagram and interconnection diagrams become huge, especially when each element has some metadata. So, to efficiently visualise large model there should be mechanism to limit depth of the tree to be rendered and individually select or blacklist shown elements.
Currently I did not find such function in the spec. It looks like non-standard library is needed for that with appropriate tool support.
Some search shows that syside uses attribute depth for that https://docs.sensmetry.com/extension/diagram-views/configuring/#extension-sysml-views-depth, but in my opinion finer control is often needed.
- Dominant language
- Go
- Stars
- 39
- Forks
- 12
- Avg merge
- 14h 14m
- Merged PRs (30d)
- 759
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Open-MBEE/OpenSysML
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Open-MBEE/OpenSysML#1199 · 5 comments ·
Maintainers usually reply within 1 day
-
bug spec compliance
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Open-MBEE/OpenSysML#1125 · 3 comments ·
Maintainers usually reply within 1 day
-
help wanted question
Difficulty 5/5 Over a week Newbie friendliness 25/100
Open-MBEE/OpenSysML#987 · 11 comments ·
Maintainers usually reply within 1 day
All issues in Open-MBEE/OpenSysML
Similar issues
-
agent-butler-finding chore
Difficulty 1/5 Under an hour Newbie friendliness 90/100
jordansmall/spindrift#5575 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JakeChampion/lang#12684 ·
Maintainers usually reply within 1 day
-
goose sub-agent runs are never indexed: blame finds no session for any file a `delegate` child wroteOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
C-bug O-community X-blathers-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cockroachdb/cockroach#176150 · 1 comment ·
Maintainers usually reply within 12 days
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
wakatime/wakatime-cli#1649 ·
Maintainers usually reply within 1 day