Ticket #2578 (closed: fixed)
HRPD Parameters file
Reported by: | Nick Draper | Owned by: | Anders Markvardsen |
---|---|---|---|
Priority: | critical | Milestone: | Iteration 28 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Roman Tolchenov |
Description
From Aziz (therefore I'm pretty sure this is HRPD):
Playing with the new _parameters.xml file I finally understood why guesses were computed wrong : There is no need for inserting a conversion factor in the “Fullprof formulaes†: these can be literally used as they are. However, since the formulae parametrize a peak profile in TOF, the proper behaviour is obtained by setting all results units in <TOF> as follows:
<component-link name="bank_bsk" > <parameter name="BackToBackExponential:S" type="fitting"> <formula eq="sqrt(7.429*centre^4+132.188*centre^2)" unit="dSpacing" result-unit="TOF" /> </parameter> <parameter name="BackToBackExponential:A" type="fitting"> <formula eq=" 0.086851/centre" unit="dSpacing" result-unit="TOF" /> <fixed /> </parameter> <parameter name="BackToBackExponential:B" type="fitting"> <formula eq=" 0.005047/(centre^4)+0.023347" unit="dSpacing" result-unit="TOF" /> <fixed /> </parameter> </component-link>
Change History
comment:1 Changed 10 years ago by Martyn Gigg
- Owner changed from Martyn Gigg to Anders Markvardsen
- Status changed from new to assigned
comment:6 Changed 9 years ago by Anders Markvardsen
- Status changed from accepted to verify
- Resolution set to fixed
Note: See
TracTickets for help on using
tickets.
Anders said he didn't understand why this change should actually make any difference given the factor that was removed should have been exactly the same as setting the result to dSpacing.