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

Spn smearing #2

Open
wants to merge 6 commits into
base: spn
Choose a base branch
from
Open

Spn smearing #2

wants to merge 6 commits into from

Conversation

theHoHsiao
Copy link

We implemented the Wuppertal smearing and APE smearing for both connected and disconnected measurements.

@fzierler
Copy link

fzierler commented Jun 3, 2024

Hi, as discussed with Paul, I found that the code here is actually slower than the one developed on top of the old HiRep code (using the old complex numbers). Specifically, I tested this code here and compared it to the one at https://github.com/fzierler/hirep-smear on DiaL3 for the connected measurements on a 64x16^3 lattice using the same input file and same flags in the Makefile. I find that the code here is about 50% slower. I don't know what could have caused this behaviour.

@fzierler
Copy link

Hi, I also tried to test this code for a source position different from (0,0,0,0). However, this leads to a failure of the Inverter on some of the configurations. Typically, this depends on the MPI partitioning and the specific machine (or maybe compiler). Further testing shows that this appears even without smearing in the conventional code for point sources.

I suggest we remove the option to place the source at an arbitrary point for the smearing code.

@fzierler
Copy link

fzierler commented Aug 9, 2024

Hi, currently this code does not measure the disconnected pieces because a function call to this measurement was lost, when I ported the code to the recent version of HiRep. I have fixed this by now and created PR for Paul's branch here: theHoHsiao#1

@edbennett
Copy link
Member

Hi both, just returning to this now—should this PR be merged in its current state, or should it wait until theHoHsiao#1 has been merged?

@fzierler
Copy link

Hi Ed, please wait until #2 is merged.

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

Successfully merging this pull request may close these issues.

3 participants