Broadband User Guide v11.2 - Revision history

Fsilva: /* User Support */

2014-07-15T19:52:28Z

User Support

Maechlin: /* Running Acceptance Tests */

2011-10-25T15:32:51Z

Running Acceptance Tests

Maechlin: /* Running Acceptance Tests */

2011-10-25T15:32:31Z

Running Acceptance Tests

Maechlin: /* Running Acceptance Tests */

2011-10-25T15:32:09Z

Running Acceptance Tests

Maechlin at 15:30, 25 October 2011

2011-10-25T15:30:30Z

Maechlin at 00:00, 5 October 2011

2011-10-05T00:00:29Z

Maechlin at 23:58, 4 October 2011

2011-10-04T23:58:29Z

Maechlin: /* Downloading the Platform */

2011-10-04T23:56:15Z

Downloading the Platform

Sandarsh: /* Unit/Acceptance Test Failures and Errors */

2011-07-19T23:40:31Z

Unit/Acceptance Test Failures and Errors

Sandarsh at 19:56, 8 July 2011

2011-07-08T19:56:38Z

@@ Line 712: / Line 712: @@
 If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].
-Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].
+Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@scec.org software@scec.org].
 = Appendix A: Possible Module Permutations =

@@ Line 249: / Line 249: @@
   $> ./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 [[User Support]].
+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 [[#User Support | User 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.

@@ Line 249: / Line 249: @@
   $> ./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 [[#User Support]].
+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 [[User 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.

@@ Line 249: / Line 249: @@
   $> ./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 [[support]].
+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 [[#User 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.

← Older revision		Revision as of 15:30, 25 October 2011
Line 1:		Line 1:
−	'''Version 11.2.0.'''	+	'''Version 11.2.2.'''

	If you find errors in this document or sections to be unclear, please either fix them yourself or contact Sandarsh Kumar (sandarsh@usc.edu), Scott Callaghan (scottcal@usc.edu) or Philip Maechling (maechlin@usc.edu).		If you find errors in this document or sections to be unclear, please either fix them yourself or contact Sandarsh Kumar (sandarsh@usc.edu), Scott Callaghan (scottcal@usc.edu) or Philip Maechling (maechlin@usc.edu).

@@ Line 211: / Line 211: @@
   $> svn update
-This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform] Building the Platform]) so that any code changes are captured in the executables.
+This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.
 = Running the Tests =

@@ Line 53: / Line 53: @@
 Once both files have passed the checksum test, untar the files.
-  $> tar xzvf bbp_dist_<version>.tgz file
+  $> tar xzvf bbp_dist_<version>.tgz
-  $> tar xzvf bbp_data_<version>.tgz file
+  $> tar xzvf bbp_data_<version>.tgz
 If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.

← Older revision		Revision as of 23:40, 19 July 2011
Line 1,574:		Line 1,574:

	'''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.		'''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.
		+
		+	==== ERROR: test_user-URS-URS-GATECH (__main__.BBP2G_Acceptance_Tests) ====
		+
		+	The acceptance test(s) with URS high frequency module throw an error with the following message:
		+	<pre>
		+	======================================================================
		+	ERROR: test_user-URS-URS-GATECH (__main__.BBP2G_Acceptance_Tests)
		+	----------------------------------------------------------------------
		+	Traceback (most recent call last):
		+	File "./at.py", line 67, in permutationTest
		+	compare_result = cmp_bbp.cmp_bbp(a_ref_file,test_file,tolerance=0.03)
		+	File ".../bbp/tests/cmp_bbp.py", line 226, in cmp_bbp
		+	fp2 = open(filename2, 'r')
		+	IOError: [Errno 2] No such file or directory: '.../bbp_2g/outdata/1024119/1024119.obre.rsp'
		+
		+	----------------------------------------------------------------------
		+	</pre>
		+
		+	'''Cause:''' The Broadband installation folder is too deeply nested resulting in input file names with long absolute paths. The high frequency module is unable to handle these long absolute paths and aborts without producing a valid seismogram for the site(s). The acceptance test throws an error as it is unable to locate the required site output files for comparison.
		+
		+	'''Solution:''' Minimize the Brodband installation directory nesting depth. For example if your Broadband installation is located in '/home/user/research/software/broadband/bbp_2g', try moving bbp_2g to say '/home/user/bbp_2g'

← Older revision		Revision as of 19:56, 8 July 2011
Line 1,574:		Line 1,574:

	'''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.		'''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.
−
−	~~# Linux VirtualBox Image~~
−	~~# Local installation on a 64-Bit Linux machine~~
−
−	~~== Oracle VirtualBox Image ==~~
−
−	The Broadband VirtualBox image allows for quick deployment of the Broadband platform with minimal configuration. This virtual machine image is based on a Fedora 14, 64-bit operating system. The image is provided with the Broadband platform fully configured, with all necessary supporting software. The image file (.vdi) is about 16 GB in size when