ERF boundary file (erfbdy)#3264
Draft
wiersema1 wants to merge 42 commits into
Draft
Conversation
…. This allows for the minimum number of boundary data times to be stored in memory. Stored boundary times are updated by reading from the boundary file as-needed during the run. This capability enables ERF to be run as a preprocessor by setting max_steps=0, which will initialize the simulation and produce checkpoint and boundary files. These features are working in serial for init_type="metgrid".
…metgrid being parsed from the global attr SIMULATION_START_DATE to the variable Times.
… and IO/ERF_WriteERFBdy.cpp
…nt at the boundaries
…MULATION_START_DATE to the variable Times.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BLUF
This PR introduces the ERF boundary data (erfbdy) file format, AMReX-native storage of boundary data FABs for real data cases using the wrfinput and metgrid pathways.
Summary
max_steps = 0) to generate erfbdy and a checkpoint file.Directory Structure
The erfbdy file uses a hierarchical directory structure:
New Input Parameters
erf.erfbdy_file"erfbdy"erf.write_erfbdytrue(for clean starts)false(for restarts)erf.real_width0Notes:
erf.real_widthmust be specified when usingerf.init_type = "metgrid"orerf.init_type = "wrfinput".erf.write_erfbdyautomatically defaults totruefor clean starts witherf.init_typeof"metgrid"or"wrfinput"andfalsefor restarts or othererf.init_type.erf.write_erfbdycan be set tofalseforinit_type = wrfinputto process boundary data on-the-fly, but must remaintrueforerf.init_type = metgridif using model restarts.Technical Details
New source files added in
Source/IO/:ERF_ReadFromERFBdy.H/cpp: Functions to read erfbdy header metadata and time slices.ERF_WriteERFBdy.H/cpp: Functions to initialize and write erfbdy files.Resolves
This PR resolves restart failures with
init_type = metgridby ensuring boundary data is properly managed across checkpoint/restart cycles. Previously, metgrid initialization could not be restarted because boundary data state was not preserved.Testing
init_type = "metgrid"real_width = 1real_width = 10init_type = "wrfinput"