A user passable flag for which spatial/embedding spaces/views/plots should be viewed by default in Connectivity Viewer
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- data-visualization
Research direction
The issue names no file, test or entry point; it proposes a per-space isViewedByDefault flag in the sidecar metadata for the Connectivity Viewer and asks how that flag should be scoped per project versus per reference space. Start by finding where the viewer reads space or plot metadata, and settle the design question in the thread (and in #49) before writing code. Done means a decided flag schema plus a working default view for the existing spaces.
Written by the indexing model from the issue text.
Description
CCM might need to carry information for Connectivity Explorer: we might need some sidecar information about which spaces should be "default" spaces to show.
so something like: so maybe each reference/embedding space should get a isViewedByDefault: True/False kind of flag?
BUT that flag should be project/dataset specific while reference spaces can be project agnostic.
something to detangle
also might be related to #49, since when the number of dimension will increase we will need a default view for it as well too or assume xy is the most desired
- Dominant language
- Python
- Stars
- 4
- Forks
- 1
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 8
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 AllenInstitute/ConnectsCommonConnectivity
-
enhancement io
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug documentation schema
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug schema
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Change PR templateOpendocumentation
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
enhancement schema
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
All issues in AllenInstitute/ConnectsCommonConnectivity
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pytest-dev/pyfakefs#1367 · 1 comment ·
Maintainers usually reply within 2 days
-
IFEvalG exclude_word_harder misses the keyword next to punctuation, at the start or end of the text, and in other letter casePossibly taken @damienen claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
allenai/open-instruct#2151 ·
Maintainers usually reply within 1 day
-
feat(plan): support convertorLabels and convertorAffinity in Plan resourcePossibly taken @AmenB claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
RedHatQE/openshift-python-wrapper#2849 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 25 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libnativeapi/nativeapi#21 ·