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

adding --netcdf4 option to ESMF_Regrid (option already available using CLT ESMF_RegridWeightGen) #264

Closed
jvmcgovern opened this issue Jul 22, 2024 · 7 comments
Assignees
Labels
closed: wontfix This will not be worked on

Comments

@jvmcgovern
Copy link

Hi there,

I recently identified an issue where when I was interpolating to a large output netcdf, the .log file would indicate that I never got the line "Finalizing ESMF".

Is it possible to add netcdf4 capability to the ESMF_Regrid CLT options as with ESMF_RegridWeightGen?

Best regards

@anntsay
Copy link

anntsay commented Dec 11, 2024

it seems that the code touch many places,

@billsacks
Copy link
Member

it seems that the code touch many places,

Finishing that comment: we felt last week that this would be too large of a change to make it into the upcoming 8.8 release. But we plan to at least get it into 8.9.

Thank you for reporting this, @jvmcgovern .

@billsacks
Copy link
Member

@jvmcgovern I have been looking into this today. I do not have experience using ESMF_Regrid myself, so I may be missing something here, but I think that the different behavior of ESMF_Regrid means that this argument is unnecessary. Specifically: It looks like the typical operation of ESMF_Regrid is to provide an existing destination grid file, and then ESMF_Regrid adds a variable to this existing file. (This is in contrast with ESMF_RegridWeightGen, where a new file is created.) Does that sound right to you in your use case?

If so, I think the solution is to change the file type of the destination file before running ESMF_Regrid. This can be done, for example, with the NetCDF Operators (NCO) tool nccopy:

nccopy -k nc4 original.nc new.nc

Please let us know if this will resolve your issue.

@billsacks
Copy link
Member

I'm going to close this as a wontfix based on the comment above, but @jvmcgovern feel free to comment and reopen if you feel this hasn't resolved your issue.

@billsacks billsacks closed this as not planned Won't fix, can't repro, duplicate, stale Dec 18, 2024
@billsacks billsacks added the closed: wontfix This will not be worked on label Dec 18, 2024
@jvmcgovern
Copy link
Author

@jvmcgovern I have been looking into this today. I do not have experience using ESMF_Regrid myself, so I may be missing something here, but I think that the different behavior of ESMF_Regrid means that this argument is unnecessary. Specifically: It looks like the typical operation of ESMF_Regrid is to provide an existing destination grid file, and then ESMF_Regrid adds a variable to this existing file. (This is in contrast with ESMF_RegridWeightGen, where a new file is created.) Does that sound right to you in your use case?

If so, I think the solution is to change the file type of the destination file before running ESMF_Regrid. This can be done, for example, with the NetCDF Operators (NCO) tool nccopy:

nccopy -k nc4 original.nc new.nc

Please let us know if this will resolve your issue.

Hi @billsacks , this is an interesting work-around which I hadn't thought of. I won't have time to trial this as a solution until the new year. If it works, then it would be great to have the recommendation added to the ESMF documentation.

Season's greetings,
Joe

@billsacks
Copy link
Member

Thanks for the reply @jvmcgovern . Yes, it would be great to have your confirmation that this solves your problem whenever you get a chance to test it. Once you do, I agree that we should document this, and I'm happy to do so.

@jvmcgovern
Copy link
Author

jvmcgovern commented Dec 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants