Hi there lovely scientific nerdi comunity! Love you all!
Im a teacher, and one of the modules I use to teach for medical institutions such hospitals, clinics and i+d+i+i …
Im writing this post cause I think that, in software development, we must respect the hierarchy “gestural-input-peripherals” over any other “actiones-functions”… I mean, if you pan-rotate-zoom whith any mouse, button, shortcut… it must not be envolved in any other action, even if you can “block” some actions just no to modify your work.
I mean: if you do “something” naturally with your mouse just to orbit around… that input should NOT be involved in any other actions.
When you design using the Baffle Planner module, if you press the middle mouse button, over your desing, the entire design () is transformed, “spatialy moved”… and using the middle mouse button must only be used to orbit around your 3d scene.
I mean, we should not “overwrite” actiones that get us the wrong output and make the users confuse on how to use the tools.
I hope it make sense.
Love you all,keep up the suuuuuper good work, Im a fan, and if you want to come to Argentina, Ill make you “Asado” hahaha (not kiding, you are welcome, will be an honour)
I guess you accidentally moved markup points by middle-button-click-and-drag. In the long term, we’ll change markup interactions so that you need to first click to select and then you can drag the selected markup. What you can do now is to enable undo/redo so that you can undo any unintended changes. You can also remap interaction events on a markup by a few lines of python script to disable moving by middle-button-click-and-drag.
Great, thanks a lot Andras.
Sorry to bother, but I cant find where exactly can I enable undo/redo.
I know I can lock the contour points, and that is really helpful.
Thanks again.
See how to enable undo here:
@Sunderlandkyl @jcfr @pieper @muratmaga what do you think about enabling undo/redo by default in Slicer for markups?
Yes, I’ve always wanted undo/redo as a first class feature. I think if we have solid testing we can catch and fix any of the event issues that have always plagued this feature in the past.
Thanks a lot Andras!
I wish I could help, but I think I can’t, cause every month a new batch of students come to my classes to learn segmentation, and, sadly, I can’t use a custom 3dSlicer, cause I explain the basics starting from “absolute zero”, like configuration (like basic design things as orthographic projection vs perspective) and how to download and install extensions…or how to avoid colors and terminology so they can name their segments the way they need (cause we cut and duplicate and things like that)…
But… I don’t know… what can I do to help?
Providing feedback and describing your perspective of using Slicer helps a lot.
With robust and efficient node copy (deep and shallow) used and thoroughly tested in sequences and scene views (thanks to @Sunderlandkyl, we can have robust undo/redo. It will surely need some fixes and we will need to introduce it step-by-step (starting with a markups and maybe transforms).
Node serialization to json and fast background saving of bulk data (WIP by @Davide_Punzo) is also a promising avenue to implement continuous scene saving and therefore undo/redo.
with the recent changes, this should not be problem at all. Please review the tutorial here. Tutorials/Segmentation/colors-and-terms at main · SlicerMorph/Tutorials · GitHub
It is designed exactly to overcome the issues you describe, particularly with students. You need to use it with a Slicer preview dated after late March…
Cool! Ill read it.
Thanks!
That could be extremely awesome!
Ill try to help if I can.
Right now, I’m trying to collect errors from DentalSegmentator and TotalSegmentator, cause 2/10 of my students have different issues, I hope someday I’ll be ready to send you “a list” of errors and “solutions”.
i.e. a few weeks ago, one of my students had a special character in her Windows username, and TotalSegmentator couldn’t finish the segmentation properly… weird right? Things like that, and a few combinations of GPU Drivers + CUDA versions + PyTorch versions… (I know I shouldn’t write it here, right now, because I can fail, but I’ll try)…
I think you sent it to me, can’t remember exactly when… or why…but it doesn’t have much to do with my work, and the work of my students.
Anyway, it is precious information, because someday it will be necessary to work within an institution and its PAKs… Thanks for sharing, hope someday, someone around me, need it.
What I do is just simply cut and duplicate parts of various segments, to make them 3d printable, looking for simulators and practice models for surgeons, biomedical engineers, teachers and researchers, while I teach the basics on how to use 3dSlicer, so then they can, for example, watch the Kitware YouTube channel and understand how to do things with their video tutorials (super fast, for people that already know how to use 3dSlicer)…
I’ve learned a lot from Sonia Pujol’s publications, like ten years ago, but know we work, “almost all the time” whit voxels instead of polygons, and things have changed through time.
My main goal, as a teacher, is to lend a hand to use the Segment Editor (nowadays) the way you need it to be, just to create 3d models from medical imaging and use them for any purpose, like pieces of human parts to create customized implants or physical 3d printed practice models that day by day become increasingly useful here in Latin America.
My students are pretty interesting people, the best of the best, always looking for methods they can use to make the patients happy, resilient, and mitigate their fear or stress. I’m so lucky to teach them the use of this tools, and luckier talking to you directly, you always provide material and resources to make our lives vivid and joyful.
I’m happy to help in anything you need.
Thanks for your time, I mean it.