fmk - updating to latest

docs/_sources/bootcamp/syllabus.rst.txt

@@ -0,0 +1,20 @@
+*********
+Syllabus
+*********
+
+Welcome to the SimCenter Programming Bootcamp 2020.  Due to COVID-19, this year's offering
+will be solely online, though the SimCenter team is putting in all effort to recreate some
+of the community building benefits through discussion sessions and social time.
+
+The bootcamp is organized as a series of live video conferencing (ZOOM), prerecorded video
+lectures, hands-on exercises with online review options, and homework assignments.  The
+ideal flow of lessons and activities is provided in the "By Day" listing below.  A "By
+Topic" organization is provided for later review.
+
+.. toctree::
+   :maxdepth: 3
+
+   syllabus_by_day
+   syllabus_by_topic
+
+

docs/_sources/bootcamp/syllabus_by_day.rst.txt

@@ -0,0 +1,44 @@
+
+By Day
+========
+
+Week 1
+------
+
+* Day 1
+   * Welcome
+   * Introduction
+   * Setup
+   * Quick intro to Linux on the virtual machine
+   * Intro to git
+
+* Day 2
+   * What is a computer?
+   * Programming philosphy
+   * Python 1: data types
+   * Python 2: loops
+   * Python 3: conditions
+   * Python 4: functions
+
+* Day 3
+   * Python 5: matrix data types
+   * Python 6: plotting
+   * Object oriented programming - the concept
+   * Python 7: classes (objects)
+
+* Day 4
+   * Python 8: modules
+   * Python 9: file handling
+   * Python 10: useful extensions
+
+* Day 5
+   * Python 11: web-scrabbing using selenium
+
+Week 2
+------
+
+* Day 6
+* Day 7
+* Day 8
+* Day 9
+* Day 10

docs/_sources/bootcamp/syllabus_by_topic.rst.txt

@@ -0,0 +1,14 @@
+
+By Topic
+========
+
+* Welcome, Introduction, General
+* Setup
+* Linux
+* git
+* python
+* C
+* C++
+* web-scrabbing
+* SimCenter tools
+

docs/_sources/common/developer_manual/architecture/desktop/R2Dworkflows.rst.txt

@@ -35,23 +35,23 @@ A user's choice of :ref:`component applications <lblbackendApps>` for R2D depend
    :figclass: align-center
 
 
-**Workflow 3** (EQ): This workflow is appropriate for implementations where ground motion records are loaded on an user-created structural model in OpenSees. The OpenSees model script must be included as an additional input.
+**Workflow 3** (EQ): This workflow is appropriate for implementations where ground motion records are loaded on a user-created structural model in OpenSees. The OpenSees model script must be included as an additional input.
 
 .. figure:: figures/workflow_diagram_3.png
    :name: figWorkflowDiagram3
    :align: center
    :figclass: align-center
 
 
-**Workflow 4** (EQ): This workflow is appropriate for implementations where ground motion records are loaded on an user-created structural model in OpenSeesPy. The OpenSeesPy model script must be included as an additional input.
+**Workflow 4** (EQ): This workflow is appropriate for implementations where ground motion records are loaded on a user-created structural model in OpenSeesPy. The OpenSeesPy model script must be included as an additional input.
 
 .. figure:: figures/workflow_diagram_4.png
    :name: figWorkflowDiagram4
    :align: center
    :figclass: align-center
 
 
-**Workflow 5** (EQ, HU, W): This workflow is appropriate for implementations where response is simulated on an user-created structural model in OpenSeesPy, and the user defines custom types and locations of EDPs to record on the model. The OpenSeesPy model script and the EDP specifications file must be included as additional inputs.
+**Workflow 5** (EQ, HU, W): This workflow is appropriate for implementations where the response is simulated on a user-created structural model in OpenSeesPy, and the user defines custom types and locations of EDPs to record on the model. The OpenSeesPy model script and the EDP specifications file must be included as additional inputs.
 
 .. figure:: figures/workflow_diagram_5.png
    :name: figWorkflowDiagram5

docs/_sources/common/developer_manual/architecture/desktop/applications/EDPApps.rst.txt

@@ -5,7 +5,7 @@ EDP Applications
 
 The **EDP application** specifies the types of *engineering demand parameters* (EDP) expected as output from the response simulation.
 It determines the EDP type from building properties in the :ref:`BIM file <lblBuildingApp>`, the type of event in the :ref:`EVENT file <lblEventApp>`, and the model information from the :ref:`SAM file <lblModelingApp>`.
-It writes the type, location, and direction (DOF) of each EDP for a simulation in an ``EDP.json`` file in, located in its corresponding **simulation working directory**.
+It writes the type, location, and direction (DOF) of each EDP for a simulation in an ``EDP.json`` file, located in its corresponding **simulation working directory**.
 Note that in the EDP file, DOF=1,2 are assumed to correspond to perpendicular horizontal directions, and DOF=3 corresponds to the vertical direction.
 
 

docs/_sources/common/developer_manual/architecture/desktop/applications/UQApps.rst.txt

@@ -3,7 +3,7 @@
 UQ Applications
 ===============
 
-The **UQ application** is used to sample *random variables* (RV) specified in any of the workflow steps (Event, Modeling, EDP, Simulation) for the purpose of uncertainty quantification, then to run commands written in the **driver file** which call on the backend applications to execute the R2D Workflow.
+The **UQ application** is used to sample *random variables* (RV) specified in any of the workflow steps (Event, Modeling, EDP, Simulation) for uncertainty quantification, then to run commands written in the **driver file** which call on the backend applications to execute the R2D Workflow.
 It first populates values for the RVs, sampled from specified probability distributions, in the corresponding files (EVENT.json, SAM.json, EDP.json, SIM.json) for each simulation before executing the workflow.
 If no RVs are specified, then the UQ application directly runs commands in the driver file without random sampling.
 

docs/_sources/common/developer_manual/architecture/desktop/applications/eventApps.rst.txt

@@ -11,7 +11,7 @@ This input information is saved in an ``EVENT.json`` file, located in its corres
    :align: center
    :figclass: align-center
 
-The following options for event applications vary in the type of event, event properties, and format of the event file which it processes.
+The following options for event applications vary in the type of event, event properties, and format of the event file that it processes.