ADIOS2 Updates for Code Coupling - #3450
Merged
Merged
Conversation
dschwoerer
approved these changes
Aug 11, 2026
dschwoerer
left a comment
Contributor
There was a problem hiding this comment.
From a short glance this seems reasonable. But I am not an Adios2 user, thus I have not tested it.
The formatting fails because it comes from a fork, I run it locally and everything is fine.
I would support merging this. @ZedThree do you want to review this, or should we just merge this?
bendudson
approved these changes
Aug 11, 2026
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.
This expands some of the ADIOS2 functionality that was in
adios_object.cxxandoptions_adios.cxxto have a simple public interface for reading and writing standard BOUT++ data types such asField2D,Field3D, andArray. This is mainly intended for code coupling where the usage would look something like