Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Dimension Correction to ReconstructedCell entity #360

Open
jmbudd opened this issue Apr 25, 2020 · 1 comment
Open

Add Dimension Correction to ReconstructedCell entity #360

jmbudd opened this issue Apr 25, 2020 · 1 comment
Assignees

Comments

@jmbudd
Copy link

jmbudd commented Apr 25, 2020

In the process of applying Neuroshapes In Vitro Slice Neuron Morphology Reconstruction schema to the curation of combined anatomical and electrophysiolgical slice data from mouse hippocampus, I encountered a number of issues. Since these issues may well arise during the curation of similar datasets for other labs, I thought it might be useful to share them here. I have created a separate ticket for each issue. (This introductory paragraph is repeated in each.)

During tissue processing and recording, shrinkage (xy-axis) and compression (z-axis) dimensional changes may occur to the slice that need to be corrected for in order to provide a more accurate geometric representation of a neuron's morphology. However, correction may have be applied to the reconstruction file prior to curation. Without specific instructions, it is ambiguous whether the file represents raw or corrected geometry. Moreover, the ReconstructedCell entity does not include information about what estimated xy- and z-axis dimensional changes occurred should an uncorrected (raw) morphology file be supplied.

To address this issue, I extended the ReconstructedCell entity to incorporate this information, i.e. in yaml format:

ReconstructedCell:
  protocol:
  person:
  date:
  name:
  mType:
  axonProjection:
  compressionCorrection:         <---- <float>
  shrinkageCorrection:           <---- <float>
  geometryCorrected:             <---- <bool>
@Jay-sanjay
Copy link

hello I will work on the issue can you provide the necessary inks to this problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants