-
Notifications
You must be signed in to change notification settings - Fork 17
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 hdf5_puff.f90.in so that new fields are written (separate files for ranks) #21
Comments
I have added some infrastructure to simplify the writing of a field mesh and limits. This is apparently working quite nicely, and has allowed me to write the front, real field to a file, which may be visualised. I need now to abstract out everything apart from the dataset specific bits (ie which I expect to get from range in z). These new blocks will make life easy for writing the electron datasets and field datasets in parallel too, since the limits are shared. |
Note - I'm going to commit only once I've got the six files there, otherwise I might be causing more trouble than I'm saving. |
Jesus Jonny, get to bed! Sent from my Samsung device -------- Original message -------- Note - I'm going to commit only once I've got the six files there, otherwise I might be causing more trouble than I'm saving. � |
I've committing what I have, though there are some questions. I fixed the particles so again they work with the distributed field, and tried the current version of the parallel-field branch on 8 cores. I looked at the sizes of the datasets produced by the various nodes, as I've not done the stitching back together yet (and stitching will be done in a fortran to C sense while the issues remain around fortran ordering in vizschema). Either see http://slideplayer.com/slide/3265765/ (slide 10 of 27) or https://ice.txcorp.com/trac/vizschema/wiki/DataOrdering for details on the fact that fortran array ordering should be supported. I'm highly likely to be getting some out by one errors in the size of the array in the meantime. The front field is present on ranks 1,2,3,4 only (seems maybe there are four cells in that region) See below: |
I think the effect above is understood. A utility has been provided to stitch these files back together, and has been 'tested' in the sense that I've checked the data structure is the right shape, and appears to have stuff on axis and not off. There is some stuff towards the back of the domain fairly quickly though, which may not be physical. Handed over to Lawrence for further testing. |
No description provided.
The text was updated successfully, but these errors were encountered: