-
Notifications
You must be signed in to change notification settings - Fork 47
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
MonitorForces not working with QUDA #517
Comments
We've reproduced this, albeit with a different error: we get a precision mismatch. This indicates that one of the parameter structs is not properly initialized (or overwritten somehow). |
Hi, yes, in case I do |
I saw similar kind of issue using hot start: |
Hi is not working, I have to say I don't understand the logic. Below is also the relevant part of the input file, maybe somebody can spot a parameter not properly set?
|
I attach @Marcogarofalo since he is observing the same issue |
I notice
is not add to the |
Ok I understand that the
is not needed and is not understood at all |
The clover monomials should always be EO (it's an unholy mess for historical reasons)...
|
ok, the global flag is set to yes, this is ruled out For some reason the heatbath part of the momomial is working, but the force calculation is not... |
in other words when the monomial is created, the sloppy gauge field is initialized, then when the force is computed, the sloppy field is freed, is not recreated, but later is addressed by the solver |
I see only now this comment by Ferenz. It looks to me like this might be related to PR #522, where we observed another problem related to gauge_state. Possibly the PR #523 might fix the issue? |
Just for reference, I report here another workaround that makes the problem disappear. One should add: updateMultigridQuda(quda_mg_preconditioner, &quda_mg_param); after this line: Line 2101 in 23003f1
|
…is 'resolves' #517 but makes using the MG a bit more expensive in the HMC because MG_Preconditioner_Setup_Update is basically called at every call of the MG
@sbacchio did the changes solve the issue with |
I still see this issue in |
@Marcogarofalo in your input file, can you specify
to see if this resolves the problem? I think there might be an issue with trying to do full double-precision MG. Doing so is not recommended anyway, but I suspect that this is the reason for what you're seeing in the online measurement. Strictly speaking we should of course support full double-precision MG, but it's not a high priority as it will be slow. |
note that you can also reduce the maximum number of iterations there to at most 500 or so. |
Yes sorry, besically the error I am seeing is #530. I thought that I had fixed the input. Thank you. |
When
MonitorForces = yes
an error occurs in QUDA. More investigation required.The error is the following:
For more details see
$SCRATCH_fssh/bacchio1/C56/logs/log_trial_4811972.out
on Juwels BoosterThe text was updated successfully, but these errors were encountered: