22eb17a6

By: ValentinHirschi <valentin.hirschi@gmail.com>

record five-decade GL638 joint weight approach study

Archive the two regular H/Z approach rays and exact source, card and build
provenance. Complete weights flatten for the joint density while optimized
LMB and direct-H weights retain their expected inverse-power growth.

Validation: 144 native physical evaluations and 2040 independent artifact
checks pass. Both runs preserve the saved state. These finite-range results
do not establish global boundedness or Monte Carlo variance reduction.

User requests:
Continue as planned, but after this current round of optimisation completes for the joint advanced sampling, stop optimizing further; we will accept current advanced sampling performance as-is for now. Instead focus on verifying that the physics expectation are met. That is:

i) The integrand weight in the HZ corner are now bounded.

ii) The variance of at least the absolute value of the integrand, but hopefully also of the integrand itself, is improved. (compare the MC error at a) fixed sample counts without advanced sampling, b) with only combinations of channels with simpler non-joint advanced maps, c) with the full optimal combination involving also joint advanced sampling maps)

iii) For a reasonable number of sample gain confidence of the fact that the case c) above leaves a bounded maximum weight, and at least smaller than the one found in b) and c). Also analyze what is the origin and cause of the remaining max weight point in b) and c) setups.

iv) Provide you current best estimate (central value + error) you current have now on GL638 cross-section. You can use up to 30 cores and 300 GB of RAM; but use less if you don't see performance scale linearly with number of cores until 30.

Continue as planned, but did you already do a local instpect/approach of the HZ corner to establish that the new joint map makes the GL638 weight bounded there now?

(
continue as planned, but also consider different combination of channels which you think are optimal,e.g. something like:

| ChannelTarget | |
| --------------- | ----------------------------------------------- |
| Cut 0 | `cut(2,6,12,13)` |
| **Cut 1 + H/Z** | `cut(2,6,10)` combined with joint H/Z focusing |
| Cut 2 | `cut(2,6,7,13,14)` |
| Cut 3 | `cut(2,4,12)` |
| Cut 4 | `cut(2,4,10,13)` |
| Cut 5 | `cut(2,4,7,14)` |
| Soft coverage | One LMB: `[6,12,13,14]`, containing both gluons |

Although the soft channel may not even be necessary.

Experiment with different combinations.

So toggling on/off the join mapping should not be by itself, but rather always in the presence of cut channels.

but of course also compare against the baseline of just the optimized LMBs (which is what we had before).

)
GitHub
Time to Start Worker time Duration Time to finish Idle
Config 2s 9s 9s 11s 2s
Eval 6s 58s 58s 1m05s 0s
Build 57s 1h36m38s - - 40s
Test 1m27s 25m14s - - 4m07s
Deploy - - - - 42m38s
Suite 2s 2h03m01s - - 47m28s

Timeline

Config Eval Build Test Failed Retried Compressed gap
0s1m2m3m4m5m6m7m8m9m10m11m12m13m14m15m16m17m18m19m20m21m22m23m24m25m26m27m28m29m30m31m32m33m34m36m37m38m39m40m41m42m