AllenInstitute / AllenInstitute/ConnectsCommonConnectivity
Embedding coordinates schema (UMAP/tSNE), distinct from spatial
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Question: computed embeddings must not be conflated with anatomical coordinates (the BKP ingest template doesn't distinguish them; we should). origin/u/morriscb/abcAtlasAccessDraftSchema drafts EmbeddingSet + EmbeddingMethod (UMAP/TSNE/PCA/MDS/OTHER). Align with / adopt that draft? Coordinate with @morriscb.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the BKP ingest template and the draft at origin/u/morriscb/abcAtlasAccessDraftSchema, focusing on EmbeddingSet and EmbeddingMethod. Coordinate with @morriscb to decide whether to align with or adopt that draft. Done means the schema distinguishes computed embeddings from anatomical coordinates and the UMAP, TSNE, PCA, MDS, and OTHER methods are resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100