The ParametricGrid and ParaGridIO classes need to be able to store information about the grid somewhere. Currently, the information is stored in the restart file and read by a python script to create the smesh file for the dynamics. On reading the data into the model, all the longitude and latitude information is ignored. When the final restart file is created, the information is unavailable, so that a model written restart file is not equivalent to one generated by the python scripts.
The data then needs to be stored somewhere. But where? Some kind of singleton or static storage would make sense: the running model can only have one grid definition at a time. The Model class certainly handles enough gridded data (at one remove) that rooting the information here might make sense. But other classes should not have to refer to Model to get grid data (or anything, preferably).
The
ParametricGridandParaGridIOclasses need to be able to store information about the grid somewhere. Currently, the information is stored in the restart file and read by a python script to create thesmeshfile for the dynamics. On reading the data into the model, all the longitude and latitude information is ignored. When the final restart file is created, the information is unavailable, so that a model written restart file is not equivalent to one generated by the python scripts.The data then needs to be stored somewhere. But where? Some kind of singleton or static storage would make sense: the running model can only have one grid definition at a time. The
Modelclass certainly handles enough gridded data (at one remove) that rooting the information here might make sense. But other classes should not have to refer to Model to get grid data (or anything, preferably).