-
Notifications
You must be signed in to change notification settings - Fork 4
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
Views for cluster and track #48
Conversation
…feat/mc-reco-view
…feat/mc-reco-view
|
Hi @brauliorivas, for the cluster I would say Type, energy and position (for the cluster I would keep it split into x, y, and z) |
I thing what is proposed in the drawing is a good start, but if you find out that it is overly complex to have it this way, feel free to ditch it. Maybe horizontal ordering will be easier to implement? I would not spend too much time in searching for the best one at this point :) |
…ent objects/colors and its properties
I think we could also have the If it's possible we could also have an "interactive view" that starts from a list of e.g. |
Very nice feature. Definitely taking this into account. |
BEGINRELEASENOTES
Cluster
andTrack
collections now have a view for the visualizations.Cluster
has a relation with: otherCluster
s,MCParticle
, andRecoParticle
. Currently, only there are two views for the first two.tree
(because the current views work the same way e.g. MCParticle or ReconstructedParticle). That's why nowTrack
andCluster
do the same algorithm to be placed on eede. I've also assumed that when the view is to show anassociation
, it's shown vertically, just like on the previous PR (e.g. MCRecoAssociation). So the view forMCTrack
andMCCluster
associations are the same (each object placed vertically).Track
.ENDRELEASENOTES
Hey @tmadlener, @kjvbrt, what pattern/design/way would you like to show the view for relations between
Cluster
-RecoParticle
, andTrack
-RecoParticle
. I was thinking to do it like associations (vertically), but to show on the left side theRecoParticle
, and on the right side, a branch of relatedCluster
orTrack
(depending of the relation). Also, what information/properties should be displayed forTrack
andCluster
?(the same logic would apply for track)
Missing: I still haven't changed the colors/shape of the different objects (as discussed with mentors).
Note: I have to test this with other generated events (the test file doesn't have this data). But in theory, this should work fine.