Adding GSFtracks Indices in SimTICLCandidate#51310
Conversation
|
cms-bot internal usage |
|
@cmsbuild please test |
|
A new Pull Request was created by @Moanwar for master. It involves the following packages:
@Moanwar, @jfernan2, @mandrenguyen, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+1 Size: This PR adds an extra 40KB to repository Comparison SummarySummary:
Max Memory Comparisons exceeding threshold@cms-sw/core-l2 , I found 4 workflow step(s) with memory usage exceeding the error threshold: Expand to see workflows ...
|
|
@cmsbuild please test |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @ftenchini, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
Hi @Moanwar was this reduction in memory understood? As we discussed, sounds weird that it gets reduced while we are adding information |
Hi @waredjeb, not really. The reduction in step5 is should be unrelated, and this PR doesn't affect step5 at all. |
|
We'v found that we have memory fluctuations on the order of < 30MB often. I wouldn't be surprised to see a case where that randomly fluctuated up to just over 30MB. We'd love to know exactly what causes these. Given the code shouldn't affect harvesting and assuming the histograms filled by harvesting aren't showing any unexpected changes, I'd say it is fine to ignore the memory change. |
|
So if I look at the memory report directly, it says a additional 513.20 MB was used by this PR compared to the base line for workflow 34634.0_TTbar_14TeV+Run4D121PU step3 (by used it means requested and released, not that the maximum memory used by the job at one time was 500MB more) That seems like something that should be checked. @gartung any idea why that didn't get flagged for the summary? I'm guessing since it is |
|
The test is only for max memory used. The other quantities are not checked but they can be added if needed. |
|
@cmsbuild please test |
|
+1 Size: This PR adds an extra 28KB to repository Comparison SummarySummary:
Max Memory Comparisons exceeding threshold@cms-sw/core-l2 , I found 4 workflow step(s) with memory usage exceeding the error threshold: Expand to see workflows ...
|
|
hi @Moanwar can you run the test on single electron sample, with and without pu? |
This PR adds the indices of the matched GSFtracks to the SimTICLCandidate collection. This can be used for validation studies and will also be used by MLPF to define the training targets.