-
Notifications
You must be signed in to change notification settings - Fork 98
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
testing parallel writes just as NOAA does them #265
Conversation
@junwang-noaa some questions: 1 - Do you define all dims first, then all vars? Or do you intermix? What is the order of dim and var creation, exactly? 2 - Also, how is the data written? There are 40 processors involved, how do they split writing of the phalf field? Do they each write 1/40th? Or does one processor write it all? 3 - You do an enddef/redef for each def_var, right? What is the exact ordering of calls there? |
We do intermix. the processors does not split writing of the phalf. Please see the code below, the valueListR4 is a array with full 128 elements of phalf. nf90_create(trim(filename),& subroutine add_dim(dim_name...) |
Where is the code that writes the values to the lat/lon variables? |
OK, I believe this code is pretty close to what NOAA code does. I had to come up with my own (checkerboard) decomposition. |
Thanks! |
@WardF thanks for the quick merge here. I will have a C version of this program (even more like the NOAA code, and with built-in timing) soon. Then this test will migrate to PIO and there become a PIO performance benchmark. So we see how a simple test program can be very useful in many different projects. ;-) |
This is a draft PR, put up so some NOAA collaborators can inspect the code and we can make this test mirror a problem area of NOAA code.
This is part of #264
@junwang-noaa please inspect the code in f90tst_paralllel_compressed.F90. This produces a file with this ncdump: