Andras Lasso

ExtraMarkups extension is the only one that is impacted. If it's a lot of work to keep `vtkMRMLMarkupsJson*` classes around (by making them call `vtkMRMLJson*` classes) then it is OK...

The extension needs to be compiled with Slicer stable and main branch, unless you confirm with the developer that he will maintain two separate branches.

@Punzo let's start to work towards integrating these changes! A specific reason is that @Sunderlandkyl would like to use the JSON read/write classes for volume rendering presets, but also in...

> sure I will do it on Monday. Perfect, thank you!

@Punzo Let's try to get this in before the new stable release. I see some merge conflicts. Could you fix those? I also see that it is still in draft...

This was tested in 3D Slicer, which uses the https://github.com/Keyn34/MOOSE/tree/SlicerMOOSE branch. I saw that there is a [commit that is related to the coordinate systems](https://github.com/Keyn34/MOOSE/commit/062ff24c16dd6a95bedf56e198d213495c22ce28), so maybe this fix is...

It's great that you could reproduce the issue, because it means it will be easy to find what makes the difference between the [main branch](https://github.com/ENHANCE-PET/MOOSE/tree/main) and the [Slicer branch](https://github.com/Keyn34/MOOSE/tree/SlicerMOOSE). Most...

This sounds great! I've tested the new models (in Slicer branch) and with the standard normalization to RAS everything works nicely (I used the nibabel function, but SimpleITK's reorientation should...

Great! To manage compatibility with Slicer-5.8, please create a `5.8` branch in https://github.com/Keyn34/MOOSE/tree/SlicerMOOSE and have the code version there that should be used with Slicer-5.8. If the branch is ready...

@Sunderlandkyl what do you think, would you have time to thoroughly review the binary labelmap flattening code correctness when some or all segments are empty (and build in safeguards to...