Skip to content
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

Plotting support #43

Closed
graeme-a-stewart opened this issue Apr 19, 2024 · 3 comments · Fixed by #46
Closed

Plotting support #43

graeme-a-stewart opened this issue Apr 19, 2024 · 3 comments · Fixed by #46
Assignees
Labels
enhancement New feature or request

Comments

@graeme-a-stewart
Copy link
Member

Based on the new ClusterSequence return type, develop plotting routines to visualise the output of the reconstruction

@graeme-a-stewart graeme-a-stewart added the enhancement New feature or request label Apr 19, 2024
@gojakuch gojakuch self-assigned this May 8, 2024
@gojakuch
Copy link
Collaborator

gojakuch commented May 8, 2024

hi, so is this issue on the branch main or on the cluster-sequence? or, to reformulate the question, should I work with what's on main or cluster-sequence?

@graeme-a-stewart
Copy link
Member Author

Hi @gojakuch. The cluster-sequence branch was rebased and merged, so it shouldn't have been hanging around - I have deleted it now.

My current development branch is inclusive-jets, which I have pushed to GitHb now, so you can see it. There are some changes in the pipeline to ClusterSequence.jl, adding algorithm and strategy information - plus the algorithm and strategy are encoded now as named enums (with the EmumX package). However, I don't think that changes anything w.r.t. the core visualisation task, which would use ClusterSequence.jets and ClusterSequence.history.

Summary: it should be ok to attack this on main!

My hope is to merge the inclusive-jets branch soon - it's in mostly working, but there are some differences with FastJet for the $d_{ij}$ cuts that I need to understand before it's really good to go (the $n_{jets}$ cut seems to work just fine). That said, next week I am at a workshop all week, so time is pretty limited for the rest of May 😅.

@graeme-a-stewart
Copy link
Member Author

Thanks so much @gojakuch and to @Moelf for helping! (I was completely overwhelmed last week at the HSF workshop)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants