Broadband User Guide v11.2.1 - Revision history

Fsilva: /* User Support */

2014-07-15T17:09:02Z

User Support

Sandarsh: /* Advanced Users */

2011-10-14T04:00:19Z

Advanced Users

Sandarsh: /* Advanced Users */

2011-10-14T03:59:48Z

Advanced Users

Maechlin: /* Advanced Users */

2011-10-05T01:21:49Z

Advanced Users

Maechlin at 03:28, 4 October 2011

2011-10-04T03:28:21Z

Maechlin: /* User Account Setup */

2011-10-04T03:26:08Z

User Account Setup

Maechlin: /* User Account Setup */

2011-10-04T03:24:06Z

User Account Setup

Maechlin: /* Setting Up Your Account */

2011-10-04T03:23:27Z

Setting Up Your Account

Maechlin: /* Setting Up Your Account */

2011-10-04T03:23:08Z

Setting Up Your Account

Maechlin at 03:20, 4 October 2011

2011-10-04T03:20:09Z

Show changes

@@ Line 781: / Line 781: @@
 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 223: / Line 223: @@
 == Advanced Users ==
-Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on intensity.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[Downloading the Platform|Downloading the Platform]] and skip this section.
+Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on intensity.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.
 You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.

@@ Line 223: / Line 223: @@
 == Advanced Users ==
-Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on intensity.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.
+Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on intensity.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[Downloading the Platform|Downloading the Platform]] and skip this section.
 You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.

@@ Line 245: / Line 245: @@
   $> 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]]) 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 Broadband Platform ==

@@ Line 162: / Line 162: @@
 === Adding aliases ===
-You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command.  We recommend creating aliases for the comps, start, and outdata directories.
+You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command.  We recommend creating aliases for the home, start, and outdata directories.
 If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:
   alias bbp= 'cd <path to bbp_2g directory>'
   alias start='cd <path to bbp_2g directory>/start'
-  alias outd='cd <path to bbp_2g directory>/outdata'
+  alias outdata='cd <path to bbp_2g directory>/outdata'
 If you're using a C shell, edit your ~/.cshrc and add:
   alias bbp cd <path to bbp_2g directory>
   alias start cd <path to bbp_2g directory>/start
-  alias outd cd <path to bbp_2g directory>/outdata
+  alias outdata cd <path to bbp_2g directory>/outdata
 Log out and log back in.  You'll notice that now you can type the alias command as a shortcut to change directories:

@@ Line 68: / Line 68: @@
 Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.
-The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests pass prior to use of a particular broadband platform installation.
+The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.
 == Data Directory ==

@@ Line 27: / Line 27: @@
 == Setting Up Your Account ==
-For simplicity of installation we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.
+For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.
 To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.