Opened 10 years ago
Closed 10 years ago
#568 closed defect (fixed)
Missing parts of helicity selection setup
| Reported by: | Juergen Reuter | Owned by: | Juergen Reuter |
|---|---|---|---|
| Priority: | P0 | Milestone: | v2.2.0 |
| Component: | core | Version: | 2.1.1 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Change History (3)
comment:1 Changed 10 years ago by
| Owner: | changed from kilian to Juergen Reuter |
|---|---|
| Priority: | P3 → P2 |
| Status: | new → assigned |
comment:2 Changed 10 years ago by
| Priority: | P2 → P0 |
|---|
This is the next one. Started to look into it Jan 27.
comment:3 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Looking into the implementation of the code in 2.2.0_beta, JRR is convinced that everything that was in 2.1.1 concerning numerical helicity selection rules has been reimplemented in 2.2.0, with the exception of the infrastructural code for the static build (#497, which is being implemented at the moment by WK). The self test has been reinstated in r5191. A final extensive check of these helicity selection rules maybe has to be done in the context of profiling and backwards validation (#521), or new methods for helicity calculational methods like MC over helicities (#395, BC), or analytical helicity selection rules (#257, #40). The selection rules seem to be working in the same way as in 2.0 and 2.1. Closing for now. [in case of any protests, reopen.]
I'm having a look into that one. Maybe it is only clean-up work.