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

Update HOOMD examples to HOOMD v3 #18

Open
bdice opened this issue Nov 7, 2020 · 4 comments
Open

Update HOOMD examples to HOOMD v3 #18

bdice opened this issue Nov 7, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@bdice
Copy link
Member

bdice commented Nov 7, 2020

The HOOMD examples should be updated to use HOOMD version 3 (currently in beta). Related to #14.

@bdice bdice added the enhancement New feature or request label Nov 7, 2020
@bdice
Copy link
Member Author

bdice commented Feb 10, 2021

Update: this has come up a few times in conversations. We're going to wait to rewrite the tutorial content using HOOMD until version 3 is finalized. That will likely be a few months from the time of writing (February 2021).

@bdice bdice mentioned this issue Feb 10, 2021
@atravitz
Copy link
Collaborator

I'd like to keep HOOMD v2 examples alongside HOOMD v3 for at least a little while after the v3 examples is introduced.

@bdice
Copy link
Member Author

bdice commented Aug 16, 2021

I think that's fine -- we can just copy and rename the folder to something like flow.hoomd2.lj and flow.hoomd3.lj. We'll only be able to test one configuration on our CI, however. We would add a file .skipci in the project folder to disable CI on one or the other. I'd prefer to skip CI on HOOMD 2.

@bdice
Copy link
Member Author

bdice commented Apr 5, 2022

HOOMD v3 has been released. This is ready for work now.

@cbkerr cbkerr linked a pull request Aug 1, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants