Skip to content
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

clover dslash_test broken with t partitioning and reconstruction #130

Closed
maddyscientist opened this issue Feb 24, 2014 · 3 comments
Closed
Assignees
Labels
Milestone

Comments

@maddyscientist
Copy link
Member

(paraphrasing message from Alejandro)

Multi-gpu clover is broken for link reconstruction different than 18 in quda-0.7 and tifr-redux branches (therefore in tmclover-quda as well). I don't know why, but I feel this is related to the way the extended gauge fields are constructed, I think these only work in recon 18, so when creating the extended fields from the original fields with recon 12 or 8, something must go wrong for multi-gpu.

mpiexec -np 2 ./dslash_test --dslash_type clover --Lsdim 1 --test 2 --tune false --sdim 24 --tdim 24 --tgridsize 2 --prec double --recon 18 --load 0000 --dagger

and

mpiexec -np 2 ./dslash_test --dslash_type clover --Lsdim 1 --test 2 --tune false --sdim 24 --tdim 24 --tgridsize 2 --prec double --recon 12 --load 0000 --dagger

I'm reading spinor and conf from disk, so I always study the same case. This two runs give me very different result, and if I use recon 8, it's even worse.

@maddyscientist maddyscientist added this to the QUDA 0.7 release milestone Feb 24, 2014
@maddyscientist maddyscientist self-assigned this Feb 24, 2014
@maddyscientist
Copy link
Member Author

I cannot reproduce this failure with the current quda-0.7 branch. It's possible this bug has been fixed already accidentally.

Alejandro, can you try to reproduce this, to see if it's still present?

The only issue I have managed to reproduce is if the gauge field that is loaded is only stored in single precision, then reconstruction will deviate at single precision accuracy. The solution to this is to reproject the gauge field on the SU(3) manifold, but that's something else entirely.

@AlexVaq
Copy link
Member

AlexVaq commented May 30, 2014

I'll try to have a look at it asap, although with the lattice so close,
everybody's going to be very busy.

Ciao,

Alex

El 30/05/2014, a las 01:17, mikeaclark notifications@github.com escribió:

I cannot reproduce this failure with the current quda-0.7 branch. It's
possible this bug has been fixed already accidentally.

Alejandro, can you try to reproduce this, to see if it's still present?

The only issue I have managed to reproduce is if the gauge field that is
loaded is only stored in single precision, then reconstruction will deviate
at single precision accuracy. The solution to this is to reproject the
gauge field on the SU(3) manifold, but that's something else entirely.


Reply to this email directly or view it on GitHub
#130 (comment).

@maddyscientist
Copy link
Member Author

This bug is now fixed with commit 00566bb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants