Skip to content

Conversation

@clpetix
Copy link
Contributor

@clpetix clpetix commented Nov 22, 2024

Fixes Issue #278.

@clpetix clpetix added the bug Something isn't working label Nov 22, 2024
@clpetix clpetix self-assigned this Nov 22, 2024
@clpetix clpetix linked an issue Nov 22, 2024 that may be closed by this pull request
@mphoward
Copy link
Collaborator

Thanks! Can we add some short unit test that checks this?

@clpetix
Copy link
Contributor Author

clpetix commented Nov 25, 2024

@mphoward, do you have any insights on why this added tests would cause the HOOMD 2 version to fail?

@mphoward
Copy link
Collaborator

I am not sure why this would fail in HOOMD 2. It is writing images out that are not just zeros, but they don't seem to be the right ones. Maybe try writing the GSD files with high frequency and watch the movies (HOOMD 2 vs. 4) to see if you spot a difference.

If it is some quirk of HOOMD 2, I move to drop it sooner rather than later.

@clpetix
Copy link
Contributor Author

clpetix commented Nov 25, 2024

Thanks! I'll try that and see, but I am in favor of dropping support for HOOMD 2 pretty soon.

@clpetix
Copy link
Contributor Author

clpetix commented Jan 21, 2025

@mphoward, dropping HOOMD 2 fixed these failing tests!

Copy link
Collaborator

@mphoward mphoward left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

@mphoward mphoward merged commit 60586a4 into main Jan 21, 2025
28 of 35 checks passed
@mphoward mphoward deleted the fix/write-gsd-image branch January 21, 2025 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix error in WriteTrajectory for dynamic image data in GSD

3 participants