Closed schlegelp closed 9 months ago
I agree, swc is not an appropriate file format for dotprops. The writer should throw an error if dotprops are given and there shouldn't be a reader.
Dropped writing dotprops to swc with caba243b67ff4a1c942db3b7cb83a18c37bb4d2c.
Currently, when passing a
Dotprop
tonavis.write_swc
it will be converted into a skeleton by turning each point + tangent vector into a 2-point skeleton segment. When reading the file back usingnavis.read_swc
the user gets a skeleton which consists of thousands of disconnected fragments. That's obviously not ideal. In hindsight I don't know why I implemented it that way to be honest.I'm bringing this up because I had a student asking why their skeletons look funky and it transpired that they actually started out with Dotprops and then ended up with skeletons through
write_swc
->read_swc
.We could teach
navis.read_swc
to loadDotprops
but that feels convoluted. My first hunch is to just disallowDotprops
forwrite_swc
- maybe with a message that points users towrite_nrrd
orwrite_parqet
. Thoughts @clbarnes?