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

Wrong io stream specified in ndown code #1907

Open
sael9740 opened this issue Aug 3, 2023 · 1 comment
Open

Wrong io stream specified in ndown code #1907

sael9740 opened this issue Aug 3, 2023 · 1 comment

Comments

@sael9740
Copy link
Contributor

sael9740 commented Aug 3, 2023

When attempting to run ndown it was failing with messages like the following:

  ndown_em main: calling open_r_dataset for wrfout_d01_2023-08-02_00:00:00
   NetCDF error: No such file or directory
   NetCDF error in wrf_io.F90, line         1077
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     307
program ndown: error opening wrfout_d01_2023-08-02_00:00:00 for reading ierr=   -1021
-------------------------------------------

This was baffling since the file was clearly there. Note that I specified io_form_auxinput2 = 2 in my namelist. I eventually found that although the debug messages indicated that ndown was trying to open the wrfout_d01_2023-08-02_00:00:00 file it was actually attempting to open the wrfout_d01_2023-08-02_00:00:00_0000 file, which would be the filename for rank 0 if I had set io_form_auxinput2=102. After digging into the code a bit I found that it was specifying DATASET=AUXINPUT1 in the open_r_dataset call:

CALL open_r_dataset ( fid, TRIM(eligible_file_name(file_counter)) , head_grid , config_flags , "DATASET=AUXINPUT1", ierr )

I just happened to have specified io_form_auxinput1 = 102 for this test case, which explains why I ran into this issue.

Changing the DATASET=AUXINPUT1 to DATASET=AUXINPUT2 fixes the issue. I can create a pull request sometime next week for this.

@dudhia
Copy link
Collaborator

dudhia commented Aug 3, 2023

Thanks for providing not only the problem but also the solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants