Adam Tyson
Adam Tyson
https://elifesciences.org/articles/87029 From a glance it looks v high quality.
http://www.3dbar.org:8080 looks to be a nice resource with many atlases already in a standardised format. There should be something useful we can do with these atlases, or move towards a...
We already have `kim_dev_...`, but we should add all the different developmental stages now they've been released (and maybe rename them). Ideally we would have one script that packages them...
I think each set of meshes is consistent, but they are scaled incorrectly, so they don't play nicely with external data.
At this line, the atlas name uses the first resolution value: https://github.com/brainglobe/bg-atlasgen/blob/f944baaf69004aca270c29dee50592369969db72/bg_atlasgen/wrapup.py#L111 This isn't particularly useful for non-isotropic atlases, but I'm not sure what would be better.
`.obj` works well, but the `mesh` directories can get large. Using newer formats could improve this a lot. [Draco](https://google.github.io/draco/) looks promising.
This issue tracks the packaging side of https://github.com/brainglobe/bg-atlasapi/issues/141.
Based on [this post](https://community.brain-map.org/t/2022-ccfv3-mouse-atlas/2287) it seems that there are updated versions of the annotations. Should we be releasing a new version of the atlas (and downsampling ourselves)?
Not sure if this is an error with the atlas, my machine or the plugin, but I noticed that loading all the `kim_dev` atlases cause an error. Full traceback ```...