Broadband User Guide - Revision history

Maechlin: Redirected page to Broadband User Guide Current

2011-11-24T05:09:10Z

Redirected page to Broadband User Guide Current

Maechlin at 16:09, 5 October 2011

2011-10-05T16:09:59Z

Sandarsh: /* Running Acceptance Tests */

2011-08-03T00:02:49Z

Running Acceptance Tests

Sandarsh: /* Science Modules */

2011-08-02T23:51:51Z

Science Modules

Sandarsh: /* Science Modules */

2011-08-02T23:39:58Z

Science Modules

Sandarsh: /* Running Acceptance Tests */

2011-08-02T23:35:39Z

Running Acceptance Tests

Sandarsh: /* Running Unit Tests */

2011-08-02T22:54:59Z

Running Unit Tests

Sandarsh: /* Running Acceptance Tests */

2011-08-02T22:54:35Z

Running Acceptance Tests

Sandarsh: /* Running Unit Tests */

2011-08-02T21:32:06Z

Running Unit Tests

Sandarsh at 21:30, 2 August 2011

2011-08-02T21:30:50Z

← Older revision		Revision as of 05:09, 24 November 2011
Line 1:		Line 1:
		+	#redirect [[Broadband User Guide Current]]
	'''Version 11.7.0'''		'''Version 11.7.0'''

← Older revision		Revision as of 16:09, 5 October 2011
Line 93:		Line 93:

	After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.		After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.
−
−	~~'''* Symbolic-link Data Directory'''~~
−
−	~~A symbolic link to the data directory, bbp_2g_gf, should be placed in the code directory, bbp_2g~~
−	~~$>ln -s <path to bbp_2g>/bbp_2g_gf <path to bbp_2g_gf>~~

	=== Edit Install_cfg.py with Installation Directory Paths ===		=== Edit Install_cfg.py with Installation Directory Paths ===

@@ Line 310: / Line 310: @@
 When they're complete, the console will either print "OK" or how many tests failed. Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory.  If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/<test that failed>.log .  If you can't determine the reason for the failure, contact [mailto:software@intensity.usc.edu support].
-Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for known issues and their solutions.
+Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in logs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for known issues and their solutions.
 = Performing Simulations =

← Older revision		Revision as of 23:51, 2 August 2011
Line 334:		Line 334:

	Site response:URS, UCSB, SDSU, GATECH		Site response:URS, UCSB, SDSU, GATECH
		+

	'''NOTE:''' This version of Broadband has limited support for GATECH site response module - Site1d. This module requires site-specific soil profile data to produce valid results. Soil profile		'''NOTE:''' This version of Broadband has limited support for GATECH site response module - Site1d. This module requires site-specific soil profile data to produce valid results. Soil profile

@@ Line 333: / Line 333: @@
 High-frequency:URS, UCSB, SDSU
-Site response:URS, UCSB, SDSU
+Site response:URS, UCSB, SDSU, GATECH
 == Utility Modules ==

@@ Line 302: / Line 302: @@
   $> cd tests
-  $> ./AcceptTests.py
+  $> nohup ./AcceptTests.py
 Since they take so long to run, you may want to background them instead and redirect their output:
-  $> ./AcceptTests.py &> accept.out &
+  $> nohup ./AcceptTests.py &> accept.out &
-When they're complete, the console will either print "OK" or how many tests failed. If you system lacks MATLAB, you may find that a number of the acceptance tests are skipped. These are tests which require MATLAB, and skipping them is to be expected. Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory.  If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/<test that failed>.log .  If you can't determine the reason for the failure, contact [mailto:software@intensity.usc.edu support].
+When they're complete, the console will either print "OK" or how many tests failed. Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory.  If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/<test that failed>.log .  If you can't determine the reason for the failure, contact [mailto:software@intensity.usc.edu support].
-Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.
+Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for known issues and their solutions.
 = Performing Simulations =

@@ Line 293: / Line 293: @@
   $> ./UnitTests.py
-The unit tests take up to 45 minutes to run. When they're complete, the console will either print "OK" or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_<module>.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log .  If you can't determine the reason for the failure, contact support.
+The unit tests take up to 45 minutes to run. When they're complete, the console will either print "OK" or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_<module>.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log .  If you can't determine the reason for the failure, contact [mailto:software@intensity.usc.edu support].
 Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.

@@ Line 1: / Line 1: @@
 '''Version 11.7.0'''
-If you find errors in this document or sections to be unclear, please either fix them yourself or contact Sandarsh Kumar (sandarsh at usc.edu) or SCEC software help.
+If you find errors in this document or sections to be unclear, please either fix them yourself or contact Sandarsh Kumar (sandarsh at usc.edu) or [mailto:software@intensity.usc.edu SCEC software help].
 = Installing the Second-Generation Broadband Platform =