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

The output file rads.64.nc contails only zero values #181

Open
sarriegi opened this issue Jan 19, 2024 · 10 comments
Open

The output file rads.64.nc contails only zero values #181

sarriegi opened this issue Jan 19, 2024 · 10 comments

Comments

@sarriegi
Copy link

Hello, in all my ADCIRC-WW3 runs the output file rads.64.nc file contains only zero values. I have checked that the wave coupling works normally (the significant wave height values are normal and the water level values are different compared to the ADCIRC standalone run). So it seems that it's just an output issue. My fort.15 file looks like this:
.
image
Do you have any idea of what might be going wrong?

Angelos

@pvelissariou1 @saeed-moghimi-noaa

@saeed-moghimi-noaa
Copy link
Collaborator

saeed-moghimi-noaa commented Jan 19, 2024

Hi @sarriegi

Please check adcirc cap, there might be a statement to overwrite that field. In that case you may comment those lines out otherwise you may dig deeper. @pvelissariou1 may have other suggestions.

Good luck,
-Saeed

@pvelissariou1
Copy link
Collaborator

@sarriegi Hi Angelos. I think that ADCIRC writes the wave data to rads.64 only when swan is compiled with adcirc (e.g., adcswan). Can you share your fort.15 file?

@sarriegi
Copy link
Author

Thank you for your responses @saeed-moghimi-noaa and @pvelissariou1 ! I am attaching the fort.15 file.

Angelos
fort15.txt

@sarriegi
Copy link
Author

Hello @saeed-moghimi-noaa, I found these lines that concern the rads.64.nc file:
image
And
image
Do you know what should I do? Should I uncomment the two ALLOCATE lines in the first picture? Or set the flag in the second picture? Or neither?

Angelos

@pvelissariou1
Copy link
Collaborator

@sarriegi I don't think you can achieve anything by modyfing the ADCIRC code as is. I believe that data in the rads.64 file are written when CSWAN is active (I didn't go through the code thoroughly). The file is generated but fields are not written. In your case the radiation stresses are produced outside SWAN. An approach is to dump the ESMF fields fron the NUOPC cap. Saeed has implemented a "dump" option for the exported fields. Can you look at this in the NUOPC cap?

@sarriegi
Copy link
Author

Hello @pvelissariou1 , the only file I see a mention of rads.64 (with 'grep -R rads.64') is the write_output.F file of ADCIRC. The dump option would be in adc_cap.F90?

Angelos

@pvelissariou1
Copy link
Collaborator

@sarriegi Yes the dump option is in adc_cap.F90 and in the subroutine State_GetFldPtr_
For your radiation stresses (sxx,syy,sxy) you call in adc_cap.F90 you have:
call State_getFldPtr_(ST=importState,fldname='sxx',fldptr=dataPtr_sxx, &
rc=rc,dump=.false.,timeStr=timeStr)
Try dump=.true.
for syy and sxy stress blocks switch State_getFldPtr to State_getFldPtr_ to get the "dump" option.
Play with these to see what happens

@sarriegi
Copy link
Author

Thank you so much!

Angelos

@sarriegi
Copy link
Author

Hello @pvelissariou1 and @saeed-moghimi-noaa, I wanted to let you know that I was able to get the rads.64.nc to show non-zero values, by modifying the ADCIRC/src/timestep.F file. More specifically, I modified the IF stametemtn in line 698:
image
Adding the .OR. ABS(NRS).EQ.5 to the IF statement.

Thank you so much for your help!

Angelos

@pvelissariou1
Copy link
Collaborator

@sarriegi Great, thank you for letting us know.

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

3 participants