Are there any linked Issues or Pull Requests?
No response
Brief description
Now that we have the concept of "external fields" they seem like a strong possible solution to XIOS interfacing. Not surprising as interfacing with 3rd parties which use different field representations is what they are designed for.
This would represent a considerable amount of work as it turns I/O inside out. Instead of it being an aspect of the field objects, it becomes a utility to which field objects are brought.
Advantages are likely to include reducing the amount of code in the field object and removing the function pointers used to handle I/O.
Further details of the issue.
No response
Are there any linked Issues or Pull Requests?
No response
Brief description
Now that we have the concept of "external fields" they seem like a strong possible solution to XIOS interfacing. Not surprising as interfacing with 3rd parties which use different field representations is what they are designed for.
This would represent a considerable amount of work as it turns I/O inside out. Instead of it being an aspect of the field objects, it becomes a utility to which field objects are brought.
Advantages are likely to include reducing the amount of code in the field object and removing the function pointers used to handle I/O.
Further details of the issue.
No response