Implement Autoregressive Multi-Track Finder - #25
Open
dhshin04 wants to merge 2 commits into
Open
Conversation
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
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.
Summary
models/AutoregressiveTrackFinder.py: inference-only iterative loop that reuses the existing single-track TrackFinder — predict one dimuon pair, remove its hits from the matrix, repeat until confidence drops below threshold ormax_itersis reached; only runs inference on still-active events each iterationeval_autoregressive.py: evaluation using Hungarian matching between predicted and GT pairs (in confidence order, not canonical order), with per-detector residuals, chi-squared, and TP/FN/FP per iterationscripts/eval_autoregressive.slurm: SLURM job for baseline inference + evaluation on the HPC clusterdata/multi_track/gen_residual_training.py(optional): generates single-track format training data from multi-track events with progressive hit removal, for fine-tuningscripts/train_autoregressive.slurm(optional): SLURM job to generate residual data, fine-tune, and evaluateNo new model architecture — the baseline reuses
track_finder_64.kerasas-is.Test plan
compute_confidenceandremove_predicted_hitsunit tests pass (uniform confidence ≈ 1/201, peaked ≈ 1.0, hit removal correct)eval_autoregressive.slurmon HPC with multi-track validation data; verify.npzoutput and evaluation metrics print correctlytrain_autoregressive.slurmto validate the fine-tuning pipeline end-to-end