Closed mtwest2718 closed 2 years ago
I am thinking that I might combine this with #2. The reason is that the arrays U_m
and U_h
have distinct names for each of the sub-arrays and presumably the maintainers would like to keep that meta-data info in the files. I will have to check. Also need to check on whether visc
and Nexcite
need to be broken out into components are not.
Because the .dac
functionality still exists, I haven't touched the file_m & file_h
name arrays yet. But having "dac" in all the meta info is rather annoying for any post-processing, so I need to learn how to split a string in Fortran.
This seems to be a clear method though I am unsure whether its possible to do this with older compilers...
For each time step & process, all output variables & the grid coordinates are saved to a single HDF5 file
output
subroutine in IO_rot.f90
..dac.
read/write subroutines remain & are functional with this update.Stuff not yet done that needs to be
compare_output.py
to handle consolidated hdf5 dataSince time series generation is dynamic and handled differently than the spatial grid and the output variables, I am not sure how exactly to handle it's porting from dac
to hdf5
.
This task will require separate file creation writing and closing steps.