You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support Geant4 nested geometry in YAPTIDE 3D View #2007
Things that came to mind while working on the design:
parenting one object to another. It would be good to be able to use drag n drop
adding new element - should we always add to top-level or as child of currently selected element?
As a child of currently selected element. It should work like directory/file explorer.
Do we need an object that is a parent of all objects on the scene, i.e environment where particles move?
Yes, we need a "World Volume", thats useful.
translating the whole hierarchy, i.e moving the Snowman all at once
removing the whole hierarchy, do we need to alert user that the action will remove all children as well?
Yes, even when removing certain level it would be nice to alert user that this will delete all children.
Is it also important to have reasonable selection mechanism: user selects an object in the 3D view, then a certain element from tree is selected and vice versa.
It would be nice to have option to duplicate given element (i.e. you create one eye for snowman and then duplicate and translate it to get a second one).
User should be able also to change order of elements at every level (i.e. first right eye, then left eye).
Think how to deal with trees with more than 10 levels. There is not so much space to the right of the 3D editor.
In JSROOT when I try to get to some leaves of the ATLAS detector geometry tree it looks ugly:
Most of the resources should be available as presentations or movies on youtube. I suspect you can get enough feeling of what other users may experience without installing these tools
Activity
kmichalikk commentedon Apr 18, 2025
Things that came to mind while working on the design:
grzanka commentedon Apr 18, 2025
Is it also important to have reasonable selection mechanism: user selects an object in the 3D view, then a certain element from tree is selected and vice versa.
It would be nice to have option to duplicate given element (i.e. you create one eye for snowman and then duplicate and translate it to get a second one).
User should be able also to change order of elements at every level (i.e. first right eye, then left eye).
grzanka commentedon Apr 18, 2025
Think how to deal with trees with more than 10 levels. There is not so much space to the right of the 3D editor.
In JSROOT when I try to get to some leaves of the ATLAS detector geometry tree it looks ugly:
https://root.cern.ch/js/latest/?file=https://root.cern/files/atlas.root&item=atlas;1&opt=dflt;black;dsize;vislvl4;zoom70
grzanka commentedon Apr 18, 2025
Another feature, but less priority. You select a node and the right click on it: "Display only this one"
Like here in JSROOT:
https://root.cern.ch/js/latest/?file=https://root.cern/files/cms.root&item=cms;1&opt=all;clipxyz;zoom70;macro:https://root.cern/files/cms_cmse.C
grzanka commentedon Apr 18, 2025
Another feature inspired by JSROOT: icon next to node with a symbol of sphere/box/cylinder or whatever the node is.
grzanka commentedon Apr 28, 2025
It would be worth as well to take a look at documentation/movies/screenshots of existing GUIs for other particle transport codes:
Most of the resources should be available as presentations or movies on youtube. I suspect you can get enough feeling of what other users may experience without installing these tools
There is also whole chapter on Visualisation in the Geant4 documentation:
https://geant4-userdoc.web.cern.ch/UsersGuides/ForApplicationDeveloper/html/Visualization/visualization.html