#!html
<h1  style="text-align: center; color: green">APS2 Build Documentation</h1>

#!html
<h2  style="text-align: center; color: red">  LEGACY: THIS PAGE IS NO LONGER ACTIVELY MAINTAINED </h1>

PageOutline

WG meeting notes (Aug. 5 2015)

WG will start to build executables for APS3. Ilia will provide recommendation for modules to be used.

** Aug 6 -- Aug 20, 2015 **

• Susan and Xiao & Ilia have built VAR32 executable from shared repo. Changes are to be reviewed by UKMO.
• Vinod is working on building SURF from a pre-released SURF package (version 31.XX?)
  • SURF will not be on the shared repo before the end of Sep. 2015.
• Zhihong and Xiao are looking into building OPS32 exe.
• Tan and Jin worked on ODB installation.

Aug 20 2015

• Updated and tested G2 executable to use I/O services (Ilia & Xiao)

  • Current timing at R & D is ~ 52 minutes for a 10 days forecast. Results are identical.
  • The UM repo and build script are updated (under nwp svn), and passed to BNOC

• Updated R2 UM and build script (Ilia & Xiao)

  • Remove the reference to Jorge's directory

• Discovered a problem in frame exe (Wenming, Zhihong, Xiao)

  • Action: Wenming to find out the source differences between APS1 and APS2 from Martin, and rebuild the frame exe.

• Updated OPS repo and build script for using updated odb module from /apps/odb (Zhihong & Xiao)

• Rebuilt APS1-G Um executable for a bug fix (Ashley & Ilia)

  Fixed code is under https://access-svn.nci.org.au/svn/um/branches/local/vn7.5_aps1_global_memfix

  executable is /g/sc/data/azs/bld_aps1/lsrc/ummodel/bin/bld_aps1.exe

  To be tested by BNOC

Remaining executables for APS2: GE2 executables are not currently under this working group's control. They were built within GE WG.

• ** There is no clear requirement so far **. We sent out a couple of emails in August, again in November. No response so far.

• Group discussion outcome:

  • Current scope of build executable is for NWP transition and HPC porting.

  • ** Each project should have a special directory under svn for the build script to refer to. **

    The special directory is ** $project/branches/local/$version ** For example, source code for APS2-G (vn8.2-n512) will be at

    • um/branches/local/vn82-aps2-n512
      (are we going to do the same for Jules and gcom that UM use? I think we should)

  • For UM, the special directory is manually created to contain sources from all used branches and patches when the executable was built. Only one instance of each file will be in this special branch.

  • For GEN family (OPS/VAR/SURF), an additional directory **extras ** was created to host sources that are not native to the project itself. For example, in OPS, we have

              * ops/branches/local/ops30.0.0  
    
              * ops/branches/extras/30.0.0    
    

  • A build script should refer to a specific revesion number under svn, not the head of the branch.

  • A build script requires a single input to define where the extracted source code will be.

    The script will extract source code from svn, create a ** build ** directory, and then build the executables into ** build/bin ** directory.

  • All build scripts should be cross check among the group.

  • run scripts will be created for most NWP related executables. Test data and results will be saved. They are to be used for verifying executables that are produced by build scripts.

    Please refer to the specific run script for its usage.

  • build scripts and run scripts will be moved to more suitable location at the end of this activity.

The executable is built using ~access/nwpdir/share/APS/scripts/build_scripts/build_n512_8.2.ksh build script based on ~access/nwpdir/share/APS/scripts/build_scripts/build_um.ksh.

Usage: build_n512_8.2.ksh <build_dir>

where build_dir – directory in which the build will be produced.

The corresponding testing job is /access/nwpdir/share/APS/scripts/run_jobs/R_aps2_n512 and instructions on how to run this job are provided in a README file located in the same as the job directory /access/nwpdir/share/APS/scripts/run_jobs.

The executable is built using ~access/nwpdir/share/APS/scripts/build_scripts/build_r12_8.4.ksh build script based on ~access/nwpdir/share/APS/scripts/build_scripts/build_um.ksh.

Usage: build_r12_8.4.ksh <build_dir>

where build_dir – directory in which the build will be produced.

The corresponding testing job is /access/nwpdir/share/APS/scripts/run_jobs/R_aps2_r12 and instructions on how to run this job are provided in a README file located in the same as the job directory /access/nwpdir/share/APS/scripts/run_jobs.

The executable is built using ~access/nwpdir/share/APS/scripts/build_scripts/ build_c1.5_8.2.ksh build script based on ~access/nwpdir/share/APS/scripts/build_scripts/build_um.ksh.

Usage: build_c1.5_8.2.ksh <build_dir>

where build_dir – directory in which the build will be produced.

Note:This script build_c1.5_8.2.ksh has been updated to contain Yimin/s wind gust fix. See http://ngamai04:8011/APS1/wiki/aps2_c_exe_log at 5.Wind gust fix provided by Yimin.

The corresponding testing job is /access/nwpdir/share/APS/scripts/run_jobs/R_aps2_vt for the Vic-Tas domain and the instructions on how to run this job are provided in a README file located in the same as the job directory /access/nwpdir/share/APS/scripts/run_jobs.

• Include test run script
• Add to ~access/nwpdir/share/APS/scripts/build_scripts

• The script for building ops30.0.0 is * ~access/nwpdir/share/APS/scripts/build_scripts/build_ops_30.0.0 *

  Usage : build_ops_30.0.0 $SRC

  The script extracs source code into $SRC/src, then build executables into $SRC/build/build/bin

• A run script for testing OPS executable is * ~access/nwpdir/share/APS/scripts/run_scripts/run_ops30.0.0.ksh * pending check

• Sample outputs are under ~access/data/testdata/ops30.0.0/results pending check the run script

  identical results are expected if same inputs (~access/data/testdata/ops30.0.0/input) are used.

• The script for building var30.0.0 global is * ~access/nwpdir/share/APS/scripts/build_scripts/build_var_30.0.0*

  Usage : build_var_30.0.0 $SRC

  The script extracs source code into $SRC/var30.0.0/src, then build executables into $SRC/var30.0.0/build/bin

• A run script for testing AnalysisPF is * ~access/nwpdir/share/APS/scripts/run_scripts/run_var_n216.ksh *

• Sample outputs are under ~access/data/testdata/var216/results

  identical results are expected if same inputs (saved) are used.

• Include test run script
• Add to ~access/nwpdir/share/APS/scripts/build_scripts

• see http://ngamai04.bom.gov.au:8011/APS1/wiki/ACCESS_GE2G2_HandOver_Document#Howtobuildexecutablesusedinaccess_gesuites

• Build SURF18.5.1 script is ~access/nwpdir/share/APS/scripts/build_scripts/build_surf_18.5.1

  Usage: build_surf_18.5.1 $SRC

  The script extracs source code into $SRC/surf18.5.1, then build executables into $SRC/surf18.5.1/build/bin

• Run scripts are under ~access/nwpdir/share/APS/scripts/run_scripts

  • run_surf_sst.ksh for sst reconfiguration.

  • run_surf_smng.ksh for soil moisture nudging.

  • run_surf_sman.ksh for soil moisture analysis

• Sample outputs -- to be used for checking your executable. You should get identical results with saved sample outputs below.

  • ~access/data/testdata/surf_sst for sst

  • ~access/data/testdata/surf_sman for soil moisture analysis

  • ~access/data/testdata/surf_smng for soil moisture nudging

• Yi Xiao
• Asri Sulaiman
• Ilia Bermous
• Wenming
• Tan Le
• Zhihong

-> Back to main Access NWP Build Procedure Page

[WikiStart -> Back to Main access page ]

--> APS Executables Portal On ngamai04 NWP-WG (APS1) trac wiki (BoM Internal Only).

--> NWP UM Build Procedure Draft (Ilia's email 8/8/13)

--> Back to NWP-WG (APS1) wiki (BoM Internal Only).

• Intel_software.docx