[Dart-dev] DART/branches Revision: 13169

[dart at ucar.edu]

mizzi at ucar.edu
2019-05-09 08:40:33 -0600 (Thu, 09 May 2019)
50
Final file clean for the WRF-Chem/DART release.





Copied: DART/branches/mizzi/README_WRF-Chem_DART_BUILD_RUN_INSTRUCTIONS (from rev 13168, DART/branches/mizzi/README_WRFCHEM_BUILD_RUN_INSTRUCTIONS)
===================================================================
--- DART/branches/mizzi/README_WRF-Chem_DART_BUILD_RUN_INSTRUCTIONS	                        (rev 0)
+++ DART/branches/mizzi/README_WRF-Chem_DART_BUILD_RUN_INSTRUCTIONS	2019-05-09 14:40:33 UTC (rev 13169)
@@ -0,0 +1,144 @@
+This file contains instructions for building and running the WRF-Chem/DART 
+release and test case.
+
+INTRODUCTION:
+
+The WRF-Chem/DART release is a "cleaned-up" version of my working/development
+directories.  As such, it is set up to run the WRF-Chem/DART test case with a
+minimum amount of effort: some user changes to adapt the compiler, mathematical 
+libraries, and ksh scripts to your local system will be necessary. At present,
+the Intel compiler has been tested and there are some routines that require the
+Intel Math Kernel Libraries.
+
+Since it is my working directory the distribution includes code that works and
+is tested, code that runs but has not been tested, and code that simply does
+not work yet. Once you have the test case running and want to test other features 
+of WRF-Chem/DART you should contact me at mizzi at ucar.edu to find out the 
+status of such features.
+
+If you have questions about WRF-Chem/DART you should contact me because there
+is not yet a Users Guide.  If your questions are more closely related to DART 
+you should contact DART support at dart at ucar.edu.  In the event your question
+is WRF-Chem/DART related they will pass it along to me.
+
+Once WRF-Chem is built and you are able to run the test case, I suggest you
+work through the run script to learn how it is structured and to learn the
+steps/tasks that are required for regional ensemble chemical weather
+forecasting/data assimilation. Once you understand the flow of the run
+script you will be in a position to make modifications and start your
+experiments.  Here again, I suggest you discuss your intended modifications
+and experiments with me in advance.  This is an unfortunate result of not
+having a Users Guide, but it has worked well for the existing users.
+
+FUNDING/SUPPORT:
+
+The WRF-Chem/DART project began in mid-2012 as a cooperative effort at the 
+National Center for Atmospheric Research (NCAR) between the Data Assimilation 
+Research Section (DAReS) and the Atmospheric Chemistry Observations and Modeling 
+Laboratory (ACOM) based on funding from the National Science Foundation (NSF) and 
+the National Aeronautics and Space Administration (NASA).  In mid-2017, ACOM's 
+support for this project ceased.  Currently, WRF-Chem/DART is supported by the 
+Colorado Department of Public Health and Environment/Air Pollution Control Division 
+(CDPHE/APCD), the University of Colorado Department of Mechanical Engineering (CUME) 
+and Research Computing Program (CURC), and DAReS.  In addition WRF-Chem/DART 
+contributions have been made by the: York University, University of California at 
+Berkeley, Nanjing University, University of Colorado, and University of Arizona.
+
+BUILD INSTRUCTIONS:
+
+1. In this discussion "../" will refers to your DART home directory.
+Also, it assumes that you have DART, WRF-Chem, WPS, and WRFDA built and
+running on your system.
+
+2. Go to the "../mkmf" directory, copy the appropriate
+"mkmf.template.compiler_type.etc" into "mkmf.template", and modify/adapt
+"mkmf.template" to your system.
+
+3. Go to "../models/wrf_chem/work" and run "./quickbuild.csh". If this
+step completes successfully, you should have some 30 WRF-Chem/DART
+executables in this "work" directory.
+
+4. Go to "../observations" and run "./buildall.csh".  This will build the
+observation converters, which convert observations from their native format
+to DART format.  If this step completes successfully you should have
+observation converter executables in the observation type "work" directories.
+NOTE: "buildall.csh" is configured to build the observation converters commonly
+used in WRF-Chem/DART.  If you want other observation converters, you will
+need to build them manually or modify "buildall.csh" to add them to the build
+list.
+
+5. Go to "../models/wrf_chem/run_scripts" and run "./buildall.csh".  This
+will build the WRF-Chem/DART support utilites.  If this step completes
+successfully, you should have WRF-Chem/DART utility executables (indicated by
+a ".exe" extension) in the utility "work" directory.  "buildall.csh" will
+build all WRF-Chem/DART utility executable existing as of the date of this
+release.  However, WRF-Chem/DART does not use all these executables because
+some are under development and some are legacy software.
+
+6. Go to "../models/wrfchem/hybrid_scripts" and modify the
+"da_run_hold_cu.ksh" and "job_script_summit.ksh" scripts for your system.
+"da_run_hold_cu.ksh" is used by the run script to test whether all ensemble
+members have completed computing on a specific task.
+"job_script_summit.ksh" is the batch job submission script. It has "SERIAL"
+and "PARALLEL" job submission options.  It will likely need to be modified to
+accomodate your particular job scheduler/load manager.
+
+7. Go to "../models/wrf_chem/runs_scripts/RUN_REAL/FINAL_TEST_SCRIPTS" and
+edit the "real_time_PANDA_RETR_RELEASE_TEST_CU.ksh" script for your system.
+The is the test case run script.  You will need to edit: 
+ (i) "CODE VERSIONS" variables to match your code version and identifiers; 
+ (ii) "ROOT DIRECTORIES" variables to match the root paths on your system.  
+      You should not need to change the "DEPENDENT INPUT DATA DIRECTORIES" variables; 
+ (iii) For now, you should not need to change the "SELECT COMPONENT RUN OPTIONS" variables, 
+       but remember this section because these switches control the various job
+       submission tasks in WRF-Chem/DART; 
+ (iv) You may need to change the "COMPUTER PARAMETERS" to match the options 
+      you set in "job_script_summit.ksh" for your particular scheduler/load manager;