Closed ckoerber closed 5 years ago
I might have miss it but I didn't see a HISQ correlator unless it is included in the meson2pt but then a mixed meson would also be nice. I see a DWFTuning but I don't understand the motivation
The correlator tables have a key pointing to a propagator table. The propagator table aggregates all types of propagators, so a meson2pt can store any variant of a two point correlator with 2 quark lines. DWTuning is basically a meson2pt also, but with a column that specifics if the sink is on the domain wall, or in the center of L5. Technically you can add this column to meson2pt, and then specify that every correlator is calculated on the domain-wall, except for like... very few. While that is probably more coherent? that sounds like a pain in practice.
I think a better name for DWTuning would be DWF5D
One idea is to make a meson2pt5d table that inherits from meson2pt actually, but with an extra l5 column. That might be better than making a whole new table.
Let me be more specific. This will make a new table with an extra l5 column but at the class definition it will be a child.
After a brief discussion with @arjunqcd and @ebatz, here are a few random remarks:
mval
be in action? Change it to flavor?a_fm
is strongly correlated with beta
.For further discussion please continue in issue #20.
Table by point of the meeting
tables.pdf
Table related points
We want basic building blocks
Wanted Help for computational tables
Useful to implement for production