Improve README before the new release tag #53
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
David-Araripe
requested review from
ChielJespers,
goodstudyqaq and
jesperswillem
goodstudyqaq
approved these changes
Nov 19, 2025
ChielJespers
approved these changes
Nov 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @jesperswillem , @ChielJespers and @goodstudyqaq,
I'm making this PR to update the README for the manuscript describing QligFEP. In the manuscript we mention we have v2.1.0 and I would like to make a release tag marking this version of the code.
Before doing so, I needed to add a mention to the benchmarking results, but I thought it would be nice to add a note that Q-GPU is still under active development.
Could you have a look at the new info I added to the README and see if you approve it? I see there's a list of
AUTHORSunder Q-GPU as well and I see Shen is not listed there yet. Maybe that's something we should also fix since the repository is public now.