We came across this in MG work but I thought we fixed it. I think this comes from the fact that we didnt set it at all since we passed the precomputed clover term so we didn't need to. I think at some point Kate tightened up the parameters checking. I can't remember if I set a default value in the Mg branch or whether Kate did it on the MG QUDA branch.
On May 22, 2016 4:04:36 PM EDT, Frank Winter notifications.com wrote:
invertQuda gives me
CALLING QUDA SOLVER ERROR: Parameter clover_coeff undefined (rank 0, host workstation, check_params.h:365 in checkInvertParam()) last kernel called was (name=N4quda10CopyCloverIffLi72ENS_6clover11FloatNOrderIfLi72ELi4EEENS1_11QDPJITOrderIfLi72EEEEE,volume=16x16x16x32,aux=out_stride=65536,in_stride=65536) QMP m0,n1@ error: abort: 1
This comes from an HMC (Chroma) input file that worked before. It's the MdagM clover operator, biCGstab (CG shows the same behavior). I cross-checked pure Wilson and that one works (Bicgstab and CG). Where/when is the quda invert parameter clover_coeff set?
What wonders me is knowing the fact that we checked quda 0.8 against these tests.
You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/lattice/quda/issues/470
Balint Joó, Scientific Computing Group, Jefferson Lab Email: bjoo.org Tel: +1 757 269 5339 Sent form my mobile phone