2010-10-07 03:00:07 +00:00
|
|
|
Description
|
|
|
|
|
===========
|
2013-12-16 14:35:43 +00:00
|
|
|
This part of the repository is for FOAM test harnesses.
|
2010-10-07 03:00:07 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
Directory Structure
|
|
|
|
|
===================
|
|
|
|
|
|
2018-05-29 08:41:36 +00:00
|
|
|
foam-extend-4.1 : Test harness for foam-extend version 4.1. See the file foam-extend-4.1/README.txt for more information
|
2010-10-07 03:00:07 +00:00
|
|
|
|
2013-12-16 14:35:43 +00:00
|
|
|
OSIG : CMake/CTest scripts for FOAM Special Interest Group (OSIG) test harness
|
2010-10-07 03:00:07 +00:00
|
|
|
OSIG/TurboMachinery : Test harness for the TurboMachinery OSIG. See the file OSIG/Turbomachinery/README.txt for more information.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Martin Beaudoin, Hydro-Quebec, 2010. All rights reserved.
|
2010-10-15 18:57:05 +00:00
|
|
|
|
2013-07-18 01:02:34 +00:00
|
|
|
|
2010-10-15 18:57:05 +00:00
|
|
|
1: Select your git branch of choice: ie:
|
2013-07-18 01:02:34 +00:00
|
|
|
|
2010-10-15 18:57:05 +00:00
|
|
|
git checkout master # For Hrv master branch
|
|
|
|
|
|
|
|
|
|
|
2013-12-16 14:35:43 +00:00
|
|
|
2: Make sure your FOAM environment is properly configured to run FOAM.
|
2010-10-15 18:57:05 +00:00
|
|
|
|
|
|
|
|
|
2013-07-18 01:02:34 +00:00
|
|
|
3: The minimal cmake version number for running the test loop is 2.8.0. Make sure you are there.
|
2010-10-15 18:57:05 +00:00
|
|
|
|
|
|
|
|
|
2013-07-18 01:02:34 +00:00
|
|
|
4: Make sure you have the test harness scripts available under your git branch;
|
2010-10-15 18:57:05 +00:00
|
|
|
otherwise, you will need to fetch this from Hrv's master branch, and merge it into yours
|
|
|
|
|
|
|
|
|
|
ls $WM_PROJECT_DIR/testHarness # Checking availability of testHarness under this branch
|
|
|
|
|
|
|
|
|
|
|
2013-12-16 14:35:43 +00:00
|
|
|
5: move to the runDir directory for the FOAM test harness
|
2013-07-18 01:02:34 +00:00
|
|
|
|
2018-05-29 08:41:36 +00:00
|
|
|
cd $WM_PROJECT_DIR/testHarness/foam-extend/4.1/runDir
|
2010-10-15 18:57:05 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
6: Normally, if using the master branch, everything should already be setup for you to run the test harness.
|
|
|
|
|
Still, I recommand always checking that these two important files are up-to-date:
|
|
|
|
|
|
|
|
|
|
cp ../CMakeFiles/CMakeLists.txt $WM_PROJECT_DIR
|
2015-07-03 01:13:35 +00:00
|
|
|
cp ../CMakeFiles/CTestConfig.cmake.foam-extend $WM_PROJECT_DIR/CTestConfig.cmake
|
2010-10-15 18:57:05 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
7: Next, running the test loop is pretty simple:
|
2013-07-18 01:02:34 +00:00
|
|
|
|
2018-05-29 08:41:36 +00:00
|
|
|
cd $WM_PROJECT_DIR/testHarness/foam-extend/4.1/runDir # you should already be there...
|
2010-10-15 18:57:05 +00:00
|
|
|
./Allclean
|
|
|
|
|
./Allrun_Experimental
|
|
|
|
|
|
|
|
|
|
|
2015-07-03 01:13:35 +00:00
|
|
|
8: The results will be published on the CDash dashboard on foam-extend.
|
2010-10-15 18:57:05 +00:00
|
|
|
|
|
|
|
|
To see your results:
|
2018-05-29 08:41:36 +00:00
|
|
|
URL : http://foam-extend.sourceforge.net/CDash/index.php?project=foam-extend-4.1
|
2010-10-15 18:57:05 +00:00
|
|
|
|
|
|
|
|
|
2013-07-18 01:02:34 +00:00
|
|
|
9: You can customize your system identifier on the dashboard using the environment variable $CDASH_SUBMIT_LOCAL_HOST_ID.
|
|
|
|
|
Otherwise, the fully qualified name of your system will be used.
|
2010-10-15 18:57:05 +00:00
|
|
|
|
2013-07-18 01:02:34 +00:00
|
|
|
A good customization idea would be to add the name of your git branch in your system ID.
|
2010-10-15 18:57:05 +00:00
|
|
|
I will probably modify my scripts to add this information automagically.
|
|
|
|
|
|
|
|
|
|
NB: Please no "forward slash" or "/" in the system ID; it looks like CDash will choke on this.
|
|
|
|
|
|
|
|
|
|
|
2018-05-29 08:41:36 +00:00
|
|
|
10: In general, see the file $WM_PROJECT_DIR/testHarness/foam-extend/4.1/README.txt for the necessary information about running the
|
2013-07-18 01:02:34 +00:00
|
|
|
test loop.
|
2010-10-15 18:57:05 +00:00
|
|
|
|
|
|
|
|
|
2013-07-18 01:02:34 +00:00
|
|
|
11: Please do not hesitate to report any problems, comments, suggestions about the test loop.
|
