External Issue: Design input for model state

chapelu · April 23, 2021, 12:30pm

17593, "JoyMonteiro", "Design input for model state", "2021-04-23T12:28:14Z"

Design input for model state

opened 12:28PM - 23 Apr 21 UTC

Hello, we are trying to design a data structure which would function as model… state for a climate model. We have an implementation in Python currently (https://sympl.readthedocs.io), but would like to shift to Chapel to take advantage of multi-locale execution. The requirement is as follows: * Each model component takes a model state which is currently a dictionary with strings as keys and a labeled array container (DataArray) as value * DataArrays contain an array of arbitrary type (we could restrict it to int, real and string) * The component extracts arrays that are relevant to it (not all may be relevant) and uses these arrays to perform some computations * Components behave like functions which take model state as input and provide a similar state variable with tendencies or new model state In Python, the model state is simply a dictionary and it works fine. However, a key-value store does not seem the ideal approach in Chapel because of typing issues (DataArray is a generic). Just to give you an idea of the current design and how it is used, `state` is the model state here: https://github.com/CliMT/climt/blob/2f03b11e2c44f454ca3f353d61c0ad9ffc27fcd2/examples/ice_sheet.py#L8 Is there some Chapel feature/ibrary that we are missing that could make this easy for us? TIA, Joy

Hello,

we are trying to design a data structure which would function as model state for a climate model.

We have an implementation in Python currently (https://sympl.readthedocs.io), but would like to shift to Chapel to take advantage of multi-locale execution.

The requirement is as follows:

Each model component takes a model state which is currently a dictionary with strings as keys and a labeled array container (DataArray) as value
DataArrays contain an array of arbitrary type (we could restrict it to int, real and string)
The component extracts arrays that are relevant to it (not all may be relevant) and uses these arrays to perform some computations
Components behave like functions which take model state as input and provide a similar state variable with tendencies or new model state

In Python, the model state is simply a dictionary and it works fine. However, a key-value store does not seem the ideal approach in Chapel because of typing issues (DataArray is a generic).

Just to give you an idea of the current design and how it is used, state is the model state here:

github.com

CliMT/climt/blob/2f03b11e2c44f454ca3f353d61c0ad9ffc27fcd2/examples/ice_sheet.py#L8


import climt
from datetime import timedelta
from sympl import PlotFunctionMonitor




ice = climt.IceSheet(maximum_snow_ice_height=30.)


state = climt.get_default_state([ice])
state['area_type'].values[:] = 'sea_ice'
state['sea_ice_thickness'].values[:] = 5.
state['surface_snow_thickness'].values[:] = 4.
state['surface_temperature'].values[:] = 260.
state['surface_upward_sensible_heat_flux'].values[:] = -0.5




def plot_function(fig, model_state):
    ax = fig.add_subplot(1, 1, 1)
    ax.plot(model_state['snow_and_ice_temperature'].values.squeeze(),

Is there some Chapel feature/ibrary that we are missing that could make this easy for us?

TIA,
Joy

Topic		Replies	Views
Design input for model state Users	25	743	May 20, 2021
Design input for units library Users	23	555	January 5, 2022
Announcing Chapel 1.24.0! Announcements	0	605	March 18, 2021
Multi-Dimensional Array Initialization Users	1	247	December 19, 2021
New chapel questions for Jan 15 - Stack Exchange Stack Overflow	0	278	January 15, 2021

External Issue: Design input for model state

Related Topics