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

Removing some debug-level prints from RRTMG lw #3

Merged
merged 2 commits into from
Sep 16, 2016

Conversation

dudhia
Copy link
Collaborator

@dudhia dudhia commented Sep 15, 2016

TYPE: no impact

KEYWORDS: remove some debug-level prints

SOURCE: internal

DESCRIPTION OF CHANGES:
Debug-level 150 prints were printing at too many grid points, and are not useful.
These will be commented out.

LIST OF MODIFIED FILES :
phys/module_ra_rrtmg_lw.F
phys/module_ra_rrtmg_lwf.F

TESTS CONDUCTED:
None.

@jamiebresch
Copy link
Contributor

Will the prints be useful in any case?
If yes, then maybe set a higher debug level for it?
If no, why not simply remove the code.

@dudhia
Copy link
Collaborator Author

dudhia commented Sep 15, 2016

I can't think of any use for these prints because it is the same
information for every grid point.
I can see a case for deleting them.
Jimy

On Thu, Sep 15, 2016 at 2:31 PM, Jamie Bresch [email protected]
wrote:

Will the prints be useful in any case?
If yes, then maybe set a higher debug level for it?
If no, why not simply remove the code.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#3 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARGf_B-hGPDjJaBNDnhbjA1o5DKa0u39ks5qqaspgaJpZM4J-DO6
.

@@ -12018,10 +12018,10 @@ SUBROUTINE RRTMG_LWRAD( &
!Mukul change the flags here with reference to the new effective cloud/ice/snow radius
IF (ICLOUD .ne. 0) THEN
IF ( has_reqc .ne. 0) THEN
IF ( wrf_dm_on_monitor() ) THEN
WRITE(message,*)'RRTMG: pre-computed cloud droplet effective radius found, setting inflglw=3'
call wrf_debug(150, message)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Jimy,
These are already at level 150, and they are formatted exactly as we ask people to do. Do these messages appear to often when the debug level is set to 150 (as in every time through the scheme)? Hardly anyone runs with debug this high, so these messages should not be problematic for most people.
Dave

@dudhia
Copy link
Collaborator Author

dudhia commented Sep 16, 2016

Yes, it is almost every grid point.

On Fri, Sep 16, 2016 at 12:53 PM, Dave Gill [email protected]
wrote:

@davegill commented on this pull request.

In phys/module_ra_rrtmg_lw.F
#3 (review):

@@ -12018,10 +12018,10 @@ SUBROUTINE RRTMG_LWRAD( &
!Mukul change the flags here with reference to the new effective cloud/ice/snow radius
IF (ICLOUD .ne. 0) THEN
IF ( has_reqc .ne. 0) THEN

  •           IF ( wrf_dm_on_monitor() ) THEN
    
  •             WRITE(message,*)'RRTMG: pre-computed cloud droplet effective radius found, setting inflglw=3'
    
  •             call wrf_debug(150, message)
    

Jimy,
These are already at level 150, and they are formatted exactly as we ask
people to do. Do these messages appear to often when the debug level is set
to 150 (as in every time through the scheme)? Hardly anyone runs with debug
this high, so these messages should not be problematic for most people.
Dave


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#3 (review), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARGf_Arwnwf5a9UvuGOgK2PnWaf9w16Zks5qquW9gaJpZM4J-DO6
.

@mkavulich
Copy link
Contributor

Developer's committee requests deleting these lines instead of commenting them out.

@dudhia dudhia merged commit ba46355 into wrf-model:master Sep 16, 2016
mkavulich referenced this pull request in mkavulich/WRF Oct 27, 2016
TYPE: no impact

KEYWORDS: remove some debug-level prints

SOURCE:  internal

DESCRIPTION OF CHANGES:
Debug-level 150 prints were printing at too many grid points, and are not useful.
These will be deleted.

LIST OF MODIFIED FILES :
phys/module_ra_rrtmg_lw.F
phys/module_ra_rrtmg_lwf.F

TESTS CONDUCTED:
None.

(cherry picked from commit ba46355)
BinLiu-NOAA pushed a commit that referenced this pull request Nov 17, 2016
KEYWORDS: rebalance 

SOURCE: Katie Lundquist (LLNL)

PURPOSE: For vertical refinement, a rebalancing step reduces noise in both high resolution LES cases and in nested hurricane cases.

DESCRIPTION OF CHANGES: 
In module_dm.F, the intermediate domain is rebalanced after vertical interpolation.  Also, for consistency, the method of integrating the perturbation fields in start_em.F is used in the init for real.  The LES case gets the removal of the reciprocal 1/RDNW, and the option of which way to compute ALB.

LIST OF MODIFIED FILES (annotated if not obvious, not required to be on a single line): 
M	Registry/Registry.EM_COMMON
Add two new variables to the Registry namelist:

1) rebalance in namelist &domains
0=NO
1=always YES
2=only YES with vertical nesting

2) ideal_init_method in &domains, immpacts code in start_em.F
0=ALB from PHB (original)
1=ALB from T_INIT

M	dyn_em/module_initialize_les.F
1) swap blah/RDNW(k) for blah*DNW(k), two locations

M	dyn_em/module_initialize_real.F
1) Test if the rebalance option is switched on.  If so, with the newly available Qv, recompute the pressure.

M	dyn_em/start_em.F
1) Do we do the rebalancing
2) Clean up the if test explanations a bit, and label the endif parts so we know what just happened in the code
3) swap the order of an if test and an OpenMP loop, no need to do an OpenMP loop if the if test is always going to be false.

M	external/RSL_LITE/module_dm.F
1) For vertical nesting, vertically interpolate for ideal cases on intermediate domain.
2) rebalance to get a new geopotential for vertical nesting

TESTS CONDUCTED (explicitly state mandatory, voluntary, and assigned tests, not required to be on a single line):
1) Regression test - do no harm
2) Katie did the summer and winter test cases, and sent along a PPT to review, without vertical refinement, no harm done.
3) Katie also conducted sensitivity tests using vertical refinement to show noise in both very-high resolution cases (LES), and in resolutions that others tend to use (1-10 km nested cases over flat terrain for huricanes).
4) Bit-wise identical results for ALMOST all non-vertically refined tests, these are the same bit-for-bit differences when comparing versions of the WRF code that modified diagnostic print statements only.
Total number of identical file tests: 1397
Total number of different file tests: 160
We expect all of the tests with vertical refinement to be different.  If we remove those from the list of diffs, then this is our list of failed bit-wise identical results:
List of bit-wise (before the mods vs after the mods) failures
TROUBLE, --->  the two wrf_9162.34/em_real/wrf_regression.namelist.input.65 wrfout_d01 files are different
TROUBLE, --->  the two wrf_9162.34/nmm_hwrf/wrf_regression.namelist.input.3 wrfout_d01 files are different
TROUBLE, --->  the two wrf_9162.54/em_real/wrf_regression.namelist.input.65NE wrfout_d01 files are different
TROUBLE, --->  the two wrf_9162.54/nmm_hwrf/wrf_regression.namelist.input.3 wrfout_d01 files are different
The HWRF test #3 is able to get bit-wise different answers with GNU 4.9.2 on repeated runs.  We never do a serial vs DM comparison for HWRF. Tests for the entire HWRF operational system are done only with Intel compilers, so the bit-wise diffs for non-Intel compilers is not really too much of a surprise.


git-svn-id: https://svn-wrf-model.cgd.ucar.edu/trunk@9163 b0b5d27b-6f0f-0410-a2a3-cb1e977edc3d
davegill added a commit that referenced this pull request May 7, 2018
TYPE: text only

KEYWORDS: version, fr3

SOURCE: internal

DESCRIPTION OF CHANGES:
Update the inc/version_decl file to indicate that this is the third friendly release, and we are getting CLOSE!

LIST OF MODIFIED FILES:
M          inc/version_decl

TESTS CONDUCTED:
1. Code compiles, good enough for this change.
davegill pushed a commit that referenced this pull request Mar 25, 2020
TYPE: bug fix

KEYWORDS: GOCART, settling

SOURCE: Stacy Walters (internal)

DESCRIPTION OF CHANGES: 
Put calculation of aerosol settling (variable = transfer_to_below_level) in layers > 1 
into IF/ELSE block that calculates gravitational settling for layer = 1.

LIST OF MODIFIED FILES: 
M chem/module_gocart_settling.F

TEST CONDUCTED:
Jenkins shows all tests PASS

**Compiled with debug option -check bounds**
_BEFORE FIX_: 2 indexes are OOB for l==1, 3rd dim of delz (> MAX) and 3rd dim of airden (0)

rsl.out.0000
 l/=1, calculting transfer_to_below_level =   3.153560196907218E-014
 l/=1, calculting transfer_to_below_level =   1.014890436929303E-012
 l/=1, calculting transfer_to_below_level =   2.118741307102124E-011
 l==1, still calculating transfer_to_below_level =
  = (temp_tc*vd_wk1)*((delz(i,j,l2)*airden(i,j,l))/(delz(i,j,l2+1)*airden(i,j,l-1)))
 l==1, index of airden(i,j,l-1) =            1           1           0
  and index of delz(i,j,l2+1) =            1           1          31
 but size of 3rd dim of delz  =           30
rsl.error.0000
forrtl: severe (408): fort: (2): Subscript #3 of the array DELZ has value 31 which is greater than the upper bound of 30

_AFTER FIX_: 
l/=1, calculating transfer_to_below_level =   3.153560196907218E-014
 l/=1, calculating transfer_to_below_level =   1.014890436929303E-012
 l/=1, calculating transfer_to_below_level =   2.118741307102124E-011
 l==1, not calculating transfer_to_below_level
dmey referenced this pull request in TEB-model/wrf-teb Mar 31, 2020
@dwongepa dwongepa mentioned this pull request Mar 14, 2021
davegill added a commit to MicroTed/WRFV4 that referenced this pull request Sep 16, 2021
twjuliano pushed a commit to twjuliano/WRF that referenced this pull request Jun 13, 2022
@weiwangncar weiwangncar mentioned this pull request Oct 4, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
fengggli pushed a commit to fengggli/WRF that referenced this pull request Nov 9, 2022
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

Successfully merging this pull request may close these issues.

4 participants