Amy M Morton

Hi all, just checking to see if there is any plan to remedy on windows? Thanks!

OK thank-you! Maybe then the suggested IDE should be switched to VSCode in the readme then?

VS Code successful- and you're right no explicit interpreter required. Thank-you! 

@BardiyaAk I think I have a handle on this - but need your input - emailing- you..

Note 1) When I examine the Transforms module, it appears that the 3D Slicer environment is very interconnected with anatomical specific directions. (LR, PA. IS). From my exposure to data...

TO DO: Documentation path forward: Many datasets uploaded and transferred via gdrive- but issues in documentaiont have been detected: https://github.com/BrownBiomechanics/Autoscoper/issues/129 [Sample data](https://github.com/BrownBiomechanics/Autoscoper/releases/tag/sample-data) included in AUtoscoper needs to be fully documented...

[legacy processing code](https://github.com/BrownBiomechanics/XGen_AutoscoperImageProcessing/tree/main/DCMGen) [WN00113 dataset](https://github.com/BrownBiomechanics/XGen_AutoscoperImageProcessing/tree/main/WN00113)

Thanks @davidelwyn When I load your data and apply the FemurDSX.tfm to the femur tiff: There is no applied image->world resolution, using the screen shot data above, the corrected spatial...

If you only modify the volume image spacing parameters, apply the Femur.tfm (rigid transform you sent) but *do not harden* The ijk to parent dir matrix is preserved... But your...

Hi @Spinexiang I'll take a closer look at your conversion code- but in the meantime, I would suggest visiting the [xmalab wiki](https://bitbucket.org/xromm/xmalab/src) We have attempted to fully document camera calibration...