Gen/ee: the fixes after - #17
Conversation
…e dirs Add a top-level "Getting started" section with the git clone command, and a note in Gen/ee/README.md that all commands assume starting from that stage's folder. Prefix WHIZARD with OMP_NUM_THREADS=1 by default, since it otherwise grabs every core on the machine, which is unfriendly on shared nodes; join it with the existing cross-section note into one numbered Notes: block. Fence the three Q&A <details> blocks with '>' to match the rest of the doc's blockquote-style asides. Rename the scratch working directories from test_whizard/<sample> to whizard_prod/mumuH and pythia_prod/<mumuH|WW|ZZ>, split by tool rather than sample - this also fixes WW/ZZ being nested under "test_whizard" despite using no WHIZARD step at all. Verified the full pipeline end-to-end against the new layout.
Note in Gen/ee/README.md and solutions/backgrounds.md that "background" here means a different physics process (WW, ZZ), not the beam-induced background FullSim students may expect - this tutorial has no BIB overlay at all. Also drop the top-level README's claims that each section has introductory slides and that students present their solutions, since neither was actually done.
Should be relative to the already-cloned repo root, not include the repo directory name itself.
| repository: | ||
|
|
||
| ```bash | ||
| cd Gen/ee |
There was a problem hiding this comment.
consider stating with a git clone and cd into the cloned repo?
| > machine, which isn't friendly (or efficient) on shared/multi-user | ||
| > nodes. `OMP_NUM_THREADS=1` restricts it to a single thread; drop it | ||
| > if you're on a machine you have exclusively to yourself and want the | ||
| > integration step to finish faster. |
There was a problem hiding this comment.
I think i would not suggest unsetting OMP_NUM_THREADS unless one knows what they are doing. Only for heavyweight processes will increasing the number of threads help.
| Two settings are deliberately left out rather than pinned explicitly, | ||
| relying on their WHIZARD defaults: | ||
|
|
||
| > Notes: |
There was a problem hiding this comment.
with "Notes:" here, the text is quite awkward. Perhaps the two sets of notes can just be merged?
| @@ -175,13 +188,13 @@ | |||
| > 1. To get a list of all available commandline arguments which one can use to | |||
There was a problem hiding this comment.
fwiw, the information flow in this section does not seem to follow a logical order as it starts with steering files, goes back to pythia files and eventually comes back to an actual steering file
(but thats not an issue with this PR).
| don't need WHIZARD: Pythia8 can generate the hard process itself directly, | ||
| so this is a single Pythia8 step with no LHE file involved at all. | ||
|
|
||
| > **Note:** "Background" here means a different *physics process* (WW, |
There was a problem hiding this comment.
this text is also in the readme. Is that sufficient?
Details
blocks with '>' to match the rest of the doc's blockquote-style asides