Add true DAG support to the clustering schema
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- jupyter-notebook
- Domain
- documentation
Research direction
Read the ClusterHierarchy and Cluster schema documentation and check how they describe parent relationships and DAG support. Update the documentation to match the supported schema, including whether a cluster can have multiple parents; done means the documented behavior is consistent with the singular Cluster.parent field and unique (hierarchy_id, id) key.
Written by the indexing model from the issue text.
Description
ClusterHierarchy is documented as supporting trees or DAGs, but Cluster.parent is singular and cluster rows are uniquely keyed by (hierarchy_id, id). A cluster label shared by multiple parents therefore cannot be represented without duplicating and renaming the node. Though currently there is no such validation.
This occurs in V1DD, where the same cluster label can appear under several subclasses. (Class -> subclass -> cluster)
Correct the schema documentation if DAG support remains unsupported.
- 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
-
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
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in AllenInstitute/ConnectsCommonConnectivity
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Imbad0202/academic-research-skills#1039 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
alexgreensh/token-optimizer#297 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
superdesigndev/treg#1343 ·
Maintainers usually reply within 1 day
-
GitHub handle should allow underscoresPossibly taken @PrakarshSrivastav claimed this today. Openbug good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nf-core/tools#4581 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue test
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ANCORATE/EncryptHome#8 ·