Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Save KPP global variables into a derived type object #11

Open
yantosca opened this issue Oct 13, 2021 · 1 comment
Open
Labels
code / structural Related to structural source code updates feature New feature or request future development Items that will be worked on in the future
Milestone

Comments

@yantosca
Copy link
Contributor

This would be for much later down the road. Right now KPP global variables are referenced by F90 USE statements. But there may be some model implementations (such as in WRF) where several chemistry domains get solved simultaneously. For such a case like that, it would be preferable to have all KPP-generated module variables stored in a F90 derived type object so that the model could instantiate as many instances of the object as there are chemistry domains being solved simulataneously.

This would be a "nice to have" but is not a high priority. I just wanted to list this here so that we don't lose sight of it.

@yantosca yantosca added feature New feature or request code / structural Related to structural source code updates labels Oct 13, 2021
@RolfSander RolfSander added this to the 4.0.0 milestone May 23, 2022
@jimmielin jimmielin mentioned this issue Jul 6, 2022
@jimmielin
Copy link
Member

Looks like this feature will be useful for MATLAB as well (see #45) as suggested by @JPSTUTZ.

We can move towards using structure arrays for MATLAB, which is the equivalent for derived types.

@yantosca yantosca added the future development Items that will be worked on in the future label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code / structural Related to structural source code updates feature New feature or request future development Items that will be worked on in the future
Projects
None yet
Development

No branches or pull requests

3 participants