sierra-research 1.3.1__py3-none-any.whl → 1.3.6__py3-none-any.whl

{sierra_research-1.3.1.data → sierra_research-1.3.6.data}/data/share/man/man7/sierra-examples.7

@@ -1,8 +1,5 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "SIERRA-EXAMPLES" "7" "Jan 25, 2023" "1.3.1" "SIERRA"
-.SH NAME
-sierra-examples \- Examples of SIERRA usage. These examples all assume that you have successfully set up SIERRA with a project of your choice.
 .
 .nr rst2man-indent-level 0
 .
@@ -30,11 +27,14 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
+.TH "SIERRA-EXAMPLES" "7" "Apr 01, 2024" "1.3.6" "SIERRA"
+.SH NAME
+sierra-examples \- Examples of SIERRA usage. These examples all assume that you have successfully set up SIERRA with a project of your choice.
 .sp
 This page contains reference examples of SIERRA usage to help you craft your own
 SIERRA invocation.  These examples use the SIERRA project plugins from the
-SIERRA sample project repo: \fI\%https://github.com:jharwell/sierra\-sample\-project.git\fP\&. See
-ln\-sierra\-trial or ln\-sierra\-getting\-started for setting up the
+SIERRA sample project repo: \fI\%https://github.com/jharwell/sierra\-sample\-project\fP\&. See
+\fI\%Trying Out SIERRA\fP or \fI\%Getting Started With SIERRA\fP for setting up the
 sample project repository.
 .sp
 In all examples:
@@ -46,7 +46,7 @@ In all examples:
 plugin
 .IP \(bu 2
 \fB$HOME/git/sierra\-sample\-project/projects\fP is on
-\fBSIERRA_PLUGIN_PATH\fP\&.
+\fI\%SIERRA_PLUGIN_PATH\fP\&.
 .UNINDENT
 .sp
 If your setup is different, adjust paths in the commands below as needed.
@@ -102,7 +102,7 @@ Within each experiment, 3 copies of each simulation will be run (each with
 different random seeds), for a total of 21 ARGoS simulations. On a reasonable
 machine it should take about 10 minutes or so to run. After it finishes, you can
 go to \fB$HOME/exp\fP and find all the simulation outputs. For an explanation of
-SIERRA\(aqs runtime directory tree, see ln\-sierra\-usage\-runtime\-exp\-tree\&.
+SIERRA\(aqs runtime directory tree, see \fI\%SIERRA Runtime Directory Tree\fP\&.
 .SS HPC Example
 .sp
 In order to run on a SLURM managed cluster, you need to invoke SIERRA within a
@@ -128,7 +128,7 @@ export ARGOS_INSTALL_PREFIX=/$HOME/.local
 export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ARGOS_INSTALL_PREFIX/lib/argos3
 export ARGOS_PLUGIN_PATH=$ARGOS_INSTALL_PREFIX/lib/argos3:$HOME/git/mycode
 export SIERRA_PLUGIN_PATH=$HOME/git/sierra\-projects
-export PARALLEL="\-\-env ARGOS_PLUGIN_PATH \-\-env LD_LIBRARY_PATH"
+export PARALLEL=\(dq\-\-env ARGOS_PLUGIN_PATH \-\-env LD_LIBRARY_PATH\(dq
 
 sierra\-cli \e
 \-\-sierra\-root=$HOME/exp \e
@@ -157,7 +157,7 @@ previous example.
 \fBIMPORTANT:\fP
 .INDENT 0.0
 .INDENT 3.5
-You need to export \fBPARALLEL\fP containing all necessary
+You need to export \fI\%PARALLEL\fP containing all necessary
 environment variables your code uses in addition to those needed
 by SIERRA before invoking it, otherwise some of them might not be
 transferred to the SLURM job and/or the new shell GNU parallel
@@ -167,7 +167,7 @@ starts each simulation in.
 .sp
 Note that if you compile ARGoS for different architectures within the same HPC
 environment, you can use a combination of conditionally setting
-\fBARGOS_PLUGIN_PATH\fP with setting \fBSIERRA_ARCH\fP to some string to
+\fI\%ARGOS_PLUGIN_PATH\fP with setting \fI\%SIERRA_ARCH\fP to some string to
 tell SIERRA to use a given version of ARGoS, depending on where you request
 resources from. For example, you could set \fBSIERRA_ARCH=x86\fP or
 \fBSIERRA_ARCH=arm\fP to link to an \fBargos3\-x86\fP or \fBargos3\-arm\fP executable
@@ -202,7 +202,7 @@ sierra\-cli \e
 The runs 3 simulations in parallel with 1 physics engine each, and runs ARGoS
 under \fBXvfb\fP to get it to render headless images. During stage 4, these
 images are stitched together using \fBffmpeg\fP to create videos (see
-ln\-sierra\-usage\-runtime\-exp\-tree for where the videos will appear). No
+\fI\%SIERRA Runtime Directory Tree\fP for where the videos will appear). No
 graphs are generated during stage 4 in this example.
 .sp
 You may also be interested in the \fB\-\-camera\-config\fP option, which allows you
@@ -358,7 +358,7 @@ different random seeds), for a total of 16 Gazebo simulations. Each experimental
 run will be will be 10 seconds of simulated time. On a reasonable machine it
 should take about 10 minutes or so to run. After it finishes, you can go to
 \fB$HOME/exp\fP and find all the simulation outputs. For an explanation of
-SIERRA\(aqs runtime directory tree, see ln\-sierra\-usage\-runtime\-exp\-tree\&.
+SIERRA\(aqs runtime directory tree, see \fI\%SIERRA Runtime Directory Tree\fP\&.
 .SS HPC Example
 .sp
 In order to run on a SLURM managed cluster, you need to invoke SIERRA within a
@@ -407,7 +407,7 @@ simulation will be 1,000 seconds long and use same scenario as before.
 \fBIMPORTANT:\fP
 .INDENT 0.0
 .INDENT 3.5
-You need to export \fBPARALLEL\fP containing all necessary
+You need to export \fI\%PARALLEL\fP containing all necessary
 environment variables your code uses in addition to those needed
 by SIERRA before invoking it, otherwise some of them might not be
 transferred to the SLURM job and/or the new shell GNU parallel
@@ -474,12 +474,12 @@ size. SIERRA will pause for 60 seconds between runs so you can reset the robot\(
 positions and environment before continuing with the next
 run. \fBturtlebots3.txt\fP contains the IP addresses of all 6 robots in the swarm
 (SIERRA may use different combinations of these if the swarm size is < 6).  You
-could also omit \fB\-\-nodefile\fP and set \fBSIERRA_NODEFILE\fP instead.
+could also omit \fB\-\-nodefile\fP and set \fI\%SIERRA_NODEFILE\fP instead.
 .sp
 For these experiments, no master node is needed, so it is disabled. After all
 runs have completed and SIERRA finishes stages 3 and 4, you can go to
 \fB$HOME/exp\fP and find all the simulation outputs. For an explanation of
-SIERRA\(aqs runtime directory tree, see ln\-sierra\-usage\-runtime\-exp\-tree\&.
+SIERRA\(aqs runtime directory tree, see \fI\%SIERRA Runtime Directory Tree\fP\&.
 .SH AUTHOR
 John Harwell
 .SH COPYRIGHT

{sierra_research-1.3.1.data → sierra_research-1.3.6.data}/data/share/man/man7/sierra-exec-envs.7

@@ -1,8 +1,5 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "SIERRA-EXEC-ENVS" "7" "Jan 25, 2023" "1.3.1" "SIERRA"
-.SH NAME
-sierra-exec-envs \- The execution environments SIERRA supports.
 .
 .nr rst2man-indent-level 0
 .
@@ -30,6 +27,9 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
+.TH "SIERRA-EXEC-ENVS" "7" "Apr 01, 2024" "1.3.6" "SIERRA"
+.SH NAME
+sierra-exec-envs \- The execution environments SIERRA supports.
 .SH HPC EXECUTION ENVIRONMENT PLUGINS
 .sp
 SIERRA is capable of adapting its runtime infrastructure to a number of
@@ -41,9 +41,9 @@ These plugins tested with the following platforms (they may work on other
 platforms out of the box too):
 .INDENT 0.0
 .IP \(bu 2
-ln\-sierra\-platform\-plugins\-argos
+\fI\%ARGoS Platform\fP
 .IP \(bu 2
-ln\-sierra\-platform\-plugins\-ros1gazebo
+\fI\%ROS1+Gazebo Platform\fP
 .UNINDENT
 .sp
 SIERRA makes the following assumptions about the HPC environments corresponding
@@ -106,7 +106,7 @@ No additional configuration/environment variables are needed with this HPC
 environment for use with SIERRA.
 .SS ARGoS Considerations
 .sp
-The # threads per experimental run is defined with
+The # threads per \fI\%experimental run\fP is defined with
 \fB\-\-physics\-n\-engines\fP, and that option is required for this HPC environment
 during stage 1.
 .SS PBS HPC Plugin
@@ -177,14 +177,14 @@ Use
 T}
 _
 T{
-\fBSIERRA_ARCH\fP
+\fI\%SIERRA_ARCH\fP
 T}	T{
 Used to enable architecture/OS specific builds of simulators for maximum
 speed at runtime on clusters.
 T}
 _
 T{
-\fBPARALLEL\fP
+\fI\%PARALLEL\fP
 T}	T{
 Used to transfer environment variables into the GNU parallel
 environment. This must be always done because PBS doesn\(aqt transfer
@@ -267,14 +267,14 @@ Use
 T}
 _
 T{
-\fBSIERRA_ARCH\fP
+\fI\%SIERRA_ARCH\fP
 T}	T{
 Used to enable architecture/OS specific builds of simulators for maximum
 speed at runtime on clusters.
 T}
 _
 T{
-\fBPARALLEL\fP
+\fI\%PARALLEL\fP
 T}	T{
 Used to transfer environment variables into the GNU parallel
 environment. This must be done even though SLURM can transfer variables
@@ -311,14 +311,14 @@ Notes
 T}
 _
 T{
-\fBSIERRA_NODEFILE\fP
+\fI\%SIERRA_NODEFILE\fP
 T}	T{
 Contains hostnames/IP address of all compute nodes SIERRA can use. Same
 format as GNU parallel \fB\-\-sshloginfile\fP\&.
 T}	T{
 \fB\-\-nodefile\fP
 T}	T{
-\fBSIERRA_NODEFILE\fP must be defined or \fB\-\-nodefile\fP passed. If
+\fI\%SIERRA_NODEFILE\fP must be defined or \fB\-\-nodefile\fP passed. If
 neither is true, SIERRA will throw an error.
 T}
 _

{sierra_research-1.3.1.data → sierra_research-1.3.6.data}/data/share/man/man7/sierra-glossary.7

@@ -1,8 +1,5 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "SIERRA-GLOSSARY" "7" "Jan 25, 2023" "1.3.1" "SIERRA"
-.SH NAME
-sierra-glossary \- Glossary of SIERRA terminology.
 .
 .nr rst2man-indent-level 0
 .
@@ -30,6 +27,9 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
+.TH "SIERRA-GLOSSARY" "7" "Apr 01, 2024" "1.3.6" "SIERRA"
+.SH NAME
+sierra-glossary \- Glossary of SIERRA terminology.
 .SH GLOSSARY
 .sp
 SIERRA uses a number of common research\-related terms, perhaps in different ways
@@ -45,7 +45,7 @@ supports as a \fI\%Platform\fP\&. The ARGoS website is at
 .B Gazebo
 A state\-of\-the\-art robotics simulator with many features including .urdf
 robot models, realistic 3D rendering, and more. The Gazebo website is at
-\fI\%http://gazebosim.org\fP\&.
+\fI\%https://gazebosim.org\fP\&.
 .TP
 .B ROS1
 You know it. You either love it or hate it, but you can\(aqt escape it. The
@@ -71,7 +71,7 @@ argument passed on the cmdline to sets of XML changes as part of
 .INDENT 7.0
 .INDENT 3.5
 The parent directories of all SIERRA project plugins must
-be on \fBSIERRA_PLUGIN_PATH\fP, or SIERRA won\(aqt be able
+be on \fI\%SIERRA_PLUGIN_PATH\fP, or SIERRA won\(aqt be able
 to find them.
 .UNINDENT
 .UNINDENT
@@ -86,7 +86,7 @@ each as needed.
 .UNINDENT
 .UNINDENT
 .sp
-Specified via \fB\-\-project\fP on the cmdline. See ln\-sierra\-usage\-cli for
+Specified via \fB\-\-project\fP on the cmdline. See \fI\%Command Line Interface\fP for
 documentation.
 .TP
 .B Tick
@@ -97,9 +97,9 @@ run.
 .B Batch Criteria
 A \fIvariable\fP you wish to use with SIERRA to measure its effect on system
 behavior. A batch criteria can has a single axis (such as
-ln\-sierra\-platform\-argos\-bc\-population\-size), in which case it is
+\fI\%Population Size\fP), in which case it is
 called \fIunivariate\fP, or have two axes (such as
-ln\-sierra\-platform\-argos\-bc\-population\-size and another batch
+\fI\%Population Size\fP and another batch
 criteria such as one defining sensor and actuator noise to apply to the
 robots), in which case it is called \fIbivariate\fP\&.
 .sp
@@ -146,7 +146,7 @@ A set of \fI\%Experiments\fP each defined by XML changes
 generated by the selected \fI\%Batch Criteria\fP to a template \fB\&.argos\fP
 file passed to SIERRA during stage 1 via \fB\-\-template\-input\-file\fP\&.
 .sp
-For example, for the ln\-sierra\-platform\-argos\-bc\-population\-size
+For example, for the \fI\%Population Size\fP
 batch criteria, each experiment is defined by a single XML change to the
 provided \fB\&.argos\fP file: the number of robots in the swarm. Depending on
 the specifics you set for the \fIrange\fP of sizes you are interested in,
@@ -212,7 +212,7 @@ not know the difference.
 .TP
 .B Inter\-Batch .csv
 A CSV file created by SIERRA during stage 5. An inter\-batch CSV
-is created by "collating" columns from a \fI\%Summary .csv\fP present in
+is created by \(dqcollating\(dq columns from a \fI\%Summary .csv\fP present in
 multiple \fI\%Batch Experiments\fP into a single
 CSV. Used during stage 5.
 .TP
@@ -245,7 +245,7 @@ controllers easily when configuring your project.
 .B Controller Category
 A semantic label attached to a set of controllers which are similar in
 some way. For example, if you have two controllers which use the same type
-of memory (say it\(aqs a "last N objects seen" memory), you could create a
+of memory (say it\(aqs a \(dqlast N objects seen\(dq memory), you could create a
 \fBLastN\fP category, and then define controllers within it, e.g.,
 \fBLastN.Ring\fP and \fBLastN.DecayRing\fP for two controllers which have a
 ringbuffer of remembered objects and a decaying ringbuffer of remembered
@@ -261,7 +261,7 @@ plotted against empirical results for comparison.
 .TP
 .B Plugin
 A python package/module living in a directory on
-\fBSIERRA_PLUGIN_PATH\fP which contains functionality to extend SIERRA
+\fI\%SIERRA_PLUGIN_PATH\fP which contains functionality to extend SIERRA
 without modifying its core (i.e., customization of different parts of the
 pipeline). Plugins come in several flavors, all of which are handled
 equivalently by SIERRA:

{sierra_research-1.3.1.data → sierra_research-1.3.6.data}/data/share/man/man7/sierra-platforms.7

@@ -1,8 +1,5 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "SIERRA-PLATFORMS" "7" "Jan 25, 2023" "1.3.1" "SIERRA"
-.SH NAME
-sierra-platforms \- The platforms SIERRA supports, and platform-specific Batch Criteria.
 .
 .nr rst2man-indent-level 0
 .
@@ -30,18 +27,21 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
+.TH "SIERRA-PLATFORMS" "7" "Apr 01, 2024" "1.3.6" "SIERRA"
+.SH NAME
+sierra-platforms \- The platforms SIERRA supports, and platform-specific Batch Criteria.
 .SH ARGOS PLATFORM
 .sp
 This platform can be selected via \fB\-\-platform=platform.argos\fP\&.
 .sp
 This is the default platform on which SIERRA will run experiments, and uses the
-ARGoS simulator. It cannot be used to run experiments on real robots.
+\fI\%ARGoS\fP simulator. It cannot be used to run experiments on real robots.
 .SS Batch Criteria
 .sp
-See Batch Criteria for a thorough explanation of batch criteria, but the
+See \fI\%Batch Criteria\fP for a thorough explanation of batch criteria, but the
 short version is that they are the core of SIERRA\-\-how to get it to DO stuff for
 you.  The following batch criteria are defined which can be used with any
-Project\&.
+\fI\%Project\fP\&.
 .INDENT 0.0
 .IP \(bu 2
 \fI\%Population Size\fP
@@ -162,38 +162,38 @@ experiment will be linearly spaced between the min and max densities.
 .UNINDENT
 .SS Environment Variables
 .sp
-This platform respects \fBSIERRA_ARCH\fP\&.
+This platform respects \fI\%SIERRA_ARCH\fP\&.
 .SS Random Seeding For Reproducibility
 .sp
 ARGoS provides its own random seed mechanism under \fB<experiment>\fP which SIERRA
-uses to seed each experiment. Project code should use this mechanism or
+uses to seed each experiment. \fI\%Project\fP code should use this mechanism or
 a similar random seed generator manager seeded by the same value so that
 experiments can be reproduced exactly. By default SIERRA does not overwrite its
 generated random seeds for each experiment once generated; you can override with
 \fB\-\-no\-preserve\-seeds\fP\&. See ln\-sierra\-tutorials\-project\-template\-input\-file and
-ln\-sierra\-req\-exp for details on the format of the provided seed.
+\fI\%Experimental Definition Requirements\fP for details on the format of the provided seed.
 .SH ROS1+GAZEBO PLATFORM
 .sp
 This platform can be selected via \fB\-\-platform=platform.ros1gazebo\fP\&.
 .sp
 This is the platform on which SIERRA will run experiments using the
-Gazebo simulator and ROS1\&. It cannot be used to run
+\fI\%Gazebo\fP simulator and \fI\%ROS1\fP\&. It cannot be used to run
 experiments on real robots. To use this platform, you must setup the
-SIERRA ROSBridge\&.
+\fI\%SIERRA ROSBridge\fP\&.
 .sp
 Worlds within ROS1+Gazebo are infinite from the perspective of physics engines,
 even though a finite area shows up in rendering. So, to place robots randomly in
-the arena at the start of simulation across Experimental Runs (if you want to do that) "dimensions" for a given world must
+the arena at the start of simulation across \fI\%Experimental Runs\fP (if you want to do that) \(dqdimensions\(dq for a given world must
 be specified as part of the \fB\-\-scenario\fP argument. If you don\(aqt specify
 dimensions as part of the \fB\-\-scenario\fP argument, then you need to supply a
 list of valid robot positions via \fB\-\-robot\-positions\fP which SIERRA will choose
 from randomly for each robot.
 .SS Batch Criteria
 .sp
-See Batch Criteria for a thorough explanation of batch criteria, but the
+See \fI\%Batch Criteria\fP for a thorough explanation of batch criteria, but the
 short version is that they are the core of SIERRA\-\-how to get it to DO stuff for
 you.  The following batch criteria are defined which can be used with any
-Project\&.
+\fI\%Project\fP\&.
 .INDENT 0.0
 .IP \(bu 2
 \fI\%System Population Size\fP
@@ -236,27 +236,27 @@ linear increment. Defaults to 10 if omitted.
 .UNINDENT
 .SS Environment Variables
 .sp
-This platform ignores \fBSIERRA_ARCH\fP\&.
+This platform ignores \fI\%SIERRA_ARCH\fP\&.
 .SS Random Seeding For Reproducibility
 .sp
 ROS1+Gazebo do not provide a random number generator manager, but SIERRA
-provides random seeds to each Experimental Run which Project
+provides random seeds to each \fI\%Experimental Run\fP which \fI\%Project\fP
 code should use to manage random number generation, if needed, to maximize
 reproducability. See ln\-sierra\-tutorials\-project\-template\-input\-file and
-ln\-sierra\-req\-exp for details on the format of the provided seed. By default
+\fI\%Experimental Definition Requirements\fP for details on the format of the provided seed. By default
 SIERRA does not overwrite its generated random seeds for each experiment once
 generated; you can override with \fB\-\-no\-preserve\-seeds\fP\&.
 .SH ROS1+ROBOT PLATFORM
 .sp
 This platform can be selected via \fB\-\-platform=platform.ros1robot\fP\&.
 .sp
-This is the platform on which SIERRA will run experiments using ROS1 on
+This is the platform on which SIERRA will run experiments using \fI\%ROS1\fP on
 a real robot of your choice. To use this platform, you must setup the
-SIERRA ROSBridge\&.  This is a generic
-platform meant to work with most real robots which ROS1 supports, and as
+\fI\%SIERRA ROSBridge\fP\&.  This is a generic
+platform meant to work with most real robots which \fI\%ROS1\fP supports, and as
 a starting point to derive more specific platform configuration for a given
 robot (if needed). For all execution environments using this platform (see
-ln\-sierra\-exec\-env\-robot for examples), SIERRA will run experiments
+\fI\%Real Robot Execution Environment Plugins\fP for examples), SIERRA will run experiments
 spread across multiple robots using GNU parallel.
 .sp
 SIERRA designates the host machine as the ROS master, and allows you to
@@ -266,10 +266,10 @@ helpful in some situations (e.g., simple robots which can\(aqt manage network
 mounted filesystems).
 .SS Batch Criteria
 .sp
-See Batch Criteria for a thorough explanation of batch criteria, but the
+See \fI\%Batch Criteria\fP for a thorough explanation of batch criteria, but the
 short version is that they are the core of SIERRA\-\-how to get it to DO stuff for
 you. The following batch criteria are defined which can be used with any
-Project\&.
+\fI\%Project\fP\&.
 .INDENT 0.0
 .IP \(bu 2
 \fI\%System Population Size\fP
@@ -311,14 +311,14 @@ linear increment. Defaults to 10 if omitted.
 .UNINDENT
 .SS Environment Variables
 .sp
-This platform ignores \fBSIERRA_ARCH\fP\&.
+This platform ignores \fI\%SIERRA_ARCH\fP\&.
 .SS Random Seeding For Reproducibility
 .sp
 ROS do not provide a random number generator manager, but SIERRA provides random
-seeds to each Experimental Run which Project code should use to
+seeds to each \fI\%Experimental Run\fP which \fI\%Project\fP code should use to
 manage random number generation, if needed, to maximize reproducability. See
 ln\-sierra\-tutorials\-project\-template\-input\-file and
-ln\-sierra\-req\-exp for details on the format of the provided seed. By
+\fI\%Experimental Definition Requirements\fP for details on the format of the provided seed. By
 default SIERRA does not overwrite its generated random seeds for each experiment
 once generated; you can override with \fB\-\-no\-preserve\-seeds\fP\&.
 .SS Real Robot Considerations
@@ -327,7 +327,7 @@ SIERRA makes the following assumptions about the robots it is allocated each
 invocation:
 .INDENT 0.0
 .IP \(bu 2
-No robots will die/run out of battery during an Experimental Run\&.
+No robots will die/run out of battery during an \fI\%Experimental Run\fP\&.
 .IP \(bu 2
 Password\-less ssh is setup to each robot SIERRA is handed to use (can be as a
 different user than the one which is invoking SIERRA on the host machine).
@@ -335,21 +335,21 @@ different user than the one which is invoking SIERRA on the host machine).
 The robots have static IP addresses, or are always allocated an IP from a
 known set so you can pass the set of IPs to SIERRA to use. This set of IP
 address/hostnames can be explicitly passed to SIERRA via cmdline (see
-ln\-sierra\-usage\-cli) or implicitly passed via
-\fBSIERRA_NODEFILE\fP\&.
+\fI\%Command Line Interface\fP) or implicitly passed via
+\fI\%SIERRA_NODEFILE\fP\&.
 .IP \(bu 2
 The ROS environment is setup either in the .bashrc for the robot login user,
 or the necessary bits are in a script which SIERRA sources on login to each
 robot (this is a configuration parameter\-\-see
 ln\-sierra\-tutorials\-project\-main\-config).
 .IP \(bu 2
-ROS does not provide a way to say "Run this experiment for X seconds", so
+ROS does not provide a way to say \(dqRun this experiment for X seconds\(dq, so
 SIERRA inserts its own timekeeper node into each robot which will exit after X
 seconds and take the roslaunch process with it on each robot and/or the master
 node.
 .UNINDENT
 .sp
-See also ln\-sierra\-req\-code\-ros1robot\&.
+See also \fI\%ROS1+Robot Platform\fP\&.
 .SH AUTHOR
 John Harwell
 .SH COPYRIGHT