1 / 5

IO Architecture Notes

IO Architecture Notes. IO Scalar Quantities. Information that is needed for the simulation that is neither grid data, nor defined as a runtime parameter (ie. simulation time) Each unit writes what, if any, scalar values they own through sendOutputScalars, which is called by IO.

reubena
Download Presentation

IO Architecture Notes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IO Architecture Notes

  2. IO Scalar Quantities Information that is needed for the simulation that is neither grid data, nor defined as a runtime parameter (ie. simulation time) Each unit writes what, if any, scalar values they own through sendOutputScalars, which is called by IO. Output scalars are read back during IO_init in Driver_initFlash

  3. Integral Quantities Quantities are integrated by volume over the grid. Cartesian geometries are supported by default as well as 2D Cylindrical. Frequently overridden to provide additional functionality Does not utilize any of the IO unit’s output machinery, you are responsible for your own MPI communication if you override the file. Recommended that you use Flash_mpi.h and FLASH_REAL for MPI calls.

  4. IO Caveats and Gotchas IO has a few exceptions to our general architecture rules Can directly access the Grid unit’s data Not all of IO is included by default IOMain and IOParticles are separate subunits! Restarts do interact with the environment Runtime parameters from the Config files and flash.par trump values stored in a checkpoint Values for Runtime Parameters in checkpoints are stored as a previous value Initialization Order IO_init must be called before any scalar quantities are used This includes sim_time! Logfiles are their own unit. They are not a part of the IO unit Diagnostic IO: watch who is writing to what file

  5. IO and Grid Variables The reading and writing of Grid variables are handled differently depending on type. Unknowns are both written and read by default Only variables to be plotted, at this time Face-centered data will be checkpointed if declared Fluxes are not checkpointed at all Scratch variables may be checkpointed for diagnostic purposes, but are never read back in

More Related