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

Source location information is not always available in propagators #13

Open
kostrzewa opened this issue Jan 13, 2012 · 1 comment
Open
Assignees

Comments

@kostrzewa
Copy link
Member

It would be good to have the source location (and perhaps more info) added in the inverter info lime message or be present in propagator files in some other way.

@ghost ghost assigned Siebren Jan 13, 2012
@Siebren
Copy link
Contributor

Siebren commented Jan 13, 2012

A general solution to this problem is not so easy, as there are several use cases, which in general need to be handled differently, and proposed solutions are not available/desirable for all cases.

  • A point source is generated inside the code
  • A volume source is generated inside the code
  • A source is read in.

For sources generated inside the code, we can reasonably expect the tmLQCD code to deliver all relevant information in some way with the propagator. For a read in source, the best we could do is copy meta information from inside the source (LIME messages?), and put these in the propagator.

For point like sources, it was (is?) standard to put the timeslice in the filename, but more information is available, such as x,y and z coordinates.

While a complete solution probably depends on properly defining what a source is, and how to describe a lot of (all?) sources, we can at least make some improvements here by at least supplying the information we have access to (LIME messages, input file settings), and accepting that that information is incomplete/inelegant for now.

kostrzewa referenced this issue in kostrzewa/tmLQCD Sep 25, 2013
use better threaded comm/comp overlapping with MPI
kostrzewa added a commit that referenced this issue Jun 13, 2017
qphix_interface: Remove old full_clover_product
kostrzewa pushed a commit that referenced this issue Nov 5, 2018
…_threaded

introduce threading into update_momenta_fg
kostrzewa pushed a commit that referenced this issue Aug 7, 2021
add mechansim to ensure that the QUDA MG setup is reset regularly
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

No branches or pull requests

2 participants