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

Bug: interp_sigma_to_hybrid and WRF_Chem output #241

Closed
anissa111 opened this issue Sep 2, 2022 · 4 comments
Closed

Bug: interp_sigma_to_hybrid and WRF_Chem output #241

anissa111 opened this issue Sep 2, 2022 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@anissa111
Copy link
Member

Hi @erogluorhan , sorry for the late response. It took me some time before I could test interp_sigma_to_hybrid. However, I am facing two difficulties in using this file for WRF_Chem output

  1. With the current implementation, it seems not possible to interpolate concentration fields directly. By default, the concentration fields have units of ppm which are not recognised by metpy. We need to convert the units into something that metpy recognizes (e.g. molecules cm-3). See the discussion here.
  2. The current implementation is very slow as compared to ncl. For example, I am interpolating my WRF-Chem absolute humidity fields on TM5 grid. While with ncl, on my machine it took me less than 1 second, with interp_sigma_to_hybrid it took me more than 200s. For your reference, I have attached my ncl script, python scripts and a sample data file here.

Best regards and thanks a lot,
Vinod

Originally posted by @vinodkatmos in #142 (comment)

@anissa111 anissa111 added the bug Something isn't working label Sep 2, 2022
@anissa111 anissa111 assigned hCraker and unassigned erogluorhan Oct 7, 2022
@anissa111
Copy link
Member Author

@vinodkatmos, just wanted to give you an update on this issue you submitted.

  1. I'm not entirely sure where the best location for this unit change would occur. If possible, could you point me to metpy's implementation or a usage example so I could better understand?
  2. We will definitely be looking into optimizing this (and other!) functionality in the near future. This issue should provide links to that progress when it occurs.

Thank you again for taking the time to provide feedback to our project!

@anissa111
Copy link
Member Author

I'm going to close this issue, as the performance issues will be included in a different issue shortly.

@erogluorhan
Copy link
Collaborator

Hey @anissa111 it was closed on Feb 21 but is now assigned to me. I am happy to look into it but just wanted to understand correctly if the intent is actually to work on this now.

@anissa111
Copy link
Member Author

Oh, whoops! I think this was a mis-click while trying to archive it in our PL meeting yesterday my bad!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants