add: Documentation of summer project with transformer jet tagger example notebook - #79
Merged
Merged
Conversation
nastiapetrovych
self-requested a review
September 2, 2026 10:18
nastiapetrovych
added
the
documentation
Collaborator
|
Thanks a lot, @semi-dlc , amazing job:) |
nastiapetrovych
approved these changes
Sep 2, 2026
Collaborator
|
@semi-dlc This should be merged to dev instead of main, otherwise good. |
semi-dlc
marked this pull request as draft
September 7, 2026 22:14
semi-dlc
marked this pull request as ready for review
September 7, 2026 22:24
Author
|
I apologize for the delay, the base branch is |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Big notebook that will take long to run and yields a bunch of variants of the transformer jet-tagger that I have been working on this summer with different compression methods.
Reduce batch size if the GPUs run out of memory. I use 47 GB H100 which is sufficient. Reduce amount of training data to 100k if fast results are necessary. The performance does not improve that much.
More infos: (Presentation 1), (Presentation 2), (Report).