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

Get parallel and serial file writing matching after reorder #123

Open
kuberry opened this issue Oct 11, 2019 · 1 comment
Open

Get parallel and serial file writing matching after reorder #123

kuberry opened this issue Oct 11, 2019 · 1 comment
Assignees
Labels
HARNESS idea Idea for future research/implementation test Suggested test

Comments

@kuberry
Copy link
Collaborator

kuberry commented Oct 11, 2019

Original data has fields copied to new file which had parts written in parallel. Original fields are never mixed up, so they don't need resorted. New data that was added needs resorted according to ID, but this is difficult to check.

Need to create a test that writes a fake data field (or recopy the lat/lon field, e.g.) and then do comparison at the end to verify correct functionality.

@kuberry kuberry added idea Idea for future research/implementation test Suggested test HARNESS labels Oct 11, 2019
@kuberry kuberry added this to the CANGA - FV to FV milestone Oct 11, 2019
@kuberry kuberry self-assigned this Oct 11, 2019
@kuberry
Copy link
Collaborator Author

kuberry commented Oct 11, 2019

While this test should still be created, parallel and serial netCDF outputs currently match to single precision.

An additional test would be to print the solution with double precision for a particle DOF# at a particular iteration #, and then to compare to see if they truly differ after serial precision, or whether they are the same but the difference comes from writing to file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
HARNESS idea Idea for future research/implementation test Suggested test
Projects
None yet
Development

No branches or pull requests

1 participant