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

Met reads for passive tracer sims, do we pull in more met fields than needed? #2722

Open
aschuh opened this issue Feb 10, 2025 · 1 comment
Labels
category: Question Further information is requested topic: Input Data Related to input data

Comments

@aschuh
Copy link

aschuh commented Feb 10, 2025

Your name

Andrew Schuh

Your affiliation

Colorado State University

Please provide a clear and concise description of your question or discussion topic.

I'm not sure if the model pulls ALL met fields in from the driving met files during the simulation, I'm guessing YES. I'm curious, if one is only running passive tracers, you need U, V, CMFMC, etc, but I'm guessing there are a lot of fields,particularly 3D, that are not needed? Is anyone aware of how this partitions, which fields wouldn't be needed? and whether there would be a way to put a switch in to control this? The met reads are the majority of the time spent running the model. Reading in 50% of the fields shoudl essentially half the run time?

Any thoughts on this?

andrew

@aschuh aschuh added the category: Question Further information is requested label Feb 10, 2025
@msulprizio
Copy link
Contributor

Yes, this has been on the GCST's wish list to evaluate the met fields needed for each simulation type and only read/allocate the necessary fields. We just haven't gotten to it. See related issue:

@yantosca yantosca added the topic: Input Data Related to input data label Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Question Further information is requested topic: Input Data Related to input data
Projects
None yet
Development

No branches or pull requests

3 participants