Opened 8 years ago
Closed 5 years ago
#828 closed enhancement (duplicate)
Disabling PS generation for unused NLO components
| Reported by: | Juergen Reuter | Owned by: | kilian |
|---|---|---|---|
| Priority: | P4 | Milestone: | v3.0.0 |
| Component: | core | Version: | 2.5.0 |
| Severity: | minor | Keywords: | Backlog |
| Cc: |
Description
BACN:
I think this could be solved just by looking at the corresponding flags when dispatch_phs is called in setup_real_component, setup_mismatch_component etc. within the almighty integration_setup_process
Change History (5)
comment:1 Changed 8 years ago by
comment:2 Changed 7 years ago by
| Milestone: | v2.6.0 → v4.0 |
|---|
comment:3 Changed 7 years ago by
| Milestone: | v4.0 → v3.0.0 |
|---|
comment:4 Changed 7 years ago by
| Summary: | Check whether phase space generation can be disabled not only for subtraction component but also other disabled nlo components → Disabling PS generation for unused NLO components |
|---|
Original title "Check whether phase space generation can be disabled not only for subtraction component but also other disabled nlo components" shortened.
comment:5 Changed 5 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Transferred back to Gitlab issue 6.
Note: See
TracTickets for help on using
tickets.
Explanation by CW:
t's about the fact that the phase space is generated also for NLO components which are not integrated. E.g. if
nlo_calculation = "Virtual", also the phase space for the Born and real component is generated. This can of course take some time for large processes.Gitlab Issue #6.