Pull back data to legacy structures on device #49
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.
ARPEGE/IFS field data are now encapsulated with Field API structures in the grid-point calculations; however, in the spectral calculations, these data are still represented by old GMV and GFL arrays.
This implies that we need to implement a fast mean of moving GFL/GMV back and forth between new Field API data structures and GMV/GFL arrays allocated on the device.
This PR implements such a mechanism, which is designed to be flexible enough to be compatible with a traversal of large data structures such as YDVARS.
The test case test_legacy.F90 illustrates this mechanism.