You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I may add more things. I'm cleaning up the formatting stuff right now while adding some documentation, but the other changes require testing so I'm going to postpone them to a different commit.
The text was updated successfully, but these errors were encountered:
The HisqSmearing class has a smearAll method carrying out the level 1 hisq smear, unitarization, and level 2 smear. Separately is class has a SmearLvl1 method and a ProjectU3 method, apparently because they are used in the force. Would it make sense to have the smearAll method call these two, to reduce code redundancy?
There is a "SHARED_GAUGENAIK", which is only shared between level 1 smearing fields. It is also shared with a gaugeNaik field in the Force profiler... I guess this should be renamed?
Along this vein, the force profiler is apparently quite outdated by now. Maybe we should just axe it?
//this is only a placeholder function for testing, real implementation is in HISQ force! REMOVE for production!voidmake_f0(Spinorfield<floatT, onDevice, Even, HaloDepthSpin> &phi, std::vector <floatT> rat_coeff);
This is in our integrator.h... What do I do?
I'm adding a bunch of you guys b/c I want your perspectives on some of the stuff I'm putting in here.
HisqMdaggMFunctor
which is not used anywhere? Should be deleted, since one would guess theapplyMdaggerM
method calls it, but it doesn't.hisqforce
include guard. Meanwhilehisqforce.h
has no include guard. Can be fixed with replace include guards with pragma once #101I may add more things. I'm cleaning up the formatting stuff right now while adding some documentation, but the other changes require testing so I'm going to postpone them to a different commit.
The text was updated successfully, but these errors were encountered: