Various syntax fixes found by FPT tool (static Fortran analysis mode)#1253
Various syntax fixes found by FPT tool (static Fortran analysis mode)#1253davegill merged 4 commits intowrf-model:release-v4.2.1from
Conversation
|
@davegill |
|
@JCollinsSimCon This validates that your code did no irreparable harm to the repository, as far as we can tell. |
|
Please find result of the WRF regression test cases in the attachment. This build is for Commit ID: 6cf16be, requested by: JCollinsSimCon for PR: #1253. For any query please send e-mail to David Gill. |
|
@davegill |
|
John,
Thanks, I'll look soon
Dave
…On Tue, Jul 14, 2020 at 12:19 AM JCollinsSimCon ***@***.***> wrote:
@davegill <https://github.com/davegill>
Assuming that module_fr_fire_phys.F has already been taken care of, I
believe we have all of the files we need for WRF_fpt_regression -
dyn_em/module_first_rk_step_part1.F, frame/Makefile,
external/io_grib2/bacio-1.3/bacio.F, phys/module_bl_mynn.F. Am I right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1253 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADAUK6R5VZKXTEH72NZOUTDR3P2HZANCNFSM4OYV52GQ>
.
|
|
@joeolson42 @weiwangncar @dudhia |
modified: frame/Makefile
|
@JCollinsSimCon You may now stand down. |
TYPE: New feature
KEYWORDS: Static analysis, regression testing
SOURCE: John Collins (SimCon / Edge Hill University)
CHANGES:
The WRF code has a large number of nonstandard constructs that have been in the code for a while. Part of the capability
of the FPT static analysis tool is to discover noncompliant Fortran syntax and usage.
The bugs are removed.
configuration processing are no longer removed by the Makefile. This was not a bug, but the static analyzer needs
the cpp manufactured code to continue to exist.
This PR represents an initial step. Once the WRF code is suitable for automatic use by FPT, then a second PR will
introduce the required exemplar files for comparison. That step, which insures no additional nonstandard Fortran
constructs or usages are introduced, will eventually be part of the jenkins testing.
MODIFIED FILES:
dyn_em/module_first_rk_step_part1.F
external/io_grib2/bacio-1.3/bacio.F
frame/Makefile
cleanscriptphys/module_bl_mynn.F
TESTS CONDUCTED:
RELEASE NOTE: Changes to implement static analysis regression testing of WRF. Please see:
http://simconglobal.com/WRF_Workshop_June_2011_Poster_Automatic_Detection_of_Software_Errors_in_WRF.pdf
http://simconglobal.com/WRF_Workshop_June_2012_Poster_QA_Analysis_of_the_WRF_Program.pdf
http://simconglobal.com/collins_et_al_2013_automated_quality_assurance_analysis_wrf_a_case_study.pdf