-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update reweighting routines for change in kappa #624
base: master
Are you sure you want to change the base?
Conversation
I checked that QUDA in the light sector works out of the box. For the non-degenerete it was not working, I add the interface using the multishift solver. The result seems unchanged to me |
@@ -56,23 +56,23 @@ void reweighting_factor(const int N, const int nstore) { | |||
init_sw_fields(); | |||
|
|||
if(mnl->type != NDCLOVERRATCOR && (mnl->kappa != mnl->kappa2 | |||
|| (mnl->type == NDDETRATIO | |||
|| (mnl->type == NDCLOVERDETRATIO |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I change the lines here such that now with a:
NDCLOVERDETRATIO
monomial we callsw_trace_nd
CLOVERDETRATIORW
monomial we callsw_trace
NDDETRATIO
monomial there is no trlog to compute, also this now can call QUDA inverter
it is necessary when using quda inverter since the only interface implemented is the multishift
now we pass the test that the reweighting factor of an In more detail NDCLOVERDETRATIO monomial
|
Good spotted. |
@Marcogarofalo for NDCLOVERDETRATIO you can use
for an extra speed-up as this will be basically like running double-half mixed-precision CG. (with some small overhead) |
Update reweighting routines to enable reweighting in "kappa"
Note: Check if similar actions are needed within the QUDA interface (kappa is usually not changed during HMC / inversions etc.)