Open chaoos opened 9 months ago
@Jenkins test this please
Thanks for this contribution @chaoos. This looks like a great PR and it will be great to OpenQCD support plumbed into QUDA 😄
@mathiaswagner and I are traveling at the moment, so reviewing this will likely take longer than normal. In the meantime, can you fix the broken builds in the CI matrix? (click on the Details
link next to the failed build, and you should be able to find the reason for the failure). Also, please add your name to the README
under the list of contributors.
cscs-ci run
@maddyscientist Could you trigger the pipeline again? Locally I fixed the problems. Thank you, Roman
@Jenkins test this please.
Thank you for this PR, this is a great contribution to QUDA. I have done an initial visual review at this point, and left a bunch of comments. My only real concern of note is the demotion of the interface to being C89 instead of C99, but those concerns may be unwarranted.
Outside of those comments, somethings that will need to be done:
* [ ] Apply clang-format (see [here](https://github.com/lattice/quda/wiki/Coding-Conventions-and-Style#coding-style-and-clang-format)) * [ ] Create a wiki page of how to use OpenQ*D with QUDA, similar for example to what we have for [MILC}(https://github.com/lattice/quda/wiki/MILC-with-QUDA)
Is there any specific functionality that is added to QUDA that we should be adding to the internal tests?
Dear Kate,
I dealt with the two points:
Best, Roman
Hi Roman,
I've added you to the lattice github group, so you should have permission to edit the wiki now (and push to branches in the lattice org).
Thx
@Jenkins ok to test
I was able to commit to the wiki, thanks for giving me access! The CI/CD also seems to be fixed.
cscs-ci run
The C89 changes are of concern, since we will be embracing a C99 interface, e.g., use of
bool
.
Dear Kate,
@chaoos apologies for the slow reply at my end. GTC and other travel got in the way.....
If you can revert the C99 -> C89 changes that would be great. It would also narrow the scope of the PR which would also be helpful.
Regarding documentation, the basic rule is that all new functions should have doxygen markup next to their declarations, together with overall conceptual documentation in the wiki. If you can write up the documentation to include cloning the openq*d and compiling the code to work with QUDA that would be great. Understood that the repo isn't public yet, and that's fine for now. Does that sound ok to you?
develop
branch