v111 spatial units in nm --> too large numbers for data type store as microns

Closed
  • Is something wrong?
#75 0 comments 0 reactions 0 assignees View on GitHub

@reneyagmur is already working on this.

Since Nov 3, 2026.

  • #87 by @reneyagmur — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
data

Research direction

The issue names no files, tests, or entry points. Start by locating where v111 spatial units are represented and stored, then check how their current units and numeric values are defined. Done should mean the stored values use microns and no longer exceed the relevant data type's range; the issue does not specify validation or tests.

Written by the indexing model from the issue text.

Description

etl

This issue has no description.

Dominant language
Python
Stars
4
Forks
1
Avg merge
2d 6h
Merged PRs (30d)
7

Getting set up

Open in Codespaces

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

  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 AllenInstitute/ConnectsCommonConnectivity

All issues in AllenInstitute/ConnectsCommonConnectivity

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.