Open h-mayorquin opened 1 month ago
Important discussion how does this fit into the considerations of #4 .
yes but the anatomomical coordinates table is in a separate repo here: https://github.com/bendichter/ndx-anatonical-localization
I think is even better if a different extension takes responability of specifying locations.
Reading the schema it seems that the current estimated_position_{x}_in_mm
would be a single column maping to an AnatomicalCoordinatesTable which is a dynamic table so that makes sense.
I also think that another good reason to decouple localization from here is that this extension can be used to store results from in-vitro experiments and the current {}_position_{x}_in_mm
do not really make sense for those cases.
From the introductory comment on #1.
I think this is a great idea for the reasons defended on #1 here
So I think that the
ChannelsTable
can be linked per-row to a newAnatomicalCoordinatesTable
and that would decouple and solve some of the problems that we have been discussing.One thing with this approach though is that the mapping between an anatomical site (a row of the
AnatomicalCoordinatesTable
) and aProbeInsertion
is not explicit but indirect in the current schema.