We store only n_mc_trajectories in the MINERvA dst file (10000 for now). In less than 1% spills, there are trajectories that go above that number. That lead to some CAFs making crashes for large number of CAFs. Until we get a smarter way to store trajectories in the dst files, we just don't look for the true trajectory of that. specific track or shower and setting tthe type to kUnknown.
linked are the error message we were getting for a specific file and the same run after the fix + the scan of that specific track that was creating an issue (with type == 0 now)
We store only
n_mc_trajectoriesin the MINERvA dst file (10000 for now). In less than 1% spills, there are trajectories that go above that number. That lead to some CAFs making crashes for large number of CAFs. Until we get a smarter way to store trajectories in the dst files, we just don't look for the true trajectory of that. specific track or shower and setting tthe type to kUnknown.linked are the error message we were getting for a specific file and the same run after the fix + the scan of that specific track that was creating an issue (with type == 0 now)