-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BoneReconstructionPlanner's virtual surgical planning is now tested #68
Comments
The test passes if it does not raise an exception. |
This test is certainly very useful for catching some me errors. It is promising for automatically generating tutorials, but for that it would be important to see mouse pointer and click positions. It would be also better to see the text near the bottom instead in the center of the screen. |
Thank you for the feedback @lassoan
Could you refer me to a code example that does this? How to do it window-size independent? How to create the test data?
I agree, I'll try to do that |
I don't have code example, but you can display a widget (such as QIcon) outside the layout to indicate the mouse position. You can do a small animation (change the size, color, flash it, etc) to indicate clicking. You could generate smooth mouse trajectory between click positions to simulate somewhat realistic mouse motion. Screen capture module can be used to capture screenshots and put them into a mp4 video. We plan to develop something like this for the Slicer for Latin America project, for automatic creation of multi-lingual training materials (videos, slide shows, documentation pages). |
@lassoan could you give feedback about it?
SlicerBoneReconstructionPlanner/BoneReconstructionPlanner/BoneReconstructionPlanner.py
Lines 4140 to 4221 in 359f8eb
Does reaching the end of the test section_SimulateAndImproveMandibleReconstruction means that the test should be considered passed? Some assertions on numeric results could be added like fibula-bone-pieces meshes number of points, what do you think?
Here is a video of the workflow tests implemented till now:
2022-12-15.16-05-54.mp4
Regarding using it as instructive material:
developer-mode=True
and restart Slicer so the reload&test button is visible?The text was updated successfully, but these errors were encountered: