Hi,
I am working with v4.11 and recently became aware that v4.11 has changed the default coordinate system (RAS -> LPS). Wondering if there will be an option in settings for the user to select their preferred coordinate system? Most of our workflows and projects are using RAS system from v4.10.
Thank you,
Greydon
Sorry for not noticing this post until now (it was added to a developer resource subcategory, which is not monitored). This page should help: https://www.slicer.org/wiki/Documentation/Nightly/Developers/Tutorials/MigrationGuide/Slicer#Slicer_5.0:_Models_are_saved_in_LPS_coordinate_system_by_default. If you have any remaining questions then let us know.
Thanks @Greydon_Gilmore for posting and @lassoan for your comments!
Up until v4.10.2, RAS has been the default output coordinate system which is what our original markup placement protocol was developed on. We started noticing issues when placements in v4.11 were displayed in versions < 4.11. That’s what led us to find this coordinate system change in markup files.
As a short term solution, we have made it pretty clear to our user base to only use up to v4.10.2 for placements.
The better solution would be to update our validator to perform more detailed checks of the header for the version and coordinate system. We created an issue for our project here: https://github.com/afids/afids-validator/issues/72
Is there a rough timeline for a stable version of Slicer v5.0 so our team can plan accordingly?
Note: Our Markup files encodes details about the L and R sides of the coordinate space (based on the location of anatomical features in the brain), which could be useful for migration test cases.
Slicer can read scenes created by previous software versions, but it is not feasible to make the Slicer compatible with all data created in future versions of the software. This means that you are not forced to upgrade your software, but if you do, then you may not be able to go back.
I would recommend to ask your users to use a specific Slicer version: either Slicer-4.10.2 or a selected Slicer-4.11.x release (you can get a download link by specifying a date or revision as described here).
We will release Slicer-5 when these issues are completed: https://github.com/Slicer/Slicer/milestone/1. It is difficult to estimate when this will happen, but hopefully within 1-2 months. This should not be a blocking point, as Since-4.11 releases are generally very stable, so you can standardize on any of them if you want to take advantage of some new features before Slicer-5 is officially released.