-
Notifications
You must be signed in to change notification settings - Fork 132
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
Relax MPCD restrictions on boxes #773
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This issue has been automatically closed because it has not had recent activity. |
We will need to address this as part of our new work. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Not stale |
@joaander I am going to do my best to get this branch to a point that we can open a PR onto |
What planned changes to do you expect to conflict? |
This change will only touch MPCD code, but it touches alot of it so I think the main conflicts will come from any global search & replace incidental to other changes. And then of course, application of code formatting. |
It looks like the majority of those changes are in C++ files, so the mostly likely cause of conflicts is #1938 which is already merged. The switch to ruff may cause conflicts in the I will be sure to review your PR soon after you post it. |
Yes, that's right—this is a big generalization of some of the underlying C++ code. Sounds like a plan, thanks! |
Done in #1950 |
Description
MPCD currently requires that the box size be (1) orthorhombic, (2) constant, and (3) a multiple of the MPCD cell size. Only requirement (3) is strictly necessary for the algorithm to work right, so I will check over the code to see if it makes sense to support other (e.g., deformed) boxes. This is change is not necessarily breaking but may not be the behavior expected by the user, so I will look into it for v3.
The text was updated successfully, but these errors were encountered: