You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some schemes rely on the dynamic use of HEAP memory (e.g module memory). This is problematic for host model applications that wish to run multiple instances of the ccpp-physics within the same executable, where we run into the issue of multiple tasks trying to read/write to the same memory.
Solution
Remove dynamic HEAP references from parameterizations and replace with Interstitials. This way each ccpp instance is self contained and "stateless" (no dynamic shared memory). This is straightforward for some schemes (i.e. Thompson MP), while quite invasive to others (i.e. ozone physics and RRTMGP).
The text was updated successfully, but these errors were encountered:
Description
Some schemes rely on the dynamic use of HEAP memory (e.g module memory). This is problematic for host model applications that wish to run multiple instances of the ccpp-physics within the same executable, where we run into the issue of multiple tasks trying to read/write to the same memory.
Solution
Remove dynamic HEAP references from parameterizations and replace with Interstitials. This way each ccpp instance is self contained and "stateless" (no dynamic shared memory). This is straightforward for some schemes (i.e. Thompson MP), while quite invasive to others (i.e. ozone physics and RRTMGP).
The text was updated successfully, but these errors were encountered: