Opened 11 years ago
Closed 11 years ago
#513 closed defect (fixed)
Resolve qcd_parameters conflict
| Reported by: | Juergen Reuter | Owned by: | kilian |
|---|---|---|---|
| Priority: | P0 | Milestone: | v2.2.0 |
| Component: | core | Version: | 2.1.1 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
qcd_parameters is currently not called. It should be initialized
from process_config_data_init, but there the information of the variables for the QCD data seems not to be present !?
Change History (8)
comment:1 Changed 11 years ago by
comment:3 Changed 11 years ago by
| Priority: | P3 → P1 |
|---|
comment:5 Changed 11 years ago by
| Status: | new → assigned |
|---|
This is now obsolete because all functionality has been included in the new module sm_qcd and the associated types. Various alpha_s running couplings are available, and the PDF builtin path is no longer a variable; the PDF set may be chose by the user.
Keeping, because some cleanup is in order (soon).
comment:6 Changed 11 years ago by
Does this cleanup also include running alphas from LHAPDF? I guess, this is not yet implemented yet.
comment:7 Changed 11 years ago by
Alpha-s from LHAPDF: yes, noted in a separate ticket #537.
Cleanup means here: eliminate dead code.
comment:8 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Cleanup, as far as it concerns this ticket, done in r4656. Minor remaining issues are covered in separate tickets; closing this one.
My suspicion is that in
process_config_data_initthere should be corresponding callscall config%qcd%initandcall config%qcd%pdf_builtin_initetc. For this, there has to be a dependence on the correspondingglobalstore.