Atlas based reconstructions leverage volumetric datasets (e.g. orientation field, density datasets, etc.) that are all registered to the same reference datasets (annotation volume, region hierarchy) and within the same coordinate framework.
So, the user has to load the reference datasets to be able to filter regions and/or manipulate other files for each step of the reconstruction. Currently, the annotations and hierarchy are only loaded/accessible when creating the topology and need to be reloaded afterwards during placement or even connectivity.
Other datasets such as the orientation or the depth fields can also be used during placement and connectivity strategies. It would be easier for the user to only define them once in the configuration.
Atlas based reconstructions leverage volumetric datasets (e.g. orientation field, density datasets, etc.) that are all registered to the same
reference datasets(annotation volume, region hierarchy) and within the same coordinate framework.So, the user has to load the
reference datasetsto be able to filter regions and/or manipulate other files for each step of the reconstruction. Currently, the annotations and hierarchy are only loaded/accessible when creating the topology and need to be reloaded afterwards during placement or even connectivity. Other datasets such as the orientation or the depth fields can also be used during placement and connectivity strategies. It would be easier for the user to only define them once in the configuration.