diff --git a/docs/.buildinfo b/docs/.buildinfo index 38bd92fc..37f55130 100644 --- a/docs/.buildinfo +++ b/docs/.buildinfo @@ -1,4 +1,4 @@ # Sphinx build info version 1 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done. -config: 3056bb726d5b0e4c1bbfde254111bc36 +config: aadc4c59e59a03fa625c3a2a68d32121 tags: 07ba9f3d13264cb0619caebd6f1ec658 diff --git a/docs/.doctrees/bootcamp/syllabus.doctree b/docs/.doctrees/bootcamp/syllabus.doctree index 6d0f16e2..0c311465 100644 Binary files a/docs/.doctrees/bootcamp/syllabus.doctree and b/docs/.doctrees/bootcamp/syllabus.doctree differ diff --git a/docs/.doctrees/bootcamp/syllabus_by_day.doctree b/docs/.doctrees/bootcamp/syllabus_by_day.doctree index 2a7bf1b5..368829ce 100644 Binary files a/docs/.doctrees/bootcamp/syllabus_by_day.doctree and b/docs/.doctrees/bootcamp/syllabus_by_day.doctree differ diff --git a/docs/.doctrees/bootcamp/syllabus_by_topic.doctree b/docs/.doctrees/bootcamp/syllabus_by_topic.doctree index 76438169..f18f0fa1 100644 Binary files a/docs/.doctrees/bootcamp/syllabus_by_topic.doctree and b/docs/.doctrees/bootcamp/syllabus_by_topic.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/DLApps.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/DLApps.doctree index 42746423..59e0eb7d 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/DLApps.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/DLApps.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/EDPApps.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/EDPApps.doctree index 6a1f0030..7ce05199 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/EDPApps.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/EDPApps.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/UQApps.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/UQApps.doctree index 567e8ce6..a7646514 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/UQApps.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/UQApps.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/buildingApps.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/buildingApps.doctree index 9caa1ee7..2c1561da 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/buildingApps.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/buildingApps.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/eventApps.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/eventApps.doctree index ec2dff9c..1069c52d 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/eventApps.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/eventApps.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/modelingApps.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/modelingApps.doctree index 65b25376..9237a736 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/modelingApps.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/modelingApps.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/preprocFEM.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/preprocFEM.doctree index 31f5731e..c209357c 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/preprocFEM.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/preprocFEM.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/preprocUQ.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/preprocUQ.doctree index cdcb1491..4fae6348 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/preprocUQ.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/preprocUQ.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/regionalMapApps.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/regionalMapApps.doctree index 168f0663..27daf640 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/regionalMapApps.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/regionalMapApps.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/simulationApps.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/simulationApps.doctree index 19db2f71..6f9ed706 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/applications/simulationApps.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/applications/simulationApps.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/architecture.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/architecture.doctree index 9e7a4a0b..baf58590 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/architecture.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/architecture.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/backendApplications.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/backendApplications.doctree index 1c9717a9..92de0d2d 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/backendApplications.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/backendApplications.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/c4model.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/c4model.doctree index 49e0fd16..bd578775 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/c4model.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/c4model.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/dynamicDiagrams.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/dynamicDiagrams.doctree index 627e1798..1aee185d 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/dynamicDiagrams.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/dynamicDiagrams.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/file-types.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/file-types.doctree index 46b13d31..f65114b7 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/file-types.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/file-types.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/file-types/Inputs.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/file-types/Inputs.doctree index 26328c79..d489c44e 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/file-types/Inputs.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/file-types/Inputs.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/file-types/Outputs.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/file-types/Outputs.doctree index 95f66109..3f3ba0b2 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/file-types/Outputs.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/file-types/Outputs.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/overview.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/overview.doctree index cbc4b39f..53cd7259 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/overview.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/overview.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually.doctree index 097ac7e8..134ba2c4 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/runLocal.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/runLocal.doctree index 558f72c6..e5d1599f 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/runLocal.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/runLocal.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/runRemote.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/runRemote.doctree index 8fb12159..fd0201fb 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/runRemote.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/runRemote.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/troubleshooting.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/troubleshooting.doctree index d4a854e2..c5f1a923 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/troubleshooting.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/run-manually/troubleshooting.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/workflows.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/workflows.doctree index bcda201f..697597d1 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/workflows.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/workflows.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/readingTheLog.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/readingTheLog.doctree index 76bbf1b0..6f5aad32 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/readingTheLog.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/readingTheLog.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/workflowCompatibility.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/workflowCompatibility.doctree index 90b32e7f..c4fc5a0a 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/workflowCompatibility.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/workflowCompatibility.doctree differ diff --git a/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/workflowStructure.doctree b/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/workflowStructure.doctree index 3795871f..f09cfbf9 100644 Binary files a/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/workflowStructure.doctree and b/docs/.doctrees/common/developer_manual/architecture/desktop/workflows/workflowStructure.doctree differ diff --git a/docs/.doctrees/common/developer_manual/coding_style/desktop/coding_style.doctree b/docs/.doctrees/common/developer_manual/coding_style/desktop/coding_style.doctree index c97df599..77220dc7 100644 Binary files a/docs/.doctrees/common/developer_manual/coding_style/desktop/coding_style.doctree and b/docs/.doctrees/common/developer_manual/coding_style/desktop/coding_style.doctree differ diff --git a/docs/.doctrees/common/developer_manual/examples/desktop/eqAssessment.doctree b/docs/.doctrees/common/developer_manual/examples/desktop/eqAssessment.doctree index ad8b502a..a085fa0f 100644 Binary files a/docs/.doctrees/common/developer_manual/examples/desktop/eqAssessment.doctree and b/docs/.doctrees/common/developer_manual/examples/desktop/eqAssessment.doctree differ diff --git a/docs/.doctrees/common/developer_manual/examples/desktop/examples.doctree b/docs/.doctrees/common/developer_manual/examples/desktop/examples.doctree index 11731a0a..752c1988 100644 Binary files a/docs/.doctrees/common/developer_manual/examples/desktop/examples.doctree and b/docs/.doctrees/common/developer_manual/examples/desktop/examples.doctree differ diff --git a/docs/.doctrees/common/developer_manual/examples/desktop/hurricaneAssessment.doctree b/docs/.doctrees/common/developer_manual/examples/desktop/hurricaneAssessment.doctree index 7e4cc377..999acff8 100644 Binary files a/docs/.doctrees/common/developer_manual/examples/desktop/hurricaneAssessment.doctree and b/docs/.doctrees/common/developer_manual/examples/desktop/hurricaneAssessment.doctree differ diff --git a/docs/.doctrees/common/developer_manual/examples/desktop/siteResponseAssessment/siteResponseAssessment.doctree b/docs/.doctrees/common/developer_manual/examples/desktop/siteResponseAssessment/siteResponseAssessment.doctree index d027883d..a0e9af49 100644 Binary files a/docs/.doctrees/common/developer_manual/examples/desktop/siteResponseAssessment/siteResponseAssessment.doctree and b/docs/.doctrees/common/developer_manual/examples/desktop/siteResponseAssessment/siteResponseAssessment.doctree differ diff --git a/docs/.doctrees/common/developer_manual/how_to_build/desktop/SimCenterBackend.doctree b/docs/.doctrees/common/developer_manual/how_to_build/desktop/SimCenterBackend.doctree index c8c41d8e..1c9fb57b 100644 Binary files a/docs/.doctrees/common/developer_manual/how_to_build/desktop/SimCenterBackend.doctree and b/docs/.doctrees/common/developer_manual/how_to_build/desktop/SimCenterBackend.doctree differ diff --git a/docs/.doctrees/common/developer_manual/how_to_build/desktop/how_to_build.doctree b/docs/.doctrees/common/developer_manual/how_to_build/desktop/how_to_build.doctree index 835c95d2..4df7b894 100644 Binary files a/docs/.doctrees/common/developer_manual/how_to_build/desktop/how_to_build.doctree and b/docs/.doctrees/common/developer_manual/how_to_build/desktop/how_to_build.doctree differ diff --git a/docs/.doctrees/common/developer_manual/how_to_build/desktop/quoFemBackend.doctree b/docs/.doctrees/common/developer_manual/how_to_build/desktop/quoFemBackend.doctree index e31daf76..1fd17b3b 100644 Binary files a/docs/.doctrees/common/developer_manual/how_to_build/desktop/quoFemBackend.doctree and b/docs/.doctrees/common/developer_manual/how_to_build/desktop/quoFemBackend.doctree differ diff --git a/docs/.doctrees/common/developer_manual/how_to_extend.doctree b/docs/.doctrees/common/developer_manual/how_to_extend.doctree index 0c33f30e..ce6724d2 100644 Binary files a/docs/.doctrees/common/developer_manual/how_to_extend.doctree and b/docs/.doctrees/common/developer_manual/how_to_extend.doctree differ diff --git a/docs/.doctrees/common/developer_manual/verification/desktop/HydroUQ/DakotaSensitivity.doctree b/docs/.doctrees/common/developer_manual/verification/desktop/HydroUQ/DakotaSensitivity.doctree index 46e244dd..bd04816f 100644 Binary files a/docs/.doctrees/common/developer_manual/verification/desktop/HydroUQ/DakotaSensitivity.doctree and b/docs/.doctrees/common/developer_manual/verification/desktop/HydroUQ/DakotaSensitivity.doctree differ diff --git a/docs/.doctrees/common/developer_manual/verification/desktop/verification.doctree b/docs/.doctrees/common/developer_manual/verification/desktop/verification.doctree index 711de145..dd9d8850 100644 Binary files a/docs/.doctrees/common/developer_manual/verification/desktop/verification.doctree and b/docs/.doctrees/common/developer_manual/verification/desktop/verification.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.31/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.31/index.doctree index 3b3e66b4..8847967d 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.31/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.31/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.33/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.33/index.doctree index b0c35167..13aeb950 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.33/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.33/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.35/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.35/index.doctree index 61d2b575..89ded02d 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.35/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.35/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.41/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.41/index.doctree index 544e5f67..426c8593 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.41/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.41/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.42/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.42/index.doctree index 4332e668..19440369 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.42/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.42/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.44/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.44/index.doctree index 50f52041..510bab63 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.44/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.44/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.49/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.49/index.doctree index 690a40d2..38504455 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.49/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.49/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.51/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.51/index.doctree index f183e68b..02deb53d 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.51/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.51/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.52/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.52/index.doctree index 9ef21f2d..b1cb4bb7 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.52/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.52/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.61/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.61/index.doctree index 29c1a0c7..d06cc2ed 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.61/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.61/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.71/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.71/index.doctree index e0ddfe92..b6e5a552 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.71/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.71/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/index.doctree index 4f8b8508..dfe05dae 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.10/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.11/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.11/index.doctree index 849106bc..8968e4f9 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.11/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.22/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.22/index.doctree index bd615c82..2bc7ac14 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.22/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.22/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.23/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.23/index.doctree index efa4265f..5ef0cef9 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.23/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.23/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/index.doctree index a58b7b93..19076f43 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.20/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.11/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.11/index.doctree index 7cb7feb0..19a721a3 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.11/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.31/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.31/index.doctree index 981ebf7b..7e9aa6c2 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.31/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.31/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.41/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.41/index.doctree index 6faed317..360920ef 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.41/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.41/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/index.doctree index 137b70e6..692141fe 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/B.30/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/index.doctree index 93474b8e..4978fef5 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/B/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.10/C.10.11/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.10/C.10.11/index.doctree index de7cf737..cee44d5d 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.10/C.10.11/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.10/C.10.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.10/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.10/index.doctree index 3f067d4d..192e9490 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.10/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.10/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.20/C.20.11/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.20/C.20.11/index.doctree index e638cc82..3bf790b1 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.20/C.20.11/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.20/C.20.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.20/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.20/index.doctree index 4409409f..07a33320 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.20/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.20/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.11/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.11/index.doctree index 624c4b8f..b72f5fec 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.11/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.21/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.21/index.doctree index b32229d9..a1dd32ef 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.21/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.21/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.27/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.27/index.doctree index 76f0c093..da15e604 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.27/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.27/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.32/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.32/index.doctree index 26894c5a..b6a95193 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.32/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.32/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.34/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.34/index.doctree index d3f56892..369ac585 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.34/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.34/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/index.doctree index dbe4639a..4ec103b2 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/C.30/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/index.doctree index 5e3e9837..2ad6eecc 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/C/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.10/D.10.14/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.10/D.10.14/index.doctree index f80296ba..5e79f0b5 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.10/D.10.14/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.10/D.10.14/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.10/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.10/index.doctree index 66102262..0c8a7427 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.10/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.10/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.21/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.21/index.doctree index 9e7049b2..4a325b43 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.21/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.21/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.22/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.22/index.doctree index 34c4917f..019bb121 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.22/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.22/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.31/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.31/index.doctree index 45919d43..d42fe5d0 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.31/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.31/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.51/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.51/index.doctree index 96b9c5a0..85271c49 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.51/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.51/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.61/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.61/index.doctree index bfbf29b8..c69c826c 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.61/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.61/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/index.doctree index a9712adc..cef506cc 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.20/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.31/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.31/index.doctree index 56e78adf..b1ae6ec2 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.31/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.31/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.32/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.32/index.doctree index f154c1c5..1339cfa2 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.32/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.32/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.41/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.41/index.doctree index 3c94a3c2..6152c626 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.41/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.41/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.52/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.52/index.doctree index 896b9cef..4fd61906 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.52/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.52/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.67/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.67/index.doctree index 40718183..7988b96d 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.67/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.67/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/index.doctree index aa61733b..1598d37b 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.30/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.40/D.40.11/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.40/D.40.11/index.doctree index ac8fbcf1..6652fa6d 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.40/D.40.11/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.40/D.40.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.40/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.40/index.doctree index 2e139375..acd2a6ba 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.40/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.40/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.11/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.11/index.doctree index b2be3780..95c11043 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.11/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.12/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.12/index.doctree index 408e7889..0e1da0c6 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.12/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.12/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.92/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.92/index.doctree index f30e8319..0f6748be 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.92/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.92/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/index.doctree index 3bb2ac04..7326d24e 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/D.50/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/index.doctree index 0b6c557f..9346bcb4 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/D/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/E.20/E.20.22/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/E.20/E.20.22/index.doctree index 49a1b930..6cd36cb5 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/E.20/E.20.22/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/E.20/E.20.22/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/E.20/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/E.20/index.doctree index e20f20cb..efcd5b44 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/E.20/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/E.20/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/index.doctree index bbbfd130..4daa5d43 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/E/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/F.10/F.10.12/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/F.10/F.10.12/index.doctree index abb44dca..5ef4ec16 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/F.10/F.10.12/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/F.10/F.10.12/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/F.10/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/F.10/index.doctree index 1a4afdd5..80daf8b4 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/F.10/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/F.10/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/index.doctree index 22939ba2..ccda2153 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/F/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/index.doctree b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/index.doctree index 9558086f..2c8a342e 100644 Binary files a/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/index.doctree and b/docs/.doctrees/common/dldb/damage/FEMA_P58_2nd/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/GF.H/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/GF.H/index.doctree index d56cb46e..e55f56f2 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/GF.H/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/GF.H/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/GF.V/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/GF.V/index.doctree index 9e1b1a9e..da5a2dcd 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/GF.V/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/GF.V/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/index.doctree index b1247b35..41c6ba3e 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/GF/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C1/index.doctree index ca56968a..68cef221 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C2/index.doctree index 43399d27..35f3fe5c 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C3/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C3/index.doctree index c005f7fa..c91c1d46 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C3/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C3/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.MH/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.MH/index.doctree index d5ceceb9..767e3b0e 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.MH/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.MH/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC1/index.doctree index 4bc97c7a..27c8946e 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC2/index.doctree index 580686e2..9731ad20 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM1/index.doctree index fa782256..aabd90d1 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM2/index.doctree index 74649fac..4df6af52 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S1/index.doctree index 03486097..13b1a9eb 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S2/index.doctree index 41c2453c..1df10049 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S3/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S3/index.doctree index 3e3c39ad..5030799d 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S3/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S3/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S4/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S4/index.doctree index 23d1041e..2d9046f8 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S4/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S4/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S5/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S5/index.doctree index 67dae433..35ba670f 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S5/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S5/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.URM/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.URM/index.doctree index 38a7646e..39db8748 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.URM/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.URM/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W1/index.doctree index 77f2a2b2..61781c27 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W2/index.doctree index 49bde50f..6dbc8cd3 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/index.doctree index aef89cca..0c791c28 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/LF/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/NSA/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/NSA/index.doctree index b3da6145..873e861e 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/NSA/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/NSA/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/NSD/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/NSD/index.doctree index 499c6300..6da209f3 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/NSD/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/NSD/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C1/index.doctree index c73328ac..de9fe30f 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C2/index.doctree index da3a8972..c4a25022 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C3/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C3/index.doctree index 143298e5..c0a7ddfb 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C3/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C3/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.MH/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.MH/index.doctree index 83dc8bb7..c047ffae 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.MH/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.MH/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC1/index.doctree index 6594c217..3cb4a49b 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC2/index.doctree index d9f7c425..cc60c9be 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM1/index.doctree index 44a49c0c..925dbf6a 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM2/index.doctree index 62b6f02a..a82abf68 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S1/index.doctree index c602f5e9..74f0577c 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S2/index.doctree index 6823b0d2..3a212deb 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S3/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S3/index.doctree index f7c87fcb..7fdf36d1 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S3/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S3/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S4/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S4/index.doctree index 2f07e323..2ad375be 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S4/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S4/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S5/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S5/index.doctree index 4015647e..7546bb5d 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S5/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S5/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.URM/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.URM/index.doctree index 4e4f7aa1..3fd7d733 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.URM/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.URM/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W1/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W1/index.doctree index 55489eef..b04c0a76 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W1/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W1/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W2/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W2/index.doctree index 27cf0949..aed8b77f 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W2/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W2/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/index.doctree index f31e9490..66f6e2bc 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/STR/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/index.doctree index 80a09125..391abe6f 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_bldg/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HRD/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HRD/index.doctree index a2b8deb1..c5ea901e 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HRD/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HRD/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HTU/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HTU/index.doctree index 5b176300..470bedfb 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HTU/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HTU/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HWB/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HWB/index.doctree index 48bf8c2c..2e6c7455 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HWB/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/HWB/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/index.doctree b/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/index.doctree index 0d42304d..d666f303 100644 Binary files a/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/index.doctree and b/docs/.doctrees/common/dldb/damage/Hazus_EQ_trnsp/index.doctree differ diff --git a/docs/.doctrees/common/dldb/damage/index.doctree b/docs/.doctrees/common/dldb/damage/index.doctree index 282eeab8..a2b2ee0b 100644 Binary files a/docs/.doctrees/common/dldb/damage/index.doctree and b/docs/.doctrees/common/dldb/damage/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.31/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.31/index.doctree index 8828fb93..6e27dd74 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.31/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.31/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.33/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.33/index.doctree index 0be294be..90d2b053 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.33/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.33/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.35/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.35/index.doctree index 367d91d0..98b83dd1 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.35/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.35/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.41/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.41/index.doctree index 15724d96..43c05105 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.41/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.41/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.42/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.42/index.doctree index 2e0ebe42..5f804e40 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.42/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.42/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.44/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.44/index.doctree index 336e137f..721386cd 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.44/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.44/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.49/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.49/index.doctree index d4a0c03e..9fe43675 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.49/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.49/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.51/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.51/index.doctree index fdcdc76b..75a07f83 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.51/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.51/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.52/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.52/index.doctree index 03f8d9fc..f1d1a851 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.52/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.52/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.61/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.61/index.doctree index 75d30a00..27525955 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.61/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.61/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.71/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.71/index.doctree index 3d774a83..50b530c6 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.71/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.71/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/index.doctree index c86f99ee..2d001dc1 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.10/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.11/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.11/index.doctree index e13dd8d3..9857eafa 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.11/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.22/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.22/index.doctree index 76f4ed49..8637d987 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.22/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.22/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.23/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.23/index.doctree index 43dfecaf..b39d037d 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.23/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.23/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/index.doctree index 019a1ac5..bb469692 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.20/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.11/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.11/index.doctree index 3de3da6b..8429449e 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.11/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.31/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.31/index.doctree index e58e6f3e..a73ef974 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.31/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.31/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.41/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.41/index.doctree index e45c81e7..187a23d1 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.41/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.41/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/index.doctree index 9e8c6d99..df846b28 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/B.30/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/index.doctree index d36bedc3..616adb35 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/B/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.10/C.10.11/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.10/C.10.11/index.doctree index d2b06dda..ac4a4fd6 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.10/C.10.11/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.10/C.10.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.10/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.10/index.doctree index 41387bb1..0f6f5e5d 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.10/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.10/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.20/C.20.11/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.20/C.20.11/index.doctree index 093ebfb3..5b50d7de 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.20/C.20.11/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.20/C.20.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.20/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.20/index.doctree index b4a86bab..46bbc399 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.20/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.20/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.11/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.11/index.doctree index ae4749d1..6efd854c 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.11/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.21/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.21/index.doctree index 58d740cc..ee773c98 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.21/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.21/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.27/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.27/index.doctree index fb0f5904..72a0417e 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.27/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.27/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.32/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.32/index.doctree index 2b8a80ca..58aec28b 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.32/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.32/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.34/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.34/index.doctree index 81b9baef..82518e51 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.34/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.34/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/index.doctree index 8ce49d58..7aec9d8a 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/C.30/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/index.doctree index f5b089bf..b269d81e 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/C/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.10/D.10.14/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.10/D.10.14/index.doctree index 2036cb2b..30230023 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.10/D.10.14/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.10/D.10.14/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.10/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.10/index.doctree index 35f2acc1..5658f50b 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.10/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.10/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.21/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.21/index.doctree index dc9e1c03..bf093615 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.21/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.21/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.22/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.22/index.doctree index 79789d19..3162ceea 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.22/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.22/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.31/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.31/index.doctree index 9f94ef4b..433a89ea 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.31/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.31/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.51/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.51/index.doctree index fad5c2ad..42fbb8ae 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.51/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.51/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.61/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.61/index.doctree index 07ff4a04..718da95d 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.61/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.61/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/index.doctree index 59abf97c..fb2bf833 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.20/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.31/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.31/index.doctree index d8b77f61..0bb18a63 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.31/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.31/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.32/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.32/index.doctree index 77cbd084..9759f8ee 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.32/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.32/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.41/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.41/index.doctree index a94a838b..065c9b7d 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.41/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.41/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.52/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.52/index.doctree index 5f9a0380..af18cd24 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.52/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.52/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.67/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.67/index.doctree index 96fbd696..1e5e3922 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.67/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.67/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/index.doctree index 0b37c41d..b2977c85 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.30/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.40/D.40.11/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.40/D.40.11/index.doctree index d3565a68..fa847a48 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.40/D.40.11/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.40/D.40.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.40/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.40/index.doctree index 39ecb07d..e0640901 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.40/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.40/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.11/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.11/index.doctree index 3febcacc..cd4f9dd5 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.11/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.11/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.12/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.12/index.doctree index 799b440e..d4162f37 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.12/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.12/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.92/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.92/index.doctree index a5dd724f..ea875613 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.92/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.92/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/index.doctree index d700d2bf..fd9d273f 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/D.50/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/index.doctree index 64925858..c5cb35b4 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/D/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/E.20/E.20.22/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/E.20/E.20.22/index.doctree index 5bef2bc1..d7aa40a1 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/E.20/E.20.22/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/E.20/E.20.22/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/E.20/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/E.20/index.doctree index aa6f8918..b833481c 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/E.20/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/E.20/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/index.doctree index 01473756..efa37ac2 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/E/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/F.10/F.10.12/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/F.10/F.10.12/index.doctree index f381baf0..78d86c1d 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/F.10/F.10.12/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/F.10/F.10.12/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/F.10/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/F.10/index.doctree index 8b215f44..0d399586 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/F.10/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/F.10/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/index.doctree index b1e05de4..b1907ba2 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/F/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/index.doctree b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/index.doctree index f629e9cf..20e1c2bd 100644 Binary files a/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/index.doctree and b/docs/.doctrees/common/dldb/repair/FEMA_P58_2nd/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/LF/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/LF/index.doctree index c311c781..69439620 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/LF/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/LF/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/NSA/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/NSA/index.doctree index c1e75f4d..3def6610 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/NSA/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/NSA/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/NSD/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/NSD/index.doctree index d58fd533..09d99d3a 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/NSD/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/NSD/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/STR/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/STR/index.doctree index 4a8ccf57..7084e328 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/STR/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/STR/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/index.doctree index 26e8b454..5afa5d7a 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_bldg/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HRD/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HRD/index.doctree index 6a4532a8..ec6bda5b 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HRD/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HRD/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HTU/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HTU/index.doctree index 2c2fae01..30abb0a9 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HTU/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HTU/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HWB/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HWB/index.doctree index cfe76885..94a527aa 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HWB/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/HWB/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/index.doctree b/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/index.doctree index ec41e0d2..05ffefd6 100644 Binary files a/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/index.doctree and b/docs/.doctrees/common/dldb/repair/Hazus_EQ_trnsp/index.doctree differ diff --git a/docs/.doctrees/common/dldb/repair/index.doctree b/docs/.doctrees/common/dldb/repair/index.doctree index dd0b18f4..e6c4698a 100644 Binary files a/docs/.doctrees/common/dldb/repair/index.doctree and b/docs/.doctrees/common/dldb/repair/index.doctree differ diff --git a/docs/.doctrees/common/front-matter/abbreviations.doctree b/docs/.doctrees/common/front-matter/abbreviations.doctree index a08a7b53..f7cc79fa 100644 Binary files a/docs/.doctrees/common/front-matter/abbreviations.doctree and b/docs/.doctrees/common/front-matter/abbreviations.doctree differ diff --git a/docs/.doctrees/common/front-matter/cite.doctree b/docs/.doctrees/common/front-matter/cite.doctree index 6549b3ee..54cb0b67 100644 Binary files a/docs/.doctrees/common/front-matter/cite.doctree and b/docs/.doctrees/common/front-matter/cite.doctree differ diff --git a/docs/.doctrees/common/front-matter/desktop/ack.doctree b/docs/.doctrees/common/front-matter/desktop/ack.doctree index 0b8ff6e2..ef9c5ff1 100644 Binary files a/docs/.doctrees/common/front-matter/desktop/ack.doctree and b/docs/.doctrees/common/front-matter/desktop/ack.doctree differ diff --git a/docs/.doctrees/common/front-matter/desktop/ack_pbe.doctree b/docs/.doctrees/common/front-matter/desktop/ack_pbe.doctree index 0cb5db79..ab573ac2 100644 Binary files a/docs/.doctrees/common/front-matter/desktop/ack_pbe.doctree and b/docs/.doctrees/common/front-matter/desktop/ack_pbe.doctree differ diff --git a/docs/.doctrees/common/front-matter/glossary.doctree b/docs/.doctrees/common/front-matter/glossary.doctree index 7e36c041..967c834f 100644 Binary files a/docs/.doctrees/common/front-matter/glossary.doctree and b/docs/.doctrees/common/front-matter/glossary.doctree differ diff --git a/docs/.doctrees/common/front-matter/license.doctree b/docs/.doctrees/common/front-matter/license.doctree index 4383a065..5588c7c9 100644 Binary files a/docs/.doctrees/common/front-matter/license.doctree and b/docs/.doctrees/common/front-matter/license.doctree differ diff --git a/docs/.doctrees/common/reqments/All-Requirements_allCols.doctree b/docs/.doctrees/common/reqments/All-Requirements_allCols.doctree index 7acae9e7..d1624a17 100644 Binary files a/docs/.doctrees/common/reqments/All-Requirements_allCols.doctree and b/docs/.doctrees/common/reqments/All-Requirements_allCols.doctree differ diff --git a/docs/.doctrees/common/reqments/HydroUQ-Requirements.doctree b/docs/.doctrees/common/reqments/HydroUQ-Requirements.doctree index c8099b05..7015cee8 100644 Binary files a/docs/.doctrees/common/reqments/HydroUQ-Requirements.doctree and b/docs/.doctrees/common/reqments/HydroUQ-Requirements.doctree differ diff --git a/docs/.doctrees/common/reqments/HydroUQ.doctree b/docs/.doctrees/common/reqments/HydroUQ.doctree index 960a53cd..7e74bddc 100644 Binary files a/docs/.doctrees/common/reqments/HydroUQ.doctree and b/docs/.doctrees/common/reqments/HydroUQ.doctree differ diff --git a/docs/.doctrees/common/reqments/key.doctree b/docs/.doctrees/common/reqments/key.doctree index 6da1808b..59c281d4 100644 Binary files a/docs/.doctrees/common/reqments/key.doctree and b/docs/.doctrees/common/reqments/key.doctree differ diff --git a/docs/.doctrees/common/reqments/reqPelicun.doctree b/docs/.doctrees/common/reqments/reqPelicun.doctree index 1cfb4481..2743c893 100644 Binary files a/docs/.doctrees/common/reqments/reqPelicun.doctree and b/docs/.doctrees/common/reqments/reqPelicun.doctree differ diff --git a/docs/.doctrees/common/reqments/reqQUOFE.doctree b/docs/.doctrees/common/reqments/reqQUOFE.doctree index ac5db5fe..4de46d5e 100644 Binary files a/docs/.doctrees/common/reqments/reqQUOFE.doctree and b/docs/.doctrees/common/reqments/reqQUOFE.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/HazardSimulationTool_useCase.doctree b/docs/.doctrees/common/technical_manual/desktop/HazardSimulationTool_useCase.doctree index 9a68a780..27a1ee4f 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/HazardSimulationTool_useCase.doctree and b/docs/.doctrees/common/technical_manual/desktop/HazardSimulationTool_useCase.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/SimCenterUQTechnical.doctree b/docs/.doctrees/common/technical_manual/desktop/SimCenterUQTechnical.doctree index fb77de87..fb8b7810 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/SimCenterUQTechnical.doctree and b/docs/.doctrees/common/technical_manual/desktop/SimCenterUQTechnical.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/UCSDUQTechnical.doctree b/docs/.doctrees/common/technical_manual/desktop/UCSDUQTechnical.doctree index c0a20015..1b247be1 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/UCSDUQTechnical.doctree and b/docs/.doctrees/common/technical_manual/desktop/UCSDUQTechnical.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/damping.doctree b/docs/.doctrees/common/technical_manual/desktop/damping.doctree index ce6fc144..a0804169 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/damping.doctree and b/docs/.doctrees/common/technical_manual/desktop/damping.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hazard_occurrence.doctree b/docs/.doctrees/common/technical_manual/desktop/hazard_occurrence.doctree index 99783670..025f4e1c 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hazard_occurrence.doctree and b/docs/.doctrees/common/technical_manual/desktop/hazard_occurrence.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/UQ/uqengine.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/UQ/uqengine.doctree index f9922b01..847d0dd6 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/UQ/uqengine.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/UQ/uqengine.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.doctree index dfa2be91..1555e121 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/kepsilon.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/kepsilon.doctree index ea0365eb..c07fcc27 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/kepsilon.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/kepsilon.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/komegasst.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/komegasst.doctree index 1de374e9..283cecf0 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/komegasst.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/cfdsolver/komegasst.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/fvm/fvm.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/fvm/fvm.doctree index 4a1365a9..c5a8ce37 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/fvm/fvm.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/fvm/fvm.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-cause.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-cause.doctree index d66e6d79..4ef3aca8 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-cause.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-cause.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-events.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-events.doctree index 587ca52b..5c1e58f6 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-events.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-events.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-numerics.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-numerics.doctree index 60a9ae1d..7109a071 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-numerics.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-numerics.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-risk.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-risk.doctree index 5ce4c14a..6f744afa 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-risk.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/surge-risk.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-cause.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-cause.doctree index 2147610f..7ff268ea 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-cause.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-cause.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-events.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-events.doctree index 8e462395..cec80c06 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-events.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-events.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-numerics.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-numerics.doctree index e83b911f..9b9668fc 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-numerics.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-numerics.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-risk.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-risk.doctree index 84004a36..e69b2b40 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-risk.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/tsu-risk.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/water.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/water.doctree index 23dbfc25..b15f92fa 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/water.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/hazards/water.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/mpm/mpm.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/mpm/mpm.doctree index 73949ee5..9d886555 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/mpm/mpm.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/mpm/mpm.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/swcfdcoupling/swcfdcoupling.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/swcfdcoupling/swcfdcoupling.doctree index 651c351c..5fa65f0b 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/swcfdcoupling/swcfdcoupling.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/swcfdcoupling/swcfdcoupling.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-output.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-output.doctree index be785625..41f9d29d 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-output.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-output.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-runtime.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-runtime.doctree index e604d067..0a66cc81 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-runtime.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-runtime.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-theory.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-theory.doctree index caed90d9..04522486 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-theory.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-theory.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-topo.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-topo.doctree index 7417e5ee..841c498d 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-topo.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/geoclaw-topo.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/simcenter-topo.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/simcenter-topo.doctree index a19d3464..38c0e4c3 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/simcenter-topo.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/simcenter-topo.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/swsolver.doctree b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/swsolver.doctree index 7900c867..246b2350 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/swsolver.doctree and b/docs/.doctrees/common/technical_manual/desktop/hydro/swsolver/swsolver.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/spatial_correlation.doctree b/docs/.doctrees/common/technical_manual/desktop/spatial_correlation.doctree index a7bbd87e..d0b0f9c3 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/spatial_correlation.doctree and b/docs/.doctrees/common/technical_manual/desktop/spatial_correlation.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/technical_manual.doctree b/docs/.doctrees/common/technical_manual/desktop/technical_manual.doctree index 5e053386..540ef26e 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/technical_manual.doctree and b/docs/.doctrees/common/technical_manual/desktop/technical_manual.doctree differ diff --git a/docs/.doctrees/common/technical_manual/desktop/uqTechnical.doctree b/docs/.doctrees/common/technical_manual/desktop/uqTechnical.doctree index 552356bd..274fe2b8 100644 Binary files a/docs/.doctrees/common/technical_manual/desktop/uqTechnical.doctree and b/docs/.doctrees/common/technical_manual/desktop/uqTechnical.doctree differ diff --git a/docs/.doctrees/common/user_manual/about/HazardSimulation/about.doctree b/docs/.doctrees/common/user_manual/about/HazardSimulation/about.doctree index f908e6cf..296006ab 100644 Binary files a/docs/.doctrees/common/user_manual/about/HazardSimulation/about.doctree and b/docs/.doctrees/common/user_manual/about/HazardSimulation/about.doctree differ diff --git a/docs/.doctrees/common/user_manual/about/Hydro/HydroUQtutorial.doctree b/docs/.doctrees/common/user_manual/about/Hydro/HydroUQtutorial.doctree index f32c82b2..aa715e22 100644 Binary files a/docs/.doctrees/common/user_manual/about/Hydro/HydroUQtutorial.doctree and b/docs/.doctrees/common/user_manual/about/Hydro/HydroUQtutorial.doctree differ diff --git a/docs/.doctrees/common/user_manual/about/Hydro/about.doctree b/docs/.doctrees/common/user_manual/about/Hydro/about.doctree index 7d8c922c..3f9dbeec 100644 Binary files a/docs/.doctrees/common/user_manual/about/Hydro/about.doctree and b/docs/.doctrees/common/user_manual/about/Hydro/about.doctree differ diff --git a/docs/.doctrees/common/user_manual/bugs.doctree b/docs/.doctrees/common/user_manual/bugs.doctree index 8f1b6d64..d48cefa9 100644 Binary files a/docs/.doctrees/common/user_manual/bugs.doctree and b/docs/.doctrees/common/user_manual/bugs.doctree differ diff --git a/docs/.doctrees/common/user_manual/dcv/Hydro/HydroUQ.doctree b/docs/.doctrees/common/user_manual/dcv/Hydro/HydroUQ.doctree index 67ebeab2..1319d101 100644 Binary files a/docs/.doctrees/common/user_manual/dcv/Hydro/HydroUQ.doctree and b/docs/.doctrees/common/user_manual/dcv/Hydro/HydroUQ.doctree differ diff --git a/docs/.doctrees/common/user_manual/examples/desktop/examples.doctree b/docs/.doctrees/common/user_manual/examples/desktop/examples.doctree index a0c725be..395065e1 100644 Binary files a/docs/.doctrees/common/user_manual/examples/desktop/examples.doctree and b/docs/.doctrees/common/user_manual/examples/desktop/examples.doctree differ diff --git a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0001/README.doctree b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0001/README.doctree index efb472c6..37feb902 100644 Binary files a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0001/README.doctree and b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0001/README.doctree differ diff --git a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0002/README.doctree b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0002/README.doctree index 524d5413..ba7d9326 100644 Binary files a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0002/README.doctree and b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0002/README.doctree differ diff --git a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0003/README.doctree b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0003/README.doctree index 6f915444..a0741495 100644 Binary files a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0003/README.doctree and b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0003/README.doctree differ diff --git a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0004/README.doctree b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0004/README.doctree index 8eefe119..5061b760 100644 Binary files a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0004/README.doctree and b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0004/README.doctree differ diff --git a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0005/README.doctree b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0005/README.doctree new file mode 100644 index 00000000..d3d0d119 Binary files /dev/null and b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0005/README.doctree differ diff --git a/docs/.doctrees/common/user_manual/examples/desktop/hdro-0010/README.doctree b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0010/README.doctree new file mode 100644 index 00000000..933a2cb1 Binary files /dev/null and b/docs/.doctrees/common/user_manual/examples/desktop/hdro-0010/README.doctree differ diff --git a/docs/.doctrees/common/user_manual/installation/desktop/downloadOther.doctree b/docs/.doctrees/common/user_manual/installation/desktop/downloadOther.doctree index 62af09c5..0b4a8c24 100644 Binary files a/docs/.doctrees/common/user_manual/installation/desktop/downloadOther.doctree and b/docs/.doctrees/common/user_manual/installation/desktop/downloadOther.doctree differ diff --git a/docs/.doctrees/common/user_manual/installation/desktop/downloadOtherMAC.doctree b/docs/.doctrees/common/user_manual/installation/desktop/downloadOtherMAC.doctree index 362b91a6..9d9a932e 100644 Binary files a/docs/.doctrees/common/user_manual/installation/desktop/downloadOtherMAC.doctree and b/docs/.doctrees/common/user_manual/installation/desktop/downloadOtherMAC.doctree differ diff --git a/docs/.doctrees/common/user_manual/installation/desktop/downloadOtherWindows.doctree b/docs/.doctrees/common/user_manual/installation/desktop/downloadOtherWindows.doctree index 6e105bd6..58649043 100644 Binary files a/docs/.doctrees/common/user_manual/installation/desktop/downloadOtherWindows.doctree and b/docs/.doctrees/common/user_manual/installation/desktop/downloadOtherWindows.doctree differ diff --git a/docs/.doctrees/common/user_manual/installation/desktop/install_Windows.doctree b/docs/.doctrees/common/user_manual/installation/desktop/install_Windows.doctree index d103b37f..508f6345 100644 Binary files a/docs/.doctrees/common/user_manual/installation/desktop/install_Windows.doctree and b/docs/.doctrees/common/user_manual/installation/desktop/install_Windows.doctree differ diff --git a/docs/.doctrees/common/user_manual/installation/desktop/install_macOS.doctree b/docs/.doctrees/common/user_manual/installation/desktop/install_macOS.doctree index 4ef57bb1..83f4a4eb 100644 Binary files a/docs/.doctrees/common/user_manual/installation/desktop/install_macOS.doctree and b/docs/.doctrees/common/user_manual/installation/desktop/install_macOS.doctree differ diff --git a/docs/.doctrees/common/user_manual/installation/desktop/installation.doctree b/docs/.doctrees/common/user_manual/installation/desktop/installation.doctree index 0b13da1c..61d94aef 100644 Binary files a/docs/.doctrees/common/user_manual/installation/desktop/installation.doctree and b/docs/.doctrees/common/user_manual/installation/desktop/installation.doctree differ diff --git a/docs/.doctrees/common/user_manual/installation/desktop/setupTACC.doctree b/docs/.doctrees/common/user_manual/installation/desktop/setupTACC.doctree new file mode 100644 index 00000000..a3169ed6 Binary files /dev/null and b/docs/.doctrees/common/user_manual/installation/desktop/setupTACC.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/eeCapabilities.doctree b/docs/.doctrees/common/user_manual/releases/eeCapabilities.doctree index 6b1e37bd..6e6bb1c1 100644 Binary files a/docs/.doctrees/common/user_manual/releases/eeCapabilities.doctree and b/docs/.doctrees/common/user_manual/releases/eeCapabilities.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/eePlans.doctree b/docs/.doctrees/common/user_manual/releases/eePlans.doctree index be456076..22c69a82 100644 Binary files a/docs/.doctrees/common/user_manual/releases/eePlans.doctree and b/docs/.doctrees/common/user_manual/releases/eePlans.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/eeReleaseNotes.doctree b/docs/.doctrees/common/user_manual/releases/eeReleaseNotes.doctree index b76a6711..88ca5851 100644 Binary files a/docs/.doctrees/common/user_manual/releases/eeReleaseNotes.doctree and b/docs/.doctrees/common/user_manual/releases/eeReleaseNotes.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/hydroCapabilities.doctree b/docs/.doctrees/common/user_manual/releases/hydroCapabilities.doctree index 7c000415..ec310921 100644 Binary files a/docs/.doctrees/common/user_manual/releases/hydroCapabilities.doctree and b/docs/.doctrees/common/user_manual/releases/hydroCapabilities.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/hydroPlans.doctree b/docs/.doctrees/common/user_manual/releases/hydroPlans.doctree index 1f02c1f0..dee3b80c 100644 Binary files a/docs/.doctrees/common/user_manual/releases/hydroPlans.doctree and b/docs/.doctrees/common/user_manual/releases/hydroPlans.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/hydroReleaseNotes.doctree b/docs/.doctrees/common/user_manual/releases/hydroReleaseNotes.doctree index 9b0db273..b2745e36 100644 Binary files a/docs/.doctrees/common/user_manual/releases/hydroReleaseNotes.doctree and b/docs/.doctrees/common/user_manual/releases/hydroReleaseNotes.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/pbeCapabilities.doctree b/docs/.doctrees/common/user_manual/releases/pbeCapabilities.doctree index fc4337a1..dbd9d158 100644 Binary files a/docs/.doctrees/common/user_manual/releases/pbeCapabilities.doctree and b/docs/.doctrees/common/user_manual/releases/pbeCapabilities.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/pbePlans.doctree b/docs/.doctrees/common/user_manual/releases/pbePlans.doctree index 1b29a869..e9552839 100644 Binary files a/docs/.doctrees/common/user_manual/releases/pbePlans.doctree and b/docs/.doctrees/common/user_manual/releases/pbePlans.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/pbeReleaseNotes.doctree b/docs/.doctrees/common/user_manual/releases/pbeReleaseNotes.doctree index ef7bef94..8385f07e 100644 Binary files a/docs/.doctrees/common/user_manual/releases/pbeReleaseNotes.doctree and b/docs/.doctrees/common/user_manual/releases/pbeReleaseNotes.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/quoCapabilities.doctree b/docs/.doctrees/common/user_manual/releases/quoCapabilities.doctree index c1d23229..3674e569 100644 Binary files a/docs/.doctrees/common/user_manual/releases/quoCapabilities.doctree and b/docs/.doctrees/common/user_manual/releases/quoCapabilities.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/quoPlans.doctree b/docs/.doctrees/common/user_manual/releases/quoPlans.doctree index 1b3bb50e..db1298dd 100644 Binary files a/docs/.doctrees/common/user_manual/releases/quoPlans.doctree and b/docs/.doctrees/common/user_manual/releases/quoPlans.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/quoReleaseNotes.doctree b/docs/.doctrees/common/user_manual/releases/quoReleaseNotes.doctree index 1a6264ad..d58fc97f 100644 Binary files a/docs/.doctrees/common/user_manual/releases/quoReleaseNotes.doctree and b/docs/.doctrees/common/user_manual/releases/quoReleaseNotes.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/r2dCapabilities.doctree b/docs/.doctrees/common/user_manual/releases/r2dCapabilities.doctree index 3429a0c9..1b485ff4 100644 Binary files a/docs/.doctrees/common/user_manual/releases/r2dCapabilities.doctree and b/docs/.doctrees/common/user_manual/releases/r2dCapabilities.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/r2dPlans.doctree b/docs/.doctrees/common/user_manual/releases/r2dPlans.doctree index a1cf71b4..cb0a9eee 100644 Binary files a/docs/.doctrees/common/user_manual/releases/r2dPlans.doctree and b/docs/.doctrees/common/user_manual/releases/r2dPlans.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/r2dRelaseNotes.doctree b/docs/.doctrees/common/user_manual/releases/r2dRelaseNotes.doctree index cfcc8f77..baee1c37 100644 Binary files a/docs/.doctrees/common/user_manual/releases/r2dRelaseNotes.doctree and b/docs/.doctrees/common/user_manual/releases/r2dRelaseNotes.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/r2dReleaseNotes.doctree b/docs/.doctrees/common/user_manual/releases/r2dReleaseNotes.doctree index 7f8a038a..17432e15 100644 Binary files a/docs/.doctrees/common/user_manual/releases/r2dReleaseNotes.doctree and b/docs/.doctrees/common/user_manual/releases/r2dReleaseNotes.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/weCapabilities.doctree b/docs/.doctrees/common/user_manual/releases/weCapabilities.doctree index b8bdc335..bd92117f 100644 Binary files a/docs/.doctrees/common/user_manual/releases/weCapabilities.doctree and b/docs/.doctrees/common/user_manual/releases/weCapabilities.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/wePlans.doctree b/docs/.doctrees/common/user_manual/releases/wePlans.doctree index f92457a0..2e0ae884 100644 Binary files a/docs/.doctrees/common/user_manual/releases/wePlans.doctree and b/docs/.doctrees/common/user_manual/releases/wePlans.doctree differ diff --git a/docs/.doctrees/common/user_manual/releases/weReleaseNotes.doctree b/docs/.doctrees/common/user_manual/releases/weReleaseNotes.doctree index fb2cba05..4e1943be 100644 Binary files a/docs/.doctrees/common/user_manual/releases/weReleaseNotes.doctree and b/docs/.doctrees/common/user_manual/releases/weReleaseNotes.doctree differ diff --git a/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshooting.doctree b/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshooting.doctree index be98a381..ee622db4 100644 Binary files a/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshooting.doctree and b/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshooting.doctree differ diff --git a/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshootingRunning.doctree b/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshootingRunning.doctree index 11817e3d..e4a3ce80 100644 Binary files a/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshootingRunning.doctree and b/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshootingRunning.doctree differ diff --git a/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshootingStartup.doctree b/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshootingStartup.doctree index 24154231..0146e989 100644 Binary files a/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshootingStartup.doctree and b/docs/.doctrees/common/user_manual/troubleshooting/desktop/troubleshootingStartup.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/Configuring_CustomUQ.doctree b/docs/.doctrees/common/user_manual/usage/desktop/Configuring_CustomUQ.doctree index 742581ad..2791a43a 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/Configuring_CustomUQ.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/Configuring_CustomUQ.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/DakotaBayesianCalibration.doctree b/docs/.doctrees/common/user_manual/usage/desktop/DakotaBayesianCalibration.doctree index 4dcb757d..5e7b3f29 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/DakotaBayesianCalibration.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/DakotaBayesianCalibration.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/DakotaDeterministicCalibration.doctree b/docs/.doctrees/common/user_manual/usage/desktop/DakotaDeterministicCalibration.doctree index f98e0f5b..e6fb2fc2 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/DakotaDeterministicCalibration.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/DakotaDeterministicCalibration.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/DakotaGradientFreeOptimization.doctree b/docs/.doctrees/common/user_manual/usage/desktop/DakotaGradientFreeOptimization.doctree index 5e7bec10..03e195bd 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/DakotaGradientFreeOptimization.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/DakotaGradientFreeOptimization.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/DakotaReliability.doctree b/docs/.doctrees/common/user_manual/usage/desktop/DakotaReliability.doctree index abb5b1df..e26292cf 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/DakotaReliability.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/DakotaReliability.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/DakotaSampling.doctree b/docs/.doctrees/common/user_manual/usage/desktop/DakotaSampling.doctree index e9f595c5..53055b92 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/DakotaSampling.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/DakotaSampling.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/DakotaSensitivity.doctree b/docs/.doctrees/common/user_manual/usage/desktop/DakotaSensitivity.doctree index 73880c64..d1ab893b 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/DakotaSensitivity.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/DakotaSensitivity.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/FEM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/FEM.doctree index 3361257c..8a277878 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/FEM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/FEM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/GI.doctree b/docs/.doctrees/common/user_manual/usage/desktop/GI.doctree index c1d14276..9e5c5e78 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/GI.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/GI.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/RV.doctree b/docs/.doctrees/common/user_manual/usage/desktop/RV.doctree index 6d558d3c..db1e1593 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/RV.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/RV.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/SIM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/SIM.doctree index 8c5141fc..f3ba551b 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/SIM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/SIM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQ.doctree b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQ.doctree index a3c5a9b2..1ec9a0bd 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQ.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQ.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQMF.doctree b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQMF.doctree index 801edb3f..57d4d305 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQMF.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQMF.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQPLoM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQPLoM.doctree index 7a4a2cdd..3d54e379 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQPLoM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQPLoM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSampling.doctree b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSampling.doctree index 13c877cb..8033aa01 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSampling.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSampling.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSensitivity.doctree b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSensitivity.doctree index 567db6c8..c9c5896a 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSensitivity.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSensitivity.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSurrogate.doctree b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSurrogate.doctree index a318feb2..179328c7 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSurrogate.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/SimCenterUQSurrogate.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/UCSD_UQ_Hierarchical.doctree b/docs/.doctrees/common/user_manual/usage/desktop/UCSD_UQ_Hierarchical.doctree index 8645dd93..8a4e27f3 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/UCSD_UQ_Hierarchical.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/UCSD_UQ_Hierarchical.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/UCSD_UQ_TMCMC.doctree b/docs/.doctrees/common/user_manual/usage/desktop/UCSD_UQ_TMCMC.doctree index 45f94f09..2025efc8 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/UCSD_UQ_TMCMC.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/UCSD_UQ_TMCMC.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/UQ.doctree b/docs/.doctrees/common/user_manual/usage/desktop/UQ.doctree index ec60f188..d45e97ca 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/UQ.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/UQ.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/BodiesMPM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/BodiesMPM.doctree index 1768afb1..dd1114e9 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/BodiesMPM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/BodiesMPM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/BoundariesMPM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/BoundariesMPM.doctree index 32f6d646..db7e419c 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/BoundariesMPM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/BoundariesMPM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Boundary.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Boundary.doctree index fb06af4f..cb8bc5da 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Boundary.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Boundary.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaR.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaR.doctree index fa56780a..221edeac 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaR.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaR.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaSa.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaSa.doctree index 1cd0bc0a..ed534e4d 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaSa.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaSa.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaSe.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaSe.doctree index 12c98696..0edf623d 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaSe.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/DakotaSe.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/EVT.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/EVT.doctree index 464f5a59..334b9d10 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/EVT.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/EVT.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/FEM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/FEM.doctree index bbecf95b..7389af71 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/FEM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/FEM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry.doctree index f6348d20..8e8d0dc1 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_Bathy.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_Bathy.doctree index 7920dcd5..f17a5b6f 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_Bathy.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_Bathy.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_STL.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_STL.doctree index 07a087af..67d75b72 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_STL.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_STL.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_SWCFD.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_SWCFD.doctree index b9470ab0..a6dc86cb 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_SWCFD.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_SWCFD.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_WFlume.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_WFlume.doctree index 87aabbb2..a1c9573a 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_WFlume.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Geometry/Geom_WFlume.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Initial.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Initial.doctree index aa364ce7..e9c6dfaa 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Initial.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Initial.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/MPM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/MPM.doctree index 811e75a2..f09d0489 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/MPM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/MPM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/MaterialMPM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/MaterialMPM.doctree index a368702e..1fa6c4e4 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/MaterialMPM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/MaterialMPM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Materials.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Materials.doctree index aa6e4bff..151b79a6 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Materials.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Materials.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Meshing.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Meshing.doctree index aec02489..30d33fce 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Meshing.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Meshing.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/OutputsMPM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/OutputsMPM.doctree index 7af223a3..e68f75c4 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/OutputsMPM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/OutputsMPM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Project.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Project.doctree index 45bc366b..8ac086ab 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Project.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Project.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/SensorsMPM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/SensorsMPM.doctree index 1f5dd757..46656a83 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/SensorsMPM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/SensorsMPM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/SettingsMPM.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/SettingsMPM.doctree index 227eafb2..a4bcf161 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/SettingsMPM.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/SettingsMPM.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Solver.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Solver.doctree index 130be1c2..e03bfcd8 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/Solver.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/Solver.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/bestpractices.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/bestpractices.doctree index a1ed0a6c..273f6a5a 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/bestpractices.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/bestpractices.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/coupled.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/coupled.doctree index bebfa154..9c10c539 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/coupled.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/coupled.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/errors.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/errors.doctree index 1b2afa87..e9fae847 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/errors.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/errors.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/general.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/general.doctree index 3384e461..69dd055b 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/general.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/general.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/helpvideo.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/helpvideo.doctree index e5dfe7e3..51e9b7f5 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/helpvideo.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/helpvideo.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/releasenotes.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/releasenotes.doctree index e85e471c..fd70abe8 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/releasenotes.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/releasenotes.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/resHydro.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/resHydro.doctree index d2a0eaf8..a5b03f76 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/resHydro.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/resHydro.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/tools.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/tools.doctree index 292f6ad9..75d32631 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/tools.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/tools.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/hydro/uguide.doctree b/docs/.doctrees/common/user_manual/usage/desktop/hydro/uguide.doctree index f09eafce..5682ff39 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/hydro/uguide.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/hydro/uguide.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/response/EDP.doctree b/docs/.doctrees/common/user_manual/usage/desktop/response/EDP.doctree index e5e72412..fd8b4b2a 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/response/EDP.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/response/EDP.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/response/resEE.doctree b/docs/.doctrees/common/user_manual/usage/desktop/response/resEE.doctree index 3c006f65..5da0f12e 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/response/resEE.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/response/resEE.doctree differ diff --git a/docs/.doctrees/common/user_manual/usage/desktop/usage.doctree b/docs/.doctrees/common/user_manual/usage/desktop/usage.doctree index 71ce073b..0fd4db08 100644 Binary files a/docs/.doctrees/common/user_manual/usage/desktop/usage.doctree and b/docs/.doctrees/common/user_manual/usage/desktop/usage.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Input_Documentation_Tables.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Input_Documentation_Tables.doctree index 8c03472e..9019069f 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Input_Documentation_Tables.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Input_Documentation_Tables.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ConcreteBuildingModel.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ConcreteBuildingModel.doctree index 49c3525a..5c114429 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ConcreteBuildingModel.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ConcreteBuildingModel.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/CustomPy.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/CustomPy.doctree index 56d02166..587708c4 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/CustomPy.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/CustomPy.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/CustomPySimulation.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/CustomPySimulation.doctree index c115ac01..ef80dffd 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/CustomPySimulation.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/CustomPySimulation.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputBayesianCalibration.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputBayesianCalibration.doctree index ab5c66cd..c4255fff 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputBayesianCalibration.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputBayesianCalibration.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputCalibration.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputCalibration.doctree index 23f19e18..0ea2ee80 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputCalibration.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputCalibration.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputOptimization.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputOptimization.doctree index c0f34665..c7e71809 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputOptimization.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputOptimization.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputReliability.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputReliability.doctree index e531ac78..2b561a70 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputReliability.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputReliability.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputSampling.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputSampling.doctree index 7d2ae2c7..26ba8ae1 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputSampling.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputSampling.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputSensitivity.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputSensitivity.doctree index fdbe54ce..cce9563f 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputSensitivity.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/DakotaInputSensitivity.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/EDP.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/EDP.doctree index 1ef8e51b..ba22694e 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/EDP.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/EDP.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/EDP_EarthquakeSelection.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/EDP_EarthquakeSelection.doctree index d9a7b2f9..d6de7d58 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/EDP_EarthquakeSelection.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/EDP_EarthquakeSelection.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ExampleWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ExampleWidget.doctree index 517f2e04..e7fa8686 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ExampleWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ExampleWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ExistingSimCenterEvents.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ExistingSimCenterEvents.doctree index 9a8fa220..b239d8b0 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ExistingSimCenterEvents.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ExistingSimCenterEvents.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/GaussianProcessInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/GaussianProcessInputWidget.doctree index ea39b20c..50a0a262 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/GaussianProcessInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/GaussianProcessInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/GlobalReliabilityWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/GlobalReliabilityWidget.doctree index d87d9b66..00e96709 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/GlobalReliabilityWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/GlobalReliabilityWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ImportSamplesWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ImportSamplesWidget.doctree index 02e687b8..1c818932 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ImportSamplesWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ImportSamplesWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ImportanceSamplingInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ImportanceSamplingInputWidget.doctree index 5ed9e093..fb1c614a 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ImportanceSamplingInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/ImportanceSamplingInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetBIM.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetBIM.doctree index c6269917..a045de0d 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetBIM.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetBIM.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetExistingEvent.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetExistingEvent.doctree index 7232d7ab..74e2890a 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetExistingEvent.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetExistingEvent.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetOpenSeesAnalysis.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetOpenSeesAnalysis.doctree index 85bf165c..87f80de2 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetOpenSeesAnalysis.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/InputWidgetOpenSeesAnalysis.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/LatinHypercubeInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/LatinHypercubeInputWidget.doctree index 9250e274..4f370808 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/LatinHypercubeInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/LatinHypercubeInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/LocalReliabilityWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/LocalReliabilityWidget.doctree index 23a233ac..66ec6af9 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/LocalReliabilityWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/LocalReliabilityWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MDOF_BuildingModel.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MDOF_BuildingModel.doctree index 5f03c70b..bd3453b7 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MDOF_BuildingModel.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MDOF_BuildingModel.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MDOF_LU.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MDOF_LU.doctree index a0182bf2..b22779a2 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MDOF_LU.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MDOF_LU.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MonteCarloInputSimWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MonteCarloInputSimWidget.doctree index dc0bab5c..298f5e8b 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MonteCarloInputSimWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MonteCarloInputSimWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MonteCarloInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MonteCarloInputWidget.doctree index 02e5d821..60594909 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MonteCarloInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MonteCarloInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MultiFidelityMonteCarlo.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MultiFidelityMonteCarlo.doctree index 6b3c0c6d..b0993b4a 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MultiFidelityMonteCarlo.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MultiFidelityMonteCarlo.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MultiFidelitySimWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MultiFidelitySimWidget.doctree index 6e81795e..b70356a2 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MultiFidelitySimWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/MultiFidelitySimWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/NoneEngine.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/NoneEngine.doctree index 95e0cac7..b421d80f 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/NoneEngine.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/NoneEngine.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/OpenSeesBuildingModel.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/OpenSeesBuildingModel.doctree index 1df48536..ca9425d2 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/OpenSeesBuildingModel.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/OpenSeesBuildingModel.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PCEInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PCEInputWidget.doctree index c6363d2a..d8f0fa61 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PCEInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PCEInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PLoMInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PLoMInputWidget.doctree index 83ed58cf..853a8556 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PLoMInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PLoMInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PLoMSimuWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PLoMSimuWidget.doctree index 0a96d777..c8981e0a 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PLoMSimuWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/PLoMSimuWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterIntensityMeasureCombo.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterIntensityMeasureCombo.doctree index 36b2fa7f..7e08debf 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterIntensityMeasureCombo.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterIntensityMeasureCombo.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterIntensityMeasureWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterIntensityMeasureWidget.doctree index 55bfe8ca..dc0613ae 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterIntensityMeasureWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterIntensityMeasureWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputPLoM.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputPLoM.doctree index a26dc483..616d271c 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputPLoM.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputPLoM.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSampling.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSampling.doctree index 3fb97928..68af4afd 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSampling.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSampling.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSensitivity.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSensitivity.doctree index 0260b7c2..98a5cdd7 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSensitivity.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSensitivity.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSurrogate.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSurrogate.doctree index 48c3c6af..8a1877af 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSurrogate.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUQInputSurrogate.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUnitsCombo.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUnitsCombo.doctree index ee9b4efe..af833a17 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUnitsCombo.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SimCenterUnitsCombo.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/StandardEDP.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/StandardEDP.doctree index b5d74524..9ec6722a 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/StandardEDP.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/StandardEDP.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/StandardEarthquakeEDP.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/StandardEarthquakeEDP.doctree index 9921ebd3..d647f089 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/StandardEarthquakeEDP.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/StandardEarthquakeEDP.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SteelBuildingModel.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SteelBuildingModel.doctree index c8811136..796a5834 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SteelBuildingModel.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SteelBuildingModel.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateDoEInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateDoEInputWidget.doctree index fd61c39b..5c9388e2 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateDoEInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateDoEInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateEDP.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateEDP.doctree index 42bf895c..af0e87db 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateEDP.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateEDP.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateGP.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateGP.doctree index e015dd46..82017399 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateGP.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateGP.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateMFInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateMFInputWidget.doctree index 1b17ffa3..ef6bb565 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateMFInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateMFInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateNoDoEInputWidget.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateNoDoEInputWidget.doctree index fa049351..9d303571 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateNoDoEInputWidget.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateNoDoEInputWidget.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateSimulation.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateSimulation.doctree index 8d89286f..3889598a 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateSimulation.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/SurrogateSimulation.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputBayesianCalibration.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputBayesianCalibration.doctree index 7d7acf73..e7583593 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputBayesianCalibration.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputBayesianCalibration.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputHierarchicalBayesian.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputHierarchicalBayesian.doctree index 8db3da4d..bddff58d 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputHierarchicalBayesian.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputHierarchicalBayesian.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputTMCMC.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputTMCMC.doctree index 8319d777..a933ed46 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputTMCMC.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UCSD_InputTMCMC.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UQpyStretch.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UQpyStretch.doctree index 3f4c31c8..fc271eaa 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UQpyStretch.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UQpyStretch.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UQpySubsetSimulation.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UQpySubsetSimulation.doctree index 0acf70ce..a0081c28 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UQpySubsetSimulation.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UQpySubsetSimulation.doctree differ diff --git a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UserDefinedEDP.doctree b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UserDefinedEDP.doctree index f2890594..a309cba9 100644 Binary files a/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UserDefinedEDP.doctree and b/docs/.doctrees/common/user_manual/user_inputs_documentation/User_Inputs_Documentation_RST_Files/UserDefinedEDP.doctree differ diff --git a/docs/.doctrees/environment.pickle b/docs/.doctrees/environment.pickle index 4aa10e54..d4ea756c 100644 Binary files a/docs/.doctrees/environment.pickle and b/docs/.doctrees/environment.pickle differ diff --git a/docs/.doctrees/index.doctree b/docs/.doctrees/index.doctree index ca851abc..a629c78e 100644 Binary files a/docs/.doctrees/index.doctree and b/docs/.doctrees/index.doctree differ diff --git a/docs/_downloads/b185f33f0f91b8d5d870c2add615082f/input_data.zip b/docs/_downloads/b185f33f0f91b8d5d870c2add615082f/input_data.zip new file mode 100644 index 00000000..a58ab76e Binary files /dev/null and b/docs/_downloads/b185f33f0f91b8d5d870c2add615082f/input_data.zip differ diff --git a/docs/_images/Credentials4.png b/docs/_images/Credentials4.png new file mode 100644 index 00000000..36e16535 Binary files /dev/null and b/docs/_images/Credentials4.png differ diff --git a/docs/_images/FEM.png b/docs/_images/FEM.png new file mode 100644 index 00000000..b09f8bce Binary files /dev/null and b/docs/_images/FEM.png differ diff --git a/docs/_images/Forces1.png b/docs/_images/Forces1.png deleted file mode 100644 index 8528d060..00000000 Binary files a/docs/_images/Forces1.png and /dev/null differ diff --git a/docs/_images/MatlabScriptCopyToLocation1.PNG b/docs/_images/MatlabScriptCopyToLocation1.PNG deleted file mode 100644 index 750a3025..00000000 Binary files a/docs/_images/MatlabScriptCopyToLocation1.PNG and /dev/null differ diff --git a/docs/_images/Moments1.png b/docs/_images/Moments1.png deleted file mode 100644 index 259ef615..00000000 Binary files a/docs/_images/Moments1.png and /dev/null differ diff --git a/docs/_images/Paraview1.PNG b/docs/_images/Paraview1.PNG deleted file mode 100644 index a2b29059..00000000 Binary files a/docs/_images/Paraview1.PNG and /dev/null differ diff --git a/docs/_images/Pressures.png b/docs/_images/Pressures.png deleted file mode 100644 index b7e5d210..00000000 Binary files a/docs/_images/Pressures.png and /dev/null differ diff --git a/docs/_images/ReactionForces1.png b/docs/_images/ReactionForces1.png deleted file mode 100644 index 10873752..00000000 Binary files a/docs/_images/ReactionForces1.png and /dev/null differ diff --git a/docs/_images/RemoteJobPanel_sWHALE.png b/docs/_images/RemoteJobPanel_sWHALE.png index b4d4155e..4d004665 100644 Binary files a/docs/_images/RemoteJobPanel_sWHALE.png and b/docs/_images/RemoteJobPanel_sWHALE.png differ diff --git a/docs/_images/TipDisplacement1.png b/docs/_images/TipDisplacement1.png deleted file mode 100644 index f9758244..00000000 Binary files a/docs/_images/TipDisplacement1.png and /dev/null differ diff --git a/docs/_images/Velocities1.png b/docs/_images/Velocities1.png deleted file mode 100644 index d372afa0..00000000 Binary files a/docs/_images/Velocities1.png and /dev/null differ diff --git a/docs/_images/WaveGauges1.png b/docs/_images/WaveGauges1.png deleted file mode 100644 index 6db844f5..00000000 Binary files a/docs/_images/WaveGauges1.png and /dev/null differ diff --git a/docs/_images/backendapps_RegionalMapping.png b/docs/_images/backendapps_RegionalMapping.png deleted file mode 100644 index c7233edf..00000000 Binary files a/docs/_images/backendapps_RegionalMapping.png and /dev/null differ diff --git a/docs/_images/hdro-0005_EDP.png b/docs/_images/hdro-0005_EDP.png new file mode 100644 index 00000000..0da7f0a3 Binary files /dev/null and b/docs/_images/hdro-0005_EDP.png differ diff --git a/docs/_images/hdro-0005_EVT.png b/docs/_images/hdro-0005_EVT.png new file mode 100644 index 00000000..4a410bf6 Binary files /dev/null and b/docs/_images/hdro-0005_EVT.png differ diff --git a/docs/_images/hdro-0005_GI.png b/docs/_images/hdro-0005_GI.png new file mode 100644 index 00000000..a1d168c0 Binary files /dev/null and b/docs/_images/hdro-0005_GI.png differ diff --git a/docs/_images/hdro-0005_IntegratedPileLoads.png b/docs/_images/hdro-0005_IntegratedPileLoads.png new file mode 100644 index 00000000..1cb87c9e Binary files /dev/null and b/docs/_images/hdro-0005_IntegratedPileLoads.png differ diff --git a/docs/_images/hdro-0005_RES_Cumulative_Forward.png b/docs/_images/hdro-0005_RES_Cumulative_Forward.png new file mode 100644 index 00000000..d264e108 Binary files /dev/null and b/docs/_images/hdro-0005_RES_Cumulative_Forward.png differ diff --git a/docs/_images/hdro-0005_RES_Scatter.png b/docs/_images/hdro-0005_RES_Scatter.png new file mode 100644 index 00000000..1e45d693 Binary files /dev/null and b/docs/_images/hdro-0005_RES_Scatter.png differ diff --git a/docs/_images/hdro-0005_RES_Scatter_Sensitivity.png b/docs/_images/hdro-0005_RES_Scatter_Sensitivity.png new file mode 100644 index 00000000..1c99b43e Binary files /dev/null and b/docs/_images/hdro-0005_RES_Scatter_Sensitivity.png differ diff --git a/docs/_images/hdro-0005_RES_Summary_Forward.png b/docs/_images/hdro-0005_RES_Summary_Forward.png new file mode 100644 index 00000000..82fe2b69 Binary files /dev/null and b/docs/_images/hdro-0005_RES_Summary_Forward.png differ diff --git a/docs/_images/hdro-0005_RES_Summary_Reliability.png b/docs/_images/hdro-0005_RES_Summary_Reliability.png new file mode 100644 index 00000000..8bcc8b64 Binary files /dev/null and b/docs/_images/hdro-0005_RES_Summary_Reliability.png differ diff --git a/docs/_images/hdro-0005_RES_Summary_Sensitivity.png b/docs/_images/hdro-0005_RES_Summary_Sensitivity.png new file mode 100644 index 00000000..86ddb936 Binary files /dev/null and b/docs/_images/hdro-0005_RES_Summary_Sensitivity.png differ diff --git a/docs/_images/hdro-0005_RV.png b/docs/_images/hdro-0005_RV.png new file mode 100644 index 00000000..a76535d9 Binary files /dev/null and b/docs/_images/hdro-0005_RV.png differ diff --git a/docs/_images/hdro-0005_RV_Sensitivity.png b/docs/_images/hdro-0005_RV_Sensitivity.png new file mode 100644 index 00000000..dffe9cbf Binary files /dev/null and b/docs/_images/hdro-0005_RV_Sensitivity.png differ diff --git a/docs/_images/hdro-0005_SIM.png b/docs/_images/hdro-0005_SIM.png new file mode 100644 index 00000000..b27744c2 Binary files /dev/null and b/docs/_images/hdro-0005_SIM.png differ diff --git a/docs/_images/hdro-0005_UQ.png b/docs/_images/hdro-0005_UQ.png new file mode 100644 index 00000000..5c9e6df1 Binary files /dev/null and b/docs/_images/hdro-0005_UQ.png differ diff --git a/docs/_images/hdro-0005_WaveTimeSeries.png b/docs/_images/hdro-0005_WaveTimeSeries.png new file mode 100644 index 00000000..3ad3d1e5 Binary files /dev/null and b/docs/_images/hdro-0005_WaveTimeSeries.png differ diff --git a/docs/_images/hdro-0005_forces.png b/docs/_images/hdro-0005_forces.png new file mode 100644 index 00000000..576b711a Binary files /dev/null and b/docs/_images/hdro-0005_forces.png differ diff --git a/docs/_images/hdro-0005_moments.png b/docs/_images/hdro-0005_moments.png new file mode 100644 index 00000000..453f4c7e Binary files /dev/null and b/docs/_images/hdro-0005_moments.png differ diff --git a/docs/_images/hdro-0010_EVT.png b/docs/_images/hdro-0010_EVT.png new file mode 100644 index 00000000..534d82ab Binary files /dev/null and b/docs/_images/hdro-0010_EVT.png differ diff --git a/docs/_images/hdro-0010_EVT_Single.png b/docs/_images/hdro-0010_EVT_Single.png new file mode 100644 index 00000000..82b6a66f Binary files /dev/null and b/docs/_images/hdro-0010_EVT_Single.png differ diff --git a/docs/_images/pythonDownload.png b/docs/_images/pythonDownload.png deleted file mode 100644 index 3091b1fd..00000000 Binary files a/docs/_images/pythonDownload.png and /dev/null differ diff --git a/docs/_images/results1.png b/docs/_images/results1.png deleted file mode 100644 index cb5de279..00000000 Binary files a/docs/_images/results1.png and /dev/null differ diff --git a/docs/_images/storyForces1.png b/docs/_images/storyForces1.png deleted file mode 100644 index 205cb9c5..00000000 Binary files a/docs/_images/storyForces1.png and /dev/null differ diff --git a/docs/_sources/common/developer_manual/architecture/desktop/applications/DLApps.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/applications/DLApps.rst.txt index cc5bfbef..418231e2 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/applications/DLApps.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/applications/DLApps.rst.txt @@ -3,25 +3,11 @@ DL Applications =============== -The **DL application** performs the damage and loss assessment for the buildings subject to the regional event(s). -It takes as input the building properties used for determining damages and losses (e. g. building occupancy, structure type, replacement cost, number of stories), -specified in the :ref:`BIM file `, as well as the response simulation output recorded in the :ref:`EDP file `. -It returns damage probabilities in a "DM.csv" file and decision variable estimates in a "DV.csv" for each simulation, saved in its corresponding -**simulation working directory**. +The **DL application** assesses the damage and loss for buildings subjected to regional events.It uses building properties, such as building occupancy, structure type, replacement cost, and number of stories, to determine damages and losses. These properties are specified in the :ref:`BIM file `. The application also uses the response simulation output recorded in the :ref:`EDP file `. +The application returns damage probabilities in a "DM.csv" file and decision variable estimates in a "DV.csv" file for each simulation. These files are saved in their respective **simulation working directories**. .. figure:: _static/images/backendapps_DL.png :align: center :figclass: align-center - -The following options for DL applications vary in the software package used to perform the damage and loss assessment. - - - -.. rendre:: cli-gallery - :data-file: $SIMCENTER_DEV/SimCenterBackendApplications/meta/backends.cache.json - :load-defaults: $SIMCENTER_DEV/SimCenterBackendApplications/meta/index.yaml#/$SIMDOC_APP - - :include-exclusive: %./categories:performDL - diff --git a/docs/_sources/common/developer_manual/architecture/desktop/applications/EDPApps.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/applications/EDPApps.rst.txt index 7f89634e..37fbf463 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/applications/EDPApps.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/applications/EDPApps.rst.txt @@ -13,19 +13,6 @@ Note that in the EDP file, DOF=1,2 are assumed to correspond to perpendicular ho :align: center :figclass: align-center - - -The following options for EDP applications vary in the type of EDPs identified for the simulation output. - - - -.. rendre:: cli-gallery - :data-file: $SIMCENTER_DEV/SimCenterBackendApplications/meta/backends.cache.json - :load-defaults: $SIMCENTER_DEV/SimCenterBackendApplications/meta/index.yaml#/$SIMDOC_APP - - :include-exclusive: %./categories:createEDP - - .. only:: HydroUQ_app .. raw:: html diff --git a/docs/_sources/common/developer_manual/architecture/desktop/applications/UQApps.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/applications/UQApps.rst.txt index 3f8d05e1..8752cd89 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/applications/UQApps.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/applications/UQApps.rst.txt @@ -3,26 +3,14 @@ UQ Applications =============== -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. - +The **UQ application** is used to sample *random variables* (RVs) specified in any of the workflow steps (Event, Modeling, EDP, Simulation) for uncertainty quantification. It then runs commands written in the **driver file**, which call on the backend applications to execute the R2D Workflow. +First, it 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, the UQ application directly runs commands in the driver file without performing random sampling. .. figure:: _static/images/backendapps_UQ.png :align: center :figclass: align-center - -The following options for UQ applications vary in the software package used to perform uncertainty quantification. - - -.. rendre:: cli-gallery - :data-file: $SIMCENTER_DEV/SimCenterBackendApplications/meta/backends.cache.json - :load-defaults: $SIMCENTER_DEV/SimCenterBackendApplications/meta/index.yaml#/$SIMDOC_APP - - :include-exclusive: %./categories:performUQ - - .. only:: HydroUQ_app .. raw:: html diff --git a/docs/_sources/common/developer_manual/architecture/desktop/applications/buildingApps.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/applications/buildingApps.rst.txt index 1159f1fb..8b15e132 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/applications/buildingApps.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/applications/buildingApps.rst.txt @@ -3,26 +3,13 @@ Building Applications ===================== - -The **building application** creates *building information model* (BIM) files for each building. It takes as input the range of asset IDs selected for simulation (expressed as "min" and "max" ID, specified in the :ref:`configuration file `) and the building-specific parameters for each simulation (specified in the :ref:`building source file `). -The inputs are parsed into ``#-BIM.json`` files in the **results** folder. +The **Building Application** creates *Building Information Model* (BIM) files for each building. It takes as input the range of asset IDs selected for simulation (expressed as "min" and "max" ID, specified in the :ref:`configuration file `), and the building-specific parameters for each simulation (specified in the :ref:`building source file `). +These inputs are parsed into ``#-BIM.json`` files, which are stored in the **results** folder. .. figure:: _static/images/backendapps_Building.png :align: center :figclass: align-center - -The following options for building applications vary in the file type of the input building source file it processes. - - - -.. rendre:: cli-gallery - :data-file: $SIMCENTER_DEV/SimCenterBackendApplications/meta/backends.cache.json - :load-defaults: $SIMCENTER_DEV/SimCenterBackendApplications/meta/index.yaml#/$SIMDOC_APP - - :include-exclusive: %./categories:createBIM - - .. only:: HydroUQ_app .. raw:: html diff --git a/docs/_sources/common/developer_manual/architecture/desktop/applications/eventApps.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/applications/eventApps.rst.txt index 2a9ec24c..97f4195d 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/applications/eventApps.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/applications/eventApps.rst.txt @@ -3,25 +3,15 @@ Event Applications ================== -The **event application** takes the event(s) selected for a building site, associates each one with a simulation, and creates EVENT files containing the event intensity measures. It obtains the name of the event from the :ref:`BIM file ` and the intensity measure information from the input :ref:`event files `. -This input information is saved in an ``EVENT.json`` file, located in its corresponding **simulation working directory**. +The **event application** takes the selected event(s) for a building site, associates each one with a simulation, and creates EVENT files containing the event intensity measures. It obtains the name of the event from the :ref:`BIM file ` and the intensity measure information from the input :ref:`event files `. +This input information is saved in an ``EVENT.json`` file, located in the corresponding **simulation working directory**. .. figure:: _static/images/backendapps_Events.png :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 that it processes. - - - - -.. rendre:: cli-gallery - :data-file: $SIMCENTER_DEV/SimCenterBackendApplications/meta/backends.cache.json - :load-defaults: $SIMCENTER_DEV/SimCenterBackendApplications/meta/index.yaml#/$SIMDOC_APP - - :include-exclusive: %./categories:createEVENT - +The following options for event applications vary in the type of event, event properties, and the format of the event file that they process. .. only:: HydroUQ_app diff --git a/docs/_sources/common/developer_manual/architecture/desktop/applications/modelingApps.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/applications/modelingApps.rst.txt index c63e5be7..ae83313d 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/applications/modelingApps.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/applications/modelingApps.rst.txt @@ -12,17 +12,6 @@ The input structural model information is parsed into a ``SAM.json`` file, locat :align: center :figclass: align-center - -The following options for modeling applications vary in the type of model and finite element program used for response simulation. - - -.. rendre:: cli-gallery - :data-file: $SIMCENTER_DEV/SimCenterBackendApplications/meta/backends.cache.json - :load-defaults: $SIMCENTER_DEV/SimCenterBackendApplications/meta/index.yaml#/$SIMDOC_APP - - :include-exclusive: %./categories:createSAM - - .. only:: HydroUQ_app .. raw:: html diff --git a/docs/_sources/common/developer_manual/architecture/desktop/applications/regionalMapApps.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/applications/regionalMapApps.rst.txt index d1ff2db3..ba573023 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/applications/regionalMapApps.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/applications/regionalMapApps.rst.txt @@ -9,19 +9,3 @@ For the set of candidate events, :ref:`event files ` must be p Once events are chosen, the application writes the name of the event file in its corresponding building file (:ref:`#-BIM.json `) in the **results** folder. -.. figure:: _static/images/backendapps_RegionalMapping.png - :align: center - :figclass: align-center - - -The following options for regional mapping applications vary in the algorithm or method used to make the event assignment. - - - -.. rendre:: cli-gallery - :data-file: $SIMCENTER_DEV/SimCenterBackendApplications/meta/backends.cache.json - :load-defaults: $SIMCENTER_DEV/SimCenterBackendApplications/meta/index.yaml#/$SIMDOC_APP - - :include-exclusive: %./categories:performRegionalMapping - - diff --git a/docs/_sources/common/developer_manual/architecture/desktop/applications/simulationApps.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/applications/simulationApps.rst.txt index c46462b5..d3a371ee 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/applications/simulationApps.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/applications/simulationApps.rst.txt @@ -3,25 +3,14 @@ Simulation Applications ======================= -The **simulation application** specifies parameters and executes the script for the response simulation. These parameters may include the integrator scheme, convergence tolerance, step size, etc. of the numerical analysis. +The **simulation application** specifies parameters and executes the script for the response simulation. These parameters may include the integrator scheme, convergence tolerance, step size, etc., of the numerical analysis. It takes as input the :ref:`BIM file `, the :ref:`EVENT file `, the :ref:`SAM file `, and the :ref:`EDP file `. -After response simulation is completed, the ``EDP.json`` file is populated with the resulting EDPs and saved in the **simulation working directory**. Note that the ``SIM.json`` file is not saved in the directory. - +After the response simulation is completed, the ``EDP.json`` file is populated with the resulting EDPs and saved in the **simulation working directory**. Note that the ``SIM.json`` file is not saved in the directory. .. figure:: _static/images/backendapps_Simulation.png :align: center :figclass: align-center - -The following options for simulation applications vary in the type of finite element program or procedure used for EDPs estimation. - - -.. rendre:: cli-gallery - :data-file: $SIMCENTER_DEV/SimCenterBackendApplications/meta/backends.cache.json - :load-defaults: $SIMCENTER_DEV/SimCenterBackendApplications/meta/index.yaml#/$SIMDOC_APP - - :include-exclusive: %./categories:performSIMULATION - .. only:: HydroUQ_app .. raw:: html diff --git a/docs/_sources/common/developer_manual/architecture/desktop/architecture.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/architecture.rst.txt index fd189bed..65f3b635 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/architecture.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/architecture.rst.txt @@ -12,27 +12,22 @@ :R2D:run-manually file-types - - -.. Within the natural hazards engineering community, there exist several widely used open-source applications, e.g., OpenFOAM, and online datasets, e.g., PEER NGA, that researchers are currently using. Consequently, and to avoid duplication, SimCenter applications incorporate many widely used applications, e.g., OpenFOAM. To do this, SimCenter develops pre- and post-processors for these existing applications and utilizes web technologies for accessing online services. +.. Within the natural hazards engineering community, there exist several widely used open-source applications, e.g., OpenFOAM, and online datasets, e.g., PEER NGA, that researchers are currently using. Consequently, to avoid duplication, SimCenter applications incorporate many widely used applications, such as OpenFOAM. To achieve this, SimCenter develops pre- and post-processors for these existing applications and utilizes web technologies for accessing online services. .. - #. DL: application to determine the damage and loss to the building/infrastructure given the event. - #. EDP: application to determine the response parameter given the event, building/lifeline, and damage and loss application. - #. BRAILS: a framework of applications for creating regional-level building inventories using machine learning. + #. DL: An application to determine the damage and loss to the building/infrastructure given the event. + #. EDP: An application to determine the response parameter given the event, building/lifeline, and damage and loss application. + #. BRAILS: A framework of applications for creating regional-level building inventories using machine learning. #. Databases containing information on building inventories for regional simulations, consequence functions for the DL applications, and experimental and corresponding simulation models for future machine learning-based AI algorithms. - .. .. note:: **Definitions** -.. #. **Workflow**: “The automation of a business process, in whole or part, during which documents, information or tasks are passed from one participant to another for action, according to a set of procedural rules.” [Workflow Management Coalition]. +.. #. **Workflow**: “The automation of a business process, in whole or part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules.” [Workflow Management Coalition]. -.. #. **Application**: A software application performs operations on data residing in a computer for a user or another program; it can be self-contained, typically termed a program or part of a group of programs. +.. #. **Application**: A software application that performs operations on data residing in a computer for a user or another program; it can be self-contained, typically termed a program or part of a group of programs. .. #. **Scientific Workflow**: A sequence of steps propagating input data through various applications to produce output. It is a loosely coupled application performing workflows in which each coordinated task is performed using an individual application. Each of the individual applications takes some data inputs and produces data outputs, which are then consumed by subsequent tasks according to the workflow definition. They are termed scientific because they are typically used by scientists to process, manage, and visualize ever-increasing amounts of data using "scientific" applications. .. #. **Scientific Workflow System**: One or more applications that aid a user in setting up, scheduling, running, and monitoring a user-defined scientific workflow. .. #. **Software Framework**: A collection of software for building applications in a specific domain. The framework defines the interfaces between the software components, provides example applications that can be developed using the provided software, and represents a clear set of interfaces. The software can be extended to build other applications. - - diff --git a/docs/_sources/common/developer_manual/architecture/desktop/backendApplications.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/backendApplications.rst.txt index 4199d2d0..cb989633 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/backendApplications.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/backendApplications.rst.txt @@ -1,21 +1,13 @@ .. _lblbackendApps: - -.. - .. _term1:: component applications - - ********************* Backend Applications ********************* - -The backend applications are categorized by function into the following workflow |term1| which creates and populate *intermediate files* used to propagate information from one component application to the next. The |term1| and their intermediate files are as follows: - +The backend applications are categorized by function into the following workflow :term:`modules` which create and populate *intermediate files* used to propagate information from one component application to the next. The :term:`modules` and their intermediate files are as follows: .. |term1| replace:: modules - .. |createBIM| replace:: :ref:`Building Applications ` - create the BIM files for every building asset, containing building properties. .. |performRegionalMap| replace:: :ref:`Regional Mapping Applications ` - map an intensity measure (IM) or time series for the hazard event to each building asset site. @@ -32,9 +24,8 @@ The backend applications are categorized by function into the following workflow .. |performDL| replace:: :ref:`Damage and Loss (DL) Applications ` - estimate expected damages and losses from the EDP application's output. - .. only:: quoFEM_app - + .. toctree:: :maxdepth: 1 @@ -145,6 +136,4 @@ The backend applications are categorized by function into the following workflow applications/UQApps applications/DLApps - -These applications make up the "backbone" of SimCenter workflow systems, with each one calling on a different subset of the component applications. - +These applications constitute the "backbone" of SimCenter workflow systems, with each one calling on a different subset of the component applications. diff --git a/docs/_sources/common/developer_manual/architecture/desktop/dynamicDiagrams.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/dynamicDiagrams.rst.txt index 28946a07..4f879c41 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/dynamicDiagrams.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/dynamicDiagrams.rst.txt @@ -4,5 +4,5 @@ Level 4 Dynamic Diagrams ======================== -To understand better the interactions between the components we will present some C4 dynamic diagrams. The dynamic diagram is similar to a UML communication diagram, which again is similar to a UML sequence diagram although it allows a free-form arrangement of diagram elements with numbered interactions to indicate ordering. +To better understand the interactions between the components, we will present some C4 dynamic diagrams. The dynamic diagram is similar to a UML communication diagram, which, again, is akin to a UML sequence diagram, albeit it allows for a free-form arrangement of diagram elements with numbered interactions to indicate ordering. diff --git a/docs/_sources/common/developer_manual/architecture/desktop/file-types.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/file-types.rst.txt index 87e41676..7ce78bce 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/file-types.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/file-types.rst.txt @@ -4,7 +4,7 @@ File Types and Schemas ********************** -In order to run an instance of the workflow, users must prepare the **input files** according to a standard file schema (the file type, structure, and contents). If input files deviate from this schema, then the workflow will return errors. Upon completion of the workflow, **output files** containing a summary of simulation results are produced. +In order to run an instance of the workflow, users must prepare the **input files** according to a standard file schema (the file type, structure, and contents). If input files deviate from this schema, the workflow will return errors. Upon completion of the workflow, **output files** containing a summary of simulation results are produced. For a guide on formatting input files and reading output files, refer to the following pages: @@ -13,3 +13,4 @@ For a guide on formatting input files and reading output files, refer to the fol file-types/Inputs file-types/Outputs + diff --git a/docs/_sources/common/developer_manual/architecture/desktop/file-types/Inputs.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/file-types/Inputs.rst.txt index 27e13c57..869f3dd6 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/file-types/Inputs.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/file-types/Inputs.rst.txt @@ -7,7 +7,6 @@ The following files must be provided by the user to execute the workflow. .. jsonschema:: File_Schema.json#/properties/Inputs/configurationFile - .. jsonschema:: File_Schema.json#/properties/Inputs/buildingSourceFile The header schema, followed by an example input, is provided. Definitions for the keywords are given in the `Custom Inventory sheet `_. @@ -21,7 +20,7 @@ The header schema, followed by an example input, is provided. Definitions for th .. jsonschema:: File_Schema.json#/properties/Inputs/transportationSourceFile1 -A JSON file containing highway transportation roadways, bridges, and tunnels for the response simulation and damage/loss estimation steps of the workflow. This file contains all the information necessary for constructing AIM files for each bridge, tunnel, and roadway. The JSON file must contain the "nodes" object and at lease one of the "hwy_bridges", "hwy_tunnels", and "roadways" object. Involved key-item pairs are: +A JSON file containing highway transportation roadways, bridges, and tunnels for the response simulation and damage/loss estimation steps of the workflow. This file contains all the information necessary for constructing AIM files for each bridge, tunnel, and roadway. The JSON file must contain the "nodes" object and at least one of the "hwy_bridges", "hwy_tunnels", and "roadways" objects. Involved key-item pairs are: * "hwy_bridges": A JSON array of JSON Objects, each containing the following key/item pairs @@ -30,7 +29,6 @@ A JSON file containing highway transportation roadways, bridges, and tunnels for :header-rows: 2 :align: center - * "hwy_tunnels": A JSON array of JSON Objects, each containing the following key/item pairs .. csv-table:: InputDataSchemaTunnel.csv @@ -38,7 +36,6 @@ A JSON file containing highway transportation roadways, bridges, and tunnels for :header-rows: 2 :align: center - * "roadways": A JSON array of JSON Objects, each containing the following key/item pairs .. csv-table:: InputDataSchemaRoadway.csv @@ -46,21 +43,15 @@ A JSON file containing highway transportation roadways, bridges, and tunnels for :header-rows: 2 :align: center - -* "nodes": A long JSON Objects containing the following key/item pairs +* "nodes": A large JSON Object containing the following key/item pairs .. csv-table:: InputDataSchemaTransportNode.csv :file: files/InputDataSchemaTransportNode.csv :header-rows: 1 :align: center - .. jsonschema:: File_Schema.json#/properties/Inputs/modelFile - .. jsonschema:: File_Schema.json#/properties/Inputs/EDPspecs - .. jsonschema:: File_Schema.json#/properties/Inputs/eventFiles - - diff --git a/docs/_sources/common/developer_manual/architecture/desktop/file-types/Outputs.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/file-types/Outputs.rst.txt index e75a2ffa..e1b09071 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/file-types/Outputs.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/file-types/Outputs.rst.txt @@ -1,10 +1,9 @@ .. _lblOutputs: Outputs -=================== - -After DL assessment is complete, the workflow collects the EDP.csv, DM.csv, and DV.csv files produced for each building asset and aggregates the results into single output files. When run locally, the workflow returns the output in a CSV format which is located in the *results* folder. When run remotely, the workflow returns the output in an HDF format which is located in the job archive. The HDF files may be converted into CSV format as a post-processing step. +======= +After the DL assessment is complete, the workflow collects the EDP.csv, DM.csv, and DV.csv files produced for each building asset and aggregates the results into single output files. When run locally, the workflow returns the output in CSV format, which is located in the *results* folder. When run remotely, the workflow returns the output in HDF format, which is located in the job archive. The HDF files can be converted into CSV format as a post-processing step. .. jsonschema:: File_Schema.json#/properties/Outputs/outputEDP diff --git a/docs/_sources/common/developer_manual/architecture/desktop/overview.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/overview.rst.txt index 5aa17f76..f4b92c93 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/overview.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/overview.rst.txt @@ -1,18 +1,16 @@ - .. _lblArchitecture: ===================== Software Architecture ===================== -The |app| is one of the SimCenter's computational applications, which are `scientific workflow systems `_ that executes a sequence of computational tasks specialized for natural hazard engineering (NHE) problems. In contrast to more general-purpose scientific workflow systems (such as `Taverna `_, `Kepler `_, and `Pegasus `_), SimCenter workflow systems include the following features: - - - Access to high-performance computing resources, available on the cloud through |DesignSafe|, to enable parallel workflows for non-trivial large-scale NHE problems; - - Uncertainty quantification capabilities using `Dakota `_, which allows users to introduce input uncertainties that are propagated through the workflow with random variables; - - Streamlined interfaces between existing software applications and datasets that are widely used by the NHE community, such as `OpenFOAM `_, |OpenSeesLink|, `ADCIRC `_, and `PEER Strong Ground Motion Databases `_. To do this, the SimCenter develops pre- and post-processors for these existing applications and utilizes web technologies for accessing online services; - - Additional custom software applications produced by the SimCenter. Among these are applications that automate the acquisition of building inventory data (`BRAILS `_), applications that simulate hazard events and generate corresponding input files for passing through the workflow system (RegionalEvent Applications), applications for damage and loss assessment (`pelicun `_), and more. - - Modular framework that allows developers to incorporate their own software applications as components to the workflow system, so long as it meets the input-output structure at component interfaces. +The |app| is one of SimCenter's computational applications, which are `scientific workflow systems `_ that execute a sequence of computational tasks specialized for natural hazard engineering (NHE) problems. In contrast to more general-purpose scientific workflow systems (such as `Taverna `_, `Kepler `_, and `Pegasus `_), SimCenter workflow systems include the following features: + - Access to high-performance computing resources, available on the cloud through |DesignSafe|, to enable parallel workflows for large-scale NHE problems; + - Uncertainty quantification capabilities using `Dakota `_, which allow users to introduce input uncertainties that are propagated through the workflow with random variables; + - Streamlined interfaces between existing software applications and datasets widely used by the NHE community, such as `OpenFOAM `_, |OpenSeesLink|, `ADCIRC `_, and `PEER Strong Ground Motion Databases `_. To do this, the SimCenter develops pre- and post-processors for these existing applications and utilizes web technologies for accessing online services; + - Additional custom software applications produced by the SimCenter. Among these are applications that automate the acquisition of building inventory data (`BRAILS `_), applications that simulate hazard events and generate corresponding input files for passing through the workflow system (RegionalEvent Applications), applications for damage and loss assessment (`pelicun `_), and more; + - A modular framework that allows developers to incorporate their own software applications as components to the workflow system, as long as they meet the input-output structure at component interfaces. .. _figFramework: @@ -23,9 +21,7 @@ The |app| is one of the SimCenter's computational applications, which are `scien SimCenter Software Framework - -A Level 1 diagram showing the system context for the SimCenter applications, i.e., how it fits in the world, -is shown in :numref:`architecture figContext`. It shows SimCenter applications (EE-UQ, WE-UQ, HydroUQ, PBE, R2D) as a box in the center surrounded by the user and the user's systems. The SimCenter applications allow a user to create and run scientific workflow applications; the data for the applications may be obtained from the web or DataDepot. The workflow applications are run on either the local desktop or on some HPC at |DesignSafe|. +A Level 1 diagram showing the system context for the SimCenter applications, i.e., how it fits in the world, is shown in :numref:`architecture figContext`. It shows SimCenter applications (EE-UQ, WE-UQ, HydroUQ, PBE, R2D) as a box in the center surrounded by the user and the user's systems. The SimCenter applications allow a user to create and run scientific workflow applications; the data for the applications may be obtained from the web or DataDepot. The workflow applications are run on either the local desktop or on an HPC at |DesignSafe|. .. _architecture figContext: @@ -36,9 +32,7 @@ is shown in :numref:`architecture figContext`. It shows SimCenter applications ( System context diagram for SimCenter applications. -Given how SimCenter applications fit in with the environment, a level 2 diagram demonstrates how the -SimCenter applications are broken into high-level components. The SimCenter applications are, as shown in -:numref:`architecture figContainer`, split into two components: A front-end UI and a back-end application that runs the workflow. The front-end applications are desktop applications written using the cross-platform `Qt framework `_. The back end is an application that processes the input from the front end, which comes in the form of a JSON file, creates a workflow, and runs it. The workflow applications, written in Python, C, or C++, utilize existing applications where possible and run on either the local desktop machine or on an HPC utilizing resources made available to the NHE community through DesignSafe. +Given how SimCenter applications fit in with the environment, a Level 2 diagram demonstrates how the SimCenter applications are broken into high-level components. The SimCenter applications are, as shown in :numref:`architecture figContainer`, split into two components: a front-end UI and a back-end application that runs the workflow. The front-end applications are desktop applications written using the cross-platform `Qt framework `_. The back end is an application that processes the input from the front end, which comes in the form of a JSON file, creates a workflow, and runs it. The workflow applications, written in Python, C, or C++, utilize existing applications where possible and run on either the local desktop machine or on an HPC using resources made available to the NHE community through DesignSafe. .. _architecture figContainer: @@ -49,8 +43,7 @@ SimCenter applications are broken into high-level components. The SimCenter appl System container diagram for SimCenter applications. -Two level 3 diagrams are now presented, which break up the two containers into the major building blocks or -components in C4 terminology. In :numref:`architecture figComponentFront`, the component diagram for the front-end UI is presented. It outlines the interaction between the user and the individual graphical elements (widgets) of the UI. Given the jigsaw puzzle analogy, the user selects which piece of the jigsaw puzzle they are working on in the component selection widget. The widget for the jigsaw piece will then be displayed on the desktop. The user for each jigsaw piece then selects which application to run for that piece. For the chosen application, they provide the inputs. When the inputs are all provided, the user can choose to run the simulations locally or remotely. For jobs that run remotely, the user can download and review previously run simulations. As seen, the widgets may subsequently interact with web services through HTTPS requests or with DesignSafe utilizing TAPIS Restful API through the RemoteService container. +Two Level 3 diagrams are now presented, which break up the two containers into the major building blocks or components in C4 terminology. In :numref:`architecture figComponentFront`, the component diagram for the front-end UI is presented. It outlines the interaction between the user and the individual graphical elements (widgets) of the UI. Given the jigsaw puzzle analogy, the user selects which piece of the jigsaw puzzle they are working on in the component selection widget. The widget for the jigsaw piece will then be displayed on the desktop. The user for each jigsaw piece then selects which application to run for that piece. For the chosen application, they provide the inputs. When the inputs are all provided, the user can choose to run the simulations locally or remotely. For jobs that run remotely, the user can download and review previously run simulations. As seen, the widgets may subsequently interact with web services through HTTPS requests or with DesignSafe utilizing TAPIS Restful API through the RemoteService container. .. _architecture figComponentFront: @@ -61,7 +54,7 @@ components in C4 terminology. In :numref:`architecture figComponentFront`, the c Component diagram for front-end UI. -The component diagram for the back-end application shown in :numref:`architecture figComponentBack`, shows that the back-end comprises several component applications. The application ``femUQ.py`` is the application that parses the input from the front end, sets up the workflow by creating a ``workflow_driver`` script and then launches the UQ engine. The choice of UQ Engine and applications to run in the workflow is determined from the data passed from the UI and information contained in a file, ``WorkflowApplication.json``. The ``WorkflowApplication.json`` file is a file that maps the applications specified in the output from the UI with a specific application contained on the users' local machine or at the remote HPC resource, as such it allows the researchers to modify the applications that may be run in the workflow w/o the need to recompile the application. Once the ``workflow_driver`` file is created, control is passed to a UQ engine, which repeatedly runs the ``workflow_driver`` to generate the results. In running the workflow, some of the applications will invoke applications not developed to meet the API. For such applications, pre- and post-processors are provided. The figure shows the back-end application running locally or remotely on an HPC at DesignSafe. +The component diagram for the back-end application shown in :numref:`architecture figComponentBack`, shows that the back-end comprises several component applications. The application ``femUQ.py`` is the application that parses the input from the front end, sets up the workflow by creating a ``workflow_driver`` script, and then launches the UQ engine. The choice of UQ engine and applications to run in the workflow is determined from the data passed from the UI and information contained in a file, ``WorkflowApplication.json``. The ``WorkflowApplication.json`` file is a file that maps the applications specified in the output from the UI with a specific application contained on the user's local machine or at the remote HPC resource. As such, it allows the researchers to modify the applications that may be run in the workflow without the need to recompile the application. Once the ``workflow_driver`` file is created, control is passed to a UQ engine, which repeatedly runs the ``workflow_driver`` to generate the results. In running the workflow, some of the applications will invoke applications not developed to meet the API. For such applications, pre- and post-processors are provided. The figure shows the back-end application running locally or remotely on an HPC at DesignSafe. .. _architecture figComponentBack: @@ -70,28 +63,28 @@ The component diagram for the back-end application shown in :numref:`architectur :width: 800 :figclass: align-center - Component diagram for Backend Application. + Component diagram for back-end application. .. note:: ``femUQ.py`` is the back-end application for the EE-UQ, WE-UQ, Hydro-UQ, and PBE applications. For R2D, the back-end application is ``R2D_Workflow.py``. The interaction between the front-end and the back-end is best understood by looking at the sequence of events when the user presses the ``Run`` button. As shown in the figure below, the UI application will first perform several steps: -1. It will create a temporary directory in the Documents folder named ``tmp.SimCenter``, and inside ``tmp.SimCenter`` will create another directory ``templatedir``. +1. It will create a temporary directory in the Documents folder named ``tmp.SimCenter``, and inside ``tmp.SimCenter`` it will create another directory ``templatedir``. 2. It will then run through all the currently selected widgets and invoke the ``copyFiles()`` method, telling these widgets to copy all files needed during the workflow to the ``templatedir`` directory. -3. It will then create a JSON file and will run through the currently selected widgets and on each invokes the methods ``outputToJSON()`` and ``outputAppDataToJSON``, these telling the application to augment the JSON file with the inputs the user has provided in the widget and also the name of the widget. +3. It will then create a JSON file and will run through the currently selected widgets and invoke the methods ``outputToJSON()`` and ``outputAppDataToJSON()``, telling the application to augment the JSON file with the inputs the user has provided in the widget and also the name of the widget. 4. The UI will start the back-end application and spin until the back-end application returns with a completion signal. -Now that the UI has been handed over to the back-end application, the back-end application will perform the following: +Now that the UI has handed over to the back-end application, the back-end application will perform the following steps: + +5. Open the output file from the UI and parse it to obtain the name of the application to run and the arguments to run the application with. Open another file, the ``WorkflowApplications.json`` file, contained within the application to determine, given the application name, the full path to the executable to be invoked. It will create in ``templatedir`` a file named ``workflow_driver``. When run by the UQ engine, this file is a script file that will generate a file named ``results.out``. ``results.out`` when the ``workflow_driver`` script has completed will contain a single line of space-separated values, one value for each EDP. -5. Open the output file from the UI and parse it to obtain the name of the application to run and the arguments to run the application with. Open up another file, the ``WorkflowApplications.json`` file, contained with the application to determine, given the application name, the full path to the executable to be invoked. It will create in ``templatedir`` a file named ``workflow_driver``. When run by the UQ engine, this file is a script file that will generate a file named ``results.out``. ``results.out`` when the ``workflow_driver`` script has completed will contain a single line of space-separated values, one value for each EDP. - -6. It will invoke each application with supplied arguments and an additional command-line argument, ``--getRV``, to inform the application to process the input file and create any additional random variables and input files needed before the workflow runs. +6. It will invoke each application with supplied arguments and an additional command-line argument, ``--getRV``, to inform the application to process the input file and create any additional random variables and input files needed before the workflow runs. -7. It will then launch the UQengine. The UQengine is typically a pre- and post-processor to an existing UQ engine. +7. It will then launch the UQ engine. The UQ engine is typically a pre- and post-processor to an existing UQ engine. 8. The pre-processor takes the JSON input file and creates an input file needed by the actual UQ engine. @@ -99,14 +92,13 @@ Now that the UI has been handed over to the back-end application, the back-end a 10. When done, the engine will output its results. -11. The UQengine will notify the UQpreprocessor that it is done. +11. The UQ engine will notify the UQ pre-processor that it is done. + +12. The UQ pre-processor will notify the femUQ application that it is done. -12. The UQpreprocessor will notify the femUQ application that it is done. - 13. The femUQ application will notify the UI that it is done. 14. The UI will read the results and present them to the user. - .. _architecture figSequenceLocal: @@ -115,15 +107,9 @@ Now that the UI has been handed over to the back-end application, the back-end a :width: 800 :figclass: align-center - Sequence diagram showing what happens when a Workflow runs Locally - - -That is for the case where the computations are performed on the local computer. When the computations are -performed remotely, the steps are different. The first 8 steps are the same. But now, the UQwrapper will not -start the UQ engine. Instead, control is returned to the UI. The UI will, as shown in the following: (11) -Compress the temporary folder. (12) Send the compressed folder to the remote HPC, shown in -:numref:`architecture figSequenceRemote`. (13) Start an application to perform the computations. All the remote data transfer and application invocation is down through a cloud service. The `TACC tapis `_ interface is used to provide SimCenter users with access to the TACC HPC resources through the DesignSafe portal. + Sequence diagram showing what happens when a workflow runs locally. +That is for the case where the computations are performed on the local computer. When the computations are performed remotely, the steps are different. The first eight steps are the same. But now, the UQ wrapper will not start the UQ engine. Instead, control is returned to the UI. The UI will, as shown in the following: (11) Compress the temporary folder, (12) Send the compressed folder to the remote HPC, shown in :numref:`architecture figSequenceRemote`, (13) Start an application to perform the computations. All the remote data transfer and application invocation is done through a cloud service. The `TACC Tapis `_ interface is used to provide SimCenter users with access to the TACC HPC resources through the DesignSafe portal. .. _architecture figSequenceRemote: @@ -132,7 +118,7 @@ Compress the temporary folder. (12) Send the compressed folder to the remote HPC :width: 800 :figclass: align-center - Sequence diagram showing what happens when a Workflow runs Remotely + Sequence diagram showing what happens when a workflow runs remotely. .. only:: R2D_app diff --git a/docs/_sources/common/developer_manual/architecture/desktop/run-manually/runLocal.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/run-manually/runLocal.rst.txt index 28961ef3..ab57edaf 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/run-manually/runLocal.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/run-manually/runLocal.rst.txt @@ -3,37 +3,47 @@ Run Locally on Your Desktop =========================== -Running applications locally on a personal desktop is convenient for running small-scale jobs and debugging. For larger jobs, the applications are available on DesignSafe for utilizing high-performance computing resources. +Running applications locally on a personal desktop is convenient for small-scale jobs and debugging. For larger jobs, the applications are available on DesignSafe to utilize high-performance computing resources. -1. Follow the directions in :ref:`How to Build ` to install the backend applications on your local desktop. Move the applications folder to a separate directory (such as ``C:/rWHALE/``). +1. Follow the directions in :ref:`How to Build ` to install the backend applications on your local desktop. The applications needed to run the backend are in the **applications** folder after you have built the backend. You can leave the folder where you have built it (which is useful if you plan to keep updating the backend applications as we make changes to the github repository, or you can move the applications folder to a seperate directory (such as ``C:/rWHALE/``) if you don't plan to update these applications. -2. Prepare the input files in a folder called ``input_data``, then zip the folder. You may use this example input file set (:download:`input_data_eq.zip `) as a template. +2. To run a workflow you first need to create a folder on your filesystem in which you will place the necessary inputs. In this folder you will need an input file that describes the workflow to run, say **input.json**, and a directory **input_data**. -3. Prepare workflow settings in the configuration file. You may use the example configuration file (:download:`rWHALE_config_eq.json `) as a template. +3. Create the input file, ``input.json`` that outlines the workflow to run. You may use the example configuration file (:download:`input.json `) as a template. There are 3 lines in this file that need changing to run the default workflow (Example1 in the R2DTool): + .. code:: - - Set ``'runDir'`` to the path containing the ``input_data`` folder. If the configuration file is in the same directory, set ``'remoteDir'='...'``. - - Set ``'localAppDir'`` to the path containing the applications folder (such as ``C:/rWHALE/``). - - Specify applications for each workflow step and their inputs. For more details on the format of the configuration file, see :ref:`Inputs `. + "remoteAppDir": "/Users/fmckenna/NHERI/SimCenterBackendApplications", + "localAppDir": "/Users/fmckenna/NHERI/SimCenterBackendApplications", + "runDir": "/Users/fmckenna/Documents/R2D/LocalWorkDir/tmp.SimCenter" + - Set ``'runDir'`` to the path containing the ``input_data`` folder. + - Set ``'localAppDir'`` and ``''remoteAppDir'`` to the path containing the applications folder (such as ``C:/rWHALE/``). + - If you wish to change thw workflow that is run, you need to specify applications for each workflow step and their inputs. For more details on the format of the configuration file, see :ref:`Inputs `. -3. The workflow is run through the command window by calling on Python and specifying paths to the application files, input files, and desired location for the results folder. The following is an example of the **initialization command**: + +4. In the ``input_data`` folder, you need to place the files needed by the applications which will run in the workflow. You may use this example input file set (:download:`input_data.zip `) as a template. Again, the downloaded default is for Example1 in R2D. -.. code-block:: - python --registry --referenceDir -w +5. Now you are ready to run the Workflow. The workflow is run through the command window by calling on Python and specifying paths to the application files, input files, and desired location for the results folder. The following is the command to issue on the command line: + +.. code-block:: + python --registry --referenceDir -w where: - - **** is the full path to the file "R2D_workflow.py" in the applications folder - - **** is the full path to the provided file ``rWHALE_config.json`` - - **** is the full path to the file ``WorkflowApplications.json`` in the applications folder + - **** is the full path to the file "rWhale.py" in the **/applications/Workflow** folder + - **** is the full path to the workflow input file, ``input.json`` + - **** is the full path to the file ``WorkflowApplications.json`` in the **applications/Workflow** folder - **** is the full path to the folder with all input files - **** is the full path to where a "results" folder will be created to contain the output files +.. note:: -4. A results folder is produced, which contains both the aggregated output files (EDP_{min id}_{max id}.csv, DM_{min id}_{max id}.csv, DV_{min id}_{max id}.csv), as well as the individual output files (EDP.csv, DM.csv, DV.csv) for each built asset in their respective folders. + If you are on a Mac, python in the above needs to be replaced by **python3**. + +6. A results folder is produced, which contains both the aggregated output files (EDP_{min id}_{max id}.csv, DM_{min id}_{max id}.csv, DV_{min id}_{max id}.csv), as well as the individual output files (EDP.csv, DM.csv, DV.csv) for each built asset in their respective folders. :: diff --git a/docs/_sources/common/developer_manual/architecture/desktop/run-manually/runRemote.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/run-manually/runRemote.rst.txt index d9ddc5dc..d64e58a5 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/run-manually/runRemote.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/run-manually/runRemote.rst.txt @@ -4,172 +4,145 @@ Run Remotely on DesignSafe ************************** -There are two ways to run the applications remotely on DesignSafe: one is through the `Data Depot `_ user interface on DesignSafe, where job details are submitted through a Jupyter notebook. The other is by calling on Tapis CLI directly through Ubuntu. - - Prepare Input Files -========================== - -1. Prepare the input files in a folder called ``input_data``, then zip the folder. You may use this example input file set (:download:`input_data_eq.zip `) as a template. +=================== +1. Prepare the input files in a folder named ``input_data``, then zip the folder. You may use this example input file set (:download:`input_data_eq.zip `) as a template. 2. Prepare workflow settings in the configuration file. You may use the example configuration file (:download:`rWHALE_config_remote.json `) as a template. - - - Set ``'runDir'`` to ``/tmp/rWhale/``. - - Set ``'localAppDir'`` to ``/tmp/rWhale/``. - - Specify applications for each workflow step and their inputs. For more details on the format of the configuration file, see :ref:`Inputs `. - + - Set ``'runDir'`` to ``/tmp/rWhale/``. + - Set ``'localAppDir'`` to ``/tmp/rWhale/``. + - Specify applications for each workflow step and their inputs. For more details on the format of the configuration file, see :ref:`Inputs `. 3. Upload the zipped ``input_data`` file and configuration file to "My Data" on the DesignSafe `Data Depot `_. - 4. Upload the :download:`CreateLauncherTasks script ` and a Jupyter notebook with commands for setting up the job on Tapis. You can use this example Jupyter Notebook (:download:`run_rWHALE.ipynb `) as a template. -On DesignSafe, the files should appear on Data Depot as: - +On DesignSafe, the files should appear in the Data Depot as: .. figure:: figures/DS_data_depot.png :align: center :figclass: align-center - - Run Job Through Jupyter -========================== +======================= -This method uses Jupyter Notebook to run the job, accessing Tapis CLI in the backend. - - -5. Click on the ``run_rWHALE.ipynb`` notebook, then click **Open in Jupyter**. You will be taken to a new page for editing the Jupyter Notebook. +This method uses a Jupyter Notebook to run the job, accessing the Tapis CLI in the background. +5. Click on the ``run_rWHALE.ipynb`` notebook, then click **Open in Jupyter**. You will be redirected to a new page for editing the Jupyter Notebook. .. figure:: figures/DS_jupyter.png :align: center :figclass: align-center - -6. Specify settings for running the job on Frontera. Submit the job by running all cells in the Jupyter Notebook (Cell > Run All). +6. Specify settings for running the job on Frontera. Submit the job by executing all cells in the Jupyter Notebook (Cell > Run All). .. .. jsonschema:: App_Schema.json#/properties/runRemote - -7. To view the status of the job, navigate to the **Workspace** on DesignSafe. The right bar will list all jobs that have been submitted in order of newest to oldest. Job outputs can be accessed by clicking on "More Info" on the job. - +7. To view the status of the job, navigate to the **Workspace** on DesignSafe. The sidebar will list all jobs that have been submitted, from newest to oldest. Job outputs can be accessed by clicking on "More Info" for the job. .. figure:: figures/DS_workspace.png :align: center :figclass: align-center +8. To access the job outputs, click on "More Info" for the job. You will be directed to the job archive folder in the Data Depot. -8. To access the job outputs, click on "More Info" on the job. It will navigate you to the job archive folder on Data Depot. - - - The aggregated outputs are saved in HDF files: "DM.hdf", "DV.hdf", and "EDP.hdf" contain the EDP and DL summary results for all built assets. "realizations.hd5" contains the response simulation results for every event simulated per built asset. - - "launcher.err" contains error messages produced from running the job. - - "launcher.out" contains the log file. - + - The aggregated outputs are saved in HDF files: "DM.hdf", "DV.hdf", and "EDP.hdf" contain the EDP and DL summary results for all built assets. "realizations.hd5" contains the response simulation results for each event simulated per built asset. + - "launcher.err" contains error messages produced during the job run. + - "launcher.out" contains the log file. .. figure:: figures/DS_results.png :align: center :figclass: align-center - - Submit Job Through Tapis -========================== +======================== -This method submits the job using Tapis CLI directly. If using Windows, this is executed in the Ubuntu subsystem. Please refer to Chapter 9 of the `Tapis How-To Guide `_ for more details. +This method involves submitting the job using the Tapis CLI directly. If using Windows, execute this in the Ubuntu subsystem. Please refer to Chapter 9 of the `Tapis How-To Guide `_ for more details. -5. First, ensure that Tapis CLI is installed on your computer. Open a Ubuntu window and install Tapis CLI using ``pip``: +5. First, ensure that the Tapis CLI is installed on your computer. Open an Ubuntu window and install the Tapis CLI using ``pip``: - ``pip install tapis-cli`` + ``pip install tapis-cli`` - -Or, install Tapis CLI from Github: +Or, install the Tapis CLI from GitHub: .. code-block:: console - git clone https://github.com/TACC-Cloud/tapis-cli-ng.git - cd tapis-cli-ng/ - pip install --upgrade --user . - - -6. Set up a Tapis session on each host where you will use the Tapis CLI. This is a one-time operation where you will be asked to agree to terms, select a tenant, and finally enter a username and password for that tenant. Run the command: + git clone https://github.com/TACC-Cloud/tapis-cli-ng.git + cd tapis-cli-ng/ + pip install --upgrade --user . - ``tapis auth init`` +6. Set up a Tapis session on each host where you will use the Tapis CLI. This is a one-time setup where you will be asked to agree to terms, select a tenant, and finally enter a username and password for that tenant. Execute the command: + ``tapis auth init`` -You will see an output in the Ubuntu window similar to the following. +You will see an output in the Ubuntu window similar to the following: - - Select "y" to the prompts. - - Set ``tenant_name`` to "designsafe". - - Set ``username`` and ``password`` to your TACC username and password. - - Keep ``registry_url`` to ``https://index.docker.io`` - - Set ``git_username`` and ``git_token`` to your Github account details. See directions `here `_ for more information on generating a git token. + - Select "y" to the prompts. + - Set ``tenant_name`` to "designsafe". + - Set ``username`` and ``password`` to your TACC username and password. + - Keep ``registry_url`` as ``https://index.docker.io`` + - Set ``git_username`` and ``git_token`` to your GitHub account details. See directions `here `_ for more information on generating a git token. .. code-block:: - Use of Tapis requires acceptance of the TACC Acceptable Use Policy - which can be found at https://portal.tacc.utexas.edu/tacc-usage-policy - Do you agree to abide by this AUP? (type 'y' or 'n' then Return) y - Use of Tapis requires acceptance of the Tapis Project Code of Conduct - which can be found at https://tapis-project.org/code-conduct - Do you agree to abide by this CoC? (type 'y' or 'n' then Return) y - To improve our ability to support Tapis and the Tapis CLI, we would like to - collect your IP address, operating system and Python version. No personally identifiable information will be collected. This data will only be shared in - aggregate form with funders and Tapis platform stakeholders. - Do you consent to this reporting? [Y/n]: Y - - +---------------+--------------------------------------+----------------------------------------+ - | Name | Description | URL | - +---------------+--------------------------------------+----------------------------------------+ - | 3dem | 3dem Tenant | https://api.3dem.org/ | - | agave.prod | Agave Public Tenant | https://public.agaveapi.co/ | - | araport.org | Araport | https://api.araport.org/ | - | bridge | Bridge | https://api.bridge.tacc.cloud/ | - | designsafe | DesignSafe | https://agave.designsafe-ci.org/ | - | iplantc.org | CyVerse Science APIs | https://agave.iplantc.org/ | - | irec | iReceptor | https://irec.tenants.prod.tacc.cloud/ | - | portals | Portals Tenant | https://portals-api.tacc.utexas.edu/ | - | sd2e | SD2E Tenant | https://api.sd2e.org/ | - | sgci | Science Gateways Community Institute | https://sgci.tacc.cloud/ | - | tacc.prod | TACC | https://api.tacc.utexas.edu/ | - | vdjserver.org | VDJ Server | https://vdj-agave-api.tacc.utexas.edu/ | - +---------------+--------------------------------------+----------------------------------------+ - - Enter a tenant name [tacc.prod]: - tacc.prod username: taccuser - tacc.prod password for taccuser: - - + Use of Tapis requires acceptance of the TACC Acceptable Use Policy + which can be found at https://portal.tacc.utexas.edu/tacc-usage-policy + Do you agree to abide by this AUP? (type 'y' or 'n' then Return) y + Use of Tapis requires acceptance of the Tapis Project Code of Conduct + which can be found at https://tapis-project.org/code-conduct + Do you agree to abide by this CoC? (type 'y' or 'n' then Return) y + To improve our ability to support Tapis and the Tapis CLI, we would like to + collect your IP address, operating system, and Python version. No personally identifiable information will be collected. This data will only be shared in + aggregate form with funders and Tapis platform stakeholders. + Do you consent to this reporting? [Y/n]: Y + + +---------------+--------------------------------------+----------------------------------------+ + | Name | Description | URL | + +---------------+--------------------------------------+----------------------------------------+ + | 3dem | 3dem Tenant | https://api.3dem.org/ | + | agave.prod | Agave Public Tenant | https://public.agaveapi.co/ | + | araport.org | Araport | https://api.araport.org/ | + | bridge | Bridge | https://api.bridge.tacc.cloud/ | + | designsafe | DesignSafe | https://agave.designsafe-ci.org/ | + | iplantc.org | CyVerse Science APIs | https://agave.iplantc.org/ | + | irec | iReceptor | https://irec.tenants.prod.tacc.cloud/ | + | portals | Portals Tenant | https://portals-api.tacc.utexas.edu/ | + | sd2e | SD2E Tenant | https://api.sd2e.org/ | + | sgci | Science Gateways Community Institute | https://sgci.tacc.cloud/ | + | tacc.prod | TACC | https://api.tacc.utexas.edu/ | + | vdjserver.org | VDJ Server | https://vdj-agave-api.tacc.utexas.edu/ | + +---------------+--------------------------------------+----------------------------------------+ + + Enter a tenant name [tacc.prod]: + tacc.prod username: taccuser + tacc.prod password for taccuser: 7. Initialize a job with the name "R2D_test_run" by executing the command: - ``tapis jobs init rWhale-2.1.0 --name R2D_test_run > job.json`` - -8. A job.json file is created. You may make changes to this file using VIM Editor, by running the command: + ``tapis jobs init rWhale-2.1.0 --name R2D_test_run > job.json`` - ``vim job.json`` +8. A job.json file is created. You may make changes to this file using the VIM Editor, by executing the command: -9. Edit the job.json file to specify settings for running the job on Frontera. To make edits in the VIM Editor, type ``Ctrl+I``. To exit out of the editor, type ``:wq``. + ``vim job.json`` +9. Edit the job.json file to specify settings for running the job on Frontera. To make edits in the VIM Editor, press ``i``. To exit out of the editor, type ``:wq``. -10. Once the job.json file is prepared, submit the job by running the command: +10. Once the job.json file is prepared, submit the job by executing the command: - ``tapis jobs submit -F job.json`` + ``tapis jobs submit -F job.json`` -An ACCEPTED status indicates the job.json was valid, and e-mail alerts (if they were specified in job.json) will track -the progress of the job. Also, take note of the long hexadecimal ID (*job ID*) when you submit the job. This identifier can be -used to track progress and download results. +An ACCEPTED status indicates that the job.json was valid, and e-mail alerts (if they were specified in job.json) will track the progress of the job. Also, take note of the long hexadecimal ID (*job ID*) when you submit the job. This identifier can be used to track progress and download results. -11. To check on the status of a particular job, run the following command with the job ID: +11. To check the status of a specific job, execute the command below, replacing `` with the ID of the job: ``tapis jobs status `` -12. Once the job has been completed, the results can be downloaded either from the job archives (accessed from the Workspace on DesignSafe) or directly from Tapis, with the following command: +12. After the job is completed, you can download the results. They are available either in the job archives (which can be accessed from the Workspace on DesignSafe) or directly from Tapis. Use the following command to download: - ``tapis jobs outputs download --progress `` + ``tapis jobs outputs download --progress `` -Or, to download a specific file from the outputs, +To download a specific file from the outputs, use: - ``tapis jobs outputs download `` + ``tapis jobs outputs download `` diff --git a/docs/_sources/common/developer_manual/architecture/desktop/run-manually/troubleshooting.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/run-manually/troubleshooting.rst.txt index 70e32cde..d0ff5865 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/run-manually/troubleshooting.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/run-manually/troubleshooting.rst.txt @@ -1,20 +1,18 @@ .. _lbltroubleshooting: Troubleshooting Errors -=========================== - -If the workflow does not run successfully, the first and best method for troubleshooting is by reading error messages output in the **log file**. For an example log file, refer to page :ref:`Backend Applications `. +====================== +If the workflow does not run successfully, the first and best method for troubleshooting is to read the error messages output in the **log file**. For an example of a log file, refer to the page :ref:`Backend Applications `. For troubleshooting with the log file, the following steps are recommended: - - **Identify which application failed in the workflow**. Read through the log file until an ERROR message appears after one of the Python commands. - - **Verify that the paths to all workflow files are correct.** These paths are specified in the :ref:`initialization command ` when run locally, or in the :ref:`job script ` when run remotely. - - **Check that the "ApplicationData" for each application in the configuration file is correct.** The workflow will fail if an application does not have all of its required application-specific inputs, or if inputs are provided with an incorrect data type. See the individual pages for the :ref:`Backend Applications ` for more details on application-specific inputs. - - **Check that there are no JSON serialization errors in the configuration file.** Mistakes in unclosed brackets or incorrect indentation in the JSON file will cause errors. - - **Check that the user-defined input files are in the correct format.** Mistakes in the header labels or formatting of CSV and JSON input files will cause errors. - - **To view print messages in the model script during response simulation, rerun Dakota.** By default, any print messages in input files are suppressed in the log file. In order to view the messages and debug issues with the model script, navigate to the results folder for one of the building assets in the command window (i.e. "results/1"). You should find three files: dakota.in, dakota.err, and dakota.out. Running the following command will re-execute the UQ application for that particular building asset: + - **Identify the application that failed in the workflow**. Read through the log file until an ERROR message appears after one of the Python commands. + - **Verify that the paths to all workflow files are correct**. These paths are specified in the :ref:`initialization command ` when run locally, or in the :ref:`job script ` when run remotely. + - **Check that the "ApplicationData" for each application in the configuration file is correct**. The workflow will fail if an application does not have all of its required application-specific inputs, or if inputs are provided with an incorrect data type. See the individual pages for the :ref:`Backend Applications ` for more details on application-specific inputs. + - **Check for any JSON serialization errors in the configuration file**. Mistakes in unclosed brackets or incorrect indentation in the JSON file will cause errors. + - **Check that the user-defined input files are in the correct format**. Mistakes in the header labels or formatting of CSV and JSON input files will cause errors. + - **To view print messages in the model script during response simulation, rerun Dakota**. By default, any print messages in input files are suppressed in the log file. To view the messages and debug issues with the model script, navigate to the results folder for one of the building assets in the command window (i.e., "results/1"). You should find three files: dakota.in, dakota.err, and dakota.out. Running the following command will re-execute the UQ application for that particular building asset: ``dakota -input dakota.in -output dakota.out -error dakota.err`` - -If problems still persist, you are encouraged to read previously posted questions or post your own at `SimCenter Forum `_. A member of the SimCenter developer team will respond to your question on the platform. +If problems still persist, you are encouraged to read previously posted questions or post your own at the |messageBoard|. A member of the SimCenter developer team will respond to your question on the platform. diff --git a/docs/_sources/common/developer_manual/architecture/desktop/workflows/readingTheLog.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/workflows/readingTheLog.rst.txt index ae1cc00f..c471b0f0 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/workflows/readingTheLog.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/workflows/readingTheLog.rst.txt @@ -4,67 +4,67 @@ Reading the Log File ******************** -The sequence of tasks carried out by the backend applications is outlined in the **log file** produced by the workflow. For :ref:`local runs `, this log is displayed in the command terminal and is reproduced in a file named ``log.txt`` in the ``results/`` directory. For :ref:`remote runs ` through Tapis, this log file is called ``launcher.out`` in the job archive folder on DesignSafe. This guide will explain how to understand the statements printed in the log file. +The sequence of tasks carried out by the backend applications is outlined in the **log file** produced by the workflow. For :ref:`local runs `, this log is displayed in the command terminal and is reproduced in a file named ``log.txt`` in the ``results/`` directory. For :ref:`remote runs ` through Tapis, this log file is named ``launcher.out`` and is located in the job archive folder on DesignSafe. This guide will explain how to understand the statements printed in the log file. The following is an example log file for a successful workflow run. The workflow can be broken down into the following sections: -I. **Read the configuration file:** +I. **Reading the configuration file:** - - **lines 12-13**: Identifies the path to the :ref:`configuration file `, which specifies the job details, and the *application registry file*, which specifies all available applications. + - **lines 12-13**: Identifies the path to the :ref:`configuration file `, which specifies the job details, and the *application registry file*, which lists all available applications. - - **line 16-62**: Reads the application registry file and displays all available applications. + - **lines 16-62**: Reads the application registry file and displays all available applications. - - **line 64-85**: Reads the configuration file and displays the units, local application directory, remote application directory, reference directory, and the applications chosen for each workflow step. Any workflow steps that are skipped (excluded from the configuration file) are also listed here. + - **lines 64-85**: Reads the configuration file and displays the units, local application directory, remote application directory, reference directory, and the applications chosen for each workflow step. Any workflow steps that are skipped (excluded from the configuration file) are also listed here. -II. **Pre-process building and event data:** +II. **Pre-processing building and event data:** - - **line 93**: Python command for executing the :ref:`Building ` application, creating the BIM files for each building asset. + - **line 93**: Python command for executing the :ref:`Building ` application, which creates the BIM files for each building asset. :: python "C:/rWHALE/applications/createBIM/CSV_to_BIM/CSV_to_BIM.py" "--buildingFile" "C:/rWHALE/earthquake_example/results/buildings1-2.json" "--Min" "1" "--Max" "2" "--buildingSourceFile" "C:/rWHALE/earthquake_example/input_data/input_params.csv" "--getRV" - - **line 103**: Python command for executing the :ref:`RegionalMapping ` application, assigning events to each of the building assets. + - **line 103**: Python command for executing the :ref:`RegionalMapping ` application, which assigns events to each of the building assets. :: python "C:/rWHALE/applications/performRegionalMapping/NearestNeighborEvents/NNE.py" "--buildingFile" "C:/rWHALE/earthquake_example/results/buildings1-2.json" "--filenameEVENTgrid" "C:/rWHALE/earthquake_example/input_data/records/EventGrid.csv" "--samples" "2" "--neighbors" "1" -III. **Set up and run simulations for each building asset:** +III. **Setting up and running simulations for each building asset:** - **line 111**: Starts with the first building asset. In this first pass, the EVENT, SAM, EDP, SIM files corresponding to "1-BIM.json" are created. - - **line 118**: Python command for executing the :ref:`Event ` application, creating the EVENT file for the building asset. + - **line 118**: Python command for executing the :ref:`Event ` application, which creates the EVENT file for the building asset. :: python "C:/rWHALE/applications/createEVENT/SimCenterEvent/SimCenterEvent.py" "--filenameBIM" "1-BIM.json" "--filenameEVENT" "EVENT.json" "--pathEventData" "C:/rWHALE/earthquake_example/input_data/records/" "--getRV" - - **line 126**: Python command for executing the :ref:`Modeling ` application, creating the SAM file for the built asset. + - **line 126**: Python command for executing the :ref:`Modeling ` application, which creates the SAM file for the building asset. :: python "C:/rWHALE/applications/createSAM/openSeesPyInput/OpenSeesPyInput.py" "--filenameBIM" "1-BIM.json" "--filenameEVENT" "EVENT.json" "--filenameSAM" "SAM.json" "--mainScript" "cantilever.py" "--modelPath" "C:/rWHALE/earthquake_example/input_data/model/" "--ndm" "3" "--dofMap" "1,2,3" "--getRV" - - **line 134**: Python command for executing the :ref:`EDP ` application, creating the EDP file for the building asset. + - **line 134**: Python command for executing the :ref:`EDP ` application, which creates the EDP file for the building asset. :: python "C:/rWHALE/applications/createEDP/userEDP_R/UserDefinedEDP.py" "--filenameBIM" "1-BIM.json" "--filenameEVENT" "EVENT.json" "--filenameSAM" "SAM.json" "--filenameEDP" "EDP.json" "--EDPspecs" "C:/rWHALE/earthquake_example/input_data/EDP_specs.json" "--getRV" - - **line 142**: Python command for executing the :ref:`Simulation ` application, creating the SIM file for the building asset. + - **line 142**: Python command for executing the :ref:`Simulation ` application, which creates the SIM file for the building asset. :: python "C:/rWHALE/applications/performSIMULATION/openSeesPy/OpenSeesPySimulation.py" "--filenameBIM" "1-BIM.json" "--filenameSAM" "SAM.json" "--filenameEVENT" "EVENT.json" "--filenameEDP" "EDP.json" "--filenameSIM" "SIM.json" "--getRV" - - **lines 153-157**: Commands which are written to the *workflow driver file*. In a "second pass" through the workflow, these commands are executed by running the workflow driver file. + - **lines 153-157**: Commands that are written to the *workflow driver file*. In a "second pass" through the workflow, these commands are executed by running the workflow driver file. :: @@ -96,7 +96,7 @@ III. **Set up and run simulations for each building asset:** python "C:/rWHALE/applications/performDL/pelicun/DL_calculation.py" "--filenameDL" "1-BIM.json" "--filenameEDP" "response.csv" "--outputEDP" "EDP.csv" "--outputDM" "DM.csv" "--outputDV" "DV.csv" "--DL_Method" "HAZUS MH EQ" "--Realizations" "2" "--detailed_results" "False" "--log_file" "True" "--coupled_EDP" "True" "--event_time" "off" "--ground_failure" "False" - - **line 213**: Continues to the second building asset ("2-BIM.json") and repeats the same workflow steps. + - **line 213**: Continues with the second building asset ("2-BIM.json") and repeats the same workflow steps. IV. **Aggregate outputs for all building assets:** diff --git a/docs/_sources/common/developer_manual/architecture/desktop/workflows/workflowStructure.rst.txt b/docs/_sources/common/developer_manual/architecture/desktop/workflows/workflowStructure.rst.txt index 56227455..fc71de69 100644 --- a/docs/_sources/common/developer_manual/architecture/desktop/workflows/workflowStructure.rst.txt +++ b/docs/_sources/common/developer_manual/architecture/desktop/workflows/workflowStructure.rst.txt @@ -5,7 +5,8 @@ Workflow Structure The backend applications for the |app| follow a standard workflow: -I. **Read the configuration file.** At the start of the workflow, the workflow settings specified in the configuration file are parsed (:ref:`Inputs `). *Note that if a particular component application is excluded from the configuration file, then it is automatically skipped in the workflow.* + +I. **Read the configuration file.** At the start of the workflow, the settings specified in the configuration file are parsed (:ref:`Inputs `). *Note that if a particular component application is not included in the configuration file, it is automatically skipped in the workflow.* II. **Pre-process building and event data.** The workflow completes a one-time step of setting up BIM files (:ref:`Building ` Application) for each building asset and assigning events to each building site (:ref:`RegionalMapping ` Application). diff --git a/docs/_sources/common/developer_manual/examples/desktop/eqAssessment.rst.txt b/docs/_sources/common/developer_manual/examples/desktop/eqAssessment.rst.txt index b41b2b31..cb34f4ff 100644 --- a/docs/_sources/common/developer_manual/examples/desktop/eqAssessment.rst.txt +++ b/docs/_sources/common/developer_manual/examples/desktop/eqAssessment.rst.txt @@ -4,7 +4,7 @@ Earthquake Assessment ********************* -This example is a small-scale regional earthquake risk assessment which performs response simulation and damage/loss estimation for a group of 20 buildings. The buildings are modeled as elastic-perfectly plastic single-degree-of-freedom (SDOF) systems defined by three input model parameters: the weight ``W``, yield strength ``f_yield``, and fundamental period ``T1``. The buildings are distributed in space in a 4x5 grid, within a 3x3 grid of event sites. At each event site, 5 ground motion records of similar intensity are assigned. +This example is a small-scale regional earthquake risk assessment that performs response simulation and damage/loss estimation for a group of 20 buildings. The buildings are modeled as elastic-perfectly plastic single-degree-of-freedom (SDOF) systems defined by three input model parameters: the weight ``W``, yield strength ``f_yield``, and fundamental period ``T1``. The buildings are distributed in space in a 4x5 grid, within a 3x3 grid of event sites. At each event site, 5 ground motion records of similar intensity are assigned. .. figure:: figures/regionalearthquakeexample.png @@ -17,8 +17,7 @@ Inputs The example input files can be downloaded here: :download:`example_eq.zip `. For more information about required input files, refer to :ref:`Inputs `. - -1. **Configuration file**: The configuration file specifies all simulation settings, including the application types, input file names, units, and type of outputs. +1. **Configuration file**: The configuration file specifies all simulation settings, including the application types, input file names, units, and types of outputs. .. literalinclude:: files/rWHALE_config_eq.json :language: python @@ -35,12 +34,11 @@ The example input files can be downloaded here: :download:`example_eq.zip ` regional mapping application. From the parameters set in the configuration file, the algorithm is set to randomly select 5 samples of ground motion records from the 4 nearest neighbors for each building asset. - .. figure:: figures/regionalearthquakeexample_annot.png :align: center :figclass: align-center -4. **Event Application**: This example uses the :ref:`SimCenterEvents ` event application. It takes as input the EventGrid.csv, event files with the ground motion intensity measures, and the site files which specify the five ground motions assigned to each event site. +4. **Event Application**: This example uses the :ref:`SimCenterEvents ` event application. It takes as input the EventGrid.csv, event files with the ground motion intensity measures, and the site files that specify the five ground motions assigned to each event site. **Event grid file:** @@ -56,7 +54,6 @@ The example input files can be downloaded here: :download:`example_eq.zip ` modeling application. The buildings are modeled as elastic-perfectly plastic single-degree-of-freedom (SDOF) systems defined by three input model parameters: the weight ``W``, yield strength ``f_yield``, and fundamental period ``T1``. Functions are included which record the peak response as EDPs for each of the EDP types specified in the EDP_specs.json file. **Model file:** @@ -75,15 +72,10 @@ The example input files can be downloaded here: :download:`example_eq.zip ` simulation application, which corresponds to the **OpenSeesPyInput** modeling application. It reads the ``build_model`` and ``run_analysis`` functions from the model file to perform the response simulation. - - 8. **UQ Application**: This example uses the :ref:`Dakota-UQ ` UQ application to run the response simulation. In the configuration file, the number of samples specified for the UQ application should match the number of ground motion samples per building asset specified for the RegionalMapping application. - - 9. **DL Application**: This example uses the :ref:`pelicun ` DL application. From the :ref:`building source file `, since the DL method selected is "HAZUS MH EQ", damage/loss estimation is performed using the HAZUS loss assessment method based on earthquake EDPs produced from the response simulation. - Run Workflow ============ @@ -93,9 +85,7 @@ The workflow can be executed by uploading the appropriate files to :ref:`DesignS python "C:/rWHALE/applications/Workflow/R2D_workflow.py" "C:/rWHALE/cantilever_example/rWHALE_config_eq.json" --registry "C:/rWHALE/applications/Workflow/WorkflowApplications.json" --referenceDir "C:/rWHALE/cantilever_example/input_data/" -w "C:/rWHALE/cantilever_example/results" - - -This command locates the backend applications in the folder "applications", and the input files in a directory "cantilever_example". Please ensure that the paths in the command appropriately identify the locations of the files in your directory. +This command locates the backend applications in the folder "applications" and the input files in a directory "cantilever_example". Please ensure that the paths in the command appropriately identify the locations of the files in your directory. :: @@ -121,10 +111,8 @@ This command locates the backend applications in the folder "applications", and ├── EDPspecs.json # EDP specifications file └── input_params.csv # building source file - - Outputs -========== +======= The example output files can be downloaded here: :download:`output_data_eq.zip `. For more information about the output files produced, refer to :ref:`Outputs `. @@ -135,7 +123,6 @@ The example output files can be downloaded here: :download:`output_data_eq.zip < :header-rows: 1 :align: center - 2. **DM_1-19.csv**: reports collapse probability and damage state probability for each building asset. .. csv-table:: DM_1-19.csv @@ -143,8 +130,7 @@ The example output files can be downloaded here: :download:`output_data_eq.zip < :header-rows: 1 :align: center - -2. **DV_1-19.csv**: reports decision variable estimates (repair cost, repair time, injuries) for each building asset. +3. **DV_1-19.csv**: reports decision variable estimates (repair cost, repair time, injuries) for each building asset. .. csv-table:: DV_1-19.csv :file: files/DV_1-19.csv diff --git a/docs/_sources/common/developer_manual/examples/desktop/examples.rst.txt b/docs/_sources/common/developer_manual/examples/desktop/examples.rst.txt index 496e6c52..787aadc6 100644 --- a/docs/_sources/common/developer_manual/examples/desktop/examples.rst.txt +++ b/docs/_sources/common/developer_manual/examples/desktop/examples.rst.txt @@ -6,7 +6,6 @@ Examples The following examples demonstrate how to use the backend applications for regional risk assessment. - .. toctree:: :maxdepth: 1 diff --git a/docs/_sources/common/developer_manual/examples/desktop/hurricaneAssessment.rst.txt b/docs/_sources/common/developer_manual/examples/desktop/hurricaneAssessment.rst.txt index 75fd6c6f..6bdda3b4 100644 --- a/docs/_sources/common/developer_manual/examples/desktop/hurricaneAssessment.rst.txt +++ b/docs/_sources/common/developer_manual/examples/desktop/hurricaneAssessment.rst.txt @@ -1,27 +1,23 @@ .. _lblhurricaneAssessment_2: - ********************* Hurricane Assessment ********************* -This example is a small-scale regional hurricane risk assessment which performs damage/loss estimation for a group of 20 wood buildings in Atlantic City under the Sandy Storm. The buildings are subject to two types of hazards: wind, measured by peak wind speed (PWS), and flooding, measured by flood water depth (FWD). This example does not use response simulation; rather, an **IMasEDP** application translates the IMs directly to the DL application and uses IM-based component fragility functions to estimate damage. -The distribution of the buildings' structural types and stories are illustrated below. - +This example is a small-scale regional hurricane risk assessment that performs damage/loss estimation for a group of 20 wooden buildings in Atlantic City during the Sandy Storm. The buildings are subject to two types of hazards: wind, measured by peak wind speed (PWS), and flooding, measured by flood water depth (FWD). This example does not use response simulation; instead, an **IMasEDP** application translates the IMs directly to the DL application and uses IM-based component fragility functions to estimate damage. The distributions of the buildings' structural types and stories are illustrated below. .. figure:: figures/SandyWindFlood.png :align: center :figclass: align-center - Peak wind speed and floor water depth maps of the Sandy Storm + Peak wind speed and flood water depth maps of the Sandy Storm Inputs -========== +====== The example input files can be downloaded here: :download:`example_hu.zip `. For more information about required input files, refer to :ref:`Inputs `. - -1. **Configuration file**: The configuration file specifies all simulation settings, including the application types, input file names, units, and type of outputs. +1. **Configuration file**: The configuration file specifies all simulation settings, including the application types, input file names, units, and types of outputs. .. literalinclude:: files/rWHALE_config_hu.json :language: python @@ -38,8 +34,6 @@ The example input files can be downloaded here: :download:`example_hu.zip ` regional mapping application. From the parameters set in the configuration file, the algorithm is set to randomly select 10 samples of wind/flooding IMs from the 4 nearest neighbors for each building asset. - - 4. **Event Application**: This example uses the :ref:`SimCenterEvents ` event application. It takes as input the EventGrid.csv and corresponding site files, which each have one instance of the intensity measures PWS and FWD assigned to the event site. **Event grid file:** @@ -56,14 +50,10 @@ The example input files can be downloaded here: :download:`example_hu.zip ` DL application. From the :ref:`building source file `, since the DL method selected is "HAZUS MH HU", damage/loss estimation is performed using the HAZUS loss assessment method based on hurricane IMs. Custom IM-based vulnerability functions are specified in the :download:`auto_HU_NJ.py `. - - Run Workflow ============ @@ -73,9 +63,7 @@ The workflow can be executed by uploading the appropriate files to :ref:`DesignS python "C:/rWHALE/applications/Workflow/R2D_workflow.py" "C:/rWHALE/hurricane_example/rWHALE_config_hu.json" --registry "C:/rWHALE/applications/Workflow/WorkflowApplications.json" --referenceDir "C:/rWHALE/hurricane_example/input_data/" -w "C:/rWHALE/hurricane_example/results" - - -This command locates the backend applications in the folder "applications", and the input files in a directory "hurricane_example". Please ensure that the paths in the command appropriately identify the locations of the files in your directory. +This command locates the backend applications in the folder "applications" and the input files in the directory "hurricane_example". Please ensure that the paths in the command accurately identify the locations of the files in your directory. :: @@ -93,30 +81,26 @@ This command locates the backend applications in the folder "applications", and ├── auto_HU_NJ.py # DL autoscript └── input_params.csv # building source file - - Outputs -========== +======= The example output files can be downloaded here: :download:`output_data_hu.zip `. For more information about the output files produced, refer to :ref:`Outputs `. -1. **EDP_1-20.csv**: reports statistics on EDP results, where the hazard IM is used as the EDP. As in HAZUS, the statistics reported are the median and lognormal standard deviation of peak wind speed (PWS) and flood water depth (FWD). +1. **EDP_1-20.csv**: This file reports statistics on EDP results, where the hazard IM is used as the EDP. As in HAZUS, the statistics reported are the median and lognormal standard deviation of peak wind speed (PWS) and flood water depth (FWD). .. csv-table:: EDP_1-20.csv :file: files/EDP_1-20.csv :header-rows: 1 :align: center - -2. **DM_1-20.csv**: reports collapse probability and damage state probability for each building asset. In the table below the "DSG_DS" values 0, 1_1, 2_1, 3_1, and 4_1 are four wind-induced damage states (from minor to severe), while the rest are the flood-induced damage states. +2. **DM_1-20.csv**: This file reports the collapse probability and damage state probability for each building asset. In the table below, the "DSG_DS" values 0, 1_1, 2_1, 3_1, and 4_1 represent four wind-induced damage states (from minor to severe), while the rest are the flood-induced damage states. .. csv-table:: DM_1-20.csv :file: files/DM_1-20.csv :header-rows: 1 :align: center - -2. **DV_1-20.csv**: reports decision variable estimates (i.e., repair cost) for each building asset. +3. **DV_1-20.csv**: This file reports decision variable estimates (i.e., repair cost) for each building asset. .. csv-table:: DV_1-20.csv :file: files/DV_1-20.csv diff --git a/docs/_sources/common/developer_manual/how_to_build/desktop/SimCenterBackend.rst.txt b/docs/_sources/common/developer_manual/how_to_build/desktop/SimCenterBackend.rst.txt index 23af036a..db53541f 100644 --- a/docs/_sources/common/developer_manual/how_to_build/desktop/SimCenterBackend.rst.txt +++ b/docs/_sources/common/developer_manual/how_to_build/desktop/SimCenterBackend.rst.txt @@ -2,12 +2,12 @@ Build the Backend ***************** - SimCenterBackendApplications contains many applications written in C++, C, and Python that are needed by all SimCenter User Interfaces. To build the backend you will need to follow the following steps: + SimCenterBackendApplications contains many applications written in C++, C, and Python that are needed by all SimCenter User Interfaces. To build the backend, you will need to follow these steps: 1. Clone the `SimCenterBackendApplications repository `_. 2. Build SimCenterBackendApplications using the following steps: - 2.1. Create a build directory for the build output, this can be done in the terminal using the command ``mkdir build``. + 2.1. Create a build directory for the build output. This can be done in the terminal using the command ``mkdir build``. 2.2. Install the backend dependencies using Conan. You can do this by going to the newly created build directory and running the command: @@ -15,14 +15,14 @@ Build the Backend This will install all the dependencies and will build dependencies from their source code as needed. - 2.3. Run CMake configuration this can be done using the command ``cmake ..``. Depending on your build environment, especially if you have multiple compilers, you may need to select a specific CMake generator. For instance, on Windows using Visual Studio 2017, you can configure CMake as follows: + 2.3. Run CMake configuration. This can be done using the command ``cmake ..``. Depending on your build environment, especially if you have multiple compilers, you may need to select a specific CMake generator. For instance, on Windows using Visual Studio 2017, you can configure CMake as follows: - ``cmake .. -G Visual Studio 15 2017 Win64`` + ``cmake .. -G "Visual Studio 15 2017 Win64"`` - 2.4. Build the release version of the backend, this can be done using the generated build system. For instance, on Unix-based systems when using make files this can be achieved using the command ``make`` or ``make release``. When using an IDE like Visual Studio on Windows or XCode on Mac, the generated project can be opened in the IDE and used to build the code. In addition, this can also be done from the terminal using CMake the command: + 2.4. Build the release version of the backend. This can be done using the generated build system. For instance, on Unix-based systems when using make files, this can be achieved using the command ``make`` or ``make release``. When using an IDE like Visual Studio on Windows or XCode on Mac, the generated project can be opened in the IDE and used to build the code. Additionally, this can also be done from the terminal using the CMake command: ``cmake --build . --config Release`` - 3. Install the backend applications to a local folder. This can be done by building the ``install target`` when using make on Unix-based systems. This can also be from IDE (e.g.) by selecting the install target or project and building it. In addition, this can be done from the terminal using the command: + 3. Install the backend applications to a local folder. This can be done by building the ``install target`` when using make on Unix-based systems. This can also be done from an IDE (e.g., by selecting the install target or project and building it). Additionally, this can be done from the terminal using the command: - ``cmake --build . --target install`` or ``cmake --install`` if you have CMake 3.15 or later. If building and installation were successful you should find a folder called ``applications`` in the repository with all the applications inside it. + ``cmake --build . --target install`` or ``cmake --install`` if you have CMake 3.15 or later. If the build and installation were successful, you should find a folder called ``applications`` in the repository with all the applications inside it. diff --git a/docs/_sources/common/developer_manual/how_to_build/desktop/how_to_build.rst.txt b/docs/_sources/common/developer_manual/how_to_build/desktop/how_to_build.rst.txt index 92a34040..75870307 100644 --- a/docs/_sources/common/developer_manual/how_to_build/desktop/how_to_build.rst.txt +++ b/docs/_sources/common/developer_manual/how_to_build/desktop/how_to_build.rst.txt @@ -4,12 +4,11 @@ How to Build ============ -SimCenter tools all comprise a frontend user interface (UI) and backend applications. They are kept in separate GitHub repositories and are also built separately. The following sections outline (1) the applications needed to build and run, (2) instructions for building the backend applications, (3) instructions for building the frontend UI, and (4) operations to perform in the running UI to link the UI and the backend. - +SimCenter tools consist of a frontend user interface (UI) and backend applications. They are maintained in separate GitHub repositories and are also built separately. The following sections outline (1) the applications needed to build and run, (2) instructions for building the backend applications, (3) instructions for building the frontend UI, and (4) operations to perform in the running UI to link the UI with the backend. .. note:: - As part of our continuous integration process, |app| is built every time we check code into the NHERI-SimCenter repositories. To do this we make use of a CI service. That current service is `appveyor `_. As a consequence in the |app| repo that you will clone as part of this build process there is a file **appveyor.yml**. This file contains shell commands that are issued to set up the operating system, download the software, and build it. If the following commands fail for you, look at the appveyor.yml file to see what commands are currently being called as these may be more up-to-date than what is presented below. + As part of our continuous integration process, |app| is built every time we check code into the NHERI-SimCenter repositories. To do this, we use a CI service. The current service is `AppVeyor `_. Consequently, in the |app| repo that you will clone as part of this build process, there is a file **appveyor.yml**. This file contains shell commands that are issued to set up the operating system, download the software, and build it. If the following commands fail for you, look at the appveyor.yml file to see what commands are currently being called, as these may be more up-to-date than what is presented below. ******************** Install Dependencies @@ -17,7 +16,7 @@ Install Dependencies First, ensure the following dependencies are installed: -* **C++17 compliant compiler**: many of the workflow applications included use C++17 features; consequently, they may need a newer C++17 compliant compiler. For Windows users, MSVC in `Visual Studio 2019 (Community Edition) `_ can be used. Some extensions of Visual Studio are also needed: Open Visual Studio Installer, go to Installed / More / Modify, under the Workloads tab, check Desktop development with C++ and Visual Studio extension development; under the Individual components tab, check C++ CMake tools for Windows. Then click Modify. +* **C++17 compliant compiler**: Many of the workflow applications included use C++17 features; consequently, they may need a newer C++17 compliant compiler. For Windows users, MSVC in `Visual Studio 2019 (Community Edition) `_ can be used. Some extensions of Visual Studio are also needed: Open Visual Studio Installer, go to Installed / More / Modify, under the Workloads tab, check Desktop development with C++ and Visual Studio extension development; under the Individual components tab, check C++ CMake tools for Windows. Then click Modify. * **OpenSees**: The workflow applications require an installation of `OpenSees `_ to carry out a structural analysis using the finite element method. @@ -25,7 +24,7 @@ First, ensure the following dependencies are installed: * **Python**: The workflow requires at least Python 3.7. -* **Conan**: This repository uses `Conan `_, a python library, for dependency management. **Install conan version 1.60.2**, for example, through +* **Conan**: This repository uses `Conan `_, a Python library, for dependency management. **Install conan version 1.60.2**, for example, through .. code:: console @@ -39,7 +38,7 @@ First, ensure the following dependencies are installed: .. warning:: - Qt Version 6.0 is currently available. It is so new we do not use it. + Qt Version 6.0 is currently available. It is so new we do not use it. ****************************** Build the Backend Applications @@ -61,7 +60,6 @@ Setup the development environment with Conan conan profile new default --detect - 3. Check the default profile of your build environment using: .. code:: console @@ -75,20 +73,19 @@ Setup the development environment with Conan conan profile update settings.compiler="Visual Studio" default conan profile update settings.compiler.version="16" default - Build the applications ====================== -#. Obtain the code in the SimCenterBackendApplications repository from `Github `_. You can do that by using your preferred Git client/GUI or by using the ``git clone`` command in the terminal: - - .. code:: - - git clone https://github.com/NHERI-SimCenter/SimCenterBackendApplications +#. Obtain the code in the SimCenterBackendApplications repository from `GitHub `_. You can do that by using your preferred Git client/GUI or by using the ``git clone`` command in the terminal: -#. To build the applications you need to now navigate to the **SimCenterBackendApplications** folder that was created with the **git clone** command. Once there you will issue the following set of commands to create a **build** folder, change directory to that folder, install needed software using conan, and finally use **cmake** to build and install the applications. The following are the set of commands to type in the terminal (see notes below the code block if the commands fail). + .. code:: console + git clone https://github.com/NHERI-SimCenter/SimCenterBackendApplications - For those developers using the Windows operating system, in a terminal or power-shell window you need to type the following: +#. To build the applications, you need to navigate to the **SimCenterBackendApplications** folder that was created with the **git clone** command. Once there, issue the following set of commands to create a **build** folder, change directory to that folder, install needed software using Conan, and finally use **CMake** to build and install the applications. The following are the set of commands to type in the terminal (see notes below the code block if the commands fail). + + On Windows, it is necessary to specify a compiler for CMake. To do this, you need to add additional arguments to line 4. That means, + for those developers using the Windows operating system, in a terminal or PowerShell window you need to type the following: .. code:: console @@ -99,8 +96,8 @@ Build the applications cmake --build . --config Release cmake --install . cd .. - - On Windows, it is necessary to specify a compiler for CMake. To do this, you need to add additional arguments to line 4, i.e., if you have Visual Studio 2019, you would instead type: + + Developer using other machines should type the following command: .. code:: console @@ -110,108 +107,97 @@ Build the applications cmake .. cmake --build . --config Release cmake --install . - make install . - cd .. + cd .. .. note:: - #. For Mac users running **Big Sur** and version **12** of XCode there are some reported issues. Replace line 3 above with the following two lines: + #. For Mac users running **Big Sur** and version **12** of XCode, there are some reported issues. Replace line 3 above with the following two lines: - .. code:: + .. code:: console conan install .. --build missing --build=libcurl mv ./missing/* ./ #. For Mac users, add the following command after **cmake --install .** to ensure the binary applications are copied to the applications folder. - .. code:: + .. code:: console make install . - - If building and installation were successful, you should find a folder called ``applications`` in the repository with all the applications inside of it. The name of this folder should not be changed. - - ************************ Build the User Interface ************************ -To build the interface, you first need to download the repo and a companion repo(SimCenterCommon) from GitHub using our `GitHub repos `_. In a folder in which you wish to build the application, issue the following two commands. +To build the interface, you first need to download the repo and a companion repo (SimCenterCommon) from GitHub using our `GitHub repos `_. In a folder in which you wish to build the application, issue the following two commands. .. only:: quoFEM_app - .. code:: - + .. code:: console + git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git git clone https://github.com/NHERI-SimCenter/quoFEM.git .. only:: R2D_app - - .. code:: - + .. code:: console + git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git git clone https://github.com/NHERI-SimCenter/R2DTool.git - .. only:: PBE_app - .. code:: + .. code:: console - git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git - git clone https://github.com/NHERI-SimCenter/QS3hark.git - git clone https://github.com/NHERI-SimCenter/EE-UQ.git - git clone https://github.com/NHERI-SimCenter/PBE.git + git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git + git clone https://github.com/NHERI-SimCenter/QS3hark.git + git clone https://github.com/NHERI-SimCenter/EE-UQ.git + git clone https://github.com/NHERI-SimCenter/PBE.git .. only:: EEUQ_app - .. code:: - - git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git - git clone https://github.com/NHERI-SimCenter/QS3hark.git - git clone https://github.com/NHERI-SimCenter/EE-UQ.git + .. code:: console -.. only:: WEUQ_app + git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git + git clone https://github.com/NHERI-SimCenter/QS3hark.git + git clone https://github.com/NHERI-SimCenter/EE-UQ.git - .. code:: +.. only:: WEUQ_app - git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git - git clone https://github.com/NHERI-SimCenter/WE-UQ.git + .. code:: console -.. only:: HydroUQ_app + git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git + git clone https://github.com/NHERI-SimCenter/WE-UQ.git - .. code:: +.. only:: HydroUQ_app - git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git - git clone https://github.com/NHERI-SimCenter/HydroUQ.git + .. code:: console + git clone https://github.com/NHERI-SimCenter/SimCenterCommon.git + git clone https://github.com/NHERI-SimCenter/HydroUQ.git .. note:: - - Use the above links if you just want to download and build the applications. If you intend to make changes to any of the code in the repos, you should fork that repo and then clone your forked repo. Forking a repo at **GitHub** is done through your browser as shown on the following `GitHub guides page `_ + Use the above links if you just want to download and build the applications. If you intend to make changes to any of the code in the repos, you should fork that repo and then clone your forked repo. Forking a repo at **GitHub** is done through your browser as shown on the following `GitHub guides page `. You now have two ways to build the application: (1) using the **Qt Creator** desktop application provided by **Qt** and (2) from the terminal application. - Build using Qt Creator ======================== 1. Start Qt Creator, then open the |short tool id|.pro file located in the |short tool id| directory that was downloaded in the previous step. 2. Set up the development kit in Qt Creator. This is usually done by selecting the Qt version, compiler, and configuration and following the onscreen dialog. -3. Build the application and run it in Qt Creator IDE using the **Run** button. This can be done using the keyboard shortcut ``F5`` to build and start the tool. - +3. Build the application and run it in the Qt Creator IDE using the **Run** button. This can be done using the keyboard shortcut ``F5`` to build and start the tool. Build from the Terminal ======================== -The operations are similar to what was done when building the backend applications. In the terminal application, starting inside the directory of the cloned application again, you will create a build directory, cd into that build directory, run **qmake**, and finally make (or on Windows nmake) to create the application. +The operations are similar to what was done when building the backend applications. In the terminal application, starting inside the directory of the cloned application again, you will create a build directory, cd into that build directory, run **qmake**, and finally make (or on Windows, nmake) to create the application. -Windows developers will type the following in a terminal or a power-shell window: +Windows developers will type the following in a terminal or a PowerShell window: - .. parsed-literal:: + .. code:: console mkdir build cd build @@ -221,7 +207,7 @@ Windows developers will type the following in a terminal or a power-shell window Linux or Mac users will type the following in a terminal window from inside the |app| directory: - .. parsed-literal:: + .. code:: console mkdir build cd build @@ -231,20 +217,21 @@ Linux or Mac users will type the following in a terminal window from inside the .. note:: - #. qmake is an application installed with Qt. To be able to run the command as known, the path to the Qt bin folder needs to be added to your **PATH** environment variable. Alternatively, you need to specify the full path to qmake, i.e., on my desktop (if I had not set my PATH variable). I would replace line 3 with the following: + #. qmake is an application installed with Qt. To be able to run the command as known, the path to the Qt bin folder needs to be added to your **PATH** environment variable. Alternatively, you need to specify the full path to qmake, i.e., on my desktop (if I had not set my PATH variable), I would replace line 3 with the following: - .. parsed-literal:: + .. code:: console /Users/fmckenna/Qt/5.15.2/clang_64/bin/qmake ../|short tool id|.pro - - #. On a Windows 10 with Visual Studio, the above commands need to be performed using a `Visual Studio x64 command prompt `_ . + #. On Windows 10 and later with Visual Studio, the above commands need to be performed using a `Visual Studio x64 command prompt `_. #. If installed, jom can also be used to build in parallel. - Once built, you can now run the tool executable. +.. note:: + + On Windows machines, you need to copy essential QGIS DLLs. To do so, run *make.bat* in R2DTool root directory **or** manually copy and past them in ./ build directory. Otehrwise, after runing **R2D.exe** file in ./build directory, you will receive missing DLL errors. ************************************* Modify the User Interface Preferences @@ -254,14 +241,13 @@ Once built, the tool **Preferences** needs to be modified. To do this, open the #. Python: provide the full path to the Python interpreter. - #. OpenSees: provide the full path to the OpenSees executable + #. OpenSees: provide the full path to the OpenSees executable. #. Dakota: provide the full path to the Dakota executable. #. Custom Local Application: Here, select the checkbox to the left, and then provide the path to the SimCenterBackendApplications directory. The code assumes that the folder **applications**, which you created when building the backend applications, exists. - - .. _figPreferences: +.. _figPreferences: .. only:: notQuoFEM @@ -278,4 +264,3 @@ Once built, the tool **Preferences** needs to be modified. To do this, open the :figclass: align-center Preferences Dialog - diff --git a/docs/_sources/common/front-matter/cite.rst.txt b/docs/_sources/common/front-matter/cite.rst.txt index 2bdc3aa9..f3195220 100644 --- a/docs/_sources/common/front-matter/cite.rst.txt +++ b/docs/_sources/common/front-matter/cite.rst.txt @@ -6,7 +6,7 @@ How To Cite .. only:: R2D_app - 1. Frank McKenna, Stevan Gavrilovic, Jinyan Zhao, Kuanshi Zhong, Adam Zsarnoczay, Barbaros Cetiner, Sang-ri Yi, Pedro Arduino, & Wael Elhaddad. (2024). NHERI-SimCenter/R2DTool: Version 4.1.0 (v4.1.0). Zenodo. ``_ + 1. Frank McKenna, Stevan Gavrilovic, Jinyan Zhao, Kuanshi Zhong, Adam Zsarnoczay, Barbaros Cetiner, Sang-ri Yi, Aakash Bangalore Satish, Sina Naeimi, & Pedro Arduino. (2024). NHERI-SimCenter/R2DTool: Version 4.2.0 (v4.2.0). Zenodo. ``_ .. only:: PBE_app @@ -14,8 +14,8 @@ How To Cite .. only:: EEUQ_app - 1. Frank McKenna, Kuanshi Zhong, Michael Gardner, Adam Zsarnoczay, Sang-ri Yi, Aakash Bangalore Satish, Charles Wang, & Wael Elhaddad. (2024). NHERI-SimCenter/EE-UQ: Version 3.5.0 (v3.5.0). Zenodo. ``_ - + 1. Frank McKenna, Kuanshi Zhong, Michael Gardner, Adam Zsarnoczay, Sang-ri Yi, Aakash Bangalore Satish, Charles Wang, Amin Pakzad, Pedro Arduino, & Wael Elhaddad. (2024). NHERI-SimCenter/EE-UQ: Version 4.1.0 (v4.1.0). Zenodo. https://doi.org/10.5281/zenodo.13865428 + .. only:: WEUQ_app 1. Frank McKenna, Abiy F. Melaku, Fei Ding, Jiawei Wan, Peter Mackenzie-Helnwein, Wael Elhaddad, diff --git a/docs/_sources/common/technical_manual/desktop/HazardSimulationTool_useCase.rst.txt b/docs/_sources/common/technical_manual/desktop/HazardSimulationTool_useCase.rst.txt index 608ae8f0..e5ea5f09 100644 --- a/docs/_sources/common/technical_manual/desktop/HazardSimulationTool_useCase.rst.txt +++ b/docs/_sources/common/technical_manual/desktop/HazardSimulationTool_useCase.rst.txt @@ -1,8 +1,10 @@ .. _lblEQSimulationUseCases: + Regional Earthquake Hazard Use Cases -==================================================== +==================================== + The major use cases of Regional Earthquake Hazard in R2D can be divided -into Scenario-specific or Probabilistic Seismic Hazard Analysis. +into Scenario-specific or Probabilistic Seismic Hazard Analysis. .. _fig-R2DScenarioOrPSHA: @@ -13,23 +15,24 @@ into Scenario-specific or Probabilistic Seismic Hazard Analysis. Specific Earthquake Scenario or Probabilistic Hazard Analysis. Scenario-specific Earthquake ------------------------------ -This option is to analyze an earthquake scenario that consists of one or more ruptures -based on an earthquake description of a past or hypothetical event. Some use cases -for which this option are: - #. Analysis of a single rupture. For example, running the "Hayward-Rodgers Creek; HN+HS" segment, which is a specific rupture location, length, characteristics, etc. - #. Broader analysis of a scenario. For example, running "an M7 earthquake on the San Andreas Fault." This would include realizations with different ruptures, that all describe an M7 on the San Andreas. - #. Multiple specified ruptures. This would be used in the case in which a user already has a defined set of ruptures they are interested in studying. This option does not fully capture the probabilistic seismic hazard of a region. - #. A past earthquake. For example, recreating the Loma Prieta earthquake. +---------------------------- + +This option is for analyzing an earthquake scenario that consists of one or more ruptures +based on the description of a past or hypothetical event. Some use cases +for this option are: + #. Analysis of a single rupture. For example, running the "Hayward-Rodgers Creek; HN+HS" segment, which is a specific rupture location, length, characteristics, etc. + #. Broader analysis of a scenario. For example, running "an M7 earthquake on the San Andreas Fault." This would include realizations with different ruptures, all describing an M7 on the San Andreas. + #. Multiple specified ruptures. This would be used when a user already has a defined set of ruptures they are interested in studying. This option does not fully capture the probabilistic seismic hazard of a region. + #. A past earthquake. For example, recreating the Loma Prieta earthquake. :numref:`fig-R2DScenarioSpecificUseCases` shows typical scenario-specific use cases in R2D. All the use cases in :numref:`fig-R2DScenarioSpecificUseCases` can be achieved with R2D. The first two options are loading predefined -ground motion records or intensity measures in the region, and are described in +ground motion records or intensity measures in the region and are described in :ref:`User-specified Ground Motions `. The functionality to -interface with some physics-based earthquake simulation databases is also under development in R2D. -The third to fifty use cases in :numref:`fig-R2DScenarioSpecificUseCases` requires +interface with some physics-based earthquake simulation databases is also under development in R2D. +The third to fifth use cases in :numref:`fig-R2DScenarioSpecificUseCases` require the :ref:`earthquake hazard simulation tool `, and the last option -can be achieved as described in :ref:`ShakeMap Earthquake Scenarios `). +can be achieved as described in :ref:`ShakeMap Earthquake Scenarios `. The functions in the earthquake hazard simulation tool required for scenario-specific use cases are Site Definition, @@ -37,8 +40,7 @@ Earthquake Rupture Forecasting, Intensity Measure Definition, Ground Motion Pred Equations, Spatial Correlations, and Ground Motion Record Selection (optional). The "Scenario-specific" option should be selected in the "Scenario Selection" tool tab. More details of the use cases, required inputs, and some benefits/limitations are -summarised in :numref:`tab-R2DScenarioSpecificUseCases`. - +summarized in :numref:`tab-R2DScenarioSpecificUseCases`. .. _fig-R2DScenarioSpecificUseCases: @@ -59,37 +61,37 @@ summarised in :numref:`tab-R2DScenarioSpecificUseCases`. - Required Inputs - Benefits/Limitations * - Predefined GM - - User already has ground motion time histories they are interested in. + - User already has ground motion time histories they are interested in. - Describe any specific file type/folder structure required. - - * - Predefined IM + * - Predefined IM - User already has an IM field they are interested in. GM selection can be done. - Describe any specific file type/folder structure required. - - * - OpenSHA/UCERF + * - OpenSHA/UCERF - Recommended where UCERF ruptures are available (maybe we can show a map). Recommended because it requires no additional inputs other than selections using the R2D interface (source models are openly available). - - No external files are required, and all selections can be done in R2D. - - Users can select out of several choices of GMM and correlation models to use through the R2D interface. Limited in that it only has information available about ruptures in certain locations. - * - OpenQuake + - No external files are required, and all selections can be done in R2D. + - Users can select from several choices of GMM and correlation models through the R2D interface. Limited in that it only has information about ruptures in certain locations. + * - OpenQuake - Recommended to describe distributed and background seismicity. Also recommended for use where rupture information is unavailable through UCERF. - - External source model file required. The format of source models can be found :ref:`here `, and a database of global earthquake sources can be found at the `GEM's Global Active Faults Database `_ [Styron2020]_ + - External source model file required. The format of source models can be found :ref:`here `, and a database of global earthquake sources can be found at the `GEM's Global Active Faults Database `_ [Styron2020]_ - Can be used to describe distributed and background seismicity where information on the faults is unavailable. * - Point Source - - For educational and/or academic use only. The point source option does not accurately reflect real faults. + - For educational and/or academic use only. The point source option does not accurately reflect real faults. - No external files are required, and all selections can be done in R2D. - - Not representative of real faults/scenarios. + - Not representative of real faults/scenarios. * - ShakeMap - Re-creation of a past earthquake event by obtaining seismic intensity measures sufficiently representative of the event. - - Inputs are USGS ShakeMap files for a given earthquake scenario. These files must be located in a folder in which at least must be a grid.xml file. The files contain ShakeMaps that include the intensity measures for a given earthquake event as spectral ordinate values (Those can be given as PGA, PGV, PGD, and spectral ordinates at different periods). These files can be obtained from `USGS's ShakeMap archives `_ for real past earthquake events. - - ShakeMap intensity measures (as spectral ordinates) for past earthquakes might not be an accurate representation of this event in locations far from the grid control points (usually recording stations where GMM predictions are adjusted to match real recorded ground motion spectra). Moreover, the set of scenarios is limited. - + - Inputs are USGS ShakeMap files for a given earthquake scenario. These files must be located in a folder with at least a grid.xml file. The files contain ShakeMaps that include the intensity measures for a given earthquake event as spectral ordinate values (These can be given as PGA, PGV, PGD, and spectral ordinates at different periods). These files can be obtained from `USGS's ShakeMap archives `_ for real past earthquake events. + - ShakeMap intensity measures (as spectral ordinates) for past earthquakes might not be an accurate representation of the event in locations far from the grid control points (usually recording stations where GMM predictions are adjusted to match real recorded ground motion spectra). Moreover, the set of scenarios is limited. Regional Probabilistic Seismic Hazard Analysis ---------------------------------------------- + The regional probabilistic seismic hazard analysis (PSHA) characterizes the probability that certain levels of intensity are exceeded in a region considering all nearby -earthquake sources. -:numref:`fig-R2DScenarioSpecificUseCases` shows two typical use cases in regional PSHA. +earthquake sources. +:numref:`fig-R2DRegionalPSHAUseCases` shows two typical use cases in regional PSHA. Both use cases can be achieved in R2D with the :ref:`earthquake hazard simulation tool `. The functions in the earthquake hazard simulation tool required for regional PSHA are Site Definition, @@ -97,7 +99,7 @@ Earthquake Rupture Forecasting, Intensity Measure Definition, Ground Motion Pred Equations, Spatial Correlations, Ground Motion Record Selection (optional), and hazard consistent downsampling (optional). The "Conventional Monte Carlo" or "Hazard consistent downsampling" option should be selected in the "Scenario Selection" tool tab. More details of the use cases, -required inputs, and some benefits/limitations are summarised in :numref:`tab-R2DRegionalPSHAUseCases`. +required inputs, and some benefits/limitations are summarized in :numref:`tab-R2DRegionalPSHAUseCases`. .. _fig-R2DRegionalPSHAUseCases: @@ -121,11 +123,10 @@ required inputs, and some benefits/limitations are summarised in :numref:`tab-R2 - Recommended where UCERF ruptures are available (maybe we can show a map). Recommended because it requires no additional inputs other than selections using the R2D interface (source models are openly available). - No external files are required, and all selections can be done in R2D. - Only available for California. - * - OpenQuake - - Recommended for use where UCERF ruptures are unavailable. - - External files required. The format of source models can be found :ref:`here `, and a database of global earthquake sources can be found at the `GEM's Global Active Faults Database `_ [Styron2020]_ + * - OpenQuake + - Recommended for use where UCERF ruptures are unavailable. + - External files required. The format of source models can be found :ref:`here `, and a database of global earthquake sources can be found at the `GEM's Global Active Faults Database `_ [Styron2020]_ - Users need to prepare their earthquake source model. - .. [Styron2020] - Styron, Richard, and Marco Pagani. “The GEM Global Active Faults Database.” Earthquake Spectra, vol. 36, no. 1_suppl, Oct. 2020, pp. 160–180, doi:10.1177/8755293020944182. + Styron, R., & Pagani, M. (2020). The GEM global active faults database. Earthquake Spectra, 36(1_suppl), 160-180. diff --git a/docs/_sources/common/technical_manual/desktop/SimCenterUQTechnical.rst.txt b/docs/_sources/common/technical_manual/desktop/SimCenterUQTechnical.rst.txt index b93f4b3c..f7dd9af1 100644 --- a/docs/_sources/common/technical_manual/desktop/SimCenterUQTechnical.rst.txt +++ b/docs/_sources/common/technical_manual/desktop/SimCenterUQTechnical.rst.txt @@ -37,7 +37,7 @@ Global sensitivity analysis =========================== Video Resources ------------------- +---------------- Global Sensitivity Analysis: why, what, and how. .. raw:: html @@ -53,7 +53,7 @@ Global Sensitivity Analysis: why, what, and how. Variance-based global sensitivity indices ------------------------------------ +----------------------------------------- Global sensitivity analysis (GSA) is performed to quantify the contribution of each input variable to the uncertainty in QoI. Using the global sensitivity indices, users can set preferences between random variables considering both inherent randomness and its propagation through the model. GSA helps users to understand the overall impact of different sources of uncertainties, as well as accelerate UQ computations by focusing on dominant dimensions or screening out trivial input variables. .. _figSensitivity1: @@ -105,7 +105,7 @@ where :math:`\boldsymbol{x}_{\sim ij}` indicates the set of all input variables Estimation of Sobol indices using Probabilistic model-based global sensitivity analysis (PM-GSA) ----------------------------- +------------------------------------------------------------------------------------------------ GSA is typically computationally expensive. High computation cost attributes to the multiple integrations (:math:`d`-dimensional) associated with the variance and expectation operations shown in Eqs. :eq:`Si` and :eq:`SiT`. To reduce the computational cost, efficient Monte Carlo methods, stochastic expansion methods, or meta-model-based methods can be employed. Among different approaches, the SimCenterUQ engine supports the probability model-based GSA (PM-GSA) framework developed by [Hu2019]_. @@ -133,7 +133,7 @@ using the expectation-maximization (EM) algorithm. The mean operation Eq. :eq:`S Dealing with high-dimensional responses with PCA-PSA ---------------------------------------------------- +---------------------------------------------------- When the number of the quantities of interest (QoI) is very large, it is computationally cumbersome to perform above Gaussian fitting independently for each QoI. To promote efficient global sensitivity analysis for such cases, SimCenterUQ provides the 'principal component analysis-based PM-GSA' module, which is referred to as PCA-PSA [Jung2022]_. In this method, the dimension of QoI is first reduced by principal component analysis (PCA), and the conditional variance required to calculate the Sobol indices (the numerators in :eq:`Si` and :eq:`SiT`) is approximately reconstructed from those of the conditional variance/covariance information of the reduced dimension variables. If the high-dimensional QoI has a linear data structure that be reconstructed with a small number of principal components, the computational gain of this approach can be significant. For example, suppose QoI can be reconstructed using 10 principal components. In that case, the Gaussian mixture fitting, which is the most time-consuming step of PM-GSA apart from FEM analysis, needs to be repeated only 10 times per random variable or group of random variables regardless of the actual dimension of QoI. :ref:`This example` shows how PCA-PSA can facilitate efficient global sensitivity analysis for a field (time series) QoI. @@ -142,7 +142,7 @@ When the number of the quantities of interest (QoI) is very large, it is computa Aggregated sensitivity index ------------------------------ +---------------------------- When the quantities of interest (QoI) are given as a vector or field variable, an aggregated sensitivity index can provide insight into the system's overall sensitivity characteristics. The aggregated sensitivity index achieves this by calculating the weighted average of the sensitivity indices of each QoI component, where the weights are proportional to the variances of the components [Jung2022]_. Component sensitivity indices are useful for visualization, while the aggregated sensitivity index gives instant intuition on how much each variable influences the system response overall. See :ref:`this example`. @@ -152,10 +152,10 @@ When the quantities of interest (QoI) are given as a vector or field variable, a .. _lbluqSimTechnical_Surrogate: Global surrogate modeling -============================ +========================= Introduction to Gaussian process regression (Kriging) --------------------------------------------------------- +----------------------------------------------------- Global surrogate modeling aims to build a regression model that reproduces the outcomes of computationally expensive high-fidelity simulations. @@ -193,7 +193,7 @@ Therefore, the main tasks of surrogate modeling are (1) to find optimal stochast Dealing with noisy measurements --------------------------------------------------------- +------------------------------- | In natural hazard applications, often the exact observations of :math:`\boldsymbol{y}` are not available and only the noisy observations :math:`\boldsymbol{y^{obs}}` are available: @@ -289,7 +289,7 @@ Input-Output settings Kernel and basis functions -^^^^^^^^^^^^^^^^^^^^^^^^^^^ +^^^^^^^^^^^^^^^^^^^^^^^^^^ The covariance kernel of the outcome process is unknown in most practical applications. Therefore, the mathematical form of the kernel is first assumed, and its parameters are calibrated based on the observation data. Following are some popular stationary covariance kernels. * **Radial-basis function (RBF)** @@ -349,7 +349,7 @@ Once the kernel form is selected, the parameters are calibrated to maximize the Adaptive Design of Experiments (DoE) -------------------------------------- +------------------------------------ .. only:: quoFEM_app @@ -509,10 +509,10 @@ We provide different verification measures for two different cases. .. _lbluqSimTechnical_MFMC: Multi-fidelity Monte Carlo (MFMC) -===================================== +================================= Models with different infidelities ---------------------------------------- +---------------------------------- When one has multiple models of a target system with different fidelities, one can introduce multi-fidelity Monte Carlo (MFMC) methods. MFMC helps us to reduce the high-fidelity simulation runs by leveraging a large number of low-fidelity simulations. The high-fidelity and low-fidelity models are defined as the following. * **High-fidelity (HF) model**: The model with the desired level of accuracy and high computational cost. @@ -543,12 +543,12 @@ The goal of MFMC is to estimate the statistics of the HF model using a small num Pre-execution checklist for MFMC ----------------------------------------------- +-------------------------------- Before running the MFMC simulation model, the users are advised to check the validity and effectiveness of MFMC for their problem. Only when the below conditions are satisfied, the users are expected to gain meaningful benefits by using MFMC compared to only HF simulations: * **The models should take the same input random variables and produce the same output quantities of interest.** For example, if the target system is a structure, if one model takes stiffness as a random variable and the other does not, the model violates the problem definition. Similarly, if :math:`j`-th output of the HF model is the 1st-floor inter-story drift, :math:`j`-th output of the LF model should also be the 1st-floor inter-story drift. -* **The models should have a clear hierarchy in terms of accuracy and time.** When the HF and LF model responses are different, the assumption is that the HF response is always accurate. Therefore, if an LF model runs faster than the HF model, it is optimal to run only the HF model, and there is no reason to introduce MFMC. +* **The models should have a clear hierarchy in terms of accuracy and time.** When the HF and LF model responses are different, the assumption is that the HF response is always accurate. Therefore, if an HF model runs faster than the LF model, it is optimal to always run only the HF model, and there is no reason to introduce MFMC. * **The response of different models should have a high correlation**. The efficiency of MFMC heavily depends on the correlation between the HF and LF model outputs. Only if the correlation is fairly high, the MF estimation is meaningfully efficient than conducting only HF simulations. @@ -565,7 +565,7 @@ The efficiency of MFMC can be evaluated using the speed-up ratio, defined as the Algorithm details ----------------------------------------------- +----------------- The implementation of MFMC in |short tool id| follows that of [Patsialis2021]_ which is based on the original work of [Peherstorfer2016]_. Let us denote the HF and LF output for a given input :math:`x` as .. math:: @@ -668,7 +668,7 @@ Note that the first four terms are evaluated using only :math:`D_1`, and the las Speed-up ----------------------------------------------- +-------- The speed-up is an efficiency metric that represents the computational time you save by using MFMC compared to only HF simulations to reach the same level of accuracy (same variance). .. math:: diff --git a/docs/_sources/common/technical_manual/desktop/hazard_occurrence.rst.txt b/docs/_sources/common/technical_manual/desktop/hazard_occurrence.rst.txt index 9f751bde..e4b97101 100644 --- a/docs/_sources/common/technical_manual/desktop/hazard_occurrence.rst.txt +++ b/docs/_sources/common/technical_manual/desktop/hazard_occurrence.rst.txt @@ -3,30 +3,30 @@ Hazard Occurrence =================== -A regional seismic risk analysis consists of three elements: (1) an exposure time over which the risk is evaluated, +A regional seismic risk analysis comprises three elements: (1) an exposure time over which the risk is evaluated, (2) a loss or quantification to be evaluated, and (3) a specification of the probability of incurring the loss during the specified -exposure time. These three elements can be formulated into different workflows and one of the possible workflows can include: -(1) hazard analysis (understanding the possible seismic sources in the studied region), (2) ground motion characterization -(representing the possible seismicity by earthquake ground motions at each site, e.g., time history records, intensity measures), +exposure time. These three elements can be formulated into different workflows. One possible workflow includes: +(1) hazard analysis (understanding the potential seismic sources in the studied region), (2) ground motion characterization +(representing the potential seismicity by earthquake ground motions at each site, e.g., time history records, intensity measures), (3) inventory identification (collecting the basic information of the buildings and infrastructures to be analyzed), and (4) response/damage/loss assessment (mapping the ground motion characteristics and building inventory to the response, damage, and loss in the region). -Different from the seismic risk analysis of a single structure, the spatial correlation between different site locations usually needs to be -considered in estimating the total damage and loss of a portfolio of buildings or infrastructures. This consideration is naturally fulfilled if +Unlike the seismic risk analysis of a single structure, the spatial correlation between different site locations usually needs to be +considered when estimating the total damage and loss of a portfolio of buildings or infrastructures. This consideration is naturally fulfilled if physics-based earthquake simulation is involved. If empirical ground motion models are used, then spatial correlation models (please see more details in :ref:`lblCorrelation`) need to be evaluated and used in sampling the ground motion maps explicitly. The simulated ground motions are then used as the input for assessing the regional seismic risk of the portfolio. To propagate the uncertainty in the seismic hazard, ground motion characteristics, and structural damage and loss fragility, the risk analysis -typically needs a sufficient number of samples (realizations) to reliably estimate the mean and variation of possible damage and loss. For instance, -if applying the conventional Monte Carlo method (e.g., [Bazzurro07]_), for each of the considered earthquake scenarios (with a specific magnitude and location), -many ground motion intensity maps are first simulated. Then, for each of the ground motion maps, several assessments of damage and loss are +typically requires a sufficient number of samples (realizations) to reliably estimate the mean and variation of potential damage and loss. For instance, +when applying the conventional Monte Carlo method (e.g., [Bazzurro07]_), for each of the considered earthquake scenarios (with a specific magnitude and location), +numerous ground motion intensity maps are first simulated. Then, for each of the ground motion maps, several assessments of damage and loss are conducted to propagate the uncertainty in the inventory, response analysis model, and/or fragility functions. The process is repeated for -all considered earthquake scenarios which leads to a tremendous number of realizations and an excessive computational demand. +all considered earthquake scenarios, leading to a large number of realizations and an excessive computational demand. To alleviate the computational cost of regional seismic risk analysis, a concept of *probabilistic earthquake scenarios* was proposed and developed by -many researchers (e.g., [Chang00]_, [Jayaram10]_, [Vaziri12]_). The key idea is to first reduce the full set of possible earthquake scenarios that affect the studied -region to a select subset of earthquakes each of which is used to evaluate the building and infrastructure performance, and then aggregate the results with +many researchers (e.g., [Chang00]_, [Jayaram10]_, [Vaziri12]_). The key idea is to first reduce the full set of potential earthquake scenarios that affect the studied +region to a select subset of earthquakes. Each of these earthquakes is used to evaluate the performance of the buildings and infrastructure, and then the results are aggregated with modified hazard-consistent probabilities for individual selected earthquakes. The modified probabilities of selected earthquakes are optimized so that the original hazard curves of individual sites can be recovered as much as possible ([Han12]_). Different optimization algorithms are implemented (e.g., [Wang20]_), different target functions beyond the error in hazard curve (e.g., [Miller14]_) are considered, and multiple intensity measures (e.g., [Ma22]_) @@ -57,7 +57,7 @@ between points on the reference hazard curves and the corresponding points on ha min \Sigma_{i=1}^{I} \Sigma_{r=1}^{R} w_{ir} (e_{ir}^{+}+e_{ir}^{-}) where :math:`e_{ir}^{+}` and :math:`e_{ir}^{-}` are the errors resulting from overestimating and underestimating, respectively, the reference hazard curve for the site :math:`i` -at the return period `r`. The weight :math:`w_{ir}` is taken as the return period so that the error occurring at a longer return period (i.e., higher intensity level) can be +at the return period :math:`r`. The weight :math:`w_{ir}` is taken as the return period so that the error occurring at a longer return period (i.e., higher intensity level) can be scaled relatively more than the error occurring at a shorter return period. This typically helps the final fitting given the nonlinear shape of a hazard curve. Assuming we have overall :math:`J` candidate earthquakes, for any earthquake scenario :math:`j`, we can use empirical ground motion model(s) to compute its resulting ground motion intensity @@ -98,7 +98,7 @@ a few more details of each major step. Workflow to generate a hazard-consistent reduced sample of earthquakes and ground motion maps using the OPS method. -In this example, we want to get a minimal number of earthquakes with modified occurrence rates to recover the reference hazard curves at each site location as much as possible. +In this example, we aim to get a minimal number of earthquakes with modified occurrence rates to recover the reference hazard curves at each site location as much as possible. The figure below plots the example sites in the San Francisco Bay Area, whose longitude and latitude data can be downloaded :download:`here <./src/SiteFile.csv>`. .. figure:: figures/hazard_occurrence_sites.png @@ -109,7 +109,7 @@ The figure below plots the example sites in the San Francisco Bay Area, whose lo Site locations for hazard occurrence modeling and probabilistic earthquake scenarios. Once downloaded, the site csv file can be loaded in the site widget of the **HAZ** panel under the "Earthquake Scenario Simulation" option. The figure below shows the site widget -after the file is loaded. The site-specific Vs30 data are fetched from Wills et al. 2015 model. +after the file is loaded. The site-specific Vs30 data are fetched from the Wills et al. 2015 model. .. figure:: figures/hazard_occurrence_site_widget.png :align: center @@ -118,10 +118,10 @@ after the file is loaded. The site-specific Vs30 data are fetched from Wills et Loading the site csv file in the site widget (scattering locations). -The figure below summarizes the hazard occurrence configuration: we want to select earthquake scenarios from the UCERF2 seismic sources. For -this demonstration, we want to have 100 candidate earthquakes. The backend script in the R2D follows the suggestion by Han and Davidson (2012) +The figure below summarizes the hazard occurrence configuration: we aim to select earthquake scenarios from the UCERF2 seismic sources. For +this demonstration, we aim to have 100 candidate earthquakes. The backend script in the R2D follows the suggestion by Han and Davidson (2012) ([Han12]_) to first order the candidate by its true occurrence rates - so the 100 candidates here are the ones with the highest occurrence rates to -the region. For the reduced representation with the probabilistic earthquake scenarios, we want no more than 10 earthquakes and no more than 100 +the region. For the reduced representation with the probabilistic earthquake scenarios, we aim to have no more than 10 earthquakes and no more than 100 ground motion maps. Note this setup is just for demonstration as the example site locations are not distant from each other - for more distributed sites, the candidate earthquake number, as well as the reduced earthquake number, should be increased to have better-matching results ([Han12]_). @@ -132,22 +132,15 @@ sites, the candidate earthquake number, as well as the reduced earthquake number Configurations for hazard occurrence modeling. -For all sites, we do not prescribe but fetch the site-specific hazard curves directly from `USGS API `_. -The intensity measure for the hazard curve is the response spectral acceleration at 1.0 second, Sa(T=1.0). The hazard curves are digitized at -four different return periods from 224 years to 2475 years. These four levels will be used later to compute the error for fitting the hazard curve. -These hazard curves are also saved during the simulation, please see the example format in :download:`./src/HazardCurves.json`. +For all sites, we fetch the site-specific hazard curves directly from the `USGS API `_, rather than prescribing them. The intensity measure for the hazard curve is the response spectral acceleration at 1.0 second, Sa(T=1.0). The hazard curves are digitized at four different return periods, ranging from 224 years to 2475 years. These four levels will be used later to compute the error for fitting the hazard curve. These hazard curves are also saved during the simulation; please see the example format in :download:`./src/HazardCurves.json`. -Once everything above is set up, please click the "Run Hazard Simulation" button located in the bottom right of the **HAZ** panel. It may take 5 to 10 -minutes to run the entire example (an internet connection is needed for fetching data in this example). Once the run is completed, there are three types of -output files in the "Output Directory" (please feel free to change the default one to your own directory in the -textbox located in the bottom left of the **HAZ** panel): +Once the above setup is complete, please click the "Run Hazard Simulation" button located in the bottom right of the **HAZ** panel. It may take 5 to 10 minutes to run the entire example (an internet connection is required for fetching data in this example). Once the run is completed, three types of output files can be found in the "Output Directory" (you are free to change the default directory to your own in the textbox located in the bottom left of the **HAZ** panel): -1. *RupSampled.json*: the information about the selected probabilistic earthquake ruptures (:download:`example <./src/RupSampled.json>`). -2. *InfoSampledGM.json*: the information about the selected ground motion maps (:download:`example <./src/InfoSampledGM.json>`). -3. *SiteIM.json*: the simulated intensity measures of the selected ground motion maps (:download:`example <./src/SiteIM.json>`). +1. *RupSampled.json*: This file contains information about the selected probabilistic earthquake ruptures (:download:`example <./src/RupSampled.json>`). +2. *InfoSampledGM.json*: This file contains information about the selected ground motion maps (:download:`example <./src/InfoSampledGM.json>`). +3. *SiteIM.json*: This file contains the simulated intensity measures of the selected ground motion maps (:download:`example <./src/SiteIM.json>`). -To validate the selected earthquake scenarios, the figure below contrasts the recovered seismic hazard curve and the reference hazard curve -(ground truth) for each site. +To validate the selected earthquake scenarios, the figure below contrasts the recovered seismic hazard curve and the reference hazard curve (ground truth) for each site. .. figure:: figures/hazard_occurrence_result.png :align: center @@ -156,7 +149,6 @@ To validate the selected earthquake scenarios, the figure below contrasts the re Comparison of recovered and reference hazard curves for the first 9 sites in the example. - .. [Bazzurro07] Bazzurro, P., & Luco, N. (2007). Effects of different sources of uncertainty and correlation on earthquake-generated losses. Australian Journal of Civil Engineering, 4(1), 1-14. @@ -182,4 +174,4 @@ To validate the selected earthquake scenarios, the figure below contrasts the re Ma, L., Conus, D., & Bocchini, P. (2022). Optimal Generation of Multivariate Seismic Intensity Maps Using Hazard Quantization. ASCE-ASME Journal of Risk and Uncertainty in Engineering Systems, Part A: Civil Engineering, 8(1), 04021078. .. [Manzour16] - Manzour, H., Davidson, R. A., Horspool, N., & Nozick, L. K. (2016). Seismic hazard and loss analysis for spatially distributed infrastructure in Christchurch, New Zealand. Earthquake Spectra, 32(2), 697-712. \ No newline at end of file + Manzour, H., Davidson, R. A., Horspool, N., & Nozick, L. K. (2016). Seismic hazard and loss analysis for spatially distributed infrastructure in Christchurch, New Zealand. Earthquake Spectra, 32(2), 697-712. diff --git a/docs/_sources/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.rst.txt b/docs/_sources/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.rst.txt index a911c472..6efbc80c 100644 --- a/docs/_sources/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.rst.txt +++ b/docs/_sources/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.rst.txt @@ -21,7 +21,7 @@ When a direct numerical simulation (DNS) is employed, the Navier-Stokes equation Since DNS is computational expensive, the large eddy simulation was proposed by Joseph Smagorinsky in 1963. The idea of LES was to ignore the smaller length scales that are expensive to resolve. Using a low-pass filtering technique, the most expensively small-scale information is removed from the numerical solution. -The HydroUQ application presently does not support either DNS or LES simulations. At present, only Reynolds Averaged Navier-Stokes (RANS) simulations are supported by the HydroUQ. If you would like to use the DNS / LES, please leave a feature request on our `message board `_. +The HydroUQ application presently does not support either DNS or LES simulations. At present, only Reynolds Averaged Navier-Stokes (RANS) simulations are supported by the HydroUQ. If you would like to use the DNS / LES, please leave a feature request on our |messageBoard|. RANS is based on the observation that the flow field contained a time-averaged state :math:`(U)` and small-local oscillations :math:`(u')`. Additional transport equation(s) are introduced for the turbulence variables and solved with the velocity and pressure. Often these can be algebraic models that depend on parameters like the velocity of the flow, distance from the wall. These models help estimate the eddy viscosity due to turbulence and is added to the molecular viscosity of the fluid. The momentum that would be transferred by the small eddies is instead translated to a viscous transport. In general, the turbulence dissipation dominates over viscous dissipation everywhere, except in the viscous sublayer close to the solid walls. Wall models help resolve the right turbulence dissipation in these sublayers. diff --git a/docs/_sources/common/technical_manual/desktop/spatial_correlation.rst.txt b/docs/_sources/common/technical_manual/desktop/spatial_correlation.rst.txt index 3ec95d79..f6a6bd62 100644 --- a/docs/_sources/common/technical_manual/desktop/spatial_correlation.rst.txt +++ b/docs/_sources/common/technical_manual/desktop/spatial_correlation.rst.txt @@ -4,7 +4,7 @@ Ground Motion Intensity Spatial Correlation Model Options ========================================================= -The regional seismic risk analysis requires the prediction of ground motion intensities at multiple sites. Such joint predictions need to consider the correlation between ground motion intensities at different sites given a specific earthquake scenario. In general, ground motion models predicting intensities at an individual site :math:`i` due to an earthquake :math:`j` have the following form: +Regional seismic risk analysis requires the prediction of ground motion intensities at multiple sites. Such joint predictions need to consider the correlation between ground motion intensities at different sites given a specific earthquake scenario. In general, ground motion models predicting intensities at an individual site :math:`i` due to an earthquake :math:`j` have the following form: .. math:: @@ -32,7 +32,7 @@ where :math:`Z_u` and :math:`Z_{u+h}` are the random variable realizations at si C(h) = E[(Z_u - \mu_Z)(Z_{u+h} - \mu_Z)] -where :math:`\mu_Z` is the mean (which is zero under the stationarity assumption). Note this spatial covariance can also be related to the semivariogram with: +where :math:`\mu_Z` is the mean (which is assumed as zero in [Jayaram08]_). Note this spatial covariance can also be related to the semivariogram with: .. math:: @@ -44,7 +44,7 @@ Similarly, the correlation coefficient is defined as: \rho(h) = \frac{C(h)}{C(0)} = 1 - \frac{\gamma(h)}{C(0)} -Given the semivariogram is often preferred in geostatistical practice (because it does not require a prior estimation of the mean), many studies were carried out to find the semivariogram models to derive the correlation :math:`rho(h)` of ground motion intensities. The available models in the current |short tool name| are briefly summarized in the following sections. +Given the semivariogram is often preferred in geostatistical practice (because it does not require a prior estimation of the mean), many studies were carried out to find the semivariogram models to derive the correlation :math:`\rho(h)` of ground motion intensities. The available models in the current |short tool name| are briefly summarized in the following sections. Jayaram and Baker (2009) ^^^^^^^^^^^^^^^^^^^^^^^^ @@ -53,29 +53,29 @@ Jayaram and Baker (2009) .. math:: - \gamma(h) = a[1 - exp(-3h / b)] + \gamma(h) = a[1 - \exp(-3h / b)] -where a and b are two modeling coefficients, namely sill and the range of the semivariogram function, respectively. When :math:`h = 0`, :math:`\gamma(h=0) = 0` which leads to :math:`\rho(h = 0) = 1`. As the distance between two sites increases, i.e., :math:`h` increases, :math:`\gamma(h)` increases and :math:`\rho(h)` decreases, which is consistent with the decaying trend of correlation between the two sites. After calibrating the model to past earthquake recordings, the following model was proposed for predicting the spatial correlation :math:`\rho(h)`: +where :math:`a` and :math:`b` are two modeling coefficients, namely sill and the range of the semivariogram function, respectively. When :math:`h = 0`, :math:`\gamma(h=0) = 0` which leads to :math:`\rho(h = 0) = 1`. As the distance between two sites increases, i.e., :math:`h` increases, :math:`\gamma(h)` increases and :math:`\rho(h)` decreases, which is consistent with the decaying trend of correlation between the two sites. After calibrating the model to past earthquake recordings, the following model was proposed for predicting the spatial correlation :math:`\rho(h)`: .. math:: - \rho(h) = exp(-3h / b) + \rho(h) = \exp(-3h / b) -The range of the semivariogram function :math:`b` was found to depend on the similarity of :math:`V_{S30}` values in the given region. If the :math:`V_{S30}` values do not show clustering, the :math:`b` is computed by: +The range of the semivariogram function :math:`b` was found to depend on the similarity of :math:`V_{S30}` values in the given region. If the :math:`V_{S30}` values do not show clustering, :math:`b` is computed by: .. math:: b = 8.5 + 17.2T, T < 1s - b = 22.0 + 3.7T, T \leq 1s + b = 22.0 + 3.7T, T \geq 1s -where T is the period. If the :math:`V_{S30}` values are very close in the given region, the :math:`b` can be computed by: +If the :math:`V_{S30}` values are very close in the given region, :math:`b` can be computed by: .. math:: b = 40.7 - 15.0T, T < 1s - b = 22.0 + 3.7T, T \leq 1s + b = 22.0 + 3.7T, T \geq 1s .. note:: @@ -84,13 +84,13 @@ where T is the period. If the :math:`V_{S30}` values are very close in the given Loth and Baker (2013) ^^^^^^^^^^^^^^^^^^^^^ -Note that the cross-semivariograms between different pairs of intensity measures can be different, for instance, :math:`\rho_{Sa(T=0.1s),Sa(T=0.2s)}(h)` might be greater than :math:`\rho_{Sa(T=0.1s), Sa(T=1s)}(h)`. This means one needs to repeat a calibration process many times to develop semivariogram functions and correlation models that have higher resolutions (i.e., direct semivariogram fit). Instead of fitting each semivariogram independently, [Loth13]_ proposed a predictive model for spatial covariance of spectral accelerations at different periods: +Note that the cross-semivariograms between different pairs of intensity measures can be different; for instance, :math:`\rho_{Sa(T=0.1s),Sa(T=0.2s)}(h)` might be greater than :math:`\rho_{Sa(T=0.1s),Sa(T=1s)}(h)`. This means one needs to repeat a calibration process many times to develop semivariogram functions and correlation models that have higher resolutions (i.e., direct semivariogram fit). Instead of fitting each semivariogram independently, [Loth13]_ proposed a predictive model for spatial covariance of spectral accelerations at different periods: .. math:: - \textbf{C}(h) = \textbf{B}^1 exp(-3h/20) + \textbf{B}^2 exp(-3h/70) + \textbf{B}^3 I_{h=0} + \textbf{C}(h) = \textbf{B}^1 \exp(-3h/20) + \textbf{B}^2 \exp(-3h/70) + \textbf{B}^3 I_{h=0} -where :math:`I_{h=0}` is the indicator function equal to 1 at :math:`h = 0` and 0 otherwise. And the three coefficient matrices :math:`\textbf{B}^1`, :math:`\textbf{B}^2`, and :math:`\textbf{B}^3` were calibrated by 2080 recordings from 8 earthquakes. +where :math:`I_{h=0}` is the indicator function equal to 1 at :math:`h = 0` and 0 otherwise. The three coefficient matrices :math:`\textbf{B}^1`, :math:`\textbf{B}^2`, and :math:`\textbf{B}^3` were calibrated by 2080 recordings from 8 earthquakes. .. figure:: figures/spatial_correlation_1.png :align: center @@ -238,7 +238,7 @@ where :math:`c_{0i}`, :math:`c_{1i}`, :math:`c_{2i}`, :math:`a_{1i}`, and :math: | 5.0 | 0.15 | 0.33 | 0.37 | 0.33 | -0.28 | 0.28 | -0.18 | -0.33 | -0.31 | 0.13 | 0.08 | -0.07 | -0.05 | -0.44 | -0.04 | 0.03 | 3.0 | 0.00 | 0.00 | +--------------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ -The general idea is to include more degrees of freedom in the predictive model if compared to linear models (e.g., [Loth13]_). The figure below contrasts the correlation coefficient functions by PCA and the linear model by [Loth13]_. +The general idea is to include more degrees of freedom in the predictive model compared to linear models (e.g., [Loth13]_). The figure below contrasts the correlation coefficient functions of PCA and the linear model by [Loth13]_. .. figure:: figures/spatial_correlation_2.png :align: center @@ -246,10 +246,9 @@ The general idea is to include more degrees of freedom in the predictive model i Comparison of principal component analysis (PCA) model and linear model of coregionalization (LMC) correlograms and cross-correlograms ([Loth13]_) for different periods - .. [Jayaram08] - Jayaram N, Baker JW. Statistical tests of the joint distribution of spectral acceleration values. Bulletin of the Seismological Society of America 2008; 98(5):2231–2243. + Jayaram, N., & Baker, J. W. (2008). Statistical tests of the joint distribution of spectral acceleration values. Bulletin of the Seismological Society of America, 98(5), 2231-2243. .. [Jayaram09] @@ -287,4 +286,4 @@ are implemented in R2D. .. [Baker08] - Baker, J. W., & Jayaram, N. (2008). Correlation of spectral acceleration values from NGA ground motion models. Earthquake Spectra, 24(1), 299-317. \ No newline at end of file + Baker, J. W., & Jayaram, N. (2008). Correlation of spectral acceleration values from NGA ground motion models. Earthquake Spectra, 24(1), 299-317. diff --git a/docs/_sources/common/user_manual/about/Hydro/HydroUQtutorial.rst.txt b/docs/_sources/common/user_manual/about/Hydro/HydroUQtutorial.rst.txt index aa79a97a..46de76bd 100644 --- a/docs/_sources/common/user_manual/about/Hydro/HydroUQtutorial.rst.txt +++ b/docs/_sources/common/user_manual/about/Hydro/HydroUQtutorial.rst.txt @@ -394,7 +394,7 @@ This tutorial will show how a **deterministic** model written/interfaced in a Py .. note:: **When running at DesignSafe (e.g. Step 3)**, SimCenter workflow uses its own Python executable installed on the cloud computer. Currently, the only supported Python packages are those installed through the 'nheri_simcenter' package. The available list of packages includes - numpy, scipy, sklearn, pandas, tables, pydoe, gpy, emukit, plotly, matplotlib. If your model uses a package beyond this list, quoFEM analysis will fail. - An option to allow user-defined Python packages on DesignSafe is under implementation. Meanwhile, if you need to request to use additional Python packages, please contact us through `user forum `_. + An option to allow user-defined Python packages on DesignSafe is under implementation. Meanwhile, if you need to request to use additional Python packages, please contact us through |messageBoard|. * **When your model consists of more than one script** @@ -404,7 +404,7 @@ This tutorial will show how a **deterministic** model written/interfaced in a Py * **Debugging** - When quoFEM analysis fails and the error message points you to a working directory, often the detailed error messages are written in ``ops.out`` file in the directory. Other ``.log`` and ``.err`` files can have information to help you identify the cause of the failure. Please feel free to ask us through `user forum `_. + When quoFEM analysis fails and the error message points you to a working directory, often the detailed error messages are written in ``ops.out`` file in the directory. Other ``.log`` and ``.err`` files can have information to help you identify the cause of the failure. Please feel free to ask us through |messageBoard|. * **When "RUN at DesignSafe" fails** @@ -424,6 +424,6 @@ This tutorial will show how a **deterministic** model written/interfaced in a Py * **Questions, bug reports, and feature requests** - We have an active `user forum `_, for any users who have questions or feature requests. The response is mostly within 24 hours and usually much less. + We have an active |messageBoard|, for any users who have questions or feature requests. The response is mostly within 24 hours and usually much less. diff --git a/docs/_sources/common/user_manual/about/Hydro/about.rst.txt b/docs/_sources/common/user_manual/about/Hydro/about.rst.txt index bbc22622..feea06e4 100644 --- a/docs/_sources/common/user_manual/about/Hydro/about.rst.txt +++ b/docs/_sources/common/user_manual/about/Hydro/about.rst.txt @@ -31,42 +31,32 @@ The additional simulations required for uncertainty quantification can be prohib .. _lblCapabilitiesAndLimitationsHydroUQ: -Capabilities and Limitations -============================ +Capabilities +============ -Below are key, modular capabilities and limitations of |short tool id|, categorized by Uncertainty Quantification (UQ), Design Building General Information (GI), Structural Information & Analysis Model (SIM), Natural Hazard Event (EVT), Engineering Demand Parameters (EDP), Finite Element Method (FEM), Random Variables (RV), and Results (RES). +Below are key, modular capabilities of |short tool id|, categorized by Uncertainty Quantification (UQ), Design Building General Information (GI), Structural Information & Analysis Model (SIM), Natural Hazard Event (EVT), Engineering Demand Parameters (EDP), Finite Element Method (FEM), Random Variables (RV), and Results (RES). .. list-table:: - :widths: 5 50 50 + :widths: 5 100 :header-rows: 1 * - Item - Capabilities - - Limitations * - UQ - Easy access to different UQ methods. Parallelized UQ algorithms. Multiple alternative algorithms for each method. - - No support for optimization under uncertainty and local sensitivity analysis. * - GI - Basic interface for user-provided general building information (e.g. location, age, and building type). - - No support for sophisticated user-defined building types. Yet to implement a map-style interface for building location so users must type in coordinates manually. * - SIM - Easy interface for user-provided structural information and analysis models (e.g. geometry, material properties, and boundary conditions). Provides a multi-degree-of-freedom (MDOF) building model. Allows for OpenSeesPy models defined in user-provided scripts. Supports investigation of multiple potential building models with associated "belief" values for each. - - Does not make full use of information (e.g. location of the building and date built influences which ASCE guidelines may have applied) provided in GI for automated structural information and analysis model generation. * - EVT - OpenFOAM computational fluid dynamics (CFD) simulations. GeoClaw Shallow-Water Equations (SWE) and OpenFOAM CFD one-way coupled simulations. FOAMySees two-way coupled CFD-FEA simulations. Material Point Method (MPM, ClaymoreUW) simulations. Pre-built and validated digital wave-flume twins. - - Most simulation types are limited to remote execution on TACC supercomputers. * - FEM - Easy interface for user-provided simulation models (not only FEM models but *any model*), including Opensees, Python, or any other simulation models (e.g. FEM or non-FEM software) with only a python-scripted interface provided by the user to HydroUQ. - - Graphical user-interface support for alternative finite element analysis (FEA) software and non-FEA software is limited. * - RV - Twelve different kinds of probability distributions with correlations. - - Does not expose which variables support this feature well to the user. No support for random fields, non-Gaussian copular, or user-defined variables. * - EDP - Scalar and vector EDP parsing. Hazard specific EDP lists (e.g. tsunami and storm-surge). Support for user-defined EDPs. - - Separate Intensity Measures (IMs) and EDPs (load and response), in functionality and GUI presentation, is not fully delineated yet. * - RES - Interactive plotting of scatter charts, histograms, and cumulative mass functions. Summary of statistics. Save data into a CSV file. - - Limited flexibility for in-app visualization. Results must be ported to external plotting software for more advanced visualization. * - General - Graphical user interface. Free and easy one-click remote running option. - - Limited guidance on how to effectively contribute to this open-source project. diff --git a/docs/_sources/common/user_manual/examples/desktop/hdro-0001/README.rst.txt b/docs/_sources/common/user_manual/examples/desktop/hdro-0001/README.rst.txt index f9109caa..aaa78f97 100644 --- a/docs/_sources/common/user_manual/examples/desktop/hdro-0001/README.rst.txt +++ b/docs/_sources/common/user_manual/examples/desktop/hdro-0001/README.rst.txt @@ -1,30 +1,36 @@ .. _hdro-0001: -Coupled Digital Twin Example -============================ +============================================================= +Multi-Story Shear Building - Coupled CFD-FEM Digital Twin +============================================================= -+---------------+----------------------------------------------+ -| Problem files | :github:`Github ` | -+---------------+----------------------------------------------+ ++---------------+----------------------------------------------------------------+ +| Problem files | :github:`HydroUQ Github Repository` | ++---------------+----------------------------------------------------------------+ -Outline -------- -This example uses a NHERI wave-flume digital twin, the OSU LWF, to simulate a scaled structure during wave loading in HydroUQ. Two-way coupled OpenFOAM-OpenSees is configured to simulate the scenario. +.. _hdro-0001-overview: -You will define a Waterborne Event (EVT) to determine the engineering demand parameters (EDP) on a specified structure, i.e. EVT --> EDP, with the following steps: +Overview +-------- +This example uses a NHERI wave-flume digital twin, the ``OSU LWF``, to simulate a scaled structure during wave loading in ``HydroUQ``. Two-way coupled OpenFOAM-OpenSees is configured to simulate the scenario. -1. Configure a FOAMySees simulation. This is a two-way coupling of OpenFOAM Finite Volume Method (FVM) for Computational Fluid Dynamics (CFD) and OpenSees Finite Element Analaysis (FEA) for Computational Structural Dynamics (CSD). +You will define a Waterborne Event (**EVT**) to determine the engineering demand parameters (**EDP**) on a specified structure, i.e. **EVT** --> **EDP**, with the following steps: -2. Next, the coupled model will determine floor loads on the building, also known as intensity measures (IM) in performance based engineering (PBE). +#. Configure a FOAMySees simulation event (**EVT**). This is a two-way coupling of OpenFOAM Finite Volume Method (FVM) for Computational Fluid Dynamics (CFD) and OpenSees Finite Element Analaysis (FEA) for Computational Structural Dynamics (CSD). -3. Then, perform an OpenSees finite element analysis (FEA) simulation of the building by taking IMs as inputs. +#. Next, the coupled model will determine floor loads on the building, also known as intensity measures (**IM**) in common performance-based engineering (PBE) nomenclature. -4. Finally, recieve engineering demand parameters (EDP) of the structural response. Though beyond this example, you can use these EDPs to perform a fragility analysis of the structure. +#. Then, perform an OpenSees finite element analysis (**FEM**) simulation of the building by taking IMs as inputs. +#. Finally, recieve engineering demand parameters (**EDP**) of the structural response. Though beyond this example, you can use these EDPs to perform a fragility analysis of the structure. -Data ----- -The dataset used presented in this example originates from experimental tests conducted in the Hinsdale Wave Research Laboratory's Large Wave Flume at Oregon State University (OSU LWF), Corvallis, in 2020. Refer to Lewis 2023 [Lewis2023]_ and Bonus 2023 [Bonus2023]_ for details. + +.. _hdro-0001-setup: + +Set-Up +------ + +The dataset in this example originates from experimental tests conducted in the Hinsdale Wave Research Laboratory's Large Wave Flume at Oregon State University (``OSU LWF``), Corvallis, in 2020. Refer to Lewis 2023 [Lewis2023]_ and Bonus 2023 [Bonus2023]_ for details. .. _figCoupled: @@ -35,27 +41,27 @@ The dataset used presented in this example originates from experimental tests co Coupled Digital Twin Illustration + Model ------ +^^^^^ This model is characterized by the parameters: -- Youngs modulus :math:`E_0`for elastic behavior, -- Initial yield stress and strain hardening ratio :math:`(f_y, b)` for plastic behavior, - -Files required --------------- +* Structural weight, :math:`w`, in kN as a random variable with a mean of 100 kN and a standard deviation of 10 kN. +^ .. warning:: - Do NOT place the files in your root, downloads, or desktop folder as when the application runs it will copy the contents on the directories and subdirectories containing these files multiple times. If you are like us, your root, Downloads or Documents folders contain a lot of files. + **Do NOT** place the files in your ``root``, ``downloads``, or ``desktop`` folder. The running application will copy every unrelated file in the directories and subdirectories multiple times. -UQ workflow ------------ -The inputs needed to run this example can be loaded into the HydroUQ user interface by selecting the ``Coupled Digital Twin`` example from the ``Examples`` menu. +Workflow +^^^^^^^^^^^ + +The inputs needed to run this example can be loaded into the HydroUQ user interface by selecting the ``Coupled Digital Twin`` example from the ``Examples`` menu at the top of the application. The inputs can also be set up manually through the following steps: -1. Start the application and the **UQ** panel will be highlighted. In the **UQ Method** drop-down menu, select the **Bayesian Calibration** option. In the **UQ Engine** dropdown menu select **UCSD-UQ** option. In the **Model** dropdown, select the **Hierarchical** option. Enter the values in this panel as shown in the figure below. A brief explanation of the different user input fields can be found in the :ref:`User Manual `. +#. Start the application and select the **UQ** panel: + In the **UQ Method** drop-down menu, select the **Bayesian Calibration** option. In the **UQ Engine** dropdown menu select **UCSD-UQ** option. In the **Model** dropdown, select the **Hierarchical** option. Enter the values in this panel as shown in the figure below. A brief explanation of the different user input fields can be found in the :ref:`User Manual `. .. _figHBMUQ: @@ -66,18 +72,20 @@ The inputs can also be set up manually through the following steps: Inputs in the UQ panel -2. Next in the **FEM** panel , select **OpenSees** and populate the **Input Script** field by choosing the path to the model file. +#. Next in the **FEM** panel: + Select **OpenSees** and populate the **Input Script** field by choosing the path to the model file. -.. .. _figHBMFEM: +.. _figHBMFEM: -.. .. figure:: figures/FEM.png -.. :align: center -.. :figclass: align-center -.. :width: 600 +.. figure:: figures/FEM.png + :align: center + :figclass: align-center + :width: 600 -.. Inputs in the FEM panel + Inputs in the FEM panel -3. Select the **RV** tab from the input panel. This panel should be pre-populated with the names of the variables that were defined in the model scripts. If not, press the **Add** button to create a new field to define the input random variable. Enter the same variable name, as required in the model script. For this example, choose the Normal probability distribution for all the random variables and enter the parameter values for each distribution as shown in the figures below: +#. Select the **RV** tab from the input panel: + This panel should be pre-populated with the names of the variables that were defined in the model scripts. If not, press the **Add** button to create a new field to define the input random variable. Enter the same variable name, as required in the model script. For this example, choose the Normal probability distribution for all the random variables and enter the parameter values for each distribution as shown in the figures below: .. _figHBMRV: @@ -103,7 +111,8 @@ The inputs can also be set up manually through the following steps: .. Inputs in the RV panel -4. In the **EDP** panel create the output quantities corresponding to each of the experiments with a descriptive name, as shown in the figures below: +#. In the **EDP** panel: + Create the output quantities corresponding to each of the experiments with a descriptive name, as shown in the figures below: .. .. _figHBMEDP1: @@ -122,9 +131,14 @@ The inputs can also be set up manually through the following steps: .. Inputs in the EDP panel -5. Click on the **Run** button. This will create the necessary input files to perform a Bayesian calibration of the hierarchical model, run the analysis, and display the results when the analysis is completed. The results produced are sample values drawn from the distribution that represents the aleatory uncertainty in the estimated material parameters from each of the datasets. +#. Click on the **Run** button. + This will create the necessary input files to perform a Bayesian calibration of the hierarchical model, run the analysis, and display the results when the analysis is completed. + +#. The **RES** tab will open with the workflow results when the simulation completers. The results produced are sample values drawn from the distribution that represents the aleatory uncertainty in the estimated material parameters from each of the datasets. + + The **Summary** tab shows the mean, standard deviation, and coefficient of variation of each of the seven parameters of the material model that were inferred in this example. -The **Summary** tab shows the mean, standard deviation, and coefficient of variation of each of the seven parameters of the material model that were inferred in this example. + In the **Data Values** tab of the **RES** panel, a chart and a table with all the sample values are shown. By clicking on the data inside the columns of the chart with the **left** or **right** mouse button (``M1`` and ``M2``), different chart types are created and shown in the chart area on the left. .. .. _figHBMRES1: @@ -140,10 +154,9 @@ The **Summary** tab shows the mean, standard deviation, and coefficient of varia .. :figclass: align-center .. :width: 600 - Results in the RES panel summary tab +.. Results in the **RES** panel summary tab -In the **Data Values** tab of the **RES** panel, a chart and a table with all the sample values are shown. By clicking on the data inside the columns of the chart with the left or right mouse button, different chart types are created and shown in the chart area on the left. .. .. _figHBMRES3: @@ -164,13 +177,18 @@ In the **Data Values** tab of the **RES** panel, a chart and a table with all th .. _lblHBMRestart: -Files for restarting the analysis ---------------------------------- - -In addition to the results displayed in the RES panel in HydroUQ, JSON files with the state of the chain at every step of the sampling algorithm are saved in a directory called ``sampling_results`` within the ``tmp.SimCenter`` directory inside the jobs directory specified in the HydroUQ Preferences menu. Any of these files can be used to resume the sampling, by copying the file to the directory containing the model files and specifying its name in the Restart File Name field in the UQ panel. +.. info:: + In addition to the results displayed in the **RES** panel in ``HydroUQ``, JSON files with the state of the chain at every step of the sampling algorithm are saved in a directory called ``sampling_results`` within the ``tmp.SimCenter`` directory inside the jobs directory specified in the ``HydroUQ`` Preferences menu. + Any of these files can be used to resume the sampling, by copying the file to the directory containing the model files and specifying its name in the Restart File Name field in the **UQ** panel. .. warning:: - The ``tmp.SimCenter`` directory is cleared every time the ``RUN`` button is clicked in HydroUQ. So, if you want to restart the analysis using one of the sampling results files outlined above, make sure to copy the results file to a location outside the ``tmp.SimCenter`` directory at the end of the analysis. + The ``tmp.SimCenter`` directory is cleared every time the ``RUN`` button is clicked in ``HydroUQ``. So, if you want to restart the analysis using one of the sampling results files outlined above, make sure to copy the results file to a location outside the ``tmp.SimCenter`` directory at the end of the analysis. + + +.. _hdro-0001-references: + +References +---------- .. [Lewis2023] Lewis, N. (2023). Development of An Open-Source Methodology for Simulation of Civil Engineering Structures Subject to Multi-Hazards. *PhD thesis*, University of Washington, Seattle, WA. ISBN: 979-8-381408-69-0. diff --git a/docs/_sources/common/user_manual/examples/desktop/hdro-0002/README.rst.txt b/docs/_sources/common/user_manual/examples/desktop/hdro-0002/README.rst.txt index cad40e75..803535cd 100644 --- a/docs/_sources/common/user_manual/examples/desktop/hdro-0002/README.rst.txt +++ b/docs/_sources/common/user_manual/examples/desktop/hdro-0002/README.rst.txt @@ -37,9 +37,9 @@ Experiments were performed in the NHERI OSU LWF, a 100 meter long flume with adj :width: 600 :figclass: align-center - NHERI OSU LWF facilty's experimental schematic used in this example. Adapted from Winter 2019 [Winter2019]_, and Mascarenas 2022 [Mascarenas2022]_. + NHERI OSU LWF facility's experimental schematic is used in this example. Adapted from Winter 2019 [Winter2019]_, and Mascarenas 2022 [Mascarenas2022]_. -This example may help to produce a robust database (numerical and physical) from which to eventually be able to extract both the first-principals of wave-driven debris-field phenomena and design guidelines on induced forces. +This example may help to produce a robust database (numerical and physical) from which to eventually be able to extract both the first principles of wave-driven debris-field phenomena and design guidelines on induced forces. We validate against two very similar (but not identical) physical studies done in the OSU LWF by [Shekhar2020]_ and [Mascarenas2022]_, indicating high accuracy of our model and low bias to minor experiment specifications. @@ -64,7 +64,7 @@ It appears similar in the mechanism of debris impact, stalling, and deflection r OSU LWF debris impact photos from Mascarenas 2022 [Mascarenas2022]_ experiments. -The experiments by Shekhar et al. 2020 [Shekhar2020]_ are also shown below for comparison. These tests had a slightly different configuartion, primarily the debris were located 0.5 meters further upstream from the box and the water level was 0.10-0.15 meters lower than the 2.0 meter datum used in the simulations and Mascarenas 2022 [Mascarenas2022]_ experiments. +The experiments by Shekhar et al. 2020 [Shekhar2020]_ are also shown below for comparison. These tests had a slightly different configuration, primarily the debris were located 0.5 meters further upstream from the box and the water level was 0.10-0.15 meters lower than the 2.0 meter datum used in the simulations and Mascarenas 2022 [Mascarenas2022]_ experiments. .. figure:: figures/OSU_LWF_Krish_Debris_8L_3Panel_Impacts_Photograph_Shekhar2020.PNG :align: center @@ -121,7 +121,7 @@ Open ``Algorithm``. Here we set the algorithm parameters for the simulation. We HydroUQ Bodies Fluid Algorithm GUI -Open ``Bodies`` / ``Fluid`` / ``Partitions``. Here we set the number of partitions for the simulation. This is the domain decomposition across discrete hardware units, i.e. Multi-GPUs. These may be kept as there default values. +Open ``Bodies`` / ``Fluid`` / ``Partitions``. Here we set the number of partitions for the simulation. This is the domain decomposition across discrete hardware units, i.e. Multi-GPUs. These may be kept as their default values. .. figure:: figures/GUI_Bodies_Fluid_Partitions.PNG :align: center @@ -130,7 +130,7 @@ Open ``Bodies`` / ``Fluid`` / ``Partitions``. Here we set the number of partitio HydroUQ Bodies Fluid Partitions GUI -Moving onto the creation of an ordered debris-array, we set the debris properties in the ``Bodies`` / ``Debris`` / ``Material`` tab. We will assume debris are made of HDPE plastic, as in experiments by Mascarenas 2022 [Mascarenas2022]_ and Shekhar et al. 2020 [Shekhar2020]_. +Moving onto the creation of an ordered debris array, we set the debris properties in the ``Bodies`` / ``Debris`` / ``Material`` tab. We will assume debris are made of HDPE plastic, as in experiments by Mascarenas 2022 [Mascarenas2022]_ and Shekhar et al. 2020 [Shekhar2020]_. .. figure:: figures/GUI_Bodies_Debris_Material.PNG :align: center @@ -148,7 +148,7 @@ Open ``Bodies`` / ``Debris`` / ``Geometry``. Here we set the debris properties, HydroUQ Bodies Debris Geometry GUI -The ``Bodies`` / ``Debris`` / ``Algorithm`` and ``Debris`` / ``Partitions`` tabs are not used in this example, but are available for more advanced users. +The ``Bodies`` / ``Debris`` / ``Algorithm`` and ``Debris`` / ``Partitions`` tabs are not used in this example but are available for more advanced users. Open ``Bodies`` / ``Structures``. Uncheck the box that enables this body, if it is checked. We will not model the structure as a body in this example, instead, we will modify it as a boundary later. @@ -159,7 +159,7 @@ Open ``Bodies`` / ``Structures``. Uncheck the box that enables this body, if it HydroUQ Bodies Structures GUI -Open ``Boundaries`` / ``Wave Flume``. We will set the boundary to be a rigid body, with a fixed separable velocity condition, that is faithful to the digital tiwn of the NHERI OSU LWF. Bathmyetry joint points should be indetical to the ones used in ``Bodeis`` / ``FLuid``. +Open ``Boundaries`` / ``Wave Flume``. We will set the boundary to be a rigid body, with a fixed separable velocity condition, that is faithful to the digital twin of the NHERI OSU LWF. Bathmyetry joint points should be identical to the ones used in ``Bodeis`` / ``FLuid``. .. figure:: figures/GUI_Boundaries_Flume.PNG :align: center @@ -168,7 +168,7 @@ Open ``Boundaries`` / ``Wave Flume``. We will set the boundary to be a rigid bod HydroUQ Boundaries Wave Flume Facility GUI -Open ``Boundaries`` / ``Wave Generator``. Fill in the appropriate file-path for the wave generator paddle motion. It is designed to produce near-solitary like waves. +Open ``Boundaries`` / ``Wave Generator``. Fill in the appropriate file-path for the wave generator paddle motion. It is designed to produce near-solitary-like waves. .. figure:: figures/GUI_Boundaries_WaveGenerator.PNG :align: center @@ -177,7 +177,7 @@ Open ``Boundaries`` / ``Wave Generator``. Fill in the appropriate file-path for HydroUQ Boundaries Wave Generator GUI -Open ``Boundaries`` / ``Rigid Structure``. This is where we will specify the raised structure as a boundary condition. By doing so, we can determine exact loads on the rigid boundary grid-nodes, which may then be mapped to the FEM tab for nonlinear UQ structural response analysis. +Open ``Boundaries`` / ``Rigid Structure``. This is where we will specify the raised structure as a boundary condition. By doing so, we can determine the exact loads on the rigid boundary grid-nodes, which may then be mapped to the FEM tab for nonlinear UQ structural response analysis. .. figure:: figures/GUI_Boundaries_RigidStructure.PNG :align: center @@ -197,7 +197,7 @@ Open ``Boundaries`` / ``RigidWalls``. Open ``Sensors`` / ``Wave Gauges``. Set the ``Use these sensor?`` box to ``True`` so that the simulation will output results for the instruments we set on this page. -Three wave gauges will be defined. The first is located prior to the bathymetry ramps, the second partially up the ramps, and the third near the the bathymetry crest, debris, and raised structure. +Three wave gauges will be defined. The first is located prior to the bathymetry ramps, the second partially up the ramps, and the third near the bathymetry crest, debris, and raised structure. Set the origins and dimensions of each wave as in the table below. To match experimental conditions, we also apply a 120 Hz sampling rate to the wave gauges, meaning they record data every 0.0083 seconds. @@ -208,7 +208,7 @@ Set the origins and dimensions of each wave as in the table below. To match expe HydroUQ Sensors Wave-Gauge GUI -These wave gauges will read all numerical bodies (i.e. particles) within their defined regions every sampling step, and will report the highest elevation value (Position Y) of a contained body as the free-surface elevation at that gauge. The results is written into our sensor results files. +These wave gauges will read all numerical bodies (i.e. particles) within their defined regions at every sampling step and will report the highest elevation value (Position Y) of a contained body as the free-surface elevation at that gauge. The results are written into our sensor results files. Open ``Sensors`` / ``Load Cells``. Set the ``Use these sensor?`` box to ``True`` so that the simulation will output results for the instruments we set on this page. @@ -221,7 +221,7 @@ Open ``Sensors`` / ``Load Cells``. Set the ``Use these sensor?`` box to ``True`` HydroUQ Sensors Load-Cells GUI -Open ``Outputs``. Here we set the non-physical output parameters for the simulation, e.g. attributes to save per frame and file extension types. The particle bodies' output frequency is set to 10 Hz (0.1 seconds), meaning the simulation will output results every 0.1 seconds. This is decent for animations without taking too much space. Fill in the rest of the data in the figure into your GUI to ensure all your outputs match this example. +Open ``Outputs``. Here we set the non-physical output parameters for the simulation, e.g. attributes to save per frame and file extension types. The particle bodies' output frequency is set to 10 Hz (0.1 seconds), meaning the simulation will output results every 0.1 seconds. This is decent for animations without taking up too much space. Fill in the rest of the data in the figure into your GUI to ensure all your outputs match this example. .. figure:: figures/GUI_Outputs.PNG :align: center @@ -237,17 +237,17 @@ Open ``Outputs``. Here we set the non-physical output parameters for the simulat Simulation ---------- -We assume that 2 hours are reserved for your simulation. For those using the reduce fluid bulk modulus or reduced resolution, this may be more than neccesary. +We assume that 2 hours are reserved for your simulation. For those using the reduce fluid bulk modulus or reduced resolution, this may be more than necessary. -This simulation was ran on the TACC Lonestar6 system. It uesd three NVIDIA A100 GPUs on a single node in the ``gpu-a100`` queue. Real time to complete was 2 hours. Simulated time in the digital twin is 26 seconds. +This simulation was run on the TACC Lonestar6 system. It uses three NVIDIA A100 GPUs on a single node in the ``gpu-a100`` queue. The real-time to complete was 2 hours. The simulated time in the digital twin is 26 seconds. -In order to retrieve results from the analysis, the analysis must complete and postprocess the model output files into an appropriate format before the end of the allotted submission time. +To retrieve results from the analysis, the analysis must complete and post-process the model output files into an appropriate format before the end of the allotted submission time. .. important:: Provide a large amount of time for the ``Max Run Time`` field in HydroUQ when submitting a job to ensure the model completes before the time allotted runs out! We recommend 2 hours in this example. .. warning:: - Only ask for what you need in terms of sensor size, count, and output sampling rate. Otherwise you will end up with massive amounts of data which can slow simulations due to I/O constraints. + Only ask for what you need in terms of sensor size, count, and output sampling rate. Otherwise, you will end up with massive amounts of data which can slow simulations due to I/O constraints. .. _hdro-0002-analysis: @@ -255,7 +255,7 @@ In order to retrieve results from the analysis, the analysis must complete and p Analysis -------- -When the simulation job has completed, the results will be available on the remote system for retrieval or remote post-processing. +When the simulation job has been completed, the results will be available on the remote system for retrieval or remote post-processing. Retrieving the ``results.zip`` folder from the ``Tools & Applications`` Page of Design Safe starts by navigating to the designsafe-ci.org website. Login and go to ``Use DesignSafe`` / ``Tools & Applications`` @@ -320,13 +320,13 @@ Extract the ``results.zip`` folder either on DesignSafe or on your local machine File-system view of results zip folder on DesignSafe. -Locate the zip folder and extract it somewhere convenient. The local or remote work directory on your computer is a good option, but note that these files may be erased if another simulation is set-up in HydroUQ, so keep a backup somewhere outside the working directories. +Locate the zip folder and extract it somewhere convenient. The local or remote work directory on your computer is a good option, but note that these files may be erased if another simulation is set up in HydroUQ, so keep a backup somewhere outside the working directories. -HydroUQ's sensor / probe / instrument output is available in ``{your_path_to_HydroUQ_WorkDir}/HydroUQ/RemoteWorkDir/results/`` as ``CSV`` files. +HydroUQ's sensor/probe/instrument output is available in ``{your_path_to_HydroUQ_WorkDir}/HydroUQ/RemoteWorkDir/results/`` as ``CSV`` files. Particle geometry files often have a ``BGEO`` extension, open Side FX Houdini Apprentice (free to use) to look at MPM results in high-detail. -Once complete, the simulation data at the three wave gauges (WG1, WG2, and WG3, left-to-right) is as showm below when plotted against experimental trials of Mascarenas 2022 [Mascarenas2022]_ for the "unbroken" solitary wave case. +Once complete, the simulation data at the three wave gauges (WG1, WG2, and WG3, left-to-right) is as shown below when plotted against experimental trials of Mascarenas 2022 [Mascarenas2022]_ for the "unbroken" solitary wave case. .. figure:: figures/OSU_LWF_Wave_Gauges_Hydro_2D_Plots3_2023.10.31.png :align: center @@ -346,9 +346,9 @@ The simulation data at the load-cell is as shown below when plotted against expe OSU LWF simulated streamwise load-cells vs. experimental data from Mascarenas 2022 [Mascarenas2022]_. -Though only one case was considered here, if many experimental debris-field cases are ran (10+) we can use HydroUQ to perform a sensitivity analysis on the debris-field parameters. This isn't pursued here-in. +Though only one case was considered here, if many experimental debris-field cases are run (10+) we can use HydroUQ to perform a sensitivity analysis on the debris-field parameters. This isn't pursued here-in. -However, the following box-and-whisker charts demonstrates the strengh of the numerical replication, as most points fall within experimental interquartile ranges and never outside of the experimental envelope for impact loads. +However, the following box-and-whisker charts demonstrate the strength of the numerical replication, as most points fall within experimental interquartile ranges and never outside of the experimental envelope for impact loads. .. figure:: figures/OSU_U_FirstPeak_BoxAndWhiskers_KrishExpOnly_31072023.png :align: center diff --git a/docs/_sources/common/user_manual/examples/desktop/hdro-0003/README.rst.txt b/docs/_sources/common/user_manual/examples/desktop/hdro-0003/README.rst.txt index 17ffc42d..061b6357 100644 --- a/docs/_sources/common/user_manual/examples/desktop/hdro-0003/README.rst.txt +++ b/docs/_sources/common/user_manual/examples/desktop/hdro-0003/README.rst.txt @@ -18,12 +18,12 @@ Cylinder Half-Submerged in Flow - UW WASIRF Twin - FOAMySees (OpenFOAM + Ope Overview -------- -This example demonstrates how to run a coupled **OpenSees-OpenFOAM** simulation (**FOAMySees**) to determine floor loads on a building caused by strongly-coupled, two-way fluid-structure interaction. +This example demonstrates how to run a coupled **OpenSees-OpenFOAM** simulation (**FOAMySees**) to determine floor loads on a building caused by strongly coupled, two-way fluid-structure interaction. You can then perform an **OpenSees** simulation of the building assuming uncertainties in the building properties. A truncated digital twin of the UW WASIRF wave flume contains a simple cantilevered cylinder. The cylinder, our structure, is half-submerged. The flow around the cylinder is calculated for a given period of time in order to determine a simulated structural response time-series under wave loading. -Outputs of the **EVT** simulation will include results, sampled at specified frequenies, for the: +Outputs of the **EVT** simulation will include results, sampled at specified frequencies, for the: #. Fluid flow's free surface elevation at wave gauges #. Flow velocity at velocimeter locations @@ -38,7 +38,7 @@ As the **EVT** and **FEM** functionality are effectively fused for FOAMySees, th The **EDP** tab will then process these results. #. Displacement of the cylinder tip from rest, peak relative-floor displacement (PFD) -#. Displacement of the cylinder tip relative to its base or supporting , peak inter-story drift (PID) +#. Displacement of the cylinder tip relative to its base or supporting, peak inter-story drift (PID) #. Peak floor acceleration (PFA) @@ -105,18 +105,18 @@ Simulation time for 1 second in the digital flume took 1 hour and 20 minutes. Th The case can be run for as long as desired, but mind that the longer the case runs, the longer the postprocessing routines will be. -In order to retrieve results from the analysis, the job must complete and postprocess the model output files into a VTK format before the end of the allotted submission time. +In order to retrieve results from the analysis, the job must complete and post-process the model output files into a VTK format before the end of the allotted submission time. .. important:: Provide a large amount of time for the *Max Run Time* field in HydroUQ when submitting a job to ensure the model completes before the time allotted runs out! .. note:: - Be aware that the smaller the OpenFOAM Outputs and OpenSees Outputs *Time Interval* value is, the longer the post processing of the case will take after analysis has completed, + Be aware that the smaller the OpenFOAM Outputs and OpenSees Outputs *Time Interval* value is, the longer the post-processing of the case will take after analysis has been completed, and the larger the ``results.zip`` folder will be. .. warning:: Be modest when requesting simulation outputs across many recording probes or full geometry snapshots. - Only ask for what you need, or your simulation will become slow due to I/O constraints and the output data will be too large to effecitvely post-process or host on your local machine. + Only ask for what you need, or your simulation will become slow due to I/O constraints and the output data will be too large to effectively post-process or host on your local machine. @@ -142,7 +142,7 @@ Check if the job has finished. If it has, click 'More info'. :width: 600 :figclass: align-center - Once the job is finished, the output files should be available in the directory which the analysis results were sent to + Once the job is finished, the output files should be available in the directory to which the analysis results were sent to Find the files by clicking 'View'. diff --git a/docs/_sources/common/user_manual/examples/desktop/hdro-0004/README.rst.txt b/docs/_sources/common/user_manual/examples/desktop/hdro-0004/README.rst.txt index af68604b..ddcee661 100644 --- a/docs/_sources/common/user_manual/examples/desktop/hdro-0004/README.rst.txt +++ b/docs/_sources/common/user_manual/examples/desktop/hdro-0004/README.rst.txt @@ -1,43 +1,39 @@ .. _hdro-0004: +=============================================================================== Tsunami Debris Motion Through a Scaled Port Setting - WU TWB Digital Twin - MPM -============================ +=============================================================================== +---------------+----------------------------------------------+ | Problem files | :github:`Github ` | +---------------+----------------------------------------------+ -Outline -------- -Example to demonstrate how to run a MPM simulation to determine floor loads on a building and then perform -an OpenSees simulation of the building assuming uncertainties in the building properties. - -The flume is 1 meter wide (from Y=-0.5m to Y=0.5 m), 1 meter tall (Z=0.0m to Z=1.0m), and 4 meters long (X=0.0m to X=4.0m). +.. contents:: Table of Contents + :local: + :backlinks: none -The case is initialized with a still water level of 0.25 meters. The velocity at the inlet is given a time history boundary condition (src/VelTime.csv). +.. _hdro-0004-overview: -This structure is a simple cylinder, with diameter 0.1 meters, located at X=1.5, Y=0.0, Z=0.0. The interface surface file is 'src/interface.stl'. - -The cylinder is represented in OpenSees by a cantilevered beam, with an elastic section, modelled with displacement-action controlled beam elements. The bottom of the cantilevered beam is fixed at Z=0.0. +Outline +------- -The constrained node is removed from the coupled solution, by omitting it from the list 'coupledNodes' in the OpenSees model file. +Example to demonstrate how to run a MPM simulation to determine loads on an array of port buildings during a tsunami with respect to debris impacts and damming. After, we perform +an OpenSees simulation of one building assuming uncertainties in the building properties. -The length of the cylinder is 0.5 meters. +The Waseda University Tsunami Wave Basin (WU TBW) flume is 4 meters wide (from X=-2m to X=2 m), 1 meter tall (Z=0.0m to Z=1.0m), and 9 meters long (Y=0.0m to Y=9.0m). -The flow around the cylinder is calculated for a given period of time. +The case is initialized with a still water level of 0.23 meters. -Outputs: -Results for free surface, velocity, and pressure, as well as interface forces and moments and a cut section of the case at a specified interval. +Results for free surface, velocity, and pressure, as well as structural load forces, are output at a specified interval to match experimental instruments. -Simulation of MPM debris impacts on one row of five obstacles .. figure:: figures/TOKYO_BoreFrontImage_Debris3_o5x1_Frame20_29072023.png :align: center :width: 600 :figclass: align-center - -Schematic of the flume and sensor locations + + Simulation of MPM debris impacts on one row of five obstacles .. figure:: figures/B4_Flume_Schematic.png @@ -45,24 +41,23 @@ Schematic of the flume and sensor locations :width: 600 :figclass: align-center + Schematic of the flume and sensor locations -Smart debris used in experiments .. figure:: figures/B4_Debris_Picture.PNG :align: center :width: 600 :figclass: align-center + Smart debris used in experiments -CASE RUN TIME ---------------- -Simulation Time: 6 seconds - Ran on TACC Lonestar6, 56 processors, 3 NVIDIA A100 GPUs, 1 node -> Real Time: 1hr, 20 minutes +.. _hdro-0004-simulation: + +Simulation +---------- -Submitted -Oct 8, 2023 1:14:37 PM -Finished -Oct 8, 2023 2:34:10 PM +Simulation Time: 6 seconds - Ran on TACC Lonestar6, 56 processors, 3 NVIDIA A100 GPUs, 1 node -> Real Time: 1hr, 20 minutes The case can be run for as long as desired, but mind that the longer the case runs, the longer the postprocessing routines will be. @@ -70,13 +65,17 @@ In order to retrieve results from the analysis, the analysis must complete and p Provide a large amount of time for the 'Max Run Time' field in HydroUQ when submitting a job to ensure the model completes before the time allotted runs out! -Be aware that the smaller the OpenFOAM Outputs and OpenSees Outputs 'Time Interval' value is, the longer the post processing of the case will take after analysis has completed, and the larger the results.zip folder will be. +Be aware that the smaller the OpenFOAM Outputs and OpenSees Outputs 'Time Interval' value is, the longer the post-processing of the case will take after analysis has been completed, and the larger the results.zip folder will be. + +.. warning:: + Use caution when requesting sensors and using high sampling rates. Only ask for what you need, or you will end up with massive amounts of data. -USE CAUTION WHEN REQUESTING OUTPUT! Only ask for what you need, or you will end up will massive amounts of data. -Post Processing -------------------------------------------------------------------- +.. _hdro-0004-analysis: + +Analysis +-------- Retrieving the results.zip folder from the Tools and Applications Page of Design Safe.. @@ -84,7 +83,8 @@ Retrieving the results.zip folder from the Tools and Applications Page of Design :align: center :width: 600 :figclass: align-center - Locating the job files on DesignSafe + + Locating the job files on DesignSafe Check if the job has finished. If it has, click 'More info'. @@ -92,7 +92,8 @@ Check if the job has finished. If it has, click 'More info'. :align: center :width: 600 :figclass: align-center - Once the job is finished, the output files should be available in the directory which the analysis results were sent to + + Once the job is finished, the output files should be available in the directory to which the analysis results were sent Find the files by clicking 'View'. @@ -100,7 +101,8 @@ Find the files by clicking 'View'. :align: center :width: 600 :figclass: align-center - Locating this directory is easy. + + Locating this directory is easy. Move the results.zip to somewhere in My Data/. Use the Extractor tool available on DesignSafe. Unzip the results.zip folder. @@ -117,7 +119,8 @@ OR Download the results.zip folder to your PC and unzip to look at the model res :align: center :width: 600 :figclass: align-center - Download the results to look at the VTK files of the analysis. This will include OpenFOAM and OpenSees field data and model geometry + + Download the results to look at the VTK files of the analysis. This will include OpenFOAM and OpenSees field data and model geometry Extract the Zip folder either on DesignSafe or on your local machine. You will need Paraview to view the model data. @@ -125,101 +128,117 @@ Extract the Zip folder either on DesignSafe or on your local machine. You will n :align: center :width: 600 :figclass: align-center - Locate the zip folder and extract it to somewhere convenient - -The results folder should look something like this. - -.. figure:: figures/results.png - :align: center - :width: 600 - :figclass: align-center - This is the output of the model - -Paraview files have a .PVD extension. Open VTK/Fluid.vtm.series to look at OpenFOAM results. -Open OpenSeesOutput.pvd to look at OpenSees results. - -.. figure:: figures/Paraview.PNG - :align: center - :width: 600 - :figclass: align-center - This is the model output data as seen from ParaView - -OpenSees Displacements And Reactions - - -.. figure:: figures/TipDisplacement.png - :align: center - :width: 600 - :figclass: align-center - This is the model output data as seen from ParaView - -.. figure:: figures/ReactionForces.png - :align: center - :width: 600 - :figclass: align-center - This is the model output data as seen from ParaView + + Locate the zip folder and extract it to somewhere convenient -OpenFOAM probe and function object output is available in results/postProcessing/. - -OpenFOAM output is messy. An example Matlab script is provided in the /src/ directory to post process the OpenFOAM output for this particular case and output. -This file can be modified to work for any case. The names of the data folders will need to be changed according to the name of the probe given in HydroUQ. - -.. figure:: figures/MatlabScriptCopyToLocation.PNG - :align: center - :width: 600 - :figclass: align-center - In the /src/ folder in the hdro-0004 folder, an example matlab script is provided to look at time history data of the output probes +.. The results folder should look something like this. +.. .. figure:: figures/results.png +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. This is the output of the model -OpenFOAM Calculated Story Forces - -.. figure:: figures/storyForces.png - :align: center - :width: 600 - :figclass: align-center - Story Forces +.. Paraview files have a .PVD extension. Open VTK/Fluid.vtm.series to look at OpenFOAM results. +.. Open OpenSeesOutput.pvd to look at OpenSees results. + +.. .. figure:: figures/Paraview.PNG +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. This is the model output data as seen from ParaView + +.. OpenSees Displacements And Reactions + +.. .. figure:: figures/TipDisplacement.png +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. This is the model output data as seen from ParaView + +.. .. figure:: figures/ReactionForces.png +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. This is the model output data as seen from ParaView + + +.. OpenFOAM probe and function object output is available in results/postProcessing/. + +.. OpenFOAM output is messy. An example Matlab script is provided in the /src/ directory to post process the OpenFOAM output for this particular case and output. +.. This file can be modified to work for any case. The names of the data folders will need to be changed according to the name of the probe given in HydroUQ. + +.. .. figure:: figures/MatlabScriptCopyToLocation.PNG +.. :align: center +.. :width: 600 +.. :figclass: align-center +.. In the /src/ folder in the hdro-0004 folder, an example matlab script is provided to look at time history data of the output probes -OpenFOAM Calculated Coupled Interface Forces - -.. figure:: figures/Forces.png - :align: center - :width: 600 - :figclass: align-center - Forces + +.. OpenFOAM Calculated Story Forces + +.. .. figure:: figures/storyForces.png +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. Story Forces + +.. OpenFOAM Calculated Coupled Interface Forces + +.. .. figure:: figures/Forces.png +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. Forces -OpenFOAM Calculated Coupled Interface Moments +.. OpenFOAM Calculated Coupled Interface Moments -.. figure:: figures/Moments.png - :align: center - :width: 600 - :figclass: align-center - Moments +.. .. figure:: figures/Moments.png +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. Moments -OpenFOAM Calculated Pressure Probe Values +.. OpenFOAM Calculated Pressure Probe Values -.. figure:: figures/Pressures.png - :align: center - :width: 600 - :figclass: align-center - Pressures +.. .. figure:: figures/Pressures.png +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. Pressures -OpenFOAM Calculated Velocity Probe Values +.. OpenFOAM Calculated Velocity Probe Values -.. figure:: figures/Velocities.png - :align: center - :width: 600 - :figclass: align-center - Velocities +.. .. figure:: figures/Velocities.png +.. :align: center +.. :width: 600 +.. :figclass: align-center +.. Velocities -OpenFOAM Calculated Free Surface Values +.. OpenFOAM Calculated Free Surface Values -.. figure:: figures/WaveGauges.png - :align: center - :width: 600 - :figclass: align-center - Wave Gauges +.. .. figure:: figures/WaveGauges.png +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. Wave Gauges + + +.. _hdro-0004-references: + +References +---------- diff --git a/docs/_sources/common/user_manual/examples/desktop/hdro-0005/README.rst.txt b/docs/_sources/common/user_manual/examples/desktop/hdro-0005/README.rst.txt new file mode 100644 index 00000000..175a95aa --- /dev/null +++ b/docs/_sources/common/user_manual/examples/desktop/hdro-0005/README.rst.txt @@ -0,0 +1,274 @@ +.. _hdro-0005: + +==================================================================================== +Feature - Stochastic Wave Loading on a Simple Structure - Stochastic Wave Spectra +==================================================================================== + ++---------------+----------------------------------------------+ +| Problem files | :github:`Github ` | ++---------------+----------------------------------------------+ + + +.. contents:: Table of Contents + :local: + :backlinks: none + + +.. _hdro-0005-overview: + +Overview +-------- + +.. figure:: figures/hdro-0005_WaveTimeSeries.png + :align: center + :width: 600 + :figclass: align-center + + Stochastic JONSWAP wave spectra produced in HydroUQ, applying the welib Python package. + +In this local workflow example, basic uncertainty quantification methods (Forward, Sensitivity, Reliability) are applied to the response of a simple structure loaded by stochastic wave spectra. + + +Set-Up +------ + +.. figure:: figures/hdro-0005_UQ.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ's desktop GUI for the NHERI OSU LWF digital wave-flume twin. + +Details for the experiments are available in various publications. Namely, the work of Andrew Winter [Winter2020]_ [Winter2019]_, Krishnendu Shekhar [Shekhar2020]_ and Dakota Mascarenas [Mascarenas2022]_ [Mascarenas2022PORTS]_. The simulations replicated in this example appeared originally in Bonus 2023 [Bonus2023Dissertation]_. + +Experiments were performed in the NHERI OSU LWF, a 100 meter long flume with adjustable bathymetry, in order to quantify stochastic impact loads of ordered and disordered debris-fields on effectively rigid, raised structure. + +.. figure:: figures/hdro-0005_GI.png + :align: center + :width: 600 + :figclass: align-center + + NHERI OSU LWF facilty's experimental schematic used in this example. Adapted from Winter 2019 [Winter2019]_, and Mascarenas 2022 [Mascarenas2022]_. + +This example may help to produce a robust database (numerical and physical) from which to eventually be able to extract both the first principles of wave-driven debris-field phenomena and design guidelines on induced forces. + +We validate against two very similar (but not identical) physical studies done in the OSU LWF by [Shekhar2020]_ and [Mascarenas2022]_, indicating high accuracy of our model and low bias to minor experiment specifications. + +Results for free surface elevation and streamwise structural loads are to be recorded for validation at a specified interval. + +Qualitatively, an MPM simulation of debris impacts on a raised structure in the OSU LWF is shown below. + +.. figure:: figures/hdro-0005_SIM.png + :align: center + :width: 600 + :figclass: align-center + + OSU LWF debris impact photos from HydroUQ's MPM simulations. + +It appears similar in the mechanism of debris impact, stalling, and deflection relative to the structure and flow for a similar case in Mascarenas 2022 [Mascarenas2022]_. + +.. figure:: figures/hdro-0005_EVT.png + :align: center + :width: 600 + :figclass: align-center + + OSU LWF debris impact photos from Mascarenas 2022 [Mascarenas2022]_ experiments. + + +The experiments by Shekhar et al. 2020 [Shekhar2020]_ are also shown below for comparison. These tests had a slightly different configuartion, primarily the debris were located 0.5 meters further upstream from the box and the water level was 0.10-0.15 meters lower than the 2.0 meter datum used in the simulations and Mascarenas 2022 [Mascarenas2022]_ experiments. + +.. figure:: figures/hdro-0005_EDP.png + :align: center + :width: 600 + :figclass: align-center + + OSU LWF debris impact photos from Shekhar et al. 2020 [Shekhar2020]_ experiments. + +Similar figures can be made for the whole range of order debris-array experiments done at the OSU LWF. However, this example focuses on teaching you how to replicate the above results. + + +.. _hdro-0005-setup: + + + +A step-by-step walkthrough on replicating an MPM simulation result from Bonus 2023 [Bonus2023Dissertation]_ is provided below. + +Open ``Settings``. Here we set the simulation time, the time step, and the number of processors to use, among other pre-simulation decisions. + +.. figure:: figures/hdro-0005_RV.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Settings GUI + + +Open ``Bodies`` / ``Fluid`` / ``Material``. Here we set the material properties of the fluid and the debris. + +.. figure:: figures/hdro-0005_RES_Summary_Forward.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Fluid Material GUI + +Open ``Bodies`` / ``Fluid`` / ``Geometry``. Here we set the geometry of the flume, the debris, and the raised structure. + +.. figure:: figures/hdro-0005_RES_Scatter.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Fluid Geometry GUI + + +Open ``Algorithm``. Here we set the algorithm parameters for the simulation. We choose to apply F-Bar antilocking to aid in the pressure field's accuracy on the fluid. The associated toggle must be checked, and the antilocking ratio set to 0.9, loosely. + +.. figure:: figures/hdro-0005_RES_Cumulative_Forward.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Fluid Algorithm GUI + +Open ``Bodies`` / ``Fluid`` / ``Partitions``. Here we set the number of partitions for the simulation. This is the domain decomposition across discrete hardware units, i.e. Multi-GPUs. These may be kept as their default values. + +.. figure:: figures/hdro-0005_RES_HistogramForward.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Fluid Partitions GUI + +Moving onto the creation of an ordered debris-array, we set the debris properties in the ``Bodies`` / ``Debris`` / ``Material`` tab. We will assume debris are made of HDPE plastic, as in experiments by Mascarenas 2022 [Mascarenas2022]_ and Shekhar et al. 2020 [Shekhar2020]_. + +.. figure:: figures/hdro-0005_RV_Sensitivity.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Debris Material GUI + +Open ``Bodies`` / ``Debris`` / ``Geometry``. Here we set the debris properties, such as the number of debris, the size of the debris, and the spacing between the debris. Rotation is another option, though not used in this example. We've elected to use an 8 x 4 grid of debris (longitudinal axis parallel to long-axis of the flume). + +.. figure:: figures/hdro-0005_RES_Summary_Sensitivity.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Debris Geometry GUI + +The ``Bodies`` / ``Debris`` / ``Algorithm`` and ``Debris`` / ``Partitions`` tabs are not used in this example, but are available for more advanced users. + +Open ``Bodies`` / ``Structures``. Uncheck the box that enables this body, if it is checked. We will not model the structure as a body in this example, instead, we will modify it as a boundary later. + +.. figure:: figures/hdro-0005_RES_Scatter_Sensitivity.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Structures GUI + +Open ``Boundaries`` / ``Wave Flume``. We will set the boundary to be a rigid body, with a fixed separable velocity condition, that is faithful to the digital tiwn of the NHERI OSU LWF. Bathmyetry joint points should be identical to the ones used in ``Bodeis`` / ``FLuid``. + +.. figure:: figures/hdro-0005_RES_Summary_Reliability.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Boundaries Wave Flume Facility GUI + +Open ``Boundaries`` / ``Wave Generator``. Fill in the appropriate file-path for the wave generator paddle motion. It is designed to produce near-solitary like waves. + +.. figure:: figures/hdro-0005_forces.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Boundaries Wave Generator GUI + +Open ``Boundaries`` / ``Rigid Structure``. This is where we will specify the raised structure as a boundary condition. By doing so, we can determine exact loads on the rigid boundary grid-nodes, which may then be mapped to the FEM tab for nonlinear UQ structural response analysis. + +.. figure:: figures/hdro-0005_moments.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Boundaries Rigid Structure GUI + +Open ``Boundaries`` / ``RigidWalls``. + +.. figure:: figures/hdro-0005_IntegratedPileLoads.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Boundaries Wave-Flume Facility GUI + +Open ``Sensors`` / ``Wave Gauges``. Set the ``Use these sensor?`` box to ``True`` so that the simulation will output results for the instruments we set on this page. + +Three wave gauges will be defined. The first is located prior to the bathymetry ramps, the second partially up the ramps, and the third near the bathymetry crest, debris, and raised structure. + +Set the origins and dimensions of each wave as in the table below. To match experimental conditions, we also apply a 120 Hz sampling rate to the wave gauges, meaning they record data every 0.0083 seconds. + + + +.. Open ``Sensors`` / ``Load Cells``. Set the ``Use these sensor?`` box to ``True`` so that the simulation will output results for the instruments we set on this page. + +.. .. figure:: figures/GUI_Sensors_LoadCells.PNG +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. HydroUQ Sensors Load-Cells GUI + + +.. Open ``Outputs``. Here we set the non-physical output parameters for the simulation, e.g. attributes to save per frame and file extension types. The particle bodies' output frequency is set to 10 Hz (0.1 seconds), meaning the simulation will output results every 0.1 seconds. This is decent for animations without taking too much space. Fill in the rest of the data in the figure into your GUI to ensure all your outputs match this example. + +.. .. figure:: figures/GUI_Outputs.PNG +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. HydroUQ Outputs GUI + + + +.. _hdro-0005-simulation: + +Simulation +---------- + +We assume most computers will be able to run this simulation within a few minutes if samples are kept below 100. + +.. warning:: + Only ask for what you need in terms of recorder count, time-step size, random variables, and UQ samples. Otherwise, you will end up with massive amounts of data which can slow simulations due to I/O constraints. + + +.. _hdro-0005-analysis: + +Analysis +-------- + + +This completes our HydroUQ validation example for stochastic wave-loading on a simple frame structure. + + +.. _hdro-0005-references: + +References +---------- + +.. [Winter2019] Winter, A. (2019). "Effects of Flow Shielding and Channeling on Tsunami-Induced Loading of Coastal Structures." PhD thesis. University of Washington, Seattle. + +.. [Winter2020] Andrew O Winter, Mohammad S Alam, Krishnendu Shekhar, Michael R Motley, Marc O Eberhard, Andre R Barbosa, Pedro Lomonaco, Pedro Arduino, Daniel T Cox (2019). "Tsunami-Like Wave Forces on an Elevated Coastal Structure: Effects of Flow Shielding and Channeling." Journal of Waterway, Port, Coastal, and Ocean Engineering. + +.. [Shekhar2020] Shekhar, K., Mascarenas, D., and Cox, D. (2020). "Wave-Driven Debris Impact on a Raised Structure in the Large Wave Flume." 17th International Conference on Hydroinformatics, Seoul, South Korea. + +.. [Mascarenas2022] Mascarenas, Dakota. (2022). "Quantification of Wave-Driven Debris Impact on a Raised Structure in a Large Wave Flume." Masters thesis. University of Washington, Seattle. + +.. [Mascarenas2022PORTS] Mascarenas, Dakota, Motley, M., Eberhard, M. (2022). "Wave-Driven Debris Impact on a Raised Structure in the Large Wave Flume." Journal of Waterway, Port, Coastal, and Ocean Engineering. + +.. [Bonus2023Dissertation] Bonus, Justin (2023). "Evaluation of Fluid-Driven Debris Impacts in a High-Performance Multi-GPU Material Point Method." PhD thesis. University of Washington, Seattle. + + diff --git a/docs/_sources/common/user_manual/examples/desktop/hdro-0010/README.rst.txt b/docs/_sources/common/user_manual/examples/desktop/hdro-0010/README.rst.txt new file mode 100644 index 00000000..a0da48f6 --- /dev/null +++ b/docs/_sources/common/user_manual/examples/desktop/hdro-0010/README.rst.txt @@ -0,0 +1,274 @@ +.. _hdro-0010: + +==================================================================================== +Forward Sampling - Simple Piston Generated Wave - Taichi Event +==================================================================================== + ++---------------+----------------------------------------------+ +| Problem files | :github:`Github ` | ++---------------+----------------------------------------------+ + + +.. contents:: Table of Contents + :local: + :backlinks: none + + +.. _hdro-0010-overview: + +Overview +-------- + +.. figure:: figures/hdro-0010_EVT_Single.png + :align: center + :width: 600 + :figclass: align-center + + TaichiEvent EVT of the pbf2d.py example. Includes a linear piston wave-maker creating breaking waves using local HPC resources (e.g. vectorized CPU, GPU). + +In this local workflow example, basic uncertainty quantification methods (Forward, Sensitivity, Reliability) are applied to the response of a simple structure loaded by stochastic wave spectra. + + +Set-Up +------ + +.. figure:: figures/hdro-0005_UQ.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ's desktop GUI for the NHERI OSU LWF digital wave-flume twin. + +Details for the experiments are available in various publications. Namely, the work of Andrew Winter [Winter2020]_ [Winter2019]_, Krishnendu Shekhar [Shekhar2020]_ and Dakota Mascarenas [Mascarenas2022]_ [Mascarenas2022PORTS]_. The simulations replicated in this example appeared originally in Bonus 2023 [Bonus2023Dissertation]_. + +Experiments were performed in the NHERI OSU LWF, a 100 meter long flume with adjustable bathymetry, in order to quantify stochastic impact loads of ordered and disordered debris-fields on effectively rigid, raised structure. + +.. figure:: figures/hdro-0005_GI.png + :align: center + :width: 600 + :figclass: align-center + + NHERI OSU LWF facilty's experimental schematic used in this example. Adapted from Winter 2019 [Winter2019]_, and Mascarenas 2022 [Mascarenas2022]_. + +This example may help to produce a robust database (numerical and physical) from which to eventually be able to extract both the first principles of wave-driven debris-field phenomena and design guidelines on induced forces. + +We validate against two very similar (but not identical) physical studies done in the OSU LWF by [Shekhar2020]_ and [Mascarenas2022]_, indicating high accuracy of our model and low bias to minor experiment specifications. + +Results for free surface elevation and streamwise structural loads are to be recorded for validation at a specified interval. + +Qualitatively, an MPM simulation of debris impacts on a raised structure in the OSU LWF is shown below. + +.. figure:: figures/hdro-0005_SIM.png + :align: center + :width: 600 + :figclass: align-center + + OSU LWF debris impact photos from HydroUQ's MPM simulations. + +It appears similar in the mechanism of debris impact, stalling, and deflection relative to the structure and flow for a similar case in Mascarenas 2022 [Mascarenas2022]_. + +.. figure:: figures/hdro-0010_EVT.png + :align: center + :width: 600 + :figclass: align-center + + OSU LWF debris impact photos from Mascarenas 2022 [Mascarenas2022]_ experiments. + + +The experiments by Shekhar et al. 2020 [Shekhar2020]_ are also shown below for comparison. These tests had a slightly different configuartion, primarily the debris were located 0.5 meters further upstream from the box and the water level was 0.10-0.15 meters lower than the 2.0 meter datum used in the simulations and Mascarenas 2022 [Mascarenas2022]_ experiments. + +.. figure:: figures/hdro-0005_EDP.png + :align: center + :width: 600 + :figclass: align-center + + OSU LWF debris impact photos from Shekhar et al. 2020 [Shekhar2020]_ experiments. + +Similar figures can be made for the whole range of order debris-array experiments done at the OSU LWF. However, this example focuses on teaching you how to replicate the above results. + + +.. _hdro-0010-setup: + + + +A step-by-step walkthrough on replicating an MPM simulation result from Bonus 2023 [Bonus2023Dissertation]_ is provided below. + +Open ``Settings``. Here we set the simulation time, the time step, and the number of processors to use, among other pre-simulation decisions. + +.. figure:: figures/hdro-0005_RV.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Settings GUI + + +Open ``Bodies`` / ``Fluid`` / ``Material``. Here we set the material properties of the fluid and the debris. + +.. figure:: figures/hdro-0005_RES_Summary_Forward.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Fluid Material GUI + +Open ``Bodies`` / ``Fluid`` / ``Geometry``. Here we set the geometry of the flume, the debris, and the raised structure. + +.. figure:: figures/hdro-0005_RES_Scatter.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Fluid Geometry GUI + + +Open ``Algorithm``. Here we set the algorithm parameters for the simulation. We choose to apply F-Bar antilocking to aid in the pressure field's accuracy on the fluid. The associated toggle must be checked, and the antilocking ratio set to 0.9, loosely. + +.. figure:: figures/hdro-0005_RES_Cumulative_Forward.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Fluid Algorithm GUI + +Open ``Bodies`` / ``Fluid`` / ``Partitions``. Here we set the number of partitions for the simulation. This is the domain decomposition across discrete hardware units, i.e. Multi-GPUs. These may be kept as their default values. + +.. figure:: figures/hdro-0005_RES_HistogramForward.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Fluid Partitions GUI + +Moving onto the creation of an ordered debris-array, we set the debris properties in the ``Bodies`` / ``Debris`` / ``Material`` tab. We will assume debris are made of HDPE plastic, as in experiments by Mascarenas 2022 [Mascarenas2022]_ and Shekhar et al. 2020 [Shekhar2020]_. + +.. figure:: figures/hdro-0005_RV_Sensitivity.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Debris Material GUI + +Open ``Bodies`` / ``Debris`` / ``Geometry``. Here we set the debris properties, such as the number of debris, the size of the debris, and the spacing between the debris. Rotation is another option, though not used in this example. We've elected to use an 8 x 4 grid of debris (longitudinal axis parallel to long-axis of the flume). + +.. figure:: figures/hdro-0005_RES_Summary_Sensitivity.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Debris Geometry GUI + +The ``Bodies`` / ``Debris`` / ``Algorithm`` and ``Debris`` / ``Partitions`` tabs are not used in this example, but are available for more advanced users. + +Open ``Bodies`` / ``Structures``. Uncheck the box that enables this body, if it is checked. We will not model the structure as a body in this example, instead, we will modify it as a boundary later. + +.. figure:: figures/hdro-0005_RES_Scatter_Sensitivity.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Bodies Structures GUI + +Open ``Boundaries`` / ``Wave Flume``. We will set the boundary to be a rigid body, with a fixed separable velocity condition, that is faithful to the digital tiwn of the NHERI OSU LWF. Bathmyetry joint points should be identical to the ones used in ``Bodeis`` / ``FLuid``. + +.. figure:: figures/hdro-0005_RES_Summary_Reliability.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Boundaries Wave Flume Facility GUI + +Open ``Boundaries`` / ``Wave Generator``. Fill in the appropriate file-path for the wave generator paddle motion. It is designed to produce near-solitary like waves. + +.. figure:: figures/hdro-0005_forces.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Boundaries Wave Generator GUI + +Open ``Boundaries`` / ``Rigid Structure``. This is where we will specify the raised structure as a boundary condition. By doing so, we can determine exact loads on the rigid boundary grid-nodes, which may then be mapped to the FEM tab for nonlinear UQ structural response analysis. + +.. figure:: figures/hdro-0005_moments.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Boundaries Rigid Structure GUI + +Open ``Boundaries`` / ``RigidWalls``. + +.. figure:: figures/hdro-0005_IntegratedPileLoads.png + :align: center + :width: 600 + :figclass: align-center + + HydroUQ Boundaries Wave-Flume Facility GUI + +Open ``Sensors`` / ``Wave Gauges``. Set the ``Use these sensor?`` box to ``True`` so that the simulation will output results for the instruments we set on this page. + +Three wave gauges will be defined. The first is located prior to the bathymetry ramps, the second partially up the ramps, and the third near the bathymetry crest, debris, and raised structure. + +Set the origins and dimensions of each wave as in the table below. To match experimental conditions, we also apply a 120 Hz sampling rate to the wave gauges, meaning they record data every 0.0083 seconds. + + + +.. Open ``Sensors`` / ``Load Cells``. Set the ``Use these sensor?`` box to ``True`` so that the simulation will output results for the instruments we set on this page. + +.. .. figure:: figures/GUI_Sensors_LoadCells.PNG +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. HydroUQ Sensors Load-Cells GUI + + +.. Open ``Outputs``. Here we set the non-physical output parameters for the simulation, e.g. attributes to save per frame and file extension types. The particle bodies' output frequency is set to 10 Hz (0.1 seconds), meaning the simulation will output results every 0.1 seconds. This is decent for animations without taking too much space. Fill in the rest of the data in the figure into your GUI to ensure all your outputs match this example. + +.. .. figure:: figures/GUI_Outputs.PNG +.. :align: center +.. :width: 600 +.. :figclass: align-center + +.. HydroUQ Outputs GUI + + + +.. _hdro-0010-simulation: + +Simulation +---------- + +We assume most computers will be able to run this simulation within a few minutes if samples are kept below 100. + +.. warning:: + Only ask for what you need in terms of recorder count, time-step size, random variables, and UQ samples. Otherwise, you will end up with massive amounts of data which can slow simulations due to I/O constraints. + + +.. _hdro-0010-analysis: + +Analysis +-------- + + +This completes our HydroUQ validation example for stochastic wave-loading on a simple frame structure. + + +.. _hdro-0010-references: + +References +---------- + +.. [Winter2019] Winter, A. (2019). "Effects of Flow Shielding and Channeling on Tsunami-Induced Loading of Coastal Structures." PhD thesis. University of Washington, Seattle. + +.. [Winter2020] Andrew O Winter, Mohammad S Alam, Krishnendu Shekhar, Michael R Motley, Marc O Eberhard, Andre R Barbosa, Pedro Lomonaco, Pedro Arduino, Daniel T Cox (2019). "Tsunami-Like Wave Forces on an Elevated Coastal Structure: Effects of Flow Shielding and Channeling." Journal of Waterway, Port, Coastal, and Ocean Engineering. + +.. [Shekhar2020] Shekhar, K., Mascarenas, D., and Cox, D. (2020). "Wave-Driven Debris Impact on a Raised Structure in the Large Wave Flume." 17th International Conference on Hydroinformatics, Seoul, South Korea. + +.. [Mascarenas2022] Mascarenas, Dakota. (2022). "Quantification of Wave-Driven Debris Impact on a Raised Structure in a Large Wave Flume." Masters thesis. University of Washington, Seattle. + +.. [Mascarenas2022PORTS] Mascarenas, Dakota, Motley, M., Eberhard, M. (2022). "Wave-Driven Debris Impact on a Raised Structure in the Large Wave Flume." Journal of Waterway, Port, Coastal, and Ocean Engineering. + +.. [Bonus2023Dissertation] Bonus, Justin (2023). "Evaluation of Fluid-Driven Debris Impacts in a High-Performance Multi-GPU Material Point Method." PhD thesis. University of Washington, Seattle. + + diff --git a/docs/_sources/common/user_manual/installation/desktop/install_Windows.rst.txt b/docs/_sources/common/user_manual/installation/desktop/install_Windows.rst.txt index 89980289..8fcacd93 100644 --- a/docs/_sources/common/user_manual/installation/desktop/install_Windows.rst.txt +++ b/docs/_sources/common/user_manual/installation/desktop/install_Windows.rst.txt @@ -26,11 +26,29 @@ Install on Windows 10 Install OpenFOAM for Windows ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - To install OpenFOAM-10 on Windows 10, follow the instructions below: + To install OpenFOAM-10 on Windows 10 or 11, follow the instructions below: - #. First, open *PowerShell* from the start menu and run it as an administrator. Then, in the command window type ``wsl --install`` which will install all the necessary Linux features. For detailed instructions please follow `Install WSL `_. + 1. First, open *PowerShell* from the start menu and run it as an administrator. In the command window, type the following which will install all the necessary Linux features. For detailed instructions please follow `Install WSL `_. - #. Open WSL from the start menu and run the following commands on the opened terminal window. + .. code:: bash + + wsl --install --distribution Ubuntu + + .. figure:: figures/weuq_wsl_installation.png + :align: center + :width: 75% + + Installing WSL(Ubuntu) Subsystem. + + This will install Ubuntu distribution and launch a new linux terminal to configure the installation. Then, input your user name and password to setup the system as shown bellow. + + .. figure:: figures/weuq_wsl_configuration.png + :align: center + :width: 75% + + Configuring WSL(Ubuntu) Subsystem. + + 2. Then, open WSL from the start menu and execute the following commands line by line on the opened terminal window. .. code:: bash @@ -40,7 +58,13 @@ Install on Windows 10 sudo apt-get install openfoam10 - Further instructions can be found in `OpenFOAM.org `_. + .. figure:: figures/weuq_openfoam_installation.png + :align: center + :width: 75% + + Installing OpenFOAM-10 on WSL. + + .. only:: HydroUQ_app diff --git a/docs/_sources/common/user_manual/installation/desktop/install_macOS.rst.txt b/docs/_sources/common/user_manual/installation/desktop/install_macOS.rst.txt index 4a47f544..6886dcc6 100644 --- a/docs/_sources/common/user_manual/installation/desktop/install_macOS.rst.txt +++ b/docs/_sources/common/user_manual/installation/desktop/install_macOS.rst.txt @@ -27,13 +27,7 @@ SimCenter tools require an x86-based Python 3.9. If your current Python version Python: Kernel Version -#. Visit `Python.org `_ and download the **macOS 64-bit Intel-only installer** for Python 3.9. - - .. figure:: figures/pythonDownload.png - :align: center - :figclass: align-center - - Python: python.org MacOS Download Page +#. To download a Python installer with your browser open the |appLink| page. There, you will find various files and directories available for download. Locate the file named **python-3.9.13-macosx10.9.pkg**, which we copied from `Python.org `_. Proceed to download this installer file and then open it on your local machine to initiate the Python installation process. #. Run the installer. Upon completion, a folder with several files will open, as shown in the figure below. Execute ``Update Shell Profile.command.sh`` and ``Install CertificateCommand.sh`` by double-clicking each. @@ -101,11 +95,11 @@ SimCenter tools require an x86-based Python 3.9. If your current Python version .. note:: The packaged distribution of OpenFOAM is only available for Linux systems. To install OpenFOAM on macOS, the user needs to use Docker for Mac. Docker will provide a virtual environment for running Linux applications on macOS. - To install OpenFOAM-10 on macOS, follow the instructions in `OpenFOAM for macOS `_ . - - - + To download and install Docker for macOS from the following site `Docker for macOS `_ . + .. note:: + Make sure to download Docker distribution that maches your machine requirements (Apple or Intel chip). + .. only:: HydroUQ_app Install OpenFOAM for macOS diff --git a/docs/_sources/common/user_manual/installation/desktop/installation.rst.txt b/docs/_sources/common/user_manual/installation/desktop/installation.rst.txt index bb6b1ecf..462fd1dd 100644 --- a/docs/_sources/common/user_manual/installation/desktop/installation.rst.txt +++ b/docs/_sources/common/user_manual/installation/desktop/installation.rst.txt @@ -11,3 +11,4 @@ All SimCenter applications can be downloaded from the |ResearchTools| page. This install_Windows install_macOS + setupTACC diff --git a/docs/_sources/common/user_manual/installation/desktop/setupTACC.rst.txt b/docs/_sources/common/user_manual/installation/desktop/setupTACC.rst.txt new file mode 100644 index 00000000..828b3b64 --- /dev/null +++ b/docs/_sources/common/user_manual/installation/desktop/setupTACC.rst.txt @@ -0,0 +1,50 @@ +.. _lblInstallWindows: + +Running Jobs at DesignSafe +========================== + +To run jobs on TACC high performance compute resources using the **Run at DesignSafe** button, the user must obtain a job allocation and then they must run applications to create **credentials** on each of the compute resourcses their jobs will run on. + +**Allocation** +^^^^^^^^^^^^^^ + +To obtain an allocation, the user can either submit a `DesignSafe Ticket `_ requesting an allocation or through the more formal `TACC allocation process `_. The **DesignSafe** process is probably quickest and easiest, e.g. a ticket with "Please can I have an allocation to run SimCenter jobs at DesignSafe" will be sufficient. + +**Credentials** +^^^^^^^^^^^^^^^ + +Due to cybersecurity issues, DesignSafe is requiring that all users obtain credentials for the machines on which jobs will run. Before you can run the application using the 'Run at DesignSafe' button, you must first obtain credentials for the machine(s) your jobs will run on. If you follow the links provided you will be taken to a DesignSafe app launch page specifically created for this process: + +.. only:: R2D_app + + 1. `Stampede3 Credentials `_ + +.. only:: PBE_app + + 1. `Frontera Credentials `_ + +.. only:: HydroUQ_app + + 1. `Frontera Credentials `_ + 2. `LoneStar6 Credentials `_ + +.. only:: EEUQ_app + + 1. `Frontera Credentials `_ + +.. only:: WEUQ_app + + 1. `Frontera Credentials `_ + 2. `Stampede3 Credentials`_ + +.. only:: quoFEM_app + + 1. `Stampede3 Credentials `_ + + +Simply press the green "Submit Job" button. On the pop up window that is then displayed, enter your DesignSafe password and the 6 digit MFA token before pressing the 'Authentificate' button. Once you see the words "Job submitted successfully. Monitor its progress in Job Status" in green, your credentials have been set-up and you can exit the webpage. If no pop up is displayed, you already have credentials for that machine and can exit the page. + + +.. figure:: figures/Credentials4.png + :align: center + :figclass: align-center diff --git a/docs/_sources/common/user_manual/releases/eeCapabilities.rst.txt b/docs/_sources/common/user_manual/releases/eeCapabilities.rst.txt index bc174baf..d2f60557 100644 --- a/docs/_sources/common/user_manual/releases/eeCapabilities.rst.txt +++ b/docs/_sources/common/user_manual/releases/eeCapabilities.rst.txt @@ -5,7 +5,7 @@ Capabilities ************ -**Version 3.5** of |app| was released **April 2024**. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked :blue:`blue` in the following list of features.) +**Version 4.1** of |app| was released **September 2024**. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked in :blue:`blue` in the following list of features.) Structural Information Model @@ -19,11 +19,11 @@ Applications used to specify/select the structural model to be used in the analy #. Concrete Building Model: automating concrete moment frame design and modeling #. MDOF-LU: MDOF shear building model #. SurrogateGP: surrogate model trained in EE-UQ -#. Multiple models: selecting multiple structural information models :blue:`[<- renaming from Multimodel]` +#. Multiple models: selecting multiple structural information models Earthquake Motion Event -======================= +=============================== Applications used to specify/select ground motions for the structure. @@ -33,7 +33,9 @@ Applications used to specify/select ground motions for the structure. #. Multiple PEER: using multiple PEER recordings #. Multiple SimCenter: using multiple SimCenter-format recordings #. User-specified Database: selecting and scaling ground motions from the user-specified flatfile -#. Physics-based ground motion simulations generate by the `M9 project `_. +#. Physics-based ground motion simulations generated by the `M9 project `_. +#. :blue:`Physics-based ground motion using shakermaker` +#. :blue:`Domain Reduction Method (DRM)` Engineering Demand Parameter Generator diff --git a/docs/_sources/common/user_manual/releases/eePlans.rst.txt b/docs/_sources/common/user_manual/releases/eePlans.rst.txt index b04d1d7a..2530ed34 100644 --- a/docs/_sources/common/user_manual/releases/eePlans.rst.txt +++ b/docs/_sources/common/user_manual/releases/eePlans.rst.txt @@ -6,11 +6,8 @@ Release Plans ************* -There are not any new releases planned for |app|. The development plans may change depending on feedback from the community. If you have any suggestions, we encourage you to contribute and contact us through the SimCenter Forum. +The development plans may change depending on feedback from the community. If you have any suggestions, we encourage you to contribute and contact us through the SimCenter Forum. -September 2024 ---------------- - #. Domain Reduction Method to incorporate physics-based ground motion simulation output (e.g., output from SW4, SCEC BP) into the workflow. (Sep 2024) December 2024 --------------- diff --git a/docs/_sources/common/user_manual/releases/eeReleaseNotes.rst.txt b/docs/_sources/common/user_manual/releases/eeReleaseNotes.rst.txt index 1d06af0c..b9256450 100644 --- a/docs/_sources/common/user_manual/releases/eeReleaseNotes.rst.txt +++ b/docs/_sources/common/user_manual/releases/eeReleaseNotes.rst.txt @@ -5,8 +5,42 @@ Release Notes ************* -Version 3.5.0 (Current) ------------------------ + +Version 4.1.0 +------------- + +**Release date:** Sept. 2024 + +**Highlights** + + +#. Domain Reduction Method option added in tools to create events for buildings given large physics- based simulations. +#. ShakerMaker option added to tool to perform earthquake rupture simulations. +#. OpenSees@DesignSafe option added in tools to allow users to run OpenSees, OpenSeesMP, OpenSeesSP, and OpenSeesPy simulations utilizing TACC HPC resources from their desktop. + + +Version 4.0.0 +------------- + +**Release date:** Aug. 2024 + +**Highlights** + +#. A needed release for changes required to interact with DesignSafe and new TapisV3 interface. +#. Due to AI generated spam on message board, users now directed to post questions using github discussions. + +Version 3.6.0 +-------------- + +**Release date:** June. 2024 + +**Highlights** + +#. Added Option to allow differenet events in multi-model and multi-fidelity simulations + + +Version 3.5.0 +------------- **Release date:** March. 2024 @@ -16,7 +50,7 @@ Version 3.5.0 (Current) Version 3.4.0 ------------------------ +------------- **Release date:** October 2023 diff --git a/docs/_sources/common/user_manual/releases/hydroCapabilities.rst.txt b/docs/_sources/common/user_manual/releases/hydroCapabilities.rst.txt index 6cc00e3c..9d627dd3 100644 --- a/docs/_sources/common/user_manual/releases/hydroCapabilities.rst.txt +++ b/docs/_sources/common/user_manual/releases/hydroCapabilities.rst.txt @@ -116,15 +116,9 @@ EVT (Event Selection) #. Available for running on TACC HPC - #. :blue:`Celeris`` (Coming Soon)` :sup:`3` - - #. :blue:`Boussinesq wave solver` - - #. :blue:`Nonlinear shallow-water solver` - - #. :blue:`WebGPU Accelerated` +.. + #. :blue:`Celeris`` (Coming Soon)` :sup:`3` #. :blue:`Boussinesq wave solver` #. :blue:`Nonlinear shallow-water solver` #. :blue:`WebGPU Accelerated` #. :blue:`Available for running through integrated browser (no installation required)` - #. :blue:`Available for running through integrated browser (no installation required)` .. note:: @@ -132,9 +126,12 @@ EVT (Event Selection) :sup:`2` GeoClaw functionality from HydroUQ v1.0 is partially deprecated in the current version. It is to be fully reintroduced in the near future. + +.. :sup:`3` Celeris is a new addition to the suite of numerical methods available in HydroUQ. It is currently in beta development and will be released soon. + FEM (Computational Model Specification) ======================================= diff --git a/docs/_sources/common/user_manual/releases/hydroPlans.rst.txt b/docs/_sources/common/user_manual/releases/hydroPlans.rst.txt index 30f63be8..653219d0 100644 --- a/docs/_sources/common/user_manual/releases/hydroPlans.rst.txt +++ b/docs/_sources/common/user_manual/releases/hydroPlans.rst.txt @@ -20,7 +20,6 @@ Year 3 (2024) June 2024 - December 2024 ------------------------- -#. Digital Wave Flume II: An automatically generated CFD model for simulating water loads on an isolated building with arbitrary shape defined by an STL surface. (July 2024, WBS 1.2.5.1) #. Surrogate Response for Debris: surrogate models for predicting the response of a water-loaded building during debris impacts for several fluid, debris, and structural parameters. (Aug 2024, WBS 1.2.2.2) #. Ability to use multi-model approaches for building response simulation. (Sep 2024, WBS 1.2.1.2) #. Hydrodynamic database creation employing CFD simulations. (Oct 2024, WBS 1.3.5.2) @@ -28,15 +27,14 @@ June 2024 - December 2024 #. Digital Wave Flume III: CFD model for evaluating water loads on a building with complex surrounding configuration - multiple buildings around it. (Dec 2024, WBS 1.2.5.1) #. Multi-fidelity Monte Carlo routines to utilize lower cost computational models along with higher fidelity models to reduce computational time while preserving accuracy (Dec 2024, WBS 1.3.3.2) - -.. _lbl-future_HydroUQ_2025_start: - -========================= -Year 4 (2025) -========================= - -January 2025 - March 2025 -------------------------- +.. + #. Digital Wave Flume II: An automatically generated CFD model for simulating water loads on an isolated building with arbitrary shape defined by an STL surface. (July 2024, WBS 1.2.5.1) + .. _lbl-future_HydroUQ_2025_start: + ========================= + Year 4 (2025) + ========================= + January 2025 - March 2025 + ------------------------- diff --git a/docs/_sources/common/user_manual/releases/pbePlans.rst.txt b/docs/_sources/common/user_manual/releases/pbePlans.rst.txt index 5e5b1ec9..a106ea31 100644 --- a/docs/_sources/common/user_manual/releases/pbePlans.rst.txt +++ b/docs/_sources/common/user_manual/releases/pbePlans.rst.txt @@ -8,14 +8,9 @@ Release Plans The following features are planned to be developed for upcoming releases of |app|. We are actively working on the features in the next release. Farther development priorities may change depending on feedback from the community. If you have any suggestions, we encourage you to contribute and contact us through the SimCenter Forum. -Jun 2024 --------- - - #. Facilitate wind damage and loss calculations by adding relevant vulnerability and loss components. The building-level components from the Hazus Hurricane Methodology will be complemented by components from recent research that supports higher resolution analyses. (1.3.5.1) - - Sept 2024 --------- + #. Facilitate wind damage and loss calculations by adding relevant vulnerability and loss components. The building-level components from the Hazus Hurricane Methodology will be complemented by components from recent research that supports higher resolution analyses. (1.3.5.1) #. Integrate additional functional recovery simulation engines, including the ATC 138 methodology and TREADS. This will enable benchmarking and further development of these methods diff --git a/docs/_sources/common/user_manual/releases/pbeReleaseNotes.rst.txt b/docs/_sources/common/user_manual/releases/pbeReleaseNotes.rst.txt index ea7aa9af..c67bfdf2 100644 --- a/docs/_sources/common/user_manual/releases/pbeReleaseNotes.rst.txt +++ b/docs/_sources/common/user_manual/releases/pbeReleaseNotes.rst.txt @@ -8,7 +8,16 @@ Release Notes Version 3 ========= - .. dropdown:: Version 3.4 (:blue:`Current`) + .. dropdown:: Version 3.5 (:blue:`Current`) + :open: + + **Release date:** June 2024 + + **Major updates:** + + - Ability to include different events in multi-model and multi-fidelity simulations + + .. dropdown:: Version 3.4 :open: **Release date:** March 2024 @@ -232,4 +241,4 @@ Version 1 -Users are welcome to contact us on the `Message Board `_ for new feature requests. +Users are welcome to contact us on the |messageBoard| for new feature requests. diff --git a/docs/_sources/common/user_manual/releases/quoReleaseNotes.rst.txt b/docs/_sources/common/user_manual/releases/quoReleaseNotes.rst.txt index 99086aff..14e06f23 100644 --- a/docs/_sources/common/user_manual/releases/quoReleaseNotes.rst.txt +++ b/docs/_sources/common/user_manual/releases/quoReleaseNotes.rst.txt @@ -1,4 +1,4 @@ -.. _lbl-release_quoFEM: +.. _lbl-release_quoFEM2: .. role:: blue ************* @@ -6,6 +6,18 @@ Release Notes ************* +Major Version 4 +=============== + + .. dropdown:: Version 4.0 (:blue:`Current`) + :open: + + **Release date:** Aug. 2024 + + **Highlights** + #. A needed release for changes required to interact with DesignSafe and new TapisV3 interface. + #. Due to AI generated spam on message board, users now directed to post questions using |messageBoard| instead of SimCenter Forum. + Major Version 3 =============== @@ -14,7 +26,7 @@ Major Version 3 The major version number was increased from 2 to 3 as changes were made to the input and output formats of |app|. This means old examples will not be loaded in this version of the tool. - .. dropdown:: Version 3.5 (:blue:`Current`) + .. dropdown:: Version 3.5 :open: **Release date:** December. 2023 diff --git a/docs/_sources/common/user_manual/releases/r2dCapabilities.rst.txt b/docs/_sources/common/user_manual/releases/r2dCapabilities.rst.txt index 8a00b15a..50bdc65f 100644 --- a/docs/_sources/common/user_manual/releases/r2dCapabilities.rst.txt +++ b/docs/_sources/common/user_manual/releases/r2dCapabilities.rst.txt @@ -27,6 +27,11 @@ Major updates from Version 4.0 are adding liquefaction-induced ground deformatio * :ref:`Transportation infrastructure `: a. Load transportation infrastructure database in SimCenter's ``.geojson`` format. b. Load transportation infrastructure database in common ``.gis`` format. + * :ref:`Water Distribution Network `: + a. Load water distribution network database in EPANet's format (used for REWET). + b. Load water distribution network from .csv files representing nodes and pipelines. + c. Load water distribution network from GIS files representing nodes and pipelines. + d. Load water distribution network database in EPANet's format. #. **Asset Modeling**: @@ -49,16 +54,23 @@ Major updates from Version 4.0 are adding liquefaction-induced ground deformatio a. IMasEDP (simplified analysis using Intensity Measures (IMs) as Engineering Demand Parameters (EDPs)). #. **Damage and Loss**: - * :ref:`Buildings `: + * :ref:`Buildings `: * Pelicun Damage and Loss Methods: a. HAZUS MH EQ Story b. HAZUS MH EQ IM c. HAZUS MH HU d. User-provided Models - * :ref:`Transportation infrastructure ` + * :ref:`Transportation infrastructure `: * Pelicun Damage and Loss Methods: a. HAZUS MH EQ IM b. User-provided Models + * :ref:`Water Network infrastructure `: + * Pelicun Damage and Loss Methods: + a. HAZUS MH EQ IM + b. User-provided Models + +#. **System Performance**: + * :ref:`REWET ` System performance with or without Recovery #. **Uncertainty Quantification**: * :ref:`Dakota `: diff --git a/docs/_sources/common/user_manual/releases/r2dPlans.rst.txt b/docs/_sources/common/user_manual/releases/r2dPlans.rst.txt index 4aa541ba..dba5d228 100644 --- a/docs/_sources/common/user_manual/releases/r2dPlans.rst.txt +++ b/docs/_sources/common/user_manual/releases/r2dPlans.rst.txt @@ -6,12 +6,12 @@ Release Plans ************* -The following features are planned to be developed for upcoming releases of |app|. Development priorities may change depending on feedback from the community and our users. For suggestions or to contribute, we encourage you to reach out via the `SimCenter Forum `_. +The following features are planned to be developed for upcoming releases of |app|. Development priorities may change depending on feedback from the community and our users. For suggestions or to contribute, we encourage you to reach out via the |messageBoard|. June 2024 ---------- -#. **Water Distribution Network, Buried Pipelines** (1.3.4.3): Add modeling capabilities for buried water pipelines and other water distribution infrastructure. +#. **Landslide-induced ground deformation** (1.3.4.4): Add modeling capabilities for buried water pipelines and other water distribution infrastructure. #. **Efficient Forward Propagation using Multi-Fidelity Monte-Carlo** (1.2.3.1): This feature leverages a small number of high-fidelity model outputs to improve the accuracy of efficient, approximate models, such as surrogates, enhancing performance with minimal computational overhead. diff --git a/docs/_sources/common/user_manual/releases/r2dReleaseNotes.rst.txt b/docs/_sources/common/user_manual/releases/r2dReleaseNotes.rst.txt index d03aafc8..9da7a962 100644 --- a/docs/_sources/common/user_manual/releases/r2dReleaseNotes.rst.txt +++ b/docs/_sources/common/user_manual/releases/r2dReleaseNotes.rst.txt @@ -6,7 +6,18 @@ Release Notes *************************** -Version 4.1.0 (Current) +Version 5.0.0 (Current) +----------------------- + +**Release date:** August 2024 + +**Highlights** + +#. A needed release for changes required to interact with DesignSafe and new TapisV3 interface. +#. Due to AI generated spam on message board, users now directed to post questions using github discussions. +#. A procedure for estimating shear-induced seismic slope displacement for shallow crustal earthquakes is added to the earthquake event generation tool. + +Version 4.1.0 ----------------------- **Release date:** April 2024 diff --git a/docs/_sources/common/user_manual/releases/weCapabilities.rst.txt b/docs/_sources/common/user_manual/releases/weCapabilities.rst.txt index 6b02da04..cbcf5a34 100644 --- a/docs/_sources/common/user_manual/releases/weCapabilities.rst.txt +++ b/docs/_sources/common/user_manual/releases/weCapabilities.rst.txt @@ -5,7 +5,7 @@ Capabilities ************ -**Version 3.2.0** of |app| was released **March 2024**. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked :blue:`blue` in the following list of features.) +**Version 4.1.0** of |app| was released **Sept 2024**. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked :blue:`blue` in the following list of features.) Structural Information Model @@ -24,11 +24,18 @@ Wind Loading Event Applications used to specify/select wind loading for the structure. -#. Stochastic Wind: simulating stochastic wind speed using spectral method +#. Stochastic Wind: Simulating stochastic wind speed using spectral methods. Includes the Wittig and Sinha 1975 model. #. CFD - Digital Wind Tunnel: CFD simulation of boundary layer wind tunnel #. CFD - Wind Load on Isolated Buildings: CFD-based wind load simulation for isolated buildings with complex geometry -#. DEDM_HRP: database-enabled design framework based on wind-tunnel data for high-rise buildings -#. LowRiseTPU: extracting aerodynamics loads based on the TPU database for low-rise buildings +#. :blue:`CFD - Wind Load on Surrounded Buildings:` + CFD-based wind load simulation for buildings surrounded by other buildings +#. Experimental Wind Forces: As seen in "Uncertainty Quantification and Simulation of Wind-Tunnel-Informed Stochastic Wind Loads". User specified force file input. +#. Experimental Wind Forces: As seen in "Uncertainty Quantification and Simulation of Wind-Tunnel-Informed Stochastic Wind Loads". User specified pressure file input. Includes CPSD group size. +#. Experimental Wind Pressures: As seen in "Uncertainty Quantification and Simulation of Wind-Tunnel-Informed Stochastic Wind Loads". +#. Wind Force Spectrum (CPSD) - As seen in "Optimization of uncertain structures subject to stochastic wind loads under system-level first excursion constraints: A data-driven approach. Provided by Prof. Seymour Spence's lab . +#. DEDM_HRP: Database-enabled design framework based on wind-tunnel data for high-rise buildings +#. LowRiseTPU: Extracting aerodynamics loads based on the TPU database for low-rise buildings +#. HighRiseTPU: Extracting aerodynamics loads based on the TPU database for high-rise buildings #. Wind Tunnel Experiment: uses pressure tap measurements from building in wind tunnel experiment #. Existing: User-supplied time-varying floor loads @@ -82,14 +89,21 @@ Applications to perform the uncertainty quantification for the response paramete a. Import input/output samples from data files -#. Surrogate Modeling +#. Reliability Analysis - A. SimCenterUQ Engine Surrogate Options: + A. Dakota Reliability Options - #. Surrogate modeling using Probabilistic Learning on Manifolds (PLoM) + #. Local Reliability Analysis + #. Global Reliability Analysis + #. Importance Sampling + Additional Tools =============== -#. :blue:`Empty Domain CFD Simulation`: - Capability to perform empty domain simulation to characterize Atmospheric Boundary Layer (ABL) flows using large-eddy simulation (LES). This feature uses the Turbulence Inflow Tool (TInF) tool for calibrating ABL flows for a subsequent wind load evaluation study. \ No newline at end of file +#. **Empty Domain CFD Simulation**: + Capability to perform empty domain simulation to characterize Atmospheric Boundary Layer (ABL) flows using large-eddy simulation (LES). This feature uses the Turbulence Inflow Tool (TInF) tool for calibrating ABL flows for a subsequent wind load evaluation study. + + +#. :blue:`Isolated Building CFD Simulation`: + Added a functionality to perform CFD-based wind load simulation on isolated building as a stand-alone workflow tool. This tool uses the user's local machine for performing pre-processing and run the actual CFD simulation on DesignSafe. \ No newline at end of file diff --git a/docs/_sources/common/user_manual/releases/wePlans.rst.txt b/docs/_sources/common/user_manual/releases/wePlans.rst.txt index a22d718b..d4a8df39 100644 --- a/docs/_sources/common/user_manual/releases/wePlans.rst.txt +++ b/docs/_sources/common/user_manual/releases/wePlans.rst.txt @@ -8,16 +8,17 @@ Release Plans The following features are intended to be included in |app| in upcoming releases. These may change, depending on feedback and changing priorities, though the ones closest out are things we are actively working and will be delivered. If you have any suggestions or wish to contribute, please contact us through the SimCenter Forum. -May 2024 ----------- - #. Digital Wind Tunnel (1.2.5.2) - CFD models for a complex-shaped building with explicitly modeled surrounding buildings. - #. Surrogate support for regional assessment (1.3.6.1) - Extend surrogates developed in EE-UQ that can be utilized in R2D for wind hazard simulation. +November 2024 +------------ -Sept 2024 ---------- - #. Aerodynamic Database (1.1.1.4) - Integrate an aerodynamic database integrating CFD simulation and experimental measurements. + #. Surrogate support for regional assessment (1.3.6.1) - Extend surrogates developed in WE-UQ that can be utilized in R2D for wind hazard simulation. + #. Multi-scale computational fluid dynamics framework for wind hazards. + +December 2024 +-------------- + #. Aerodynamic Database (1.1.1.4) - Integrate an aerodynamic database integrating CFD simulation and experimental measurements. #. Digital Wind Tunnel (1.2.5.2) - Customization of the Digital Wind Tunnel models for low-rise buildings with additional application examples. - #. Ability to save & utilize surrogate models using advanced Surrogate-Modeling algorithms (1.2.2.2) + #. Ability to save and utilize surrogate models using advanced Surrogate-Modeling algorithms (1.2.2.2) #. Reduced order surrogates modeling for CFD simulations (1.2.2.3) #. Regional-scale CFD simulation integration with R2D for high-resolution damage and loss assessment of wind storms (1.2.2.3) diff --git a/docs/_sources/common/user_manual/releases/weReleaseNotes.rst.txt b/docs/_sources/common/user_manual/releases/weReleaseNotes.rst.txt index 5452adb9..bc71c235 100644 --- a/docs/_sources/common/user_manual/releases/weReleaseNotes.rst.txt +++ b/docs/_sources/common/user_manual/releases/weReleaseNotes.rst.txt @@ -5,16 +5,54 @@ Release Notes ************* +Version 4.1 (Current) +----------------------- + +**Release date:** Sept. 2024 + +**Highlights** + +#. Implemented new functionality to visualize and export overall/pressure loads on building for performance based wind engineering analysis. +#. New capability to surrogate structural responses and use the surrogate model in the workflow. +#. Added numerical example for simulating wind loads on a building with surroundings assuming a idealized topology. +#. Minor bug fixes to pre-/post-processing of the CFD-based events. + + +Version 4.0 +----------------------- + +**Release date:** Aug. 2024 + +**Highlights** -Version 3.3 (Current) +#. Added CFD functionality to simulate wind loads on isolated buildings without running the entire workflow in WE-UQ +#. Major changes required for interfacing with DesignSafe the newly released Version 3 of Tapis. Updated major version to reflect preferences needed for users to submit jobs to TACC HPC resources. + + +Version 3.4 +----------------------- + +**Release date:** May. 2024 + +**Highlights** + +#. Simulate wind loading on structures surrounded by an array of buildings. Surrounding buildings heights may be randomized or user-defined. +#. Minor bug fixes in the tool. + + +Version 3.3 ----------------------- **Release date:** Apr. 2024 **Highlights** +#. Simulate wind loading on structures surrounded by an array of buildings. Surrounding buildings heights may be randomized or user-defined. #. A new wind load generator module: wind-tunnel informed stochastic wind pressure generator +#. Empty domain simulation tool. + + Version 3.2 ----------- diff --git a/docs/_sources/common/user_manual/troubleshooting/desktop/troubleshootingRunning.rst.txt b/docs/_sources/common/user_manual/troubleshooting/desktop/troubleshootingRunning.rst.txt index 7c22c030..12e88c0e 100644 --- a/docs/_sources/common/user_manual/troubleshooting/desktop/troubleshootingRunning.rst.txt +++ b/docs/_sources/common/user_manual/troubleshooting/desktop/troubleshootingRunning.rst.txt @@ -7,7 +7,7 @@ When running simulations, failures can occur due to various reasons such as inco #. A temporary directory, ``tmp.SimCenter``, is created in the working directory, followed by a ``templatedir`` within it. #. The UI processes all input panels, and workflow applications transfer necessary files to the ``templatedir``. -#. A Python script, specific to the simulation type (rWHALE.py for regional simulations, sWHALE.py for individual assessments), is executed from ``templatedir``. rWHALE serves as a wrapper, invoking sWHALE for each asset in regional assessments. +#. A Python script, specific to the simulation type (rWHALE.py for regional simulations, sWHALE.py for individual assessments), is executed from the ``templatedir``. rWHALE serves as a wrapper, invoking sWHALE for each asset in regional assessments. #. For structural response simulations, uncertainty quantification is managed by the chosen UQ Engine (e.g., Dakota), which generates an input file (e.g., ``dakota.in``) placed in ``tmp.SimCenter``. #. The UQ engine runs the response simulation using the earlier created input file. #. For each structural response realization, the UQ engine creates a separate workdir folder within ``tmp.SimCenter``. @@ -34,4 +34,22 @@ Below are common issues encountered during failures, along with troubleshooting #. **No results and you used the Site Response to create the event**. You must run a simulated event in the Site Response Widget before you can submit a job to run. -For unresolved issues, please seek assistance on the |messageBoard|. \ No newline at end of file + +#. **Don't Like Default Screen Layout**. There are configuarion you can do for startup. In the directory in which the executable exists you can place a **config.json** file. At present the options are limited: You can set screen size of the application to be full screen, and you can set and change the size of the **output** window. A sample config .json file: + +.. code-block:: + + { + "screenSize":"fullScreen", + "outputLocation":{"position":"right","numPixels":500} + } + +.. note:: + + You can also start the application from the terminal and pass config options. These options overwrite any existing. + + .. code-block + + application -screenSize fullScreen -helpLocation '{"position":"right","numPixels":400}' + +For unresolved issues, please seek assistance on the |messageBoard|. diff --git a/docs/_sources/common/user_manual/usage/desktop/DakotaSampling.rst.txt b/docs/_sources/common/user_manual/usage/desktop/DakotaSampling.rst.txt index bf91e0f9..87ee2e38 100644 --- a/docs/_sources/common/user_manual/usage/desktop/DakotaSampling.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/DakotaSampling.rst.txt @@ -14,7 +14,7 @@ and sampling based on surrogate models, including: 3. **Gaussian Process Regression (GPR)** 4. **Polynomial Chaos Expansion (PCE)** -Depending on the option selected, the user must specify the appropriate input parameters. For instance, for MCS, the number of samples specifies the number of simulations to be performed, and providing a seed value for the pseudo-random number generator will produce the same sequence of random numbers allowing the user to reproduce the sampling results multiple times. The user selects the sampling method from the dropdown ``Dakota Method Category`` menu. Additional information regarding sampling techniques offered in Dakota can be found `here `_. +Depending on the option selected, the user must specify the appropriate input parameters. For instance, for MCS, the number of samples specifies the number of simulations to be performed, and providing a seed value for the pseudo-random number generator will produce the same sequence of random numbers allowing the user to reproduce the sampling results multiple times. The user selects the sampling method from the dropdown ``Dakota Method Category`` menu. Additional information regarding sampling techniques offered in Dakota can be found `here `_. Monte Carlo Sampling (MCS) ^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/BoundariesMPM.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/BoundariesMPM.rst.txt index 337b0b23..6446b281 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/BoundariesMPM.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/BoundariesMPM.rst.txt @@ -4,5 +4,5 @@ Boundaries ---------- -There are four aspects related to the definition of boundaries, namely geometry of the ocean floor or wave flume, buildings or specimens, floating bodies, and shallow water to CFD interface. +There are four aspects related to the definition of boundaries, namely geometry of the ocean floor or wave flume, buildings or specimens, floating bodies, and shallow water to the CFD interface. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaR.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaR.rst.txt index 2d5de719..bcd41058 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaR.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaR.rst.txt @@ -47,7 +47,7 @@ The default local reliability method is the most probable point (MPP) method. Fo Eldred, M.S., Bichon, B.J., and Adams, B.M., "Overview of Reliability Analysis and Design Capabilities in DAKOTA, Proceedings of the NSF Workshop on Reliable Engineering Computing (REC 2006), Savannah, GA, February 22-24, 2006. -The second local reliability method available is the Mean Value method (also known as MVFOSM). It is the simplest and least-expensive reliability method because it estimates the response means, response standard deviations, and all response probability levels from a single evaluation of the response functions and their gradients at the uncertain variable means. This approximation can have acceptable accuracy when the response functions are nearly linear. Their distributions are approximately Gaussian, but **can have poor accuracy in other situations**. +The second local reliability method available is the Mean Value method (also known as MVFOSM). It is the simplest and least-expensive reliability method because it estimates the response means, response standard deviations and all response probability levels from a single evaluation of the response functions and their gradients at the uncertain variable means. This approximation can have acceptable accuracy when the response functions are nearly linear. Their distributions are approximately Gaussian, but **can have poor accuracy in other situations**. As shown in the figure below, the user selects either to use response levels or probability levels. The user then inputs the levels. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaSa.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaSa.rst.txt index 23fbf0dc..32fc830e 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaSa.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaSa.rst.txt @@ -3,7 +3,7 @@ Forward Propagation *************************** -The forward propagation analysis provides a probabilistic understanding of output variables by producing sample realizations and statistical moments (mean, standard deviation, skewness, and kurtosis). Currently, five sampling methods are available: Monte Carlo Sampling (MCS), Latin Hypercube Sampling (LHS), Importance Sampling (IS), and sampling-based on surrogate models, including Gaussian Process Regression (GPR) and Polynomial Chaos Expansion (PCE). Depending on the option selected, the user must specify the appropriate input parameters. For instance, for MCS, the number of samples specifies the number of simulations to be performed. Providing a random seed allows the user to reproduce the sampling results multiple times. The user selects the sampling method from the dropdown ``Methods`` menu. Additional information regarding sampling techniques offered in Dakota can be found `here `_. +The forward propagation analysis provides a probabilistic understanding of output variables by producing sample realizations and statistical moments (mean, standard deviation, skewness, and kurtosis). Currently, five sampling methods are available: Monte Carlo Sampling (MCS), Latin Hypercube Sampling (LHS), Importance Sampling (IS), and sampling based on surrogate models, including Gaussian Process Regression (GPR) and Polynomial Chaos Expansion (PCE). Depending on the option selected, the user must specify the appropriate input parameters. For instance, for MCS, the number of samples specifies the number of simulations to be performed. Providing a random seed allows the user to reproduce the sampling results multiple times. The user selects the sampling method from the dropdown ``Methods`` menu. Additional information regarding sampling techniques offered in Dakota can be found `here `_. Monte Carlo Sampling (MCS) ^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -41,7 +41,7 @@ Latin hypercube sampling (LHS) is a pseudo-random, stratified sampling approach. Importance Sampling (IS) ^^^^^^^^^^^^^^^^^^^^^^^^ -For problems where one is interested in the rare events rather than the whole distribution of output, such as earthquake or storm surge events, conventional sampling methods may require a considerable number of simulations to obtain an accurate estimation of tail distribution. For such problems, importance sampling (IS) bypasses conventional sampling methods (MCS or LHS). An alternative sampling distribution is introduced around the tail part of the original distribution so that the generated samples have a better resolution at the domain of interest. +For problems where one is interested in rare events rather than the whole distribution of output, such as earthquake or storm surge events, conventional sampling methods may require a considerable number of simulations to obtain an accurate estimation of tail distribution. For such problems, importance sampling (IS) bypasses conventional sampling methods (MCS or LHS). An alternative sampling distribution is introduced around the tail part of the original distribution so that the generated samples have a better resolution at the domain of interest. :numref:`figIS` shows the input panel for IS scheme. Like MCS and LHS, IS requires both the number of samples to be executed and the corresponding seed for generating such random samples. In addition, IS algorithm can be performed via three different approaches, as specified by the third input method: @@ -65,7 +65,7 @@ For more information on each, please refer to the Dakota manual. Gaussian Process Regression (GPR) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -For the problems in which computationally expensive models are involved, conventional sampling schemes such as LHS and MCS can be highly time-consuming. A surrogate model can be constructed based on a fewer number of simulation runs in such a case. Then the surrogate model can be used to efficiently generate a required number of samples replacing the expensive simulations. +For the problems in which computationally expensive models are involved, conventional sampling schemes such as LHS and MCS can be highly time-consuming. A surrogate model can be constructed based on a fewer number of simulation runs in such a case. Then the surrogate model can be used to efficiently generate the required number of samples replacing the expensive simulations. Gaussian Process Regression (GPR), also known as Kriging, is a well-established surrogate technique that constructs an approximated response surface based on Gaussian process modeling and covariance matrix optimizations. :numref:`figGPR` shows the input panel for the GPR model that consists of training and sampling panels. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaSe.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaSe.rst.txt index 7ca0583b..e8834fdb 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaSe.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/DakotaSe.rst.txt @@ -41,7 +41,7 @@ The sensitivity analysis results will show both the main effect and total effect When the associated FEM model is computationally expensive, the user should consider that the actual number of the simulation runs is larger than the number of samples specified in the input panel. The exact number of simulation runs are NS*(2+NRV) - - NS = number of samples specified by user + - NS = number of samples specified by the user - NRV = number of random variables diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/EVT.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/EVT.rst.txt index 3b2592f2..da4bf1a5 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/EVT.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/EVT.rst.txt @@ -6,7 +6,7 @@ EVT: Hydro Events The event panel presents the user with a drop-down menu with a list of available event applications. -Event applications are applications that, given the building and user supplied data inputs, will generate a list of events (i.e., typically time-dependent loads that represent natural disasters) for the building. +Event applications are applications that, given the building and user-supplied data inputs, will generate a list of events (i.e., typically time-dependent loads that represent natural disasters) for the building. The ``Hydro EVT`` is used to setup the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and CFD solver or using the CFD solver alone. @@ -21,7 +21,7 @@ The following options are available in the drop-down menu: .. note:: - :sup:`*` The new ``MPM`` module is only availble in the current release |tool version| as a standalone ``Tools`` app, though it is designed to be an EVT option. It will be fully-implemented as a workflow EVT in the next release. + :sup:`*` The new ``MPM`` module is only available in the current release |tool version| as a standalone ``Tools`` app, though it is designed to be an EVT option. It will be fully implemented as a workflow EVT in the next release. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/FEM.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/FEM.rst.txt index fcc58878..580ed037 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/FEM.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/FEM.rst.txt @@ -9,7 +9,7 @@ The **FEM** tab will present users with a selection of FEM applications that wil .. contents:: :local: -Currently, there is one application, OpenSees. The current OpenSees implementation extends the standard OpenSees executable with a pre- and post-processor to take the BIM and EVENT files and use OpenSees to simulate the response and return it in an EDP file. +Currently, there is one application, OpenSees. The current OpenSees implementation extends the standard OpenSees executable with a pre-/post-processor to take the BIM and EVENT files and use OpenSees to simulate the response and return it in an EDP file. .. _figFEM: @@ -28,7 +28,7 @@ options to be used in the transient analysis. As shown in :numref:`figFEM`, this #. `Integration Scheme `_: The integration scheme specifies the time-stepping algorithm being employed to solve the transient problem (:math:`M \ddot{U}(t) + C \dot{U}(t) + Fs(U(t)) = P(t)`). The integration scheme determined the coefficients in the :math:`A` matrix, the meaning of the :math:`x` and :math:`b` vectors and how the nodal displacements, velocities, and accelerations should be updated given :math:`x`. The default is Newmark's linear acceleration method (Newmark 0.5 0.25). Other Newmark methods can be employed by changing the :math:`\alpha` and :math:`\beta` terms, and other methods, HHT, CentralDifference, can be selected. -#. `Convergence Test `_, the default is the norm of the unbalance force with a convergence tolerance of 1.0e-2 and a limit of 10 trial steps to achieve convergence. Other convergence criteria that can be chosen include NormDispIncr, EnergyIncrement, and the relative norms. +#. `Convergence Test `_, the default is the norm of the unbalanced force with a convergence tolerance of 1.0e-2 and a limit of 10 trial steps to achieve convergence. Other convergence criteria that can be chosen include NormDispIncr, EnergyIncrement, and the relative norms. #. Damping Model: The pull-down menu defaults to **Rayleigh Damping**. The other option is **Modal Damping**. The theory behind the two is presented in :ref:`lblDamping`. @@ -45,7 +45,7 @@ options to be used in the transient analysis. As shown in :numref:`figFEM`, this #. Analysis Script. This shall be left blank by default. Advanced users of OpenSees who have their preferred analysis script and wish to provide their own damping model can give it here. If this option is provided, the user in their script should use the variables **numStep** and **dt**. -A default transient analysis script is run with these inputs. It is built for Version 3.0.0+ of OpenSees and uses a divide and conquer algorithm to overcome convergence issues. This new algorithm does not work for every nonlinear problem. The actual analysis command that is created based on the defaults is the following: +A default transient analysis script is run with these inputs. It is built for Version 3.0.0+ of OpenSees and uses a divide-and-conquer algorithm to overcome convergence issues. This new algorithm does not work for every nonlinear problem. The actual analysis command that is created based on the defaults is the following: .. code-block:: none diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/Geometry.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/Geometry.rst.txt index 513e5506..02774c18 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/Geometry.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/Geometry.rst.txt @@ -4,7 +4,7 @@ Geometry ******** -There are four aspects related to the definition of geometry, namely geometry of the ocean floor or wave flume, buildings or specimens, floating bodies, and shallow water to CFD interface. This section discusses the setup of all aspects of geometry. +There are four aspects related to the definition of geometry, namely geometry of the ocean floor or wave flume, buildings or specimens, floating bodies, and shallow water to the CFD interface. This section discusses the setup of all aspects of geometry. Bathymetry ========== @@ -42,7 +42,7 @@ The shallow-water to CFD interface can only be defined for the simulation type w Uploading the ``.csv`` file that defines the interface -Consider the problem description as shown in the :numref:`SWCFDInter2`. Consider an event (earthquake on a fault or low-pressure due to a hurricane) represented by the red line on the left. The shallow-water solvers are used over the Ocean domain. In order to provide a high-fidelity solution for the structural response, the shallow-water domain is further refined using 3D CFD. The yellow boxes represent the shallow water to CFD interfaces. This interface information is provided in a ``.csv`` file. +Consider the problem description as shown in the :numref:`SWCFDInter2`. Consider an event (earthquake on a fault or low-pressure due to a hurricane) represented by the red line on the left. The shallow-water solvers are used over the Ocean domain. To provide a high-fidelity solution for the structural response, the shallow-water domain is further refined using 3D CFD. The yellow boxes represent the shallow water to CFD interfaces. This interface information is provided in a ``.csv`` file. .. _SWCFDInter2: @@ -66,13 +66,13 @@ The ``.csv`` needs four patches to be explicitly defined. The first is the patch .. note:: - #. It is necessary that the point provided to define the interface needs to be closed and a quadrilateral. + #. It is necessary that the points provided to define the interface needs to be closed and create a quadrilateral. #. The patch names need to be provided to identify appropriate boundaries. Buildings and Scaled Specimens ============================== -Buildings or specimens can be defined in the ``EVT``. It is important here to note that there can be two types of buildings: (a) Building of interest for which the structural response is measured (b) Other neighboring buildings that impact the flow fields. +Buildings or specimens can be defined in the ``EVT``. It is important here to note that there can be two types of buildings: (a) The building of interest for which the structural response is measured (b) Other neighboring buildings that impact the flow fields. These can either be defined manually in a tabular format or parametrically as shown in :numref:`BuildDef`. @@ -101,7 +101,7 @@ For the manual definition of the building, a tabular format is used for the user At present, HydroUQ only supports one type of building to be defined using a ``STL`` geometry. This file needs to be in ASCII format. This limitation will be removed in the upcoming versions. -#. **Center:** This refers to the location of the building/specimen. This is defined in terms of the coordinates (``x`` , ``y`` , ``z``) or latitude-longitude depending on the type of simulation chosen earlier in :ref:`lbl-projsett`. Suppose the simulation is based on shallow-water to CFD or bathymetry settings. In that case, the latitude and longitude need to be specified. Else, the position is input in terms of the coordinates. +#. **Center:** This refers to the location of the building/specimen. This is defined in terms of the coordinates (``x`` , ``y`` , ``z``) or latitude-longitude depending on the type of simulation chosen earlier in :ref:`lbl-projsett`. Suppose the simulation is based on shallow-water to CFD or bathymetry settings. In that case, the latitude and longitude need to be specified. Otherwise, the position is input in terms of the coordinates. .. note:: Here, the building position refers to the center of the bottom surface of the building. @@ -115,7 +115,7 @@ Parametric Definition The parametric definition of the building is recommended for usage mainly for the flume. This is recommended for usage when all the buildings are of the same shape and size. Here, the buildings are automatically generated based on a set of parametric inputs. The building of interest is directly determined by the |app| by using the coordinate information from the ``GI`` tab and matching it with the nearest building. The set of parameters include: -#. **Number of buildings along the coast:** This refers to the number of building in the direction orthogonal to the flow, i.e., between right and left interfaces or walls of the CFD domain. +#. **Number of buildings along the coast:** This refers to the number of buildings in the direction orthogonal to the flow, i.e., between right and left interfaces or walls of the CFD domain. #. **Number of buildings into the coast:** This refers to the number of buildings in the flow direction, i.e., between entry and exit of the CFD domain. #. **Distance from coast:** This refers to the distance of the first building from (0,0). #. **Distance between buildings (Side):** This refers to the center-to-center distance between the buildings in the direction orthogonal to the flow. @@ -148,4 +148,4 @@ The parametric definition of the building is recommended for usage mainly for th Debris and Floating Bodies ========================== -Currently, HydroUQ |version| only supports floating bodies in the Material Point Method Event. This may expand to include OpenFOAM in an upcoming versions of |app|. +Currently, HydroUQ |version| only supports floating bodies in the Material Point Method Event. This may expand to include OpenFOAM in an upcoming version of |app|. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/Initial.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/Initial.rst.txt index 7bb1eda7..5e799b72 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/Initial.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/Initial.rst.txt @@ -6,7 +6,7 @@ Initial conditions The initial settings window can be activated by selecting the option from the left panel as shown in :numref:`InitialSett`. At present, this option is available only to set the initial height of the water in the domain. By default, the domain is defined to contain only air (i.e., alpha is zero). It is, thus, necessary to define a box where water is present (i.e., alpha is one). -This is automatically set using the shallow-water solutions for simulation types involving coupling between shallow-water and CFD. This must be manually provided for all other simulation types using the tabular format shown in :numref:`InitialSett`. +This is automatically set using the shallow-water solutions for simulation types involving coupling between shallow water and CFD. This must be manually provided for all other simulation types using the tabular format shown in :numref:`InitialSett`. .. _InitialSett: diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/MPM.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/MPM.rst.txt index 8fad5c8a..78f86eea 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/MPM.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/MPM.rst.txt @@ -4,7 +4,7 @@ Material Point Method ===================== -The ``MPM`` event option is used to setup the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and MPM solver or using the ClaymoreUW MPM solver alone. The steps of the setup process for the event have been kept nearly similar to that often used in Finite Element Method to make it easier for researchers from structural engineering background to easily use this application. This includes ``SettingsMPM`` >> ``BodiesMPM`` >> ``BoundariesMPM`` >> ``SensorsMPM`` >> ``OutputsMPM``. Figure :numref:`HydroSteps_MPM` shows the steps as selectable tab-pages in the GUI. +The ``MPM`` event option is used to set the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and MPM solver or using the ClaymoreUW MPM solver alone. The steps of the setup process for the event have been kept nearly similar to that often used in the Finite Element Method to make it easier for researchers from structural engineering background to easily use this application. This includes ``SettingsMPM`` >> ``BodiesMPM`` >> ``BoundariesMPM`` >> ``SensorsMPM`` >> ``OutputsMPM``. Figure :numref:`HydroSteps_MPM` shows the steps as selectable tab-pages in the GUI. .. _EVTSettings_MPM: diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/MaterialMPM.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/MaterialMPM.rst.txt index 6df2e307..9d303b03 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/MaterialMPM.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/MaterialMPM.rst.txt @@ -8,11 +8,11 @@ Water, plastic, concrete, sand, steel, clay, rubber, etc. are some of the materi #. **Isotropic Fluid with Viscous Shear Stress / J-Fluid:** This is used to define a basic Newtonian fluid. The material properties include density, bulk modulus, derivative of the bulk modulus with respect to pressure, and dynamic viscosity. #. **Fixed-Corotated / Neo-Hookean:** This is used to define solid hyperelastic material behavior under large strains. The material properties include Young's modulus, Poisson's ratio, and density. -#. **Drucker-Prager:** This is used to define solid / granular material behavior under large strains. The material properties include Young's modulus, Poisson's ratio, density, and the Drucker-Prager parameters. -#. **Non-Associative Cam-Clay:** This is used to define solid / granular material behavior under large strains. The material properties include Young's modulus, Poisson's ratio, density, and the Non-Associative Cam-Clay parameters. +#. **Drucker-Prager:** This is used to define solid/granular material behavior under large strains. The material properties include Young's modulus, Poisson's ratio, density, and the Drucker-Prager parameters. +#. **Non-Associative Cam-Clay:** This is used to define solid/granular material behavior under large strains. The material properties include Young's modulus, Poisson's ratio, density, and the Non-Associative Cam-Clay parameters. -Material properties are defined in the ``Material`` tab and are specific to the chosen constitutive law / material model. The material properties include: +Material properties are defined in the ``Material`` tab and are specific to the chosen constitutive law/material model. The material properties include: #. **Density:** This refers to the density of the material. This is defined in terms of the mass per unit volume. The units are generally in kg/m\ :sup:`3`. #. **Young's Modulus:** This refers to the stiffness of the material. This is defined in terms of the force per unit area. The units are generally in Pa. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/OutputsMPM.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/OutputsMPM.rst.txt index 09bfc9c0..68e73acf 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/OutputsMPM.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/OutputsMPM.rst.txt @@ -4,4 +4,4 @@ Outputs ------- -Outputs from the simulation not controlled by individual Sensors are collected in the ``Outputs`` tab. This includes choosing the output file format, checkpoint-resume file configuration, among other output related settings. +Outputs from the simulation not controlled by individual Sensors are collected in the ``Outputs`` tab. This includes choosing the output file format, checkpoint-resume file configuration, and other settings related to output. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/Project.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/Project.rst.txt index c0d7e4a0..79dbaec4 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/Project.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/Project.rst.txt @@ -16,7 +16,7 @@ The first step is to setup the project as shown in :numref:`EVTSettings`. All of 1. **Project name and description**: This is an *optional* parameter primarily meant for the user to identify and differentiate between projects. -2. **Simulation type**: This is *mandatory* and without a selection of the type, no other options can be set. The various simulation types available in ``Hydro`` event are as shown in :numref:`SimType`. The differences between different simulation types are as given below. +2. **Simulation type**: This is *mandatory* and without a selection of the type, no other options can be set. The various simulation options available in ``Hydro`` event are as shown in :numref:`SimType`. The differences between different simulation types are as given below. .. _SimType: @@ -26,7 +26,7 @@ The first step is to setup the project as shown in :numref:`EVTSettings`. All of Simulation types available in ``Hydro`` event - a. **CFD to resolve SW (Using SW results)**: This setting facilitates the user to import solutions from pre-run two-dimensional shallow water solver. The user can select small portions of the shallow-water domain and setup high-fidelity three-dimensional CFD on these selected areas. For example: If one had a GeoClaw simulation for an earthquake on the Alaska fault and one is interested in the inundation in Cresant City, CA (USA). Then, the user can bring in the GeoClaw solutions and resolve the near-coast using a full three-dimensional CFD simulation. + a. **CFD to resolve SW (Using SW results)**: This setting facilitates the user to import solutions from a pre-run two-dimensional shallow water solver. The user can select small portions of the shallow-water domain and setup high-fidelity three-dimensional CFD on these selected areas. For example: If one had a GeoClaw simulation for an earthquake on the Alaska fault and one is interested in the inundation in Cresant City, CA (USA). Then, the user can bring in the GeoClaw solutions and resolve the near-coast using a full three-dimensional CFD simulation. b. **CFD using bathymetry data**: This simulation type allows the user to setup a CFD simulation using the geometry defined through the bathymetry data of the ocean floor. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/SensorsMPM.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/SensorsMPM.rst.txt index 523fc546..de191cad 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/SensorsMPM.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/SensorsMPM.rst.txt @@ -4,6 +4,6 @@ Sensors ------- -Sensors are used to measure physical quantities such as force, pressure, etc. within the simulation. Fundamentally, a sensor is a function that maps the state of the simulation within some specified space to a scalar or vector value. These functions are often "higher-order", i.e. reduction operation such as max or add. +Sensors are used to measure physical quantities such as force, pressure, etc. within the simulation. Fundamentally, a sensor is a function that maps the state of the simulation within some specified space to a scalar or vector value. These functions are often "higher-order", i.e. reduction operations such as max or add. Defining a sensor in MPM involves specifying the sensor type, the material point variable to measure, and the region of the domain to measure. The sensor type is specified using the ``sensor_type`` parameter, and the material point variable to measure is specified using the ``mp_var`` parameter. The region of the domain to measure is specified using the ``region`` parameter. The sensor type can be one of the following: diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/bestpractices.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/bestpractices.rst.txt index 4cf3cca3..e0c2e354 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/bestpractices.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/bestpractices.rst.txt @@ -11,7 +11,7 @@ There are several sources of errors that are often observed in CFD simulations. #. The model is described by the Navier-Stokes equations. The exact N-S equations are solved when Direct Numerical Simulations (DNS) are employed. However, when the RANS approach is involved, as in HydroUQ, this involves approximations that could lead to errors and uncertainties. Thus, selecting the correct parameters is paramount. -#. If the solution shows divergence, check the boundary conditions, grid, discretization, and convergence errors. Check whether the flow is steady or unsteady and the timestep used in this regard. +#. If the solution shows divergence, check the boundary conditions, grid, discretization, and convergence errors. Check whether the flow is steady or unsteady and the time step used in this regard. Froude number =============================== @@ -35,7 +35,7 @@ Spatial discretization #. It is recommended that the aspect ratio be below 5 but can be up to 10 inside the boundary layer. Ensure that the change in grid size is gradual, and the maximum variation in grid spacing should be less than 20%. -# Avoid highly skewed cells so that the angles between gridlines are orthogonal or near orthogonal. Angles with less than 40-degrees or greater than 140-degrees may lead to numerical instabilities or unsatisfactory results. +# Avoid highly skewed cells so that the angles between grid lines are orthogonal or near orthogonal. Angles with less than 40 degrees or greater than 140 degrees may lead to numerical instabilities or unsatisfactory results. Temporal discretization =============================== @@ -63,13 +63,13 @@ Boundary conditions SW-CFD domain sizes =============================== -#. Note that each degree of latitude is approximately 69 miles (111 km apart). At the Equator, the distance is 68.703 miles (110.567 km); at Tropic of Cancer and Capricorn, it is 68.94 miles (110.948 km), and at the poles, it is 69.94 miles (111.699 km). +#. Note that each degree of latitude is approximately 69 miles (111 km apart). At the Equator, the distance is 68.703 miles (110.567 km); at the Tropic of Cancer and Capricorn, it is 68.94 miles (110.948 km), and at the poles, it is 69.94 miles (111.699 km). #. 60 minutes = 1 degree #. For a 1-minute grid used in the SW-solver, this is approximately a 2 x 2 km grid (in terms of distances). This could still be a considerably large domain for the CFD simulation, depending on the topography and bathymetry. -#. If the simulation type is SW-CFD coupling, then there can be wave reflections. Such wave reflections can lead to unphysical fluid accumulation at the boundary. +#. If the simulation type is SW-CFD coupling, then there can be wave reflections. Such wave reflections can lead to non-physical fluid accumulation at the boundary. Turbulence modeling =============================== @@ -111,14 +111,14 @@ where :math:`L` is the characteristic length scale, :math:`y^{+}` is the desired #. The :math:`k-\epsilon` model is inaccurate for flows with adverse pressure gradients. It does not allow integration of the conservation equations through the viscous sublayer where low Reynolds number corrections are recommended. -#. The :math:`k-\omega` model is very sensitive to the freestream boundary conditions. However, it performs well for flows with variable pressure gradients. +#. The :math:`k-\omega` model is very sensitive to the free-stream boundary conditions. However, it performs well for flows with variable pressure gradients. User errors =============================== #. Check for details in the geometry. Do not over-simplify the geometry without an understanding of the given problem. -#. Inaccurate use of boundary conditions and / or low-quality grids (e.g., poorly meshed in critical locations, inadaquate resolution for the problem) are commonly observed user errors. +#. Inaccurate use of boundary conditions and/or low-quality grids (e.g., poorly meshed in critical locations, inadequate resolution for the problem) are commonly observed user errors. #. Ensure that the timestep sizes provided are reasonable. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/coupled.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/coupled.rst.txt index b77dfb48..c9a009f6 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/coupled.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/coupled.rst.txt @@ -28,13 +28,13 @@ Coupled Simulation Settings The user is presented with a variety of settings to specify the coupled simulation. The GUI is shown in Figure :numref:`EVT-CoupledSettings` and individual input parameters are as follows: -``Time Step``: The coupling timestep for the solution. This value should be selected such that CFD model CFL criterion is satisfied, as well as the required minimum timestep for finite element analysis model stability. +``Time Step``: The coupling timestep for the solution. This value should be selected such that the CFD model CFL criterion is satisfied, as well as the required minimum timestep for finite element analysis model stability. ``Duration``: Coupled simulation duration. ``Preload Structure w/ Gravity``: Utilize the nodal masses to create a gravity loading in the -Z direction of the OpenSees model. (optional, this could be handled manually within the OpenSees script itself) -``Run Preliminary Structural Analysis``: Utilize the end state of the OpenSees analysis (if defined in the OpenSees script) as the initial state of structure during the coupled analysis. +``Run Preliminary Structural Analysis``: Utilize the end state of the OpenSees analysis (if defined in the OpenSees script) as the initial state of the structure during the coupled analysis. .. _EVT-CoupledSettings: @@ -62,25 +62,25 @@ The user is presented with a variety of settings to specify the coupled simulati ``Initial Relaxation Factor``: The relaxation factor for FSI coupling iterations. -``Maximum Coupling Iterations``: Default, 100. Keep at a large value, should converge before reaching maximum iterations. +``Maximum Coupling Iterations``: Default, 100. Keep at a large value, and should converge before reaching maximum iterations. ``Coupling Iteration Convergence Tolerance``: This is a relative convergence measure of the coupling data passed between participants within each coupling timestep. This value should be below 5e-3, but not too small. This is a measure of how much the coupling residuals change from coupling iteration to coupling iteration. Once the values have nearly approached their desired values from the interface acceleration techniques, the coupling convergence tolerance is satisfied. -``Data Mapping Scheme``: Nearest Neighbor is recommended. Radial-basis-function mapping is available, but is less stable and slower than nearest neighbor. +``Data Mapping Scheme``: Nearest Neighbor is recommended. Radial-basis-function mapping is available but is less stable and slower than the nearest neighbor. ``Output Data from Coupling Iterations``: Not recommended. Intended for debugging of coupling iterations for models which are not converging. ``Coupling Iteration Output Data Frequency``: A large value is recommended. -Specificy OpenSees Structural Model and an External Surface File +Specify OpenSees Structural Model and an External Surface File ---------------------------------------------------------------- **OpenSees Model** ``OpenSees File``: Must be an OpenSeesPy script -``External surface file``: Must be a STL file, this is the boundary which will represent the structure within a three-dimensional CFD simulation, which will be coupled to the FEA model) +``External surface file``: Must be an STL file, this is the boundary that will represent the structure within a three-dimensional CFD simulation, which will be coupled to the FEA model) .. figure:: coupled/OpenSees.png @@ -90,12 +90,12 @@ Specificy OpenSees Structural Model and an External Surface File OpenSees -Specificy OpenFOAM CFD Model and Initial Conditions +Specify OpenFOAM CFD Model and Initial Conditions --------------------------------------------------- **OpenFOAM Model** -Select a NHERI flume facility or specify the flume geometry within the text field boxes provided. +Select the NHERI flume facility or specify the flume geometry within the text field boxes provided. Specify a flume cell size (this is the approximate edge length size of the volumes within the CFD domain for the largest cells). The minimum flume cell size could tentatively be 8 times smaller than this value, due to mesh castellation during automatic meshing routines. Use caution when specifying this value. CFD mesh resolution is increased in the structural near field. @@ -109,7 +109,7 @@ Specify a flume cell size (this is the approximate edge length size of the volum **Specify the flume bathymetry (STL file, or point list of x position, elevation of flume floor at x position).** -If there is no bathymetry, please provide points within the point list which are outside of the boundary of the flume, or specify the bottom of the flume as a two point list with your start x location and end x location as the start and end of the flume and the flume elevation at both points as 0. +If there is no bathymetry, please provide points within the point list that are outside of the boundary of the flume, or specify the bottom of the flume as a two-point list with your start x location and end x location as the start and end of the flume and the flume elevation at both points as 0. .. figure:: coupled/bathymetryOF.png @@ -140,7 +140,7 @@ If there is no bathymetry, please provide points within the point list which are **Specify the wave generation techniques for the CFD model, if waves are desired.** -``Paddle Generated Waves``: Upload a CSV of times, displacements of the paddle at the inlet. This will create a paddle generated wave through motion of the CFD boundary at the minimum X boundary of the model. +``Paddle Generated Waves``: Upload a CSV of times, displacements of the paddle at the inlet. This will create a paddle-generated wave through the motion of the CFD boundary at the minimum X boundary of the model. ``Periodic Waves``: Specify the wave properties to apply a periodic wave inlet boundary condition to the CFD model. @@ -156,7 +156,7 @@ If there is no bathymetry, please provide points within the point list which are Specify Outputs --------------- -A variety of outputs from the coupled model can be obtained through specification of the output settings. +A variety of outputs from the coupled model can be obtained through the specification of the output settings. - Output VTK - Output a VTK file of the OpenSees and OpenFOAM models at the specified time interval. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/errors.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/errors.rst.txt index a16dd8b1..5b6eba08 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/errors.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/errors.rst.txt @@ -41,9 +41,9 @@ The following is a list of things that we have observed go wrong when the user i #. **dakota.err file exists but is empty**: This means that Dakota ran, but there was a problem with the simulation. Go to one of the ``workdir`` locations. There is a file workflow driver that can be run. Run it and see what the errors are. - #. **You ran at DesignSafe and no dakota.out files come back**: Go to your data depot folder at DesignSafe using your browser. Go to archive/jobs and use the job number shown in table that pops up when you ask to get the job from DesignSafe. Study both the ``.err`` and ``.out`` files in that directory for a clues to as what went wrong. + #. **You ran at DesignSafe and no dakota.out files come back**: Go to your data depot folder at DesignSafe using your browser. Go to archive/jobs and use the job number shown in the table that pops up when you ask to get the job from DesignSafe. Study both the ``.err`` and ``.out`` files in that directory for clues to as what went wrong. -If problems persists, please post them on the |messageBoard| +If the problem persis, please post them on the |messageBoard| Other issues ---------------- @@ -52,7 +52,7 @@ Some of the other common tips and tricks for troubleshooting include: **Know the objective** -Before starting the simulation, it is essential to understand the intended goal of the project. This will help set up appropriate inputs. ``Hydro-UQ`` workflows already helps with this to the best extent possible. Yet, the user's understanding of the physics is much necessary. +Before starting the simulation, it is essential to understand the intended goal of the project. This will help set up appropriate inputs. ``Hydro-UQ`` workflows already help with this to the best extent possible. Yet, the user's understanding of the physics is much necessary. **Mesh quality** diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/general.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/general.rst.txt index 60521b28..c7ffeda4 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/general.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/general.rst.txt @@ -2,7 +2,7 @@ General Event (Legacy) ---------------------- -The ``general`` event option is used to setup the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and CFD solver or using the CFD solver alone. The steps of the setup process for the event have been kept nearly similar to that often used in Finite Element Method to make it easier for researchers from structural engineering background to easily use this application. This includes ``project settings`` >> ``geometry`` >> ``meshing`` >> ``materials`` >> ``initial conditions`` >> ``boundary conditions`` >> ``solver settings``. These steps are available through a tree-structure as shown in :numref:`EVTSettings`. +The ``general`` event option is used to set the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and CFD solver or using the CFD solver alone. The steps of the setup process for the event have been kept nearly similar to that often used in the Finite Element Method to make it easier for researchers from structural engineering background to easily use this application. This includes ``project settings`` >> ``geometry`` >> ``meshing`` >> ``materials`` >> ``initial conditions`` >> ``boundary conditions`` >> ``solver settings``. These steps are available through a tree structure as shown in :numref:`EVTSettings`. .. _EVTSettings: @@ -10,7 +10,7 @@ The ``general`` event option is used to setup the flow parameters related to the :align: center :figclass: align-center - The steps involved in setup of the ``HydroUQ`` event + The steps involved in the setup of the ``HydroUQ`` event Each of the above steps in the setup process differs depending on the type of simulation considered. They will be outlined in detail below: diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/releasenotes.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/releasenotes.rst.txt index 37337b61..04b16718 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/releasenotes.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/releasenotes.rst.txt @@ -32,7 +32,7 @@ Version 3.1 **Debris** a. Added debris modeling to ``MPM`` simulations. - b. Added support for complex debris geomtries (e.g. vehicles, shipping crates, composed primitives). + b. Added support for complex debris geometries (e.g. vehicles, shipping crates, composed primitives). c. Added support for advanced debris material models (e.g. ``Fixed-Corotated``, ``Neo-Hookean``, ``Drucker-Prager``, ``Non-Associative Cam-Clay``). @@ -60,7 +60,7 @@ Version 3.1 * ``Fixed-Corotated``: Hyperelastic material model for plastic and rubber-like materials. * ``Neo-Hookean``: Hyperelastic material model for plastic and rubber-like materials. * ``Drucker-Prager``: Applicable to granular materials, concrete, and other materials with a yield surface. - * ``Non-Associative Cam-Clay``: Aplicable to clays, concrete, and other topology changing material bodies + * ``Non-Associative Cam-Clay``: Applicable to clays, concrete, and other topology-changing material bodies #. **Geometry** @@ -86,21 +86,21 @@ Version 3.1 * Bodies may be split across multiple hardware partitions. * Accelerates simulation times by running multiple bodies in parallel. * A valid hardware partition may be a core, a GPU, or a node in an HPC cluster. - * Each partition may hold some maximum number of bodies at once (specific to the system which the simulating tool was compiled on). + * Each partition may hold some maximum number of bodies at once (specific to the system on which the simulating tool was compiled). #. **Boundaries** - Any object in a simulation that is not a sensor or body is considered a ``Boundary``. ``Boundaries``, the collection of ``Boundary`` objects, are enforced boundary conditions which may apply to parts of the simulation (e.g. on grid-nodes or particles). + Any object in a simulation that is not a sensor or body is considered a ``Boundary``. ``Boundaries``, the collection of ``Boundary`` objects, are enforced boundary conditions that may apply to parts of the simulation (e.g. on grid nodes or particles). * Added boundaries for geometry primitives (e.g. ``sphere``, ``box``, ``cylinder``). * Added selectable contact models (e.g. ``Sticky``, ``Slip``, ``Separable``). * Added boundaries for the ``OSU LWF`` and ``WU TWB`` digital twin bathymetries. * Added boundary for the ``OSU LWF`` moving piston wave-maker. - * Implemented array operations for boundary conditions (e.g. instace a boundary at specified spacings in X, Y, and Z). + * Implemented array operations for boundary conditions (e.g. instance a boundary at specified spacings in X, Y, and Z). #. **Sensors** - Any object in a simulation that is not a boundary condition or body is considered a ``Sensor``. ``Sensors``, the collection of ``Sensor`` objects, are used to monitor the simulation, collect desired data, reduce said data, and report the aggregated output as a time-series. In effect, they replicate instruments / sensors used in experiments (e.g. load-cells, wave-gauges, piezometers, velocimeters). + Any object in a simulation that is not a boundary condition or body is considered a ``Sensor``. ``Sensors``, the collection of ``Sensor`` objects, are used to monitor the simulation, collect desired data, reduce said data, and report the aggregated output as a time-series. In effect, they replicate instruments/sensors used in experiments (e.g. load-cells, wave-gauges, piezometers, velocimeters). * Sensors may be placed on numerical bodies (e.g. on ``particles`` or ``grid-nodes`` for ``MPM``) to monitor the simulation. * Supports force, pressure, velocity, and elevation sensors by default. @@ -110,18 +110,18 @@ Version 3.1 #. **Outputs** - Collection of simulation settings that do not effect the simulation itself, but rather the output it gives to the user. + Collection of simulation settings that do not affect the simulation itself, but rather the output it gives to the user. * Supports output of simulation geometry data in the form of ``.bgeo`` files, ``.vtk`` files, and ``.csv`` files. * Supports output of simulation sensor data in the form of ``.csv`` and ``.txt`` files. * Supports output of simulation state data in the form of ``.bgeo`` files. - * Enable / disable tracking of and output of simulation energy (kinetic, strain, etc.). - * Enable / disable output of simulation checkpoints (allow for a simulation to be resumed if stopped). + * Enable/disable tracking of and output of simulation energy (kinetic, strain, etc.). + * Enable/disable output of simulation checkpoints (allow for a simulation to be resumed if stopped). **Visualization** * Enabled visualization of the Event (``EVT``) using ``Qt3D`` - * Added support for mouse controls of camera in 3D visualization. + * Added support for mouse controls of the camera in 3D visualization. * Added support for visualizing simulation ``Bodies`` in 3D. * Added support for visualizing simulation ``Boundaries`` in 3D. * Added support for visualizing simulation ``Sensors`` in 3D. @@ -134,7 +134,7 @@ Version 3.1 **DesignSafe Support and Hardware** - * Multi-GPU accelerated simulations now supported in certain simulation types (e.g. ``ClaymoreUW MPM``). + * Multi-GPU accelerated simulations are now supported in certain simulation types (e.g. ``ClaymoreUW MPM``). * Updated support for the TACC Frontera supercomputer: @@ -225,7 +225,7 @@ Version 1.0 #. **Boundary conditions**: - a. The boundary conditions can be selected based using standard patch names. Here standard patches include entry / exit / inlet / outlet / left / right. + a. The boundary conditions can be selected based using standard patch names. Here standard patches include entry/exit / inlet/outlet / left/right. b. Velocity boundary conditions for inlet conditions include shallow-water solutions, moving wall, and constant velocity; for outlet conditions include zeroGradient and inletOutlet c. Pressure boundary conditions include zeroGradient and fixedValue. Alternatively, the user can also leave the default option. An appropriate boundary condition relevant to the velocity boundary will be chosen. d. It is recommended to use the wall boundary conditions for walls @@ -234,7 +234,7 @@ Version 1.0 a. Allows simple decomposition techniques from OpenFOAM. b. Can set start and end times for simulation - c. Can set time interval and the write intervals + c. Can set time intervals and write intervals d. Restarting facility is supported #. **Turbulence**: diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/resHydro.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/resHydro.rst.txt index 6832273d..80ed66f5 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/resHydro.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/resHydro.rst.txt @@ -9,9 +9,9 @@ RES: Results Workflow Results ---------------- -A successful run or download of a job that ran successfully at |DesignSafe| will result in 2 tabbed widgets displayed in the results panel. The first tab, as shown in :numRef:`figResultsSummary` shows the summary statistics: **mean**, **stdDev**, and **kurtosis**. +A successful run or download of a job that ran successfully at |DesignSafe| will result in 2 tabbed widgets displayed in the results panel. The first tab, as shown in :numref:`figResultsSummaryMPM` shows the summary statistics: **mean**, **stdDev**, and **kurtosis**. -.. _figResultsSummary: +.. _figResultsSummaryMPM: .. figure:: figures/resultsSummary.png :align: center @@ -19,7 +19,7 @@ A successful run or download of a job that ran successfully at |DesignSafe| will Results summary. -The second panel, shown in :numref:`figResultsData` presents the results both graphically and in tabular form. By selecting different columns with left and right mouse buttons in the table below the graphic, the information in the graph is changed. Selecting the left mouse button changes the Y-axis, the right mouse changes the X-axis. If the same column is selected using both left and right keys, either the CDF and PDF are displayed. If the last mouse press was with the left button, the PDF would be displayed; if the previous mouse press was the right one, the CDF would be displayed. +The second panel, shown in :numref:`figResultsData` presents the results both graphically and in tabular form. By selecting different columns with left and right mouse buttons in the table below the graphic, the information in the graph is changed. Selecting the left mouse button changes the Y-axis, the right mouse changes the X-axis. If the same column is selected using both the left and right keys, either the CDF or PDF is displayed. If the last mouse press was with the left button, the PDF would be displayed; if the previous mouse press was the right one, the CDF would be displayed. Regarding the columns in the table below the figure: You will see a column for each random variable the workflow came across and then the columns for the response quantities. There may be more random variables than you specified. This is because, for specific applications, the user may introduce additional random variables for the UQ engine to consider. diff --git a/docs/_sources/common/user_manual/usage/desktop/hydro/uguide.rst.txt b/docs/_sources/common/user_manual/usage/desktop/hydro/uguide.rst.txt index 11d75579..5d92261f 100644 --- a/docs/_sources/common/user_manual/usage/desktop/hydro/uguide.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/hydro/uguide.rst.txt @@ -12,7 +12,7 @@ The HydroUQ app, as will be discussed in :ref:`lblArchitecture`, is a hazard eve :align: center :figclass: align-center - The Hydro-UQ app user interface, with the EVT panel selected and the lnew HydroUQ v3.0 GUI. Numerical solver shown is the MPM solver, which is only available as a standalone pop-out Tool in the current app release, with integration in the next release. + The Hydro-UQ app user interface, with the EVT panel selected and the new HydroUQ v3.0 GUI. The numerical solver shown is the MPM solver, which is only available as a standalone pop-out Tool in the current app release, with integration in the next release. .. _legacyGUI: diff --git a/docs/_sources/common/user_manual/usage/desktop/usage.rst.txt b/docs/_sources/common/user_manual/usage/desktop/usage.rst.txt index a0cfe499..896163e0 100644 --- a/docs/_sources/common/user_manual/usage/desktop/usage.rst.txt +++ b/docs/_sources/common/user_manual/usage/desktop/usage.rst.txt @@ -5,7 +5,7 @@ User Interface ************** -The |app| is a scientific workflow application that creates workflows and runs them in the background. These workflows can integrate multiple applications, detailed further in the backend and workflows section (:ref:`lblArchitecture`). Upon launching |app|, the user is presented with the user interface (UI) shown in |figGenericUI|, which facilitates the selection of workflow applications, configuration of application parameters, initiation of workflows either locally or remotely, and visualization of simulation outcomes. +The |app| is a scientific workflow application that creates workflows and runs them in the background. These workflows can integrate multiple applications, as detailed in the backend and workflows section (:ref:`lblArchitecture`). Upon launching |app|, users are presented with the user interface (UI) shown in |figGenericUI|. This UI facilitates the selection of workflow applications, configuration of application parameters, initiation of workflows either locally or remotely, and visualization of simulation outcomes. .. only:: quoFEM_app diff --git a/docs/_static/design-style.1e8bd061cd6da7fc9cf755528e8ffc24.min.css b/docs/_sphinx_design_static/sphinx-design.5ea377869091fd0449014c60fc090103.min.css similarity index 87% rename from docs/_static/design-style.1e8bd061cd6da7fc9cf755528e8ffc24.min.css rename to docs/_sphinx_design_static/sphinx-design.5ea377869091fd0449014c60fc090103.min.css index eb19f698..a325746f 100644 --- a/docs/_static/design-style.1e8bd061cd6da7fc9cf755528e8ffc24.min.css +++ b/docs/_sphinx_design_static/sphinx-design.5ea377869091fd0449014c60fc090103.min.css @@ -1 +1 @@ -.sd-bg-primary{background-color:var(--sd-color-primary) !important}.sd-bg-text-primary{color:var(--sd-color-primary-text) !important}button.sd-bg-primary:focus,button.sd-bg-primary:hover{background-color:var(--sd-color-primary-highlight) !important}a.sd-bg-primary:focus,a.sd-bg-primary:hover{background-color:var(--sd-color-primary-highlight) !important}.sd-bg-secondary{background-color:var(--sd-color-secondary) !important}.sd-bg-text-secondary{color:var(--sd-color-secondary-text) !important}button.sd-bg-secondary:focus,button.sd-bg-secondary:hover{background-color:var(--sd-color-secondary-highlight) !important}a.sd-bg-secondary:focus,a.sd-bg-secondary:hover{background-color:var(--sd-color-secondary-highlight) !important}.sd-bg-success{background-color:var(--sd-color-success) !important}.sd-bg-text-success{color:var(--sd-color-success-text) !important}button.sd-bg-success:focus,button.sd-bg-success:hover{background-color:var(--sd-color-success-highlight) !important}a.sd-bg-success:focus,a.sd-bg-success:hover{background-color:var(--sd-color-success-highlight) !important}.sd-bg-info{background-color:var(--sd-color-info) !important}.sd-bg-text-info{color:var(--sd-color-info-text) !important}button.sd-bg-info:focus,button.sd-bg-info:hover{background-color:var(--sd-color-info-highlight) !important}a.sd-bg-info:focus,a.sd-bg-info:hover{background-color:var(--sd-color-info-highlight) !important}.sd-bg-warning{background-color:var(--sd-color-warning) !important}.sd-bg-text-warning{color:var(--sd-color-warning-text) !important}button.sd-bg-warning:focus,button.sd-bg-warning:hover{background-color:var(--sd-color-warning-highlight) !important}a.sd-bg-warning:focus,a.sd-bg-warning:hover{background-color:var(--sd-color-warning-highlight) !important}.sd-bg-danger{background-color:var(--sd-color-danger) !important}.sd-bg-text-danger{color:var(--sd-color-danger-text) !important}button.sd-bg-danger:focus,button.sd-bg-danger:hover{background-color:var(--sd-color-danger-highlight) !important}a.sd-bg-danger:focus,a.sd-bg-danger:hover{background-color:var(--sd-color-danger-highlight) !important}.sd-bg-light{background-color:var(--sd-color-light) !important}.sd-bg-text-light{color:var(--sd-color-light-text) !important}button.sd-bg-light:focus,button.sd-bg-light:hover{background-color:var(--sd-color-light-highlight) !important}a.sd-bg-light:focus,a.sd-bg-light:hover{background-color:var(--sd-color-light-highlight) !important}.sd-bg-muted{background-color:var(--sd-color-muted) !important}.sd-bg-text-muted{color:var(--sd-color-muted-text) !important}button.sd-bg-muted:focus,button.sd-bg-muted:hover{background-color:var(--sd-color-muted-highlight) !important}a.sd-bg-muted:focus,a.sd-bg-muted:hover{background-color:var(--sd-color-muted-highlight) !important}.sd-bg-dark{background-color:var(--sd-color-dark) !important}.sd-bg-text-dark{color:var(--sd-color-dark-text) !important}button.sd-bg-dark:focus,button.sd-bg-dark:hover{background-color:var(--sd-color-dark-highlight) !important}a.sd-bg-dark:focus,a.sd-bg-dark:hover{background-color:var(--sd-color-dark-highlight) !important}.sd-bg-black{background-color:var(--sd-color-black) !important}.sd-bg-text-black{color:var(--sd-color-black-text) !important}button.sd-bg-black:focus,button.sd-bg-black:hover{background-color:var(--sd-color-black-highlight) !important}a.sd-bg-black:focus,a.sd-bg-black:hover{background-color:var(--sd-color-black-highlight) !important}.sd-bg-white{background-color:var(--sd-color-white) !important}.sd-bg-text-white{color:var(--sd-color-white-text) !important}button.sd-bg-white:focus,button.sd-bg-white:hover{background-color:var(--sd-color-white-highlight) !important}a.sd-bg-white:focus,a.sd-bg-white:hover{background-color:var(--sd-color-white-highlight) !important}.sd-text-primary,.sd-text-primary>p{color:var(--sd-color-primary) !important}a.sd-text-primary:focus,a.sd-text-primary:hover{color:var(--sd-color-primary-highlight) !important}.sd-text-secondary,.sd-text-secondary>p{color:var(--sd-color-secondary) !important}a.sd-text-secondary:focus,a.sd-text-secondary:hover{color:var(--sd-color-secondary-highlight) !important}.sd-text-success,.sd-text-success>p{color:var(--sd-color-success) !important}a.sd-text-success:focus,a.sd-text-success:hover{color:var(--sd-color-success-highlight) !important}.sd-text-info,.sd-text-info>p{color:var(--sd-color-info) !important}a.sd-text-info:focus,a.sd-text-info:hover{color:var(--sd-color-info-highlight) !important}.sd-text-warning,.sd-text-warning>p{color:var(--sd-color-warning) !important}a.sd-text-warning:focus,a.sd-text-warning:hover{color:var(--sd-color-warning-highlight) !important}.sd-text-danger,.sd-text-danger>p{color:var(--sd-color-danger) !important}a.sd-text-danger:focus,a.sd-text-danger:hover{color:var(--sd-color-danger-highlight) !important}.sd-text-light,.sd-text-light>p{color:var(--sd-color-light) !important}a.sd-text-light:focus,a.sd-text-light:hover{color:var(--sd-color-light-highlight) !important}.sd-text-muted,.sd-text-muted>p{color:var(--sd-color-muted) !important}a.sd-text-muted:focus,a.sd-text-muted:hover{color:var(--sd-color-muted-highlight) !important}.sd-text-dark,.sd-text-dark>p{color:var(--sd-color-dark) !important}a.sd-text-dark:focus,a.sd-text-dark:hover{color:var(--sd-color-dark-highlight) !important}.sd-text-black,.sd-text-black>p{color:var(--sd-color-black) !important}a.sd-text-black:focus,a.sd-text-black:hover{color:var(--sd-color-black-highlight) !important}.sd-text-white,.sd-text-white>p{color:var(--sd-color-white) !important}a.sd-text-white:focus,a.sd-text-white:hover{color:var(--sd-color-white-highlight) !important}.sd-outline-primary{border-color:var(--sd-color-primary) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-primary:focus,a.sd-outline-primary:hover{border-color:var(--sd-color-primary-highlight) !important}.sd-outline-secondary{border-color:var(--sd-color-secondary) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-secondary:focus,a.sd-outline-secondary:hover{border-color:var(--sd-color-secondary-highlight) !important}.sd-outline-success{border-color:var(--sd-color-success) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-success:focus,a.sd-outline-success:hover{border-color:var(--sd-color-success-highlight) !important}.sd-outline-info{border-color:var(--sd-color-info) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-info:focus,a.sd-outline-info:hover{border-color:var(--sd-color-info-highlight) !important}.sd-outline-warning{border-color:var(--sd-color-warning) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-warning:focus,a.sd-outline-warning:hover{border-color:var(--sd-color-warning-highlight) !important}.sd-outline-danger{border-color:var(--sd-color-danger) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-danger:focus,a.sd-outline-danger:hover{border-color:var(--sd-color-danger-highlight) !important}.sd-outline-light{border-color:var(--sd-color-light) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-light:focus,a.sd-outline-light:hover{border-color:var(--sd-color-light-highlight) !important}.sd-outline-muted{border-color:var(--sd-color-muted) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-muted:focus,a.sd-outline-muted:hover{border-color:var(--sd-color-muted-highlight) !important}.sd-outline-dark{border-color:var(--sd-color-dark) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-dark:focus,a.sd-outline-dark:hover{border-color:var(--sd-color-dark-highlight) !important}.sd-outline-black{border-color:var(--sd-color-black) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-black:focus,a.sd-outline-black:hover{border-color:var(--sd-color-black-highlight) !important}.sd-outline-white{border-color:var(--sd-color-white) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-white:focus,a.sd-outline-white:hover{border-color:var(--sd-color-white-highlight) !important}.sd-bg-transparent{background-color:transparent !important}.sd-outline-transparent{border-color:transparent !important}.sd-text-transparent{color:transparent !important}.sd-p-0{padding:0 !important}.sd-pt-0,.sd-py-0{padding-top:0 !important}.sd-pr-0,.sd-px-0{padding-right:0 !important}.sd-pb-0,.sd-py-0{padding-bottom:0 !important}.sd-pl-0,.sd-px-0{padding-left:0 !important}.sd-p-1{padding:.25rem !important}.sd-pt-1,.sd-py-1{padding-top:.25rem !important}.sd-pr-1,.sd-px-1{padding-right:.25rem !important}.sd-pb-1,.sd-py-1{padding-bottom:.25rem !important}.sd-pl-1,.sd-px-1{padding-left:.25rem !important}.sd-p-2{padding:.5rem !important}.sd-pt-2,.sd-py-2{padding-top:.5rem !important}.sd-pr-2,.sd-px-2{padding-right:.5rem !important}.sd-pb-2,.sd-py-2{padding-bottom:.5rem !important}.sd-pl-2,.sd-px-2{padding-left:.5rem !important}.sd-p-3{padding:1rem !important}.sd-pt-3,.sd-py-3{padding-top:1rem !important}.sd-pr-3,.sd-px-3{padding-right:1rem !important}.sd-pb-3,.sd-py-3{padding-bottom:1rem !important}.sd-pl-3,.sd-px-3{padding-left:1rem !important}.sd-p-4{padding:1.5rem !important}.sd-pt-4,.sd-py-4{padding-top:1.5rem !important}.sd-pr-4,.sd-px-4{padding-right:1.5rem !important}.sd-pb-4,.sd-py-4{padding-bottom:1.5rem !important}.sd-pl-4,.sd-px-4{padding-left:1.5rem !important}.sd-p-5{padding:3rem !important}.sd-pt-5,.sd-py-5{padding-top:3rem !important}.sd-pr-5,.sd-px-5{padding-right:3rem !important}.sd-pb-5,.sd-py-5{padding-bottom:3rem !important}.sd-pl-5,.sd-px-5{padding-left:3rem !important}.sd-m-auto{margin:auto !important}.sd-mt-auto,.sd-my-auto{margin-top:auto !important}.sd-mr-auto,.sd-mx-auto{margin-right:auto !important}.sd-mb-auto,.sd-my-auto{margin-bottom:auto !important}.sd-ml-auto,.sd-mx-auto{margin-left:auto !important}.sd-m-0{margin:0 !important}.sd-mt-0,.sd-my-0{margin-top:0 !important}.sd-mr-0,.sd-mx-0{margin-right:0 !important}.sd-mb-0,.sd-my-0{margin-bottom:0 !important}.sd-ml-0,.sd-mx-0{margin-left:0 !important}.sd-m-1{margin:.25rem !important}.sd-mt-1,.sd-my-1{margin-top:.25rem !important}.sd-mr-1,.sd-mx-1{margin-right:.25rem !important}.sd-mb-1,.sd-my-1{margin-bottom:.25rem !important}.sd-ml-1,.sd-mx-1{margin-left:.25rem !important}.sd-m-2{margin:.5rem !important}.sd-mt-2,.sd-my-2{margin-top:.5rem !important}.sd-mr-2,.sd-mx-2{margin-right:.5rem !important}.sd-mb-2,.sd-my-2{margin-bottom:.5rem !important}.sd-ml-2,.sd-mx-2{margin-left:.5rem !important}.sd-m-3{margin:1rem !important}.sd-mt-3,.sd-my-3{margin-top:1rem !important}.sd-mr-3,.sd-mx-3{margin-right:1rem !important}.sd-mb-3,.sd-my-3{margin-bottom:1rem !important}.sd-ml-3,.sd-mx-3{margin-left:1rem !important}.sd-m-4{margin:1.5rem !important}.sd-mt-4,.sd-my-4{margin-top:1.5rem !important}.sd-mr-4,.sd-mx-4{margin-right:1.5rem !important}.sd-mb-4,.sd-my-4{margin-bottom:1.5rem !important}.sd-ml-4,.sd-mx-4{margin-left:1.5rem !important}.sd-m-5{margin:3rem !important}.sd-mt-5,.sd-my-5{margin-top:3rem !important}.sd-mr-5,.sd-mx-5{margin-right:3rem !important}.sd-mb-5,.sd-my-5{margin-bottom:3rem !important}.sd-ml-5,.sd-mx-5{margin-left:3rem !important}.sd-w-25{width:25% !important}.sd-w-50{width:50% !important}.sd-w-75{width:75% !important}.sd-w-100{width:100% !important}.sd-w-auto{width:auto !important}.sd-h-25{height:25% !important}.sd-h-50{height:50% !important}.sd-h-75{height:75% !important}.sd-h-100{height:100% !important}.sd-h-auto{height:auto !important}.sd-d-none{display:none !important}.sd-d-inline{display:inline !important}.sd-d-inline-block{display:inline-block !important}.sd-d-block{display:block !important}.sd-d-grid{display:grid !important}.sd-d-flex-row{display:-ms-flexbox !important;display:flex !important;flex-direction:row !important}.sd-d-flex-column{display:-ms-flexbox !important;display:flex !important;flex-direction:column !important}.sd-d-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}@media(min-width: 576px){.sd-d-sm-none{display:none !important}.sd-d-sm-inline{display:inline !important}.sd-d-sm-inline-block{display:inline-block !important}.sd-d-sm-block{display:block !important}.sd-d-sm-grid{display:grid !important}.sd-d-sm-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-sm-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 768px){.sd-d-md-none{display:none !important}.sd-d-md-inline{display:inline !important}.sd-d-md-inline-block{display:inline-block !important}.sd-d-md-block{display:block !important}.sd-d-md-grid{display:grid !important}.sd-d-md-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-md-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 992px){.sd-d-lg-none{display:none !important}.sd-d-lg-inline{display:inline !important}.sd-d-lg-inline-block{display:inline-block !important}.sd-d-lg-block{display:block !important}.sd-d-lg-grid{display:grid !important}.sd-d-lg-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-lg-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 1200px){.sd-d-xl-none{display:none !important}.sd-d-xl-inline{display:inline !important}.sd-d-xl-inline-block{display:inline-block !important}.sd-d-xl-block{display:block !important}.sd-d-xl-grid{display:grid !important}.sd-d-xl-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-xl-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}.sd-align-major-start{justify-content:flex-start !important}.sd-align-major-end{justify-content:flex-end !important}.sd-align-major-center{justify-content:center !important}.sd-align-major-justify{justify-content:space-between !important}.sd-align-major-spaced{justify-content:space-evenly !important}.sd-align-minor-start{align-items:flex-start !important}.sd-align-minor-end{align-items:flex-end !important}.sd-align-minor-center{align-items:center !important}.sd-align-minor-stretch{align-items:stretch !important}.sd-text-justify{text-align:justify !important}.sd-text-left{text-align:left !important}.sd-text-right{text-align:right !important}.sd-text-center{text-align:center !important}.sd-font-weight-light{font-weight:300 !important}.sd-font-weight-lighter{font-weight:lighter !important}.sd-font-weight-normal{font-weight:400 !important}.sd-font-weight-bold{font-weight:700 !important}.sd-font-weight-bolder{font-weight:bolder !important}.sd-font-italic{font-style:italic !important}.sd-text-decoration-none{text-decoration:none !important}.sd-text-lowercase{text-transform:lowercase !important}.sd-text-uppercase{text-transform:uppercase !important}.sd-text-capitalize{text-transform:capitalize !important}.sd-text-wrap{white-space:normal !important}.sd-text-nowrap{white-space:nowrap !important}.sd-text-truncate{overflow:hidden;text-overflow:ellipsis;white-space:nowrap}.sd-fs-1,.sd-fs-1>p{font-size:calc(1.375rem + 1.5vw) !important;line-height:unset !important}.sd-fs-2,.sd-fs-2>p{font-size:calc(1.325rem + 0.9vw) !important;line-height:unset !important}.sd-fs-3,.sd-fs-3>p{font-size:calc(1.3rem + 0.6vw) !important;line-height:unset !important}.sd-fs-4,.sd-fs-4>p{font-size:calc(1.275rem + 0.3vw) !important;line-height:unset !important}.sd-fs-5,.sd-fs-5>p{font-size:1.25rem !important;line-height:unset !important}.sd-fs-6,.sd-fs-6>p{font-size:1rem !important;line-height:unset !important}.sd-border-0{border:0 solid !important}.sd-border-top-0{border-top:0 solid !important}.sd-border-bottom-0{border-bottom:0 solid !important}.sd-border-right-0{border-right:0 solid !important}.sd-border-left-0{border-left:0 solid !important}.sd-border-1{border:1px solid !important}.sd-border-top-1{border-top:1px solid !important}.sd-border-bottom-1{border-bottom:1px solid !important}.sd-border-right-1{border-right:1px solid !important}.sd-border-left-1{border-left:1px solid !important}.sd-border-2{border:2px solid !important}.sd-border-top-2{border-top:2px solid !important}.sd-border-bottom-2{border-bottom:2px solid !important}.sd-border-right-2{border-right:2px solid !important}.sd-border-left-2{border-left:2px solid !important}.sd-border-3{border:3px solid !important}.sd-border-top-3{border-top:3px solid !important}.sd-border-bottom-3{border-bottom:3px solid !important}.sd-border-right-3{border-right:3px solid !important}.sd-border-left-3{border-left:3px solid !important}.sd-border-4{border:4px solid !important}.sd-border-top-4{border-top:4px solid !important}.sd-border-bottom-4{border-bottom:4px solid !important}.sd-border-right-4{border-right:4px solid !important}.sd-border-left-4{border-left:4px solid !important}.sd-border-5{border:5px solid !important}.sd-border-top-5{border-top:5px solid !important}.sd-border-bottom-5{border-bottom:5px solid !important}.sd-border-right-5{border-right:5px solid !important}.sd-border-left-5{border-left:5px solid !important}.sd-rounded-0{border-radius:0 !important}.sd-rounded-1{border-radius:.2rem !important}.sd-rounded-2{border-radius:.3rem !important}.sd-rounded-3{border-radius:.5rem !important}.sd-rounded-pill{border-radius:50rem !important}.sd-rounded-circle{border-radius:50% !important}.shadow-none{box-shadow:none !important}.sd-shadow-sm{box-shadow:0 .125rem .25rem var(--sd-color-shadow) !important}.sd-shadow-md{box-shadow:0 .5rem 1rem var(--sd-color-shadow) !important}.sd-shadow-lg{box-shadow:0 1rem 3rem var(--sd-color-shadow) !important}@keyframes sd-slide-from-left{0%{transform:translateX(-100%)}100%{transform:translateX(0)}}@keyframes sd-slide-from-right{0%{transform:translateX(200%)}100%{transform:translateX(0)}}@keyframes sd-grow100{0%{transform:scale(0);opacity:.5}100%{transform:scale(1);opacity:1}}@keyframes sd-grow50{0%{transform:scale(0.5);opacity:.5}100%{transform:scale(1);opacity:1}}@keyframes sd-grow50-rot20{0%{transform:scale(0.5) rotateZ(-20deg);opacity:.5}75%{transform:scale(1) rotateZ(5deg);opacity:1}95%{transform:scale(1) rotateZ(-1deg);opacity:1}100%{transform:scale(1) rotateZ(0);opacity:1}}.sd-animate-slide-from-left{animation:1s ease-out 0s 1 normal none running sd-slide-from-left}.sd-animate-slide-from-right{animation:1s ease-out 0s 1 normal none running sd-slide-from-right}.sd-animate-grow100{animation:1s ease-out 0s 1 normal none running sd-grow100}.sd-animate-grow50{animation:1s ease-out 0s 1 normal none running sd-grow50}.sd-animate-grow50-rot20{animation:1s ease-out 0s 1 normal none running sd-grow50-rot20}.sd-badge{display:inline-block;padding:.35em .65em;font-size:.75em;font-weight:700;line-height:1;text-align:center;white-space:nowrap;vertical-align:baseline;border-radius:.25rem}.sd-badge:empty{display:none}a.sd-badge{text-decoration:none}.sd-btn .sd-badge{position:relative;top:-1px}.sd-btn{background-color:transparent;border:1px solid transparent;border-radius:.25rem;cursor:pointer;display:inline-block;font-weight:400;font-size:1rem;line-height:1.5;padding:.375rem .75rem;text-align:center;text-decoration:none;transition:color .15s ease-in-out,background-color .15s ease-in-out,border-color .15s ease-in-out,box-shadow .15s ease-in-out;vertical-align:middle;user-select:none;-moz-user-select:none;-ms-user-select:none;-webkit-user-select:none}.sd-btn:hover{text-decoration:none}@media(prefers-reduced-motion: reduce){.sd-btn{transition:none}}.sd-btn-primary,.sd-btn-outline-primary:hover,.sd-btn-outline-primary:focus{color:var(--sd-color-primary-text) !important;background-color:var(--sd-color-primary) !important;border-color:var(--sd-color-primary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-primary:hover,.sd-btn-primary:focus{color:var(--sd-color-primary-text) !important;background-color:var(--sd-color-primary-highlight) !important;border-color:var(--sd-color-primary-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-primary{color:var(--sd-color-primary) !important;border-color:var(--sd-color-primary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-secondary,.sd-btn-outline-secondary:hover,.sd-btn-outline-secondary:focus{color:var(--sd-color-secondary-text) !important;background-color:var(--sd-color-secondary) !important;border-color:var(--sd-color-secondary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-secondary:hover,.sd-btn-secondary:focus{color:var(--sd-color-secondary-text) !important;background-color:var(--sd-color-secondary-highlight) !important;border-color:var(--sd-color-secondary-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-secondary{color:var(--sd-color-secondary) !important;border-color:var(--sd-color-secondary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-success,.sd-btn-outline-success:hover,.sd-btn-outline-success:focus{color:var(--sd-color-success-text) !important;background-color:var(--sd-color-success) !important;border-color:var(--sd-color-success) !important;border-width:1px !important;border-style:solid !important}.sd-btn-success:hover,.sd-btn-success:focus{color:var(--sd-color-success-text) !important;background-color:var(--sd-color-success-highlight) !important;border-color:var(--sd-color-success-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-success{color:var(--sd-color-success) !important;border-color:var(--sd-color-success) !important;border-width:1px !important;border-style:solid !important}.sd-btn-info,.sd-btn-outline-info:hover,.sd-btn-outline-info:focus{color:var(--sd-color-info-text) !important;background-color:var(--sd-color-info) !important;border-color:var(--sd-color-info) !important;border-width:1px !important;border-style:solid !important}.sd-btn-info:hover,.sd-btn-info:focus{color:var(--sd-color-info-text) !important;background-color:var(--sd-color-info-highlight) !important;border-color:var(--sd-color-info-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-info{color:var(--sd-color-info) !important;border-color:var(--sd-color-info) !important;border-width:1px !important;border-style:solid !important}.sd-btn-warning,.sd-btn-outline-warning:hover,.sd-btn-outline-warning:focus{color:var(--sd-color-warning-text) !important;background-color:var(--sd-color-warning) !important;border-color:var(--sd-color-warning) !important;border-width:1px !important;border-style:solid !important}.sd-btn-warning:hover,.sd-btn-warning:focus{color:var(--sd-color-warning-text) !important;background-color:var(--sd-color-warning-highlight) !important;border-color:var(--sd-color-warning-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-warning{color:var(--sd-color-warning) !important;border-color:var(--sd-color-warning) !important;border-width:1px !important;border-style:solid !important}.sd-btn-danger,.sd-btn-outline-danger:hover,.sd-btn-outline-danger:focus{color:var(--sd-color-danger-text) !important;background-color:var(--sd-color-danger) !important;border-color:var(--sd-color-danger) !important;border-width:1px !important;border-style:solid !important}.sd-btn-danger:hover,.sd-btn-danger:focus{color:var(--sd-color-danger-text) !important;background-color:var(--sd-color-danger-highlight) !important;border-color:var(--sd-color-danger-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-danger{color:var(--sd-color-danger) !important;border-color:var(--sd-color-danger) !important;border-width:1px !important;border-style:solid !important}.sd-btn-light,.sd-btn-outline-light:hover,.sd-btn-outline-light:focus{color:var(--sd-color-light-text) !important;background-color:var(--sd-color-light) !important;border-color:var(--sd-color-light) !important;border-width:1px !important;border-style:solid !important}.sd-btn-light:hover,.sd-btn-light:focus{color:var(--sd-color-light-text) !important;background-color:var(--sd-color-light-highlight) !important;border-color:var(--sd-color-light-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-light{color:var(--sd-color-light) !important;border-color:var(--sd-color-light) !important;border-width:1px !important;border-style:solid !important}.sd-btn-muted,.sd-btn-outline-muted:hover,.sd-btn-outline-muted:focus{color:var(--sd-color-muted-text) !important;background-color:var(--sd-color-muted) !important;border-color:var(--sd-color-muted) !important;border-width:1px !important;border-style:solid !important}.sd-btn-muted:hover,.sd-btn-muted:focus{color:var(--sd-color-muted-text) !important;background-color:var(--sd-color-muted-highlight) !important;border-color:var(--sd-color-muted-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-muted{color:var(--sd-color-muted) !important;border-color:var(--sd-color-muted) !important;border-width:1px !important;border-style:solid !important}.sd-btn-dark,.sd-btn-outline-dark:hover,.sd-btn-outline-dark:focus{color:var(--sd-color-dark-text) !important;background-color:var(--sd-color-dark) !important;border-color:var(--sd-color-dark) !important;border-width:1px !important;border-style:solid !important}.sd-btn-dark:hover,.sd-btn-dark:focus{color:var(--sd-color-dark-text) !important;background-color:var(--sd-color-dark-highlight) !important;border-color:var(--sd-color-dark-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-dark{color:var(--sd-color-dark) !important;border-color:var(--sd-color-dark) !important;border-width:1px !important;border-style:solid !important}.sd-btn-black,.sd-btn-outline-black:hover,.sd-btn-outline-black:focus{color:var(--sd-color-black-text) !important;background-color:var(--sd-color-black) !important;border-color:var(--sd-color-black) !important;border-width:1px !important;border-style:solid !important}.sd-btn-black:hover,.sd-btn-black:focus{color:var(--sd-color-black-text) !important;background-color:var(--sd-color-black-highlight) !important;border-color:var(--sd-color-black-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-black{color:var(--sd-color-black) !important;border-color:var(--sd-color-black) !important;border-width:1px !important;border-style:solid !important}.sd-btn-white,.sd-btn-outline-white:hover,.sd-btn-outline-white:focus{color:var(--sd-color-white-text) !important;background-color:var(--sd-color-white) !important;border-color:var(--sd-color-white) !important;border-width:1px !important;border-style:solid !important}.sd-btn-white:hover,.sd-btn-white:focus{color:var(--sd-color-white-text) !important;background-color:var(--sd-color-white-highlight) !important;border-color:var(--sd-color-white-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-white{color:var(--sd-color-white) !important;border-color:var(--sd-color-white) !important;border-width:1px !important;border-style:solid !important}.sd-stretched-link::after{position:absolute;top:0;right:0;bottom:0;left:0;z-index:1;content:""}.sd-hide-link-text{font-size:0}.sd-octicon,.sd-material-icon{display:inline-block;fill:currentColor;vertical-align:middle}.sd-avatar-xs{border-radius:50%;object-fit:cover;object-position:center;width:1rem;height:1rem}.sd-avatar-sm{border-radius:50%;object-fit:cover;object-position:center;width:3rem;height:3rem}.sd-avatar-md{border-radius:50%;object-fit:cover;object-position:center;width:5rem;height:5rem}.sd-avatar-lg{border-radius:50%;object-fit:cover;object-position:center;width:7rem;height:7rem}.sd-avatar-xl{border-radius:50%;object-fit:cover;object-position:center;width:10rem;height:10rem}.sd-avatar-inherit{border-radius:50%;object-fit:cover;object-position:center;width:inherit;height:inherit}.sd-avatar-initial{border-radius:50%;object-fit:cover;object-position:center;width:initial;height:initial}.sd-card{background-clip:border-box;background-color:var(--sd-color-card-background);border:1px solid var(--sd-color-card-border);border-radius:.25rem;color:var(--sd-color-card-text);display:-ms-flexbox;display:flex;-ms-flex-direction:column;flex-direction:column;min-width:0;position:relative;word-wrap:break-word}.sd-card>hr{margin-left:0;margin-right:0}.sd-card-hover:hover{border-color:var(--sd-color-card-border-hover);transform:scale(1.01)}.sd-card-body{-ms-flex:1 1 auto;flex:1 1 auto;padding:1rem 1rem}.sd-card-title{margin-bottom:.5rem}.sd-card-subtitle{margin-top:-0.25rem;margin-bottom:0}.sd-card-text:last-child{margin-bottom:0}.sd-card-link:hover{text-decoration:none}.sd-card-link+.card-link{margin-left:1rem}.sd-card-header{padding:.5rem 1rem;margin-bottom:0;background-color:var(--sd-color-card-header);border-bottom:1px solid var(--sd-color-card-border)}.sd-card-header:first-child{border-radius:calc(0.25rem - 1px) calc(0.25rem - 1px) 0 0}.sd-card-footer{padding:.5rem 1rem;background-color:var(--sd-color-card-footer);border-top:1px solid var(--sd-color-card-border)}.sd-card-footer:last-child{border-radius:0 0 calc(0.25rem - 1px) calc(0.25rem - 1px)}.sd-card-header-tabs{margin-right:-0.5rem;margin-bottom:-0.5rem;margin-left:-0.5rem;border-bottom:0}.sd-card-header-pills{margin-right:-0.5rem;margin-left:-0.5rem}.sd-card-img-overlay{position:absolute;top:0;right:0;bottom:0;left:0;padding:1rem;border-radius:calc(0.25rem - 1px)}.sd-card-img,.sd-card-img-bottom,.sd-card-img-top{width:100%}.sd-card-img,.sd-card-img-top{border-top-left-radius:calc(0.25rem - 1px);border-top-right-radius:calc(0.25rem - 1px)}.sd-card-img,.sd-card-img-bottom{border-bottom-left-radius:calc(0.25rem - 1px);border-bottom-right-radius:calc(0.25rem - 1px)}.sd-cards-carousel{width:100%;display:flex;flex-wrap:nowrap;-ms-flex-direction:row;flex-direction:row;overflow-x:hidden;scroll-snap-type:x mandatory}.sd-cards-carousel.sd-show-scrollbar{overflow-x:auto}.sd-cards-carousel:hover,.sd-cards-carousel:focus{overflow-x:auto}.sd-cards-carousel>.sd-card{flex-shrink:0;scroll-snap-align:start}.sd-cards-carousel>.sd-card:not(:last-child){margin-right:3px}.sd-card-cols-1>.sd-card{width:90%}.sd-card-cols-2>.sd-card{width:45%}.sd-card-cols-3>.sd-card{width:30%}.sd-card-cols-4>.sd-card{width:22.5%}.sd-card-cols-5>.sd-card{width:18%}.sd-card-cols-6>.sd-card{width:15%}.sd-card-cols-7>.sd-card{width:12.8571428571%}.sd-card-cols-8>.sd-card{width:11.25%}.sd-card-cols-9>.sd-card{width:10%}.sd-card-cols-10>.sd-card{width:9%}.sd-card-cols-11>.sd-card{width:8.1818181818%}.sd-card-cols-12>.sd-card{width:7.5%}.sd-container,.sd-container-fluid,.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container-xl{margin-left:auto;margin-right:auto;padding-left:var(--sd-gutter-x, 0.75rem);padding-right:var(--sd-gutter-x, 0.75rem);width:100%}@media(min-width: 576px){.sd-container-sm,.sd-container{max-width:540px}}@media(min-width: 768px){.sd-container-md,.sd-container-sm,.sd-container{max-width:720px}}@media(min-width: 992px){.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container{max-width:960px}}@media(min-width: 1200px){.sd-container-xl,.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container{max-width:1140px}}.sd-row{--sd-gutter-x: 1.5rem;--sd-gutter-y: 0;display:-ms-flexbox;display:flex;-ms-flex-wrap:wrap;flex-wrap:wrap;margin-top:calc(var(--sd-gutter-y) * -1);margin-right:calc(var(--sd-gutter-x) * -0.5);margin-left:calc(var(--sd-gutter-x) * -0.5)}.sd-row>*{box-sizing:border-box;flex-shrink:0;width:100%;max-width:100%;padding-right:calc(var(--sd-gutter-x) * 0.5);padding-left:calc(var(--sd-gutter-x) * 0.5);margin-top:var(--sd-gutter-y)}.sd-col{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-auto>*{flex:0 0 auto;width:auto}.sd-row-cols-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}@media(min-width: 576px){.sd-col-sm{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-sm-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-sm-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-sm-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-sm-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-sm-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-sm-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-sm-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-sm-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-sm-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-sm-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-sm-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-sm-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-sm-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 768px){.sd-col-md{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-md-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-md-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-md-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-md-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-md-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-md-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-md-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-md-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-md-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-md-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-md-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-md-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-md-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 992px){.sd-col-lg{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-lg-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-lg-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-lg-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-lg-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-lg-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-lg-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-lg-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-lg-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-lg-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-lg-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-lg-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-lg-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-lg-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 1200px){.sd-col-xl{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-xl-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-xl-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-xl-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-xl-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-xl-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-xl-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-xl-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-xl-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-xl-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-xl-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-xl-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-xl-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-xl-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}.sd-col-auto{flex:0 0 auto;-ms-flex:0 0 auto;width:auto}.sd-col-1{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}.sd-col-2{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-col-3{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-col-4{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-col-5{flex:0 0 auto;-ms-flex:0 0 auto;width:41.6666666667%}.sd-col-6{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-col-7{flex:0 0 auto;-ms-flex:0 0 auto;width:58.3333333333%}.sd-col-8{flex:0 0 auto;-ms-flex:0 0 auto;width:66.6666666667%}.sd-col-9{flex:0 0 auto;-ms-flex:0 0 auto;width:75%}.sd-col-10{flex:0 0 auto;-ms-flex:0 0 auto;width:83.3333333333%}.sd-col-11{flex:0 0 auto;-ms-flex:0 0 auto;width:91.6666666667%}.sd-col-12{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-g-0,.sd-gy-0{--sd-gutter-y: 0}.sd-g-0,.sd-gx-0{--sd-gutter-x: 0}.sd-g-1,.sd-gy-1{--sd-gutter-y: 0.25rem}.sd-g-1,.sd-gx-1{--sd-gutter-x: 0.25rem}.sd-g-2,.sd-gy-2{--sd-gutter-y: 0.5rem}.sd-g-2,.sd-gx-2{--sd-gutter-x: 0.5rem}.sd-g-3,.sd-gy-3{--sd-gutter-y: 1rem}.sd-g-3,.sd-gx-3{--sd-gutter-x: 1rem}.sd-g-4,.sd-gy-4{--sd-gutter-y: 1.5rem}.sd-g-4,.sd-gx-4{--sd-gutter-x: 1.5rem}.sd-g-5,.sd-gy-5{--sd-gutter-y: 3rem}.sd-g-5,.sd-gx-5{--sd-gutter-x: 3rem}@media(min-width: 576px){.sd-col-sm-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-sm-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-sm-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-sm-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-sm-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-sm-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-sm-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-sm-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-sm-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-sm-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-sm-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-sm-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-sm-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-sm-0,.sd-gy-sm-0{--sd-gutter-y: 0}.sd-g-sm-0,.sd-gx-sm-0{--sd-gutter-x: 0}.sd-g-sm-1,.sd-gy-sm-1{--sd-gutter-y: 0.25rem}.sd-g-sm-1,.sd-gx-sm-1{--sd-gutter-x: 0.25rem}.sd-g-sm-2,.sd-gy-sm-2{--sd-gutter-y: 0.5rem}.sd-g-sm-2,.sd-gx-sm-2{--sd-gutter-x: 0.5rem}.sd-g-sm-3,.sd-gy-sm-3{--sd-gutter-y: 1rem}.sd-g-sm-3,.sd-gx-sm-3{--sd-gutter-x: 1rem}.sd-g-sm-4,.sd-gy-sm-4{--sd-gutter-y: 1.5rem}.sd-g-sm-4,.sd-gx-sm-4{--sd-gutter-x: 1.5rem}.sd-g-sm-5,.sd-gy-sm-5{--sd-gutter-y: 3rem}.sd-g-sm-5,.sd-gx-sm-5{--sd-gutter-x: 3rem}}@media(min-width: 768px){.sd-col-md-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-md-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-md-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-md-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-md-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-md-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-md-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-md-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-md-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-md-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-md-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-md-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-md-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-md-0,.sd-gy-md-0{--sd-gutter-y: 0}.sd-g-md-0,.sd-gx-md-0{--sd-gutter-x: 0}.sd-g-md-1,.sd-gy-md-1{--sd-gutter-y: 0.25rem}.sd-g-md-1,.sd-gx-md-1{--sd-gutter-x: 0.25rem}.sd-g-md-2,.sd-gy-md-2{--sd-gutter-y: 0.5rem}.sd-g-md-2,.sd-gx-md-2{--sd-gutter-x: 0.5rem}.sd-g-md-3,.sd-gy-md-3{--sd-gutter-y: 1rem}.sd-g-md-3,.sd-gx-md-3{--sd-gutter-x: 1rem}.sd-g-md-4,.sd-gy-md-4{--sd-gutter-y: 1.5rem}.sd-g-md-4,.sd-gx-md-4{--sd-gutter-x: 1.5rem}.sd-g-md-5,.sd-gy-md-5{--sd-gutter-y: 3rem}.sd-g-md-5,.sd-gx-md-5{--sd-gutter-x: 3rem}}@media(min-width: 992px){.sd-col-lg-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-lg-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-lg-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-lg-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-lg-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-lg-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-lg-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-lg-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-lg-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-lg-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-lg-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-lg-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-lg-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-lg-0,.sd-gy-lg-0{--sd-gutter-y: 0}.sd-g-lg-0,.sd-gx-lg-0{--sd-gutter-x: 0}.sd-g-lg-1,.sd-gy-lg-1{--sd-gutter-y: 0.25rem}.sd-g-lg-1,.sd-gx-lg-1{--sd-gutter-x: 0.25rem}.sd-g-lg-2,.sd-gy-lg-2{--sd-gutter-y: 0.5rem}.sd-g-lg-2,.sd-gx-lg-2{--sd-gutter-x: 0.5rem}.sd-g-lg-3,.sd-gy-lg-3{--sd-gutter-y: 1rem}.sd-g-lg-3,.sd-gx-lg-3{--sd-gutter-x: 1rem}.sd-g-lg-4,.sd-gy-lg-4{--sd-gutter-y: 1.5rem}.sd-g-lg-4,.sd-gx-lg-4{--sd-gutter-x: 1.5rem}.sd-g-lg-5,.sd-gy-lg-5{--sd-gutter-y: 3rem}.sd-g-lg-5,.sd-gx-lg-5{--sd-gutter-x: 3rem}}@media(min-width: 1200px){.sd-col-xl-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-xl-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-xl-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-xl-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-xl-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-xl-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-xl-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-xl-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-xl-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-xl-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-xl-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-xl-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-xl-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-xl-0,.sd-gy-xl-0{--sd-gutter-y: 0}.sd-g-xl-0,.sd-gx-xl-0{--sd-gutter-x: 0}.sd-g-xl-1,.sd-gy-xl-1{--sd-gutter-y: 0.25rem}.sd-g-xl-1,.sd-gx-xl-1{--sd-gutter-x: 0.25rem}.sd-g-xl-2,.sd-gy-xl-2{--sd-gutter-y: 0.5rem}.sd-g-xl-2,.sd-gx-xl-2{--sd-gutter-x: 0.5rem}.sd-g-xl-3,.sd-gy-xl-3{--sd-gutter-y: 1rem}.sd-g-xl-3,.sd-gx-xl-3{--sd-gutter-x: 1rem}.sd-g-xl-4,.sd-gy-xl-4{--sd-gutter-y: 1.5rem}.sd-g-xl-4,.sd-gx-xl-4{--sd-gutter-x: 1.5rem}.sd-g-xl-5,.sd-gy-xl-5{--sd-gutter-y: 3rem}.sd-g-xl-5,.sd-gx-xl-5{--sd-gutter-x: 3rem}}.sd-flex-row-reverse{flex-direction:row-reverse !important}details.sd-dropdown{position:relative}details.sd-dropdown .sd-summary-title{font-weight:700;padding-right:3em !important;-moz-user-select:none;-ms-user-select:none;-webkit-user-select:none;user-select:none}details.sd-dropdown:hover{cursor:pointer}details.sd-dropdown .sd-summary-content{cursor:default}details.sd-dropdown summary{list-style:none;padding:1em}details.sd-dropdown summary .sd-octicon.no-title{vertical-align:middle}details.sd-dropdown[open] summary .sd-octicon.no-title{visibility:hidden}details.sd-dropdown summary::-webkit-details-marker{display:none}details.sd-dropdown summary:focus{outline:none}details.sd-dropdown .sd-summary-icon{margin-right:.5em}details.sd-dropdown .sd-summary-icon svg{opacity:.8}details.sd-dropdown summary:hover .sd-summary-up svg,details.sd-dropdown summary:hover .sd-summary-down svg{opacity:1;transform:scale(1.1)}details.sd-dropdown .sd-summary-up svg,details.sd-dropdown .sd-summary-down svg{display:block;opacity:.6}details.sd-dropdown .sd-summary-up,details.sd-dropdown .sd-summary-down{pointer-events:none;position:absolute;right:1em;top:1em}details.sd-dropdown[open]>.sd-summary-title .sd-summary-down{visibility:hidden}details.sd-dropdown:not([open])>.sd-summary-title .sd-summary-up{visibility:hidden}details.sd-dropdown:not([open]).sd-card{border:none}details.sd-dropdown:not([open])>.sd-card-header{border:1px solid var(--sd-color-card-border);border-radius:.25rem}details.sd-dropdown.sd-fade-in[open] summary~*{-moz-animation:sd-fade-in .5s ease-in-out;-webkit-animation:sd-fade-in .5s ease-in-out;animation:sd-fade-in .5s ease-in-out}details.sd-dropdown.sd-fade-in-slide-down[open] summary~*{-moz-animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out;-webkit-animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out;animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out}.sd-col>.sd-dropdown{width:100%}.sd-summary-content>.sd-tab-set:first-child{margin-top:0}@keyframes sd-fade-in{0%{opacity:0}100%{opacity:1}}@keyframes sd-slide-down{0%{transform:translate(0, -10px)}100%{transform:translate(0, 0)}}.sd-tab-set{border-radius:.125rem;display:flex;flex-wrap:wrap;margin:1em 0;position:relative}.sd-tab-set>input{opacity:0;position:absolute}.sd-tab-set>input:checked+label{border-color:var(--sd-color-tabs-underline-active);color:var(--sd-color-tabs-label-active)}.sd-tab-set>input:checked+label+.sd-tab-content{display:block}.sd-tab-set>input:not(:checked)+label:hover{color:var(--sd-color-tabs-label-hover);border-color:var(--sd-color-tabs-underline-hover)}.sd-tab-set>input:focus+label{outline-style:auto}.sd-tab-set>input:not(.focus-visible)+label{outline:none;-webkit-tap-highlight-color:transparent}.sd-tab-set>label{border-bottom:.125rem solid transparent;margin-bottom:0;color:var(--sd-color-tabs-label-inactive);border-color:var(--sd-color-tabs-underline-inactive);cursor:pointer;font-size:var(--sd-fontsize-tabs-label);font-weight:700;padding:1em 1.25em .5em;transition:color 250ms;width:auto;z-index:1}html .sd-tab-set>label:hover{color:var(--sd-color-tabs-label-active)}.sd-col>.sd-tab-set{width:100%}.sd-tab-content{box-shadow:0 -0.0625rem var(--sd-color-tabs-overline),0 .0625rem var(--sd-color-tabs-underline);display:none;order:99;padding-bottom:.75rem;padding-top:.75rem;width:100%}.sd-tab-content>:first-child{margin-top:0 !important}.sd-tab-content>:last-child{margin-bottom:0 !important}.sd-tab-content>.sd-tab-set{margin:0}.sd-sphinx-override,.sd-sphinx-override *{-moz-box-sizing:border-box;-webkit-box-sizing:border-box;box-sizing:border-box}.sd-sphinx-override p{margin-top:0}:root{--sd-color-primary: #0071bc;--sd-color-secondary: #6c757d;--sd-color-success: #28a745;--sd-color-info: #17a2b8;--sd-color-warning: #f0b37e;--sd-color-danger: #dc3545;--sd-color-light: #f8f9fa;--sd-color-muted: #6c757d;--sd-color-dark: #212529;--sd-color-black: black;--sd-color-white: white;--sd-color-primary-highlight: #0060a0;--sd-color-secondary-highlight: #5c636a;--sd-color-success-highlight: #228e3b;--sd-color-info-highlight: #148a9c;--sd-color-warning-highlight: #cc986b;--sd-color-danger-highlight: #bb2d3b;--sd-color-light-highlight: #d3d4d5;--sd-color-muted-highlight: #5c636a;--sd-color-dark-highlight: #1c1f23;--sd-color-black-highlight: black;--sd-color-white-highlight: #d9d9d9;--sd-color-primary-text: #fff;--sd-color-secondary-text: #fff;--sd-color-success-text: #fff;--sd-color-info-text: #fff;--sd-color-warning-text: #212529;--sd-color-danger-text: #fff;--sd-color-light-text: #212529;--sd-color-muted-text: #fff;--sd-color-dark-text: #fff;--sd-color-black-text: #fff;--sd-color-white-text: #212529;--sd-color-shadow: rgba(0, 0, 0, 0.15);--sd-color-card-border: rgba(0, 0, 0, 0.125);--sd-color-card-border-hover: hsla(231, 99%, 66%, 1);--sd-color-card-background: transparent;--sd-color-card-text: inherit;--sd-color-card-header: transparent;--sd-color-card-footer: transparent;--sd-color-tabs-label-active: hsla(231, 99%, 66%, 1);--sd-color-tabs-label-hover: hsla(231, 99%, 66%, 1);--sd-color-tabs-label-inactive: hsl(0, 0%, 66%);--sd-color-tabs-underline-active: hsla(231, 99%, 66%, 1);--sd-color-tabs-underline-hover: rgba(178, 206, 245, 0.62);--sd-color-tabs-underline-inactive: transparent;--sd-color-tabs-overline: rgb(222, 222, 222);--sd-color-tabs-underline: rgb(222, 222, 222);--sd-fontsize-tabs-label: 1rem} +.sd-bg-primary{background-color:var(--sd-color-primary) !important}.sd-bg-text-primary{color:var(--sd-color-primary-text) !important}button.sd-bg-primary:focus,button.sd-bg-primary:hover{background-color:var(--sd-color-primary-highlight) !important}a.sd-bg-primary:focus,a.sd-bg-primary:hover{background-color:var(--sd-color-primary-highlight) !important}.sd-bg-secondary{background-color:var(--sd-color-secondary) !important}.sd-bg-text-secondary{color:var(--sd-color-secondary-text) !important}button.sd-bg-secondary:focus,button.sd-bg-secondary:hover{background-color:var(--sd-color-secondary-highlight) !important}a.sd-bg-secondary:focus,a.sd-bg-secondary:hover{background-color:var(--sd-color-secondary-highlight) !important}.sd-bg-success{background-color:var(--sd-color-success) !important}.sd-bg-text-success{color:var(--sd-color-success-text) !important}button.sd-bg-success:focus,button.sd-bg-success:hover{background-color:var(--sd-color-success-highlight) !important}a.sd-bg-success:focus,a.sd-bg-success:hover{background-color:var(--sd-color-success-highlight) !important}.sd-bg-info{background-color:var(--sd-color-info) !important}.sd-bg-text-info{color:var(--sd-color-info-text) !important}button.sd-bg-info:focus,button.sd-bg-info:hover{background-color:var(--sd-color-info-highlight) !important}a.sd-bg-info:focus,a.sd-bg-info:hover{background-color:var(--sd-color-info-highlight) !important}.sd-bg-warning{background-color:var(--sd-color-warning) !important}.sd-bg-text-warning{color:var(--sd-color-warning-text) !important}button.sd-bg-warning:focus,button.sd-bg-warning:hover{background-color:var(--sd-color-warning-highlight) !important}a.sd-bg-warning:focus,a.sd-bg-warning:hover{background-color:var(--sd-color-warning-highlight) !important}.sd-bg-danger{background-color:var(--sd-color-danger) !important}.sd-bg-text-danger{color:var(--sd-color-danger-text) !important}button.sd-bg-danger:focus,button.sd-bg-danger:hover{background-color:var(--sd-color-danger-highlight) !important}a.sd-bg-danger:focus,a.sd-bg-danger:hover{background-color:var(--sd-color-danger-highlight) !important}.sd-bg-light{background-color:var(--sd-color-light) !important}.sd-bg-text-light{color:var(--sd-color-light-text) !important}button.sd-bg-light:focus,button.sd-bg-light:hover{background-color:var(--sd-color-light-highlight) !important}a.sd-bg-light:focus,a.sd-bg-light:hover{background-color:var(--sd-color-light-highlight) !important}.sd-bg-muted{background-color:var(--sd-color-muted) !important}.sd-bg-text-muted{color:var(--sd-color-muted-text) !important}button.sd-bg-muted:focus,button.sd-bg-muted:hover{background-color:var(--sd-color-muted-highlight) !important}a.sd-bg-muted:focus,a.sd-bg-muted:hover{background-color:var(--sd-color-muted-highlight) !important}.sd-bg-dark{background-color:var(--sd-color-dark) !important}.sd-bg-text-dark{color:var(--sd-color-dark-text) !important}button.sd-bg-dark:focus,button.sd-bg-dark:hover{background-color:var(--sd-color-dark-highlight) !important}a.sd-bg-dark:focus,a.sd-bg-dark:hover{background-color:var(--sd-color-dark-highlight) !important}.sd-bg-black{background-color:var(--sd-color-black) !important}.sd-bg-text-black{color:var(--sd-color-black-text) !important}button.sd-bg-black:focus,button.sd-bg-black:hover{background-color:var(--sd-color-black-highlight) !important}a.sd-bg-black:focus,a.sd-bg-black:hover{background-color:var(--sd-color-black-highlight) !important}.sd-bg-white{background-color:var(--sd-color-white) !important}.sd-bg-text-white{color:var(--sd-color-white-text) !important}button.sd-bg-white:focus,button.sd-bg-white:hover{background-color:var(--sd-color-white-highlight) !important}a.sd-bg-white:focus,a.sd-bg-white:hover{background-color:var(--sd-color-white-highlight) !important}.sd-text-primary,.sd-text-primary>p{color:var(--sd-color-primary) !important}a.sd-text-primary:focus,a.sd-text-primary:hover{color:var(--sd-color-primary-highlight) !important}.sd-text-secondary,.sd-text-secondary>p{color:var(--sd-color-secondary) !important}a.sd-text-secondary:focus,a.sd-text-secondary:hover{color:var(--sd-color-secondary-highlight) !important}.sd-text-success,.sd-text-success>p{color:var(--sd-color-success) !important}a.sd-text-success:focus,a.sd-text-success:hover{color:var(--sd-color-success-highlight) !important}.sd-text-info,.sd-text-info>p{color:var(--sd-color-info) !important}a.sd-text-info:focus,a.sd-text-info:hover{color:var(--sd-color-info-highlight) !important}.sd-text-warning,.sd-text-warning>p{color:var(--sd-color-warning) !important}a.sd-text-warning:focus,a.sd-text-warning:hover{color:var(--sd-color-warning-highlight) !important}.sd-text-danger,.sd-text-danger>p{color:var(--sd-color-danger) !important}a.sd-text-danger:focus,a.sd-text-danger:hover{color:var(--sd-color-danger-highlight) !important}.sd-text-light,.sd-text-light>p{color:var(--sd-color-light) !important}a.sd-text-light:focus,a.sd-text-light:hover{color:var(--sd-color-light-highlight) !important}.sd-text-muted,.sd-text-muted>p{color:var(--sd-color-muted) !important}a.sd-text-muted:focus,a.sd-text-muted:hover{color:var(--sd-color-muted-highlight) !important}.sd-text-dark,.sd-text-dark>p{color:var(--sd-color-dark) !important}a.sd-text-dark:focus,a.sd-text-dark:hover{color:var(--sd-color-dark-highlight) !important}.sd-text-black,.sd-text-black>p{color:var(--sd-color-black) !important}a.sd-text-black:focus,a.sd-text-black:hover{color:var(--sd-color-black-highlight) !important}.sd-text-white,.sd-text-white>p{color:var(--sd-color-white) !important}a.sd-text-white:focus,a.sd-text-white:hover{color:var(--sd-color-white-highlight) !important}.sd-outline-primary{border-color:var(--sd-color-primary) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-primary:focus,a.sd-outline-primary:hover{border-color:var(--sd-color-primary-highlight) !important}.sd-outline-secondary{border-color:var(--sd-color-secondary) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-secondary:focus,a.sd-outline-secondary:hover{border-color:var(--sd-color-secondary-highlight) !important}.sd-outline-success{border-color:var(--sd-color-success) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-success:focus,a.sd-outline-success:hover{border-color:var(--sd-color-success-highlight) !important}.sd-outline-info{border-color:var(--sd-color-info) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-info:focus,a.sd-outline-info:hover{border-color:var(--sd-color-info-highlight) !important}.sd-outline-warning{border-color:var(--sd-color-warning) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-warning:focus,a.sd-outline-warning:hover{border-color:var(--sd-color-warning-highlight) !important}.sd-outline-danger{border-color:var(--sd-color-danger) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-danger:focus,a.sd-outline-danger:hover{border-color:var(--sd-color-danger-highlight) !important}.sd-outline-light{border-color:var(--sd-color-light) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-light:focus,a.sd-outline-light:hover{border-color:var(--sd-color-light-highlight) !important}.sd-outline-muted{border-color:var(--sd-color-muted) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-muted:focus,a.sd-outline-muted:hover{border-color:var(--sd-color-muted-highlight) !important}.sd-outline-dark{border-color:var(--sd-color-dark) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-dark:focus,a.sd-outline-dark:hover{border-color:var(--sd-color-dark-highlight) !important}.sd-outline-black{border-color:var(--sd-color-black) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-black:focus,a.sd-outline-black:hover{border-color:var(--sd-color-black-highlight) !important}.sd-outline-white{border-color:var(--sd-color-white) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-white:focus,a.sd-outline-white:hover{border-color:var(--sd-color-white-highlight) !important}.sd-bg-transparent{background-color:transparent !important}.sd-outline-transparent{border-color:transparent !important}.sd-text-transparent{color:transparent !important}.sd-p-0{padding:0 !important}.sd-pt-0,.sd-py-0{padding-top:0 !important}.sd-pr-0,.sd-px-0{padding-right:0 !important}.sd-pb-0,.sd-py-0{padding-bottom:0 !important}.sd-pl-0,.sd-px-0{padding-left:0 !important}.sd-p-1{padding:.25rem !important}.sd-pt-1,.sd-py-1{padding-top:.25rem !important}.sd-pr-1,.sd-px-1{padding-right:.25rem !important}.sd-pb-1,.sd-py-1{padding-bottom:.25rem !important}.sd-pl-1,.sd-px-1{padding-left:.25rem !important}.sd-p-2{padding:.5rem !important}.sd-pt-2,.sd-py-2{padding-top:.5rem !important}.sd-pr-2,.sd-px-2{padding-right:.5rem !important}.sd-pb-2,.sd-py-2{padding-bottom:.5rem !important}.sd-pl-2,.sd-px-2{padding-left:.5rem !important}.sd-p-3{padding:1rem !important}.sd-pt-3,.sd-py-3{padding-top:1rem !important}.sd-pr-3,.sd-px-3{padding-right:1rem !important}.sd-pb-3,.sd-py-3{padding-bottom:1rem !important}.sd-pl-3,.sd-px-3{padding-left:1rem !important}.sd-p-4{padding:1.5rem !important}.sd-pt-4,.sd-py-4{padding-top:1.5rem !important}.sd-pr-4,.sd-px-4{padding-right:1.5rem !important}.sd-pb-4,.sd-py-4{padding-bottom:1.5rem !important}.sd-pl-4,.sd-px-4{padding-left:1.5rem !important}.sd-p-5{padding:3rem !important}.sd-pt-5,.sd-py-5{padding-top:3rem !important}.sd-pr-5,.sd-px-5{padding-right:3rem !important}.sd-pb-5,.sd-py-5{padding-bottom:3rem !important}.sd-pl-5,.sd-px-5{padding-left:3rem !important}.sd-m-auto{margin:auto !important}.sd-mt-auto,.sd-my-auto{margin-top:auto !important}.sd-mr-auto,.sd-mx-auto{margin-right:auto !important}.sd-mb-auto,.sd-my-auto{margin-bottom:auto !important}.sd-ml-auto,.sd-mx-auto{margin-left:auto !important}.sd-m-0{margin:0 !important}.sd-mt-0,.sd-my-0{margin-top:0 !important}.sd-mr-0,.sd-mx-0{margin-right:0 !important}.sd-mb-0,.sd-my-0{margin-bottom:0 !important}.sd-ml-0,.sd-mx-0{margin-left:0 !important}.sd-m-1{margin:.25rem !important}.sd-mt-1,.sd-my-1{margin-top:.25rem !important}.sd-mr-1,.sd-mx-1{margin-right:.25rem !important}.sd-mb-1,.sd-my-1{margin-bottom:.25rem !important}.sd-ml-1,.sd-mx-1{margin-left:.25rem !important}.sd-m-2{margin:.5rem !important}.sd-mt-2,.sd-my-2{margin-top:.5rem !important}.sd-mr-2,.sd-mx-2{margin-right:.5rem !important}.sd-mb-2,.sd-my-2{margin-bottom:.5rem !important}.sd-ml-2,.sd-mx-2{margin-left:.5rem !important}.sd-m-3{margin:1rem !important}.sd-mt-3,.sd-my-3{margin-top:1rem !important}.sd-mr-3,.sd-mx-3{margin-right:1rem !important}.sd-mb-3,.sd-my-3{margin-bottom:1rem !important}.sd-ml-3,.sd-mx-3{margin-left:1rem !important}.sd-m-4{margin:1.5rem !important}.sd-mt-4,.sd-my-4{margin-top:1.5rem !important}.sd-mr-4,.sd-mx-4{margin-right:1.5rem !important}.sd-mb-4,.sd-my-4{margin-bottom:1.5rem !important}.sd-ml-4,.sd-mx-4{margin-left:1.5rem !important}.sd-m-5{margin:3rem !important}.sd-mt-5,.sd-my-5{margin-top:3rem !important}.sd-mr-5,.sd-mx-5{margin-right:3rem !important}.sd-mb-5,.sd-my-5{margin-bottom:3rem !important}.sd-ml-5,.sd-mx-5{margin-left:3rem !important}.sd-w-25{width:25% !important}.sd-w-50{width:50% !important}.sd-w-75{width:75% !important}.sd-w-100{width:100% !important}.sd-w-auto{width:auto !important}.sd-h-25{height:25% !important}.sd-h-50{height:50% !important}.sd-h-75{height:75% !important}.sd-h-100{height:100% !important}.sd-h-auto{height:auto !important}.sd-d-none{display:none !important}.sd-d-inline{display:inline !important}.sd-d-inline-block{display:inline-block !important}.sd-d-block{display:block !important}.sd-d-grid{display:grid !important}.sd-d-flex-row{display:-ms-flexbox !important;display:flex !important;flex-direction:row !important}.sd-d-flex-column{display:-ms-flexbox !important;display:flex !important;flex-direction:column !important}.sd-d-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}@media(min-width: 576px){.sd-d-sm-none{display:none !important}.sd-d-sm-inline{display:inline !important}.sd-d-sm-inline-block{display:inline-block !important}.sd-d-sm-block{display:block !important}.sd-d-sm-grid{display:grid !important}.sd-d-sm-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-sm-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 768px){.sd-d-md-none{display:none !important}.sd-d-md-inline{display:inline !important}.sd-d-md-inline-block{display:inline-block !important}.sd-d-md-block{display:block !important}.sd-d-md-grid{display:grid !important}.sd-d-md-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-md-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 992px){.sd-d-lg-none{display:none !important}.sd-d-lg-inline{display:inline !important}.sd-d-lg-inline-block{display:inline-block !important}.sd-d-lg-block{display:block !important}.sd-d-lg-grid{display:grid !important}.sd-d-lg-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-lg-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 1200px){.sd-d-xl-none{display:none !important}.sd-d-xl-inline{display:inline !important}.sd-d-xl-inline-block{display:inline-block !important}.sd-d-xl-block{display:block !important}.sd-d-xl-grid{display:grid !important}.sd-d-xl-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-xl-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}.sd-align-major-start{justify-content:flex-start !important}.sd-align-major-end{justify-content:flex-end !important}.sd-align-major-center{justify-content:center !important}.sd-align-major-justify{justify-content:space-between !important}.sd-align-major-spaced{justify-content:space-evenly !important}.sd-align-minor-start{align-items:flex-start !important}.sd-align-minor-end{align-items:flex-end !important}.sd-align-minor-center{align-items:center !important}.sd-align-minor-stretch{align-items:stretch !important}.sd-text-justify{text-align:justify !important}.sd-text-left{text-align:left !important}.sd-text-right{text-align:right !important}.sd-text-center{text-align:center !important}.sd-font-weight-light{font-weight:300 !important}.sd-font-weight-lighter{font-weight:lighter !important}.sd-font-weight-normal{font-weight:400 !important}.sd-font-weight-bold{font-weight:700 !important}.sd-font-weight-bolder{font-weight:bolder !important}.sd-font-italic{font-style:italic !important}.sd-text-decoration-none{text-decoration:none !important}.sd-text-lowercase{text-transform:lowercase !important}.sd-text-uppercase{text-transform:uppercase !important}.sd-text-capitalize{text-transform:capitalize !important}.sd-text-wrap{white-space:normal !important}.sd-text-nowrap{white-space:nowrap !important}.sd-text-truncate{overflow:hidden;text-overflow:ellipsis;white-space:nowrap}.sd-fs-1,.sd-fs-1>p{font-size:calc(1.375rem + 1.5vw) !important;line-height:unset !important}.sd-fs-2,.sd-fs-2>p{font-size:calc(1.325rem + 0.9vw) !important;line-height:unset !important}.sd-fs-3,.sd-fs-3>p{font-size:calc(1.3rem + 0.6vw) !important;line-height:unset !important}.sd-fs-4,.sd-fs-4>p{font-size:calc(1.275rem + 0.3vw) !important;line-height:unset !important}.sd-fs-5,.sd-fs-5>p{font-size:1.25rem !important;line-height:unset !important}.sd-fs-6,.sd-fs-6>p{font-size:1rem !important;line-height:unset !important}.sd-border-0{border:0 solid !important}.sd-border-top-0{border-top:0 solid !important}.sd-border-bottom-0{border-bottom:0 solid !important}.sd-border-right-0{border-right:0 solid !important}.sd-border-left-0{border-left:0 solid !important}.sd-border-1{border:1px solid !important}.sd-border-top-1{border-top:1px solid !important}.sd-border-bottom-1{border-bottom:1px solid !important}.sd-border-right-1{border-right:1px solid !important}.sd-border-left-1{border-left:1px solid !important}.sd-border-2{border:2px solid !important}.sd-border-top-2{border-top:2px solid !important}.sd-border-bottom-2{border-bottom:2px solid !important}.sd-border-right-2{border-right:2px solid !important}.sd-border-left-2{border-left:2px solid !important}.sd-border-3{border:3px solid !important}.sd-border-top-3{border-top:3px solid !important}.sd-border-bottom-3{border-bottom:3px solid !important}.sd-border-right-3{border-right:3px solid !important}.sd-border-left-3{border-left:3px solid !important}.sd-border-4{border:4px solid !important}.sd-border-top-4{border-top:4px solid !important}.sd-border-bottom-4{border-bottom:4px solid !important}.sd-border-right-4{border-right:4px solid !important}.sd-border-left-4{border-left:4px solid !important}.sd-border-5{border:5px solid !important}.sd-border-top-5{border-top:5px solid !important}.sd-border-bottom-5{border-bottom:5px solid !important}.sd-border-right-5{border-right:5px solid !important}.sd-border-left-5{border-left:5px solid !important}.sd-rounded-0{border-radius:0 !important}.sd-rounded-1{border-radius:.2rem !important}.sd-rounded-2{border-radius:.3rem !important}.sd-rounded-3{border-radius:.5rem !important}.sd-rounded-pill{border-radius:50rem !important}.sd-rounded-circle{border-radius:50% !important}.shadow-none{box-shadow:none !important}.sd-shadow-sm{box-shadow:0 .125rem .25rem var(--sd-color-shadow) !important}.sd-shadow-md{box-shadow:0 .5rem 1rem var(--sd-color-shadow) !important}.sd-shadow-lg{box-shadow:0 1rem 3rem var(--sd-color-shadow) !important}@keyframes sd-slide-from-left{0%{transform:translateX(-100%)}100%{transform:translateX(0)}}@keyframes sd-slide-from-right{0%{transform:translateX(200%)}100%{transform:translateX(0)}}@keyframes sd-grow100{0%{transform:scale(0);opacity:.5}100%{transform:scale(1);opacity:1}}@keyframes sd-grow50{0%{transform:scale(0.5);opacity:.5}100%{transform:scale(1);opacity:1}}@keyframes sd-grow50-rot20{0%{transform:scale(0.5) rotateZ(-20deg);opacity:.5}75%{transform:scale(1) rotateZ(5deg);opacity:1}95%{transform:scale(1) rotateZ(-1deg);opacity:1}100%{transform:scale(1) rotateZ(0);opacity:1}}.sd-animate-slide-from-left{animation:1s ease-out 0s 1 normal none running sd-slide-from-left}.sd-animate-slide-from-right{animation:1s ease-out 0s 1 normal none running sd-slide-from-right}.sd-animate-grow100{animation:1s ease-out 0s 1 normal none running sd-grow100}.sd-animate-grow50{animation:1s ease-out 0s 1 normal none running sd-grow50}.sd-animate-grow50-rot20{animation:1s ease-out 0s 1 normal none running sd-grow50-rot20}.sd-badge{display:inline-block;padding:.35em .65em;font-size:.75em;font-weight:700;line-height:1;text-align:center;white-space:nowrap;vertical-align:baseline;border-radius:.25rem}.sd-badge:empty{display:none}a.sd-badge{text-decoration:none}.sd-btn .sd-badge{position:relative;top:-1px}.sd-btn{background-color:transparent;border:1px solid transparent;border-radius:.25rem;cursor:pointer;display:inline-block;font-weight:400;font-size:1rem;line-height:1.5;padding:.375rem .75rem;text-align:center;text-decoration:none;transition:color .15s ease-in-out,background-color .15s ease-in-out,border-color .15s ease-in-out,box-shadow .15s ease-in-out;vertical-align:middle;user-select:none;-moz-user-select:none;-ms-user-select:none;-webkit-user-select:none}.sd-btn:hover{text-decoration:none}@media(prefers-reduced-motion: reduce){.sd-btn{transition:none}}.sd-btn-primary,.sd-btn-outline-primary:hover,.sd-btn-outline-primary:focus{color:var(--sd-color-primary-text) !important;background-color:var(--sd-color-primary) !important;border-color:var(--sd-color-primary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-primary:hover,.sd-btn-primary:focus{color:var(--sd-color-primary-text) !important;background-color:var(--sd-color-primary-highlight) !important;border-color:var(--sd-color-primary-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-primary{color:var(--sd-color-primary) !important;border-color:var(--sd-color-primary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-secondary,.sd-btn-outline-secondary:hover,.sd-btn-outline-secondary:focus{color:var(--sd-color-secondary-text) !important;background-color:var(--sd-color-secondary) !important;border-color:var(--sd-color-secondary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-secondary:hover,.sd-btn-secondary:focus{color:var(--sd-color-secondary-text) !important;background-color:var(--sd-color-secondary-highlight) !important;border-color:var(--sd-color-secondary-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-secondary{color:var(--sd-color-secondary) !important;border-color:var(--sd-color-secondary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-success,.sd-btn-outline-success:hover,.sd-btn-outline-success:focus{color:var(--sd-color-success-text) !important;background-color:var(--sd-color-success) !important;border-color:var(--sd-color-success) !important;border-width:1px !important;border-style:solid !important}.sd-btn-success:hover,.sd-btn-success:focus{color:var(--sd-color-success-text) !important;background-color:var(--sd-color-success-highlight) !important;border-color:var(--sd-color-success-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-success{color:var(--sd-color-success) !important;border-color:var(--sd-color-success) !important;border-width:1px !important;border-style:solid !important}.sd-btn-info,.sd-btn-outline-info:hover,.sd-btn-outline-info:focus{color:var(--sd-color-info-text) !important;background-color:var(--sd-color-info) !important;border-color:var(--sd-color-info) !important;border-width:1px !important;border-style:solid !important}.sd-btn-info:hover,.sd-btn-info:focus{color:var(--sd-color-info-text) !important;background-color:var(--sd-color-info-highlight) !important;border-color:var(--sd-color-info-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-info{color:var(--sd-color-info) !important;border-color:var(--sd-color-info) !important;border-width:1px !important;border-style:solid !important}.sd-btn-warning,.sd-btn-outline-warning:hover,.sd-btn-outline-warning:focus{color:var(--sd-color-warning-text) !important;background-color:var(--sd-color-warning) !important;border-color:var(--sd-color-warning) !important;border-width:1px !important;border-style:solid !important}.sd-btn-warning:hover,.sd-btn-warning:focus{color:var(--sd-color-warning-text) !important;background-color:var(--sd-color-warning-highlight) !important;border-color:var(--sd-color-warning-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-warning{color:var(--sd-color-warning) !important;border-color:var(--sd-color-warning) !important;border-width:1px !important;border-style:solid !important}.sd-btn-danger,.sd-btn-outline-danger:hover,.sd-btn-outline-danger:focus{color:var(--sd-color-danger-text) !important;background-color:var(--sd-color-danger) !important;border-color:var(--sd-color-danger) !important;border-width:1px !important;border-style:solid !important}.sd-btn-danger:hover,.sd-btn-danger:focus{color:var(--sd-color-danger-text) !important;background-color:var(--sd-color-danger-highlight) !important;border-color:var(--sd-color-danger-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-danger{color:var(--sd-color-danger) !important;border-color:var(--sd-color-danger) !important;border-width:1px !important;border-style:solid !important}.sd-btn-light,.sd-btn-outline-light:hover,.sd-btn-outline-light:focus{color:var(--sd-color-light-text) !important;background-color:var(--sd-color-light) !important;border-color:var(--sd-color-light) !important;border-width:1px !important;border-style:solid !important}.sd-btn-light:hover,.sd-btn-light:focus{color:var(--sd-color-light-text) !important;background-color:var(--sd-color-light-highlight) !important;border-color:var(--sd-color-light-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-light{color:var(--sd-color-light) !important;border-color:var(--sd-color-light) !important;border-width:1px !important;border-style:solid !important}.sd-btn-muted,.sd-btn-outline-muted:hover,.sd-btn-outline-muted:focus{color:var(--sd-color-muted-text) !important;background-color:var(--sd-color-muted) !important;border-color:var(--sd-color-muted) !important;border-width:1px !important;border-style:solid !important}.sd-btn-muted:hover,.sd-btn-muted:focus{color:var(--sd-color-muted-text) !important;background-color:var(--sd-color-muted-highlight) !important;border-color:var(--sd-color-muted-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-muted{color:var(--sd-color-muted) !important;border-color:var(--sd-color-muted) !important;border-width:1px !important;border-style:solid !important}.sd-btn-dark,.sd-btn-outline-dark:hover,.sd-btn-outline-dark:focus{color:var(--sd-color-dark-text) !important;background-color:var(--sd-color-dark) !important;border-color:var(--sd-color-dark) !important;border-width:1px !important;border-style:solid !important}.sd-btn-dark:hover,.sd-btn-dark:focus{color:var(--sd-color-dark-text) !important;background-color:var(--sd-color-dark-highlight) !important;border-color:var(--sd-color-dark-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-dark{color:var(--sd-color-dark) !important;border-color:var(--sd-color-dark) !important;border-width:1px !important;border-style:solid !important}.sd-btn-black,.sd-btn-outline-black:hover,.sd-btn-outline-black:focus{color:var(--sd-color-black-text) !important;background-color:var(--sd-color-black) !important;border-color:var(--sd-color-black) !important;border-width:1px !important;border-style:solid !important}.sd-btn-black:hover,.sd-btn-black:focus{color:var(--sd-color-black-text) !important;background-color:var(--sd-color-black-highlight) !important;border-color:var(--sd-color-black-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-black{color:var(--sd-color-black) !important;border-color:var(--sd-color-black) !important;border-width:1px !important;border-style:solid !important}.sd-btn-white,.sd-btn-outline-white:hover,.sd-btn-outline-white:focus{color:var(--sd-color-white-text) !important;background-color:var(--sd-color-white) !important;border-color:var(--sd-color-white) !important;border-width:1px !important;border-style:solid !important}.sd-btn-white:hover,.sd-btn-white:focus{color:var(--sd-color-white-text) !important;background-color:var(--sd-color-white-highlight) !important;border-color:var(--sd-color-white-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-white{color:var(--sd-color-white) !important;border-color:var(--sd-color-white) !important;border-width:1px !important;border-style:solid !important}.sd-stretched-link::after{position:absolute;top:0;right:0;bottom:0;left:0;z-index:1;content:""}.sd-hide-link-text{font-size:0}.sd-octicon,.sd-material-icon{display:inline-block;fill:currentColor;vertical-align:middle}.sd-avatar-xs{border-radius:50%;object-fit:cover;object-position:center;width:1rem;height:1rem}.sd-avatar-sm{border-radius:50%;object-fit:cover;object-position:center;width:3rem;height:3rem}.sd-avatar-md{border-radius:50%;object-fit:cover;object-position:center;width:5rem;height:5rem}.sd-avatar-lg{border-radius:50%;object-fit:cover;object-position:center;width:7rem;height:7rem}.sd-avatar-xl{border-radius:50%;object-fit:cover;object-position:center;width:10rem;height:10rem}.sd-avatar-inherit{border-radius:50%;object-fit:cover;object-position:center;width:inherit;height:inherit}.sd-avatar-initial{border-radius:50%;object-fit:cover;object-position:center;width:initial;height:initial}.sd-card{background-clip:border-box;background-color:var(--sd-color-card-background);border:1px solid var(--sd-color-card-border);border-radius:.25rem;color:var(--sd-color-card-text);display:-ms-flexbox;display:flex;-ms-flex-direction:column;flex-direction:column;min-width:0;position:relative;word-wrap:break-word}.sd-card>hr{margin-left:0;margin-right:0}.sd-card-hover:hover{border-color:var(--sd-color-card-border-hover);transform:scale(1.01)}.sd-card-body{-ms-flex:1 1 auto;flex:1 1 auto;padding:1rem 1rem}.sd-card-title{margin-bottom:.5rem}.sd-card-subtitle{margin-top:-0.25rem;margin-bottom:0}.sd-card-text:last-child{margin-bottom:0}.sd-card-link:hover{text-decoration:none}.sd-card-link+.card-link{margin-left:1rem}.sd-card-header{padding:.5rem 1rem;margin-bottom:0;background-color:var(--sd-color-card-header);border-bottom:1px solid var(--sd-color-card-border)}.sd-card-header:first-child{border-radius:calc(0.25rem - 1px) calc(0.25rem - 1px) 0 0}.sd-card-footer{padding:.5rem 1rem;background-color:var(--sd-color-card-footer);border-top:1px solid var(--sd-color-card-border)}.sd-card-footer:last-child{border-radius:0 0 calc(0.25rem - 1px) calc(0.25rem - 1px)}.sd-card-header-tabs{margin-right:-0.5rem;margin-bottom:-0.5rem;margin-left:-0.5rem;border-bottom:0}.sd-card-header-pills{margin-right:-0.5rem;margin-left:-0.5rem}.sd-card-img-overlay{position:absolute;top:0;right:0;bottom:0;left:0;padding:1rem;border-radius:calc(0.25rem - 1px)}.sd-card-img,.sd-card-img-bottom,.sd-card-img-top{width:100%}.sd-card-img,.sd-card-img-top{border-top-left-radius:calc(0.25rem - 1px);border-top-right-radius:calc(0.25rem - 1px)}.sd-card-img,.sd-card-img-bottom{border-bottom-left-radius:calc(0.25rem - 1px);border-bottom-right-radius:calc(0.25rem - 1px)}.sd-cards-carousel{width:100%;display:flex;flex-wrap:nowrap;-ms-flex-direction:row;flex-direction:row;overflow-x:hidden;scroll-snap-type:x mandatory}.sd-cards-carousel.sd-show-scrollbar{overflow-x:auto}.sd-cards-carousel:hover,.sd-cards-carousel:focus{overflow-x:auto}.sd-cards-carousel>.sd-card{flex-shrink:0;scroll-snap-align:start}.sd-cards-carousel>.sd-card:not(:last-child){margin-right:3px}.sd-card-cols-1>.sd-card{width:90%}.sd-card-cols-2>.sd-card{width:45%}.sd-card-cols-3>.sd-card{width:30%}.sd-card-cols-4>.sd-card{width:22.5%}.sd-card-cols-5>.sd-card{width:18%}.sd-card-cols-6>.sd-card{width:15%}.sd-card-cols-7>.sd-card{width:12.8571428571%}.sd-card-cols-8>.sd-card{width:11.25%}.sd-card-cols-9>.sd-card{width:10%}.sd-card-cols-10>.sd-card{width:9%}.sd-card-cols-11>.sd-card{width:8.1818181818%}.sd-card-cols-12>.sd-card{width:7.5%}.sd-container,.sd-container-fluid,.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container-xl{margin-left:auto;margin-right:auto;padding-left:var(--sd-gutter-x, 0.75rem);padding-right:var(--sd-gutter-x, 0.75rem);width:100%}@media(min-width: 576px){.sd-container-sm,.sd-container{max-width:540px}}@media(min-width: 768px){.sd-container-md,.sd-container-sm,.sd-container{max-width:720px}}@media(min-width: 992px){.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container{max-width:960px}}@media(min-width: 1200px){.sd-container-xl,.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container{max-width:1140px}}.sd-row{--sd-gutter-x: 1.5rem;--sd-gutter-y: 0;display:-ms-flexbox;display:flex;-ms-flex-wrap:wrap;flex-wrap:wrap;margin-top:calc(var(--sd-gutter-y) * -1);margin-right:calc(var(--sd-gutter-x) * -0.5);margin-left:calc(var(--sd-gutter-x) * -0.5)}.sd-row>*{box-sizing:border-box;flex-shrink:0;width:100%;max-width:100%;padding-right:calc(var(--sd-gutter-x) * 0.5);padding-left:calc(var(--sd-gutter-x) * 0.5);margin-top:var(--sd-gutter-y)}.sd-col{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-auto>*{flex:0 0 auto;width:auto}.sd-row-cols-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}@media(min-width: 576px){.sd-col-sm{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-sm-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-sm-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-sm-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-sm-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-sm-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-sm-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-sm-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-sm-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-sm-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-sm-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-sm-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-sm-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-sm-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 768px){.sd-col-md{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-md-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-md-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-md-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-md-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-md-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-md-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-md-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-md-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-md-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-md-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-md-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-md-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-md-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 992px){.sd-col-lg{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-lg-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-lg-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-lg-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-lg-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-lg-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-lg-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-lg-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-lg-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-lg-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-lg-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-lg-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-lg-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-lg-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 1200px){.sd-col-xl{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-xl-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-xl-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-xl-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-xl-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-xl-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-xl-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-xl-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-xl-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-xl-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-xl-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-xl-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-xl-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-xl-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}.sd-col-auto{flex:0 0 auto;-ms-flex:0 0 auto;width:auto}.sd-col-1{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}.sd-col-2{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-col-3{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-col-4{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-col-5{flex:0 0 auto;-ms-flex:0 0 auto;width:41.6666666667%}.sd-col-6{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-col-7{flex:0 0 auto;-ms-flex:0 0 auto;width:58.3333333333%}.sd-col-8{flex:0 0 auto;-ms-flex:0 0 auto;width:66.6666666667%}.sd-col-9{flex:0 0 auto;-ms-flex:0 0 auto;width:75%}.sd-col-10{flex:0 0 auto;-ms-flex:0 0 auto;width:83.3333333333%}.sd-col-11{flex:0 0 auto;-ms-flex:0 0 auto;width:91.6666666667%}.sd-col-12{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-g-0,.sd-gy-0{--sd-gutter-y: 0}.sd-g-0,.sd-gx-0{--sd-gutter-x: 0}.sd-g-1,.sd-gy-1{--sd-gutter-y: 0.25rem}.sd-g-1,.sd-gx-1{--sd-gutter-x: 0.25rem}.sd-g-2,.sd-gy-2{--sd-gutter-y: 0.5rem}.sd-g-2,.sd-gx-2{--sd-gutter-x: 0.5rem}.sd-g-3,.sd-gy-3{--sd-gutter-y: 1rem}.sd-g-3,.sd-gx-3{--sd-gutter-x: 1rem}.sd-g-4,.sd-gy-4{--sd-gutter-y: 1.5rem}.sd-g-4,.sd-gx-4{--sd-gutter-x: 1.5rem}.sd-g-5,.sd-gy-5{--sd-gutter-y: 3rem}.sd-g-5,.sd-gx-5{--sd-gutter-x: 3rem}@media(min-width: 576px){.sd-col-sm-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-sm-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-sm-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-sm-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-sm-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-sm-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-sm-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-sm-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-sm-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-sm-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-sm-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-sm-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-sm-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-sm-0,.sd-gy-sm-0{--sd-gutter-y: 0}.sd-g-sm-0,.sd-gx-sm-0{--sd-gutter-x: 0}.sd-g-sm-1,.sd-gy-sm-1{--sd-gutter-y: 0.25rem}.sd-g-sm-1,.sd-gx-sm-1{--sd-gutter-x: 0.25rem}.sd-g-sm-2,.sd-gy-sm-2{--sd-gutter-y: 0.5rem}.sd-g-sm-2,.sd-gx-sm-2{--sd-gutter-x: 0.5rem}.sd-g-sm-3,.sd-gy-sm-3{--sd-gutter-y: 1rem}.sd-g-sm-3,.sd-gx-sm-3{--sd-gutter-x: 1rem}.sd-g-sm-4,.sd-gy-sm-4{--sd-gutter-y: 1.5rem}.sd-g-sm-4,.sd-gx-sm-4{--sd-gutter-x: 1.5rem}.sd-g-sm-5,.sd-gy-sm-5{--sd-gutter-y: 3rem}.sd-g-sm-5,.sd-gx-sm-5{--sd-gutter-x: 3rem}}@media(min-width: 768px){.sd-col-md-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-md-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-md-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-md-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-md-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-md-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-md-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-md-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-md-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-md-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-md-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-md-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-md-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-md-0,.sd-gy-md-0{--sd-gutter-y: 0}.sd-g-md-0,.sd-gx-md-0{--sd-gutter-x: 0}.sd-g-md-1,.sd-gy-md-1{--sd-gutter-y: 0.25rem}.sd-g-md-1,.sd-gx-md-1{--sd-gutter-x: 0.25rem}.sd-g-md-2,.sd-gy-md-2{--sd-gutter-y: 0.5rem}.sd-g-md-2,.sd-gx-md-2{--sd-gutter-x: 0.5rem}.sd-g-md-3,.sd-gy-md-3{--sd-gutter-y: 1rem}.sd-g-md-3,.sd-gx-md-3{--sd-gutter-x: 1rem}.sd-g-md-4,.sd-gy-md-4{--sd-gutter-y: 1.5rem}.sd-g-md-4,.sd-gx-md-4{--sd-gutter-x: 1.5rem}.sd-g-md-5,.sd-gy-md-5{--sd-gutter-y: 3rem}.sd-g-md-5,.sd-gx-md-5{--sd-gutter-x: 3rem}}@media(min-width: 992px){.sd-col-lg-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-lg-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-lg-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-lg-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-lg-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-lg-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-lg-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-lg-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-lg-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-lg-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-lg-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-lg-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-lg-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-lg-0,.sd-gy-lg-0{--sd-gutter-y: 0}.sd-g-lg-0,.sd-gx-lg-0{--sd-gutter-x: 0}.sd-g-lg-1,.sd-gy-lg-1{--sd-gutter-y: 0.25rem}.sd-g-lg-1,.sd-gx-lg-1{--sd-gutter-x: 0.25rem}.sd-g-lg-2,.sd-gy-lg-2{--sd-gutter-y: 0.5rem}.sd-g-lg-2,.sd-gx-lg-2{--sd-gutter-x: 0.5rem}.sd-g-lg-3,.sd-gy-lg-3{--sd-gutter-y: 1rem}.sd-g-lg-3,.sd-gx-lg-3{--sd-gutter-x: 1rem}.sd-g-lg-4,.sd-gy-lg-4{--sd-gutter-y: 1.5rem}.sd-g-lg-4,.sd-gx-lg-4{--sd-gutter-x: 1.5rem}.sd-g-lg-5,.sd-gy-lg-5{--sd-gutter-y: 3rem}.sd-g-lg-5,.sd-gx-lg-5{--sd-gutter-x: 3rem}}@media(min-width: 1200px){.sd-col-xl-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-xl-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-xl-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-xl-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-xl-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-xl-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-xl-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-xl-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-xl-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-xl-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-xl-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-xl-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-xl-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-xl-0,.sd-gy-xl-0{--sd-gutter-y: 0}.sd-g-xl-0,.sd-gx-xl-0{--sd-gutter-x: 0}.sd-g-xl-1,.sd-gy-xl-1{--sd-gutter-y: 0.25rem}.sd-g-xl-1,.sd-gx-xl-1{--sd-gutter-x: 0.25rem}.sd-g-xl-2,.sd-gy-xl-2{--sd-gutter-y: 0.5rem}.sd-g-xl-2,.sd-gx-xl-2{--sd-gutter-x: 0.5rem}.sd-g-xl-3,.sd-gy-xl-3{--sd-gutter-y: 1rem}.sd-g-xl-3,.sd-gx-xl-3{--sd-gutter-x: 1rem}.sd-g-xl-4,.sd-gy-xl-4{--sd-gutter-y: 1.5rem}.sd-g-xl-4,.sd-gx-xl-4{--sd-gutter-x: 1.5rem}.sd-g-xl-5,.sd-gy-xl-5{--sd-gutter-y: 3rem}.sd-g-xl-5,.sd-gx-xl-5{--sd-gutter-x: 3rem}}.sd-flex-row-reverse{flex-direction:row-reverse !important}details.sd-dropdown{position:relative;font-size:var(--sd-fontsize-dropdown)}details.sd-dropdown:hover{cursor:pointer}details.sd-dropdown .sd-summary-content{cursor:default}details.sd-dropdown summary.sd-summary-title{padding:.5em 1em;font-size:var(--sd-fontsize-dropdown-title);font-weight:var(--sd-fontweight-dropdown-title);user-select:none;-moz-user-select:none;-ms-user-select:none;-webkit-user-select:none;list-style:none;display:inline-flex;justify-content:space-between}details.sd-dropdown summary.sd-summary-title::-webkit-details-marker{display:none}details.sd-dropdown summary.sd-summary-title:focus{outline:none}details.sd-dropdown summary.sd-summary-title .sd-summary-icon{margin-right:.6em;display:inline-flex;align-items:center}details.sd-dropdown summary.sd-summary-title .sd-summary-icon svg{opacity:.8}details.sd-dropdown summary.sd-summary-title .sd-summary-text{flex-grow:1;line-height:1.5;padding-right:.5rem}details.sd-dropdown summary.sd-summary-title .sd-summary-state-marker{pointer-events:none;display:inline-flex;align-items:center}details.sd-dropdown summary.sd-summary-title .sd-summary-state-marker svg{opacity:.6}details.sd-dropdown summary.sd-summary-title:hover .sd-summary-state-marker svg{opacity:1;transform:scale(1.1)}details.sd-dropdown[open] summary .sd-octicon.no-title{visibility:hidden}details.sd-dropdown .sd-summary-chevron-right{transition:.25s}details.sd-dropdown[open]>.sd-summary-title .sd-summary-chevron-right{transform:rotate(90deg)}details.sd-dropdown[open]>.sd-summary-title .sd-summary-chevron-down{transform:rotate(180deg)}details.sd-dropdown:not([open]).sd-card{border:none}details.sd-dropdown:not([open])>.sd-card-header{border:1px solid var(--sd-color-card-border);border-radius:.25rem}details.sd-dropdown.sd-fade-in[open] summary~*{-moz-animation:sd-fade-in .5s ease-in-out;-webkit-animation:sd-fade-in .5s ease-in-out;animation:sd-fade-in .5s ease-in-out}details.sd-dropdown.sd-fade-in-slide-down[open] summary~*{-moz-animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out;-webkit-animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out;animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out}.sd-col>.sd-dropdown{width:100%}.sd-summary-content>.sd-tab-set:first-child{margin-top:0}@keyframes sd-fade-in{0%{opacity:0}100%{opacity:1}}@keyframes sd-slide-down{0%{transform:translate(0, -10px)}100%{transform:translate(0, 0)}}.sd-tab-set{border-radius:.125rem;display:flex;flex-wrap:wrap;margin:1em 0;position:relative}.sd-tab-set>input{opacity:0;position:absolute}.sd-tab-set>input:checked+label{border-color:var(--sd-color-tabs-underline-active);color:var(--sd-color-tabs-label-active)}.sd-tab-set>input:checked+label+.sd-tab-content{display:block}.sd-tab-set>input:not(:checked)+label:hover{color:var(--sd-color-tabs-label-hover);border-color:var(--sd-color-tabs-underline-hover)}.sd-tab-set>input:focus+label{outline-style:auto}.sd-tab-set>input:not(.focus-visible)+label{outline:none;-webkit-tap-highlight-color:transparent}.sd-tab-set>label{border-bottom:.125rem solid transparent;margin-bottom:0;color:var(--sd-color-tabs-label-inactive);border-color:var(--sd-color-tabs-underline-inactive);cursor:pointer;font-size:var(--sd-fontsize-tabs-label);font-weight:700;padding:1em 1.25em .5em;transition:color 250ms;width:auto;z-index:1}html .sd-tab-set>label:hover{color:var(--sd-color-tabs-label-active)}.sd-col>.sd-tab-set{width:100%}.sd-tab-content{box-shadow:0 -0.0625rem var(--sd-color-tabs-overline),0 .0625rem var(--sd-color-tabs-underline);display:none;order:99;padding-bottom:.75rem;padding-top:.75rem;width:100%}.sd-tab-content>:first-child{margin-top:0 !important}.sd-tab-content>:last-child{margin-bottom:0 !important}.sd-tab-content>.sd-tab-set{margin:0}.sd-sphinx-override,.sd-sphinx-override *{-moz-box-sizing:border-box;-webkit-box-sizing:border-box;box-sizing:border-box}.sd-sphinx-override p{margin-top:0}:root{--sd-color-primary: #0071bc;--sd-color-secondary: #6c757d;--sd-color-success: #28a745;--sd-color-info: #17a2b8;--sd-color-warning: #f0b37e;--sd-color-danger: #dc3545;--sd-color-light: #f8f9fa;--sd-color-muted: #6c757d;--sd-color-dark: #212529;--sd-color-black: black;--sd-color-white: white;--sd-color-primary-highlight: #0060a0;--sd-color-secondary-highlight: #5c636a;--sd-color-success-highlight: #228e3b;--sd-color-info-highlight: #148a9c;--sd-color-warning-highlight: #cc986b;--sd-color-danger-highlight: #bb2d3b;--sd-color-light-highlight: #d3d4d5;--sd-color-muted-highlight: #5c636a;--sd-color-dark-highlight: #1c1f23;--sd-color-black-highlight: black;--sd-color-white-highlight: #d9d9d9;--sd-color-primary-bg: rgba(0, 113, 188, 0.2);--sd-color-secondary-bg: rgba(108, 117, 125, 0.2);--sd-color-success-bg: rgba(40, 167, 69, 0.2);--sd-color-info-bg: rgba(23, 162, 184, 0.2);--sd-color-warning-bg: rgba(240, 179, 126, 0.2);--sd-color-danger-bg: rgba(220, 53, 69, 0.2);--sd-color-light-bg: rgba(248, 249, 250, 0.2);--sd-color-muted-bg: rgba(108, 117, 125, 0.2);--sd-color-dark-bg: rgba(33, 37, 41, 0.2);--sd-color-black-bg: rgba(0, 0, 0, 0.2);--sd-color-white-bg: rgba(255, 255, 255, 0.2);--sd-color-primary-text: #fff;--sd-color-secondary-text: #fff;--sd-color-success-text: #fff;--sd-color-info-text: #fff;--sd-color-warning-text: #212529;--sd-color-danger-text: #fff;--sd-color-light-text: #212529;--sd-color-muted-text: #fff;--sd-color-dark-text: #fff;--sd-color-black-text: #fff;--sd-color-white-text: #212529;--sd-color-shadow: rgba(0, 0, 0, 0.15);--sd-color-card-border: rgba(0, 0, 0, 0.125);--sd-color-card-border-hover: hsla(231, 99%, 66%, 1);--sd-color-card-background: transparent;--sd-color-card-text: inherit;--sd-color-card-header: transparent;--sd-color-card-footer: transparent;--sd-color-tabs-label-active: hsla(231, 99%, 66%, 1);--sd-color-tabs-label-hover: hsla(231, 99%, 66%, 1);--sd-color-tabs-label-inactive: hsl(0, 0%, 66%);--sd-color-tabs-underline-active: hsla(231, 99%, 66%, 1);--sd-color-tabs-underline-hover: rgba(178, 206, 245, 0.62);--sd-color-tabs-underline-inactive: transparent;--sd-color-tabs-overline: rgb(222, 222, 222);--sd-color-tabs-underline: rgb(222, 222, 222);--sd-fontsize-tabs-label: 1rem;--sd-fontsize-dropdown: inherit;--sd-fontsize-dropdown-title: 1rem;--sd-fontweight-dropdown-title: 700} diff --git a/docs/_static/basic.css b/docs/_static/basic.css index 7243282d..7d5974c3 100644 --- a/docs/_static/basic.css +++ b/docs/_static/basic.css @@ -236,7 +236,6 @@ div.body p, div.body dd, div.body li, div.body blockquote { a.headerlink { visibility: hidden; } - a.brackets:before, span.brackets > a:before{ content: "["; @@ -247,6 +246,7 @@ span.brackets > a:after { content: "]"; } + h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, @@ -334,13 +334,11 @@ aside.sidebar { p.sidebar-title { font-weight: bold; } - div.admonition, div.topic, blockquote { clear: left; } /* -- topics ---------------------------------------------------------------- */ - div.topic { border: 1px solid #ccc; padding: 7px; diff --git a/docs/_sphinx_design_static/design-style.1e8bd061cd6da7fc9cf755528e8ffc24.min.css b/docs/_static/sphinx-design.5ea377869091fd0449014c60fc090103.min.css similarity index 87% rename from docs/_sphinx_design_static/design-style.1e8bd061cd6da7fc9cf755528e8ffc24.min.css rename to docs/_static/sphinx-design.5ea377869091fd0449014c60fc090103.min.css index eb19f698..a325746f 100644 --- a/docs/_sphinx_design_static/design-style.1e8bd061cd6da7fc9cf755528e8ffc24.min.css +++ b/docs/_static/sphinx-design.5ea377869091fd0449014c60fc090103.min.css @@ -1 +1 @@ -.sd-bg-primary{background-color:var(--sd-color-primary) !important}.sd-bg-text-primary{color:var(--sd-color-primary-text) !important}button.sd-bg-primary:focus,button.sd-bg-primary:hover{background-color:var(--sd-color-primary-highlight) !important}a.sd-bg-primary:focus,a.sd-bg-primary:hover{background-color:var(--sd-color-primary-highlight) !important}.sd-bg-secondary{background-color:var(--sd-color-secondary) !important}.sd-bg-text-secondary{color:var(--sd-color-secondary-text) !important}button.sd-bg-secondary:focus,button.sd-bg-secondary:hover{background-color:var(--sd-color-secondary-highlight) !important}a.sd-bg-secondary:focus,a.sd-bg-secondary:hover{background-color:var(--sd-color-secondary-highlight) !important}.sd-bg-success{background-color:var(--sd-color-success) !important}.sd-bg-text-success{color:var(--sd-color-success-text) !important}button.sd-bg-success:focus,button.sd-bg-success:hover{background-color:var(--sd-color-success-highlight) !important}a.sd-bg-success:focus,a.sd-bg-success:hover{background-color:var(--sd-color-success-highlight) !important}.sd-bg-info{background-color:var(--sd-color-info) !important}.sd-bg-text-info{color:var(--sd-color-info-text) !important}button.sd-bg-info:focus,button.sd-bg-info:hover{background-color:var(--sd-color-info-highlight) !important}a.sd-bg-info:focus,a.sd-bg-info:hover{background-color:var(--sd-color-info-highlight) !important}.sd-bg-warning{background-color:var(--sd-color-warning) !important}.sd-bg-text-warning{color:var(--sd-color-warning-text) !important}button.sd-bg-warning:focus,button.sd-bg-warning:hover{background-color:var(--sd-color-warning-highlight) !important}a.sd-bg-warning:focus,a.sd-bg-warning:hover{background-color:var(--sd-color-warning-highlight) !important}.sd-bg-danger{background-color:var(--sd-color-danger) !important}.sd-bg-text-danger{color:var(--sd-color-danger-text) !important}button.sd-bg-danger:focus,button.sd-bg-danger:hover{background-color:var(--sd-color-danger-highlight) !important}a.sd-bg-danger:focus,a.sd-bg-danger:hover{background-color:var(--sd-color-danger-highlight) !important}.sd-bg-light{background-color:var(--sd-color-light) !important}.sd-bg-text-light{color:var(--sd-color-light-text) !important}button.sd-bg-light:focus,button.sd-bg-light:hover{background-color:var(--sd-color-light-highlight) !important}a.sd-bg-light:focus,a.sd-bg-light:hover{background-color:var(--sd-color-light-highlight) !important}.sd-bg-muted{background-color:var(--sd-color-muted) !important}.sd-bg-text-muted{color:var(--sd-color-muted-text) !important}button.sd-bg-muted:focus,button.sd-bg-muted:hover{background-color:var(--sd-color-muted-highlight) !important}a.sd-bg-muted:focus,a.sd-bg-muted:hover{background-color:var(--sd-color-muted-highlight) !important}.sd-bg-dark{background-color:var(--sd-color-dark) !important}.sd-bg-text-dark{color:var(--sd-color-dark-text) !important}button.sd-bg-dark:focus,button.sd-bg-dark:hover{background-color:var(--sd-color-dark-highlight) !important}a.sd-bg-dark:focus,a.sd-bg-dark:hover{background-color:var(--sd-color-dark-highlight) !important}.sd-bg-black{background-color:var(--sd-color-black) !important}.sd-bg-text-black{color:var(--sd-color-black-text) !important}button.sd-bg-black:focus,button.sd-bg-black:hover{background-color:var(--sd-color-black-highlight) !important}a.sd-bg-black:focus,a.sd-bg-black:hover{background-color:var(--sd-color-black-highlight) !important}.sd-bg-white{background-color:var(--sd-color-white) !important}.sd-bg-text-white{color:var(--sd-color-white-text) !important}button.sd-bg-white:focus,button.sd-bg-white:hover{background-color:var(--sd-color-white-highlight) !important}a.sd-bg-white:focus,a.sd-bg-white:hover{background-color:var(--sd-color-white-highlight) !important}.sd-text-primary,.sd-text-primary>p{color:var(--sd-color-primary) !important}a.sd-text-primary:focus,a.sd-text-primary:hover{color:var(--sd-color-primary-highlight) !important}.sd-text-secondary,.sd-text-secondary>p{color:var(--sd-color-secondary) !important}a.sd-text-secondary:focus,a.sd-text-secondary:hover{color:var(--sd-color-secondary-highlight) !important}.sd-text-success,.sd-text-success>p{color:var(--sd-color-success) !important}a.sd-text-success:focus,a.sd-text-success:hover{color:var(--sd-color-success-highlight) !important}.sd-text-info,.sd-text-info>p{color:var(--sd-color-info) !important}a.sd-text-info:focus,a.sd-text-info:hover{color:var(--sd-color-info-highlight) !important}.sd-text-warning,.sd-text-warning>p{color:var(--sd-color-warning) !important}a.sd-text-warning:focus,a.sd-text-warning:hover{color:var(--sd-color-warning-highlight) !important}.sd-text-danger,.sd-text-danger>p{color:var(--sd-color-danger) !important}a.sd-text-danger:focus,a.sd-text-danger:hover{color:var(--sd-color-danger-highlight) !important}.sd-text-light,.sd-text-light>p{color:var(--sd-color-light) !important}a.sd-text-light:focus,a.sd-text-light:hover{color:var(--sd-color-light-highlight) !important}.sd-text-muted,.sd-text-muted>p{color:var(--sd-color-muted) !important}a.sd-text-muted:focus,a.sd-text-muted:hover{color:var(--sd-color-muted-highlight) !important}.sd-text-dark,.sd-text-dark>p{color:var(--sd-color-dark) !important}a.sd-text-dark:focus,a.sd-text-dark:hover{color:var(--sd-color-dark-highlight) !important}.sd-text-black,.sd-text-black>p{color:var(--sd-color-black) !important}a.sd-text-black:focus,a.sd-text-black:hover{color:var(--sd-color-black-highlight) !important}.sd-text-white,.sd-text-white>p{color:var(--sd-color-white) !important}a.sd-text-white:focus,a.sd-text-white:hover{color:var(--sd-color-white-highlight) !important}.sd-outline-primary{border-color:var(--sd-color-primary) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-primary:focus,a.sd-outline-primary:hover{border-color:var(--sd-color-primary-highlight) !important}.sd-outline-secondary{border-color:var(--sd-color-secondary) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-secondary:focus,a.sd-outline-secondary:hover{border-color:var(--sd-color-secondary-highlight) !important}.sd-outline-success{border-color:var(--sd-color-success) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-success:focus,a.sd-outline-success:hover{border-color:var(--sd-color-success-highlight) !important}.sd-outline-info{border-color:var(--sd-color-info) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-info:focus,a.sd-outline-info:hover{border-color:var(--sd-color-info-highlight) !important}.sd-outline-warning{border-color:var(--sd-color-warning) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-warning:focus,a.sd-outline-warning:hover{border-color:var(--sd-color-warning-highlight) !important}.sd-outline-danger{border-color:var(--sd-color-danger) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-danger:focus,a.sd-outline-danger:hover{border-color:var(--sd-color-danger-highlight) !important}.sd-outline-light{border-color:var(--sd-color-light) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-light:focus,a.sd-outline-light:hover{border-color:var(--sd-color-light-highlight) !important}.sd-outline-muted{border-color:var(--sd-color-muted) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-muted:focus,a.sd-outline-muted:hover{border-color:var(--sd-color-muted-highlight) !important}.sd-outline-dark{border-color:var(--sd-color-dark) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-dark:focus,a.sd-outline-dark:hover{border-color:var(--sd-color-dark-highlight) !important}.sd-outline-black{border-color:var(--sd-color-black) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-black:focus,a.sd-outline-black:hover{border-color:var(--sd-color-black-highlight) !important}.sd-outline-white{border-color:var(--sd-color-white) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-white:focus,a.sd-outline-white:hover{border-color:var(--sd-color-white-highlight) !important}.sd-bg-transparent{background-color:transparent !important}.sd-outline-transparent{border-color:transparent !important}.sd-text-transparent{color:transparent !important}.sd-p-0{padding:0 !important}.sd-pt-0,.sd-py-0{padding-top:0 !important}.sd-pr-0,.sd-px-0{padding-right:0 !important}.sd-pb-0,.sd-py-0{padding-bottom:0 !important}.sd-pl-0,.sd-px-0{padding-left:0 !important}.sd-p-1{padding:.25rem !important}.sd-pt-1,.sd-py-1{padding-top:.25rem !important}.sd-pr-1,.sd-px-1{padding-right:.25rem !important}.sd-pb-1,.sd-py-1{padding-bottom:.25rem !important}.sd-pl-1,.sd-px-1{padding-left:.25rem !important}.sd-p-2{padding:.5rem !important}.sd-pt-2,.sd-py-2{padding-top:.5rem !important}.sd-pr-2,.sd-px-2{padding-right:.5rem !important}.sd-pb-2,.sd-py-2{padding-bottom:.5rem !important}.sd-pl-2,.sd-px-2{padding-left:.5rem !important}.sd-p-3{padding:1rem !important}.sd-pt-3,.sd-py-3{padding-top:1rem !important}.sd-pr-3,.sd-px-3{padding-right:1rem !important}.sd-pb-3,.sd-py-3{padding-bottom:1rem !important}.sd-pl-3,.sd-px-3{padding-left:1rem !important}.sd-p-4{padding:1.5rem !important}.sd-pt-4,.sd-py-4{padding-top:1.5rem !important}.sd-pr-4,.sd-px-4{padding-right:1.5rem !important}.sd-pb-4,.sd-py-4{padding-bottom:1.5rem !important}.sd-pl-4,.sd-px-4{padding-left:1.5rem !important}.sd-p-5{padding:3rem !important}.sd-pt-5,.sd-py-5{padding-top:3rem !important}.sd-pr-5,.sd-px-5{padding-right:3rem !important}.sd-pb-5,.sd-py-5{padding-bottom:3rem !important}.sd-pl-5,.sd-px-5{padding-left:3rem !important}.sd-m-auto{margin:auto !important}.sd-mt-auto,.sd-my-auto{margin-top:auto !important}.sd-mr-auto,.sd-mx-auto{margin-right:auto !important}.sd-mb-auto,.sd-my-auto{margin-bottom:auto !important}.sd-ml-auto,.sd-mx-auto{margin-left:auto !important}.sd-m-0{margin:0 !important}.sd-mt-0,.sd-my-0{margin-top:0 !important}.sd-mr-0,.sd-mx-0{margin-right:0 !important}.sd-mb-0,.sd-my-0{margin-bottom:0 !important}.sd-ml-0,.sd-mx-0{margin-left:0 !important}.sd-m-1{margin:.25rem !important}.sd-mt-1,.sd-my-1{margin-top:.25rem !important}.sd-mr-1,.sd-mx-1{margin-right:.25rem !important}.sd-mb-1,.sd-my-1{margin-bottom:.25rem !important}.sd-ml-1,.sd-mx-1{margin-left:.25rem !important}.sd-m-2{margin:.5rem !important}.sd-mt-2,.sd-my-2{margin-top:.5rem !important}.sd-mr-2,.sd-mx-2{margin-right:.5rem !important}.sd-mb-2,.sd-my-2{margin-bottom:.5rem !important}.sd-ml-2,.sd-mx-2{margin-left:.5rem !important}.sd-m-3{margin:1rem !important}.sd-mt-3,.sd-my-3{margin-top:1rem !important}.sd-mr-3,.sd-mx-3{margin-right:1rem !important}.sd-mb-3,.sd-my-3{margin-bottom:1rem !important}.sd-ml-3,.sd-mx-3{margin-left:1rem !important}.sd-m-4{margin:1.5rem !important}.sd-mt-4,.sd-my-4{margin-top:1.5rem !important}.sd-mr-4,.sd-mx-4{margin-right:1.5rem !important}.sd-mb-4,.sd-my-4{margin-bottom:1.5rem !important}.sd-ml-4,.sd-mx-4{margin-left:1.5rem !important}.sd-m-5{margin:3rem !important}.sd-mt-5,.sd-my-5{margin-top:3rem !important}.sd-mr-5,.sd-mx-5{margin-right:3rem !important}.sd-mb-5,.sd-my-5{margin-bottom:3rem !important}.sd-ml-5,.sd-mx-5{margin-left:3rem !important}.sd-w-25{width:25% !important}.sd-w-50{width:50% !important}.sd-w-75{width:75% !important}.sd-w-100{width:100% !important}.sd-w-auto{width:auto !important}.sd-h-25{height:25% !important}.sd-h-50{height:50% !important}.sd-h-75{height:75% !important}.sd-h-100{height:100% !important}.sd-h-auto{height:auto !important}.sd-d-none{display:none !important}.sd-d-inline{display:inline !important}.sd-d-inline-block{display:inline-block !important}.sd-d-block{display:block !important}.sd-d-grid{display:grid !important}.sd-d-flex-row{display:-ms-flexbox !important;display:flex !important;flex-direction:row !important}.sd-d-flex-column{display:-ms-flexbox !important;display:flex !important;flex-direction:column !important}.sd-d-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}@media(min-width: 576px){.sd-d-sm-none{display:none !important}.sd-d-sm-inline{display:inline !important}.sd-d-sm-inline-block{display:inline-block !important}.sd-d-sm-block{display:block !important}.sd-d-sm-grid{display:grid !important}.sd-d-sm-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-sm-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 768px){.sd-d-md-none{display:none !important}.sd-d-md-inline{display:inline !important}.sd-d-md-inline-block{display:inline-block !important}.sd-d-md-block{display:block !important}.sd-d-md-grid{display:grid !important}.sd-d-md-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-md-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 992px){.sd-d-lg-none{display:none !important}.sd-d-lg-inline{display:inline !important}.sd-d-lg-inline-block{display:inline-block !important}.sd-d-lg-block{display:block !important}.sd-d-lg-grid{display:grid !important}.sd-d-lg-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-lg-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 1200px){.sd-d-xl-none{display:none !important}.sd-d-xl-inline{display:inline !important}.sd-d-xl-inline-block{display:inline-block !important}.sd-d-xl-block{display:block !important}.sd-d-xl-grid{display:grid !important}.sd-d-xl-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-xl-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}.sd-align-major-start{justify-content:flex-start !important}.sd-align-major-end{justify-content:flex-end !important}.sd-align-major-center{justify-content:center !important}.sd-align-major-justify{justify-content:space-between !important}.sd-align-major-spaced{justify-content:space-evenly !important}.sd-align-minor-start{align-items:flex-start !important}.sd-align-minor-end{align-items:flex-end !important}.sd-align-minor-center{align-items:center !important}.sd-align-minor-stretch{align-items:stretch !important}.sd-text-justify{text-align:justify !important}.sd-text-left{text-align:left !important}.sd-text-right{text-align:right !important}.sd-text-center{text-align:center !important}.sd-font-weight-light{font-weight:300 !important}.sd-font-weight-lighter{font-weight:lighter !important}.sd-font-weight-normal{font-weight:400 !important}.sd-font-weight-bold{font-weight:700 !important}.sd-font-weight-bolder{font-weight:bolder !important}.sd-font-italic{font-style:italic !important}.sd-text-decoration-none{text-decoration:none !important}.sd-text-lowercase{text-transform:lowercase !important}.sd-text-uppercase{text-transform:uppercase !important}.sd-text-capitalize{text-transform:capitalize !important}.sd-text-wrap{white-space:normal !important}.sd-text-nowrap{white-space:nowrap !important}.sd-text-truncate{overflow:hidden;text-overflow:ellipsis;white-space:nowrap}.sd-fs-1,.sd-fs-1>p{font-size:calc(1.375rem + 1.5vw) !important;line-height:unset !important}.sd-fs-2,.sd-fs-2>p{font-size:calc(1.325rem + 0.9vw) !important;line-height:unset !important}.sd-fs-3,.sd-fs-3>p{font-size:calc(1.3rem + 0.6vw) !important;line-height:unset !important}.sd-fs-4,.sd-fs-4>p{font-size:calc(1.275rem + 0.3vw) !important;line-height:unset !important}.sd-fs-5,.sd-fs-5>p{font-size:1.25rem !important;line-height:unset !important}.sd-fs-6,.sd-fs-6>p{font-size:1rem !important;line-height:unset !important}.sd-border-0{border:0 solid !important}.sd-border-top-0{border-top:0 solid !important}.sd-border-bottom-0{border-bottom:0 solid !important}.sd-border-right-0{border-right:0 solid !important}.sd-border-left-0{border-left:0 solid !important}.sd-border-1{border:1px solid !important}.sd-border-top-1{border-top:1px solid !important}.sd-border-bottom-1{border-bottom:1px solid !important}.sd-border-right-1{border-right:1px solid !important}.sd-border-left-1{border-left:1px solid !important}.sd-border-2{border:2px solid !important}.sd-border-top-2{border-top:2px solid !important}.sd-border-bottom-2{border-bottom:2px solid !important}.sd-border-right-2{border-right:2px solid !important}.sd-border-left-2{border-left:2px solid !important}.sd-border-3{border:3px solid !important}.sd-border-top-3{border-top:3px solid !important}.sd-border-bottom-3{border-bottom:3px solid !important}.sd-border-right-3{border-right:3px solid !important}.sd-border-left-3{border-left:3px solid !important}.sd-border-4{border:4px solid !important}.sd-border-top-4{border-top:4px solid !important}.sd-border-bottom-4{border-bottom:4px solid !important}.sd-border-right-4{border-right:4px solid !important}.sd-border-left-4{border-left:4px solid !important}.sd-border-5{border:5px solid !important}.sd-border-top-5{border-top:5px solid !important}.sd-border-bottom-5{border-bottom:5px solid !important}.sd-border-right-5{border-right:5px solid !important}.sd-border-left-5{border-left:5px solid !important}.sd-rounded-0{border-radius:0 !important}.sd-rounded-1{border-radius:.2rem !important}.sd-rounded-2{border-radius:.3rem !important}.sd-rounded-3{border-radius:.5rem !important}.sd-rounded-pill{border-radius:50rem !important}.sd-rounded-circle{border-radius:50% !important}.shadow-none{box-shadow:none !important}.sd-shadow-sm{box-shadow:0 .125rem .25rem var(--sd-color-shadow) !important}.sd-shadow-md{box-shadow:0 .5rem 1rem var(--sd-color-shadow) !important}.sd-shadow-lg{box-shadow:0 1rem 3rem var(--sd-color-shadow) !important}@keyframes sd-slide-from-left{0%{transform:translateX(-100%)}100%{transform:translateX(0)}}@keyframes sd-slide-from-right{0%{transform:translateX(200%)}100%{transform:translateX(0)}}@keyframes sd-grow100{0%{transform:scale(0);opacity:.5}100%{transform:scale(1);opacity:1}}@keyframes sd-grow50{0%{transform:scale(0.5);opacity:.5}100%{transform:scale(1);opacity:1}}@keyframes sd-grow50-rot20{0%{transform:scale(0.5) rotateZ(-20deg);opacity:.5}75%{transform:scale(1) rotateZ(5deg);opacity:1}95%{transform:scale(1) rotateZ(-1deg);opacity:1}100%{transform:scale(1) rotateZ(0);opacity:1}}.sd-animate-slide-from-left{animation:1s ease-out 0s 1 normal none running sd-slide-from-left}.sd-animate-slide-from-right{animation:1s ease-out 0s 1 normal none running sd-slide-from-right}.sd-animate-grow100{animation:1s ease-out 0s 1 normal none running sd-grow100}.sd-animate-grow50{animation:1s ease-out 0s 1 normal none running sd-grow50}.sd-animate-grow50-rot20{animation:1s ease-out 0s 1 normal none running sd-grow50-rot20}.sd-badge{display:inline-block;padding:.35em .65em;font-size:.75em;font-weight:700;line-height:1;text-align:center;white-space:nowrap;vertical-align:baseline;border-radius:.25rem}.sd-badge:empty{display:none}a.sd-badge{text-decoration:none}.sd-btn .sd-badge{position:relative;top:-1px}.sd-btn{background-color:transparent;border:1px solid transparent;border-radius:.25rem;cursor:pointer;display:inline-block;font-weight:400;font-size:1rem;line-height:1.5;padding:.375rem .75rem;text-align:center;text-decoration:none;transition:color .15s ease-in-out,background-color .15s ease-in-out,border-color .15s ease-in-out,box-shadow .15s ease-in-out;vertical-align:middle;user-select:none;-moz-user-select:none;-ms-user-select:none;-webkit-user-select:none}.sd-btn:hover{text-decoration:none}@media(prefers-reduced-motion: reduce){.sd-btn{transition:none}}.sd-btn-primary,.sd-btn-outline-primary:hover,.sd-btn-outline-primary:focus{color:var(--sd-color-primary-text) !important;background-color:var(--sd-color-primary) !important;border-color:var(--sd-color-primary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-primary:hover,.sd-btn-primary:focus{color:var(--sd-color-primary-text) !important;background-color:var(--sd-color-primary-highlight) !important;border-color:var(--sd-color-primary-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-primary{color:var(--sd-color-primary) !important;border-color:var(--sd-color-primary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-secondary,.sd-btn-outline-secondary:hover,.sd-btn-outline-secondary:focus{color:var(--sd-color-secondary-text) !important;background-color:var(--sd-color-secondary) !important;border-color:var(--sd-color-secondary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-secondary:hover,.sd-btn-secondary:focus{color:var(--sd-color-secondary-text) !important;background-color:var(--sd-color-secondary-highlight) !important;border-color:var(--sd-color-secondary-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-secondary{color:var(--sd-color-secondary) !important;border-color:var(--sd-color-secondary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-success,.sd-btn-outline-success:hover,.sd-btn-outline-success:focus{color:var(--sd-color-success-text) !important;background-color:var(--sd-color-success) !important;border-color:var(--sd-color-success) !important;border-width:1px !important;border-style:solid !important}.sd-btn-success:hover,.sd-btn-success:focus{color:var(--sd-color-success-text) !important;background-color:var(--sd-color-success-highlight) !important;border-color:var(--sd-color-success-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-success{color:var(--sd-color-success) !important;border-color:var(--sd-color-success) !important;border-width:1px !important;border-style:solid !important}.sd-btn-info,.sd-btn-outline-info:hover,.sd-btn-outline-info:focus{color:var(--sd-color-info-text) !important;background-color:var(--sd-color-info) !important;border-color:var(--sd-color-info) !important;border-width:1px !important;border-style:solid !important}.sd-btn-info:hover,.sd-btn-info:focus{color:var(--sd-color-info-text) !important;background-color:var(--sd-color-info-highlight) !important;border-color:var(--sd-color-info-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-info{color:var(--sd-color-info) !important;border-color:var(--sd-color-info) !important;border-width:1px !important;border-style:solid !important}.sd-btn-warning,.sd-btn-outline-warning:hover,.sd-btn-outline-warning:focus{color:var(--sd-color-warning-text) !important;background-color:var(--sd-color-warning) !important;border-color:var(--sd-color-warning) !important;border-width:1px !important;border-style:solid !important}.sd-btn-warning:hover,.sd-btn-warning:focus{color:var(--sd-color-warning-text) !important;background-color:var(--sd-color-warning-highlight) !important;border-color:var(--sd-color-warning-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-warning{color:var(--sd-color-warning) !important;border-color:var(--sd-color-warning) !important;border-width:1px !important;border-style:solid !important}.sd-btn-danger,.sd-btn-outline-danger:hover,.sd-btn-outline-danger:focus{color:var(--sd-color-danger-text) !important;background-color:var(--sd-color-danger) !important;border-color:var(--sd-color-danger) !important;border-width:1px !important;border-style:solid !important}.sd-btn-danger:hover,.sd-btn-danger:focus{color:var(--sd-color-danger-text) !important;background-color:var(--sd-color-danger-highlight) !important;border-color:var(--sd-color-danger-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-danger{color:var(--sd-color-danger) !important;border-color:var(--sd-color-danger) !important;border-width:1px !important;border-style:solid !important}.sd-btn-light,.sd-btn-outline-light:hover,.sd-btn-outline-light:focus{color:var(--sd-color-light-text) !important;background-color:var(--sd-color-light) !important;border-color:var(--sd-color-light) !important;border-width:1px !important;border-style:solid !important}.sd-btn-light:hover,.sd-btn-light:focus{color:var(--sd-color-light-text) !important;background-color:var(--sd-color-light-highlight) !important;border-color:var(--sd-color-light-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-light{color:var(--sd-color-light) !important;border-color:var(--sd-color-light) !important;border-width:1px !important;border-style:solid !important}.sd-btn-muted,.sd-btn-outline-muted:hover,.sd-btn-outline-muted:focus{color:var(--sd-color-muted-text) !important;background-color:var(--sd-color-muted) !important;border-color:var(--sd-color-muted) !important;border-width:1px !important;border-style:solid !important}.sd-btn-muted:hover,.sd-btn-muted:focus{color:var(--sd-color-muted-text) !important;background-color:var(--sd-color-muted-highlight) !important;border-color:var(--sd-color-muted-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-muted{color:var(--sd-color-muted) !important;border-color:var(--sd-color-muted) !important;border-width:1px !important;border-style:solid !important}.sd-btn-dark,.sd-btn-outline-dark:hover,.sd-btn-outline-dark:focus{color:var(--sd-color-dark-text) !important;background-color:var(--sd-color-dark) !important;border-color:var(--sd-color-dark) !important;border-width:1px !important;border-style:solid !important}.sd-btn-dark:hover,.sd-btn-dark:focus{color:var(--sd-color-dark-text) !important;background-color:var(--sd-color-dark-highlight) !important;border-color:var(--sd-color-dark-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-dark{color:var(--sd-color-dark) !important;border-color:var(--sd-color-dark) !important;border-width:1px !important;border-style:solid !important}.sd-btn-black,.sd-btn-outline-black:hover,.sd-btn-outline-black:focus{color:var(--sd-color-black-text) !important;background-color:var(--sd-color-black) !important;border-color:var(--sd-color-black) !important;border-width:1px !important;border-style:solid !important}.sd-btn-black:hover,.sd-btn-black:focus{color:var(--sd-color-black-text) !important;background-color:var(--sd-color-black-highlight) !important;border-color:var(--sd-color-black-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-black{color:var(--sd-color-black) !important;border-color:var(--sd-color-black) !important;border-width:1px !important;border-style:solid !important}.sd-btn-white,.sd-btn-outline-white:hover,.sd-btn-outline-white:focus{color:var(--sd-color-white-text) !important;background-color:var(--sd-color-white) !important;border-color:var(--sd-color-white) !important;border-width:1px !important;border-style:solid !important}.sd-btn-white:hover,.sd-btn-white:focus{color:var(--sd-color-white-text) !important;background-color:var(--sd-color-white-highlight) !important;border-color:var(--sd-color-white-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-white{color:var(--sd-color-white) !important;border-color:var(--sd-color-white) !important;border-width:1px !important;border-style:solid !important}.sd-stretched-link::after{position:absolute;top:0;right:0;bottom:0;left:0;z-index:1;content:""}.sd-hide-link-text{font-size:0}.sd-octicon,.sd-material-icon{display:inline-block;fill:currentColor;vertical-align:middle}.sd-avatar-xs{border-radius:50%;object-fit:cover;object-position:center;width:1rem;height:1rem}.sd-avatar-sm{border-radius:50%;object-fit:cover;object-position:center;width:3rem;height:3rem}.sd-avatar-md{border-radius:50%;object-fit:cover;object-position:center;width:5rem;height:5rem}.sd-avatar-lg{border-radius:50%;object-fit:cover;object-position:center;width:7rem;height:7rem}.sd-avatar-xl{border-radius:50%;object-fit:cover;object-position:center;width:10rem;height:10rem}.sd-avatar-inherit{border-radius:50%;object-fit:cover;object-position:center;width:inherit;height:inherit}.sd-avatar-initial{border-radius:50%;object-fit:cover;object-position:center;width:initial;height:initial}.sd-card{background-clip:border-box;background-color:var(--sd-color-card-background);border:1px solid var(--sd-color-card-border);border-radius:.25rem;color:var(--sd-color-card-text);display:-ms-flexbox;display:flex;-ms-flex-direction:column;flex-direction:column;min-width:0;position:relative;word-wrap:break-word}.sd-card>hr{margin-left:0;margin-right:0}.sd-card-hover:hover{border-color:var(--sd-color-card-border-hover);transform:scale(1.01)}.sd-card-body{-ms-flex:1 1 auto;flex:1 1 auto;padding:1rem 1rem}.sd-card-title{margin-bottom:.5rem}.sd-card-subtitle{margin-top:-0.25rem;margin-bottom:0}.sd-card-text:last-child{margin-bottom:0}.sd-card-link:hover{text-decoration:none}.sd-card-link+.card-link{margin-left:1rem}.sd-card-header{padding:.5rem 1rem;margin-bottom:0;background-color:var(--sd-color-card-header);border-bottom:1px solid var(--sd-color-card-border)}.sd-card-header:first-child{border-radius:calc(0.25rem - 1px) calc(0.25rem - 1px) 0 0}.sd-card-footer{padding:.5rem 1rem;background-color:var(--sd-color-card-footer);border-top:1px solid var(--sd-color-card-border)}.sd-card-footer:last-child{border-radius:0 0 calc(0.25rem - 1px) calc(0.25rem - 1px)}.sd-card-header-tabs{margin-right:-0.5rem;margin-bottom:-0.5rem;margin-left:-0.5rem;border-bottom:0}.sd-card-header-pills{margin-right:-0.5rem;margin-left:-0.5rem}.sd-card-img-overlay{position:absolute;top:0;right:0;bottom:0;left:0;padding:1rem;border-radius:calc(0.25rem - 1px)}.sd-card-img,.sd-card-img-bottom,.sd-card-img-top{width:100%}.sd-card-img,.sd-card-img-top{border-top-left-radius:calc(0.25rem - 1px);border-top-right-radius:calc(0.25rem - 1px)}.sd-card-img,.sd-card-img-bottom{border-bottom-left-radius:calc(0.25rem - 1px);border-bottom-right-radius:calc(0.25rem - 1px)}.sd-cards-carousel{width:100%;display:flex;flex-wrap:nowrap;-ms-flex-direction:row;flex-direction:row;overflow-x:hidden;scroll-snap-type:x mandatory}.sd-cards-carousel.sd-show-scrollbar{overflow-x:auto}.sd-cards-carousel:hover,.sd-cards-carousel:focus{overflow-x:auto}.sd-cards-carousel>.sd-card{flex-shrink:0;scroll-snap-align:start}.sd-cards-carousel>.sd-card:not(:last-child){margin-right:3px}.sd-card-cols-1>.sd-card{width:90%}.sd-card-cols-2>.sd-card{width:45%}.sd-card-cols-3>.sd-card{width:30%}.sd-card-cols-4>.sd-card{width:22.5%}.sd-card-cols-5>.sd-card{width:18%}.sd-card-cols-6>.sd-card{width:15%}.sd-card-cols-7>.sd-card{width:12.8571428571%}.sd-card-cols-8>.sd-card{width:11.25%}.sd-card-cols-9>.sd-card{width:10%}.sd-card-cols-10>.sd-card{width:9%}.sd-card-cols-11>.sd-card{width:8.1818181818%}.sd-card-cols-12>.sd-card{width:7.5%}.sd-container,.sd-container-fluid,.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container-xl{margin-left:auto;margin-right:auto;padding-left:var(--sd-gutter-x, 0.75rem);padding-right:var(--sd-gutter-x, 0.75rem);width:100%}@media(min-width: 576px){.sd-container-sm,.sd-container{max-width:540px}}@media(min-width: 768px){.sd-container-md,.sd-container-sm,.sd-container{max-width:720px}}@media(min-width: 992px){.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container{max-width:960px}}@media(min-width: 1200px){.sd-container-xl,.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container{max-width:1140px}}.sd-row{--sd-gutter-x: 1.5rem;--sd-gutter-y: 0;display:-ms-flexbox;display:flex;-ms-flex-wrap:wrap;flex-wrap:wrap;margin-top:calc(var(--sd-gutter-y) * -1);margin-right:calc(var(--sd-gutter-x) * -0.5);margin-left:calc(var(--sd-gutter-x) * -0.5)}.sd-row>*{box-sizing:border-box;flex-shrink:0;width:100%;max-width:100%;padding-right:calc(var(--sd-gutter-x) * 0.5);padding-left:calc(var(--sd-gutter-x) * 0.5);margin-top:var(--sd-gutter-y)}.sd-col{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-auto>*{flex:0 0 auto;width:auto}.sd-row-cols-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}@media(min-width: 576px){.sd-col-sm{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-sm-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-sm-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-sm-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-sm-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-sm-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-sm-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-sm-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-sm-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-sm-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-sm-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-sm-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-sm-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-sm-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 768px){.sd-col-md{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-md-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-md-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-md-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-md-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-md-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-md-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-md-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-md-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-md-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-md-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-md-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-md-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-md-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 992px){.sd-col-lg{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-lg-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-lg-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-lg-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-lg-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-lg-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-lg-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-lg-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-lg-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-lg-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-lg-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-lg-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-lg-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-lg-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 1200px){.sd-col-xl{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-xl-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-xl-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-xl-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-xl-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-xl-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-xl-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-xl-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-xl-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-xl-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-xl-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-xl-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-xl-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-xl-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}.sd-col-auto{flex:0 0 auto;-ms-flex:0 0 auto;width:auto}.sd-col-1{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}.sd-col-2{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-col-3{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-col-4{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-col-5{flex:0 0 auto;-ms-flex:0 0 auto;width:41.6666666667%}.sd-col-6{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-col-7{flex:0 0 auto;-ms-flex:0 0 auto;width:58.3333333333%}.sd-col-8{flex:0 0 auto;-ms-flex:0 0 auto;width:66.6666666667%}.sd-col-9{flex:0 0 auto;-ms-flex:0 0 auto;width:75%}.sd-col-10{flex:0 0 auto;-ms-flex:0 0 auto;width:83.3333333333%}.sd-col-11{flex:0 0 auto;-ms-flex:0 0 auto;width:91.6666666667%}.sd-col-12{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-g-0,.sd-gy-0{--sd-gutter-y: 0}.sd-g-0,.sd-gx-0{--sd-gutter-x: 0}.sd-g-1,.sd-gy-1{--sd-gutter-y: 0.25rem}.sd-g-1,.sd-gx-1{--sd-gutter-x: 0.25rem}.sd-g-2,.sd-gy-2{--sd-gutter-y: 0.5rem}.sd-g-2,.sd-gx-2{--sd-gutter-x: 0.5rem}.sd-g-3,.sd-gy-3{--sd-gutter-y: 1rem}.sd-g-3,.sd-gx-3{--sd-gutter-x: 1rem}.sd-g-4,.sd-gy-4{--sd-gutter-y: 1.5rem}.sd-g-4,.sd-gx-4{--sd-gutter-x: 1.5rem}.sd-g-5,.sd-gy-5{--sd-gutter-y: 3rem}.sd-g-5,.sd-gx-5{--sd-gutter-x: 3rem}@media(min-width: 576px){.sd-col-sm-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-sm-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-sm-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-sm-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-sm-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-sm-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-sm-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-sm-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-sm-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-sm-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-sm-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-sm-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-sm-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-sm-0,.sd-gy-sm-0{--sd-gutter-y: 0}.sd-g-sm-0,.sd-gx-sm-0{--sd-gutter-x: 0}.sd-g-sm-1,.sd-gy-sm-1{--sd-gutter-y: 0.25rem}.sd-g-sm-1,.sd-gx-sm-1{--sd-gutter-x: 0.25rem}.sd-g-sm-2,.sd-gy-sm-2{--sd-gutter-y: 0.5rem}.sd-g-sm-2,.sd-gx-sm-2{--sd-gutter-x: 0.5rem}.sd-g-sm-3,.sd-gy-sm-3{--sd-gutter-y: 1rem}.sd-g-sm-3,.sd-gx-sm-3{--sd-gutter-x: 1rem}.sd-g-sm-4,.sd-gy-sm-4{--sd-gutter-y: 1.5rem}.sd-g-sm-4,.sd-gx-sm-4{--sd-gutter-x: 1.5rem}.sd-g-sm-5,.sd-gy-sm-5{--sd-gutter-y: 3rem}.sd-g-sm-5,.sd-gx-sm-5{--sd-gutter-x: 3rem}}@media(min-width: 768px){.sd-col-md-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-md-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-md-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-md-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-md-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-md-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-md-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-md-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-md-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-md-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-md-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-md-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-md-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-md-0,.sd-gy-md-0{--sd-gutter-y: 0}.sd-g-md-0,.sd-gx-md-0{--sd-gutter-x: 0}.sd-g-md-1,.sd-gy-md-1{--sd-gutter-y: 0.25rem}.sd-g-md-1,.sd-gx-md-1{--sd-gutter-x: 0.25rem}.sd-g-md-2,.sd-gy-md-2{--sd-gutter-y: 0.5rem}.sd-g-md-2,.sd-gx-md-2{--sd-gutter-x: 0.5rem}.sd-g-md-3,.sd-gy-md-3{--sd-gutter-y: 1rem}.sd-g-md-3,.sd-gx-md-3{--sd-gutter-x: 1rem}.sd-g-md-4,.sd-gy-md-4{--sd-gutter-y: 1.5rem}.sd-g-md-4,.sd-gx-md-4{--sd-gutter-x: 1.5rem}.sd-g-md-5,.sd-gy-md-5{--sd-gutter-y: 3rem}.sd-g-md-5,.sd-gx-md-5{--sd-gutter-x: 3rem}}@media(min-width: 992px){.sd-col-lg-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-lg-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-lg-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-lg-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-lg-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-lg-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-lg-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-lg-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-lg-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-lg-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-lg-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-lg-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-lg-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-lg-0,.sd-gy-lg-0{--sd-gutter-y: 0}.sd-g-lg-0,.sd-gx-lg-0{--sd-gutter-x: 0}.sd-g-lg-1,.sd-gy-lg-1{--sd-gutter-y: 0.25rem}.sd-g-lg-1,.sd-gx-lg-1{--sd-gutter-x: 0.25rem}.sd-g-lg-2,.sd-gy-lg-2{--sd-gutter-y: 0.5rem}.sd-g-lg-2,.sd-gx-lg-2{--sd-gutter-x: 0.5rem}.sd-g-lg-3,.sd-gy-lg-3{--sd-gutter-y: 1rem}.sd-g-lg-3,.sd-gx-lg-3{--sd-gutter-x: 1rem}.sd-g-lg-4,.sd-gy-lg-4{--sd-gutter-y: 1.5rem}.sd-g-lg-4,.sd-gx-lg-4{--sd-gutter-x: 1.5rem}.sd-g-lg-5,.sd-gy-lg-5{--sd-gutter-y: 3rem}.sd-g-lg-5,.sd-gx-lg-5{--sd-gutter-x: 3rem}}@media(min-width: 1200px){.sd-col-xl-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-xl-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-xl-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-xl-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-xl-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-xl-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-xl-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-xl-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-xl-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-xl-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-xl-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-xl-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-xl-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-xl-0,.sd-gy-xl-0{--sd-gutter-y: 0}.sd-g-xl-0,.sd-gx-xl-0{--sd-gutter-x: 0}.sd-g-xl-1,.sd-gy-xl-1{--sd-gutter-y: 0.25rem}.sd-g-xl-1,.sd-gx-xl-1{--sd-gutter-x: 0.25rem}.sd-g-xl-2,.sd-gy-xl-2{--sd-gutter-y: 0.5rem}.sd-g-xl-2,.sd-gx-xl-2{--sd-gutter-x: 0.5rem}.sd-g-xl-3,.sd-gy-xl-3{--sd-gutter-y: 1rem}.sd-g-xl-3,.sd-gx-xl-3{--sd-gutter-x: 1rem}.sd-g-xl-4,.sd-gy-xl-4{--sd-gutter-y: 1.5rem}.sd-g-xl-4,.sd-gx-xl-4{--sd-gutter-x: 1.5rem}.sd-g-xl-5,.sd-gy-xl-5{--sd-gutter-y: 3rem}.sd-g-xl-5,.sd-gx-xl-5{--sd-gutter-x: 3rem}}.sd-flex-row-reverse{flex-direction:row-reverse !important}details.sd-dropdown{position:relative}details.sd-dropdown .sd-summary-title{font-weight:700;padding-right:3em !important;-moz-user-select:none;-ms-user-select:none;-webkit-user-select:none;user-select:none}details.sd-dropdown:hover{cursor:pointer}details.sd-dropdown .sd-summary-content{cursor:default}details.sd-dropdown summary{list-style:none;padding:1em}details.sd-dropdown summary .sd-octicon.no-title{vertical-align:middle}details.sd-dropdown[open] summary .sd-octicon.no-title{visibility:hidden}details.sd-dropdown summary::-webkit-details-marker{display:none}details.sd-dropdown summary:focus{outline:none}details.sd-dropdown .sd-summary-icon{margin-right:.5em}details.sd-dropdown .sd-summary-icon svg{opacity:.8}details.sd-dropdown summary:hover .sd-summary-up svg,details.sd-dropdown summary:hover .sd-summary-down svg{opacity:1;transform:scale(1.1)}details.sd-dropdown .sd-summary-up svg,details.sd-dropdown .sd-summary-down svg{display:block;opacity:.6}details.sd-dropdown .sd-summary-up,details.sd-dropdown .sd-summary-down{pointer-events:none;position:absolute;right:1em;top:1em}details.sd-dropdown[open]>.sd-summary-title .sd-summary-down{visibility:hidden}details.sd-dropdown:not([open])>.sd-summary-title .sd-summary-up{visibility:hidden}details.sd-dropdown:not([open]).sd-card{border:none}details.sd-dropdown:not([open])>.sd-card-header{border:1px solid var(--sd-color-card-border);border-radius:.25rem}details.sd-dropdown.sd-fade-in[open] summary~*{-moz-animation:sd-fade-in .5s ease-in-out;-webkit-animation:sd-fade-in .5s ease-in-out;animation:sd-fade-in .5s ease-in-out}details.sd-dropdown.sd-fade-in-slide-down[open] summary~*{-moz-animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out;-webkit-animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out;animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out}.sd-col>.sd-dropdown{width:100%}.sd-summary-content>.sd-tab-set:first-child{margin-top:0}@keyframes sd-fade-in{0%{opacity:0}100%{opacity:1}}@keyframes sd-slide-down{0%{transform:translate(0, -10px)}100%{transform:translate(0, 0)}}.sd-tab-set{border-radius:.125rem;display:flex;flex-wrap:wrap;margin:1em 0;position:relative}.sd-tab-set>input{opacity:0;position:absolute}.sd-tab-set>input:checked+label{border-color:var(--sd-color-tabs-underline-active);color:var(--sd-color-tabs-label-active)}.sd-tab-set>input:checked+label+.sd-tab-content{display:block}.sd-tab-set>input:not(:checked)+label:hover{color:var(--sd-color-tabs-label-hover);border-color:var(--sd-color-tabs-underline-hover)}.sd-tab-set>input:focus+label{outline-style:auto}.sd-tab-set>input:not(.focus-visible)+label{outline:none;-webkit-tap-highlight-color:transparent}.sd-tab-set>label{border-bottom:.125rem solid transparent;margin-bottom:0;color:var(--sd-color-tabs-label-inactive);border-color:var(--sd-color-tabs-underline-inactive);cursor:pointer;font-size:var(--sd-fontsize-tabs-label);font-weight:700;padding:1em 1.25em .5em;transition:color 250ms;width:auto;z-index:1}html .sd-tab-set>label:hover{color:var(--sd-color-tabs-label-active)}.sd-col>.sd-tab-set{width:100%}.sd-tab-content{box-shadow:0 -0.0625rem var(--sd-color-tabs-overline),0 .0625rem var(--sd-color-tabs-underline);display:none;order:99;padding-bottom:.75rem;padding-top:.75rem;width:100%}.sd-tab-content>:first-child{margin-top:0 !important}.sd-tab-content>:last-child{margin-bottom:0 !important}.sd-tab-content>.sd-tab-set{margin:0}.sd-sphinx-override,.sd-sphinx-override *{-moz-box-sizing:border-box;-webkit-box-sizing:border-box;box-sizing:border-box}.sd-sphinx-override p{margin-top:0}:root{--sd-color-primary: #0071bc;--sd-color-secondary: #6c757d;--sd-color-success: #28a745;--sd-color-info: #17a2b8;--sd-color-warning: #f0b37e;--sd-color-danger: #dc3545;--sd-color-light: #f8f9fa;--sd-color-muted: #6c757d;--sd-color-dark: #212529;--sd-color-black: black;--sd-color-white: white;--sd-color-primary-highlight: #0060a0;--sd-color-secondary-highlight: #5c636a;--sd-color-success-highlight: #228e3b;--sd-color-info-highlight: #148a9c;--sd-color-warning-highlight: #cc986b;--sd-color-danger-highlight: #bb2d3b;--sd-color-light-highlight: #d3d4d5;--sd-color-muted-highlight: #5c636a;--sd-color-dark-highlight: #1c1f23;--sd-color-black-highlight: black;--sd-color-white-highlight: #d9d9d9;--sd-color-primary-text: #fff;--sd-color-secondary-text: #fff;--sd-color-success-text: #fff;--sd-color-info-text: #fff;--sd-color-warning-text: #212529;--sd-color-danger-text: #fff;--sd-color-light-text: #212529;--sd-color-muted-text: #fff;--sd-color-dark-text: #fff;--sd-color-black-text: #fff;--sd-color-white-text: #212529;--sd-color-shadow: rgba(0, 0, 0, 0.15);--sd-color-card-border: rgba(0, 0, 0, 0.125);--sd-color-card-border-hover: hsla(231, 99%, 66%, 1);--sd-color-card-background: transparent;--sd-color-card-text: inherit;--sd-color-card-header: transparent;--sd-color-card-footer: transparent;--sd-color-tabs-label-active: hsla(231, 99%, 66%, 1);--sd-color-tabs-label-hover: hsla(231, 99%, 66%, 1);--sd-color-tabs-label-inactive: hsl(0, 0%, 66%);--sd-color-tabs-underline-active: hsla(231, 99%, 66%, 1);--sd-color-tabs-underline-hover: rgba(178, 206, 245, 0.62);--sd-color-tabs-underline-inactive: transparent;--sd-color-tabs-overline: rgb(222, 222, 222);--sd-color-tabs-underline: rgb(222, 222, 222);--sd-fontsize-tabs-label: 1rem} +.sd-bg-primary{background-color:var(--sd-color-primary) !important}.sd-bg-text-primary{color:var(--sd-color-primary-text) !important}button.sd-bg-primary:focus,button.sd-bg-primary:hover{background-color:var(--sd-color-primary-highlight) !important}a.sd-bg-primary:focus,a.sd-bg-primary:hover{background-color:var(--sd-color-primary-highlight) !important}.sd-bg-secondary{background-color:var(--sd-color-secondary) !important}.sd-bg-text-secondary{color:var(--sd-color-secondary-text) !important}button.sd-bg-secondary:focus,button.sd-bg-secondary:hover{background-color:var(--sd-color-secondary-highlight) !important}a.sd-bg-secondary:focus,a.sd-bg-secondary:hover{background-color:var(--sd-color-secondary-highlight) !important}.sd-bg-success{background-color:var(--sd-color-success) !important}.sd-bg-text-success{color:var(--sd-color-success-text) !important}button.sd-bg-success:focus,button.sd-bg-success:hover{background-color:var(--sd-color-success-highlight) !important}a.sd-bg-success:focus,a.sd-bg-success:hover{background-color:var(--sd-color-success-highlight) !important}.sd-bg-info{background-color:var(--sd-color-info) !important}.sd-bg-text-info{color:var(--sd-color-info-text) !important}button.sd-bg-info:focus,button.sd-bg-info:hover{background-color:var(--sd-color-info-highlight) !important}a.sd-bg-info:focus,a.sd-bg-info:hover{background-color:var(--sd-color-info-highlight) !important}.sd-bg-warning{background-color:var(--sd-color-warning) !important}.sd-bg-text-warning{color:var(--sd-color-warning-text) !important}button.sd-bg-warning:focus,button.sd-bg-warning:hover{background-color:var(--sd-color-warning-highlight) !important}a.sd-bg-warning:focus,a.sd-bg-warning:hover{background-color:var(--sd-color-warning-highlight) !important}.sd-bg-danger{background-color:var(--sd-color-danger) !important}.sd-bg-text-danger{color:var(--sd-color-danger-text) !important}button.sd-bg-danger:focus,button.sd-bg-danger:hover{background-color:var(--sd-color-danger-highlight) !important}a.sd-bg-danger:focus,a.sd-bg-danger:hover{background-color:var(--sd-color-danger-highlight) !important}.sd-bg-light{background-color:var(--sd-color-light) !important}.sd-bg-text-light{color:var(--sd-color-light-text) !important}button.sd-bg-light:focus,button.sd-bg-light:hover{background-color:var(--sd-color-light-highlight) !important}a.sd-bg-light:focus,a.sd-bg-light:hover{background-color:var(--sd-color-light-highlight) !important}.sd-bg-muted{background-color:var(--sd-color-muted) !important}.sd-bg-text-muted{color:var(--sd-color-muted-text) !important}button.sd-bg-muted:focus,button.sd-bg-muted:hover{background-color:var(--sd-color-muted-highlight) !important}a.sd-bg-muted:focus,a.sd-bg-muted:hover{background-color:var(--sd-color-muted-highlight) !important}.sd-bg-dark{background-color:var(--sd-color-dark) !important}.sd-bg-text-dark{color:var(--sd-color-dark-text) !important}button.sd-bg-dark:focus,button.sd-bg-dark:hover{background-color:var(--sd-color-dark-highlight) !important}a.sd-bg-dark:focus,a.sd-bg-dark:hover{background-color:var(--sd-color-dark-highlight) !important}.sd-bg-black{background-color:var(--sd-color-black) !important}.sd-bg-text-black{color:var(--sd-color-black-text) !important}button.sd-bg-black:focus,button.sd-bg-black:hover{background-color:var(--sd-color-black-highlight) !important}a.sd-bg-black:focus,a.sd-bg-black:hover{background-color:var(--sd-color-black-highlight) !important}.sd-bg-white{background-color:var(--sd-color-white) !important}.sd-bg-text-white{color:var(--sd-color-white-text) !important}button.sd-bg-white:focus,button.sd-bg-white:hover{background-color:var(--sd-color-white-highlight) !important}a.sd-bg-white:focus,a.sd-bg-white:hover{background-color:var(--sd-color-white-highlight) !important}.sd-text-primary,.sd-text-primary>p{color:var(--sd-color-primary) !important}a.sd-text-primary:focus,a.sd-text-primary:hover{color:var(--sd-color-primary-highlight) !important}.sd-text-secondary,.sd-text-secondary>p{color:var(--sd-color-secondary) !important}a.sd-text-secondary:focus,a.sd-text-secondary:hover{color:var(--sd-color-secondary-highlight) !important}.sd-text-success,.sd-text-success>p{color:var(--sd-color-success) !important}a.sd-text-success:focus,a.sd-text-success:hover{color:var(--sd-color-success-highlight) !important}.sd-text-info,.sd-text-info>p{color:var(--sd-color-info) !important}a.sd-text-info:focus,a.sd-text-info:hover{color:var(--sd-color-info-highlight) !important}.sd-text-warning,.sd-text-warning>p{color:var(--sd-color-warning) !important}a.sd-text-warning:focus,a.sd-text-warning:hover{color:var(--sd-color-warning-highlight) !important}.sd-text-danger,.sd-text-danger>p{color:var(--sd-color-danger) !important}a.sd-text-danger:focus,a.sd-text-danger:hover{color:var(--sd-color-danger-highlight) !important}.sd-text-light,.sd-text-light>p{color:var(--sd-color-light) !important}a.sd-text-light:focus,a.sd-text-light:hover{color:var(--sd-color-light-highlight) !important}.sd-text-muted,.sd-text-muted>p{color:var(--sd-color-muted) !important}a.sd-text-muted:focus,a.sd-text-muted:hover{color:var(--sd-color-muted-highlight) !important}.sd-text-dark,.sd-text-dark>p{color:var(--sd-color-dark) !important}a.sd-text-dark:focus,a.sd-text-dark:hover{color:var(--sd-color-dark-highlight) !important}.sd-text-black,.sd-text-black>p{color:var(--sd-color-black) !important}a.sd-text-black:focus,a.sd-text-black:hover{color:var(--sd-color-black-highlight) !important}.sd-text-white,.sd-text-white>p{color:var(--sd-color-white) !important}a.sd-text-white:focus,a.sd-text-white:hover{color:var(--sd-color-white-highlight) !important}.sd-outline-primary{border-color:var(--sd-color-primary) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-primary:focus,a.sd-outline-primary:hover{border-color:var(--sd-color-primary-highlight) !important}.sd-outline-secondary{border-color:var(--sd-color-secondary) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-secondary:focus,a.sd-outline-secondary:hover{border-color:var(--sd-color-secondary-highlight) !important}.sd-outline-success{border-color:var(--sd-color-success) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-success:focus,a.sd-outline-success:hover{border-color:var(--sd-color-success-highlight) !important}.sd-outline-info{border-color:var(--sd-color-info) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-info:focus,a.sd-outline-info:hover{border-color:var(--sd-color-info-highlight) !important}.sd-outline-warning{border-color:var(--sd-color-warning) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-warning:focus,a.sd-outline-warning:hover{border-color:var(--sd-color-warning-highlight) !important}.sd-outline-danger{border-color:var(--sd-color-danger) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-danger:focus,a.sd-outline-danger:hover{border-color:var(--sd-color-danger-highlight) !important}.sd-outline-light{border-color:var(--sd-color-light) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-light:focus,a.sd-outline-light:hover{border-color:var(--sd-color-light-highlight) !important}.sd-outline-muted{border-color:var(--sd-color-muted) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-muted:focus,a.sd-outline-muted:hover{border-color:var(--sd-color-muted-highlight) !important}.sd-outline-dark{border-color:var(--sd-color-dark) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-dark:focus,a.sd-outline-dark:hover{border-color:var(--sd-color-dark-highlight) !important}.sd-outline-black{border-color:var(--sd-color-black) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-black:focus,a.sd-outline-black:hover{border-color:var(--sd-color-black-highlight) !important}.sd-outline-white{border-color:var(--sd-color-white) !important;border-style:solid !important;border-width:1px !important}a.sd-outline-white:focus,a.sd-outline-white:hover{border-color:var(--sd-color-white-highlight) !important}.sd-bg-transparent{background-color:transparent !important}.sd-outline-transparent{border-color:transparent !important}.sd-text-transparent{color:transparent !important}.sd-p-0{padding:0 !important}.sd-pt-0,.sd-py-0{padding-top:0 !important}.sd-pr-0,.sd-px-0{padding-right:0 !important}.sd-pb-0,.sd-py-0{padding-bottom:0 !important}.sd-pl-0,.sd-px-0{padding-left:0 !important}.sd-p-1{padding:.25rem !important}.sd-pt-1,.sd-py-1{padding-top:.25rem !important}.sd-pr-1,.sd-px-1{padding-right:.25rem !important}.sd-pb-1,.sd-py-1{padding-bottom:.25rem !important}.sd-pl-1,.sd-px-1{padding-left:.25rem !important}.sd-p-2{padding:.5rem !important}.sd-pt-2,.sd-py-2{padding-top:.5rem !important}.sd-pr-2,.sd-px-2{padding-right:.5rem !important}.sd-pb-2,.sd-py-2{padding-bottom:.5rem !important}.sd-pl-2,.sd-px-2{padding-left:.5rem !important}.sd-p-3{padding:1rem !important}.sd-pt-3,.sd-py-3{padding-top:1rem !important}.sd-pr-3,.sd-px-3{padding-right:1rem !important}.sd-pb-3,.sd-py-3{padding-bottom:1rem !important}.sd-pl-3,.sd-px-3{padding-left:1rem !important}.sd-p-4{padding:1.5rem !important}.sd-pt-4,.sd-py-4{padding-top:1.5rem !important}.sd-pr-4,.sd-px-4{padding-right:1.5rem !important}.sd-pb-4,.sd-py-4{padding-bottom:1.5rem !important}.sd-pl-4,.sd-px-4{padding-left:1.5rem !important}.sd-p-5{padding:3rem !important}.sd-pt-5,.sd-py-5{padding-top:3rem !important}.sd-pr-5,.sd-px-5{padding-right:3rem !important}.sd-pb-5,.sd-py-5{padding-bottom:3rem !important}.sd-pl-5,.sd-px-5{padding-left:3rem !important}.sd-m-auto{margin:auto !important}.sd-mt-auto,.sd-my-auto{margin-top:auto !important}.sd-mr-auto,.sd-mx-auto{margin-right:auto !important}.sd-mb-auto,.sd-my-auto{margin-bottom:auto !important}.sd-ml-auto,.sd-mx-auto{margin-left:auto !important}.sd-m-0{margin:0 !important}.sd-mt-0,.sd-my-0{margin-top:0 !important}.sd-mr-0,.sd-mx-0{margin-right:0 !important}.sd-mb-0,.sd-my-0{margin-bottom:0 !important}.sd-ml-0,.sd-mx-0{margin-left:0 !important}.sd-m-1{margin:.25rem !important}.sd-mt-1,.sd-my-1{margin-top:.25rem !important}.sd-mr-1,.sd-mx-1{margin-right:.25rem !important}.sd-mb-1,.sd-my-1{margin-bottom:.25rem !important}.sd-ml-1,.sd-mx-1{margin-left:.25rem !important}.sd-m-2{margin:.5rem !important}.sd-mt-2,.sd-my-2{margin-top:.5rem !important}.sd-mr-2,.sd-mx-2{margin-right:.5rem !important}.sd-mb-2,.sd-my-2{margin-bottom:.5rem !important}.sd-ml-2,.sd-mx-2{margin-left:.5rem !important}.sd-m-3{margin:1rem !important}.sd-mt-3,.sd-my-3{margin-top:1rem !important}.sd-mr-3,.sd-mx-3{margin-right:1rem !important}.sd-mb-3,.sd-my-3{margin-bottom:1rem !important}.sd-ml-3,.sd-mx-3{margin-left:1rem !important}.sd-m-4{margin:1.5rem !important}.sd-mt-4,.sd-my-4{margin-top:1.5rem !important}.sd-mr-4,.sd-mx-4{margin-right:1.5rem !important}.sd-mb-4,.sd-my-4{margin-bottom:1.5rem !important}.sd-ml-4,.sd-mx-4{margin-left:1.5rem !important}.sd-m-5{margin:3rem !important}.sd-mt-5,.sd-my-5{margin-top:3rem !important}.sd-mr-5,.sd-mx-5{margin-right:3rem !important}.sd-mb-5,.sd-my-5{margin-bottom:3rem !important}.sd-ml-5,.sd-mx-5{margin-left:3rem !important}.sd-w-25{width:25% !important}.sd-w-50{width:50% !important}.sd-w-75{width:75% !important}.sd-w-100{width:100% !important}.sd-w-auto{width:auto !important}.sd-h-25{height:25% !important}.sd-h-50{height:50% !important}.sd-h-75{height:75% !important}.sd-h-100{height:100% !important}.sd-h-auto{height:auto !important}.sd-d-none{display:none !important}.sd-d-inline{display:inline !important}.sd-d-inline-block{display:inline-block !important}.sd-d-block{display:block !important}.sd-d-grid{display:grid !important}.sd-d-flex-row{display:-ms-flexbox !important;display:flex !important;flex-direction:row !important}.sd-d-flex-column{display:-ms-flexbox !important;display:flex !important;flex-direction:column !important}.sd-d-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}@media(min-width: 576px){.sd-d-sm-none{display:none !important}.sd-d-sm-inline{display:inline !important}.sd-d-sm-inline-block{display:inline-block !important}.sd-d-sm-block{display:block !important}.sd-d-sm-grid{display:grid !important}.sd-d-sm-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-sm-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 768px){.sd-d-md-none{display:none !important}.sd-d-md-inline{display:inline !important}.sd-d-md-inline-block{display:inline-block !important}.sd-d-md-block{display:block !important}.sd-d-md-grid{display:grid !important}.sd-d-md-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-md-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 992px){.sd-d-lg-none{display:none !important}.sd-d-lg-inline{display:inline !important}.sd-d-lg-inline-block{display:inline-block !important}.sd-d-lg-block{display:block !important}.sd-d-lg-grid{display:grid !important}.sd-d-lg-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-lg-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}@media(min-width: 1200px){.sd-d-xl-none{display:none !important}.sd-d-xl-inline{display:inline !important}.sd-d-xl-inline-block{display:inline-block !important}.sd-d-xl-block{display:block !important}.sd-d-xl-grid{display:grid !important}.sd-d-xl-flex{display:-ms-flexbox !important;display:flex !important}.sd-d-xl-inline-flex{display:-ms-inline-flexbox !important;display:inline-flex !important}}.sd-align-major-start{justify-content:flex-start !important}.sd-align-major-end{justify-content:flex-end !important}.sd-align-major-center{justify-content:center !important}.sd-align-major-justify{justify-content:space-between !important}.sd-align-major-spaced{justify-content:space-evenly !important}.sd-align-minor-start{align-items:flex-start !important}.sd-align-minor-end{align-items:flex-end !important}.sd-align-minor-center{align-items:center !important}.sd-align-minor-stretch{align-items:stretch !important}.sd-text-justify{text-align:justify !important}.sd-text-left{text-align:left !important}.sd-text-right{text-align:right !important}.sd-text-center{text-align:center !important}.sd-font-weight-light{font-weight:300 !important}.sd-font-weight-lighter{font-weight:lighter !important}.sd-font-weight-normal{font-weight:400 !important}.sd-font-weight-bold{font-weight:700 !important}.sd-font-weight-bolder{font-weight:bolder !important}.sd-font-italic{font-style:italic !important}.sd-text-decoration-none{text-decoration:none !important}.sd-text-lowercase{text-transform:lowercase !important}.sd-text-uppercase{text-transform:uppercase !important}.sd-text-capitalize{text-transform:capitalize !important}.sd-text-wrap{white-space:normal !important}.sd-text-nowrap{white-space:nowrap !important}.sd-text-truncate{overflow:hidden;text-overflow:ellipsis;white-space:nowrap}.sd-fs-1,.sd-fs-1>p{font-size:calc(1.375rem + 1.5vw) !important;line-height:unset !important}.sd-fs-2,.sd-fs-2>p{font-size:calc(1.325rem + 0.9vw) !important;line-height:unset !important}.sd-fs-3,.sd-fs-3>p{font-size:calc(1.3rem + 0.6vw) !important;line-height:unset !important}.sd-fs-4,.sd-fs-4>p{font-size:calc(1.275rem + 0.3vw) !important;line-height:unset !important}.sd-fs-5,.sd-fs-5>p{font-size:1.25rem !important;line-height:unset !important}.sd-fs-6,.sd-fs-6>p{font-size:1rem !important;line-height:unset !important}.sd-border-0{border:0 solid !important}.sd-border-top-0{border-top:0 solid !important}.sd-border-bottom-0{border-bottom:0 solid !important}.sd-border-right-0{border-right:0 solid !important}.sd-border-left-0{border-left:0 solid !important}.sd-border-1{border:1px solid !important}.sd-border-top-1{border-top:1px solid !important}.sd-border-bottom-1{border-bottom:1px solid !important}.sd-border-right-1{border-right:1px solid !important}.sd-border-left-1{border-left:1px solid !important}.sd-border-2{border:2px solid !important}.sd-border-top-2{border-top:2px solid !important}.sd-border-bottom-2{border-bottom:2px solid !important}.sd-border-right-2{border-right:2px solid !important}.sd-border-left-2{border-left:2px solid !important}.sd-border-3{border:3px solid !important}.sd-border-top-3{border-top:3px solid !important}.sd-border-bottom-3{border-bottom:3px solid !important}.sd-border-right-3{border-right:3px solid !important}.sd-border-left-3{border-left:3px solid !important}.sd-border-4{border:4px solid !important}.sd-border-top-4{border-top:4px solid !important}.sd-border-bottom-4{border-bottom:4px solid !important}.sd-border-right-4{border-right:4px solid !important}.sd-border-left-4{border-left:4px solid !important}.sd-border-5{border:5px solid !important}.sd-border-top-5{border-top:5px solid !important}.sd-border-bottom-5{border-bottom:5px solid !important}.sd-border-right-5{border-right:5px solid !important}.sd-border-left-5{border-left:5px solid !important}.sd-rounded-0{border-radius:0 !important}.sd-rounded-1{border-radius:.2rem !important}.sd-rounded-2{border-radius:.3rem !important}.sd-rounded-3{border-radius:.5rem !important}.sd-rounded-pill{border-radius:50rem !important}.sd-rounded-circle{border-radius:50% !important}.shadow-none{box-shadow:none !important}.sd-shadow-sm{box-shadow:0 .125rem .25rem var(--sd-color-shadow) !important}.sd-shadow-md{box-shadow:0 .5rem 1rem var(--sd-color-shadow) !important}.sd-shadow-lg{box-shadow:0 1rem 3rem var(--sd-color-shadow) !important}@keyframes sd-slide-from-left{0%{transform:translateX(-100%)}100%{transform:translateX(0)}}@keyframes sd-slide-from-right{0%{transform:translateX(200%)}100%{transform:translateX(0)}}@keyframes sd-grow100{0%{transform:scale(0);opacity:.5}100%{transform:scale(1);opacity:1}}@keyframes sd-grow50{0%{transform:scale(0.5);opacity:.5}100%{transform:scale(1);opacity:1}}@keyframes sd-grow50-rot20{0%{transform:scale(0.5) rotateZ(-20deg);opacity:.5}75%{transform:scale(1) rotateZ(5deg);opacity:1}95%{transform:scale(1) rotateZ(-1deg);opacity:1}100%{transform:scale(1) rotateZ(0);opacity:1}}.sd-animate-slide-from-left{animation:1s ease-out 0s 1 normal none running sd-slide-from-left}.sd-animate-slide-from-right{animation:1s ease-out 0s 1 normal none running sd-slide-from-right}.sd-animate-grow100{animation:1s ease-out 0s 1 normal none running sd-grow100}.sd-animate-grow50{animation:1s ease-out 0s 1 normal none running sd-grow50}.sd-animate-grow50-rot20{animation:1s ease-out 0s 1 normal none running sd-grow50-rot20}.sd-badge{display:inline-block;padding:.35em .65em;font-size:.75em;font-weight:700;line-height:1;text-align:center;white-space:nowrap;vertical-align:baseline;border-radius:.25rem}.sd-badge:empty{display:none}a.sd-badge{text-decoration:none}.sd-btn .sd-badge{position:relative;top:-1px}.sd-btn{background-color:transparent;border:1px solid transparent;border-radius:.25rem;cursor:pointer;display:inline-block;font-weight:400;font-size:1rem;line-height:1.5;padding:.375rem .75rem;text-align:center;text-decoration:none;transition:color .15s ease-in-out,background-color .15s ease-in-out,border-color .15s ease-in-out,box-shadow .15s ease-in-out;vertical-align:middle;user-select:none;-moz-user-select:none;-ms-user-select:none;-webkit-user-select:none}.sd-btn:hover{text-decoration:none}@media(prefers-reduced-motion: reduce){.sd-btn{transition:none}}.sd-btn-primary,.sd-btn-outline-primary:hover,.sd-btn-outline-primary:focus{color:var(--sd-color-primary-text) !important;background-color:var(--sd-color-primary) !important;border-color:var(--sd-color-primary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-primary:hover,.sd-btn-primary:focus{color:var(--sd-color-primary-text) !important;background-color:var(--sd-color-primary-highlight) !important;border-color:var(--sd-color-primary-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-primary{color:var(--sd-color-primary) !important;border-color:var(--sd-color-primary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-secondary,.sd-btn-outline-secondary:hover,.sd-btn-outline-secondary:focus{color:var(--sd-color-secondary-text) !important;background-color:var(--sd-color-secondary) !important;border-color:var(--sd-color-secondary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-secondary:hover,.sd-btn-secondary:focus{color:var(--sd-color-secondary-text) !important;background-color:var(--sd-color-secondary-highlight) !important;border-color:var(--sd-color-secondary-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-secondary{color:var(--sd-color-secondary) !important;border-color:var(--sd-color-secondary) !important;border-width:1px !important;border-style:solid !important}.sd-btn-success,.sd-btn-outline-success:hover,.sd-btn-outline-success:focus{color:var(--sd-color-success-text) !important;background-color:var(--sd-color-success) !important;border-color:var(--sd-color-success) !important;border-width:1px !important;border-style:solid !important}.sd-btn-success:hover,.sd-btn-success:focus{color:var(--sd-color-success-text) !important;background-color:var(--sd-color-success-highlight) !important;border-color:var(--sd-color-success-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-success{color:var(--sd-color-success) !important;border-color:var(--sd-color-success) !important;border-width:1px !important;border-style:solid !important}.sd-btn-info,.sd-btn-outline-info:hover,.sd-btn-outline-info:focus{color:var(--sd-color-info-text) !important;background-color:var(--sd-color-info) !important;border-color:var(--sd-color-info) !important;border-width:1px !important;border-style:solid !important}.sd-btn-info:hover,.sd-btn-info:focus{color:var(--sd-color-info-text) !important;background-color:var(--sd-color-info-highlight) !important;border-color:var(--sd-color-info-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-info{color:var(--sd-color-info) !important;border-color:var(--sd-color-info) !important;border-width:1px !important;border-style:solid !important}.sd-btn-warning,.sd-btn-outline-warning:hover,.sd-btn-outline-warning:focus{color:var(--sd-color-warning-text) !important;background-color:var(--sd-color-warning) !important;border-color:var(--sd-color-warning) !important;border-width:1px !important;border-style:solid !important}.sd-btn-warning:hover,.sd-btn-warning:focus{color:var(--sd-color-warning-text) !important;background-color:var(--sd-color-warning-highlight) !important;border-color:var(--sd-color-warning-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-warning{color:var(--sd-color-warning) !important;border-color:var(--sd-color-warning) !important;border-width:1px !important;border-style:solid !important}.sd-btn-danger,.sd-btn-outline-danger:hover,.sd-btn-outline-danger:focus{color:var(--sd-color-danger-text) !important;background-color:var(--sd-color-danger) !important;border-color:var(--sd-color-danger) !important;border-width:1px !important;border-style:solid !important}.sd-btn-danger:hover,.sd-btn-danger:focus{color:var(--sd-color-danger-text) !important;background-color:var(--sd-color-danger-highlight) !important;border-color:var(--sd-color-danger-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-danger{color:var(--sd-color-danger) !important;border-color:var(--sd-color-danger) !important;border-width:1px !important;border-style:solid !important}.sd-btn-light,.sd-btn-outline-light:hover,.sd-btn-outline-light:focus{color:var(--sd-color-light-text) !important;background-color:var(--sd-color-light) !important;border-color:var(--sd-color-light) !important;border-width:1px !important;border-style:solid !important}.sd-btn-light:hover,.sd-btn-light:focus{color:var(--sd-color-light-text) !important;background-color:var(--sd-color-light-highlight) !important;border-color:var(--sd-color-light-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-light{color:var(--sd-color-light) !important;border-color:var(--sd-color-light) !important;border-width:1px !important;border-style:solid !important}.sd-btn-muted,.sd-btn-outline-muted:hover,.sd-btn-outline-muted:focus{color:var(--sd-color-muted-text) !important;background-color:var(--sd-color-muted) !important;border-color:var(--sd-color-muted) !important;border-width:1px !important;border-style:solid !important}.sd-btn-muted:hover,.sd-btn-muted:focus{color:var(--sd-color-muted-text) !important;background-color:var(--sd-color-muted-highlight) !important;border-color:var(--sd-color-muted-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-muted{color:var(--sd-color-muted) !important;border-color:var(--sd-color-muted) !important;border-width:1px !important;border-style:solid !important}.sd-btn-dark,.sd-btn-outline-dark:hover,.sd-btn-outline-dark:focus{color:var(--sd-color-dark-text) !important;background-color:var(--sd-color-dark) !important;border-color:var(--sd-color-dark) !important;border-width:1px !important;border-style:solid !important}.sd-btn-dark:hover,.sd-btn-dark:focus{color:var(--sd-color-dark-text) !important;background-color:var(--sd-color-dark-highlight) !important;border-color:var(--sd-color-dark-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-dark{color:var(--sd-color-dark) !important;border-color:var(--sd-color-dark) !important;border-width:1px !important;border-style:solid !important}.sd-btn-black,.sd-btn-outline-black:hover,.sd-btn-outline-black:focus{color:var(--sd-color-black-text) !important;background-color:var(--sd-color-black) !important;border-color:var(--sd-color-black) !important;border-width:1px !important;border-style:solid !important}.sd-btn-black:hover,.sd-btn-black:focus{color:var(--sd-color-black-text) !important;background-color:var(--sd-color-black-highlight) !important;border-color:var(--sd-color-black-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-black{color:var(--sd-color-black) !important;border-color:var(--sd-color-black) !important;border-width:1px !important;border-style:solid !important}.sd-btn-white,.sd-btn-outline-white:hover,.sd-btn-outline-white:focus{color:var(--sd-color-white-text) !important;background-color:var(--sd-color-white) !important;border-color:var(--sd-color-white) !important;border-width:1px !important;border-style:solid !important}.sd-btn-white:hover,.sd-btn-white:focus{color:var(--sd-color-white-text) !important;background-color:var(--sd-color-white-highlight) !important;border-color:var(--sd-color-white-highlight) !important;border-width:1px !important;border-style:solid !important}.sd-btn-outline-white{color:var(--sd-color-white) !important;border-color:var(--sd-color-white) !important;border-width:1px !important;border-style:solid !important}.sd-stretched-link::after{position:absolute;top:0;right:0;bottom:0;left:0;z-index:1;content:""}.sd-hide-link-text{font-size:0}.sd-octicon,.sd-material-icon{display:inline-block;fill:currentColor;vertical-align:middle}.sd-avatar-xs{border-radius:50%;object-fit:cover;object-position:center;width:1rem;height:1rem}.sd-avatar-sm{border-radius:50%;object-fit:cover;object-position:center;width:3rem;height:3rem}.sd-avatar-md{border-radius:50%;object-fit:cover;object-position:center;width:5rem;height:5rem}.sd-avatar-lg{border-radius:50%;object-fit:cover;object-position:center;width:7rem;height:7rem}.sd-avatar-xl{border-radius:50%;object-fit:cover;object-position:center;width:10rem;height:10rem}.sd-avatar-inherit{border-radius:50%;object-fit:cover;object-position:center;width:inherit;height:inherit}.sd-avatar-initial{border-radius:50%;object-fit:cover;object-position:center;width:initial;height:initial}.sd-card{background-clip:border-box;background-color:var(--sd-color-card-background);border:1px solid var(--sd-color-card-border);border-radius:.25rem;color:var(--sd-color-card-text);display:-ms-flexbox;display:flex;-ms-flex-direction:column;flex-direction:column;min-width:0;position:relative;word-wrap:break-word}.sd-card>hr{margin-left:0;margin-right:0}.sd-card-hover:hover{border-color:var(--sd-color-card-border-hover);transform:scale(1.01)}.sd-card-body{-ms-flex:1 1 auto;flex:1 1 auto;padding:1rem 1rem}.sd-card-title{margin-bottom:.5rem}.sd-card-subtitle{margin-top:-0.25rem;margin-bottom:0}.sd-card-text:last-child{margin-bottom:0}.sd-card-link:hover{text-decoration:none}.sd-card-link+.card-link{margin-left:1rem}.sd-card-header{padding:.5rem 1rem;margin-bottom:0;background-color:var(--sd-color-card-header);border-bottom:1px solid var(--sd-color-card-border)}.sd-card-header:first-child{border-radius:calc(0.25rem - 1px) calc(0.25rem - 1px) 0 0}.sd-card-footer{padding:.5rem 1rem;background-color:var(--sd-color-card-footer);border-top:1px solid var(--sd-color-card-border)}.sd-card-footer:last-child{border-radius:0 0 calc(0.25rem - 1px) calc(0.25rem - 1px)}.sd-card-header-tabs{margin-right:-0.5rem;margin-bottom:-0.5rem;margin-left:-0.5rem;border-bottom:0}.sd-card-header-pills{margin-right:-0.5rem;margin-left:-0.5rem}.sd-card-img-overlay{position:absolute;top:0;right:0;bottom:0;left:0;padding:1rem;border-radius:calc(0.25rem - 1px)}.sd-card-img,.sd-card-img-bottom,.sd-card-img-top{width:100%}.sd-card-img,.sd-card-img-top{border-top-left-radius:calc(0.25rem - 1px);border-top-right-radius:calc(0.25rem - 1px)}.sd-card-img,.sd-card-img-bottom{border-bottom-left-radius:calc(0.25rem - 1px);border-bottom-right-radius:calc(0.25rem - 1px)}.sd-cards-carousel{width:100%;display:flex;flex-wrap:nowrap;-ms-flex-direction:row;flex-direction:row;overflow-x:hidden;scroll-snap-type:x mandatory}.sd-cards-carousel.sd-show-scrollbar{overflow-x:auto}.sd-cards-carousel:hover,.sd-cards-carousel:focus{overflow-x:auto}.sd-cards-carousel>.sd-card{flex-shrink:0;scroll-snap-align:start}.sd-cards-carousel>.sd-card:not(:last-child){margin-right:3px}.sd-card-cols-1>.sd-card{width:90%}.sd-card-cols-2>.sd-card{width:45%}.sd-card-cols-3>.sd-card{width:30%}.sd-card-cols-4>.sd-card{width:22.5%}.sd-card-cols-5>.sd-card{width:18%}.sd-card-cols-6>.sd-card{width:15%}.sd-card-cols-7>.sd-card{width:12.8571428571%}.sd-card-cols-8>.sd-card{width:11.25%}.sd-card-cols-9>.sd-card{width:10%}.sd-card-cols-10>.sd-card{width:9%}.sd-card-cols-11>.sd-card{width:8.1818181818%}.sd-card-cols-12>.sd-card{width:7.5%}.sd-container,.sd-container-fluid,.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container-xl{margin-left:auto;margin-right:auto;padding-left:var(--sd-gutter-x, 0.75rem);padding-right:var(--sd-gutter-x, 0.75rem);width:100%}@media(min-width: 576px){.sd-container-sm,.sd-container{max-width:540px}}@media(min-width: 768px){.sd-container-md,.sd-container-sm,.sd-container{max-width:720px}}@media(min-width: 992px){.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container{max-width:960px}}@media(min-width: 1200px){.sd-container-xl,.sd-container-lg,.sd-container-md,.sd-container-sm,.sd-container{max-width:1140px}}.sd-row{--sd-gutter-x: 1.5rem;--sd-gutter-y: 0;display:-ms-flexbox;display:flex;-ms-flex-wrap:wrap;flex-wrap:wrap;margin-top:calc(var(--sd-gutter-y) * -1);margin-right:calc(var(--sd-gutter-x) * -0.5);margin-left:calc(var(--sd-gutter-x) * -0.5)}.sd-row>*{box-sizing:border-box;flex-shrink:0;width:100%;max-width:100%;padding-right:calc(var(--sd-gutter-x) * 0.5);padding-left:calc(var(--sd-gutter-x) * 0.5);margin-top:var(--sd-gutter-y)}.sd-col{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-auto>*{flex:0 0 auto;width:auto}.sd-row-cols-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}@media(min-width: 576px){.sd-col-sm{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-sm-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-sm-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-sm-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-sm-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-sm-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-sm-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-sm-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-sm-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-sm-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-sm-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-sm-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-sm-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-sm-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 768px){.sd-col-md{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-md-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-md-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-md-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-md-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-md-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-md-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-md-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-md-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-md-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-md-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-md-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-md-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-md-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 992px){.sd-col-lg{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-lg-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-lg-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-lg-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-lg-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-lg-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-lg-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-lg-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-lg-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-lg-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-lg-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-lg-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-lg-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-lg-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}@media(min-width: 1200px){.sd-col-xl{flex:1 0 0%;-ms-flex:1 0 0%}.sd-row-cols-xl-auto{flex:1 0 auto;-ms-flex:1 0 auto;width:100%}.sd-row-cols-xl-1>*{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-row-cols-xl-2>*{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-row-cols-xl-3>*{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-row-cols-xl-4>*{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-row-cols-xl-5>*{flex:0 0 auto;-ms-flex:0 0 auto;width:20%}.sd-row-cols-xl-6>*{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-row-cols-xl-7>*{flex:0 0 auto;-ms-flex:0 0 auto;width:14.2857142857%}.sd-row-cols-xl-8>*{flex:0 0 auto;-ms-flex:0 0 auto;width:12.5%}.sd-row-cols-xl-9>*{flex:0 0 auto;-ms-flex:0 0 auto;width:11.1111111111%}.sd-row-cols-xl-10>*{flex:0 0 auto;-ms-flex:0 0 auto;width:10%}.sd-row-cols-xl-11>*{flex:0 0 auto;-ms-flex:0 0 auto;width:9.0909090909%}.sd-row-cols-xl-12>*{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}}.sd-col-auto{flex:0 0 auto;-ms-flex:0 0 auto;width:auto}.sd-col-1{flex:0 0 auto;-ms-flex:0 0 auto;width:8.3333333333%}.sd-col-2{flex:0 0 auto;-ms-flex:0 0 auto;width:16.6666666667%}.sd-col-3{flex:0 0 auto;-ms-flex:0 0 auto;width:25%}.sd-col-4{flex:0 0 auto;-ms-flex:0 0 auto;width:33.3333333333%}.sd-col-5{flex:0 0 auto;-ms-flex:0 0 auto;width:41.6666666667%}.sd-col-6{flex:0 0 auto;-ms-flex:0 0 auto;width:50%}.sd-col-7{flex:0 0 auto;-ms-flex:0 0 auto;width:58.3333333333%}.sd-col-8{flex:0 0 auto;-ms-flex:0 0 auto;width:66.6666666667%}.sd-col-9{flex:0 0 auto;-ms-flex:0 0 auto;width:75%}.sd-col-10{flex:0 0 auto;-ms-flex:0 0 auto;width:83.3333333333%}.sd-col-11{flex:0 0 auto;-ms-flex:0 0 auto;width:91.6666666667%}.sd-col-12{flex:0 0 auto;-ms-flex:0 0 auto;width:100%}.sd-g-0,.sd-gy-0{--sd-gutter-y: 0}.sd-g-0,.sd-gx-0{--sd-gutter-x: 0}.sd-g-1,.sd-gy-1{--sd-gutter-y: 0.25rem}.sd-g-1,.sd-gx-1{--sd-gutter-x: 0.25rem}.sd-g-2,.sd-gy-2{--sd-gutter-y: 0.5rem}.sd-g-2,.sd-gx-2{--sd-gutter-x: 0.5rem}.sd-g-3,.sd-gy-3{--sd-gutter-y: 1rem}.sd-g-3,.sd-gx-3{--sd-gutter-x: 1rem}.sd-g-4,.sd-gy-4{--sd-gutter-y: 1.5rem}.sd-g-4,.sd-gx-4{--sd-gutter-x: 1.5rem}.sd-g-5,.sd-gy-5{--sd-gutter-y: 3rem}.sd-g-5,.sd-gx-5{--sd-gutter-x: 3rem}@media(min-width: 576px){.sd-col-sm-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-sm-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-sm-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-sm-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-sm-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-sm-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-sm-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-sm-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-sm-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-sm-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-sm-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-sm-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-sm-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-sm-0,.sd-gy-sm-0{--sd-gutter-y: 0}.sd-g-sm-0,.sd-gx-sm-0{--sd-gutter-x: 0}.sd-g-sm-1,.sd-gy-sm-1{--sd-gutter-y: 0.25rem}.sd-g-sm-1,.sd-gx-sm-1{--sd-gutter-x: 0.25rem}.sd-g-sm-2,.sd-gy-sm-2{--sd-gutter-y: 0.5rem}.sd-g-sm-2,.sd-gx-sm-2{--sd-gutter-x: 0.5rem}.sd-g-sm-3,.sd-gy-sm-3{--sd-gutter-y: 1rem}.sd-g-sm-3,.sd-gx-sm-3{--sd-gutter-x: 1rem}.sd-g-sm-4,.sd-gy-sm-4{--sd-gutter-y: 1.5rem}.sd-g-sm-4,.sd-gx-sm-4{--sd-gutter-x: 1.5rem}.sd-g-sm-5,.sd-gy-sm-5{--sd-gutter-y: 3rem}.sd-g-sm-5,.sd-gx-sm-5{--sd-gutter-x: 3rem}}@media(min-width: 768px){.sd-col-md-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-md-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-md-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-md-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-md-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-md-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-md-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-md-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-md-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-md-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-md-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-md-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-md-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-md-0,.sd-gy-md-0{--sd-gutter-y: 0}.sd-g-md-0,.sd-gx-md-0{--sd-gutter-x: 0}.sd-g-md-1,.sd-gy-md-1{--sd-gutter-y: 0.25rem}.sd-g-md-1,.sd-gx-md-1{--sd-gutter-x: 0.25rem}.sd-g-md-2,.sd-gy-md-2{--sd-gutter-y: 0.5rem}.sd-g-md-2,.sd-gx-md-2{--sd-gutter-x: 0.5rem}.sd-g-md-3,.sd-gy-md-3{--sd-gutter-y: 1rem}.sd-g-md-3,.sd-gx-md-3{--sd-gutter-x: 1rem}.sd-g-md-4,.sd-gy-md-4{--sd-gutter-y: 1.5rem}.sd-g-md-4,.sd-gx-md-4{--sd-gutter-x: 1.5rem}.sd-g-md-5,.sd-gy-md-5{--sd-gutter-y: 3rem}.sd-g-md-5,.sd-gx-md-5{--sd-gutter-x: 3rem}}@media(min-width: 992px){.sd-col-lg-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-lg-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-lg-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-lg-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-lg-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-lg-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-lg-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-lg-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-lg-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-lg-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-lg-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-lg-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-lg-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-lg-0,.sd-gy-lg-0{--sd-gutter-y: 0}.sd-g-lg-0,.sd-gx-lg-0{--sd-gutter-x: 0}.sd-g-lg-1,.sd-gy-lg-1{--sd-gutter-y: 0.25rem}.sd-g-lg-1,.sd-gx-lg-1{--sd-gutter-x: 0.25rem}.sd-g-lg-2,.sd-gy-lg-2{--sd-gutter-y: 0.5rem}.sd-g-lg-2,.sd-gx-lg-2{--sd-gutter-x: 0.5rem}.sd-g-lg-3,.sd-gy-lg-3{--sd-gutter-y: 1rem}.sd-g-lg-3,.sd-gx-lg-3{--sd-gutter-x: 1rem}.sd-g-lg-4,.sd-gy-lg-4{--sd-gutter-y: 1.5rem}.sd-g-lg-4,.sd-gx-lg-4{--sd-gutter-x: 1.5rem}.sd-g-lg-5,.sd-gy-lg-5{--sd-gutter-y: 3rem}.sd-g-lg-5,.sd-gx-lg-5{--sd-gutter-x: 3rem}}@media(min-width: 1200px){.sd-col-xl-auto{-ms-flex:0 0 auto;flex:0 0 auto;width:auto}.sd-col-xl-1{-ms-flex:0 0 auto;flex:0 0 auto;width:8.3333333333%}.sd-col-xl-2{-ms-flex:0 0 auto;flex:0 0 auto;width:16.6666666667%}.sd-col-xl-3{-ms-flex:0 0 auto;flex:0 0 auto;width:25%}.sd-col-xl-4{-ms-flex:0 0 auto;flex:0 0 auto;width:33.3333333333%}.sd-col-xl-5{-ms-flex:0 0 auto;flex:0 0 auto;width:41.6666666667%}.sd-col-xl-6{-ms-flex:0 0 auto;flex:0 0 auto;width:50%}.sd-col-xl-7{-ms-flex:0 0 auto;flex:0 0 auto;width:58.3333333333%}.sd-col-xl-8{-ms-flex:0 0 auto;flex:0 0 auto;width:66.6666666667%}.sd-col-xl-9{-ms-flex:0 0 auto;flex:0 0 auto;width:75%}.sd-col-xl-10{-ms-flex:0 0 auto;flex:0 0 auto;width:83.3333333333%}.sd-col-xl-11{-ms-flex:0 0 auto;flex:0 0 auto;width:91.6666666667%}.sd-col-xl-12{-ms-flex:0 0 auto;flex:0 0 auto;width:100%}.sd-g-xl-0,.sd-gy-xl-0{--sd-gutter-y: 0}.sd-g-xl-0,.sd-gx-xl-0{--sd-gutter-x: 0}.sd-g-xl-1,.sd-gy-xl-1{--sd-gutter-y: 0.25rem}.sd-g-xl-1,.sd-gx-xl-1{--sd-gutter-x: 0.25rem}.sd-g-xl-2,.sd-gy-xl-2{--sd-gutter-y: 0.5rem}.sd-g-xl-2,.sd-gx-xl-2{--sd-gutter-x: 0.5rem}.sd-g-xl-3,.sd-gy-xl-3{--sd-gutter-y: 1rem}.sd-g-xl-3,.sd-gx-xl-3{--sd-gutter-x: 1rem}.sd-g-xl-4,.sd-gy-xl-4{--sd-gutter-y: 1.5rem}.sd-g-xl-4,.sd-gx-xl-4{--sd-gutter-x: 1.5rem}.sd-g-xl-5,.sd-gy-xl-5{--sd-gutter-y: 3rem}.sd-g-xl-5,.sd-gx-xl-5{--sd-gutter-x: 3rem}}.sd-flex-row-reverse{flex-direction:row-reverse !important}details.sd-dropdown{position:relative;font-size:var(--sd-fontsize-dropdown)}details.sd-dropdown:hover{cursor:pointer}details.sd-dropdown .sd-summary-content{cursor:default}details.sd-dropdown summary.sd-summary-title{padding:.5em 1em;font-size:var(--sd-fontsize-dropdown-title);font-weight:var(--sd-fontweight-dropdown-title);user-select:none;-moz-user-select:none;-ms-user-select:none;-webkit-user-select:none;list-style:none;display:inline-flex;justify-content:space-between}details.sd-dropdown summary.sd-summary-title::-webkit-details-marker{display:none}details.sd-dropdown summary.sd-summary-title:focus{outline:none}details.sd-dropdown summary.sd-summary-title .sd-summary-icon{margin-right:.6em;display:inline-flex;align-items:center}details.sd-dropdown summary.sd-summary-title .sd-summary-icon svg{opacity:.8}details.sd-dropdown summary.sd-summary-title .sd-summary-text{flex-grow:1;line-height:1.5;padding-right:.5rem}details.sd-dropdown summary.sd-summary-title .sd-summary-state-marker{pointer-events:none;display:inline-flex;align-items:center}details.sd-dropdown summary.sd-summary-title .sd-summary-state-marker svg{opacity:.6}details.sd-dropdown summary.sd-summary-title:hover .sd-summary-state-marker svg{opacity:1;transform:scale(1.1)}details.sd-dropdown[open] summary .sd-octicon.no-title{visibility:hidden}details.sd-dropdown .sd-summary-chevron-right{transition:.25s}details.sd-dropdown[open]>.sd-summary-title .sd-summary-chevron-right{transform:rotate(90deg)}details.sd-dropdown[open]>.sd-summary-title .sd-summary-chevron-down{transform:rotate(180deg)}details.sd-dropdown:not([open]).sd-card{border:none}details.sd-dropdown:not([open])>.sd-card-header{border:1px solid var(--sd-color-card-border);border-radius:.25rem}details.sd-dropdown.sd-fade-in[open] summary~*{-moz-animation:sd-fade-in .5s ease-in-out;-webkit-animation:sd-fade-in .5s ease-in-out;animation:sd-fade-in .5s ease-in-out}details.sd-dropdown.sd-fade-in-slide-down[open] summary~*{-moz-animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out;-webkit-animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out;animation:sd-fade-in .5s ease-in-out,sd-slide-down .5s ease-in-out}.sd-col>.sd-dropdown{width:100%}.sd-summary-content>.sd-tab-set:first-child{margin-top:0}@keyframes sd-fade-in{0%{opacity:0}100%{opacity:1}}@keyframes sd-slide-down{0%{transform:translate(0, -10px)}100%{transform:translate(0, 0)}}.sd-tab-set{border-radius:.125rem;display:flex;flex-wrap:wrap;margin:1em 0;position:relative}.sd-tab-set>input{opacity:0;position:absolute}.sd-tab-set>input:checked+label{border-color:var(--sd-color-tabs-underline-active);color:var(--sd-color-tabs-label-active)}.sd-tab-set>input:checked+label+.sd-tab-content{display:block}.sd-tab-set>input:not(:checked)+label:hover{color:var(--sd-color-tabs-label-hover);border-color:var(--sd-color-tabs-underline-hover)}.sd-tab-set>input:focus+label{outline-style:auto}.sd-tab-set>input:not(.focus-visible)+label{outline:none;-webkit-tap-highlight-color:transparent}.sd-tab-set>label{border-bottom:.125rem solid transparent;margin-bottom:0;color:var(--sd-color-tabs-label-inactive);border-color:var(--sd-color-tabs-underline-inactive);cursor:pointer;font-size:var(--sd-fontsize-tabs-label);font-weight:700;padding:1em 1.25em .5em;transition:color 250ms;width:auto;z-index:1}html .sd-tab-set>label:hover{color:var(--sd-color-tabs-label-active)}.sd-col>.sd-tab-set{width:100%}.sd-tab-content{box-shadow:0 -0.0625rem var(--sd-color-tabs-overline),0 .0625rem var(--sd-color-tabs-underline);display:none;order:99;padding-bottom:.75rem;padding-top:.75rem;width:100%}.sd-tab-content>:first-child{margin-top:0 !important}.sd-tab-content>:last-child{margin-bottom:0 !important}.sd-tab-content>.sd-tab-set{margin:0}.sd-sphinx-override,.sd-sphinx-override *{-moz-box-sizing:border-box;-webkit-box-sizing:border-box;box-sizing:border-box}.sd-sphinx-override p{margin-top:0}:root{--sd-color-primary: #0071bc;--sd-color-secondary: #6c757d;--sd-color-success: #28a745;--sd-color-info: #17a2b8;--sd-color-warning: #f0b37e;--sd-color-danger: #dc3545;--sd-color-light: #f8f9fa;--sd-color-muted: #6c757d;--sd-color-dark: #212529;--sd-color-black: black;--sd-color-white: white;--sd-color-primary-highlight: #0060a0;--sd-color-secondary-highlight: #5c636a;--sd-color-success-highlight: #228e3b;--sd-color-info-highlight: #148a9c;--sd-color-warning-highlight: #cc986b;--sd-color-danger-highlight: #bb2d3b;--sd-color-light-highlight: #d3d4d5;--sd-color-muted-highlight: #5c636a;--sd-color-dark-highlight: #1c1f23;--sd-color-black-highlight: black;--sd-color-white-highlight: #d9d9d9;--sd-color-primary-bg: rgba(0, 113, 188, 0.2);--sd-color-secondary-bg: rgba(108, 117, 125, 0.2);--sd-color-success-bg: rgba(40, 167, 69, 0.2);--sd-color-info-bg: rgba(23, 162, 184, 0.2);--sd-color-warning-bg: rgba(240, 179, 126, 0.2);--sd-color-danger-bg: rgba(220, 53, 69, 0.2);--sd-color-light-bg: rgba(248, 249, 250, 0.2);--sd-color-muted-bg: rgba(108, 117, 125, 0.2);--sd-color-dark-bg: rgba(33, 37, 41, 0.2);--sd-color-black-bg: rgba(0, 0, 0, 0.2);--sd-color-white-bg: rgba(255, 255, 255, 0.2);--sd-color-primary-text: #fff;--sd-color-secondary-text: #fff;--sd-color-success-text: #fff;--sd-color-info-text: #fff;--sd-color-warning-text: #212529;--sd-color-danger-text: #fff;--sd-color-light-text: #212529;--sd-color-muted-text: #fff;--sd-color-dark-text: #fff;--sd-color-black-text: #fff;--sd-color-white-text: #212529;--sd-color-shadow: rgba(0, 0, 0, 0.15);--sd-color-card-border: rgba(0, 0, 0, 0.125);--sd-color-card-border-hover: hsla(231, 99%, 66%, 1);--sd-color-card-background: transparent;--sd-color-card-text: inherit;--sd-color-card-header: transparent;--sd-color-card-footer: transparent;--sd-color-tabs-label-active: hsla(231, 99%, 66%, 1);--sd-color-tabs-label-hover: hsla(231, 99%, 66%, 1);--sd-color-tabs-label-inactive: hsl(0, 0%, 66%);--sd-color-tabs-underline-active: hsla(231, 99%, 66%, 1);--sd-color-tabs-underline-hover: rgba(178, 206, 245, 0.62);--sd-color-tabs-underline-inactive: transparent;--sd-color-tabs-overline: rgb(222, 222, 222);--sd-color-tabs-underline: rgb(222, 222, 222);--sd-fontsize-tabs-label: 1rem;--sd-fontsize-dropdown: inherit;--sd-fontsize-dropdown-title: 1rem;--sd-fontweight-dropdown-title: 700} diff --git a/docs/_static/tabs.css b/docs/_static/tabs.css index c74e8956..957ba60d 100644 --- a/docs/_static/tabs.css +++ b/docs/_static/tabs.css @@ -51,3 +51,39 @@ .sphinx-tab img { margin-bottom: 24 px; } + +/* Dark theme preference styling */ + +@media (prefers-color-scheme: dark) { + body[data-theme="auto"] .sphinx-tabs-panel { + color: white; + background-color: rgb(50, 50, 50); + } + + body[data-theme="auto"] .sphinx-tabs-tab { + color: white; + background-color: rgba(255, 255, 255, 0.05); + } + + body[data-theme="auto"] .sphinx-tabs-tab[aria-selected="true"] { + border-bottom: 1px solid rgb(50, 50, 50); + background-color: rgb(50, 50, 50); + } +} + +/* Explicit dark theme styling */ + +body[data-theme="dark"] .sphinx-tabs-panel { + color: white; + background-color: rgb(50, 50, 50); +} + +body[data-theme="dark"] .sphinx-tabs-tab { + color: white; + background-color: rgba(255, 255, 255, 0.05); +} + +body[data-theme="dark"] .sphinx-tabs-tab[aria-selected="true"] { + border-bottom: 2px solid rgb(50, 50, 50); + background-color: rgb(50, 50, 50); +} diff --git a/docs/bootcamp/syllabus.html b/docs/bootcamp/syllabus.html index fde21bc4..43e473df 100644 --- a/docs/bootcamp/syllabus.html +++ b/docs/bootcamp/syllabus.html @@ -16,7 +16,7 @@ - + @@ -242,7 +242,7 @@

Syllabus

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/bootcamp/syllabus_by_day.html b/docs/bootcamp/syllabus_by_day.html index cdc3dac4..11f474ac 100644 --- a/docs/bootcamp/syllabus_by_day.html +++ b/docs/bootcamp/syllabus_by_day.html @@ -16,7 +16,7 @@ - + @@ -289,7 +289,7 @@

Week 2

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/bootcamp/syllabus_by_topic.html b/docs/bootcamp/syllabus_by_topic.html index 5aa74682..1f545122 100644 --- a/docs/bootcamp/syllabus_by_topic.html +++ b/docs/bootcamp/syllabus_by_topic.html @@ -16,7 +16,7 @@ - + @@ -236,7 +236,7 @@

By Topic

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/DLApps.html b/docs/common/developer_manual/architecture/desktop/applications/DLApps.html index b3ae48ec..f443e8c8 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/DLApps.html +++ b/docs/common/developer_manual/architecture/desktop/applications/DLApps.html @@ -16,7 +16,7 @@ - + @@ -221,16 +221,12 @@

2.3.9. DL Applications

-

The DL application performs the damage and loss assessment for the buildings subject to the regional event(s). -It takes as input the building properties used for determining damages and losses (e. g. building occupancy, structure type, replacement cost, number of stories), -specified in the BIM file, as well as the response simulation output recorded in the EDP file. -It returns damage probabilities in a “DM.csv” file and decision variable estimates in a “DV.csv” for each simulation, saved in its corresponding -simulation working directory.

+

The DL application assesses the damage and loss for buildings subjected to regional events.It uses building properties, such as building occupancy, structure type, replacement cost, and number of stories, to determine damages and losses. These properties are specified in the BIM file. The application also uses the response simulation output recorded in the EDP file.

+

The application returns damage probabilities in a “DM.csv” file and decision variable estimates in a “DV.csv” file for each simulation. These files are saved in their respective simulation working directories.

../../../../../_images/backendapps_DL.png
-

The following options for DL applications vary in the software package used to perform the damage and loss assessment.

-main.html
+ @@ -242,7 +238,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/EDPApps.html b/docs/common/developer_manual/architecture/desktop/applications/EDPApps.html index 776e0b6f..26646f0e 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/EDPApps.html +++ b/docs/common/developer_manual/architecture/desktop/applications/EDPApps.html @@ -16,7 +16,7 @@ - + @@ -242,8 +242,7 @@
../../../../../_images/backendapps_EDP.png
-

The following options for EDP applications vary in the type of EDPs identified for the simulation output.

-main.html +
@@ -500,7 +499,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/UQApps.html b/docs/common/developer_manual/architecture/desktop/applications/UQApps.html index fa204bb4..d05b9302 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/UQApps.html +++ b/docs/common/developer_manual/architecture/desktop/applications/UQApps.html @@ -16,7 +16,7 @@ - + @@ -235,14 +235,13 @@

2.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 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.

+

The UQ application is used to sample random variables (RVs) specified in any of the workflow steps (Event, Modeling, EDP, Simulation) for uncertainty quantification. It then runs commands written in the driver file, which call on the backend applications to execute the R2D Workflow. +First, it 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, the UQ application directly runs commands in the driver file without performing random sampling.

../../../../../_images/backendapps_UQ.png
-

The following options for UQ applications vary in the software package used to perform uncertainty quantification.

-main.html +
@@ -387,7 +386,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/buildingApps.html b/docs/common/developer_manual/architecture/desktop/applications/buildingApps.html index 1531182d..b81d043e 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/buildingApps.html +++ b/docs/common/developer_manual/architecture/desktop/applications/buildingApps.html @@ -16,7 +16,7 @@ - + @@ -221,13 +221,12 @@

2.3.8. Building Applications

-

The building application creates building information model (BIM) files for each building. It takes as input the range of asset IDs selected for simulation (expressed as “min” and “max” ID, specified in the configuration file) and the building-specific parameters for each simulation (specified in the building source file). -The inputs are parsed into #-BIM.json files in the results folder.

+

The Building Application creates Building Information Model (BIM) files for each building. It takes as input the range of asset IDs selected for simulation (expressed as “min” and “max” ID, specified in the configuration file), and the building-specific parameters for each simulation (specified in the building source file). +These inputs are parsed into #-BIM.json files, which are stored in the results folder.

../../../../../_images/backendapps_Building.png
-

The following options for building applications vary in the file type of the input building source file it processes.

-main.html +
@@ -453,7 +452,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/eventApps.html b/docs/common/developer_manual/architecture/desktop/applications/eventApps.html index 51458701..8f69414e 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/eventApps.html +++ b/docs/common/developer_manual/architecture/desktop/applications/eventApps.html @@ -16,7 +16,7 @@ - + @@ -235,13 +235,13 @@

2.3.3. Event Applications

-

The event application takes the event(s) selected for a building site, associates each one with a simulation, and creates EVENT files containing the event intensity measures. It obtains the name of the event from the BIM file and the intensity measure information from the input event files. -This input information is saved in an EVENT.json file, located in its corresponding simulation working directory.

+

The event application takes the selected event(s) for a building site, associates each one with a simulation, and creates EVENT files containing the event intensity measures. It obtains the name of the event from the BIM file and the intensity measure information from the input event files. +This input information is saved in an EVENT.json file, located in the corresponding simulation working directory.

../../../../../_images/backendapps_Events.png
-

The following options for event applications vary in the type of event, event properties, and format of the event file that it processes.

-main.html +

The following options for event applications vary in the type of event, event properties, and the format of the event file that they process.

+
@@ -578,7 +578,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/modelingApps.html b/docs/common/developer_manual/architecture/desktop/applications/modelingApps.html index 18279ce7..3cbe17e5 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/modelingApps.html +++ b/docs/common/developer_manual/architecture/desktop/applications/modelingApps.html @@ -16,7 +16,7 @@ - + @@ -241,8 +241,7 @@
../../../../../_images/backendapps_Modeling.png
-

The following options for modeling applications vary in the type of model and finite element program used for response simulation.

-main.html +
@@ -524,7 +523,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/preprocFEM.html b/docs/common/developer_manual/architecture/desktop/applications/preprocFEM.html index 7e21596e..894e1411 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/preprocFEM.html +++ b/docs/common/developer_manual/architecture/desktop/applications/preprocFEM.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

2.3.1. FEM Pre-processors

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/preprocUQ.html b/docs/common/developer_manual/architecture/desktop/applications/preprocUQ.html index 6a598471..e1f4e8bf 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/preprocUQ.html +++ b/docs/common/developer_manual/architecture/desktop/applications/preprocUQ.html @@ -16,7 +16,7 @@ - + @@ -222,8 +222,6 @@

2.3.2. UQ Pre-processors

- -
@@ -241,7 +237,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/applications/simulationApps.html b/docs/common/developer_manual/architecture/desktop/applications/simulationApps.html index d8f96422..73ec6879 100644 --- a/docs/common/developer_manual/architecture/desktop/applications/simulationApps.html +++ b/docs/common/developer_manual/architecture/desktop/applications/simulationApps.html @@ -16,7 +16,7 @@ - + @@ -235,14 +235,13 @@

2.3.6. Simulation Applications

-

The simulation application specifies parameters and executes the script for the response simulation. These parameters may include the integrator scheme, convergence tolerance, step size, etc. of the numerical analysis. +

The simulation application specifies parameters and executes the script for the response simulation. These parameters may include the integrator scheme, convergence tolerance, step size, etc., of the numerical analysis. It takes as input the BIM file, the EVENT file, the SAM file, and the EDP file. -After response simulation is completed, the EDP.json file is populated with the resulting EDPs and saved in the simulation working directory. Note that the SIM.json file is not saved in the directory.

+After the response simulation is completed, the EDP.json file is populated with the resulting EDPs and saved in the simulation working directory. Note that the SIM.json file is not saved in the directory.

../../../../../_images/backendapps_Simulation.png
-

The following options for simulation applications vary in the type of finite element program or procedure used for EDPs estimation.

-main.html +
@@ -607,7 +606,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/architecture.html b/docs/common/developer_manual/architecture/desktop/architecture.html index 472ec3aa..e33ee619 100644 --- a/docs/common/developer_manual/architecture/desktop/architecture.html +++ b/docs/common/developer_manual/architecture/desktop/architecture.html @@ -16,7 +16,7 @@ - + @@ -270,7 +270,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/backendApplications.html b/docs/common/developer_manual/architecture/desktop/backendApplications.html index 891a9e5b..959107b7 100644 --- a/docs/common/developer_manual/architecture/desktop/backendApplications.html +++ b/docs/common/developer_manual/architecture/desktop/backendApplications.html @@ -16,7 +16,7 @@ - + @@ -231,9 +231,9 @@
-
-

2.3. Backend Applications

-

The backend applications are categorized by function into the following workflow modules which creates and populate intermediate files used to propagate information from one component application to the next. The modules and their intermediate files are as follows:

+
+

2.3. Backend Applications

+

The backend applications are categorized by function into the following workflow modules which create and populate intermediate files used to propagate information from one component application to the next. The modules and their intermediate files are as follows:

  1. Event Applications - create the EVENT files for every building asset, containing loads corresponding to the hazard event(s).

  2. Modeling Applications - create the Structural Analysis Model (SAM) files for every building asset, containing structural model parameters.

    3. @@ -243,7 +243,7 @@

    2.3. Backend Applications

-

These applications make up the “backbone” of SimCenter workflow systems, with each one calling on a different subset of the component applications.

+

These applications constitute the “backbone” of SimCenter workflow systems, with each one calling on a different subset of the component applications.

@@ -256,7 +256,7 @@

2.3. Backend Applications

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/c4model.html b/docs/common/developer_manual/architecture/desktop/c4model.html index c7260993..b84e886f 100644 --- a/docs/common/developer_manual/architecture/desktop/c4model.html +++ b/docs/common/developer_manual/architecture/desktop/c4model.html @@ -16,7 +16,7 @@ - + @@ -489,7 +489,7 @@

2.2.7. UML HydroUQ

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/dynamicDiagrams.html b/docs/common/developer_manual/architecture/desktop/dynamicDiagrams.html index d5074f81..9799479b 100644 --- a/docs/common/developer_manual/architecture/desktop/dynamicDiagrams.html +++ b/docs/common/developer_manual/architecture/desktop/dynamicDiagrams.html @@ -16,7 +16,7 @@ - + @@ -213,7 +213,7 @@

Level 4 Dynamic Diagrams

-

To understand better the interactions between the components we will present some C4 dynamic diagrams. The dynamic diagram is similar to a UML communication diagram, which again is similar to a UML sequence diagram although it allows a free-form arrangement of diagram elements with numbered interactions to indicate ordering.

+

To better understand the interactions between the components, we will present some C4 dynamic diagrams. The dynamic diagram is similar to a UML communication diagram, which, again, is akin to a UML sequence diagram, albeit it allows for a free-form arrangement of diagram elements with numbered interactions to indicate ordering.

@@ -226,7 +226,7 @@

- © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

diff --git a/docs/common/developer_manual/architecture/desktop/file-types.html b/docs/common/developer_manual/architecture/desktop/file-types.html index 4d4f3464..d74034aa 100644 --- a/docs/common/developer_manual/architecture/desktop/file-types.html +++ b/docs/common/developer_manual/architecture/desktop/file-types.html @@ -16,7 +16,7 @@ - + @@ -230,7 +230,7 @@

2.4. File Types and Schemas

-

In order to run an instance of the workflow, users must prepare the input files according to a standard file schema (the file type, structure, and contents). If input files deviate from this schema, then the workflow will return errors. Upon completion of the workflow, output files containing a summary of simulation results are produced.

+

In order to run an instance of the workflow, users must prepare the input files according to a standard file schema (the file type, structure, and contents). If input files deviate from this schema, the workflow will return errors. Upon completion of the workflow, output files containing a summary of simulation results are produced.

For a guide on formatting input files and reading output files, refer to the following pages:

    @@ -250,7 +250,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/file-types/Inputs.html b/docs/common/developer_manual/architecture/desktop/file-types/Inputs.html index 2ce261b8..cb0bad5e 100644 --- a/docs/common/developer_manual/architecture/desktop/file-types/Inputs.html +++ b/docs/common/developer_manual/architecture/desktop/file-types/Inputs.html @@ -16,7 +16,7 @@ - + @@ -475,7 +475,7 @@

    2.4.1.2. Building Source File

    2.4.1.3. Transportation Network Source File Option 1

-

A JSON file containing highway transportation roadways, bridges, and tunnels for the response simulation and damage/loss estimation steps of the workflow. This file contains all the information necessary for constructing AIM files for each bridge, tunnel, and roadway. The JSON file must contain the “nodes” object and at lease one of the “hwy_bridges”, “hwy_tunnels”, and “roadways” object. Involved key-item pairs are:

+

A JSON file containing highway transportation roadways, bridges, and tunnels for the response simulation and damage/loss estimation steps of the workflow. This file contains all the information necessary for constructing AIM files for each bridge, tunnel, and roadway. The JSON file must contain the “nodes” object and at least one of the “hwy_bridges”, “hwy_tunnels”, and “roadways” objects. Involved key-item pairs are:

  • “hwy_bridges”: A JSON array of JSON Objects, each containing the following key/item pairs

@@ -625,7 +625,7 @@

2.4.1.2. Building Source File -

  • “nodes”: A long JSON Objects containing the following key/item pairs

    • +

  • “nodes”: A large JSON Object containing the following key/item pairs

    • @@ -837,7 +837,7 @@

    2.4.1.6. Event Files

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/file-types/Outputs.html b/docs/common/developer_manual/architecture/desktop/file-types/Outputs.html index f96c48a6..2eecd70a 100644 --- a/docs/common/developer_manual/architecture/desktop/file-types/Outputs.html +++ b/docs/common/developer_manual/architecture/desktop/file-types/Outputs.html @@ -16,7 +16,7 @@ - + @@ -237,7 +237,7 @@

    2.4.2. Outputs

    -

    After DL assessment is complete, the workflow collects the EDP.csv, DM.csv, and DV.csv files produced for each building asset and aggregates the results into single output files. When run locally, the workflow returns the output in a CSV format which is located in the results folder. When run remotely, the workflow returns the output in an HDF format which is located in the job archive. The HDF files may be converted into CSV format as a post-processing step.

    +

    After the DL assessment is complete, the workflow collects the EDP.csv, DM.csv, and DV.csv files produced for each building asset and aggregates the results into single output files. When run locally, the workflow returns the output in CSV format, which is located in the results folder. When run remotely, the workflow returns the output in HDF format, which is located in the job archive. The HDF files can be converted into CSV format as a post-processing step.

    2.4.2.1. EDP Output File

    Table 2.4.1.5 InputDataSchemaTransportNode.csv
     @@ -952,7 +952,7 @@

    2.4.2.3. DV Output File

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/overview.html b/docs/common/developer_manual/architecture/desktop/overview.html index 56883f8b..ebc98b72 100644 --- a/docs/common/developer_manual/architecture/desktop/overview.html +++ b/docs/common/developer_manual/architecture/desktop/overview.html @@ -16,7 +16,7 @@ - + @@ -228,43 +228,39 @@

    2.1. Software Architecture

    -

    The HydroUQ app is one of the SimCenter’s computational applications, which are scientific workflow systems that executes a sequence of computational tasks specialized for natural hazard engineering (NHE) problems. In contrast to more general-purpose scientific workflow systems (such as Taverna, Kepler, and Pegasus), SimCenter workflow systems include the following features:

    +

    The HydroUQ app is one of SimCenter’s computational applications, which are scientific workflow systems that execute a sequence of computational tasks specialized for natural hazard engineering (NHE) problems. In contrast to more general-purpose scientific workflow systems (such as Taverna, Kepler, and Pegasus), SimCenter workflow systems include the following features:

      -

    • Access to high-performance computing resources, available on the cloud through DesignSafe, to enable parallel workflows for non-trivial large-scale NHE problems;

      • -

    • Uncertainty quantification capabilities using Dakota, which allows users to introduce input uncertainties that are propagated through the workflow with random variables;

      • -

    • Streamlined interfaces between existing software applications and datasets that are widely used by the NHE community, such as OpenFOAM, OpenSees, ADCIRC, and PEER Strong Ground Motion Databases. To do this, the SimCenter develops pre- and post-processors for these existing applications and utilizes web technologies for accessing online services;

      • -

    • Additional custom software applications produced by the SimCenter. Among these are applications that automate the acquisition of building inventory data (BRAILS), applications that simulate hazard events and generate corresponding input files for passing through the workflow system (RegionalEvent Applications), applications for damage and loss assessment (pelicun), and more.

      • -

    • Modular framework that allows developers to incorporate their own software applications as components to the workflow system, so long as it meets the input-output structure at component interfaces.

      • +

    • Access to high-performance computing resources, available on the cloud through DesignSafe, to enable parallel workflows for large-scale NHE problems;

      • +

    • Uncertainty quantification capabilities using Dakota, which allow users to introduce input uncertainties that are propagated through the workflow with random variables;

      • +

    • Streamlined interfaces between existing software applications and datasets widely used by the NHE community, such as OpenFOAM, OpenSees, ADCIRC, and PEER Strong Ground Motion Databases. To do this, the SimCenter develops pre- and post-processors for these existing applications and utilizes web technologies for accessing online services;

      • +

    • Additional custom software applications produced by the SimCenter. Among these are applications that automate the acquisition of building inventory data (BRAILS), applications that simulate hazard events and generate corresponding input files for passing through the workflow system (RegionalEvent Applications), applications for damage and loss assessment (pelicun), and more;

      • +

    • A modular framework that allows developers to incorporate their own software applications as components to the workflow system, as long as they meet the input-output structure at component interfaces.

    ../../../../_images/SimCenterFramework.png

    Fig. 2.1.1 SimCenter Software Framework

    -

    A Level 1 diagram showing the system context for the SimCenter applications, i.e., how it fits in the world, -is shown in Fig. 2.1.2. It shows SimCenter applications (EE-UQ, WE-UQ, HydroUQ, PBE, R2D) as a box in the center surrounded by the user and the user’s systems. The SimCenter applications allow a user to create and run scientific workflow applications; the data for the applications may be obtained from the web or DataDepot. The workflow applications are run on either the local desktop or on some HPC at DesignSafe.

    +

    A Level 1 diagram showing the system context for the SimCenter applications, i.e., how it fits in the world, is shown in Fig. 2.1.2. It shows SimCenter applications (EE-UQ, WE-UQ, HydroUQ, PBE, R2D) as a box in the center surrounded by the user and the user’s systems. The SimCenter applications allow a user to create and run scientific workflow applications; the data for the applications may be obtained from the web or DataDepot. The workflow applications are run on either the local desktop or on an HPC at DesignSafe.

    ../../../../_images/context.png

    Fig. 2.1.2 System context diagram for SimCenter applications.

    -

    Given how SimCenter applications fit in with the environment, a level 2 diagram demonstrates how the -SimCenter applications are broken into high-level components. The SimCenter applications are, as shown in -Fig. 2.1.3, split into two components: A front-end UI and a back-end application that runs the workflow. The front-end applications are desktop applications written using the cross-platform Qt framework. The back end is an application that processes the input from the front end, which comes in the form of a JSON file, creates a workflow, and runs it. The workflow applications, written in Python, C, or C++, utilize existing applications where possible and run on either the local desktop machine or on an HPC utilizing resources made available to the NHE community through DesignSafe.

    +

    Given how SimCenter applications fit in with the environment, a Level 2 diagram demonstrates how the SimCenter applications are broken into high-level components. The SimCenter applications are, as shown in Fig. 2.1.3, split into two components: a front-end UI and a back-end application that runs the workflow. The front-end applications are desktop applications written using the cross-platform Qt framework. The back end is an application that processes the input from the front end, which comes in the form of a JSON file, creates a workflow, and runs it. The workflow applications, written in Python, C, or C++, utilize existing applications where possible and run on either the local desktop machine or on an HPC using resources made available to the NHE community through DesignSafe.

    ../../../../_images/container.png

    Fig. 2.1.3 System container diagram for SimCenter applications.

    -

    Two level 3 diagrams are now presented, which break up the two containers into the major building blocks or -components in C4 terminology. In Fig. 2.1.4, the component diagram for the front-end UI is presented. It outlines the interaction between the user and the individual graphical elements (widgets) of the UI. Given the jigsaw puzzle analogy, the user selects which piece of the jigsaw puzzle they are working on in the component selection widget. The widget for the jigsaw piece will then be displayed on the desktop. The user for each jigsaw piece then selects which application to run for that piece. For the chosen application, they provide the inputs. When the inputs are all provided, the user can choose to run the simulations locally or remotely. For jobs that run remotely, the user can download and review previously run simulations. As seen, the widgets may subsequently interact with web services through HTTPS requests or with DesignSafe utilizing TAPIS Restful API through the RemoteService container.

    +

    Two Level 3 diagrams are now presented, which break up the two containers into the major building blocks or components in C4 terminology. In Fig. 2.1.4, the component diagram for the front-end UI is presented. It outlines the interaction between the user and the individual graphical elements (widgets) of the UI. Given the jigsaw puzzle analogy, the user selects which piece of the jigsaw puzzle they are working on in the component selection widget. The widget for the jigsaw piece will then be displayed on the desktop. The user for each jigsaw piece then selects which application to run for that piece. For the chosen application, they provide the inputs. When the inputs are all provided, the user can choose to run the simulations locally or remotely. For jobs that run remotely, the user can download and review previously run simulations. As seen, the widgets may subsequently interact with web services through HTTPS requests or with DesignSafe utilizing TAPIS Restful API through the RemoteService container.

    ../../../../_images/componentFront.png

    Fig. 2.1.4 Component diagram for front-end UI.

    -

    The component diagram for the back-end application shown in Fig. 2.1.5, shows that the back-end comprises several component applications. The application femUQ.py is the application that parses the input from the front end, sets up the workflow by creating a workflow_driver script and then launches the UQ engine. The choice of UQ Engine and applications to run in the workflow is determined from the data passed from the UI and information contained in a file, WorkflowApplication.json. The WorkflowApplication.json file is a file that maps the applications specified in the output from the UI with a specific application contained on the users’ local machine or at the remote HPC resource, as such it allows the researchers to modify the applications that may be run in the workflow w/o the need to recompile the application. Once the workflow_driver file is created, control is passed to a UQ engine, which repeatedly runs the workflow_driver to generate the results. In running the workflow, some of the applications will invoke applications not developed to meet the API. For such applications, pre- and post-processors are provided. The figure shows the back-end application running locally or remotely on an HPC at DesignSafe.

    +

    The component diagram for the back-end application shown in Fig. 2.1.5, shows that the back-end comprises several component applications. The application femUQ.py is the application that parses the input from the front end, sets up the workflow by creating a workflow_driver script, and then launches the UQ engine. The choice of UQ engine and applications to run in the workflow is determined from the data passed from the UI and information contained in a file, WorkflowApplication.json. The WorkflowApplication.json file is a file that maps the applications specified in the output from the UI with a specific application contained on the user’s local machine or at the remote HPC resource. As such, it allows the researchers to modify the applications that may be run in the workflow without the need to recompile the application. Once the workflow_driver file is created, control is passed to a UQ engine, which repeatedly runs the workflow_driver to generate the results. In running the workflow, some of the applications will invoke applications not developed to meet the API. For such applications, pre- and post-processors are provided. The figure shows the back-end application running locally or remotely on an HPC at DesignSafe.

    ../../../../_images/componentBack.png -

    Fig. 2.1.5 Component diagram for Backend Application.

    +

    Fig. 2.1.5 Component diagram for back-end application.

    Note

    @@ -272,36 +268,32 @@

    The interaction between the front-end and the back-end is best understood by looking at the sequence of events when the user presses the Run button. As shown in the figure below, the UI application will first perform several steps:

      -

    1. It will create a temporary directory in the Documents folder named tmp.SimCenter, and inside tmp.SimCenter will create another directory templatedir.

      2. +

    2. It will create a temporary directory in the Documents folder named tmp.SimCenter, and inside tmp.SimCenter it will create another directory templatedir.

    3. It will then run through all the currently selected widgets and invoke the copyFiles() method, telling these widgets to copy all files needed during the workflow to the templatedir directory.

      4. -

    4. It will then create a JSON file and will run through the currently selected widgets and on each invokes the methods outputToJSON() and outputAppDataToJSON, these telling the application to augment the JSON file with the inputs the user has provided in the widget and also the name of the widget.

      5. +

    5. It will then create a JSON file and will run through the currently selected widgets and invoke the methods outputToJSON() and outputAppDataToJSON(), telling the application to augment the JSON file with the inputs the user has provided in the widget and also the name of the widget.

    6. The UI will start the back-end application and spin until the back-end application returns with a completion signal.

    -

    Now that the UI has been handed over to the back-end application, the back-end application will perform the following:

    +

    Now that the UI has handed over to the back-end application, the back-end application will perform the following steps:

      -

    1. Open the output file from the UI and parse it to obtain the name of the application to run and the arguments to run the application with. Open up another file, the WorkflowApplications.json file, contained with the application to determine, given the application name, the full path to the executable to be invoked. It will create in templatedir a file named workflow_driver. When run by the UQ engine, this file is a script file that will generate a file named results.out. results.out when the workflow_driver script has completed will contain a single line of space-separated values, one value for each EDP.

      2. +

    2. Open the output file from the UI and parse it to obtain the name of the application to run and the arguments to run the application with. Open another file, the WorkflowApplications.json file, contained within the application to determine, given the application name, the full path to the executable to be invoked. It will create in templatedir a file named workflow_driver. When run by the UQ engine, this file is a script file that will generate a file named results.out. results.out when the workflow_driver script has completed will contain a single line of space-separated values, one value for each EDP.

    3. It will invoke each application with supplied arguments and an additional command-line argument, --getRV, to inform the application to process the input file and create any additional random variables and input files needed before the workflow runs.

      4. -

    4. It will then launch the UQengine. The UQengine is typically a pre- and post-processor to an existing UQ engine.

      5. +

    5. It will then launch the UQ engine. The UQ engine is typically a pre- and post-processor to an existing UQ engine.

    6. The pre-processor takes the JSON input file and creates an input file needed by the actual UQ engine.

    7. The pre-processor will launch the UQ application. This application will typically run the workflow_driver many times, passing as input to the workflow a file \params and obtaining output from the workflow_driver a file results.out.

    8. When done, the engine will output its results.

      9. -

    9. The UQengine will notify the UQpreprocessor that it is done.

      10. -

    10. The UQpreprocessor will notify the femUQ application that it is done.

      11. +

    11. The UQ engine will notify the UQ pre-processor that it is done.

      12. +

    12. The UQ pre-processor will notify the femUQ application that it is done.

    13. The femUQ application will notify the UI that it is done.

    14. The UI will read the results and present them to the user.

    ../../../../_images/sequenceLocal.png -

    Fig. 2.1.6 Sequence diagram showing what happens when a Workflow runs Locally

    +

    Fig. 2.1.6 Sequence diagram showing what happens when a workflow runs locally.

    -

    That is for the case where the computations are performed on the local computer. When the computations are -performed remotely, the steps are different. The first 8 steps are the same. But now, the UQwrapper will not -start the UQ engine. Instead, control is returned to the UI. The UI will, as shown in the following: (11) -Compress the temporary folder. (12) Send the compressed folder to the remote HPC, shown in -Fig. 2.1.7. (13) Start an application to perform the computations. All the remote data transfer and application invocation is down through a cloud service. The TACC tapis interface is used to provide SimCenter users with access to the TACC HPC resources through the DesignSafe portal.

    +

    That is for the case where the computations are performed on the local computer. When the computations are performed remotely, the steps are different. The first eight steps are the same. But now, the UQ wrapper will not start the UQ engine. Instead, control is returned to the UI. The UI will, as shown in the following: (11) Compress the temporary folder, (12) Send the compressed folder to the remote HPC, shown in Fig. 2.1.7, (13) Start an application to perform the computations. All the remote data transfer and application invocation is done through a cloud service. The TACC Tapis interface is used to provide SimCenter users with access to the TACC HPC resources through the DesignSafe portal.

    ../../../../_images/sequenceRemote.png -

    Fig. 2.1.7 Sequence diagram showing what happens when a Workflow runs Remotely

    +

    Fig. 2.1.7 Sequence diagram showing what happens when a workflow runs remotely.

    @@ -315,7 +307,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/run-manually.html b/docs/common/developer_manual/architecture/desktop/run-manually.html index eac07741..90c40c31 100644 --- a/docs/common/developer_manual/architecture/desktop/run-manually.html +++ b/docs/common/developer_manual/architecture/desktop/run-manually.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/run-manually/runLocal.html b/docs/common/developer_manual/architecture/desktop/run-manually/runLocal.html index 3ee77c00..eea49f39 100644 --- a/docs/common/developer_manual/architecture/desktop/run-manually/runLocal.html +++ b/docs/common/developer_manual/architecture/desktop/run-manually/runLocal.html @@ -16,7 +16,7 @@ - + @@ -213,37 +213,43 @@

    Run Locally on Your Desktop

    -

    Running applications locally on a personal desktop is convenient for running small-scale jobs and debugging. For larger jobs, the applications are available on DesignSafe for utilizing high-performance computing resources.

    +

    Running applications locally on a personal desktop is convenient for small-scale jobs and debugging. For larger jobs, the applications are available on DesignSafe to utilize high-performance computing resources.

      -

    1. Follow the directions in How to Build to install the backend applications on your local desktop. Move the applications folder to a separate directory (such as C:/rWHALE/).

      2. -

    2. Prepare the input files in a folder called input_data, then zip the folder. You may use this example input file set (input_data_eq.zip) as a template.

      3. -

    3. Prepare workflow settings in the configuration file. You may use the example configuration file (rWHALE_config_eq.json) as a template.

      -
      -
        -

      • Set 'runDir' to the path containing the input_data folder. If the configuration file is in the same directory, set 'remoteDir'='...'.

        • -

      • Set 'localAppDir' to the path containing the applications folder (such as C:/rWHALE/).

        • -

      • Specify applications for each workflow step and their inputs. For more details on the format of the configuration file, see Inputs.

        • +

      • Follow the directions in How to Build to install the backend applications on your local desktop. The applications needed to run the backend are in the applications folder after you have built the backend. You can leave the folder where you have built it (which is useful if you plan to keep updating the backend applications as we make changes to the github repository, or you can move the applications folder to a seperate directory (such as C:/rWHALE/) if you don’t plan to update these applications.

        • +

      • To run a workflow you first need to create a folder on your filesystem in which you will place the necessary inputs. In this folder you will need an input file that describes the workflow to run, say input.json, and a directory input_data.

        • +

      • Create the input file, input.json that outlines the workflow to run. You may use the example configuration file (input.json) as a template. There are 3 lines in this file that need changing to run the default workflow (Example1 in the R2DTool):

        +
        "remoteAppDir": "/Users/fmckenna/NHERI/SimCenterBackendApplications",
+"localAppDir": "/Users/fmckenna/NHERI/SimCenterBackendApplications",
+"runDir": "/Users/fmckenna/Documents/R2D/LocalWorkDir/tmp.SimCenter"
+
        +
        +
          +

        • Set 'runDir' to the path containing the input_data folder.

          • +

        • Set 'localAppDir' and ''remoteAppDir' to the path containing the applications folder (such as C:/rWHALE/).

          • +

        • If you wish to change thw workflow that is run, you need to specify applications for each workflow step and their inputs. For more details on the format of the configuration file, see Inputs.

        -
      4. +

    4. In the input_data folder, you need to place the files needed by the applications which will run in the workflow. You may use this example input file set (input_data.zip) as a template. Again, the downloaded default is for Example1 in R2D.

      5. +

    5. Now you are ready to run the Workflow. The workflow is run through the command window by calling on Python and specifying paths to the application files, input files, and desired location for the results folder. The following is the command to issue on the command line:

    -
      -

    1. The workflow is run through the command window by calling on Python and specifying paths to the application files, input files, and desired location for the results folder. The following is an example of the initialization command:

      2. -
    -
    python <path to R2D_workflow.py> <path to rWHALE_config.json> --registry <path to WorkflowApplications.json> --referenceDir <path to input_data folder> -w <path to output results folder>
+
    python <path to rWhale.py> <path to wfInput.json> --registry <path to WorkflowApplications.json> --referenceDir <path to input_data folder> -w <path to output results folder>
 
    
 
    
 
    
 
    where:
      
-
    • <path to R2D_workflow.py> is the full path to the file “R2D_workflow.py” in the applications folder
      • 
-
    • <path to rWHALE_config.json> is the full path to the provided file rWHALE_config.json
      • 
-
    • <path to WorkflowApplications.json> is the full path to the file WorkflowApplications.json in the applications folder
      • 
+
    • <path to R2D_workflow.py> is the full path to the file “rWhale.py” in the /applications/Workflow folder
      • 
+
    • <path to rWHALE_config.json> is the full path to the workflow input file, input.json
      • 
+
    • <path to WorkflowApplications.json> is the full path to the file WorkflowApplications.json in the applications/Workflow folder
      • 
 
    • <path to input_data folder> is the full path to the folder with all input files
      • 
 
    • <path to output results folder> is the full path to where a “results” folder will be created to contain the output files
      • 
 
    
 
    
 
    
-
      
+
      
+
      Note
      
+
      If you are on a Mac, python in the above needs to be replaced by python3.
      
+
      
+
        
 
      1. A results folder is produced, which contains both the aggregated output files (EDP_{min id}_{max id}.csv, DM_{min id}_{max id}.csv, DV_{min id}_{max id}.csv), as well as the individual output files (EDP.csv, DM.csv, DV.csv) for each built asset in their respective folders.
        2. 
 
      
 
      results
@@ -290,7 +296,7 @@
 
   
      
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      
diff --git a/docs/common/developer_manual/architecture/desktop/run-manually/runRemote.html b/docs/common/developer_manual/architecture/desktop/run-manually/runRemote.html
index 8bbb7a68..54a22dd0 100644
--- a/docs/common/developer_manual/architecture/desktop/run-manually/runRemote.html
+++ b/docs/common/developer_manual/architecture/desktop/run-manually/runRemote.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -213,55 +213,50 @@
             
   
      
 
      Run Remotely on DesignSafe
      
-
      There are two ways to run the applications remotely on DesignSafe: one is through the Data Depot user interface on DesignSafe, where job details are submitted through a Jupyter notebook. The other is by calling on Tapis CLI directly through Ubuntu.
      
 
      
 
      Prepare Input Files
      
-
        
-
      1. Prepare the input files in a folder called input_data, then zip the folder. You may use this example input file set (input_data_eq.zip) as a template.
        2. 
+
          
+
        1. Prepare the input files in a folder named input_data, then zip the folder. You may use this example input file set (input_data_eq.zip) as a template.
          2. 
 
        2. Prepare workflow settings in the configuration file. You may use the example configuration file (rWHALE_config_remote.json) as a template.
          
-
          
-
            
+
              
 
            • Set 'runDir' to /tmp/rWhale/.
              • 
 
            • Set 'localAppDir' to /tmp/rWhale/.
              • 
 
            • Specify applications for each workflow step and their inputs. For more details on the format of the configuration file, see Inputs.
              • 
 
            
-
          
 
          3. 
 
        3. Upload the zipped input_data file and configuration file to “My Data” on the DesignSafe Data Depot.
          4. 
 
        4. Upload the CreateLauncherTasks script and a Jupyter notebook with commands for setting up the job on Tapis. You can use this example Jupyter Notebook (run_rWHALE.ipynb) as a template.
          5. 
 
        
-
        On DesignSafe, the files should appear on Data Depot as:
        
+
        On DesignSafe, the files should appear in the Data Depot as:
        
 
        
 ../../../../../_images/DS_data_depot.png
 
        
 
      
 
      
 
      Run Job Through Jupyter
      
-
      This method uses Jupyter Notebook to run the job, accessing Tapis CLI in the backend.
      
+
      This method uses a Jupyter Notebook to run the job, accessing the Tapis CLI in the background.
      
 
        
-
      1. Click on the run_rWHALE.ipynb notebook, then click Open in Jupyter. You will be taken to a new page for editing the Jupyter Notebook.
        2. 
+
      2. Click on the run_rWHALE.ipynb notebook, then click Open in Jupyter. You will be redirected to a new page for editing the Jupyter Notebook.
        3. 
 
      
 
      
 ../../../../../_images/DS_jupyter.png
 
      
 
        
-
      1. Specify settings for running the job on Frontera. Submit the job by running all cells in the Jupyter Notebook (Cell > Run All).
        2. 
+
      2. Specify settings for running the job on Frontera. Submit the job by executing all cells in the Jupyter Notebook (Cell > Run All).
        3. 
 
      
 
        
-
      1. To view the status of the job, navigate to the Workspace on DesignSafe. The right bar will list all jobs that have been submitted in order of newest to oldest. Job outputs can be accessed by clicking on “More Info” on the job.
        2. 
+
      2. To view the status of the job, navigate to the Workspace on DesignSafe. The sidebar will list all jobs that have been submitted, from newest to oldest. Job outputs can be accessed by clicking on “More Info” for the job.
        3. 
 
      
 
      
 ../../../../../_images/DS_workspace.png
 
      
-
        
-
      1. To access the job outputs, click on “More Info” on the job. It will navigate you to the job archive folder on Data Depot.
        
-
        
-
          
-
        • The aggregated outputs are saved in HDF files: “DM.hdf”, “DV.hdf”, and “EDP.hdf” contain the EDP and DL summary results for all built assets. “realizations.hd5” contains the response simulation results for every event simulated per built asset.
          • 
-
        • “launcher.err” contains error messages produced from running the job.
          • 
+
            
+
          1. To access the job outputs, click on “More Info” for the job. You will be directed to the job archive folder in the Data Depot.
            
+
              
+
            • The aggregated outputs are saved in HDF files: “DM.hdf”, “DV.hdf”, and “EDP.hdf” contain the EDP and DL summary results for all built assets. “realizations.hd5” contains the response simulation results for each event simulated per built asset.
              • 
+
            • “launcher.err” contains error messages produced during the job run.
              • 
 
            • “launcher.out” contains the log file.
              • 
 
            
-
        
 
        2. 
 
      
 
      
@@ -270,35 +265,31 @@ 
      Run Job Through Jupyter
 
      
 
      Submit Job Through Tapis
      
-
      This method submits the job using Tapis CLI directly. If using Windows,  this is executed in the Ubuntu subsystem. Please refer to Chapter 9 of the Tapis How-To Guide  for more details.
      
+
      This method involves submitting the job using the Tapis CLI directly. If using Windows, execute this in the Ubuntu subsystem. Please refer to Chapter 9 of the Tapis How-To Guide for more details.
      
 
        
-
      1. First, ensure that Tapis CLI is installed on your computer. Open a Ubuntu window and install Tapis CLI using pip:
        
-
        
-
        pip install tapis-cli
        
-
        
+
      2. First, ensure that the Tapis CLI is installed on your computer. Open an Ubuntu window and install the Tapis CLI using pip:
        
+
        pip install tapis-cli
        
 
        3. 
 
      
-
      Or, install Tapis CLI from Github:
      
+
      Or, install the Tapis CLI from GitHub:
      
 
      git clone https://github.com/TACC-Cloud/tapis-cli-ng.git
 cd tapis-cli-ng/
 pip install --upgrade --user .
 
      
 
      
 
        
-
      1. Set up a Tapis session on each host where you will use the Tapis CLI. This is a one-time operation where you will be asked to agree to terms, select a tenant, and finally enter a username and password for that tenant. Run the command:
        
-
        
-
        tapis auth init
        
-
        
+
      2. Set up a Tapis session on each host where you will use the Tapis CLI. This is a one-time setup where you will be asked to agree to terms, select a tenant, and finally enter a username and password for that tenant. Execute the command:
        
+
        tapis auth init
        
 
        3. 
 
      
-
      You will see an output in the Ubuntu window similar to the following.
      
+
      You will see an output in the Ubuntu window similar to the following:
      
 
      
 
        
 
      • Select “y” to the prompts.
        • 
 
      • Set tenant_name to “designsafe”.
        • 
 
      • Set username and password to your TACC username and password.
        • 
-
      • Keep registry_url to https://index.docker.io
        • 
-
      • Set git_username and git_token to your Github account details. See directions here for more information on generating a git token.
        • 
+
      • Keep registry_url as https://index.docker.io
        • 
+
      • Set git_username and git_token to your GitHub account details. See directions here for more information on generating a git token.
        • 
 
      
 
      
 
      Use of Tapis requires acceptance of the TACC Acceptable Use Policy
@@ -308,25 +299,25 @@ 
      Submit Job Through Tapis
 
    1. Initialize a job with the name “R2D_test_run” by executing the command:
      
-
      
-
      tapis jobs init rWhale-2.1.0 --name R2D_test_run > job.json
      
-
      
+
      tapis jobs init rWhale-2.1.0 --name R2D_test_run > job.json
      
 
      2. 
-
    2. A job.json file is created. You may make changes to this file using VIM Editor, by running the command:
      
-
      
-
      vim job.json
      
-
      
+
    3. A job.json file is created. You may make changes to this file using the VIM Editor, by executing the command:
      
+
      vim job.json
      
 
      4. 
-
    4. Edit the job.json file to specify settings for running the job on Frontera. To make edits in the VIM Editor, type Ctrl+I. To exit out of the editor, type :wq.
      5. 
-
    5. Once the job.json file is prepared, submit the job by running the command:
      
-
      
-
      tapis jobs submit -F job.json
      
-
      
+
    6. Edit the job.json file to specify settings for running the job on Frontera. To make edits in the VIM Editor, press i. To exit out of the editor, type :wq.
      7. 
+
    7. Once the job.json file is prepared, submit the job by executing the command:
      
+
      tapis jobs submit -F job.json
      
 
      8. 
 
    
-
    An ACCEPTED status indicates the job.json was valid, and e-mail alerts (if they were specified in job.json) will track
-the progress of the job. Also, take note of the long hexadecimal ID (job ID) when you submit the job. This identifier can be
-used to track progress and download results.
    
+
    An ACCEPTED status indicates that the job.json was valid, and e-mail alerts (if they were specified in job.json) will track the progress of the job. Also, take note of the long hexadecimal ID (job ID) when you submit the job. This identifier can be used to track progress and download results.
    
 
      
-
    1. To check on the status of a particular job, run the following command with the job ID:
      
+
    2. To check the status of a specific job, execute the command below, replacing <job ID> with the ID of the job:
      
 
      
 
      tapis jobs status <job ID>
      
 
      
 
      3. 
-
    3. Once the job has been completed, the results can be downloaded either from the job archives (accessed from the Workspace on DesignSafe) or directly from Tapis, with the following command:
      
+
    4. After the job is completed, you can download the results. They are available either in the job archives (which can be accessed from the Workspace on DesignSafe) or directly from Tapis. Use the following command to download:
      
 
      
-
      tapis jobs outputs download --progress <job ID string>
      
+
      tapis jobs outputs download --progress <job ID>
      
 
      
 
      5. 
 
    
-
    Or, to download a specific file from the outputs,
    
+
    To download a specific file from the outputs, use:
    
 
    
-
    tapis jobs outputs download <job ID> <name of file>
    
+
    tapis jobs outputs download <job ID> <file name>
    @@ -384,7 +367,7 @@

    Submit Job Through Tapis

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/run-manually/troubleshooting.html b/docs/common/developer_manual/architecture/desktop/run-manually/troubleshooting.html index 1ef83b35..b09f4cb5 100644 --- a/docs/common/developer_manual/architecture/desktop/run-manually/troubleshooting.html +++ b/docs/common/developer_manual/architecture/desktop/run-manually/troubleshooting.html @@ -16,7 +16,7 @@ - + @@ -213,15 +213,15 @@

    Troubleshooting Errors

    -

    If the workflow does not run successfully, the first and best method for troubleshooting is by reading error messages output in the log file. For an example log file, refer to page Backend Applications.

    +

    If the workflow does not run successfully, the first and best method for troubleshooting is to read the error messages output in the log file. For an example of a log file, refer to the page Backend Applications.

    For troubleshooting with the log file, the following steps are recommended:
      -

    • Identify which application failed in the workflow. Read through the log file until an ERROR message appears after one of the Python commands.

      • -

    • Verify that the paths to all workflow files are correct. These paths are specified in the initialization command when run locally, or in the job script when run remotely.

      • -

    • Check that the “ApplicationData” for each application in the configuration file is correct. The workflow will fail if an application does not have all of its required application-specific inputs, or if inputs are provided with an incorrect data type. See the individual pages for the Backend Applications for more details on application-specific inputs.

      • -

    • Check that there are no JSON serialization errors in the configuration file. Mistakes in unclosed brackets or incorrect indentation in the JSON file will cause errors.

      • -

    • Check that the user-defined input files are in the correct format. Mistakes in the header labels or formatting of CSV and JSON input files will cause errors.

      • -

    • To view print messages in the model script during response simulation, rerun Dakota. By default, any print messages in input files are suppressed in the log file. In order to view the messages and debug issues with the model script, navigate to the results folder for one of the building assets in the command window (i.e. “results/1”). You should find three files: dakota.in, dakota.err, and dakota.out. Running the following command will re-execute the UQ application for that particular building asset:

      +

    • Identify the application that failed in the workflow. Read through the log file until an ERROR message appears after one of the Python commands.

      • +

    • Verify that the paths to all workflow files are correct. These paths are specified in the initialization command when run locally, or in the job script when run remotely.

      • +

    • Check that the “ApplicationData” for each application in the configuration file is correct. The workflow will fail if an application does not have all of its required application-specific inputs, or if inputs are provided with an incorrect data type. See the individual pages for the Backend Applications for more details on application-specific inputs.

      • +

    • Check for any JSON serialization errors in the configuration file. Mistakes in unclosed brackets or incorrect indentation in the JSON file will cause errors.

      • +

    • Check that the user-defined input files are in the correct format. Mistakes in the header labels or formatting of CSV and JSON input files will cause errors.

      • +

    • To view print messages in the model script during response simulation, rerun Dakota. By default, any print messages in input files are suppressed in the log file. To view the messages and debug issues with the model script, navigate to the results folder for one of the building assets in the command window (i.e., “results/1”). You should find three files: dakota.in, dakota.err, and dakota.out. Running the following command will re-execute the UQ application for that particular building asset:

      dakota -input dakota.in -output dakota.out -error dakota.err

      @@ -229,7 +229,7 @@
    -

    If problems still persist, you are encouraged to read previously posted questions or post your own at SimCenter Forum. A member of the SimCenter developer team will respond to your question on the platform.

    +

    If problems still persist, you are encouraged to read previously posted questions or post your own at the github discussion page. A member of the SimCenter developer team will respond to your question on the platform.

    @@ -242,7 +242,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/workflows.html b/docs/common/developer_manual/architecture/desktop/workflows.html index f5628226..6e48b81c 100644 --- a/docs/common/developer_manual/architecture/desktop/workflows.html +++ b/docs/common/developer_manual/architecture/desktop/workflows.html @@ -16,7 +16,7 @@ - + @@ -234,7 +234,7 @@

    Creating Workflows

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/workflows/readingTheLog.html b/docs/common/developer_manual/architecture/desktop/workflows/readingTheLog.html index b0366b2e..6a73b91a 100644 --- a/docs/common/developer_manual/architecture/desktop/workflows/readingTheLog.html +++ b/docs/common/developer_manual/architecture/desktop/workflows/readingTheLog.html @@ -16,7 +16,7 @@ - + @@ -213,28 +213,28 @@

    Reading the Log File

    -

    The sequence of tasks carried out by the backend applications is outlined in the log file produced by the workflow. For local runs, this log is displayed in the command terminal and is reproduced in a file named log.txt in the results/ directory. For remote runs through Tapis, this log file is called launcher.out in the job archive folder on DesignSafe. This guide will explain how to understand the statements printed in the log file.

    +

    The sequence of tasks carried out by the backend applications is outlined in the log file produced by the workflow. For local runs, this log is displayed in the command terminal and is reproduced in a file named log.txt in the results/ directory. For remote runs through Tapis, this log file is named launcher.out and is located in the job archive folder on DesignSafe. This guide will explain how to understand the statements printed in the log file.

    The following is an example log file for a successful workflow run. The workflow can be broken down into the following sections:

      -

    1. Read the configuration file:

      +

    2. Reading the configuration file:

        -

      • lines 12-13: Identifies the path to the configuration file, which specifies the job details, and the application registry file, which specifies all available applications.

        • -

      • line 16-62: Reads the application registry file and displays all available applications.

        • -

      • line 64-85: Reads the configuration file and displays the units, local application directory, remote application directory, reference directory, and the applications chosen for each workflow step. Any workflow steps that are skipped (excluded from the configuration file) are also listed here.

        • +

      • lines 12-13: Identifies the path to the configuration file, which specifies the job details, and the application registry file, which lists all available applications.

        • +

      • lines 16-62: Reads the application registry file and displays all available applications.

        • +

      • lines 64-85: Reads the configuration file and displays the units, local application directory, remote application directory, reference directory, and the applications chosen for each workflow step. Any workflow steps that are skipped (excluded from the configuration file) are also listed here.

      3. -

    3. Pre-process building and event data:

      +

    4. Pre-processing building and event data:

        -

      • line 93: Python command for executing the Building application, creating the BIM files for each building asset.

        +

      • line 93: Python command for executing the Building application, which creates the BIM files for each building asset.

        python "C:/rWHALE/applications/createBIM/CSV_to_BIM/CSV_to_BIM.py" "--buildingFile" "C:/rWHALE/earthquake_example/results/buildings1-2.json" "--Min" "1" "--Max" "2" "--buildingSourceFile" "C:/rWHALE/earthquake_example/input_data/input_params.csv" "--getRV"
        • -

      • line 103: Python command for executing the RegionalMapping application, assigning events to each of the building assets.

        +

      • line 103: Python command for executing the RegionalMapping application, which assigns events to each of the building assets.

        python "C:/rWHALE/applications/performRegionalMapping/NearestNeighborEvents/NNE.py" "--buildingFile" "C:/rWHALE/earthquake_example/results/buildings1-2.json" "--filenameEVENTgrid" "C:/rWHALE/earthquake_example/input_data/records/EventGrid.csv" "--samples" "2" "--neighbors" "1"
        @@ -243,40 +243,40 @@
      5. -

    5. Set up and run simulations for each building asset:

      6. +

    6. Setting up and running simulations for each building asset:

    • line 111: Starts with the first building asset. In this first pass, the EVENT, SAM, EDP, SIM files corresponding to “1-BIM.json” are created.

      • -

    • line 118: Python command for executing the Event application, creating the EVENT file for the building asset.

      +

    • line 118: Python command for executing the Event application, which creates the EVENT file for the building asset.

      python "C:/rWHALE/applications/createEVENT/SimCenterEvent/SimCenterEvent.py" "--filenameBIM" "1-BIM.json" "--filenameEVENT" "EVENT.json" "--pathEventData" "C:/rWHALE/earthquake_example/input_data/records/" "--getRV"
      • -

    • line 126: Python command for executing the Modeling application, creating the SAM file for the built asset.

      +

    • line 126: Python command for executing the Modeling application, which creates the SAM file for the building asset.

      python "C:/rWHALE/applications/createSAM/openSeesPyInput/OpenSeesPyInput.py" "--filenameBIM" "1-BIM.json" "--filenameEVENT" "EVENT.json" "--filenameSAM" "SAM.json" "--mainScript" "cantilever.py" "--modelPath" "C:/rWHALE/earthquake_example/input_data/model/" "--ndm" "3" "--dofMap" "1,2,3" "--getRV"
      • -

    • line 134: Python command for executing the EDP application, creating the EDP file for the building asset.

      +

    • line 134: Python command for executing the EDP application, which creates the EDP file for the building asset.

      python "C:/rWHALE/applications/createEDP/userEDP_R/UserDefinedEDP.py" "--filenameBIM" "1-BIM.json" "--filenameEVENT" "EVENT.json" "--filenameSAM" "SAM.json" "--filenameEDP" "EDP.json" "--EDPspecs" "C:/rWHALE/earthquake_example/input_data/EDP_specs.json" "--getRV"
      • -

    • line 142: Python command for executing the Simulation application, creating the SIM file for the building asset.

      +

    • line 142: Python command for executing the Simulation application, which creates the SIM file for the building asset.

      python "C:/rWHALE/applications/performSIMULATION/openSeesPy/OpenSeesPySimulation.py" "--filenameBIM" "1-BIM.json" "--filenameSAM" "SAM.json" "--filenameEVENT" "EVENT.json" "--filenameEDP" "EDP.json" "--filenameSIM" "SIM.json" "--getRV"
      • -

    • lines 153-157: Commands which are written to the workflow driver file. In a “second pass” through the workflow, these commands are executed by running the workflow driver file.

      +

    • lines 153-157: Commands that are written to the workflow driver file. In a “second pass” through the workflow, these commands are executed by running the workflow driver file.

      python "C:/rWHALE/applications/createBIM/CSV_to_BIM/CSV_to_BIM.py" "--buildingFile" "C:/rWHALE/earthquake_example/results/buildings1-2.json" "--Min" "1" "--Max" "2" "--buildingSourceFile" "C:/rWHALE/earthquake_example/input_data/input_params.csv"
 python "C:/rWHALE/applications/createEVENT/SimCenterEvent/SimCenterEvent.py" "--filenameBIM" "1-BIM.json" "--filenameEVENT" "EVENT.json" "--pathEventData" "C:/rWHALE/earthquake_example/input_data/records/"
@@ -308,7 +308,7 @@
      • -

    • line 213: Continues to the second building asset (“2-BIM.json”) and repeats the same workflow steps.

      • +

    • line 213: Continues with the second building asset (“2-BIM.json”) and repeats the same workflow steps.

      @@ -659,7 +659,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/developer_manual/architecture/desktop/workflows/workflowCompatibility.html b/docs/common/developer_manual/architecture/desktop/workflows/workflowCompatibility.html index 4310d27c..8bcd2428 100644 --- a/docs/common/developer_manual/architecture/desktop/workflows/workflowCompatibility.html +++ b/docs/common/developer_manual/architecture/desktop/workflows/workflowCompatibility.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

      Choosing Component Applications

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/architecture/desktop/workflows/workflowStructure.html b/docs/common/developer_manual/architecture/desktop/workflows/workflowStructure.html index 69098a0d..acd2472b 100644 --- a/docs/common/developer_manual/architecture/desktop/workflows/workflowStructure.html +++ b/docs/common/developer_manual/architecture/desktop/workflows/workflowStructure.html @@ -16,7 +16,7 @@ - + @@ -215,7 +215,7 @@

    Workflow Structure

    The backend applications for the HydroUQ app follow a standard workflow:

      -

    1. Read the configuration file. At the start of the workflow, the workflow settings specified in the configuration file are parsed (Inputs). Note that if a particular component application is excluded from the configuration file, then it is automatically skipped in the workflow.

      2. +

    2. Read the configuration file. At the start of the workflow, the settings specified in the configuration file are parsed (Inputs). Note that if a particular component application is not included in the configuration file, it is automatically skipped in the workflow.

    3. Pre-process building and event data. The workflow completes a one-time step of setting up BIM files (Building Application) for each building asset and assigning events to each building site (RegionalMapping Application).

    4. Set up and run simulations for each building asset. From here, the workflow begins its iterative processes of running simulations for each building asset. The workflow runs two passes for each building asset: the supporting simulation files (from the Event, Modeling, EDP, and Simulation Applications) are set up in the first pass, and the workflow commands are executed in the second pass. At the end of the iteration, simulation results are used to perform damage/loss assessment (DL Application). When run remotely on DesignSafe, this iterative process is parallelized across computing resources.

    5. Aggregate outputs for all building assets. After iterating through simulations, the workflow aggregates the content of individual EDP.csv, DM.csv, and DV.csv results for every building asset into single output summary files (Outputs).

      6. @@ -245,7 +245,7 @@

      Workflow Structure

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/developer_manual/coding_style/desktop/coding_style.html b/docs/common/developer_manual/coding_style/desktop/coding_style.html index 529887d9..62520abf 100644 --- a/docs/common/developer_manual/coding_style/desktop/coding_style.html +++ b/docs/common/developer_manual/coding_style/desktop/coding_style.html @@ -16,7 +16,7 @@ - + @@ -415,7 +415,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/developer_manual/examples/desktop/eqAssessment.html b/docs/common/developer_manual/examples/desktop/eqAssessment.html index 1440dbf0..22752721 100644 --- a/docs/common/developer_manual/examples/desktop/eqAssessment.html +++ b/docs/common/developer_manual/examples/desktop/eqAssessment.html @@ -16,7 +16,7 @@ - + @@ -213,7 +213,7 @@

      Earthquake Assessment

      -

      This example is a small-scale regional earthquake risk assessment which performs response simulation and damage/loss estimation for a group of 20 buildings. The buildings are modeled as elastic-perfectly plastic single-degree-of-freedom (SDOF) systems defined by three input model parameters: the weight W, yield strength f_yield, and fundamental period T1. The buildings are distributed in space in a 4x5 grid, within a 3x3 grid of event sites. At each event site, 5 ground motion records of similar intensity are assigned.

      +

      This example is a small-scale regional earthquake risk assessment that performs response simulation and damage/loss estimation for a group of 20 buildings. The buildings are modeled as elastic-perfectly plastic single-degree-of-freedom (SDOF) systems defined by three input model parameters: the weight W, yield strength f_yield, and fundamental period T1. The buildings are distributed in space in a 4x5 grid, within a 3x3 grid of event sites. At each event site, 5 ground motion records of similar intensity are assigned.

      ../../../../_images/regionalearthquakeexample.png
      @@ -221,7 +221,7 @@

      Inputs

      The example input files can be downloaded here: example_eq.zip. For more information about required input files, refer to Inputs.

        -

      1. Configuration file: The configuration file specifies all simulation settings, including the application types, input file names, units, and type of outputs.

        2. +

      2. Configuration file: The configuration file specifies all simulation settings, including the application types, input file names, units, and types of outputs.

       1{
  2  "Name": "rWHALE_",
@@ -615,7 +615,7 @@ 
      Inputs
        -

      1. Event Application: This example uses the SimCenterEvents event application. It takes as input the EventGrid.csv, event files with the ground motion intensity measures, and the site files which specify the five ground motions assigned to each event site.

        2. +

      2. Event Application: This example uses the SimCenterEvents event application. It takes as input the EventGrid.csv, event files with the ground motion intensity measures, and the site files that specify the five ground motions assigned to each event site.

      Event grid file:

    @@ -1055,7 +1055,7 @@

    Run Workflow
    python "C:/rWHALE/applications/Workflow/R2D_workflow.py" "C:/rWHALE/cantilever_example/rWHALE_config_eq.json" --registry "C:/rWHALE/applications/Workflow/WorkflowApplications.json" --referenceDir "C:/rWHALE/cantilever_example/input_data/" -w "C:/rWHALE/cantilever_example/results"
    -

    This command locates the backend applications in the folder “applications”, and the input files in a directory “cantilever_example”. Please ensure that the paths in the command appropriately identify the locations of the files in your directory.

    +

    This command locates the backend applications in the folder “applications” and the input files in a directory “cantilever_example”. Please ensure that the paths in the command appropriately identify the locations of the files in your directory.

    applications
 cantilever_example
 ├── rWHALE_config_eq.json              # configuration file
@@ -1993,7 +1993,7 @@ 
    Outputs
+
      
 
    1. DV_1-19.csv: reports decision variable estimates (repair cost, repair time, injuries) for each building asset.
      2.

    @@ -3313,7 +3313,7 @@

    Outputs

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/examples/desktop/examples.html b/docs/common/developer_manual/examples/desktop/examples.html index f656be87..17930848 100644 --- a/docs/common/developer_manual/examples/desktop/examples.html +++ b/docs/common/developer_manual/examples/desktop/examples.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/examples/desktop/hurricaneAssessment.html b/docs/common/developer_manual/examples/desktop/hurricaneAssessment.html index c3469dd4..16be1d7c 100644 --- a/docs/common/developer_manual/examples/desktop/hurricaneAssessment.html +++ b/docs/common/developer_manual/examples/desktop/hurricaneAssessment.html @@ -16,7 +16,7 @@ - + @@ -213,17 +213,16 @@

    Hurricane Assessment

    -

    This example is a small-scale regional hurricane risk assessment which performs damage/loss estimation for a group of 20 wood buildings in Atlantic City under the Sandy Storm. The buildings are subject to two types of hazards: wind, measured by peak wind speed (PWS), and flooding, measured by flood water depth (FWD). This example does not use response simulation; rather, an IMasEDP application translates the IMs directly to the DL application and uses IM-based component fragility functions to estimate damage. -The distribution of the buildings’ structural types and stories are illustrated below.

    +

    This example is a small-scale regional hurricane risk assessment that performs damage/loss estimation for a group of 20 wooden buildings in Atlantic City during the Sandy Storm. The buildings are subject to two types of hazards: wind, measured by peak wind speed (PWS), and flooding, measured by flood water depth (FWD). This example does not use response simulation; instead, an IMasEDP application translates the IMs directly to the DL application and uses IM-based component fragility functions to estimate damage. The distributions of the buildings’ structural types and stories are illustrated below.

    ../../../../_images/SandyWindFlood.png -

    Peak wind speed and floor water depth maps of the Sandy Storm

    +

    Peak wind speed and flood water depth maps of the Sandy Storm

    Inputs

    The example input files can be downloaded here: example_hu.zip. For more information about required input files, refer to Inputs.

      -

    1. Configuration file: The configuration file specifies all simulation settings, including the application types, input file names, units, and type of outputs.

      2. +

    2. Configuration file: The configuration file specifies all simulation settings, including the application types, input file names, units, and types of outputs.

     1{
  2  "Name": "rWHALE_",
@@ -6048,7 +6047,7 @@ 
    Run Workflow
    python "C:/rWHALE/applications/Workflow/R2D_workflow.py" "C:/rWHALE/hurricane_example/rWHALE_config_hu.json" --registry "C:/rWHALE/applications/Workflow/WorkflowApplications.json" --referenceDir "C:/rWHALE/hurricane_example/input_data/" -w "C:/rWHALE/hurricane_example/results"
    -

    This command locates the backend applications in the folder “applications”, and the input files in a directory “hurricane_example”. Please ensure that the paths in the command appropriately identify the locations of the files in your directory.

    +

    This command locates the backend applications in the folder “applications” and the input files in the directory “hurricane_example”. Please ensure that the paths in the command accurately identify the locations of the files in your directory.

    applications
 hurricane_example
 ├── rWHALE_config_hu.json          # configuration file
@@ -6069,7 +6068,7 @@ 
    Run Workflow
    
 
    The example output files can be downloaded here: output_data_hu.zip. For more information about the output files produced, refer to Outputs.
    
 
      
-
    1. EDP_1-20.csv: reports statistics on EDP results, where the hazard IM is used as the EDP. As in HAZUS, the statistics reported are the median and lognormal standard deviation of peak wind speed (PWS) and flood water depth (FWD).
      2. 
+
    2. EDP_1-20.csv: This file reports statistics on EDP results, where the hazard IM is used as the EDP. As in HAZUS, the statistics reported are the median and lognormal standard deviation of peak wind speed (PWS) and flood water depth (FWD).
      3.

    @@ -6230,7 +6229,7 @@

    Outputs -

  • DM_1-20.csv: reports collapse probability and damage state probability for each building asset. In the table below the “DSG_DS” values 0, 1_1, 2_1, 3_1, and 4_1 are four wind-induced damage states (from minor to severe), while the rest are the flood-induced damage states.

    • +

  • DM_1-20.csv: This file reports the collapse probability and damage state probability for each building asset. In the table below, the “DSG_DS” values 0, 1_1, 2_1, 3_1, and 4_1 represent four wind-induced damage states (from minor to severe), while the rest are the flood-induced damage states.

    • EDP_1-20.csv
    @@ -6912,8 +6911,8 @@

    Outputs -

  • DV_1-20.csv: reports decision variable estimates (i.e., repair cost) for each building asset.

    • +
      +

    1. DV_1-20.csv: This file reports decision variable estimates (i.e., repair cost) for each building asset.

    DM_1-20.csv
    @@ -7136,7 +7135,7 @@

    Outputs

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/examples/desktop/siteResponseAssessment/siteResponseAssessment.html b/docs/common/developer_manual/examples/desktop/siteResponseAssessment/siteResponseAssessment.html index 9a2ba160..694c0454 100644 --- a/docs/common/developer_manual/examples/desktop/siteResponseAssessment/siteResponseAssessment.html +++ b/docs/common/developer_manual/examples/desktop/siteResponseAssessment/siteResponseAssessment.html @@ -16,7 +16,7 @@ - + @@ -1113,7 +1113,7 @@

    Appendix

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/how_to_build/desktop/SimCenterBackend.html b/docs/common/developer_manual/how_to_build/desktop/SimCenterBackend.html index 1ced18e7..36310ecf 100644 --- a/docs/common/developer_manual/how_to_build/desktop/SimCenterBackend.html +++ b/docs/common/developer_manual/how_to_build/desktop/SimCenterBackend.html @@ -16,7 +16,7 @@ - + @@ -214,30 +214,30 @@

    Build the Backend

    -

    SimCenterBackendApplications contains many applications written in C++, C, and Python that are needed by all SimCenter User Interfaces. To build the backend you will need to follow the following steps:

    +

    SimCenterBackendApplications contains many applications written in C++, C, and Python that are needed by all SimCenter User Interfaces. To build the backend, you will need to follow these steps:

    1. Clone the SimCenterBackendApplications repository.

    2. Build SimCenterBackendApplications using the following steps:

      -

      2.1. Create a build directory for the build output, this can be done in the terminal using the command mkdir build.

      +

      2.1. Create a build directory for the build output. This can be done in the terminal using the command mkdir build.

      2.2. Install the backend dependencies using Conan. You can do this by going to the newly created build directory and running the command:

      conan install .. --build missing

      This will install all the dependencies and will build dependencies from their source code as needed.

      -

      2.3. Run CMake configuration this can be done using the command cmake ... Depending on your build environment, especially if you have multiple compilers, you may need to select a specific CMake generator. For instance, on Windows using Visual Studio 2017, you can configure CMake as follows:

      +

      2.3. Run CMake configuration. This can be done using the command cmake ... Depending on your build environment, especially if you have multiple compilers, you may need to select a specific CMake generator. For instance, on Windows using Visual Studio 2017, you can configure CMake as follows:

      -

      cmake .. -G Visual Studio 15 2017 Win64

      +

      cmake .. -G "Visual Studio 15 2017 Win64"

      -

      2.4. Build the release version of the backend, this can be done using the generated build system. For instance, on Unix-based systems when using make files this can be achieved using the command make or make release. When using an IDE like Visual Studio on Windows or XCode on Mac, the generated project can be opened in the IDE and used to build the code. In addition, this can also be done from the terminal using CMake the command:

      +

      2.4. Build the release version of the backend. This can be done using the generated build system. For instance, on Unix-based systems when using make files, this can be achieved using the command make or make release. When using an IDE like Visual Studio on Windows or XCode on Mac, the generated project can be opened in the IDE and used to build the code. Additionally, this can also be done from the terminal using the CMake command:

      cmake --build . --config Release

      3. -

    3. Install the backend applications to a local folder. This can be done by building the install target when using make on Unix-based systems. This can also be from IDE (e.g.) by selecting the install target or project and building it. In addition, this can be done from the terminal using the command:

      +

    4. Install the backend applications to a local folder. This can be done by building the install target when using make on Unix-based systems. This can also be done from an IDE (e.g., by selecting the install target or project and building it). Additionally, this can be done from the terminal using the command:

      -

      cmake --build . --target install or cmake --install if you have CMake 3.15 or later. If building and installation were successful you should find a folder called applications in the repository with all the applications inside it.

      +

      cmake --build . --target install or cmake --install if you have CMake 3.15 or later. If the build and installation were successful, you should find a folder called applications in the repository with all the applications inside it.

    @@ -254,7 +254,7 @@

    Build the Backend

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/developer_manual/how_to_build/desktop/how_to_build.html b/docs/common/developer_manual/how_to_build/desktop/how_to_build.html index 6c09824d..9b40cf38 100644 --- a/docs/common/developer_manual/how_to_build/desktop/how_to_build.html +++ b/docs/common/developer_manual/how_to_build/desktop/how_to_build.html @@ -16,7 +16,7 @@ - + @@ -229,20 +229,20 @@

    1. How to Build

    -

    SimCenter tools all comprise a frontend user interface (UI) and backend applications. They are kept in separate GitHub repositories and are also built separately. The following sections outline (1) the applications needed to build and run, (2) instructions for building the backend applications, (3) instructions for building the frontend UI, and (4) operations to perform in the running UI to link the UI and the backend.

    +

    SimCenter tools consist of a frontend user interface (UI) and backend applications. They are maintained in separate GitHub repositories and are also built separately. The following sections outline (1) the applications needed to build and run, (2) instructions for building the backend applications, (3) instructions for building the frontend UI, and (4) operations to perform in the running UI to link the UI with the backend.

    Note

    -

    As part of our continuous integration process, HydroUQ app is built every time we check code into the NHERI-SimCenter repositories. To do this we make use of a CI service. That current service is appveyor. As a consequence in the HydroUQ app repo that you will clone as part of this build process there is a file appveyor.yml. This file contains shell commands that are issued to set up the operating system, download the software, and build it. If the following commands fail for you, look at the appveyor.yml file to see what commands are currently being called as these may be more up-to-date than what is presented below.

    +

    As part of our continuous integration process, HydroUQ app is built every time we check code into the NHERI-SimCenter repositories. To do this, we use a CI service. The current service is AppVeyor. Consequently, in the HydroUQ app repo that you will clone as part of this build process, there is a file appveyor.yml. This file contains shell commands that are issued to set up the operating system, download the software, and build it. If the following commands fail for you, look at the appveyor.yml file to see what commands are currently being called, as these may be more up-to-date than what is presented below.

    1.1. Install Dependencies

    First, ensure the following dependencies are installed:

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.49/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.49/index.html index b645b858..373036b2 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.49/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.49/index.html @@ -16,7 +16,7 @@ - + @@ -368,7 +368,7 @@

    B.10.49 - RC Flat Slabs

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.51/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.51/index.html index f27603ba..f3a1388a 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.51/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.51/index.html @@ -16,7 +16,7 @@ - + @@ -310,7 +310,7 @@

    B.10.51 - Ordinary Reinforced Masonry Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.52/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.52/index.html index 03298d74..66213916 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.52/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.52/index.html @@ -16,7 +16,7 @@ - + @@ -282,7 +282,7 @@

    B.10.52 - Special Reinforced Masonry Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.61/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.61/index.html index d295d2ba..79a55f94 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.61/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.61/index.html @@ -16,7 +16,7 @@ - + @@ -274,7 +274,7 @@

    B.10.61 - Cold-formed Steel Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.71/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.71/index.html index 70481d33..9f1d97b3 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.71/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/B.10.71/index.html @@ -16,7 +16,7 @@ - + @@ -269,7 +269,7 @@

    B.10.71 - Wood Light Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/index.html index c982041d..3604dd69 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.10/index.html @@ -16,7 +16,7 @@ - + @@ -241,7 +241,7 @@

    B.10 - Super Structure

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.11/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.11/index.html index 30ea660c..9823f292 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.11/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.11/index.html @@ -16,7 +16,7 @@ - + @@ -336,7 +336,7 @@

    B.20.11 - Exterior Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.22/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.22/index.html index 3aea8d6a..5510674b 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.22/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.22/index.html @@ -16,7 +16,7 @@ - + @@ -328,7 +328,7 @@

    B.20.22 - Curtain Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.23/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.23/index.html index 473ae856..12396349 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.23/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/B.20.23/index.html @@ -16,7 +16,7 @@ - + @@ -304,7 +304,7 @@

    B.20.23 - Storefronts

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/index.html index 4f100c8c..40262a63 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.20/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    B.20 - Exterior Enclosure

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.11/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.11/index.html index 0878209f..beefc1ba 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.11/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.11/index.html @@ -16,7 +16,7 @@ - + @@ -258,7 +258,7 @@

    B.30.11 - Roof Coverings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.31/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.31/index.html index 7657fb41..f93f072f 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.31/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.31/index.html @@ -16,7 +16,7 @@ - + @@ -286,7 +286,7 @@

    B.30.31 - Masonry Chimney

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.41/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.41/index.html index b5b2ae42..74b80cec 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.41/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/B.30.41/index.html @@ -16,7 +16,7 @@ - + @@ -234,7 +234,7 @@

    B.30.41 - Masonry Parapet

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/index.html index d6a3c4df..3e294872 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/B.30/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    B.30 - Roofing

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/B/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/B/index.html index d08486ed..8eac5b99 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/B/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/B/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    B - Shell

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.10/C.10.11/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.10/C.10.11/index.html index 22448dca..48466806 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.10/C.10.11/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.10/C.10.11/index.html @@ -16,7 +16,7 @@ - + @@ -261,7 +261,7 @@

    C.10.11 - Partitions

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.10/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.10/index.html index 23c2b236..5d4e52a6 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.10/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.10/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    C.10 - Interior Construction

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.20/C.20.11/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.20/C.20.11/index.html index 61aea300..58946f03 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.20/C.20.11/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.20/C.20.11/index.html @@ -16,7 +16,7 @@ - + @@ -315,7 +315,7 @@

    C.20.11 - Stair Construction

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.20/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.20/index.html index a091fd96..24fef5c5 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.20/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.20/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    C.20 - Stairs

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.11/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.11/index.html index cf5da852..de616999 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.11/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.11/index.html @@ -16,7 +16,7 @@ - + @@ -310,7 +310,7 @@

    C.30.11 - Wall Finishes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.21/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.21/index.html index 9783fae7..534149ae 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.21/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.21/index.html @@ -16,7 +16,7 @@ - + @@ -338,7 +338,7 @@

    C.30.21 - Floor Finishes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.27/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.27/index.html index 674e13ab..c35b61d6 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.27/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.27/index.html @@ -16,7 +16,7 @@ - + @@ -244,7 +244,7 @@

    C.30.27 - Access Pedastal Flooring

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.32/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.32/index.html index 9d60e974..fcb7f47a 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.32/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.32/index.html @@ -16,7 +16,7 @@ - + @@ -322,7 +322,7 @@

    C.30.32 - Ceiling Finishes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.34/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.34/index.html index 435ab503..7a36a8c1 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.34/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/C.30.34/index.html @@ -16,7 +16,7 @@ - + @@ -244,7 +244,7 @@

    C.30.34 - Independent Pendant Lighting

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/index.html index c74e760f..51c79a24 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/C.30/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    C.30 - Interior Finishes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/C/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/C/index.html index f7981be9..87c36ffd 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/C/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/C/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    C - Interiors

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.10/D.10.14/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.10/D.10.14/index.html index 150c5ac7..dfde6531 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.10/D.10.14/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.10/D.10.14/index.html @@ -16,7 +16,7 @@ - + @@ -254,7 +254,7 @@

    D.10.14 - Elevators & Lifts

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.10/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.10/index.html index fcfc0476..fd5dce2d 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.10/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.10/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    D.10 - Conveying

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.21/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.21/index.html index 69244447..7fe322e9 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.21/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.21/index.html @@ -16,7 +16,7 @@ - + @@ -352,7 +352,7 @@

    D.20.21 - Domestic Water Distribution - Cold Water

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.22/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.22/index.html index 2390f6fa..ffffd512 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.22/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.22/index.html @@ -16,7 +16,7 @@ - + @@ -352,7 +352,7 @@

    D.20.22 - Domestic Water Distribution - Hot Water

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.31/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.31/index.html index 656f1a88..f3b270f6 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.31/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.31/index.html @@ -16,7 +16,7 @@ - + @@ -334,7 +334,7 @@

    D.20.31 - Sanitary Waste

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.51/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.51/index.html index 0bddee59..a9071532 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.51/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.51/index.html @@ -16,7 +16,7 @@ - + @@ -361,7 +361,7 @@

    D.20.51 - Chilled Water Distribution

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.61/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.61/index.html index ef526de3..ef52174f 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.61/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/D.20.61/index.html @@ -16,7 +16,7 @@ - + @@ -352,7 +352,7 @@

    D.20.61 - Steam Distribution

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/index.html index 4573437a..85f9f1cc 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.20/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    D.20 - Plumbing

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.31/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.31/index.html index e9270e10..cc7c79f7 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.31/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.31/index.html @@ -16,7 +16,7 @@ - + @@ -706,7 +706,7 @@

    D.30.31 - Cooling Generating Systems - Chilled Water

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.32/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.32/index.html index 49ef31f4..1bb677b3 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.32/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.32/index.html @@ -16,7 +16,7 @@ - + @@ -466,7 +466,7 @@

    D.30.32 - Cooling Generating Systems - Direct Expansion

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.41/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.41/index.html index e3f40458..7b99cd0b 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.41/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.41/index.html @@ -16,7 +16,7 @@ - + @@ -558,7 +558,7 @@

    D.30.41 - Air Distribution Systems

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.52/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.52/index.html index 3047bd68..655acd50 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.52/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.52/index.html @@ -16,7 +16,7 @@ - + @@ -362,7 +362,7 @@

    D.30.52 - Terminal & Package Units

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.67/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.67/index.html index a050f7e6..a05d711a 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.67/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/D.30.67/index.html @@ -16,7 +16,7 @@ - + @@ -260,7 +260,7 @@

    D.30.67 - Controls and Instrumentation

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/index.html index 3df474f4..1069706e 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.30/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    D.30 - HVAC

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.40/D.40.11/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.40/D.40.11/index.html index feff3547..f1379fbb 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.40/D.40.11/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.40/D.40.11/index.html @@ -16,7 +16,7 @@ - + @@ -388,7 +388,7 @@

    D.40.11 - Sprinklers

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.40/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.40/index.html index fc21c596..2d6609ad 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.40/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.40/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    D.40 - Fire Protection

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.11/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.11/index.html index 7852ac0c..f418afe3 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.11/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.11/index.html @@ -16,7 +16,7 @@ - + @@ -362,7 +362,7 @@

    D.50.11 - Electrical Service & Distribution - High Tension

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.12/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.12/index.html index 7588b12b..8df6dd01 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.12/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.12/index.html @@ -16,7 +16,7 @@ - + @@ -532,7 +532,7 @@

    D.50.12 - Electrical Service & Distribution - Low Tension

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.92/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.92/index.html index 1c421587..c7c11c75 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.92/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/D.50.92/index.html @@ -16,7 +16,7 @@ - + @@ -534,7 +534,7 @@

    D.50.92 - Other Electrical Systems

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/index.html index c12d1628..5cd9bbc0 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/D.50/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    D.50 - Electrical

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/D/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/D/index.html index 2ee01512..e8b51031 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/D/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/D/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    D - Services

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/E/E.20/E.20.22/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/E/E.20/E.20.22/index.html index 0617478b..5566456b 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/E/E.20/E.20.22/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/E/E.20/E.20.22/index.html @@ -16,7 +16,7 @@ - + @@ -468,7 +468,7 @@

    E.20.22 - Movable Furnishings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/E/E.20/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/E/E.20/index.html index 3669f2d4..6b50d878 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/E/E.20/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/E/E.20/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    E.20 - Furnishings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/E/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/E/index.html index e91d5854..a086cc8f 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/E/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/E/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    E - Equipments and furnishings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/F/F.10/F.10.12/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/F/F.10/F.10.12/index.html index b1658fd1..87935708 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/F/F.10/F.10.12/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/F/F.10/F.10.12/index.html @@ -16,7 +16,7 @@ - + @@ -234,7 +234,7 @@

    F.10.12 - Special Structures

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/F/F.10/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/F/F.10/index.html index 92f67dd8..59dcac30 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/F/F.10/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/F/F.10/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    F.10 - Special Construction

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/F/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/F/index.html index 90f837a3..8fa29b99 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/F/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/F/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    F - Special Construction & Demolition

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/FEMA_P58_2nd/index.html b/docs/common/dldb/damage/FEMA_P58_2nd/index.html index e7a3c25d..2fd21f5c 100644 --- a/docs/common/dldb/damage/FEMA_P58_2nd/index.html +++ b/docs/common/dldb/damage/FEMA_P58_2nd/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    FEMA P-58 2nd Edition

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/GF/GF.H/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/GF/GF.H/index.html index e5d60614..47f04570 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/GF/GF.H/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/GF/GF.H/index.html @@ -16,7 +16,7 @@ - + @@ -240,7 +240,7 @@

    GF.H - Horizontal Spreading

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/GF/GF.V/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/GF/GF.V/index.html index f51f4bdd..ad6a15ca 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/GF/GF.V/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/GF/GF.V/index.html @@ -16,7 +16,7 @@ - + @@ -240,7 +240,7 @@

    GF.V - Vertical Settlement

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/GF/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/GF/index.html index 05c9a4df..4331caed 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/GF/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/GF/index.html @@ -16,7 +16,7 @@ - + @@ -232,7 +232,7 @@

    GF - Geotechnical Failure

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C1/index.html index decb463f..eb466c3f 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C1/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    LF.C1 - Concrete Moment Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C2/index.html index cf184140..fdf86a98 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C2/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    LF.C2 - Concrete Shear Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C3/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C3/index.html index 7307afd6..f579f7c6 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C3/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.C3/index.html @@ -16,7 +16,7 @@ - + @@ -301,7 +301,7 @@

    LF.C3 - Concrete Frame with Unreinforced Masonry Infill Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.MH/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.MH/index.html index 2106bc8a..e3ef421a 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.MH/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.MH/index.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

    LF.MH - Mobile Homes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC1/index.html index 4bc4fc57..d7f31617 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC1/index.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

    LF.PC1 - Precast Concrete Tilt-Up Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC2/index.html index 888c63d1..e52fb0d3 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.PC2/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    LF.PC2 - Precast Concrete Frames with Concrete Shear Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM1/index.html index 57fe3ccc..74b32009 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM1/index.html @@ -16,7 +16,7 @@ - + @@ -314,7 +314,7 @@

    LF.RM1 - Reinforced Masonry Bearing Walls with Wood or Metal Deck Diaphragms

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM2/index.html index a7539681..38a2189a 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.RM2/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    LF.RM2 - Reinforced Masonry Bearing Walls with Precast Concrete Diaphragms

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S1/index.html index 17225c2e..fc545a42 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S1/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    LF.S1 - Steel Moment Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S2/index.html index 0bb5cff1..535498fd 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S2/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    LF.S2 - Steel Braced Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S3/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S3/index.html index 659cabff..c47f9efe 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S3/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S3/index.html @@ -16,7 +16,7 @@ - + @@ -270,7 +270,7 @@

    LF.S3 - Steel Light Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S4/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S4/index.html index a3abffe1..1f37094c 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S4/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S4/index.html @@ -16,7 +16,7 @@ - + @@ -370,7 +370,7 @@

    LF.S4 - Steel Frame with Cast-in-Place Concrete Shear Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S5/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S5/index.html index 079f47bf..ca9635c4 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S5/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.S5/index.html @@ -16,7 +16,7 @@ - + @@ -301,7 +301,7 @@

    LF.S5 - Steel Frame with Unreinforced Masonry Infill Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.URM/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.URM/index.html index dec2ba6e..84e01b91 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.URM/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.URM/index.html @@ -16,7 +16,7 @@ - + @@ -272,7 +272,7 @@

    LF.URM - Unreinforced Masonry Bearing Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W1/index.html index ad0a0477..f430b62a 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W1/index.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

    LF.W1 - Wood, Light Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W2/index.html index 2a2bec34..946c4557 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/LF.W2/index.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

    LF.W2 - Wood, Commercial & Industrial

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/index.html index 0d2718e5..1199d915 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/LF/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/LF/index.html @@ -16,7 +16,7 @@ - + @@ -246,7 +246,7 @@

    LF - Lifeline Facilities

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/NSA/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/NSA/index.html index 609f5d80..bf271a86 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/NSA/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/NSA/index.html @@ -16,7 +16,7 @@ - + @@ -268,7 +268,7 @@

    NSA - Non-Structural Acceleration-Sensitive

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/NSD/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/NSD/index.html index eae2af11..60e4f8ae 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/NSD/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/NSD/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    NSD - Non-Structural Drift-Sensitive

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C1/index.html index 4b80909e..9324640a 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C1/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    STR.C1 - Concrete Moment Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C2/index.html index a9430d69..d5453f14 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C2/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    STR.C2 - Concrete Shear Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C3/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C3/index.html index b24fbb7b..099735d5 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C3/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.C3/index.html @@ -16,7 +16,7 @@ - + @@ -301,7 +301,7 @@

    STR.C3 - Concrete Frame with Unreinforced Masonry Infill Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.MH/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.MH/index.html index 4274a7bc..78a41635 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.MH/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.MH/index.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

    STR.MH - Mobile Homes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC1/index.html index fe54daa4..b35f4782 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC1/index.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

    STR.PC1 - Precast Concrete Tilt-Up Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC2/index.html index 1aa607c8..b396074c 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.PC2/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    STR.PC2 - Precast Concrete Frames with Concrete Shear Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM1/index.html index 2a356462..9a98cc09 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM1/index.html @@ -16,7 +16,7 @@ - + @@ -314,7 +314,7 @@

    STR.RM1 - Reinforced Masonry Bearing Walls with Wood or Metal Deck Diaphragm

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM2/index.html index 32acc94a..332f53ba 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.RM2/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    STR.RM2 - Reinforced Masonry Bearing Walls with Precast Concrete Diaphragms<

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S1/index.html index b57b78b5..3815878b 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S1/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    STR.S1 - Steel Moment Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S2/index.html index 75f5a590..ceb28981 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S2/index.html @@ -16,7 +16,7 @@ - + @@ -358,7 +358,7 @@

    STR.S2 - Steel Braced Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S3/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S3/index.html index 97f8850a..7ac26bfb 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S3/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S3/index.html @@ -16,7 +16,7 @@ - + @@ -270,7 +270,7 @@

    STR.S3 - Steel Light Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S4/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S4/index.html index 9e73f941..55262552 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S4/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S4/index.html @@ -16,7 +16,7 @@ - + @@ -370,7 +370,7 @@

    STR.S4 - Steel Frame with Cast-in-Place Concrete Shear Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S5/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S5/index.html index 21b61eee..5b618788 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S5/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.S5/index.html @@ -16,7 +16,7 @@ - + @@ -301,7 +301,7 @@

    STR.S5 - Steel Frame with Unreinforced Masonry Infill Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.URM/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.URM/index.html index 5cc3440f..ba72ef8e 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.URM/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.URM/index.html @@ -16,7 +16,7 @@ - + @@ -272,7 +272,7 @@

    STR.URM - Unreinforced Masonry Bearing Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W1/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W1/index.html index f573e1d1..9c161e35 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W1/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W1/index.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

    STR.W1 - Wood, Light Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W2/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W2/index.html index e68cf663..90c58774 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W2/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/STR.W2/index.html @@ -16,7 +16,7 @@ - + @@ -266,7 +266,7 @@

    STR.W2 - Wood, Commercial & Industrial

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/index.html index ac6d7e73..88e93fa3 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/STR/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/STR/index.html @@ -16,7 +16,7 @@ - + @@ -246,7 +246,7 @@

    STR - Structural

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_bldg/index.html b/docs/common/dldb/damage/Hazus_EQ_bldg/index.html index f25ba1aa..82fa8684 100644 --- a/docs/common/dldb/damage/Hazus_EQ_bldg/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_bldg/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    Hazus Earthquake Methodology - Buildings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_trnsp/HRD/index.html b/docs/common/dldb/damage/Hazus_EQ_trnsp/HRD/index.html index fc921b79..66967c35 100644 --- a/docs/common/dldb/damage/Hazus_EQ_trnsp/HRD/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_trnsp/HRD/index.html @@ -16,7 +16,7 @@ - + @@ -232,7 +232,7 @@

    HRD - Road segments

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_trnsp/HTU/index.html b/docs/common/dldb/damage/Hazus_EQ_trnsp/HTU/index.html index fd592f99..d21c256c 100644 --- a/docs/common/dldb/damage/Hazus_EQ_trnsp/HTU/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_trnsp/HTU/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    HTU - Tunnels

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_trnsp/HWB/index.html b/docs/common/dldb/damage/Hazus_EQ_trnsp/HWB/index.html index 479e8daf..5da5c526 100644 --- a/docs/common/dldb/damage/Hazus_EQ_trnsp/HWB/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_trnsp/HWB/index.html @@ -16,7 +16,7 @@ - + @@ -313,7 +313,7 @@

    HWB - Bridges

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/Hazus_EQ_trnsp/index.html b/docs/common/dldb/damage/Hazus_EQ_trnsp/index.html index 10c37ace..e8d279ee 100644 --- a/docs/common/dldb/damage/Hazus_EQ_trnsp/index.html +++ b/docs/common/dldb/damage/Hazus_EQ_trnsp/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    Hazus Earthquake Methodology - Transportation

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/damage/index.html b/docs/common/dldb/damage/index.html index 3f4c4f2e..9bc46bf2 100644 --- a/docs/common/dldb/damage/index.html +++ b/docs/common/dldb/damage/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.31/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.31/index.html index 0f7d5746..63073136 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.31/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.31/index.html @@ -16,7 +16,7 @@ - + @@ -334,7 +334,7 @@

    B.10.31 - Steel Columns

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.33/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.33/index.html index 0883ff7f..d3a16c5e 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.33/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.33/index.html @@ -16,7 +16,7 @@ - + @@ -1327,7 +1327,7 @@

    B.10.33 - Steel Braces

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.35/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.35/index.html index 53b436b0..3d91cfbe 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.35/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.35/index.html @@ -16,7 +16,7 @@ - + @@ -462,7 +462,7 @@

    B.10.35 - Steel Connections

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.41/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.41/index.html index a915e934..34594c59 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.41/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.41/index.html @@ -16,7 +16,7 @@ - + @@ -1516,7 +1516,7 @@

    B.10.41 - RC or Composite Columns

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.42/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.42/index.html index 15c0ba96..7262209d 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.42/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.42/index.html @@ -16,7 +16,7 @@ - + @@ -394,7 +394,7 @@

    B.10.42 - RC or Composite Beams

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.44/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.44/index.html index 5c6bd4a2..1c1e9ce4 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.44/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.44/index.html @@ -16,7 +16,7 @@ - + @@ -784,7 +784,7 @@

    B.10.44 - RC or Composite Shearwalls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.49/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.49/index.html index 6afac333..16c258e4 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.49/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.49/index.html @@ -16,7 +16,7 @@ - + @@ -512,7 +512,7 @@

    B.10.49 - RC Flat Slabs

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.51/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.51/index.html index 6452865a..c6966e40 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.51/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.51/index.html @@ -16,7 +16,7 @@ - + @@ -406,7 +406,7 @@

    B.10.51 - Ordinary Reinforced Masonry Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.52/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.52/index.html index 53cdfa72..21e1569e 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.52/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.52/index.html @@ -16,7 +16,7 @@ - + @@ -346,7 +346,7 @@

    B.10.52 - Special Reinforced Masonry Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.61/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.61/index.html index 8e327bbb..1a80f11a 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.61/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.61/index.html @@ -16,7 +16,7 @@ - + @@ -322,7 +322,7 @@

    B.10.61 - Cold-formed Steel Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.71/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.71/index.html index 4093a9b8..7f0d6270 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.71/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/B.10.71/index.html @@ -16,7 +16,7 @@ - + @@ -317,7 +317,7 @@

    B.10.71 - Wood Light Frame

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/index.html index 54cf8d23..274feb7e 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.10/index.html @@ -16,7 +16,7 @@ - + @@ -241,7 +241,7 @@

    B.10 - Super Structure

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.11/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.11/index.html index d747973c..7257fd45 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.11/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.11/index.html @@ -16,7 +16,7 @@ - + @@ -440,7 +440,7 @@

    B.20.11 - Exterior Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.22/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.22/index.html index 9e5e3ff1..46e65e3f 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.22/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.22/index.html @@ -16,7 +16,7 @@ - + @@ -576,7 +576,7 @@

    B.20.22 - Curtain Walls

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.23/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.23/index.html index a90ab887..7e91e1d8 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.23/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/B.20.23/index.html @@ -16,7 +16,7 @@ - + @@ -440,7 +440,7 @@

    B.20.23 - Storefronts

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/index.html index 4b2a792a..97af3950 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.20/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    B.20 - Exterior Enclosure

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.11/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.11/index.html index a934a26a..280793ac 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.11/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.11/index.html @@ -16,7 +16,7 @@ - + @@ -290,7 +290,7 @@

    B.30.11 - Roof Coverings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.31/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.31/index.html index 8479d322..60527162 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.31/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.31/index.html @@ -16,7 +16,7 @@ - + @@ -334,7 +334,7 @@

    B.30.31 - Masonry Chimney

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.41/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.41/index.html index 15ae37bd..21a502fc 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.41/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/B.30.41/index.html @@ -16,7 +16,7 @@ - + @@ -242,7 +242,7 @@

    B.30.41 - Masonry Parapet

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/index.html index 1543ac85..9ba96012 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/B.30/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    B.30 - Roofing

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/B/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/B/index.html index e738eeb9..e4c12019 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/B/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/B/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    B - Shell

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.10/C.10.11/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.10/C.10.11/index.html index 28dbf1a6..960d586e 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.10/C.10.11/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.10/C.10.11/index.html @@ -16,7 +16,7 @@ - + @@ -301,7 +301,7 @@

    C.10.11 - Partitions

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.10/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.10/index.html index 1df160c3..d24b539f 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.10/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.10/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    C.10 - Interior Construction

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.20/C.20.11/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.20/C.20.11/index.html index 19b21df2..1b3e638f 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.20/C.20.11/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.20/C.20.11/index.html @@ -16,7 +16,7 @@ - + @@ -395,7 +395,7 @@

    C.20.11 - Stair Construction

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.20/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.20/index.html index 58a35868..c529f437 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.20/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.20/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    C.20 - Stairs

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.11/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.11/index.html index 33cb29e0..e2c43ba4 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.11/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.11/index.html @@ -16,7 +16,7 @@ - + @@ -406,7 +406,7 @@

    C.30.11 - Wall Finishes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.21/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.21/index.html index 42365f35..d17abfb9 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.21/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.21/index.html @@ -16,7 +16,7 @@ - + @@ -466,7 +466,7 @@

    C.30.21 - Floor Finishes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.27/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.27/index.html index cadaf6e2..7608cf12 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.27/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.27/index.html @@ -16,7 +16,7 @@ - + @@ -260,7 +260,7 @@

    C.30.27 - Access Pedastal Flooring

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.32/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.32/index.html index fab30016..d807c62a 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.32/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.32/index.html @@ -16,7 +16,7 @@ - + @@ -418,7 +418,7 @@

    C.30.32 - Ceiling Finishes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.34/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.34/index.html index 3e16b04e..562295b4 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.34/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/C.30.34/index.html @@ -16,7 +16,7 @@ - + @@ -260,7 +260,7 @@

    C.30.34 - Independent Pendant Lighting

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/index.html index eea1cf51..a2811daa 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/C.30/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    C.30 - Interior Finishes

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/C/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/C/index.html index acfc4df8..543751f1 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/C/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/C/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    C - Interiors

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.10/D.10.14/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.10/D.10.14/index.html index 79be289c..f6249f2d 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.10/D.10.14/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.10/D.10.14/index.html @@ -16,7 +16,7 @@ - + @@ -286,7 +286,7 @@

    D.10.14 - Elevators & Lifts

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.10/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.10/index.html index deb525df..87de6beb 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.10/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.10/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    D.10 - Conveying

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.21/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.21/index.html index f2ad1f58..ea407553 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.21/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.21/index.html @@ -16,7 +16,7 @@ - + @@ -464,7 +464,7 @@

    D.20.21 - Domestic Water Distribution - Cold Water

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.22/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.22/index.html index cd7ea65a..a415fb64 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.22/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.22/index.html @@ -16,7 +16,7 @@ - + @@ -464,7 +464,7 @@

    D.20.22 - Domestic Water Distribution - Hot Water

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.31/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.31/index.html index 5e9f6d4c..a96d9202 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.31/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.31/index.html @@ -16,7 +16,7 @@ - + @@ -430,7 +430,7 @@

    D.20.31 - Sanitary Waste

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.51/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.51/index.html index 4b426b4e..b96b4cbb 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.51/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.51/index.html @@ -16,7 +16,7 @@ - + @@ -481,7 +481,7 @@

    D.20.51 - Chilled Water Distribution

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.61/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.61/index.html index c07f325c..8645ff9a 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.61/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/D.20.61/index.html @@ -16,7 +16,7 @@ - + @@ -464,7 +464,7 @@

    D.20.61 - Steam Distribution

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/index.html index 408e0b98..2576d448 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.20/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    D.20 - Plumbing

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.31/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.31/index.html index fcf05d73..c334ee46 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.31/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.31/index.html @@ -16,7 +16,7 @@ - + @@ -1154,7 +1154,7 @@

    D.30.31 - Cooling Generating Systems - Chilled Water

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.32/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.32/index.html index 93fdbc91..7456f69c 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.32/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.32/index.html @@ -16,7 +16,7 @@ - + @@ -690,7 +690,7 @@

    D.30.32 - Cooling Generating Systems - Direct Expansion

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.41/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.41/index.html index 9721df64..3aa667e2 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.41/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.41/index.html @@ -16,7 +16,7 @@ - + @@ -870,7 +870,7 @@

    D.30.41 - Air Distribution Systems

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.52/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.52/index.html index 6fe5fc1e..56a5479a 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.52/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.52/index.html @@ -16,7 +16,7 @@ - + @@ -490,7 +490,7 @@

    D.30.52 - Terminal & Package Units

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.67/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.67/index.html index 92b23ebf..61e36a69 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.67/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/D.30.67/index.html @@ -16,7 +16,7 @@ - + @@ -292,7 +292,7 @@

    D.30.67 - Controls and Instrumentation

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/index.html index 0cf01791..f0124316 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.30/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    D.30 - HVAC

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.40/D.40.11/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.40/D.40.11/index.html index 4d87e393..6c385676 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.40/D.40.11/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.40/D.40.11/index.html @@ -16,7 +16,7 @@ - + @@ -532,7 +532,7 @@

    D.40.11 - Sprinklers

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.40/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.40/index.html index 35f23325..06babd8f 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.40/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.40/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    D.40 - Fire Protection

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.11/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.11/index.html index 09521462..9412d3d0 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.11/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.11/index.html @@ -16,7 +16,7 @@ - + @@ -490,7 +490,7 @@

    D.50.11 - Electrical Service & Distribution - High Tension

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.12/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.12/index.html index d5ac9080..d56e1c7c 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.12/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.12/index.html @@ -16,7 +16,7 @@ - + @@ -820,7 +820,7 @@

    D.50.12 - Electrical Service & Distribution - Low Tension

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.92/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.92/index.html index 88f62ee9..0329dec7 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.92/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/D.50.92/index.html @@ -16,7 +16,7 @@ - + @@ -822,7 +822,7 @@

    D.50.92 - Other Electrical Systems

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/index.html index 438b3597..e0f9a84b 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/D.50/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    D.50 - Electrical

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/D/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/D/index.html index 165790b1..ceb551cc 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/D/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/D/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    D - Services

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/E/E.20/E.20.22/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/E/E.20/E.20.22/index.html index afc9ae0c..024b1706 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/E/E.20/E.20.22/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/E/E.20/E.20.22/index.html @@ -16,7 +16,7 @@ - + @@ -226,7 +226,7 @@

    E.20.22 - Movable Furnishings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/E/E.20/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/E/E.20/index.html index 4e2545bc..5afd8c05 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/E/E.20/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/E/E.20/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    E.20 - Furnishings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/E/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/E/index.html index 9939f311..a36b13a4 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/E/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/E/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    E - Equipments and furnishings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/F/F.10/F.10.12/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/F/F.10/F.10.12/index.html index 80525d09..0b31a55b 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/F/F.10/F.10.12/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/F/F.10/F.10.12/index.html @@ -16,7 +16,7 @@ - + @@ -242,7 +242,7 @@

    F.10.12 - Special Structures

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/F/F.10/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/F/F.10/index.html index 1911853f..f0b4a0d2 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/F/F.10/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/F/F.10/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    F.10 - Special Construction

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/F/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/F/index.html index 1e3fe15a..1d2da352 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/F/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/F/index.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    F - Special Construction & Demolition

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/FEMA_P58_2nd/index.html b/docs/common/dldb/repair/FEMA_P58_2nd/index.html index 205e6c12..64646067 100644 --- a/docs/common/dldb/repair/FEMA_P58_2nd/index.html +++ b/docs/common/dldb/repair/FEMA_P58_2nd/index.html @@ -16,7 +16,7 @@ - + @@ -235,7 +235,7 @@

    FEMA P-58 2nd Edition

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_bldg/LF/index.html b/docs/common/dldb/repair/Hazus_EQ_bldg/LF/index.html index 61b31a9f..e54ba4a7 100644 --- a/docs/common/dldb/repair/Hazus_EQ_bldg/LF/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_bldg/LF/index.html @@ -16,7 +16,7 @@ - + @@ -534,7 +534,7 @@

    LF - Lifeline Facilities

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_bldg/NSA/index.html b/docs/common/dldb/repair/Hazus_EQ_bldg/NSA/index.html index f39853c5..a6f2359a 100644 --- a/docs/common/dldb/repair/Hazus_EQ_bldg/NSA/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_bldg/NSA/index.html @@ -16,7 +16,7 @@ - + @@ -506,7 +506,7 @@

    NSA - Non-Structural Acceleration-Sensitive

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_bldg/NSD/index.html b/docs/common/dldb/repair/Hazus_EQ_bldg/NSD/index.html index e957fa26..d2ac7a52 100644 --- a/docs/common/dldb/repair/Hazus_EQ_bldg/NSD/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_bldg/NSD/index.html @@ -16,7 +16,7 @@ - + @@ -506,7 +506,7 @@

    NSD - Non-Structural Drift-Sensitive

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_bldg/STR/index.html b/docs/common/dldb/repair/Hazus_EQ_bldg/STR/index.html index 8803aad1..b854cc5e 100644 --- a/docs/common/dldb/repair/Hazus_EQ_bldg/STR/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_bldg/STR/index.html @@ -16,7 +16,7 @@ - + @@ -534,7 +534,7 @@

    STR - Structural

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_bldg/index.html b/docs/common/dldb/repair/Hazus_EQ_bldg/index.html index 2f9737a7..70692420 100644 --- a/docs/common/dldb/repair/Hazus_EQ_bldg/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_bldg/index.html @@ -16,7 +16,7 @@ - + @@ -234,7 +234,7 @@

    Hazus Earthquake Methodology - Buildings

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_trnsp/HRD/index.html b/docs/common/dldb/repair/Hazus_EQ_trnsp/HRD/index.html index 849e78cf..41886075 100644 --- a/docs/common/dldb/repair/Hazus_EQ_trnsp/HRD/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_trnsp/HRD/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    HRD - Road segments

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_trnsp/HTU/index.html b/docs/common/dldb/repair/Hazus_EQ_trnsp/HTU/index.html index 9faa22c8..77811f20 100644 --- a/docs/common/dldb/repair/Hazus_EQ_trnsp/HTU/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_trnsp/HTU/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    HTU - Tunnels

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_trnsp/HWB/index.html b/docs/common/dldb/repair/Hazus_EQ_trnsp/HWB/index.html index 0c8805ea..e304e54c 100644 --- a/docs/common/dldb/repair/Hazus_EQ_trnsp/HWB/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_trnsp/HWB/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    HWB - Bridges

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/Hazus_EQ_trnsp/index.html b/docs/common/dldb/repair/Hazus_EQ_trnsp/index.html index 314d6d7b..7040b858 100644 --- a/docs/common/dldb/repair/Hazus_EQ_trnsp/index.html +++ b/docs/common/dldb/repair/Hazus_EQ_trnsp/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    Hazus Earthquake Methodology - Transportation

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/dldb/repair/index.html b/docs/common/dldb/repair/index.html index 096347e5..6956023b 100644 --- a/docs/common/dldb/repair/index.html +++ b/docs/common/dldb/repair/index.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/front-matter/abbreviations.html b/docs/common/front-matter/abbreviations.html index 81973525..924f71ce 100644 --- a/docs/common/front-matter/abbreviations.html +++ b/docs/common/front-matter/abbreviations.html @@ -16,7 +16,7 @@ - + @@ -264,7 +264,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/front-matter/cite.html b/docs/common/front-matter/cite.html index 9fb9536a..9b546314 100644 --- a/docs/common/front-matter/cite.html +++ b/docs/common/front-matter/cite.html @@ -16,7 +16,7 @@ - + @@ -239,7 +239,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/front-matter/desktop/ack.html b/docs/common/front-matter/desktop/ack.html index ab74fbeb..93514cf5 100644 --- a/docs/common/front-matter/desktop/ack.html +++ b/docs/common/front-matter/desktop/ack.html @@ -16,7 +16,7 @@ - + @@ -228,7 +228,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/front-matter/desktop/ack_pbe.html b/docs/common/front-matter/desktop/ack_pbe.html index 88b30065..8a931074 100644 --- a/docs/common/front-matter/desktop/ack_pbe.html +++ b/docs/common/front-matter/desktop/ack_pbe.html @@ -16,7 +16,7 @@ - + @@ -242,7 +242,7 @@

    Contributors

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/front-matter/glossary.html b/docs/common/front-matter/glossary.html index f5e4877e..48030d8e 100644 --- a/docs/common/front-matter/glossary.html +++ b/docs/common/front-matter/glossary.html @@ -16,7 +16,7 @@ - + @@ -240,7 +240,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/front-matter/license.html b/docs/common/front-matter/license.html index e540bbfb..da4f4d68 100644 --- a/docs/common/front-matter/license.html +++ b/docs/common/front-matter/license.html @@ -16,7 +16,7 @@ - + @@ -257,7 +257,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/reqments/All-Requirements_allCols.html b/docs/common/reqments/All-Requirements_allCols.html index 5bf1fb9c..1900117a 100644 --- a/docs/common/reqments/All-Requirements_allCols.html +++ b/docs/common/reqments/All-Requirements_allCols.html @@ -16,7 +16,7 @@ - + @@ -2242,7 +2242,7 @@

    Earthquake Loading RequirementsR2D UM 2.3.5

    +

    @@ -2377,7 +2377,7 @@

    Earthquake Loading Requirementseeuq-0002

    - + @@ -6290,7 +6290,7 @@

    DL Database Requirements

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/reqments/HydroUQ-Requirements.html b/docs/common/reqments/HydroUQ-Requirements.html index 0d3bf1f9..de54bd75 100644 --- a/docs/common/reqments/HydroUQ-Requirements.html +++ b/docs/common/reqments/HydroUQ-Requirements.html @@ -16,7 +16,7 @@ - + @@ -2008,7 +2008,7 @@

    Common Research Application Requirements

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/reqments/HydroUQ.html b/docs/common/reqments/HydroUQ.html index 18d29362..14377c3b 100644 --- a/docs/common/reqments/HydroUQ.html +++ b/docs/common/reqments/HydroUQ.html @@ -16,7 +16,7 @@ - + @@ -2024,7 +2024,7 @@

    7.7. Common Research Application Require

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/reqments/key.html b/docs/common/reqments/key.html index 2a258454..8c4e19df 100644 --- a/docs/common/reqments/key.html +++ b/docs/common/reqments/key.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/reqments/reqPelicun.html b/docs/common/reqments/reqPelicun.html index aa85d5ac..eb2acb02 100644 --- a/docs/common/reqments/reqPelicun.html +++ b/docs/common/reqments/reqPelicun.html @@ -16,7 +16,7 @@ - + @@ -1217,7 +1217,7 @@

    Databases & Files

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/reqments/reqQUOFE.html b/docs/common/reqments/reqQUOFE.html index 3a7f6e53..e1dbd4fe 100644 --- a/docs/common/reqments/reqQUOFE.html +++ b/docs/common/reqments/reqQUOFE.html @@ -16,7 +16,7 @@ - + @@ -1104,7 +1104,7 @@

    Common Research Application Requirements

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/HazardSimulationTool_useCase.html b/docs/common/technical_manual/desktop/HazardSimulationTool_useCase.html index 8e69a53a..e23a5fc9 100644 --- a/docs/common/technical_manual/desktop/HazardSimulationTool_useCase.html +++ b/docs/common/technical_manual/desktop/HazardSimulationTool_useCase.html @@ -16,7 +16,7 @@ - + @@ -212,7 +212,7 @@
    -

    Regional Earthquake Hazard Use Cases

    +

    Regional Earthquake Hazard Use Cases

    The major use cases of Regional Earthquake Hazard in R2D can be divided into Scenario-specific or Probabilistic Seismic Hazard Analysis.

    @@ -221,32 +221,32 @@

    Regional Earthquake Hazard Use Cases

    Scenario-specific Earthquake

    -

    This option is to analyze an earthquake scenario that consists of one or more ruptures -based on an earthquake description of a past or hypothetical event. Some use cases -for which this option are:

    +

    This option is for analyzing an earthquake scenario that consists of one or more ruptures +based on the description of a past or hypothetical event. Some use cases +for this option are:

    1. Analysis of a single rupture. For example, running the “Hayward-Rodgers Creek; HN+HS” segment, which is a specific rupture location, length, characteristics, etc.

      2. -

    2. Broader analysis of a scenario. For example, running “an M7 earthquake on the San Andreas Fault.” This would include realizations with different ruptures, that all describe an M7 on the San Andreas.

      3. -

    3. Multiple specified ruptures. This would be used in the case in which a user already has a defined set of ruptures they are interested in studying. This option does not fully capture the probabilistic seismic hazard of a region.

      4. +

    4. Broader analysis of a scenario. For example, running “an M7 earthquake on the San Andreas Fault.” This would include realizations with different ruptures, all describing an M7 on the San Andreas.

      5. +

    5. Multiple specified ruptures. This would be used when a user already has a defined set of ruptures they are interested in studying. This option does not fully capture the probabilistic seismic hazard of a region.

    6. A past earthquake. For example, recreating the Loma Prieta earthquake.

    fig-R2DScenarioSpecificUseCases shows typical scenario-specific use cases in R2D. All the use cases in fig-R2DScenarioSpecificUseCases can be achieved with R2D. The first two options are loading predefined -ground motion records or intensity measures in the region, and are described in +ground motion records or intensity measures in the region and are described in User-specified Ground Motions. The functionality to interface with some physics-based earthquake simulation databases is also under development in R2D. -The third to fifty use cases in fig-R2DScenarioSpecificUseCases requires +The third to fifth use cases in fig-R2DScenarioSpecificUseCases require the earthquake hazard simulation tool, and the last option -can be achieved as described in ShakeMap Earthquake Scenarios).

    +can be achieved as described in ShakeMap Earthquake Scenarios.

    The functions in the earthquake hazard simulation tool required for scenario-specific use cases are Site Definition, Earthquake Rupture Forecasting, Intensity Measure Definition, Ground Motion Prediction Equations, Spatial Correlations, and Ground Motion Record Selection (optional). The “Scenario-specific” option should be selected in the “Scenario Selection” tool tab. More details of the use cases, required inputs, and some benefits/limitations are -summarised in tab-R2DScenarioSpecificUseCases.

    +summarized in tab-R2DScenarioSpecificUseCases.

    ../../../_images/R2DScenarioSpecificUseCases.png

    Scenario-specific earthquake hazard use cases.

    @@ -280,7 +280,7 @@

    Scenario-specific Earthquake

    - + @@ -294,8 +294,8 @@

    Scenario-specific Earthquake

    - - + +
    DV_1-20.csv

    R2D Example 10

    EL.1.1.4

    Interface between asset and regional simulations using DRM method

    _

    R2D UM 2.3.5

    R2D Example 10

    EL.2.7.2

    Nonlinear site response with bidirectional loading

    OpenSHA/UCERF

    Recommended where UCERF ruptures are available (maybe we can show a map). Recommended because it requires no additional inputs other than selections using the R2D interface (source models are openly available).

    No external files are required, and all selections can be done in R2D.

    Users can select out of several choices of GMM and correlation models to use through the R2D interface. Limited in that it only has information available about ruptures in certain locations.

    Users can select from several choices of GMM and correlation models through the R2D interface. Limited in that it only has information about ruptures in certain locations.

    OpenQuake

    Recommended to describe distributed and background seismicity. Also recommended for use where rupture information is unavailable through UCERF.

    ShakeMap

    Re-creation of a past earthquake event by obtaining seismic intensity measures sufficiently representative of the event.

    Inputs are USGS ShakeMap files for a given earthquake scenario. These files must be located in a folder in which at least must be a grid.xml file. The files contain ShakeMaps that include the intensity measures for a given earthquake event as spectral ordinate values (Those can be given as PGA, PGV, PGD, and spectral ordinates at different periods). These files can be obtained from USGS’s ShakeMap archives for real past earthquake events.

    ShakeMap intensity measures (as spectral ordinates) for past earthquakes might not be an accurate representation of this event in locations far from the grid control points (usually recording stations where GMM predictions are adjusted to match real recorded ground motion spectra). Moreover, the set of scenarios is limited.

    Inputs are USGS ShakeMap files for a given earthquake scenario. These files must be located in a folder with at least a grid.xml file. The files contain ShakeMaps that include the intensity measures for a given earthquake event as spectral ordinate values (These can be given as PGA, PGV, PGD, and spectral ordinates at different periods). These files can be obtained from USGS’s ShakeMap archives for real past earthquake events.

    ShakeMap intensity measures (as spectral ordinates) for past earthquakes might not be an accurate representation of the event in locations far from the grid control points (usually recording stations where GMM predictions are adjusted to match real recorded ground motion spectra). Moreover, the set of scenarios is limited.
    @@ -305,7 +305,7 @@

    Regional Probabilistic Seismic Hazard Analysisfig-R2DScenarioSpecificUseCases shows two typical use cases in regional PSHA. +fig-R2DRegionalPSHAUseCases shows two typical use cases in regional PSHA. Both use cases can be achieved in R2D with the earthquake hazard simulation tool. The functions in the earthquake hazard simulation tool required for regional PSHA are Site Definition, @@ -313,7 +313,7 @@

    Regional Probabilistic Seismic Hazard Analysistab-R2DRegionalPSHAUseCases.

    +required inputs, and some benefits/limitations are summarized in tab-R2DRegionalPSHAUseCases.

    ../../../_images/R2DRegionalPSHAUseCases.png

    Regional probabilistic seismic hazard analysis use cases.

    @@ -341,14 +341,14 @@

    Regional Probabilistic Seismic Hazard Analysis

    OpenQuake

    Recommended for use where UCERF ruptures are unavailable.

    -

    External files required. The format of source models can be found here, and a database of global earthquake sources can be found at the GEM’s Global Active Faults Database [Styron2020]

    +

    External files required. The format of source models can be found here, and a database of global earthquake sources can be found at the GEM’s Global Active Faults Database [Styron2020]

    Users need to prepare their earthquake source model.

    Styron2020(1,2)
    -

    Styron, Richard, and Marco Pagani. “The GEM Global Active Faults Database.” Earthquake Spectra, vol. 36, no. 1_suppl, Oct. 2020, pp. 160–180, doi:10.1177/8755293020944182.

    +

    Styron, R., & Pagani, M. (2020). The GEM global active faults database. Earthquake Spectra, 36(1_suppl), 160-180.

    @@ -364,7 +364,7 @@

    Regional Probabilistic Seismic Hazard Analysis

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/SimCenterUQTechnical.html b/docs/common/technical_manual/desktop/SimCenterUQTechnical.html index 3f03a5a7..0d5b1216 100644 --- a/docs/common/technical_manual/desktop/SimCenterUQTechnical.html +++ b/docs/common/technical_manual/desktop/SimCenterUQTechnical.html @@ -16,7 +16,7 @@ - + @@ -569,7 +569,7 @@

    Pre-execution checklist for MFMC

  • The models should take the same input random variables and produce the same output quantities of interest. For example, if the target system is a structure, if one model takes stiffness as a random variable and the other does not, the model violates the problem definition. Similarly, if \(j\)-th output of the HF model is the 1st-floor inter-story drift, \(j\)-th output of the LF model should also be the 1st-floor inter-story drift.

    • -

  • The models should have a clear hierarchy in terms of accuracy and time. When the HF and LF model responses are different, the assumption is that the HF response is always accurate. Therefore, if an LF model runs faster than the HF model, it is optimal to run only the HF model, and there is no reason to introduce MFMC.

    • +

  • The models should have a clear hierarchy in terms of accuracy and time. When the HF and LF model responses are different, the assumption is that the HF response is always accurate. Therefore, if an HF model runs faster than the LF model, it is optimal to always run only the HF model, and there is no reason to introduce MFMC.

  • The response of different models should have a high correlation. The efficiency of MFMC heavily depends on the correlation between the HF and LF model outputs. Only if the correlation is fairly high, the MF estimation is meaningfully efficient than conducting only HF simulations.

    • The efficiency of MFMC can be evaluated using the speed-up ratio, defined as the reduction of computational effort you need to get the same Monte Carlo statistical accuracy by the MFMC and direct Monte Carlo method. fig-MF-SP shows the expected speed-up factor for different computation time ratios and correlation coefficient values. One can notice that only when the ratio of the model evaluation time is greater than 100 and when the correlation is greater than 0.85-0.9, the expected speed-up is significant [Patsialis2021]. The formulation used to estimate the speed-up ratio can be found at the end of this section.

    @@ -678,7 +678,7 @@

    Speed-up

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/UCSDUQTechnical.html b/docs/common/technical_manual/desktop/UCSDUQTechnical.html index a90d378b..34aae57d 100644 --- a/docs/common/technical_manual/desktop/UCSDUQTechnical.html +++ b/docs/common/technical_manual/desktop/UCSDUQTechnical.html @@ -16,7 +16,7 @@ - + @@ -369,7 +369,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/damping.html b/docs/common/technical_manual/desktop/damping.html index fa171e61..dddf5330 100644 --- a/docs/common/technical_manual/desktop/damping.html +++ b/docs/common/technical_manual/desktop/damping.html @@ -16,7 +16,7 @@ - + @@ -317,7 +317,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hazard_occurrence.html b/docs/common/technical_manual/desktop/hazard_occurrence.html index 0f4bdb1a..53549919 100644 --- a/docs/common/technical_manual/desktop/hazard_occurrence.html +++ b/docs/common/technical_manual/desktop/hazard_occurrence.html @@ -16,7 +16,7 @@ - + @@ -214,27 +214,27 @@

    Hazard Occurrence

    -

    A regional seismic risk analysis consists of three elements: (1) an exposure time over which the risk is evaluated, +

    A regional seismic risk analysis comprises three elements: (1) an exposure time over which the risk is evaluated, (2) a loss or quantification to be evaluated, and (3) a specification of the probability of incurring the loss during the specified -exposure time. These three elements can be formulated into different workflows and one of the possible workflows can include: -(1) hazard analysis (understanding the possible seismic sources in the studied region), (2) ground motion characterization -(representing the possible seismicity by earthquake ground motions at each site, e.g., time history records, intensity measures), +exposure time. These three elements can be formulated into different workflows. One possible workflow includes: +(1) hazard analysis (understanding the potential seismic sources in the studied region), (2) ground motion characterization +(representing the potential seismicity by earthquake ground motions at each site, e.g., time history records, intensity measures), (3) inventory identification (collecting the basic information of the buildings and infrastructures to be analyzed), and (4) response/damage/loss assessment (mapping the ground motion characteristics and building inventory to the response, damage, and loss in the region).

    -

    Different from the seismic risk analysis of a single structure, the spatial correlation between different site locations usually needs to be -considered in estimating the total damage and loss of a portfolio of buildings or infrastructures. This consideration is naturally fulfilled if +

    Unlike the seismic risk analysis of a single structure, the spatial correlation between different site locations usually needs to be +considered when estimating the total damage and loss of a portfolio of buildings or infrastructures. This consideration is naturally fulfilled if physics-based earthquake simulation is involved. If empirical ground motion models are used, then spatial correlation models (please see more details in Ground Motion Intensity Spatial Correlation Model Options) need to be evaluated and used in sampling the ground motion maps explicitly. The simulated ground motions are then used as the input for assessing the regional seismic risk of the portfolio.

    To propagate the uncertainty in the seismic hazard, ground motion characteristics, and structural damage and loss fragility, the risk analysis -typically needs a sufficient number of samples (realizations) to reliably estimate the mean and variation of possible damage and loss. For instance, -if applying the conventional Monte Carlo method (e.g., [Bazzurro07]), for each of the considered earthquake scenarios (with a specific magnitude and location), -many ground motion intensity maps are first simulated. Then, for each of the ground motion maps, several assessments of damage and loss are +typically requires a sufficient number of samples (realizations) to reliably estimate the mean and variation of potential damage and loss. For instance, +when applying the conventional Monte Carlo method (e.g., [Bazzurro07]), for each of the considered earthquake scenarios (with a specific magnitude and location), +numerous ground motion intensity maps are first simulated. Then, for each of the ground motion maps, several assessments of damage and loss are conducted to propagate the uncertainty in the inventory, response analysis model, and/or fragility functions. The process is repeated for -all considered earthquake scenarios which leads to a tremendous number of realizations and an excessive computational demand.

    +all considered earthquake scenarios, leading to a large number of realizations and an excessive computational demand.

    To alleviate the computational cost of regional seismic risk analysis, a concept of probabilistic earthquake scenarios was proposed and developed by -many researchers (e.g., [Chang00], [Jayaram10], [Vaziri12]). The key idea is to first reduce the full set of possible earthquake scenarios that affect the studied -region to a select subset of earthquakes each of which is used to evaluate the building and infrastructure performance, and then aggregate the results with +many researchers (e.g., [Chang00], [Jayaram10], [Vaziri12]). The key idea is to first reduce the full set of potential earthquake scenarios that affect the studied +region to a select subset of earthquakes. Each of these earthquakes is used to evaluate the performance of the buildings and infrastructure, and then the results are aggregated with modified hazard-consistent probabilities for individual selected earthquakes. The modified probabilities of selected earthquakes are optimized so that the original hazard curves of individual sites can be recovered as much as possible ([Han12]). Different optimization algorithms are implemented (e.g., [Wang20]), different target functions beyond the error in hazard curve (e.g., [Miller14]) are considered, and multiple intensity measures (e.g., [Ma22]) @@ -256,7 +256,7 @@

    Manzour and Davidson (2016) ()\[min \Sigma_{i=1}^{I} \Sigma_{r=1}^{R} w_{ir} (e_{ir}^{+}+e_{ir}^{-})\]

    where \(e_{ir}^{+}\) and \(e_{ir}^{-}\) are the errors resulting from overestimating and underestimating, respectively, the reference hazard curve for the site \(i\) -at the return period r. The weight \(w_{ir}\) is taken as the return period so that the error occurring at a longer return period (i.e., higher intensity level) can be +at the return period \(r\). The weight \(w_{ir}\) is taken as the return period so that the error occurring at a longer return period (i.e., higher intensity level) can be scaled relatively more than the error occurring at a shorter return period. This typically helps the final fitting given the nonlinear shape of a hazard curve.

    Assuming we have overall \(J\) candidate earthquakes, for any earthquake scenario \(j\), we can use empirical ground motion model(s) to compute its resulting ground motion intensity (i.e., the mean and standard deviation) for each site \(i\): \(m_{lnSa}\) and \(\sigma_{lnSa}\). Suppose that for the site \(i\) and return period \(r\), @@ -284,43 +284,36 @@

    Manzour and Davidson (2016)../../../_images/hazard_occurrence_flowchart.png

    Workflow to generate a hazard-consistent reduced sample of earthquakes and ground motion maps using the OPS method.

    -

    In this example, we want to get a minimal number of earthquakes with modified occurrence rates to recover the reference hazard curves at each site location as much as possible. +

    In this example, we aim to get a minimal number of earthquakes with modified occurrence rates to recover the reference hazard curves at each site location as much as possible. The figure below plots the example sites in the San Francisco Bay Area, whose longitude and latitude data can be downloaded here.

    ../../../_images/hazard_occurrence_sites.png

    Site locations for hazard occurrence modeling and probabilistic earthquake scenarios.

    Once downloaded, the site csv file can be loaded in the site widget of the HAZ panel under the “Earthquake Scenario Simulation” option. The figure below shows the site widget -after the file is loaded. The site-specific Vs30 data are fetched from Wills et al. 2015 model.

    +after the file is loaded. The site-specific Vs30 data are fetched from the Wills et al. 2015 model.

    ../../../_images/hazard_occurrence_site_widget.png

    Loading the site csv file in the site widget (scattering locations).

    -

    The figure below summarizes the hazard occurrence configuration: we want to select earthquake scenarios from the UCERF2 seismic sources. For -this demonstration, we want to have 100 candidate earthquakes. The backend script in the R2D follows the suggestion by Han and Davidson (2012) +

    The figure below summarizes the hazard occurrence configuration: we aim to select earthquake scenarios from the UCERF2 seismic sources. For +this demonstration, we aim to have 100 candidate earthquakes. The backend script in the R2D follows the suggestion by Han and Davidson (2012) ([Han12]) to first order the candidate by its true occurrence rates - so the 100 candidates here are the ones with the highest occurrence rates to -the region. For the reduced representation with the probabilistic earthquake scenarios, we want no more than 10 earthquakes and no more than 100 +the region. For the reduced representation with the probabilistic earthquake scenarios, we aim to have no more than 10 earthquakes and no more than 100 ground motion maps. Note this setup is just for demonstration as the example site locations are not distant from each other - for more distributed sites, the candidate earthquake number, as well as the reduced earthquake number, should be increased to have better-matching results ([Han12]).

    ../../../_images/hazard_occurrence_configuration.png

    Configurations for hazard occurrence modeling.

    -

    For all sites, we do not prescribe but fetch the site-specific hazard curves directly from USGS API. -The intensity measure for the hazard curve is the response spectral acceleration at 1.0 second, Sa(T=1.0). The hazard curves are digitized at -four different return periods from 224 years to 2475 years. These four levels will be used later to compute the error for fitting the hazard curve. -These hazard curves are also saved during the simulation, please see the example format in ./src/HazardCurves.json.

    -

    Once everything above is set up, please click the “Run Hazard Simulation” button located in the bottom right of the HAZ panel. It may take 5 to 10 -minutes to run the entire example (an internet connection is needed for fetching data in this example). Once the run is completed, there are three types of -output files in the “Output Directory” (please feel free to change the default one to your own directory in the -textbox located in the bottom left of the HAZ panel):

    +

    For all sites, we fetch the site-specific hazard curves directly from the USGS API, rather than prescribing them. The intensity measure for the hazard curve is the response spectral acceleration at 1.0 second, Sa(T=1.0). The hazard curves are digitized at four different return periods, ranging from 224 years to 2475 years. These four levels will be used later to compute the error for fitting the hazard curve. These hazard curves are also saved during the simulation; please see the example format in ./src/HazardCurves.json.

    +

    Once the above setup is complete, please click the “Run Hazard Simulation” button located in the bottom right of the HAZ panel. It may take 5 to 10 minutes to run the entire example (an internet connection is required for fetching data in this example). Once the run is completed, three types of output files can be found in the “Output Directory” (you are free to change the default directory to your own in the textbox located in the bottom left of the HAZ panel):

      -

    1. RupSampled.json: the information about the selected probabilistic earthquake ruptures (example).

      2. -

    2. InfoSampledGM.json: the information about the selected ground motion maps (example).

      3. -

    3. SiteIM.json: the simulated intensity measures of the selected ground motion maps (example).

      4. +

    4. RupSampled.json: This file contains information about the selected probabilistic earthquake ruptures (example).

      5. +

    5. InfoSampledGM.json: This file contains information about the selected ground motion maps (example).

      6. +

    6. SiteIM.json: This file contains the simulated intensity measures of the selected ground motion maps (example).

    -

    To validate the selected earthquake scenarios, the figure below contrasts the recovered seismic hazard curve and the reference hazard curve -(ground truth) for each site.

    +

    To validate the selected earthquake scenarios, the figure below contrasts the recovered seismic hazard curve and the reference hazard curve (ground truth) for each site.

    ../../../_images/hazard_occurrence_result.png

    Comparison of recovered and reference hazard curves for the first 9 sites in the example.

    @@ -367,7 +360,7 @@

    Manzour and Davidson (2016)

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/UQ/uqengine.html b/docs/common/technical_manual/desktop/hydro/UQ/uqengine.html index 94482f6d..833e332a 100644 --- a/docs/common/technical_manual/desktop/hydro/UQ/uqengine.html +++ b/docs/common/technical_manual/desktop/hydro/UQ/uqengine.html @@ -16,7 +16,7 @@ - + @@ -226,7 +226,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.html b/docs/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.html index 10ad0f8a..46033958 100644 --- a/docs/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.html +++ b/docs/common/technical_manual/desktop/hydro/cfdsolver/cfdsolver.html @@ -16,7 +16,7 @@ - + @@ -229,8 +229,8 @@
    @@ -238,11 +238,11 @@

    5.1. Turbulence models\(L\) associated with the motions containing the largest percentage of the kinetic energy.

    Since DNS is computational expensive, the large eddy simulation was proposed by Joseph Smagorinsky in 1963. The idea of LES was to ignore the smaller length scales that are expensive to resolve. Using a low-pass filtering technique, the most expensively small-scale information is removed from the numerical solution.

    -

    The HydroUQ application presently does not support either DNS or LES simulations. At present, only Reynolds Averaged Navier-Stokes (RANS) simulations are supported by the HydroUQ. If you would like to use the DNS / LES, please leave a feature request on our message board.

    +

    The HydroUQ application presently does not support either DNS or LES simulations. At present, only Reynolds Averaged Navier-Stokes (RANS) simulations are supported by the HydroUQ. If you would like to use the DNS / LES, please leave a feature request on our github discussion page.

    RANS is based on the observation that the flow field contained a time-averaged state \((U)\) and small-local oscillations \((u')\). Additional transport equation(s) are introduced for the turbulence variables and solved with the velocity and pressure. Often these can be algebraic models that depend on parameters like the velocity of the flow, distance from the wall. These models help estimate the eddy viscosity due to turbulence and is added to the molecular viscosity of the fluid. The momentum that would be transferred by the small eddies is instead translated to a viscous transport. In general, the turbulence dissipation dominates over viscous dissipation everywhere, except in the viscous sublayer close to the solid walls. Wall models help resolve the right turbulence dissipation in these sublayers.

    -
    +
    Four regimes of the flow over a flat-plate -

    Fig. 5.1.1 Four regimes of the flow for a flow considered over a flat-plate

    +

    Fig. 5.1.1 Four regimes of the flow for a flow considered over a flat-plate

    As shown in Fig. 5.1.1, the flow near a flat bottom can be divided into four regimes. The velocity of the fluid at the wall is nearly zero. Viscous effects domainate in a small thin layer above the wall. This is known as the viscous sublayer. Further away from the all is a transition region known as the buffer sublayer. Here, the turbulence stresses start to increase and dominate over the viscous stresses. Further away is the log-law region, where the flow is fully turbulent and the average velocity is related to the log of the distance to the wall. Even further away is the free-stream region. The thickness of the viscous and buffer sublayers are almost hundred times smaller than the log-law region. Thus, instead of resolving them, a wall model can be used that would assume an analytic solution for the flow in the viscous layer and thus reduce the computational costs. Such an approximation is reasonable for applications in geological flows.

    There are several turbulence models available for usage. Among them, two models are made available for usage in the HydroUQ application. It is important to choose the right models for the application of interest.

    @@ -270,7 +270,7 @@

    5.2. Input file formats

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/cfdsolver/kepsilon.html b/docs/common/technical_manual/desktop/hydro/cfdsolver/kepsilon.html index 9367d253..40571696 100644 --- a/docs/common/technical_manual/desktop/hydro/cfdsolver/kepsilon.html +++ b/docs/common/technical_manual/desktop/hydro/cfdsolver/kepsilon.html @@ -16,7 +16,7 @@ - + @@ -282,7 +282,7 @@

    References

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/cfdsolver/komegasst.html b/docs/common/technical_manual/desktop/hydro/cfdsolver/komegasst.html index d363598d..3336e43a 100644 --- a/docs/common/technical_manual/desktop/hydro/cfdsolver/komegasst.html +++ b/docs/common/technical_manual/desktop/hydro/cfdsolver/komegasst.html @@ -16,7 +16,7 @@ - + @@ -276,7 +276,7 @@

    References

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/fvm/fvm.html b/docs/common/technical_manual/desktop/hydro/fvm/fvm.html index a3d4cef1..f01435ae 100644 --- a/docs/common/technical_manual/desktop/hydro/fvm/fvm.html +++ b/docs/common/technical_manual/desktop/hydro/fvm/fvm.html @@ -16,7 +16,7 @@ - + @@ -382,7 +382,7 @@

    6.5. References

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/surge-cause.html b/docs/common/technical_manual/desktop/hydro/hazards/surge-cause.html index 320aa968..b2524a32 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/surge-cause.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/surge-cause.html @@ -16,7 +16,7 @@ - + @@ -244,7 +244,7 @@

    Causes of storm surge

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/surge-events.html b/docs/common/technical_manual/desktop/hydro/hazards/surge-events.html index 67e9120d..8126a077 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/surge-events.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/surge-events.html @@ -16,7 +16,7 @@ - + @@ -261,7 +261,7 @@

    Storm surge events

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/surge-numerics.html b/docs/common/technical_manual/desktop/hydro/hazards/surge-numerics.html index 4238f8f1..20bce3fb 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/surge-numerics.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/surge-numerics.html @@ -16,7 +16,7 @@ - + @@ -275,7 +275,7 @@

    References

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/surge-risk.html b/docs/common/technical_manual/desktop/hydro/hazards/surge-risk.html index 09bffce4..84c28d7d 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/surge-risk.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/surge-risk.html @@ -16,7 +16,7 @@ - + @@ -272,7 +272,7 @@

    NJ coast

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/tsu-cause.html b/docs/common/technical_manual/desktop/hydro/hazards/tsu-cause.html index 2cd7bc92..4796b122 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/tsu-cause.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/tsu-cause.html @@ -16,7 +16,7 @@ - + @@ -282,7 +282,7 @@

    Extraterrestrial

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/tsu-events.html b/docs/common/technical_manual/desktop/hydro/hazards/tsu-events.html index cb94cd1b..279cff78 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/tsu-events.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/tsu-events.html @@ -16,7 +16,7 @@ - + @@ -261,7 +261,7 @@

    Tsunami events

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/tsu-numerics.html b/docs/common/technical_manual/desktop/hydro/hazards/tsu-numerics.html index b4dfafff..40c121b5 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/tsu-numerics.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/tsu-numerics.html @@ -16,7 +16,7 @@ - + @@ -294,7 +294,7 @@

    References

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/tsu-risk.html b/docs/common/technical_manual/desktop/hydro/hazards/tsu-risk.html index d330a71b..e8db1d2d 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/tsu-risk.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/tsu-risk.html @@ -16,7 +16,7 @@ - + @@ -263,7 +263,7 @@

    Hazard vs. risk

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/hazards/water.html b/docs/common/technical_manual/desktop/hydro/hazards/water.html index 5c7f460b..1864b08b 100644 --- a/docs/common/technical_manual/desktop/hydro/hazards/water.html +++ b/docs/common/technical_manual/desktop/hydro/hazards/water.html @@ -16,7 +16,7 @@ - + @@ -285,7 +285,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/mpm/mpm.html b/docs/common/technical_manual/desktop/hydro/mpm/mpm.html index 92b3318b..5e377c4d 100644 --- a/docs/common/technical_manual/desktop/hydro/mpm/mpm.html +++ b/docs/common/technical_manual/desktop/hydro/mpm/mpm.html @@ -16,7 +16,7 @@ - + @@ -446,7 +446,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/swcfdcoupling/swcfdcoupling.html b/docs/common/technical_manual/desktop/hydro/swcfdcoupling/swcfdcoupling.html index f92ef813..b26ddf8d 100644 --- a/docs/common/technical_manual/desktop/hydro/swcfdcoupling/swcfdcoupling.html +++ b/docs/common/technical_manual/desktop/hydro/swcfdcoupling/swcfdcoupling.html @@ -16,7 +16,7 @@ - + @@ -226,7 +226,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-output.html b/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-output.html index 37e0976a..f677c730 100644 --- a/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-output.html +++ b/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-output.html @@ -16,7 +16,7 @@ - + @@ -243,7 +243,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-runtime.html b/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-runtime.html index 0ebb6c78..23130898 100644 --- a/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-runtime.html +++ b/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-runtime.html @@ -16,7 +16,7 @@ - + @@ -243,7 +243,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-theory.html b/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-theory.html index 6776f374..7d820064 100644 --- a/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-theory.html +++ b/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-theory.html @@ -16,7 +16,7 @@ - + @@ -247,7 +247,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-topo.html b/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-topo.html index 7f100d29..b2626462 100644 --- a/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-topo.html +++ b/docs/common/technical_manual/desktop/hydro/swsolver/geoclaw-topo.html @@ -16,7 +16,7 @@ - + @@ -488,7 +488,7 @@

    Generate topo files

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/swsolver/simcenter-topo.html b/docs/common/technical_manual/desktop/hydro/swsolver/simcenter-topo.html index 60477037..41e807d6 100644 --- a/docs/common/technical_manual/desktop/hydro/swsolver/simcenter-topo.html +++ b/docs/common/technical_manual/desktop/hydro/swsolver/simcenter-topo.html @@ -16,7 +16,7 @@ - + @@ -249,7 +249,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/hydro/swsolver/swsolver.html b/docs/common/technical_manual/desktop/hydro/swsolver/swsolver.html index 6e545e48..f602fc4e 100644 --- a/docs/common/technical_manual/desktop/hydro/swsolver/swsolver.html +++ b/docs/common/technical_manual/desktop/hydro/swsolver/swsolver.html @@ -16,7 +16,7 @@ - + @@ -278,7 +278,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/spatial_correlation.html b/docs/common/technical_manual/desktop/spatial_correlation.html index 6bb38f94..0dbec21e 100644 --- a/docs/common/technical_manual/desktop/spatial_correlation.html +++ b/docs/common/technical_manual/desktop/spatial_correlation.html @@ -16,7 +16,7 @@ - + @@ -214,7 +214,7 @@

    Ground Motion Intensity Spatial Correlation Model Options

    -

    The regional seismic risk analysis requires the prediction of ground motion intensities at multiple sites. Such joint predictions need to consider the correlation between ground motion intensities at different sites given a specific earthquake scenario. In general, ground motion models predicting intensities at an individual site \(i\) due to an earthquake \(j\) have the following form:

    +

    Regional seismic risk analysis requires the prediction of ground motion intensities at multiple sites. Such joint predictions need to consider the correlation between ground motion intensities at different sites given a specific earthquake scenario. In general, ground motion models predicting intensities at an individual site \(i\) due to an earthquake \(j\) have the following form:

    ()\[ln(Y_{ij}) = ln(\bar{Y}_{ij}) + \epsilon_{ij} + \eta_j\]

    where \(Y_{ij}\) is the intensity measure (e.g., \(Sa(T)\)), \(\bar{Y}_{ij}\) is the predicted median intensity (given magnitude, distance, period, and site conditions), \(\epsilon_{ij}\) is the intra-event residual, and \(\eta_j\) is the inter-event residual. It is assumed that \(\epsilon_{ij}\) and \(\eta_j\) are random variables with zero means and standard deviations \(\sigma_{ij}\) and \(\tau_j\).

    @@ -233,27 +233,27 @@

    Intra-event Correlation Model Options\(Z_u\) and \(Z_{u+h}\) are the random variable realizations at sites with a distance of \(h\). The covariance between \(Z_u\) and \(Z_{u+h}\) are:

    ()\[C(h) = E[(Z_u - \mu_Z)(Z_{u+h} - \mu_Z)]\]
    -

    where \(\mu_Z\) is the mean (which is zero under the stationarity assumption). Note this spatial covariance can also be related to the semivariogram with:

    +

    where \(\mu_Z\) is the mean (which is assumed as zero in [Jayaram08]). Note this spatial covariance can also be related to the semivariogram with:

    ()\[C(h) = C(0) - \gamma(h)\]

    Similarly, the correlation coefficient is defined as:

    ()\[\rho(h) = \frac{C(h)}{C(0)} = 1 - \frac{\gamma(h)}{C(0)}\]
    -

    Given the semivariogram is often preferred in geostatistical practice (because it does not require a prior estimation of the mean), many studies were carried out to find the semivariogram models to derive the correlation \(rho(h)\) of ground motion intensities. The available models in the current HydroUQ app are briefly summarized in the following sections.

    +

    Given the semivariogram is often preferred in geostatistical practice (because it does not require a prior estimation of the mean), many studies were carried out to find the semivariogram models to derive the correlation \(\rho(h)\) of ground motion intensities. The available models in the current HydroUQ app are briefly summarized in the following sections.

    Jayaram and Baker (2009)

    -

    [Jayaram09] adopted an exponential model for the semivariogram function with an isotropic hypothesis (i.e., the distance \(h\) is the separation length):

    +

    [Jayaram09] adopted an exponential model for the semivariogram function with an isotropic hypothesis (i.e., the distance \(h\) is the separation length):

    -()\[\gamma(h) = a[1 - exp(-3h / b)]\]
    -

    where a and b are two modeling coefficients, namely sill and the range of the semivariogram function, respectively. When \(h = 0\), \(\gamma(h=0) = 0\) which leads to \(\rho(h = 0) = 1\). As the distance between two sites increases, i.e., \(h\) increases, \(\gamma(h)\) increases and \(\rho(h)\) decreases, which is consistent with the decaying trend of correlation between the two sites. After calibrating the model to past earthquake recordings, the following model was proposed for predicting the spatial correlation \(\rho(h)\):

    +()\[\gamma(h) = a[1 - \exp(-3h / b)]\]
    +

    where \(a\) and \(b\) are two modeling coefficients, namely sill and the range of the semivariogram function, respectively. When \(h = 0\), \(\gamma(h=0) = 0\) which leads to \(\rho(h = 0) = 1\). As the distance between two sites increases, i.e., \(h\) increases, \(\gamma(h)\) increases and \(\rho(h)\) decreases, which is consistent with the decaying trend of correlation between the two sites. After calibrating the model to past earthquake recordings, the following model was proposed for predicting the spatial correlation \(\rho(h)\):

    -()\[\rho(h) = exp(-3h / b)\]
    -

    The range of the semivariogram function \(b\) was found to depend on the similarity of \(V_{S30}\) values in the given region. If the \(V_{S30}\) values do not show clustering, the \(b\) is computed by:

    +()\[\rho(h) = \exp(-3h / b)\]

    +

    The range of the semivariogram function \(b\) was found to depend on the similarity of \(V_{S30}\) values in the given region. If the \(V_{S30}\) values do not show clustering, \(b\) is computed by:

    -()\[ \begin{align}\begin{aligned}b = 8.5 + 17.2T, T < 1s\\b = 22.0 + 3.7T, T \leq 1s\end{aligned}\end{align} \]
    -

    where T is the period. If the \(V_{S30}\) values are very close in the given region, the \(b\) can be computed by:

    +()\[ \begin{align}\begin{aligned}b = 8.5 + 17.2T, T < 1s\\b = 22.0 + 3.7T, T \geq 1s\end{aligned}\end{align} \] +

    If the \(V_{S30}\) values are very close in the given region, \(b\) can be computed by:

    -()\[ \begin{align}\begin{aligned}b = 40.7 - 15.0T, T < 1s\\b = 22.0 + 3.7T, T \leq 1s\end{aligned}\end{align} \]
    +()\[ \begin{align}\begin{aligned}b = 40.7 - 15.0T, T < 1s\\b = 22.0 + 3.7T, T \geq 1s\end{aligned}\end{align} \]

    Note

    Earthquakes that were considered in the development: Anza earthquake, Alum Rock earthquake, Parkfield earthquake, Chi-Chi earthquake, Northridge earthquake, Big Bear City earthquake, and Chino Hills earthquake.

    @@ -261,16 +261,16 @@

    Jayaram and Baker (2009)

    Loth and Baker (2013)

    -

    Note that the cross-semivariograms between different pairs of intensity measures can be different, for instance, \(\rho_{Sa(T=0.1s),Sa(T=0.2s)}(h)\) might be greater than \(\rho_{Sa(T=0.1s), Sa(T=1s)}(h)\). This means one needs to repeat a calibration process many times to develop semivariogram functions and correlation models that have higher resolutions (i.e., direct semivariogram fit). Instead of fitting each semivariogram independently, [Loth13] proposed a predictive model for spatial covariance of spectral accelerations at different periods:

    +

    Note that the cross-semivariograms between different pairs of intensity measures can be different; for instance, \(\rho_{Sa(T=0.1s),Sa(T=0.2s)}(h)\) might be greater than \(\rho_{Sa(T=0.1s),Sa(T=1s)}(h)\). This means one needs to repeat a calibration process many times to develop semivariogram functions and correlation models that have higher resolutions (i.e., direct semivariogram fit). Instead of fitting each semivariogram independently, [Loth13] proposed a predictive model for spatial covariance of spectral accelerations at different periods:

    -()\[\textbf{C}(h) = \textbf{B}^1 exp(-3h/20) + \textbf{B}^2 exp(-3h/70) + \textbf{B}^3 I_{h=0}\]
    -

    where \(I_{h=0}\) is the indicator function equal to 1 at \(h = 0\) and 0 otherwise. And the three coefficient matrices \(\textbf{B}^1\), \(\textbf{B}^2\), and \(\textbf{B}^3\) were calibrated by 2080 recordings from 8 earthquakes.

    -
    +()\[\textbf{C}(h) = \textbf{B}^1 \exp(-3h/20) + \textbf{B}^2 \exp(-3h/70) + \textbf{B}^3 I_{h=0}\]
    +

    where \(I_{h=0}\) is the indicator function equal to 1 at \(h = 0\) and 0 otherwise. The three coefficient matrices \(\textbf{B}^1\), \(\textbf{B}^2\), and \(\textbf{B}^3\) were calibrated by 2080 recordings from 8 earthquakes.

    +
    ../../../_images/spatial_correlation_1.png -

    Location of recordings from the 8 earthquakes considered by [Loth13]

    +

    Location of recordings from the 8 earthquakes considered by [Loth13]

    - - +
    Short-range coregionalization matrix, \(\textbf{B}^1\)
    +@@ -396,8 +396,8 @@

    Loth and Baker (2013)

    Short-range coregionalization matrix, \(\textbf{B}^1\)
    - - +
    Short-range coregionalization matrix, \(\textbf{B}^2\)
    +@@ -523,8 +523,8 @@

    Loth and Baker (2013)

    Short-range coregionalization matrix, \(\textbf{B}^2\)
    - - +
    Short-range coregionalization matrix, \(\textbf{B}^3\)
    +@@ -653,7 +653,7 @@

    Loth and Baker (2013)

    Markhvida et al. (2017)

    -

    [Markhvida17] proposed to use Principal Component Analysis (PCA) to develop the predictive model for cross-correlograms. In theory, PCA performs a linear transformation of the variables of interest to an orthogonal basis, where the resulting projections onto the new basis are uncorrelated:

    +

    [Markhvida17] proposed to use Principal Component Analysis (PCA) to develop the predictive model for cross-correlograms. In theory, PCA performs a linear transformation of the variables of interest to an orthogonal basis, where the resulting projections onto the new basis are uncorrelated:

    ()\[\textbf{P} \textbf{Z} = \textbf{Y}\]

    where \(\textbf{P}\) is an orthogonal linear transformation matrix, \(\textbf{Z}\) is the original data matrix, and \(\textbf{Y}\) is the transformed variable matrix which contains uncorrelated principal components \(\textbf{Y}_i\). Since \(\textbf{P}\) is orthogonal, the inversion is easy to compute:

    @@ -663,8 +663,8 @@

    Markhvida et al. (2017) ()\[C_i(h) = c_{0i}I_{h=0} + c_{1i} exp(-3h/a_{1i}) + c_{2i} exp(-3h/a_{2i})\]

    where \(c_{0i}\), \(c_{1i}\), \(c_{2i}\), \(a_{1i}\), and \(a_{2i}\) are modeling coefficients for \(i^{th}\) principal component. Instead of directly simulating the desired intensity measures, this PCA-based method would first simulate uncorrelated variables using \(C_i(h)\) and then transform them back to intensity measures.

    -

    Short-range coregionalization matrix, \(\textbf{B}^3\)
    - +
    Principal component transformation coefficients
    +@@ -1110,22 +1110,22 @@

    Markhvida et al. (2017)

    Principal component transformation coefficients
    -

    The general idea is to include more degrees of freedom in the predictive model if compared to linear models (e.g., [Loth13]). The figure below contrasts the correlation coefficient functions by PCA and the linear model by [Loth13].

    -
    +

    The general idea is to include more degrees of freedom in the predictive model compared to linear models (e.g., [Loth13]). The figure below contrasts the correlation coefficient functions of PCA and the linear model by [Loth13].

    +
    ../../../_images/spatial_correlation_2.png -

    Comparison of principal component analysis (PCA) model and linear model of coregionalization (LMC) correlograms and cross-correlograms ([Loth13]) for different periods

    +

    Comparison of principal component analysis (PCA) model and linear model of coregionalization (LMC) correlograms and cross-correlograms ([Loth13]) for different periods

    -
    Jayaram08
    -

    Jayaram N, Baker JW. Statistical tests of the joint distribution of spectral acceleration values. Bulletin of the Seismological Society of America 2008; 98(5):2231–2243.

    +
    Jayaram08(1,2)
    +

    Jayaram, N., & Baker, J. W. (2008). Statistical tests of the joint distribution of spectral acceleration values. Bulletin of the Seismological Society of America, 98(5), 2231-2243.

    -
    Jayaram09
    +
    Jayaram09

    Jayaram, N., & Baker, J. W. (2009). Correlation model for spatially distributed ground‐motion intensities. Earthquake Engineering & Structural Dynamics, 38(15), 1687-1708.

    -
    Loth13(1,2,3,4,5)
    +
    Loth13(1,2,3,4,5)

    Loth, C., & Baker, J. W. (2013). A spatial cross‐correlation model of spectral accelerations at multiple periods. Earthquake Engineering & Structural Dynamics, 42(3), 397-417.

    -
    Markhvida17
    +
    Markhvida17

    Markhvida, M., Ceferino, L., & Baker, J. W. (2018). Modeling spatially correlated spectral accelerations at multiple periods using principal component analysis and geostatistics. Earthquake Engineering & Structural Dynamics, 47(5), 1107-1123.

    @@ -1133,7 +1133,7 @@

    Markhvida et al. (2017)

    Inter-event Correlation Model Options

    -

    [Baker08] presented equations to predict the inter-event residual correlations of spectral acceleration values, +

    [Baker08] presented equations to predict the inter-event residual correlations of spectral acceleration values, using the Next Generation Attenuation (NGA) ground motion library and the new NGA ground motion models (GMMs). A predictive equation was presented that provides correlations between logarithmic spectral accelerations at two periods. This equation was observed to be valid for @@ -1149,10 +1149,10 @@

    Inter-event Correlation Model Options[Baker08]) +enough extent that correlations change noticeably. The predictive equations (Eq. 5 and Eq. 6 in [Baker08]) are implemented in R2D.

    -
    Baker08(1,2)
    +
    Baker08(1,2)

    Baker, J. W., & Jayaram, N. (2008). Correlation of spectral acceleration values from NGA ground motion models. Earthquake Spectra, 24(1), 299-317.

    @@ -1169,7 +1169,7 @@

    Inter-event Correlation Model Options

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/technical_manual.html b/docs/common/technical_manual/desktop/technical_manual.html index e911a9a7..9a609660 100644 --- a/docs/common/technical_manual/desktop/technical_manual.html +++ b/docs/common/technical_manual/desktop/technical_manual.html @@ -16,7 +16,7 @@ - + @@ -298,7 +298,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/technical_manual/desktop/uqTechnical.html b/docs/common/technical_manual/desktop/uqTechnical.html index c808e176..9dff4997 100644 --- a/docs/common/technical_manual/desktop/uqTechnical.html +++ b/docs/common/technical_manual/desktop/uqTechnical.html @@ -16,7 +16,7 @@ - + @@ -230,7 +230,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/about/HazardSimulation/about.html b/docs/common/user_manual/about/HazardSimulation/about.html index 67fefc1a..96948df8 100644 --- a/docs/common/user_manual/about/HazardSimulation/about.html +++ b/docs/common/user_manual/about/HazardSimulation/about.html @@ -16,7 +16,7 @@ - + @@ -213,8 +213,8 @@

    About

    -

    This is an open-source research application, HydroUQ Github page, released under a BSD clause 2 license, Copyright and License. The HydroUQ app can be used to simulate regional ground motion intensities given user-defined earthquake scenarios. Users can specify artificial earthquake sources (e.g., point sources) or select from faults in earthquake forecast models (e.g., UCERF3). Users can also specify the site soil velocities in addition to using the default database in |opensha link|. HydroUQ app provides different options for ground motion prediction equations and correlation models to compute spatially correlated intensity measures at user-defined site locations. Users can use HydroUQ app to generate multiple realizations to represent the uncertainty from earthquake sources and soil properties. If the user provide valid account information on |peer nga link|, HydroUQ app will download and parse ground motion accelerograms for running time history analyses.

    -

    This is Version 3.1.0 of the tool. Users are encouraged to comment on what additional features and capabilities they would like to see in this application. These requests and feedback can be submitted through an anonymous user survey. We greatly appreciate any input you have. If there are features you want, chances are many of your colleagues also would benefit from them. Users are encouraged to review the lbl-requirements to see what features are planned for this application.

    +

    This is an open-source research application, HydroUQ Github page, released under a BSD clause 2 license, Copyright and License. The HydroUQ app can be used to simulate regional ground motion intensities given user-defined earthquake scenarios. Users can specify artificial earthquake sources (e.g., point sources) or select from faults in earthquake forecast models (e.g., UCERF3). Users can also specify the site soil velocities in addition to using the default database in OpenSHA. HydroUQ app provides different options for ground motion prediction equations and correlation models to compute spatially correlated intensity measures at user-defined site locations. Users can use HydroUQ app to generate multiple realizations to represent the uncertainty from earthquake sources and soil properties. If the user provide valid account information on PEER_NGA, HydroUQ app will download and parse ground motion accelerograms for running time history analyses.

    +

    This is Version 4.0.0 of the tool. Users are encouraged to comment on what additional features and capabilities they would like to see in this application. These requests and feedback can be submitted through an anonymous user survey. We greatly appreciate any input you have. If there are features you want, chances are many of your colleagues also would benefit from them. Users are encouraged to review the lbl-requirements to see what features are planned for this application.

    @@ -227,7 +227,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/about/Hydro/HydroUQtutorial.html b/docs/common/user_manual/about/Hydro/HydroUQtutorial.html index c61a20c8..0477d1f7 100644 --- a/docs/common/user_manual/about/Hydro/HydroUQtutorial.html +++ b/docs/common/user_manual/about/Hydro/HydroUQtutorial.html @@ -16,7 +16,7 @@ - + @@ -242,7 +242,7 @@

    HydroUQ for a Python Model Interface -

    Step 0. Prepare a Python Model

    @@ -267,9 +267,9 @@

    HydroUQ for a Python Model InterfaceOpenSeesPy example manual, navigate to Structural Example - Elastic Truss Analysis

  • In the Elastic Truss Analysis page, click the download button. Create a new folder named TrussExample and save ElasticTruss.py in the folder.

    • -
    +
    ../../../../_images/step2_openseesPy.svg -

    Download OpenSeesPy Elastic Truss Analysis

    +

    Download OpenSeesPy Elastic Truss Analysis

    Important

    @@ -283,14 +283,14 @@

    HydroUQ for a Python Model Interface{$PathToPythonExe} should be replaced with the python path found in the preference window.

    -
    +
    ../../../../_images/step1_preference_default.svg -

    Find the Python path in File-Preference in the menu bar

    +

    Find the Python path in File-Preference in the menu bar

    According to ElasticTruss.py, the analysis should print out “Passed!”, meaning the model ran successfully.

    -
    +
    ../../../../_images/step0_openseespy_test.svg -

    Testing ElasticTruss.py

    +

    Testing ElasticTruss.py

    Now we are ready to run a probabilistic analysis using this model.

    @@ -315,7 +315,7 @@

    HydroUQ for a Python Model Interface -

    Step 1. Modify the Model Script to Define Random Variables and Quantities of Interest

    @@ -541,9 +541,9 @@

    HydroUQ for a Python Model Interfaceresults.out should be created in the folder TrussExample, which contains the following two values.

    -
    +
    ../../../../_images/step1_results.svg -

    Created results.out

    +

    Created results.out

    If the test was successful, remove all the files except ElasticTruss.py and params.py. This model can now be readily imported into quoFEM.

    @@ -555,7 +555,7 @@

    HydroUQ for a Python Model Interface -

    Step 2. Run quoFEM

    @@ -579,9 +579,9 @@

    HydroUQ for a Python Model Interfacedakota-Sensitivity Analysis for this example.

    -
    +
    ../../../../_images/step2_UQ.PNG -

    UQ Panel

    +

    UQ Panel

    Tip

    @@ -592,9 +592,9 @@

    HydroUQ for a Python Model Interface +
    ../../../../_images/step2_FEM.PNG -

    FEM Panel

    +

    FEM Panel

    The post-processing script is not needed in this example because the results.out is already printed in the main script. See here for more about the post-processing script

    @@ -602,23 +602,23 @@

    HydroUQ for a Python Model Interfaceparams.py, quoFEM auto-populates the RVs as follows.

    -
    +
    ../../../../_images/step2_RV.PNG -

    RV Panel

    +

    RV Panel

    Then one can modify their distribution types and parameters. Further, if you believe some variables are correlated, use the correlation button to specify the values.

    -
    +
    ../../../../_images/step2_RV_corr.PNG -

    Correlation Window

    +

    Correlation Window

  • EDP (Engineering Demand Parameters) or QoI (Quantities of Interest)

    Because our Python script will write two values in results.out file, we will specify two QoI as follows.

    -
    +
    ../../../../_images/step2_QoI.PNG -

    EDP Panel

    +

    EDP Panel

    The order should match that written in the results.out file, and the specified name of QoIs is used only for the display in this example. Please see here to learn about vector QoIs that have a length greater than 1

    @@ -626,23 +626,23 @@

    HydroUQ for a Python Model Interface +
    ../../../../_images/step2_RES1.PNG -

    Working directories

    +

    Working directories

    Once the analysis is done, move on to the RES tab.

    RES (Results)

    The results indicate that the horizontal displacement is most affected by the height while vertical displacement is dominated by the elastic modulus and vertical force.

    -
    +
    ../../../../_images/step2_RES2.PNG -

    RES - Summary

    +

    RES - Summary

    And this can be confirmed by the strong/weak trends observed in the scatter plots.

    -
    +
    ../../../../_images/step2_RES3.PNG -

    RES - Data Values - Scatter plot of H and disp_x

    +

    RES - Data Values - Scatter plot of H and disp_x

    The right/left mouse buttons (fn-clink, option-click, or command-click replaces the left click on Mac) will allow the users to draw various scatter plots, histograms, and cumulative mass plots from the sample points.

    See Dakota or SimCenterUQ theory manual to learn more about the sensitivity analysis and the difference between main and total indices.

    @@ -654,7 +654,7 @@

    HydroUQ for a Python Model Interface -

    Step 3. Run quoFEM at DesignSafe

    @@ -675,48 +675,48 @@

    HydroUQ for a Python Model InterfaceDesignSafe at Texas Super Computing Center (TACC). For this, login to DesignSafe by clicking Login on the right upper corner of quoFEM, or by clicking RUN at DesignSafe Button

    -
    +
    ../../../../_images/step3_Login.PNG -

    Login window

    +

    Login window

    If you don’t have a DesignSafe account, you can easily sign up at DesignSafe.

    Then by clicking RUN at DesignSafe, one can specify the job details. Please see here for more details on the number of nodes and processors.

    -
    +
    ../../../../_images/step3_Run.PNG -

    Run at DesignSafe

    +

    Run at DesignSafe

    If one sets 32 processors, quoFEM will run 32 model evaluations simultaneously in parallel. By clicking Submit, the jobs will be automatically submitted to DesignSafe. (See here to learn more about “What happens when RUN at DesignSafe button is clicked”). Depending on how busy the Frontera at TACC is, your job may start within 30 sec or it may take longer. By clicking GET from DesignSafe, one can check the status. The major stages are Queued, Running, and Finished.

    -
    +
    ../../../../_images/step3_Jobs.PNG -

    Run at DesignSafe

    +

    Run at DesignSafe

    Once the status is changed to Finished, select the job name and click Retrieve Data. The quoFEM will load the data. The results should be the same as the local analysis results.

    -
    +
    ../../../../_images/step2_RES2.PNG -

    Sensitivity Analysis Results from DesignSafe

    +

    Sensitivity Analysis Results from DesignSafe

    The created results files can be found in your Remote working directory which can be found in the preference window. Furthermore, one can access all the output files and logs created by quoFEM by signing in to DesignSafe and navigating in the menu bar to Workspace - Tools & Applications - Jobs Status (at the right-hand side edge), and clicking More info and View button (See below figures).

    -
    +
    ../../../../_images/step3_DesignSafe1.svg -

    DesignSafe - Job status

    +

    DesignSafe - Job status

    -
    +
    ../../../../_images/step3_DesignSafe2.svg -

    DesignSafe - See results files

    +

    DesignSafe - See results files

    • -

    @@ -738,7 +738,7 @@

    HydroUQ for a Python Model Interfaceops.out file in the directory. Other .log and .err files can have information to help you identify the cause of the failure. Please feel free to ask us through user forum.

    +

    When quoFEM analysis fails and the error message points you to a working directory, often the detailed error messages are written in ops.out file in the directory. Other .log and .err files can have information to help you identify the cause of the failure. Please feel free to ask us through github discussion page.

  • When “RUN at DesignSafe” fails

    @@ -755,7 +755,7 @@

    HydroUQ for a Python Model Interfaceuser forum, for any users who have questions or feature requests. The response is mostly within 24 hours and usually much less.

    +

    We have an active github discussion page, for any users who have questions or feature requests. The response is mostly within 24 hours and usually much less.

    • @@ -775,7 +775,7 @@

    HydroUQ for a Python Model Interface

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/about/Hydro/about.html b/docs/common/user_manual/about/Hydro/about.html index c091a01a..57c2f486 100644 --- a/docs/common/user_manual/about/Hydro/about.html +++ b/docs/common/user_manual/about/Hydro/about.html @@ -16,7 +16,7 @@ - + @@ -111,7 +111,7 @@
    -

    This is Version 3.1.0 of the tool. Users are encouraged to comment on what additional features and capabilities they would like to see in this application. These requests and feedback can be submitted through an anonymous user survey. We greatly appreciate any input you have. If there are features you want, chances are many of your colleagues also would benefit from them. We encourage you to review the Requirments Traceability Matrix to see what features are planned.

    +

    This is Version 4.0.0 of the tool. Users are encouraged to comment on what additional features and capabilities they would like to see in this application. These requests and feedback can be submitted through an anonymous user survey. We greatly appreciate any input you have. If there are features you want, chances are many of your colleagues also would benefit from them. We encourage you to review the Requirments Traceability Matrix to see what features are planned.

    The additional simulations required for uncertainty quantification can be prohibitively expensive. To overcome this impediment, the user has the option to perform the response simulations on the Frontera and Lonestar6 supercomputers, located at the Texas Advanced Computing Center (TACC). These HPC resources are made available to the user through NHERI DesignSafe-CI, the cyberinfrastructure provider for the distributed NSF-funded Natural Hazards Engineering Research Infrastructure (NHERI) facility.

    -
    -

    1.2. Capabilities and Limitations

    -

    Below are key, modular capabilities and limitations of HydroUQ, categorized by Uncertainty Quantification (UQ), Design Building General Information (GI), Structural Information & Analysis Model (SIM), Natural Hazard Event (EVT), Engineering Demand Parameters (EDP), Finite Element Method (FEM), Random Variables (RV), and Results (RES).

    +
    +

    1.2. Capabilities

    +

    Below are key, modular capabilities of HydroUQ, categorized by Uncertainty Quantification (UQ), Design Building General Information (GI), Structural Information & Analysis Model (SIM), Natural Hazard Event (EVT), Engineering Demand Parameters (EDP), Finite Element Method (FEM), Random Variables (RV), and Results (RES).

    --+ - - - - - - - - - -

    Item

    Capabilities

    Limitations

    UQ

    Easy access to different UQ methods. Parallelized UQ algorithms. Multiple alternative algorithms for each method.

    No support for optimization under uncertainty and local sensitivity analysis.

    GI

    Basic interface for user-provided general building information (e.g. location, age, and building type).

    No support for sophisticated user-defined building types. Yet to implement a map-style interface for building location so users must type in coordinates manually.

    SIM

    Easy interface for user-provided structural information and analysis models (e.g. geometry, material properties, and boundary conditions). Provides a multi-degree-of-freedom (MDOF) building model. Allows for OpenSeesPy models defined in user-provided scripts. Supports investigation of multiple potential building models with associated “belief” values for each.

    Does not make full use of information (e.g. location of the building and date built influences which ASCE guidelines may have applied) provided in GI for automated structural information and analysis model generation.

    EVT

    OpenFOAM computational fluid dynamics (CFD) simulations. GeoClaw Shallow-Water Equations (SWE) and OpenFOAM CFD one-way coupled simulations. FOAMySees two-way coupled CFD-FEA simulations. Material Point Method (MPM, ClaymoreUW) simulations. Pre-built and validated digital wave-flume twins.

    Most simulation types are limited to remote execution on TACC supercomputers.

    FEM

    Easy interface for user-provided simulation models (not only FEM models but any model), including Opensees, Python, or any other simulation models (e.g. FEM or non-FEM software) with only a python-scripted interface provided by the user to HydroUQ.

    Graphical user-interface support for alternative finite element analysis (FEA) software and non-FEA software is limited.

    RV

    Twelve different kinds of probability distributions with correlations.

    Does not expose which variables support this feature well to the user. No support for random fields, non-Gaussian copular, or user-defined variables.

    EDP

    Scalar and vector EDP parsing. Hazard specific EDP lists (e.g. tsunami and storm-surge). Support for user-defined EDPs.

    Separate Intensity Measures (IMs) and EDPs (load and response), in functionality and GUI presentation, is not fully delineated yet.

    RES

    Interactive plotting of scatter charts, histograms, and cumulative mass functions. Summary of statistics. Save data into a CSV file.

    Limited flexibility for in-app visualization. Results must be ported to external plotting software for more advanced visualization.

    General

    Graphical user interface. Free and easy one-click remote running option.

    Limited guidance on how to effectively contribute to this open-source project.
    @@ -301,7 +290,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/bugs.html b/docs/common/user_manual/bugs.html index 9508ee3b..ceb698a0 100644 --- a/docs/common/user_manual/bugs.html +++ b/docs/common/user_manual/bugs.html @@ -16,7 +16,7 @@ - + @@ -219,7 +219,7 @@

    8. Bugs & Feature Requests

    -

    If you find bugs, have feature requests, or have questions about how to install or use the application, please post on the Message Board. +

    If you find bugs, have feature requests, or have questions about how to install or use the application, please post on the github discussion page. To avoid duplication, try the Search feature before creating a New Topic. When creating a New Topic to report a bug or new feature request it would be helpful if you could place in the Subject area, as shown in Fig. 8.2.1, an indication of what the post is about:

    Table of Contents

    @@ -253,7 +253,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/dcv/Hydro/HydroUQ.html b/docs/common/user_manual/dcv/Hydro/HydroUQ.html index 0396bb35..05d61e3d 100644 --- a/docs/common/user_manual/dcv/Hydro/HydroUQ.html +++ b/docs/common/user_manual/dcv/Hydro/HydroUQ.html @@ -16,7 +16,7 @@ - + @@ -255,7 +255,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/examples/desktop/examples.html b/docs/common/user_manual/examples/desktop/examples.html index 271c58d9..1637317b 100644 --- a/docs/common/user_manual/examples/desktop/examples.html +++ b/docs/common/user_manual/examples/desktop/examples.html @@ -16,7 +16,7 @@ - + @@ -49,7 +49,7 @@ - + @@ -125,8 +125,12 @@
  • 2. User Interface
  • 3. Tools
  • 4. Examples
  • 5. Best Practices
    • @@ -229,6 +233,78 @@ @@ -359,7 +459,7 @@
    Cylinder Half-Submerged in Flow - UW WASIRF

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/examples/desktop/hdro-0001/README.html b/docs/common/user_manual/examples/desktop/hdro-0001/README.html index 211165c1..f6e61e68 100644 --- a/docs/common/user_manual/examples/desktop/hdro-0001/README.html +++ b/docs/common/user_manual/examples/desktop/hdro-0001/README.html @@ -7,7 +7,7 @@ - Coupled Digital Twin Example — Hydro-UQ documentation + 4.3. Multi-Story Shear Building - Coupled CFD-FEM Digital Twin — Hydro-UQ documentation @@ -16,7 +16,7 @@ - + @@ -50,6 +50,8 @@ + + @@ -119,11 +121,28 @@
  • 9. Abbreviations

    • User Manual

    -
      +
      • 1. Installation
      • 2. User Interface
      • 3. Tools
        • -
      • 4. Examples
        • +
      • 4. Examples +
      • 5. Best Practices
      • 6. Troubleshooting
      • 7. Requirements
        • @@ -193,7 +212,9 @@
      • »
        • -
      • Coupled Digital Twin Example
        • +
      • 4. Examples »
        • + +
      • 4.3. Multi-Story Shear Building - Coupled CFD-FEM Digital Twin
      • @@ -212,86 +233,97 @@
        -
        -

        Coupled Digital Twin Example

        +
        +

        4.3. Multi-Story Shear Building - Coupled CFD-FEM Digital Twin

        --++ - +

        Problem files

        Github

        HydroUQ Github Repository
        -
        -

        Outline

        -

        This example uses a NHERI wave-flume digital twin, the OSU LWF, to simulate a scaled structure during wave loading in HydroUQ. Two-way coupled OpenFOAM-OpenSees is configured to simulate the scenario.

        -

        You will define a Waterborne Event (EVT) to determine the engineering demand parameters (EDP) on a specified structure, i.e. EVT –> EDP, with the following steps:

        +
        +

        4.3.1. Overview

        +

        This example uses a NHERI wave-flume digital twin, the OSU LWF, to simulate a scaled structure during wave loading in HydroUQ. Two-way coupled OpenFOAM-OpenSees is configured to simulate the scenario.

        +

        You will define a Waterborne Event (EVT) to determine the engineering demand parameters (EDP) on a specified structure, i.e. EVT –> EDP, with the following steps:

          -

        1. Configure a FOAMySees simulation. This is a two-way coupling of OpenFOAM Finite Volume Method (FVM) for Computational Fluid Dynamics (CFD) and OpenSees Finite Element Analaysis (FEA) for Computational Structural Dynamics (CSD).

          2. -

        2. Next, the coupled model will determine floor loads on the building, also known as intensity measures (IM) in performance based engineering (PBE).

          3. -

        3. Then, perform an OpenSees finite element analysis (FEA) simulation of the building by taking IMs as inputs.

          4. -

        4. Finally, recieve engineering demand parameters (EDP) of the structural response. Though beyond this example, you can use these EDPs to perform a fragility analysis of the structure.

          5. +

        5. Configure a FOAMySees simulation event (EVT). This is a two-way coupling of OpenFOAM Finite Volume Method (FVM) for Computational Fluid Dynamics (CFD) and OpenSees Finite Element Analaysis (FEA) for Computational Structural Dynamics (CSD).

          6. +

        6. Next, the coupled model will determine floor loads on the building, also known as intensity measures (IM) in common performance-based engineering (PBE) nomenclature.

          7. +

        7. Then, perform an OpenSees finite element analysis (FEM) simulation of the building by taking IMs as inputs.

          8. +

        8. Finally, recieve engineering demand parameters (EDP) of the structural response. Though beyond this example, you can use these EDPs to perform a fragility analysis of the structure.

        -
        -

        Data

        -

        The dataset used presented in this example originates from experimental tests conducted in the Hinsdale Wave Research Laboratory’s Large Wave Flume at Oregon State University (OSU LWF), Corvallis, in 2020. Refer to Lewis 2023 [Lewis2023] and Bonus 2023 [Bonus2023] for details.

        +
        +

        4.3.2. Set-Up

        +

        The dataset in this example originates from experimental tests conducted in the Hinsdale Wave Research Laboratory’s Large Wave Flume at Oregon State University (OSU LWF), Corvallis, in 2020. Refer to Lewis 2023 [Lewis2023] and Bonus 2023 [Bonus2023] for details.

        ../../../../../_images/Coupled.png -

        Coupled Digital Twin Illustration

        -
        +

        Fig. 4.3.2.1 Coupled Digital Twin Illustration

        -

        Model

        -

        This model is characterized by the parameters: -- Youngs modulus \(E_0\) for plastic behavior,

        -
        -
        -

        Files required

        -
        -

        Warning

        -

        Do NOT place the files in your root, downloads, or desktop folder as when the application runs it will copy the contents on the directories and subdirectories containing these files multiple times. If you are like us, your root, Downloads or Documents folders contain a lot of files.

        +

        4.3.2.1. Model

        +

        This model is characterized by the parameters:

        +
          +

        • Structural weight, \(w\), in kN as a random variable with a mean of 100 kN and a standard deviation of 10 kN.

          • +
        +

        ^ +.. warning:

        +
        **Do NOT** place the files in your ``root``, ``downloads``, or ``desktop`` folder. The running application will copy every unrelated file in the directories and subdirectories multiple times.
+
        -
        -

        UQ workflow

        -

        The inputs needed to run this example can be loaded into the HydroUQ user interface by selecting the Coupled Digital Twin example from the Examples menu.

        +
        +

        4.3.2.2. Workflow

        +

        The inputs needed to run this example can be loaded into the HydroUQ user interface by selecting the Coupled Digital Twin example from the Examples menu at the top of the application.

        The inputs can also be set up manually through the following steps:

          -

        1. Start the application and the UQ panel will be highlighted. In the UQ Method drop-down menu, select the Bayesian Calibration option. In the UQ Engine dropdown menu select UCSD-UQ option. In the Model dropdown, select the Hierarchical option. Enter the values in this panel as shown in the figure below. A brief explanation of the different user input fields can be found in the User Manual.

          2. +

        2. Start the application and select the UQ panel: +In the UQ Method drop-down menu, select the Bayesian Calibration option. In the UQ Engine dropdown menu select UCSD-UQ option. In the Model dropdown, select the Hierarchical option. Enter the values in this panel as shown in the figure below. A brief explanation of the different user input fields can be found in the User Manual.

        ../../../../../_images/UQ.png -

        Inputs in the UQ panel

        +

        Fig. 4.3.2.2.1 Inputs in the UQ panel

        -
          -

        1. Next in the FEM panel , select OpenSees and populate the Input Script field by choosing the path to the model file.

          2. +
            +

          1. Next in the FEM panel: +Select OpenSees and populate the Input Script field by choosing the path to the model file.

          -
            -

          1. Select the RV tab from the input panel. This panel should be pre-populated with the names of the variables that were defined in the model scripts. If not, press the Add button to create a new field to define the input random variable. Enter the same variable name, as required in the model script. For this example, choose the Normal probability distribution for all the random variables and enter the parameter values for each distribution as shown in the figures below:

            2. +
            +../../../../../_images/FEM.png +

            Fig. 4.3.2.2.2 Inputs in the FEM panel

            +
            +
              +

            1. Select the RV tab from the input panel: +This panel should be pre-populated with the names of the variables that were defined in the model scripts. If not, press the Add button to create a new field to define the input random variable. Enter the same variable name, as required in the model script. For this example, choose the Normal probability distribution for all the random variables and enter the parameter values for each distribution as shown in the figures below:

            ../../../../../_images/RV.png
            -
              -

            1. In the EDP panel create the output quantities corresponding to each of the experiments with a descriptive name, as shown in the figures below:

              2. +
                +

              1. In the EDP panel: +Create the output quantities corresponding to each of the experiments with a descriptive name, as shown in the figures below:

              -
                -

              1. Click on the Run button. This will create the necessary input files to perform a Bayesian calibration of the hierarchical model, run the analysis, and display the results when the analysis is completed. The results produced are sample values drawn from the distribution that represents the aleatory uncertainty in the estimated material parameters from each of the datasets.

                2. +
                  +

                1. Click on the Run button. +This will create the necessary input files to perform a Bayesian calibration of the hierarchical model, run the analysis, and display the results when the analysis is completed.

                  2. +

                2. The RES tab will open with the workflow results when the simulation completers. The results produced are sample values drawn from the distribution that represents the aleatory uncertainty in the estimated material parameters from each of the datasets.

                -

                The Summary tab shows the mean, standard deviation, and coefficient of variation of each of the seven parameters of the material model that were inferred in this example.

                -

                In the Data Values tab of the RES panel, a chart and a table with all the sample values are shown. By clicking on the data inside the columns of the chart with the left or right mouse button, different chart types are created and shown in the chart area on the left.

                -
        -
        -

        Files for restarting the analysis

        -

        In addition to the results displayed in the RES panel in HydroUQ, JSON files with the state of the chain at every step of the sampling algorithm are saved in a directory called sampling_results within the tmp.SimCenter directory inside the jobs directory specified in the HydroUQ Preferences menu. Any of these files can be used to resume the sampling, by copying the file to the directory containing the model files and specifying its name in the Restart File Name field in the UQ panel.

        +
        +

        The Summary tab shows the mean, standard deviation, and coefficient of variation of each of the seven parameters of the material model that were inferred in this example.

        +

        In the Data Values tab of the RES panel, a chart and a table with all the sample values are shown. By clicking on the data inside the columns of the chart with the left or right mouse button (M1 and M2), different chart types are created and shown in the chart area on the left.

        +

        Warning

        -

        The tmp.SimCenter directory is cleared every time the RUN button is clicked in HydroUQ. So, if you want to restart the analysis using one of the sampling results files outlined above, make sure to copy the results file to a location outside the tmp.SimCenter directory at the end of the analysis.

        +

        The tmp.SimCenter directory is cleared every time the RUN button is clicked in HydroUQ. So, if you want to restart the analysis using one of the sampling results files outlined above, make sure to copy the results file to a location outside the tmp.SimCenter directory at the end of the analysis.

        +
        +
        +
        +

        4.3.3. References

        Lewis2023

        Lewis, N. (2023). Development of An Open-Source Methodology for Simulation of Civil Engineering Structures Subject to Multi-Hazards. PhD thesis, University of Washington, Seattle, WA. ISBN: 979-8-381408-69-0.

        @@ -313,7 +345,7 @@

        UQ workflow

        - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

        diff --git a/docs/common/user_manual/examples/desktop/hdro-0002/README.html b/docs/common/user_manual/examples/desktop/hdro-0002/README.html index 03b07bd3..e02c9fbc 100644 --- a/docs/common/user_manual/examples/desktop/hdro-0002/README.html +++ b/docs/common/user_manual/examples/desktop/hdro-0002/README.html @@ -7,7 +7,7 @@ - 4.1. Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF) — Hydro-UQ documentation + 4.4. Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF) — Hydro-UQ documentation @@ -16,7 +16,7 @@ - + @@ -49,8 +49,8 @@ - - + + @@ -125,15 +125,19 @@
      • 2. User Interface
      • 3. Tools
      • 4. Examples
          -
        • 4.1. Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF)
        • 5. Best Practices
          • @@ -207,7 +211,7 @@
        • 4. Examples »
          • -
        • 4.1. Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF)
          • +
        • 4.4. Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF)
        • @@ -227,7 +231,7 @@
          -

          4.1. Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF)

          +

          4.4. Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF)

          @@ -250,193 +254,193 @@
          -

          4.1.1. Overview

          +

          4.4.1. Overview

          In this digital twin validation example, debris-field wave-flume tests at a NHERI facility, Oregon State University’s Large Wave Flume (OSU LWF), are briefly summarized before demonstrating the use of HydroUQ’s OSU LWF digital twin paired with the Material Point Method (MPM).

          ../../../../../_images/HydroUQ_MPM_3DViewPort_OSULWF_2024.04.251.gif -

          Fig. 4.1.1.1 HydroUQ’s desktop GUI for the NHERI OSU LWF digital wave-flume twin.

          +

          Fig. 4.4.1.1 HydroUQ’s desktop GUI for the NHERI OSU LWF digital wave-flume twin.

          -

          Details for the experiments are available in various publications. Namely, the work of Andrew Winter [Winter2020] [Winter2019], Krishnendu Shekhar [Shekhar2020] and Dakota Mascarenas [Mascarenas2022] [Mascarenas2022PORTS]. The simulations replicated in this example appeared originally in Bonus 2023 [Bonus2023Dissertation].

          +

          Details for the experiments are available in various publications. Namely, the work of Andrew Winter [Winter2020] [Winter2019], Krishnendu Shekhar [Shekhar2020] and Dakota Mascarenas [Mascarenas2022] [Mascarenas2022PORTS]. The simulations replicated in this example appeared originally in Bonus 2023 [Bonus2023Dissertation].

          Experiments were performed in the NHERI OSU LWF, a 100 meter long flume with adjustable bathymetry, in order to quantify stochastic impact loads of ordered and disordered debris-fields on effectively rigid, raised structure.

          ../../../../../_images/OSU_Flume_Schematic_Dakota_Alam.png -

          Fig. 4.1.1.2 NHERI OSU LWF facilty’s experimental schematic used in this example. Adapted from Winter 2019 [Winter2019], and Mascarenas 2022 [Mascarenas2022].

          +

          Fig. 4.4.1.2 NHERI OSU LWF facility’s experimental schematic is used in this example. Adapted from Winter 2019 [Winter2019], and Mascarenas 2022 [Mascarenas2022].

          -

          This example may help to produce a robust database (numerical and physical) from which to eventually be able to extract both the first-principals of wave-driven debris-field phenomena and design guidelines on induced forces.

          -

          We validate against two very similar (but not identical) physical studies done in the OSU LWF by [Shekhar2020] and [Mascarenas2022], indicating high accuracy of our model and low bias to minor experiment specifications.

          +

          This example may help to produce a robust database (numerical and physical) from which to eventually be able to extract both the first principles of wave-driven debris-field phenomena and design guidelines on induced forces.

          +

          We validate against two very similar (but not identical) physical studies done in the OSU LWF by [Shekhar2020] and [Mascarenas2022], indicating high accuracy of our model and low bias to minor experiment specifications.

          Results for free surface elevation and streamwise structural loads are to be recorded for validation at a specified interval.

          Qualitatively, an MPM simulation of debris impacts on a raised structure in the OSU LWF is shown below.

          ../../../../../_images/OSU_LWF_MPM_32L_Impact_3Photos.png -

          Fig. 4.1.1.3 OSU LWF debris impact photos from HydroUQ’s MPM simulations.

          +

          Fig. 4.4.1.3 OSU LWF debris impact photos from HydroUQ’s MPM simulations.

          -

          It appears similar in the mechanism of debris impact, stalling, and deflection relative to the structure and flow for a similar case in Mascarenas 2022 [Mascarenas2022].

          +

          It appears similar in the mechanism of debris impact, stalling, and deflection relative to the structure and flow for a similar case in Mascarenas 2022 [Mascarenas2022].

          ../../../../../_images/OSU_LWF_Dakota_8L_Impact_3Photos.PNG -

          Fig. 4.1.1.4 OSU LWF debris impact photos from Mascarenas 2022 [Mascarenas2022] experiments.

          +

          Fig. 4.4.1.4 OSU LWF debris impact photos from Mascarenas 2022 [Mascarenas2022] experiments.

          -

          The experiments by Shekhar et al. 2020 [Shekhar2020] are also shown below for comparison. These tests had a slightly different configuartion, primarily the debris were located 0.5 meters further upstream from the box and the water level was 0.10-0.15 meters lower than the 2.0 meter datum used in the simulations and Mascarenas 2022 [Mascarenas2022] experiments.

          +

          The experiments by Shekhar et al. 2020 [Shekhar2020] are also shown below for comparison. These tests had a slightly different configuration, primarily the debris were located 0.5 meters further upstream from the box and the water level was 0.10-0.15 meters lower than the 2.0 meter datum used in the simulations and Mascarenas 2022 [Mascarenas2022] experiments.

          ../../../../../_images/OSU_LWF_Krish_Debris_8L_3Panel_Impacts_Photograph_Shekhar2020.PNG -

          Fig. 4.1.1.5 OSU LWF debris impact photos from Shekhar et al. 2020 [Shekhar2020] experiments.

          +

          Fig. 4.4.1.5 OSU LWF debris impact photos from Shekhar et al. 2020 [Shekhar2020] experiments.

          Similar figures can be made for the whole range of order debris-array experiments done at the OSU LWF. However, this example focuses on teaching you how to replicate the above results.

          -

          4.1.2. Set-Up

          -

          A step-by-step walkthrough on replicating an MPM simulation result from Bonus 2023 [Bonus2023Dissertation] is provided below.

          +

          4.4.2. Set-Up

          +

          A step-by-step walkthrough on replicating an MPM simulation result from Bonus 2023 [Bonus2023Dissertation] is provided below.

          Open Settings. Here we set the simulation time, the time step, and the number of processors to use, among other pre-simulation decisions.

          ../../../../../_images/GUI_Settings.PNG -

          Fig. 4.1.2.1 HydroUQ Settings GUI

          +

          Fig. 4.4.2.1 HydroUQ Settings GUI

          Open Bodies / Fluid / Material. Here we set the material properties of the fluid and the debris.

          ../../../../../_images/GUI_Bodies_Fluid_Material.PNG -

          Fig. 4.1.2.2 HydroUQ Bodies Fluid Material GUI

          +

          Fig. 4.4.2.2 HydroUQ Bodies Fluid Material GUI

          Open Bodies / Fluid / Geometry. Here we set the geometry of the flume, the debris, and the raised structure.

          ../../../../../_images/GUI_Bodies_Fluid_Geometry.PNG -

          Fig. 4.1.2.3 HydroUQ Bodies Fluid Geometry GUI

          +

          Fig. 4.4.2.3 HydroUQ Bodies Fluid Geometry GUI

          Open Algorithm. Here we set the algorithm parameters for the simulation. We choose to apply F-Bar antilocking to aid in the pressure field’s accuracy on the fluid. The associated toggle must be checked, and the antilocking ratio set to 0.9, loosely.

          ../../../../../_images/GUI_Bodies_Fluid_Algorithm.PNG -

          Fig. 4.1.2.4 HydroUQ Bodies Fluid Algorithm GUI

          +

          Fig. 4.4.2.4 HydroUQ Bodies Fluid Algorithm GUI

          -

          Open Bodies / Fluid / Partitions. Here we set the number of partitions for the simulation. This is the domain decomposition across discrete hardware units, i.e. Multi-GPUs. These may be kept as there default values.

          +

          Open Bodies / Fluid / Partitions. Here we set the number of partitions for the simulation. This is the domain decomposition across discrete hardware units, i.e. Multi-GPUs. These may be kept as their default values.

          ../../../../../_images/GUI_Bodies_Fluid_Partitions.PNG -

          Fig. 4.1.2.5 HydroUQ Bodies Fluid Partitions GUI

          +

          Fig. 4.4.2.5 HydroUQ Bodies Fluid Partitions GUI

          -

          Moving onto the creation of an ordered debris-array, we set the debris properties in the Bodies / Debris / Material tab. We will assume debris are made of HDPE plastic, as in experiments by Mascarenas 2022 [Mascarenas2022] and Shekhar et al. 2020 [Shekhar2020].

          +

          Moving onto the creation of an ordered debris array, we set the debris properties in the Bodies / Debris / Material tab. We will assume debris are made of HDPE plastic, as in experiments by Mascarenas 2022 [Mascarenas2022] and Shekhar et al. 2020 [Shekhar2020].

          ../../../../../_images/GUI_Bodies_Debris_Material.PNG -

          Fig. 4.1.2.6 HydroUQ Bodies Debris Material GUI

          +

          Fig. 4.4.2.6 HydroUQ Bodies Debris Material GUI

          Open Bodies / Debris / Geometry. Here we set the debris properties, such as the number of debris, the size of the debris, and the spacing between the debris. Rotation is another option, though not used in this example. We’ve elected to use an 8 x 4 grid of debris (longitudinal axis parallel to long-axis of the flume).

          ../../../../../_images/GUI_Bodies_Debris_Geometry.PNG -

          Fig. 4.1.2.7 HydroUQ Bodies Debris Geometry GUI

          +

          Fig. 4.4.2.7 HydroUQ Bodies Debris Geometry GUI

          -

          The Bodies / Debris / Algorithm and Debris / Partitions tabs are not used in this example, but are available for more advanced users.

          +

          The Bodies / Debris / Algorithm and Debris / Partitions tabs are not used in this example but are available for more advanced users.

          Open Bodies / Structures. Uncheck the box that enables this body, if it is checked. We will not model the structure as a body in this example, instead, we will modify it as a boundary later.

          ../../../../../_images/GUI_Bodies_Structure_Disabled.PNG -

          Fig. 4.1.2.8 HydroUQ Bodies Structures GUI

          +

          Fig. 4.4.2.8 HydroUQ Bodies Structures GUI

          -

          Open Boundaries / Wave Flume. We will set the boundary to be a rigid body, with a fixed separable velocity condition, that is faithful to the digital tiwn of the NHERI OSU LWF. Bathmyetry joint points should be indetical to the ones used in Bodeis / FLuid.

          +

          Open Boundaries / Wave Flume. We will set the boundary to be a rigid body, with a fixed separable velocity condition, that is faithful to the digital twin of the NHERI OSU LWF. Bathmyetry joint points should be identical to the ones used in Bodeis / FLuid.

          ../../../../../_images/GUI_Boundaries_Flume.PNG -

          Fig. 4.1.2.9 HydroUQ Boundaries Wave Flume Facility GUI

          +

          Fig. 4.4.2.9 HydroUQ Boundaries Wave Flume Facility GUI

          -

          Open Boundaries / Wave Generator. Fill in the appropriate file-path for the wave generator paddle motion. It is designed to produce near-solitary like waves.

          +

          Open Boundaries / Wave Generator. Fill in the appropriate file-path for the wave generator paddle motion. It is designed to produce near-solitary-like waves.

          ../../../../../_images/GUI_Boundaries_WaveGenerator.PNG -

          Fig. 4.1.2.10 HydroUQ Boundaries Wave Generator GUI

          +

          Fig. 4.4.2.10 HydroUQ Boundaries Wave Generator GUI

          -

          Open Boundaries / Rigid Structure. This is where we will specify the raised structure as a boundary condition. By doing so, we can determine exact loads on the rigid boundary grid-nodes, which may then be mapped to the FEM tab for nonlinear UQ structural response analysis.

          +

          Open Boundaries / Rigid Structure. This is where we will specify the raised structure as a boundary condition. By doing so, we can determine the exact loads on the rigid boundary grid-nodes, which may then be mapped to the FEM tab for nonlinear UQ structural response analysis.

          ../../../../../_images/GUI_Boundaries_RigidStructure.PNG -

          Fig. 4.1.2.11 HydroUQ Boundaries Rigid Structure GUI

          +

          Fig. 4.4.2.11 HydroUQ Boundaries Rigid Structure GUI

          Open Boundaries / RigidWalls.

          ../../../../../_images/GUI_Boundaries_RigidWalls.PNG -

          Fig. 4.1.2.12 HydroUQ Boundaries Wave-Flume Facility GUI

          +

          Fig. 4.4.2.12 HydroUQ Boundaries Wave-Flume Facility GUI

          Open Sensors / Wave Gauges. Set the Use these sensor? box to True so that the simulation will output results for the instruments we set on this page.

          -

          Three wave gauges will be defined. The first is located prior to the bathymetry ramps, the second partially up the ramps, and the third near the the bathymetry crest, debris, and raised structure.

          +

          Three wave gauges will be defined. The first is located prior to the bathymetry ramps, the second partially up the ramps, and the third near the bathymetry crest, debris, and raised structure.

          Set the origins and dimensions of each wave as in the table below. To match experimental conditions, we also apply a 120 Hz sampling rate to the wave gauges, meaning they record data every 0.0083 seconds.

          ../../../../../_images/GUI_Sensors_WaveGauges.PNG -

          Fig. 4.1.2.13 HydroUQ Sensors Wave-Gauge GUI

          +

          Fig. 4.4.2.13 HydroUQ Sensors Wave-Gauge GUI

          -

          These wave gauges will read all numerical bodies (i.e. particles) within their defined regions every sampling step, and will report the highest elevation value (Position Y) of a contained body as the free-surface elevation at that gauge. The results is written into our sensor results files.

          +

          These wave gauges will read all numerical bodies (i.e. particles) within their defined regions at every sampling step and will report the highest elevation value (Position Y) of a contained body as the free-surface elevation at that gauge. The results are written into our sensor results files.

          Open Sensors / Load Cells. Set the Use these sensor? box to True so that the simulation will output results for the instruments we set on this page.

          ../../../../../_images/GUI_Sensors_LoadCells.PNG -

          Fig. 4.1.2.14 HydroUQ Sensors Load-Cells GUI

          +

          Fig. 4.4.2.14 HydroUQ Sensors Load-Cells GUI

          -

          Open Outputs. Here we set the non-physical output parameters for the simulation, e.g. attributes to save per frame and file extension types. The particle bodies’ output frequency is set to 10 Hz (0.1 seconds), meaning the simulation will output results every 0.1 seconds. This is decent for animations without taking too much space. Fill in the rest of the data in the figure into your GUI to ensure all your outputs match this example.

          +

          Open Outputs. Here we set the non-physical output parameters for the simulation, e.g. attributes to save per frame and file extension types. The particle bodies’ output frequency is set to 10 Hz (0.1 seconds), meaning the simulation will output results every 0.1 seconds. This is decent for animations without taking up too much space. Fill in the rest of the data in the figure into your GUI to ensure all your outputs match this example.

          ../../../../../_images/GUI_Outputs.PNG -

          Fig. 4.1.2.15 HydroUQ Outputs GUI

          +

          Fig. 4.4.2.15 HydroUQ Outputs GUI

          -

          4.1.3. Simulation

          -

          We assume that 2 hours are reserved for your simulation. For those using the reduce fluid bulk modulus or reduced resolution, this may be more than neccesary.

          -

          This simulation was ran on the TACC Lonestar6 system. It uesd three NVIDIA A100 GPUs on a single node in the gpu-a100 queue. Real time to complete was 2 hours. Simulated time in the digital twin is 26 seconds.

          -

          In order to retrieve results from the analysis, the analysis must complete and postprocess the model output files into an appropriate format before the end of the allotted submission time.

          +

          4.4.3. Simulation

          +

          We assume that 2 hours are reserved for your simulation. For those using the reduce fluid bulk modulus or reduced resolution, this may be more than necessary.

          +

          This simulation was run on the TACC Lonestar6 system. It uses three NVIDIA A100 GPUs on a single node in the gpu-a100 queue. The real-time to complete was 2 hours. The simulated time in the digital twin is 26 seconds.

          +

          To retrieve results from the analysis, the analysis must complete and post-process the model output files into an appropriate format before the end of the allotted submission time.

          Important

          Provide a large amount of time for the Max Run Time field in HydroUQ when submitting a job to ensure the model completes before the time allotted runs out! We recommend 2 hours in this example.

          Warning

          -

          Only ask for what you need in terms of sensor size, count, and output sampling rate. Otherwise you will end up with massive amounts of data which can slow simulations due to I/O constraints.

          +

          Only ask for what you need in terms of sensor size, count, and output sampling rate. Otherwise, you will end up with massive amounts of data which can slow simulations due to I/O constraints.

          -

          4.1.4. Analysis

          -

          When the simulation job has completed, the results will be available on the remote system for retrieval or remote post-processing.

          +

          4.4.4. Analysis

          +

          When the simulation job has been completed, the results will be available on the remote system for retrieval or remote post-processing.

          Retrieving the results.zip folder from the Tools & Applications Page of Design Safe starts by navigating to the designsafe-ci.org website. Login and go to Use DesignSafe / Tools & Applications

          ../../../../../_images/DSToolsAndAppsJobsStatus.PNG -

          Fig. 4.1.4.1 Locating the job files on DesignSafe

          +

          Fig. 4.4.4.1 Locating the job files on DesignSafe

          Check if the job has finished in the right-side vertical drawer by clicking the refresh icon. If it has, click More info.

          ../../../../../_images/DSToolsAndAppsJobsStatusFinished.PNG -

          Fig. 4.1.4.2 Job status is finished on DesignSafe

          +

          Fig. 4.4.4.2 Job status is finished on DesignSafe

          Once the job is finished, the output files should be available in the directory which the analysis results were sent to

          Find the files by clicking View.

          ../../../../../_images/DSToolsAndAppsJobsStatusViewFiles.PNG -

          Fig. 4.1.4.3 Viewing the job files on DesignSafe

          +

          Fig. 4.4.4.3 Viewing the job files on DesignSafe

          Move the results.zip to somewhere in My Data/. Use the Extractor tool available on DesignSafe. Unzip the results.zip folder.

          ../../../../../_images/extractonDS.PNG -

          Fig. 4.1.4.4 Extracting the results.zip folder on DesignSafe

          +

          Fig. 4.4.4.4 Extracting the results.zip folder on DesignSafe

          OR Download the results.zip folder to your PC and unzip to look at the model results.

          ../../../../../_images/downloadResults.PNG -

          Fig. 4.1.4.5 Download button on DesignSafe shown in red

          +

          Fig. 4.4.4.5 Download button on DesignSafe shown in red

          Download the results to look at the geometry files of the analysis.

          Extract the results.zip folder either on DesignSafe or on your local machine. You will likely want to have a free Side FX Houdini Apprentice installation to view BGEO files.

          ../../../../../_images/resultsZip.png -

          Fig. 4.1.4.6 File-system view of results zip folder on DesignSafe.

          +

          Fig. 4.4.4.6 File-system view of results zip folder on DesignSafe.

          -

          Locate the zip folder and extract it somewhere convenient. The local or remote work directory on your computer is a good option, but note that these files may be erased if another simulation is set-up in HydroUQ, so keep a backup somewhere outside the working directories.

          -

          HydroUQ’s sensor / probe / instrument output is available in {your_path_to_HydroUQ_WorkDir}/HydroUQ/RemoteWorkDir/results/ as CSV files.

          +

          Locate the zip folder and extract it somewhere convenient. The local or remote work directory on your computer is a good option, but note that these files may be erased if another simulation is set up in HydroUQ, so keep a backup somewhere outside the working directories.

          +

          HydroUQ’s sensor/probe/instrument output is available in {your_path_to_HydroUQ_WorkDir}/HydroUQ/RemoteWorkDir/results/ as CSV files.

          Particle geometry files often have a BGEO extension, open Side FX Houdini Apprentice (free to use) to look at MPM results in high-detail.

          -

          Once complete, the simulation data at the three wave gauges (WG1, WG2, and WG3, left-to-right) is as showm below when plotted against experimental trials of Mascarenas 2022 [Mascarenas2022] for the “unbroken” solitary wave case.

          +

          Once complete, the simulation data at the three wave gauges (WG1, WG2, and WG3, left-to-right) is as shown below when plotted against experimental trials of Mascarenas 2022 [Mascarenas2022] for the “unbroken” solitary wave case.

          ../../../../../_images/OSU_LWF_Wave_Gauges_Hydro_2D_Plots3_2023.10.31.png -

          Fig. 4.1.4.7 OSU LWF simulated free-surface elevation wave gauges vs. experimental data from Mascarenas 2022 [Mascarenas2022].

          +

          Fig. 4.4.4.7 OSU LWF simulated free-surface elevation wave gauges vs. experimental data from Mascarenas 2022 [Mascarenas2022].

          -

          The simulation data at the load-cell is as shown below when plotted against experimental trials of Mascarenas 2022 [Mascarenas2022] for the “unbroken” solitary wave case. The experimental streamwise load is the combination of “LC5” and “LC8” in Mascarenas 2022 [Mascarenas2022], as both measured streamwise load on the box to reduce errors from position / slight box apparatus out-of-plane rotation.

          +

          The simulation data at the load-cell is as shown below when plotted against experimental trials of Mascarenas 2022 [Mascarenas2022] for the “unbroken” solitary wave case. The experimental streamwise load is the combination of “LC5” and “LC8” in Mascarenas 2022 [Mascarenas2022], as both measured streamwise load on the box to reduce errors from position / slight box apparatus out-of-plane rotation.

          ../../../../../_images/OSU_LWF_Load_Cells_Hydro_2023.10.31.png -

          Fig. 4.1.4.8 OSU LWF simulated streamwise load-cells vs. experimental data from Mascarenas 2022 [Mascarenas2022].

          +

          Fig. 4.4.4.8 OSU LWF simulated streamwise load-cells vs. experimental data from Mascarenas 2022 [Mascarenas2022].

          -

          Though only one case was considered here, if many experimental debris-field cases are ran (10+) we can use HydroUQ to perform a sensitivity analysis on the debris-field parameters. This isn’t pursued here-in.

          -

          However, the following box-and-whisker charts demonstrates the strengh of the numerical replication, as most points fall within experimental interquartile ranges and never outside of the experimental envelope for impact loads.

          +

          Though only one case was considered here, if many experimental debris-field cases are run (10+) we can use HydroUQ to perform a sensitivity analysis on the debris-field parameters. This isn’t pursued here-in.

          +

          However, the following box-and-whisker charts demonstrate the strength of the numerical replication, as most points fall within experimental interquartile ranges and never outside of the experimental envelope for impact loads.

          ../../../../../_images/OSU_U_FirstPeak_BoxAndWhiskers_KrishExpOnly_31072023.png -

          Fig. 4.1.4.9 OSU LWF simulated first peak debris impact loads vs. experimental data from Mascarenas 2022 [Mascarenas2022].

          +

          Fig. 4.4.4.9 OSU LWF simulated first peak debris impact loads vs. experimental data from Mascarenas 2022 [Mascarenas2022].

          -

          This complete our HydroUQ validation example for multiple debris impacts on a raised structure in the OSU LWF, Bonus 2023 [Bonus2023Dissertation].

          +

          This complete our HydroUQ validation example for multiple debris impacts on a raised structure in the OSU LWF, Bonus 2023 [Bonus2023Dissertation].

          -

          4.1.5. References

          +

          4.4.5. References

          Winter2019(1,2)

          Winter, A. (2019). “Effects of Flow Shielding and Channeling on Tsunami-Induced Loading of Coastal Structures.” PhD thesis. University of Washington, Seattle.

          @@ -470,7 +474,7 @@

          - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

          diff --git a/docs/common/user_manual/examples/desktop/hdro-0003/README.html b/docs/common/user_manual/examples/desktop/hdro-0003/README.html index 0fc761da..00c0a543 100644 --- a/docs/common/user_manual/examples/desktop/hdro-0003/README.html +++ b/docs/common/user_manual/examples/desktop/hdro-0003/README.html @@ -7,7 +7,7 @@ - 4.2. Cylinder Half-Submerged in Flow - UW WASIRF Twin - FOAMySees (OpenFOAM + OpenSees) — Hydro-UQ documentation + 4.5. Cylinder Half-Submerged in Flow - UW WASIRF Twin - FOAMySees (OpenFOAM + OpenSees) — Hydro-UQ documentation @@ -16,7 +16,7 @@ - + @@ -49,8 +49,8 @@ - - + + @@ -125,16 +125,20 @@
        • 2. User Interface
        • 3. Tools
        • 4. Examples
          • @@ -252,11 +256,11 @@
          -

          4.2.1. Overview

          -

          This example demonstrates how to run a coupled OpenSees-OpenFOAM simulation (FOAMySees) to determine floor loads on a building caused by strongly-coupled, two-way fluid-structure interaction. +

          4.5.1. Overview

          +

          This example demonstrates how to run a coupled OpenSees-OpenFOAM simulation (FOAMySees) to determine floor loads on a building caused by strongly coupled, two-way fluid-structure interaction. You can then perform an OpenSees simulation of the building assuming uncertainties in the building properties.

          A truncated digital twin of the UW WASIRF wave flume contains a simple cantilevered cylinder. The cylinder, our structure, is half-submerged. The flow around the cylinder is calculated for a given period of time in order to determine a simulated structural response time-series under wave loading.

          -

          Outputs of the EVT simulation will include results, sampled at specified frequenies, for the:

          +

          Outputs of the EVT simulation will include results, sampled at specified frequencies, for the:

          1. Fluid flow’s free surface elevation at wave gauges

          2. Flow velocity at velocimeter locations

            3. @@ -271,12 +275,12 @@

            The EDP tab will then process these results.

            1. Displacement of the cylinder tip from rest, peak relative-floor displacement (PFD)

              2. -

            2. Displacement of the cylinder tip relative to its base or supporting , peak inter-story drift (PID)

              3. +

            3. Displacement of the cylinder tip relative to its base or supporting, peak inter-story drift (PID)

            4. Peak floor acceleration (PFA)

          -

          4.2.2. Set-Up

          +

          4.5.2. Set-Up

          The case is set up in the HydroUQ tool on DesignSafe. You can select the case from the list of available examples off of the HydroUQ menubar, i.e. Examples / hdro-0003. The case is set up as follows.

          The flume is 1 meter wide (from Y=-0.5m to Y=0.5 m), 1 meter tall (Z=0.0m to Z=1.0m), and 4 meters long (X=0.0m to X=4.0m). The cardinal direction Z+ is vertical, X+ is downstream, and Y+ is crossflow. Gravity is -9.81 m / s^2 in the Z direction.

          The case is initialized with a still water level of 0.25 meters. The velocity at the inlet is given a time history boundary condition, src/VelTime.csv.

          @@ -286,57 +290,57 @@

          The interface surface file is 'src/interface.stl'.

          ../../../../../_images/hdro-0003example.png -

          Fig. 4.2.2.1 Schematic of the digital twin example in the UW WASIRF truncated flume

          +

          Fig. 4.5.2.1 Schematic of the digital twin example in the UW WASIRF truncated flume

          Probe positions in the digital flume are set at the following locations:

          ../../../../../_images/hdro-0003exampleprobeLoc.png -

          Fig. 4.2.2.2 Instrumentation locations in theUW WASIRF truncated digital flume

          +

          Fig. 4.5.2.2 Instrumentation locations in theUW WASIRF truncated digital flume

          Inlet Velocity Time History (U(t)) for the truncated digital twin is given by the following function in OpenFOAM:

          ../../../../../_images/inletVTH.png -

          Fig. 4.2.2.3 Inlet Velocity Time History for the UW WASIRF digital twin

          +

          Fig. 4.5.2.3 Inlet Velocity Time History for the UW WASIRF digital twin

          We now have a coupled simulation configured for fluid flow around, and the structural response of, a cylinder. Next, we will run the simulation on a remote TACC high-performance computing system.

          -

          4.2.3. Simulation

          +

          4.5.3. Simulation

          Login to DesignSafe and submit the job to run remotely on a TACC system, either Frontera or Stampede3.

          Simulation time for 1 second in the digital flume took 1 hour and 20 minutes. This was using one computational node on TACC Frontera, possessing 56 cores.

          The case can be run for as long as desired, but mind that the longer the case runs, the longer the postprocessing routines will be.

          -

          In order to retrieve results from the analysis, the job must complete and postprocess the model output files into a VTK format before the end of the allotted submission time.

          +

          In order to retrieve results from the analysis, the job must complete and post-process the model output files into a VTK format before the end of the allotted submission time.

          Important

          Provide a large amount of time for the Max Run Time field in HydroUQ when submitting a job to ensure the model completes before the time allotted runs out!

          Note

          -

          Be aware that the smaller the OpenFOAM Outputs and OpenSees Outputs Time Interval value is, the longer the post processing of the case will take after analysis has completed, +

          Be aware that the smaller the OpenFOAM Outputs and OpenSees Outputs Time Interval value is, the longer the post-processing of the case will take after analysis has been completed, and the larger the results.zip folder will be.

          Warning

          Be modest when requesting simulation outputs across many recording probes or full geometry snapshots. -Only ask for what you need, or your simulation will become slow due to I/O constraints and the output data will be too large to effecitvely post-process or host on your local machine.

          +Only ask for what you need, or your simulation will become slow due to I/O constraints and the output data will be too large to effectively post-process or host on your local machine.

          -

          4.2.4. Results

          +

          4.5.4. Results

          First, we must retrieve the results.zip folder from the DesignSafe file storage. This zip file will contain all our from the Tools and Applications Page of Design Safe

          ../../../../../_images/DSToolsAndAppsJobsStatus1.PNG -

          Fig. 4.2.4.1 Locating the job files on DesignSafe

          +

          Fig. 4.5.4.1 Locating the job files on DesignSafe

          Check if the job has finished. If it has, click ‘More info’.

          ../../../../../_images/DSToolsAndAppsJobsStatusFinished1.PNG -

          Fig. 4.2.4.2 Once the job is finished, the output files should be available in the directory which the analysis results were sent to

          +

          Fig. 4.5.4.2 Once the job is finished, the output files should be available in the directory to which the analysis results were sent to

          Find the files by clicking ‘View’.

          ../../../../../_images/DSToolsAndAppsJobsStatusViewFiles1.PNG -

          Fig. 4.2.4.3 Directory shown on DesignSafe contains the results.zip output for a HydroUQ EVT simulation. Download the results.zip folder to your local machine to view the model results.

          +

          Fig. 4.5.4.3 Directory shown on DesignSafe contains the results.zip output for a HydroUQ EVT simulation. Download the results.zip folder to your local machine to view the model results.

          Move the results.zip to somewhere in My Data/. Use the Extractor tool available on DesignSafe. Unzip the results.zip folder.

          @@ -345,35 +349,35 @@

          OR Download the results.zip folder to your PC and unzip to look at the model results.

          ../../../../../_images/downloadResults1.PNG -

          Fig. 4.2.4.4 Download the results to look at the VTK files of the analysis. This will include OpenFOAM and OpenSees field data and model geometry

          +

          Fig. 4.5.4.4 Download the results to look at the VTK files of the analysis. This will include OpenFOAM and OpenSees field data and model geometry

          Extract the Zip folder either on DesignSafe or on your local machine. You will need Paraview to view the model data.

          ../../../../../_images/resultsZip1.png -

          Fig. 4.2.4.5 Locate the zip folder and extract it to somewhere convenient

          +

          Fig. 4.5.4.5 Locate the zip folder and extract it to somewhere convenient

          The results folder should look something like this.

          ../../../../../_images/results.png -

          Fig. 4.2.4.6 This is the output of the model

          +

          Fig. 4.5.4.6 This is the output of the model

          -

          4.2.5. Analysis

          +

          4.5.5. Analysis

          Paraview files have a .PVD extension. Open VTK/Fluid.vtm.series to look at OpenFOAM results. Open OpenSeesOutput.pvd to look at OpenSees results.

          ../../../../../_images/Paraview.PNG -

          Fig. 4.2.5.1 This is the model output data as seen from ParaView

          +

          Fig. 4.5.5.1 This is the model output data as seen from ParaView

          OpenSees Displacements And Reactions

          ../../../../../_images/TipDisplacement.png -

          Fig. 4.2.5.2 This is the model output data as seen from ParaView

          +

          Fig. 4.5.5.2 This is the model output data as seen from ParaView

          ../../../../../_images/ReactionForces.png -

          Fig. 4.2.5.3 This is the model output data as seen from ParaView

          +

          Fig. 4.5.5.3 This is the model output data as seen from ParaView

          OpenFOAM probe and function object output is available in results/postProcessing/. OpenFOAM output is currently unorganized. An example Matlab script is provided in the src/ directory to post process the OpenFOAM output for this particular case and output. This file can be modified to work for any case. The names of the data folders will need to be changed according to the name of the probe given in HydroUQ.

          @@ -383,33 +387,33 @@

          OpenFOAM Calculated Story Forces are

          ../../../../../_images/storyForces.png -

          Fig. 4.2.5.4 Story Forces in OpenFOAM

          +

          Fig. 4.5.5.4 Story Forces in OpenFOAM

          OpenFOAM Calculated Coupled Interface Forces are visualized in the following figure

          ../../../../../_images/Forces.png -

          Fig. 4.2.5.5 Coupled Interface Forces in OpenFOAM-OpenSees

          +

          Fig. 4.5.5.5 Coupled Interface Forces in OpenFOAM-OpenSees

          OpenFOAM calculated, coupled interface moments at the structural surface are

          ../../../../../_images/Moments.png -

          Fig. 4.2.5.6 Coupled Interface Moments in OpenFOAM-OpenSees

          +

          Fig. 4.5.5.6 Coupled Interface Moments in OpenFOAM-OpenSees

          OpenFOAM calculated pressure probe values throughout the flume are

          OpenFOAM calculated fluid velocity probe values throughout the flume are

          ../../../../../_images/Velocities.png -

          Fig. 4.2.5.7 Velocity Probe Values in OpenFOAM

          +

          Fig. 4.5.5.7 Velocity Probe Values in OpenFOAM

          OpenFOAM calculated wave gauge free-surface values at key locations in the facility are

          ../../../../../_images/WaveGauges.png -

          Fig. 4.2.5.8 Wave Gauge Free-Surface Probe Values in OpenFOAM

          +

          Fig. 4.5.5.8 Wave Gauge Free-Surface Probe Values in OpenFOAM

          This completes the analysis of the model. In validation of any flume experimental case, a similar process may be employed with an added step of comparison to experimental data.

          -

          4.2.6. References

          +

          4.5.6. References

          Lewis2023

          Lewis, N. (2023). Development of An Open-Source Methodology for Simulation of Civil Engineering Structures Subject to Multi-Hazards. PhD thesis, University of Washington, Seattle, WA. ISBN: 979-8-381408-69-0.

          @@ -449,7 +453,7 @@

          - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

          diff --git a/docs/common/user_manual/examples/desktop/hdro-0004/README.html b/docs/common/user_manual/examples/desktop/hdro-0004/README.html index 4cfb401f..112f3da7 100644 --- a/docs/common/user_manual/examples/desktop/hdro-0004/README.html +++ b/docs/common/user_manual/examples/desktop/hdro-0004/README.html @@ -7,7 +7,7 @@ - Tsunami Debris Motion Through a Scaled Port Setting - WU TWB Digital Twin - MPM — Hydro-UQ documentation + 4.6. Tsunami Debris Motion Through a Scaled Port Setting - WU TWB Digital Twin - MPM — Hydro-UQ documentation @@ -16,7 +16,7 @@ - + @@ -49,6 +49,8 @@ + + @@ -118,11 +120,25 @@
        • 9. Abbreviations

          • User Manual

          -
          @@ -224,117 +242,81 @@
          +
          +

          Table of Contents

          + +
          -

          Outline

          -

          Example to demonstrate how to run a MPM simulation to determine floor loads on a building and then perform -an OpenSees simulation of the building assuming uncertainties in the building properties.

          -

          The flume is 1 meter wide (from Y=-0.5m to Y=0.5 m), 1 meter tall (Z=0.0m to Z=1.0m), and 4 meters long (X=0.0m to X=4.0m).

          -

          The case is initialized with a still water level of 0.25 meters. The velocity at the inlet is given a time history boundary condition (src/VelTime.csv).

          -

          This structure is a simple cylinder, with diameter 0.1 meters, located at X=1.5, Y=0.0, Z=0.0. The interface surface file is ‘src/interface.stl’.

          -

          The cylinder is represented in OpenSees by a cantilevered beam, with an elastic section, modelled with displacement-action controlled beam elements. The bottom of the cantilevered beam is fixed at Z=0.0.

          -

          The constrained node is removed from the coupled solution, by omitting it from the list ‘coupledNodes’ in the OpenSees model file.

          -

          The length of the cylinder is 0.5 meters.

          -

          The flow around the cylinder is calculated for a given period of time.

          -

          Outputs: -Results for free surface, velocity, and pressure, as well as interface forces and moments and a cut section of the case at a specified interval.

          -

          Simulation of MPM debris impacts on one row of five obstacles

          -
          +

          4.6.1. Outline

          +

          Example to demonstrate how to run a MPM simulation to determine loads on an array of port buildings during a tsunami with respect to debris impacts and damming. After, we perform +an OpenSees simulation of one building assuming uncertainties in the building properties.

          +

          The Waseda University Tsunami Wave Basin (WU TBW) flume is 4 meters wide (from X=-2m to X=2 m), 1 meter tall (Z=0.0m to Z=1.0m), and 9 meters long (Y=0.0m to Y=9.0m).

          +

          The case is initialized with a still water level of 0.23 meters.

          +

          Results for free surface, velocity, and pressure, as well as structural load forces, are output at a specified interval to match experimental instruments.

          +
          ../../../../../_images/TOKYO_BoreFrontImage_Debris3_o5x1_Frame20_29072023.png +

          Fig. 4.6.1.1 Simulation of MPM debris impacts on one row of five obstacles

          -

          Schematic of the flume and sensor locations

          -
          +
          ../../../../../_images/B4_Flume_Schematic.png +

          Fig. 4.6.1.2 Schematic of the flume and sensor locations

          -

          Smart debris used in experiments

          -
          +
          ../../../../../_images/B4_Debris_Picture.PNG +

          Fig. 4.6.1.3 Smart debris used in experiments

          -
          -

          CASE RUN TIME

          +
          +

          4.6.2. Simulation

          Simulation Time: 6 seconds - Ran on TACC Lonestar6, 56 processors, 3 NVIDIA A100 GPUs, 1 node -> Real Time: 1hr, 20 minutes

          -

          Submitted -Oct 8, 2023 1:14:37 PM -Finished -Oct 8, 2023 2:34:10 PM

          The case can be run for as long as desired, but mind that the longer the case runs, the longer the postprocessing routines will be.

          In order to retrieve results from the analysis, the analysis must complete and postprocess the model output files into a VTK format before the end of the allotted submission time.

          Provide a large amount of time for the ‘Max Run Time’ field in HydroUQ when submitting a job to ensure the model completes before the time allotted runs out!

          -

          Be aware that the smaller the OpenFOAM Outputs and OpenSees Outputs ‘Time Interval’ value is, the longer the post processing of the case will take after analysis has completed, and the larger the results.zip folder will be.

          -

          USE CAUTION WHEN REQUESTING OUTPUT! Only ask for what you need, or you will end up will massive amounts of data.

          +

          Be aware that the smaller the OpenFOAM Outputs and OpenSees Outputs ‘Time Interval’ value is, the longer the post-processing of the case will take after analysis has been completed, and the larger the results.zip folder will be.

          +
          +

          Warning

          +

          Use caution when requesting sensors and using high sampling rates. Only ask for what you need, or you will end up with massive amounts of data.

          +
          -
          -

          Post Processing

          +
          +

          4.6.3. Analysis

          Retrieving the results.zip folder from the Tools and Applications Page of Design Safe..

          -
          +
          ../../../../../_images/DSToolsAndAppsJobsStatus2.PNG +

          Fig. 4.6.3.1 Locating the job files on DesignSafe

          Check if the job has finished. If it has, click ‘More info’.

          -
          +
          ../../../../../_images/DSToolsAndAppsJobsStatusFinished2.PNG +

          Fig. 4.6.3.2 Once the job is finished, the output files should be available in the directory to which the analysis results were sent

          Find the files by clicking ‘View’.

          -
          +
          ../../../../../_images/DSToolsAndAppsJobsStatusViewFiles2.PNG +

          Fig. 4.6.3.3 Locating this directory is easy.

          Move the results.zip to somewhere in My Data/. Use the Extractor tool available on DesignSafe. Unzip the results.zip folder.

          ../../../../../_images/extractonDS2.PNG

          OR Download the results.zip folder to your PC and unzip to look at the model results.

          -
          +
          ../../../../../_images/downloadResults2.PNG +

          Fig. 4.6.3.4 Download the results to look at the VTK files of the analysis. This will include OpenFOAM and OpenSees field data and model geometry

          Extract the Zip folder either on DesignSafe or on your local machine. You will need Paraview to view the model data.

          -
          +
          ../../../../../_images/resultsZip2.png +

          Fig. 4.6.3.5 Locate the zip folder and extract it to somewhere convenient

          -

          The results folder should look something like this.

          -
          -../../../../../_images/results1.png -
          -

          Paraview files have a .PVD extension. Open VTK/Fluid.vtm.series to look at OpenFOAM results. -Open OpenSeesOutput.pvd to look at OpenSees results.

          -
          -../../../../../_images/Paraview1.PNG -
          -

          OpenSees Displacements And Reactions

          -
          -../../../../../_images/TipDisplacement1.png -
          -
          -../../../../../_images/ReactionForces1.png -
          -

          OpenFOAM probe and function object output is available in results/postProcessing/.

          -

          OpenFOAM output is messy. An example Matlab script is provided in the /src/ directory to post process the OpenFOAM output for this particular case and output. -This file can be modified to work for any case. The names of the data folders will need to be changed according to the name of the probe given in HydroUQ.

          -
          -../../../../../_images/MatlabScriptCopyToLocation1.PNG -
          -

          OpenFOAM Calculated Story Forces

          -
          -../../../../../_images/storyForces1.png -
          -

          OpenFOAM Calculated Coupled Interface Forces

          -
          -../../../../../_images/Forces1.png -
          -

          OpenFOAM Calculated Coupled Interface Moments

          -
          -../../../../../_images/Moments1.png -
          -

          OpenFOAM Calculated Pressure Probe Values

          -
          -../../../../../_images/Pressures.png -
          -

          OpenFOAM Calculated Velocity Probe Values

          -
          -../../../../../_images/Velocities1.png -
          -

          OpenFOAM Calculated Free Surface Values

          -
          -../../../../../_images/WaveGauges1.png
          +
          +

          4.6.4. References

          @@ -348,7 +330,7 @@

          Post Processing

          - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

          diff --git a/docs/common/user_manual/examples/desktop/hdro-0005/README.html b/docs/common/user_manual/examples/desktop/hdro-0005/README.html new file mode 100644 index 00000000..0ecae19d --- /dev/null +++ b/docs/common/user_manual/examples/desktop/hdro-0005/README.html @@ -0,0 +1,501 @@ + + + + + + + + + + 4.1. Feature - Stochastic Wave Loading on a Simple Structure - Stochastic Wave Spectra — Hydro-UQ documentation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          + + + +
          + + + + + +
          + +
          + + + + + + + + + + + + + + + + + + + +
          + +
            + +
          • »
            • + +
          • 4. Examples »
            • + +
          • 4.1. Feature - Stochastic Wave Loading on a Simple Structure - Stochastic Wave Spectra
            • + + +
          • + + + View page source + + +
            • + +
          + + +
          +
          +
          +
          + +
          +

          4.1. Feature - Stochastic Wave Loading on a Simple Structure - Stochastic Wave Spectra

          + ++++ + + + + + +

          Problem files

          Github

          +
          +

          Table of Contents

          + +
          +
          +

          4.1.1. Overview

          +
          +../../../../../_images/hdro-0005_WaveTimeSeries.png +

          Fig. 4.1.1.1 Stochastic JONSWAP wave spectra produced in HydroUQ, applying the welib Python package.

          +
          +

          In this local workflow example, basic uncertainty quantification methods (Forward, Sensitivity, Reliability) are applied to the response of a simple structure loaded by stochastic wave spectra.

          +
          +
          +

          4.1.2. Set-Up

          +
          +../../../../../_images/hdro-0005_UQ.png +

          Fig. 4.1.2.1 HydroUQ’s desktop GUI for the NHERI OSU LWF digital wave-flume twin.

          +
          +

          Details for the experiments are available in various publications. Namely, the work of Andrew Winter [Winter2020] [Winter2019], Krishnendu Shekhar [Shekhar2020] and Dakota Mascarenas [Mascarenas2022] [Mascarenas2022PORTS]. The simulations replicated in this example appeared originally in Bonus 2023 [Bonus2023Dissertation].

          +

          Experiments were performed in the NHERI OSU LWF, a 100 meter long flume with adjustable bathymetry, in order to quantify stochastic impact loads of ordered and disordered debris-fields on effectively rigid, raised structure.

          +
          +../../../../../_images/hdro-0005_GI.png +

          Fig. 4.1.2.2 NHERI OSU LWF facilty’s experimental schematic used in this example. Adapted from Winter 2019 [Winter2019], and Mascarenas 2022 [Mascarenas2022].

          +
          +

          This example may help to produce a robust database (numerical and physical) from which to eventually be able to extract both the first principles of wave-driven debris-field phenomena and design guidelines on induced forces.

          +

          We validate against two very similar (but not identical) physical studies done in the OSU LWF by [Shekhar2020] and [Mascarenas2022], indicating high accuracy of our model and low bias to minor experiment specifications.

          +

          Results for free surface elevation and streamwise structural loads are to be recorded for validation at a specified interval.

          +

          Qualitatively, an MPM simulation of debris impacts on a raised structure in the OSU LWF is shown below.

          +
          +../../../../../_images/hdro-0005_SIM.png +

          Fig. 4.1.2.3 OSU LWF debris impact photos from HydroUQ’s MPM simulations.

          +
          +

          It appears similar in the mechanism of debris impact, stalling, and deflection relative to the structure and flow for a similar case in Mascarenas 2022 [Mascarenas2022].

          +
          +../../../../../_images/hdro-0005_EVT.png +

          Fig. 4.1.2.4 OSU LWF debris impact photos from Mascarenas 2022 [Mascarenas2022] experiments.

          +
          +

          The experiments by Shekhar et al. 2020 [Shekhar2020] are also shown below for comparison. These tests had a slightly different configuartion, primarily the debris were located 0.5 meters further upstream from the box and the water level was 0.10-0.15 meters lower than the 2.0 meter datum used in the simulations and Mascarenas 2022 [Mascarenas2022] experiments.

          +
          +../../../../../_images/hdro-0005_EDP.png +

          Fig. 4.1.2.5 OSU LWF debris impact photos from Shekhar et al. 2020 [Shekhar2020] experiments.

          +
          +

          Similar figures can be made for the whole range of order debris-array experiments done at the OSU LWF. However, this example focuses on teaching you how to replicate the above results.

          +

          A step-by-step walkthrough on replicating an MPM simulation result from Bonus 2023 [Bonus2023Dissertation] is provided below.

          +

          Open Settings. Here we set the simulation time, the time step, and the number of processors to use, among other pre-simulation decisions.

          +
          +../../../../../_images/hdro-0005_RV.png +

          Fig. 4.1.2.6 HydroUQ Settings GUI

          +
          +

          Open Bodies / Fluid / Material. Here we set the material properties of the fluid and the debris.

          +
          +../../../../../_images/hdro-0005_RES_Summary_Forward.png +

          Fig. 4.1.2.7 HydroUQ Bodies Fluid Material GUI

          +
          +

          Open Bodies / Fluid / Geometry. Here we set the geometry of the flume, the debris, and the raised structure.

          +
          +../../../../../_images/hdro-0005_RES_Scatter.png +

          Fig. 4.1.2.8 HydroUQ Bodies Fluid Geometry GUI

          +
          +

          Open Algorithm. Here we set the algorithm parameters for the simulation. We choose to apply F-Bar antilocking to aid in the pressure field’s accuracy on the fluid. The associated toggle must be checked, and the antilocking ratio set to 0.9, loosely.

          +
          +../../../../../_images/hdro-0005_RES_Cumulative_Forward.png +

          Fig. 4.1.2.9 HydroUQ Bodies Fluid Algorithm GUI

          +
          +

          Open Bodies / Fluid / Partitions. Here we set the number of partitions for the simulation. This is the domain decomposition across discrete hardware units, i.e. Multi-GPUs. These may be kept as their default values.

          +
          +common/user_manual/examples/desktop/hdro-0005/figures/hdro-0005_RES_HistogramForward.png +

          Fig. 4.1.2.10 HydroUQ Bodies Fluid Partitions GUI

          +
          +

          Moving onto the creation of an ordered debris-array, we set the debris properties in the Bodies / Debris / Material tab. We will assume debris are made of HDPE plastic, as in experiments by Mascarenas 2022 [Mascarenas2022] and Shekhar et al. 2020 [Shekhar2020].

          +
          +../../../../../_images/hdro-0005_RV_Sensitivity.png +

          Fig. 4.1.2.11 HydroUQ Bodies Debris Material GUI

          +
          +

          Open Bodies / Debris / Geometry. Here we set the debris properties, such as the number of debris, the size of the debris, and the spacing between the debris. Rotation is another option, though not used in this example. We’ve elected to use an 8 x 4 grid of debris (longitudinal axis parallel to long-axis of the flume).

          +
          +../../../../../_images/hdro-0005_RES_Summary_Sensitivity.png +

          Fig. 4.1.2.12 HydroUQ Bodies Debris Geometry GUI

          +
          +

          The Bodies / Debris / Algorithm and Debris / Partitions tabs are not used in this example, but are available for more advanced users.

          +

          Open Bodies / Structures. Uncheck the box that enables this body, if it is checked. We will not model the structure as a body in this example, instead, we will modify it as a boundary later.

          +
          +../../../../../_images/hdro-0005_RES_Scatter_Sensitivity.png +

          Fig. 4.1.2.13 HydroUQ Bodies Structures GUI

          +
          +

          Open Boundaries / Wave Flume. We will set the boundary to be a rigid body, with a fixed separable velocity condition, that is faithful to the digital tiwn of the NHERI OSU LWF. Bathmyetry joint points should be identical to the ones used in Bodeis / FLuid.

          +
          +../../../../../_images/hdro-0005_RES_Summary_Reliability.png +

          Fig. 4.1.2.14 HydroUQ Boundaries Wave Flume Facility GUI

          +
          +

          Open Boundaries / Wave Generator. Fill in the appropriate file-path for the wave generator paddle motion. It is designed to produce near-solitary like waves.

          +
          +../../../../../_images/hdro-0005_forces.png +

          Fig. 4.1.2.15 HydroUQ Boundaries Wave Generator GUI

          +
          +

          Open Boundaries / Rigid Structure. This is where we will specify the raised structure as a boundary condition. By doing so, we can determine exact loads on the rigid boundary grid-nodes, which may then be mapped to the FEM tab for nonlinear UQ structural response analysis.

          +
          +../../../../../_images/hdro-0005_moments.png +

          Fig. 4.1.2.16 HydroUQ Boundaries Rigid Structure GUI

          +
          +

          Open Boundaries / RigidWalls.

          +
          +../../../../../_images/hdro-0005_IntegratedPileLoads.png +

          Fig. 4.1.2.17 HydroUQ Boundaries Wave-Flume Facility GUI

          +
          +

          Open Sensors / Wave Gauges. Set the Use these sensor? box to True so that the simulation will output results for the instruments we set on this page.

          +

          Three wave gauges will be defined. The first is located prior to the bathymetry ramps, the second partially up the ramps, and the third near the bathymetry crest, debris, and raised structure.

          +

          Set the origins and dimensions of each wave as in the table below. To match experimental conditions, we also apply a 120 Hz sampling rate to the wave gauges, meaning they record data every 0.0083 seconds.

          +
          +
          +

          4.1.3. Simulation

          +

          We assume most computers will be able to run this simulation within a few minutes if samples are kept below 100.

          +
          +

          Warning

          +

          Only ask for what you need in terms of recorder count, time-step size, random variables, and UQ samples. Otherwise, you will end up with massive amounts of data which can slow simulations due to I/O constraints.

          +
          +
          +
          +

          4.1.4. Analysis

          +

          This completes our HydroUQ validation example for stochastic wave-loading on a simple frame structure.

          +
          +
          +

          4.1.5. References

          +
          +
          Winter2019(1,2)
          +

          Winter, A. (2019). “Effects of Flow Shielding and Channeling on Tsunami-Induced Loading of Coastal Structures.” PhD thesis. University of Washington, Seattle.

          +
          +
          Winter2020
          +

          Andrew O Winter, Mohammad S Alam, Krishnendu Shekhar, Michael R Motley, Marc O Eberhard, Andre R Barbosa, Pedro Lomonaco, Pedro Arduino, Daniel T Cox (2019). “Tsunami-Like Wave Forces on an Elevated Coastal Structure: Effects of Flow Shielding and Channeling.” Journal of Waterway, Port, Coastal, and Ocean Engineering.

          +
          +
          Shekhar2020(1,2,3,4,5)
          +

          Shekhar, K., Mascarenas, D., and Cox, D. (2020). “Wave-Driven Debris Impact on a Raised Structure in the Large Wave Flume.” 17th International Conference on Hydroinformatics, Seoul, South Korea.

          +
          +
          Mascarenas2022(1,2,3,4,5,6,7)
          +

          Mascarenas, Dakota. (2022). “Quantification of Wave-Driven Debris Impact on a Raised Structure in a Large Wave Flume.” Masters thesis. University of Washington, Seattle.

          +
          +
          Mascarenas2022PORTS
          +

          Mascarenas, Dakota, Motley, M., Eberhard, M. (2022). “Wave-Driven Debris Impact on a Raised Structure in the Large Wave Flume.” Journal of Waterway, Port, Coastal, and Ocean Engineering.

          +
          +
          Bonus2023Dissertation(1,2)
          +

          Bonus, Justin (2023). “Evaluation of Fluid-Driven Debris Impacts in a High-Performance Multi-GPU Material Point Method.” PhD thesis. University of Washington, Seattle.

          +
          +
          +
          +
          + + +
          + +
          +
          + +
          + +
          +

          + © Copyright 2020-2024, The Regents of the University of California. + +

          +
          + + + + Built with Sphinx using a + + theme + + provided by Read the Docs. + +
          +
          +
          + +
          + +
          + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/common/user_manual/examples/desktop/hdro-0010/README.html b/docs/common/user_manual/examples/desktop/hdro-0010/README.html new file mode 100644 index 00000000..9f9ba7d2 --- /dev/null +++ b/docs/common/user_manual/examples/desktop/hdro-0010/README.html @@ -0,0 +1,501 @@ + + + + + + + + + + 4.2. Forward Sampling - Simple Piston Generated Wave - Taichi Event — Hydro-UQ documentation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          + + + +
          + + + + + +
          + +
          + + + + + + + + + + + + + + + + + + + +
          + + + + +
          +
          +
          +
          + +
          +

          4.2. Forward Sampling - Simple Piston Generated Wave - Taichi Event

          + ++++ + + + + + +

          Problem files

          Github

          +
          +

          Table of Contents

          + +
          +
          +

          4.2.1. Overview

          +
          +../../../../../_images/hdro-0010_EVT_Single.png +

          Fig. 4.2.1.1 TaichiEvent EVT of the pbf2d.py example. Includes a linear piston wave-maker creating breaking waves using local HPC resources (e.g. vectorized CPU, GPU).

          +
          +

          In this local workflow example, basic uncertainty quantification methods (Forward, Sensitivity, Reliability) are applied to the response of a simple structure loaded by stochastic wave spectra.

          +
          +
          +

          4.2.2. Set-Up

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_UQ.png +

          Fig. 4.2.2.1 HydroUQ’s desktop GUI for the NHERI OSU LWF digital wave-flume twin.

          +
          +

          Details for the experiments are available in various publications. Namely, the work of Andrew Winter [Winter2020] [Winter2019], Krishnendu Shekhar [Shekhar2020] and Dakota Mascarenas [Mascarenas2022] [Mascarenas2022PORTS]. The simulations replicated in this example appeared originally in Bonus 2023 [Bonus2023Dissertation].

          +

          Experiments were performed in the NHERI OSU LWF, a 100 meter long flume with adjustable bathymetry, in order to quantify stochastic impact loads of ordered and disordered debris-fields on effectively rigid, raised structure.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_GI.png +

          Fig. 4.2.2.2 NHERI OSU LWF facilty’s experimental schematic used in this example. Adapted from Winter 2019 [Winter2019], and Mascarenas 2022 [Mascarenas2022].

          +
          +

          This example may help to produce a robust database (numerical and physical) from which to eventually be able to extract both the first principles of wave-driven debris-field phenomena and design guidelines on induced forces.

          +

          We validate against two very similar (but not identical) physical studies done in the OSU LWF by [Shekhar2020] and [Mascarenas2022], indicating high accuracy of our model and low bias to minor experiment specifications.

          +

          Results for free surface elevation and streamwise structural loads are to be recorded for validation at a specified interval.

          +

          Qualitatively, an MPM simulation of debris impacts on a raised structure in the OSU LWF is shown below.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_SIM.png +

          Fig. 4.2.2.3 OSU LWF debris impact photos from HydroUQ’s MPM simulations.

          +
          +

          It appears similar in the mechanism of debris impact, stalling, and deflection relative to the structure and flow for a similar case in Mascarenas 2022 [Mascarenas2022].

          +
          +../../../../../_images/hdro-0010_EVT.png +

          Fig. 4.2.2.4 OSU LWF debris impact photos from Mascarenas 2022 [Mascarenas2022] experiments.

          +
          +

          The experiments by Shekhar et al. 2020 [Shekhar2020] are also shown below for comparison. These tests had a slightly different configuartion, primarily the debris were located 0.5 meters further upstream from the box and the water level was 0.10-0.15 meters lower than the 2.0 meter datum used in the simulations and Mascarenas 2022 [Mascarenas2022] experiments.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_EDP.png +

          Fig. 4.2.2.5 OSU LWF debris impact photos from Shekhar et al. 2020 [Shekhar2020] experiments.

          +
          +

          Similar figures can be made for the whole range of order debris-array experiments done at the OSU LWF. However, this example focuses on teaching you how to replicate the above results.

          +

          A step-by-step walkthrough on replicating an MPM simulation result from Bonus 2023 [Bonus2023Dissertation] is provided below.

          +

          Open Settings. Here we set the simulation time, the time step, and the number of processors to use, among other pre-simulation decisions.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RV.png +

          Fig. 4.2.2.6 HydroUQ Settings GUI

          +
          +

          Open Bodies / Fluid / Material. Here we set the material properties of the fluid and the debris.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RES_Summary_Forward.png +

          Fig. 4.2.2.7 HydroUQ Bodies Fluid Material GUI

          +
          +

          Open Bodies / Fluid / Geometry. Here we set the geometry of the flume, the debris, and the raised structure.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RES_Scatter.png +

          Fig. 4.2.2.8 HydroUQ Bodies Fluid Geometry GUI

          +
          +

          Open Algorithm. Here we set the algorithm parameters for the simulation. We choose to apply F-Bar antilocking to aid in the pressure field’s accuracy on the fluid. The associated toggle must be checked, and the antilocking ratio set to 0.9, loosely.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RES_Cumulative_Forward.png +

          Fig. 4.2.2.9 HydroUQ Bodies Fluid Algorithm GUI

          +
          +

          Open Bodies / Fluid / Partitions. Here we set the number of partitions for the simulation. This is the domain decomposition across discrete hardware units, i.e. Multi-GPUs. These may be kept as their default values.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RES_HistogramForward.png +

          Fig. 4.2.2.10 HydroUQ Bodies Fluid Partitions GUI

          +
          +

          Moving onto the creation of an ordered debris-array, we set the debris properties in the Bodies / Debris / Material tab. We will assume debris are made of HDPE plastic, as in experiments by Mascarenas 2022 [Mascarenas2022] and Shekhar et al. 2020 [Shekhar2020].

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RV_Sensitivity.png +

          Fig. 4.2.2.11 HydroUQ Bodies Debris Material GUI

          +
          +

          Open Bodies / Debris / Geometry. Here we set the debris properties, such as the number of debris, the size of the debris, and the spacing between the debris. Rotation is another option, though not used in this example. We’ve elected to use an 8 x 4 grid of debris (longitudinal axis parallel to long-axis of the flume).

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RES_Summary_Sensitivity.png +

          Fig. 4.2.2.12 HydroUQ Bodies Debris Geometry GUI

          +
          +

          The Bodies / Debris / Algorithm and Debris / Partitions tabs are not used in this example, but are available for more advanced users.

          +

          Open Bodies / Structures. Uncheck the box that enables this body, if it is checked. We will not model the structure as a body in this example, instead, we will modify it as a boundary later.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RES_Scatter_Sensitivity.png +

          Fig. 4.2.2.13 HydroUQ Bodies Structures GUI

          +
          +

          Open Boundaries / Wave Flume. We will set the boundary to be a rigid body, with a fixed separable velocity condition, that is faithful to the digital tiwn of the NHERI OSU LWF. Bathmyetry joint points should be identical to the ones used in Bodeis / FLuid.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_RES_Summary_Reliability.png +

          Fig. 4.2.2.14 HydroUQ Boundaries Wave Flume Facility GUI

          +
          +

          Open Boundaries / Wave Generator. Fill in the appropriate file-path for the wave generator paddle motion. It is designed to produce near-solitary like waves.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_forces.png +

          Fig. 4.2.2.15 HydroUQ Boundaries Wave Generator GUI

          +
          +

          Open Boundaries / Rigid Structure. This is where we will specify the raised structure as a boundary condition. By doing so, we can determine exact loads on the rigid boundary grid-nodes, which may then be mapped to the FEM tab for nonlinear UQ structural response analysis.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_moments.png +

          Fig. 4.2.2.16 HydroUQ Boundaries Rigid Structure GUI

          +
          +

          Open Boundaries / RigidWalls.

          +
          +common/user_manual/examples/desktop/hdro-0010/figures/hdro-0005_IntegratedPileLoads.png +

          Fig. 4.2.2.17 HydroUQ Boundaries Wave-Flume Facility GUI

          +
          +

          Open Sensors / Wave Gauges. Set the Use these sensor? box to True so that the simulation will output results for the instruments we set on this page.

          +

          Three wave gauges will be defined. The first is located prior to the bathymetry ramps, the second partially up the ramps, and the third near the bathymetry crest, debris, and raised structure.

          +

          Set the origins and dimensions of each wave as in the table below. To match experimental conditions, we also apply a 120 Hz sampling rate to the wave gauges, meaning they record data every 0.0083 seconds.

          +
          +
          +

          4.2.3. Simulation

          +

          We assume most computers will be able to run this simulation within a few minutes if samples are kept below 100.

          +
          +

          Warning

          +

          Only ask for what you need in terms of recorder count, time-step size, random variables, and UQ samples. Otherwise, you will end up with massive amounts of data which can slow simulations due to I/O constraints.

          +
          +
          +
          +

          4.2.4. Analysis

          +

          This completes our HydroUQ validation example for stochastic wave-loading on a simple frame structure.

          +
          +
          +

          4.2.5. References

          +
          +
          Winter2019(1,2)
          +

          Winter, A. (2019). “Effects of Flow Shielding and Channeling on Tsunami-Induced Loading of Coastal Structures.” PhD thesis. University of Washington, Seattle.

          +
          +
          Winter2020
          +

          Andrew O Winter, Mohammad S Alam, Krishnendu Shekhar, Michael R Motley, Marc O Eberhard, Andre R Barbosa, Pedro Lomonaco, Pedro Arduino, Daniel T Cox (2019). “Tsunami-Like Wave Forces on an Elevated Coastal Structure: Effects of Flow Shielding and Channeling.” Journal of Waterway, Port, Coastal, and Ocean Engineering.

          +
          +
          Shekhar2020(1,2,3,4,5)
          +

          Shekhar, K., Mascarenas, D., and Cox, D. (2020). “Wave-Driven Debris Impact on a Raised Structure in the Large Wave Flume.” 17th International Conference on Hydroinformatics, Seoul, South Korea.

          +
          +
          Mascarenas2022(1,2,3,4,5,6,7)
          +

          Mascarenas, Dakota. (2022). “Quantification of Wave-Driven Debris Impact on a Raised Structure in a Large Wave Flume.” Masters thesis. University of Washington, Seattle.

          +
          +
          Mascarenas2022PORTS
          +

          Mascarenas, Dakota, Motley, M., Eberhard, M. (2022). “Wave-Driven Debris Impact on a Raised Structure in the Large Wave Flume.” Journal of Waterway, Port, Coastal, and Ocean Engineering.

          +
          +
          Bonus2023Dissertation(1,2)
          +

          Bonus, Justin (2023). “Evaluation of Fluid-Driven Debris Impacts in a High-Performance Multi-GPU Material Point Method.” PhD thesis. University of Washington, Seattle.

          +
          +
          +
          +
          + + +
          + +
          +
          + +
          + +
          +

          + © Copyright 2020-2024, The Regents of the University of California. + +

          +
          + + + + Built with Sphinx using a + + theme + + provided by Read the Docs. + +
          +
          +
          + +
          + +
          + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/common/user_manual/installation/desktop/downloadOther.html b/docs/common/user_manual/installation/desktop/downloadOther.html index f099aacc..b3673d10 100644 --- a/docs/common/user_manual/installation/desktop/downloadOther.html +++ b/docs/common/user_manual/installation/desktop/downloadOther.html @@ -16,7 +16,7 @@ - + @@ -228,7 +228,7 @@

          - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

          diff --git a/docs/common/user_manual/installation/desktop/downloadOtherMAC.html b/docs/common/user_manual/installation/desktop/downloadOtherMAC.html index 469e59ec..6f606386 100644 --- a/docs/common/user_manual/installation/desktop/downloadOtherMAC.html +++ b/docs/common/user_manual/installation/desktop/downloadOtherMAC.html @@ -16,7 +16,7 @@ - + @@ -355,7 +355,7 @@

          Test the Install of Python, OpenSees & Dakota

          - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

          diff --git a/docs/common/user_manual/installation/desktop/downloadOtherWindows.html b/docs/common/user_manual/installation/desktop/downloadOtherWindows.html index dec3dbd6..f1e30e06 100644 --- a/docs/common/user_manual/installation/desktop/downloadOtherWindows.html +++ b/docs/common/user_manual/installation/desktop/downloadOtherWindows.html @@ -16,7 +16,7 @@ - + @@ -327,7 +327,7 @@

          Test the Install of Python, OpenSees & Dakota

          - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

          diff --git a/docs/common/user_manual/installation/desktop/install_Windows.html b/docs/common/user_manual/installation/desktop/install_Windows.html index 41731600..524397ae 100644 --- a/docs/common/user_manual/installation/desktop/install_Windows.html +++ b/docs/common/user_manual/installation/desktop/install_Windows.html @@ -16,7 +16,7 @@ - + @@ -130,6 +130,7 @@
      • 1.2. Install on MacOS
        • +
      • 1.3. Running Jobs at DesignSafe
    • 2. User Interface
      • @@ -251,9 +252,9 @@

      1.1.3. Install OpenFOAM for Windows

      1.1.4. Download the Application

      Navigate to the HydroUQ Download page, which should resemble Fig. 1.1.4.6, for a list of downloadable files and directories. Click the Windows_Download.zip file and select Download in the pop-up window’s bottom right.

      -
      +
      HydroUQ tool download page -

      Fig. 1.1.4.6 HydroUQ tool download page.

      +

      Fig. 1.1.4.6 HydroUQ tool download page.

      After downloading, extract the zip file to your preferred location, such as C:/SimCenter/. You can create and move a shortcut of the HydroUQ.exe to your Desktop for convenience.

      @@ -268,10 +269,10 @@

      1.1.5. Test the InstallationNote

      Since the SimCenter is not registered as a Windows vendor, our applications may trigger a warning about unsigned applications from unknown sources when you start the HydroUQ app application for the first time. It is safe to bypass this warning for SimCenter applications.

      -

      Launch the application to view the user interface as shown in Fig. 1.1.5.6. It’s recommended to run the Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF) to ensure proper operation.

      -
      +

      Launch the application to view the user interface as shown in Fig. 1.1.5.6. It’s recommended to run the Feature - Stochastic Wave Loading on a Simple Structure - Stochastic Wave Spectra to ensure proper operation.

      +
      ../../../../_images/HydroWin.png -

      Fig. 1.1.5.6 HydroUQ tool on startup in Windows 10

      +

      Fig. 1.1.5.6 HydroUQ tool on startup in Windows 10

      @@ -299,7 +300,7 @@

      1.1.6. Troubleshooting<

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/installation/desktop/install_macOS.html b/docs/common/user_manual/installation/desktop/install_macOS.html index 2f166e8b..85f4c225 100644 --- a/docs/common/user_manual/installation/desktop/install_macOS.html +++ b/docs/common/user_manual/installation/desktop/install_macOS.html @@ -16,7 +16,7 @@ - + @@ -49,7 +49,7 @@ - + @@ -130,6 +130,7 @@
    • 1.2.6. Test the Installation

    +
  • 1.3. Running Jobs at DesignSafe
  • 2. User Interface
    • @@ -239,21 +240,16 @@

    1.2.1. Install Python 3.9 +
    ../../../../_images/pythonKernel.png -

    Fig. 1.2.1.1 Python: Kernel Version

    -
    - -

  • Visit Python.org and download the macOS 64-bit Intel-only installer for Python 3.9.

    -
    -../../../../_images/pythonDownload.png -

    Fig. 1.2.1.2 Python: python.org MacOS Download Page

    +

    Fig. 1.2.1.1 Python: Kernel Version

    • +

  • To download a Python installer with your browser open the HydroUQ Download page. There, you will find various files and directories available for download. Locate the file named python-3.9.13-macosx10.9.pkg, which we copied from Python.org. Proceed to download this installer file and then open it on your local machine to initiate the Python installation process.

  • Run the installer. Upon completion, a folder with several files will open, as shown in the figure below. Execute Update Shell Profile.command.sh and Install CertificateCommand.sh by double-clicking each.

    -
    +
    ../../../../_images/pythonInstallShell.png -

    Fig. 1.2.1.3 Python: Folder Displayed at Conclusion of Install

    +

    Fig. 1.2.1.2 Python: Folder Displayed at Conclusion of Install

  • Install additional packages via the nheri_simcenter package by starting a Terminal window and type the following command:

    @@ -297,9 +293,9 @@

    1.2.4. Install OpenFOAM for macOS

    1.2.5. Download the Application

    To download the HydroUQ app, navigate to the HydroUQ Download page which should resemble Fig. 1.2.5.6. The download page contains a list of downloadable files and directories.

    -
    +
    ../../../../_images/H20Download.png -

    Fig. 1.2.5.6 HydroUQ tool download page.

    +

    Fig. 1.2.5.6 HydroUQ tool download page.

    Click on the file with a name ending with Mac_Download.dmg to download the HydroUQ app. In the pop-up window, click on the Download button in the bottom right corner. After the download is completed, open the dmg file and copy the HydroUQ app to a location in your filesystem.

    @@ -318,17 +314,17 @@

    1.2.6. Test the Installation../../../../_images/AppleSecurity.png

    -

    Once the application starts, verify the setup by running an example problem Validation - Multiple Debris Impacts on a Raised Structure - Digital Twin (OSU LWF), see Fig. 1.2.6.6.

    -
    +

    Once the application starts, verify the setup by running an example problem Feature - Stochastic Wave Loading on a Simple Structure - Stochastic Wave Spectra, see Fig. 1.2.6.6.

    +
    ../../../../_images/HydroMac.png -

    Fig. 1.2.6.6 HydroUQ application on startup.

    +

    Fig. 1.2.6.6 HydroUQ application on startup.

    Note

    When the HydroUQ app is running, open the app/preferences or File/Preferences and make sure that python3 appears under External Applications:Python, as shown in the figure below. If you used older versions of SimCenter tools this was not the default. The exact location of Python3 that you installed can be found by opening the terminal application and executing the which python3 command. Enter the path shown as a response in the Preferences panel under Python and then press the Save button.

    -
    +
    ../../../../_images/pythonPreferences.png -

    Fig. 1.2.6.7 Set Python Preferences.

    +

    Fig. 1.2.6.7 Set Python Preferences.

    @@ -344,7 +340,7 @@

    1.2.6. Test the Installation

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/installation/desktop/installation.html b/docs/common/user_manual/installation/desktop/installation.html index 6650ef31..534a74e1 100644 --- a/docs/common/user_manual/installation/desktop/installation.html +++ b/docs/common/user_manual/installation/desktop/installation.html @@ -16,7 +16,7 @@ - + @@ -124,6 +124,7 @@
  • 1. Installation
  • 2. User Interface
    • @@ -236,6 +237,11 @@
  • 1.2.6. Test the Installation

    • +
  • 1.3. Running Jobs at DesignSafe +

    • @@ -250,7 +256,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/installation/desktop/setupTACC.html b/docs/common/user_manual/installation/desktop/setupTACC.html new file mode 100644 index 00000000..54144f1d --- /dev/null +++ b/docs/common/user_manual/installation/desktop/setupTACC.html @@ -0,0 +1,351 @@ + + + + + + + + + + 1.3. Running Jobs at DesignSafe — Hydro-UQ documentation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + + +
    + + + + + +
    + +
    + + + + + + + + + + + + + + + + + + + +
    + + + + +
    +
    +
    +
    + +
    +

    1.3. Running Jobs at DesignSafe

    +

    To run jobs on TACC high performance compute resources using the Run at DesignSafe button, the user must obtain a job allocation and then they must run applications to create credentials on each of the compute resourcses their jobs will run on.

    +
    +

    1.3.1. Allocation

    +

    To obtain an allocation, the user can either submit a DesignSafe Ticket requesting an allocation or through the more formal TACC allocation process. The DesignSafe process is probably quickest and easiest, e.g. a ticket with “Please can I have an allocation to run SimCenter jobs at DesignSafe” will be sufficient.

    +
    +
    +

    1.3.2. Credentials

    +

    Due to cybersecurity issues, DesignSafe is requiring that all users obtain credentials for the machines on which jobs will run. Before you can run the application using the ‘Run at DesignSafe’ button, you must first obtain credentials for the machine(s) your jobs will run on. If you follow the links provided you will be taken to a DesignSafe app launch page specifically created for this process:

    +
      +

    1. Frontera Credentials

      2. +

    2. LoneStar6 Credentials

      3. +
    +

    Simply press the green “Submit Job” button. On the pop up window that is then displayed, enter your DesignSafe password and the 6 digit MFA token before pressing the ‘Authentificate’ button. Once you see the words “Job submitted successfully. Monitor its progress in Job Status” in green, your credentials have been set-up and you can exit the webpage. If no pop up is displayed, you already have credentials for that machine and can exit the page.

    +
    +../../../../_images/Credentials4.png +
    +
    +
    + + +
    + +
    +
    + +
    + +
    +

    + © Copyright 2020-2024, The Regents of the University of California. + +

    +
    + + + + Built with Sphinx using a + + theme + + provided by Read the Docs. + +
    +
    +
    + +
    + +
    + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/common/user_manual/releases/eeCapabilities.html b/docs/common/user_manual/releases/eeCapabilities.html index 5b19bd78..a42be3cf 100644 --- a/docs/common/user_manual/releases/eeCapabilities.html +++ b/docs/common/user_manual/releases/eeCapabilities.html @@ -16,7 +16,7 @@ - + @@ -213,7 +213,7 @@

    Capabilities

    -

    Version 3.5 of HydroUQ app was released April 2024. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked blue in the following list of features.)

    +

    Version 4.1 of HydroUQ app was released September 2024. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked in blue in the following list of features.)

    Structural Information Model

    Applications used to specify/select the structural model to be used in the analysis.

    @@ -224,7 +224,7 @@

    Structural Information Model[<- renaming from Multimodel]

    +

  • Multiple models: selecting multiple structural information models

    • diff --git a/docs/common/user_manual/releases/eePlans.html b/docs/common/user_manual/releases/eePlans.html index b7bbdce4..660368fb 100644 --- a/docs/common/user_manual/releases/eePlans.html +++ b/docs/common/user_manual/releases/eePlans.html @@ -16,7 +16,7 @@ - + @@ -213,15 +213,7 @@

    Release Plans

    -

    There are not any new releases planned for HydroUQ app. The development plans may change depending on feedback from the community. If you have any suggestions, we encourage you to contribute and contact us through the SimCenter Forum.

    -
    -

    September 2024

    -
    -
      -

    1. Domain Reduction Method to incorporate physics-based ground motion simulation output (e.g., output from SW4, SCEC BP) into the workflow. (Sep 2024)

      2. -
    -
    -
    +

    The development plans may change depending on feedback from the community. If you have any suggestions, we encourage you to contribute and contact us through the SimCenter Forum.

    diff --git a/docs/common/user_manual/releases/eeReleaseNotes.html b/docs/common/user_manual/releases/eeReleaseNotes.html index 5e20989e..9d63769b 100644 --- a/docs/common/user_manual/releases/eeReleaseNotes.html +++ b/docs/common/user_manual/releases/eeReleaseNotes.html @@ -16,7 +16,7 @@ - + @@ -213,8 +213,35 @@

    Release Notes

    -
    -

    Version 3.5.0 (Current)

    +
    +

    Version 4.1.0

    +

    Release date: Sept. 2024

    +

    Highlights

    +
      +

    1. Domain Reduction Method option added in tools to create events for buildings given large physics- based simulations.

      2. +

    2. ShakerMaker option added to tool to perform earthquake rupture simulations.

      3. +

    3. OpenSees@DesignSafe option added in tools to allow users to run OpenSees, OpenSeesMP, OpenSeesSP, and OpenSeesPy simulations utilizing TACC HPC resources from their desktop.

      4. +
    +
    +
    +

    Version 4.0.0

    +

    Release date: Aug. 2024

    +

    Highlights

    +
      +

    1. A needed release for changes required to interact with DesignSafe and new TapisV3 interface.

      2. +

    2. Due to AI generated spam on message board, users now directed to post questions using github discussions.

      3. +
    +
    +
    +

    Version 3.6.0

    +

    Release date: June. 2024

    +

    Highlights

    +
      +

    1. Added Option to allow differenet events in multi-model and multi-fidelity simulations

      2. +
    +
    + diff --git a/docs/common/user_manual/releases/hydroCapabilities.html b/docs/common/user_manual/releases/hydroCapabilities.html index 2141fc76..b546ae09 100644 --- a/docs/common/user_manual/releases/hydroCapabilities.html +++ b/docs/common/user_manual/releases/hydroCapabilities.html @@ -16,7 +16,7 @@ - + @@ -224,7 +224,7 @@

    5. Capabilities

    -

    Version 3.1.0 of the HydroUQ app was released on April 1st, 2024. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked blue in the following list of features.)

    +

    Version 4.0.0 of the HydroUQ app was released on April 1st, 2024. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked blue in the following list of features.)

    1. Water Event Selection: Users are provided with multiple paths for water borne hazard generation:

        @@ -346,16 +346,6 @@

        5.3. EVT (Event Selection)Celeris` (Coming Soon)` 3

        -
        -
          -

        1. Boussinesq wave solver

          2. -

        2. Nonlinear shallow-water solver

          3. -

        3. WebGPU Accelerated

          4. -

        4. Available for running through integrated browser (no installation required)

          5. -
        -
        -

    @@ -364,7 +354,6 @@

    5.3. EVT (Event Selection)Note

    1 ClaymoreUW MPM numerical method currently only available as a standalone tool in the Tools header-ribbon. Soon to be introduced into the full workflow.

    2 GeoClaw functionality from HydroUQ v1.0 is partially deprecated in the current version. It is to be fully reintroduced in the near future.

    -

    3 Celeris is a new addition to the suite of numerical methods available in HydroUQ. It is currently in beta development and will be released soon.

    @@ -523,7 +512,7 @@

    5.7. RES (Summary and Visualization of U

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/releases/hydroPlans.html b/docs/common/user_manual/releases/hydroPlans.html index 41c55f37..de165d09 100644 --- a/docs/common/user_manual/releases/hydroPlans.html +++ b/docs/common/user_manual/releases/hydroPlans.html @@ -16,7 +16,7 @@ - + @@ -120,10 +120,6 @@
  • 7.1.1. June 2024 - December 2024
    • -
  • 7.2. Year 4 (2025) -
  • 8. Glossary
    • @@ -235,7 +231,6 @@

    7.1.1. June 2024 - December 2024

      -

    1. Digital Wave Flume II: An automatically generated CFD model for simulating water loads on an isolated building with arbitrary shape defined by an STL surface. (July 2024, WBS 1.2.5.1)

    2. Surrogate Response for Debris: surrogate models for predicting the response of a water-loaded building during debris impacts for several fluid, debris, and structural parameters. (Aug 2024, WBS 1.2.2.2)

    3. Ability to use multi-model approaches for building response simulation. (Sep 2024, WBS 1.2.1.2)

    4. Hydrodynamic database creation employing CFD simulations. (Oct 2024, WBS 1.3.5.2)

      5. @@ -245,12 +240,6 @@

      7.1.1. June 2024 - December 2024

    -
    -

    7.2. Year 4 (2025)

    -
    -

    7.2.1. January 2025 - March 2025

    -
    -
    @@ -263,7 +252,7 @@

    7.2.1. January 2025 - March 2025

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/releases/hydroReleaseNotes.html b/docs/common/user_manual/releases/hydroReleaseNotes.html index 75534bb5..0f748b2f 100644 --- a/docs/common/user_manual/releases/hydroReleaseNotes.html +++ b/docs/common/user_manual/releases/hydroReleaseNotes.html @@ -16,7 +16,7 @@ - + @@ -218,11 +218,7 @@

    Version 3.1 -Version 3.1.0 (Current)
    -
    -
    -
    -
    +Version 3.1.0 (Current)

    Release date: April 1st, 2024

    Highlights

    @@ -305,11 +301,7 @@

    Version 2.0 -Version 2.0.0
    -
    -
    -
    -
    +Version 2.0.0

    Release date: November 30th, 2023

      @@ -338,11 +330,7 @@

      Version 1.0 -Version 1.0.0
      -
      -
      -
      -
      +Version 1.0.0

      Release date: Apr 30th, 2021

      1. Supports run on DesignSafe only. Local run on the user’s desktop is not supported.

        2. @@ -435,7 +423,7 @@

        Version 1.0

        - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/releases/pbeCapabilities.html b/docs/common/user_manual/releases/pbeCapabilities.html index 63448f3a..62337fee 100644 --- a/docs/common/user_manual/releases/pbeCapabilities.html +++ b/docs/common/user_manual/releases/pbeCapabilities.html @@ -16,7 +16,7 @@ - + @@ -262,7 +262,7 @@

      Uncertainty Quantification

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/releases/pbePlans.html b/docs/common/user_manual/releases/pbePlans.html index fd83f9bd..d01af4b5 100644 --- a/docs/common/user_manual/releases/pbePlans.html +++ b/docs/common/user_manual/releases/pbePlans.html @@ -16,7 +16,7 @@ - + @@ -214,18 +214,15 @@

      Release Plans

      The following features are planned to be developed for upcoming releases of HydroUQ app. We are actively working on the features in the next release. Farther development priorities may change depending on feedback from the community. If you have any suggestions, we encourage you to contribute and contact us through the SimCenter Forum.

      -
      -

      Jun 2024

      +
      +

      Sept 2024

      +

      1. Facilitate wind damage and loss calculations by adding relevant vulnerability and loss components. The building-level components from the Hazus Hurricane Methodology will be complemented by components from recent research that supports higher resolution analyses. (1.3.5.1)

      -
      -
      -

      Sept 2024

      -
      -
        +

        1. Integrate additional functional recovery simulation engines, including the ATC 138 methodology and TREADS. This will enable benchmarking and further development of these methods

        2. Automatic access to physics-based ground motion simulation results (1.1.1.3)

        @@ -257,7 +254,7 @@

        Dec 2024

        - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/releases/pbeReleaseNotes.html b/docs/common/user_manual/releases/pbeReleaseNotes.html index 1fe83060..ebd90f88 100644 --- a/docs/common/user_manual/releases/pbeReleaseNotes.html +++ b/docs/common/user_manual/releases/pbeReleaseNotes.html @@ -16,7 +16,7 @@ - + @@ -218,11 +218,16 @@

      Version 3 -Version 3.4 (Current)
      -
      -
      -
      -
      +Version 3.5 (Current)
      +

      Release date: June 2024

      +

      Major updates:

      +
        +

      • Ability to include different events in multi-model and multi-fidelity simulations

        • +
      +
      +
      + +Version 3.4

      Release date: March 2024

      Major updates:

      -

      Users are welcome to contact us on the Message Board for new feature requests.

      +

      Users are welcome to contact us on the github discussion page for new feature requests.

      @@ -523,7 +496,7 @@

      Version 1

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/releases/quoCapabilities.html b/docs/common/user_manual/releases/quoCapabilities.html index 1cf101c4..b0f73506 100644 --- a/docs/common/user_manual/releases/quoCapabilities.html +++ b/docs/common/user_manual/releases/quoCapabilities.html @@ -16,7 +16,7 @@ - + @@ -213,7 +213,7 @@

      Capabilities

      -

      Version 3.1.0 of the HydroUQ app was released on December 29, 2023. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked blue in the following list of features.)

      +

      Version 4.0.0 of the HydroUQ app was released on December 29, 2023. The following lists the functionality available in this current version. (Note: New features and fixes in this release are marked blue in the following list of features.)

      UQ (Uncertainty Quantification and Optimization Options)

        @@ -477,7 +477,7 @@

        RES (Summary and Visualization of UQ Analysis Results)

        - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/releases/quoPlans.html b/docs/common/user_manual/releases/quoPlans.html index 5c5481b1..77234ff8 100644 --- a/docs/common/user_manual/releases/quoPlans.html +++ b/docs/common/user_manual/releases/quoPlans.html @@ -16,7 +16,7 @@ - + @@ -241,7 +241,7 @@

      October 2024

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/releases/quoReleaseNotes.html b/docs/common/user_manual/releases/quoReleaseNotes.html index fbe017ca..6d76e4a4 100644 --- a/docs/common/user_manual/releases/quoReleaseNotes.html +++ b/docs/common/user_manual/releases/quoReleaseNotes.html @@ -16,7 +16,7 @@ - + @@ -212,7 +212,24 @@
      -

      Release Notes

      +

      Release Notes

      +
      +

      Major Version 4

      +
      +
      + +Version 4.0 (Current)
      +

      Release date: Aug. 2024

      +
      +
      Highlights
        +

      1. A needed release for changes required to interact with DesignSafe and new TapisV3 interface.

        2. +

      2. Due to AI generated spam on message board, users now directed to post questions using github discussion page instead of SimCenter Forum.

        3. +
      +
      +
      +
      +
      +

      Major Version 3

      @@ -222,11 +239,7 @@

      Major Version 3 -Version 3.5 (Current)
      -
      -
      -
      -
      +Version 3.5

      Release date: December. 2023

      Highlights
        @@ -237,11 +250,7 @@

        Major Version 3 -Version 3.4
        -
        -
        -
        -
        +Version 3.4

        Release date: October. 2023

        Highlights
          @@ -252,11 +261,7 @@

          Major Version 3 -Version 3.3
          -
          -
          -
          -
          +Version 3.3

          Release date: March. 2023

          Highlights
            @@ -270,11 +275,7 @@

            Major Version 3 -Version 3.2
            -
            -
            -
            -
            +Version 3.2

            Release date: September. 2022

            Highlights
              @@ -298,11 +299,7 @@

              Major Version 3 -Version 3.1
              -
              -
              -
              -
              +Version 3.1

              Release date: June. 2022

              Highlights

              @@ -317,11 +314,7 @@

              Major Version 3 -Version 3.0
              -
              -
              -
              -
              +Version 3.0

              Release date: March. 2022

              Highlights

              @@ -343,11 +336,7 @@

              Major Version 2 -Version 2.4.1
              -
              -
              -
              -
              +Version 2.4.1

              Release date: Dec. 2021

              Highlights

              @@ -363,11 +352,7 @@

              Major Version 2 -Version 2.4.0
              -
              -
              -
              -
              +Version 2.4.0

              Release date: Oct. 2021

              Highlights

              @@ -384,11 +369,7 @@

              Major Version 2 -Version 2.3
              -
              -
              -
              -
              +Version 2.3

              Release date: May 2021

              Highlights

              @@ -402,11 +383,7 @@

              Major Version 2 -Version 2.2
              -
              -
              -
              -
              +Version 2.2

              Release date: Oct. 2020

              Highlights

              @@ -421,11 +398,7 @@

              Major Version 2 -Version 2.0
              -
              -
              -
              -
              +Version 2.0

              Release date: Sept. 2019

              Highlights

              @@ -451,7 +424,7 @@

              Major Version 2

              - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

              diff --git a/docs/common/user_manual/releases/r2dCapabilities.html b/docs/common/user_manual/releases/r2dCapabilities.html index 668d68df..240aa966 100644 --- a/docs/common/user_manual/releases/r2dCapabilities.html +++ b/docs/common/user_manual/releases/r2dCapabilities.html @@ -16,7 +16,7 @@ - + @@ -213,7 +213,7 @@

              Capabilities

              -

              Version 3.1.0 of HydroUQ app was released in April 2024, introducing significant updates and enhancements. This document outlines the functionalities available in the current version, highlighting new features and improvements in blue.

              +

              Version 4.0.0 of HydroUQ app was released in April 2024, introducing significant updates and enhancements. This document outlines the functionalities available in the current version, highlighting new features and improvements in blue.

              Major updates from Version 4.0 are adding liquefaction-induced ground deformation estimation in the regional earthquake event generation tool, refactored regional inventory generation tool BRAILS, and upgraded damage and loss engine Pelicun.

              Release date: April, 2024

                @@ -230,7 +230,7 @@

              1. Asset Types:

                -

              Additional Tools

                -

              1. Empty Domain CFD Simulation: +

              2. Empty Domain CFD Simulation: Capability to perform empty domain simulation to characterize Atmospheric Boundary Layer (ABL) flows using large-eddy simulation (LES). This feature uses the Turbulence Inflow Tool (TInF) tool for calibrating ABL flows for a subsequent wind load evaluation study.

                3. +

              3. Isolated Building CFD Simulation: +Added a functionality to perform CFD-based wind load simulation on isolated building as a stand-alone workflow tool. This tool uses the user’s local machine for performing pre-processing and run the actual CFD simulation on DesignSafe.

              @@ -330,7 +341,7 @@

              Additional Tools

              - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

              diff --git a/docs/common/user_manual/releases/wePlans.html b/docs/common/user_manual/releases/wePlans.html index 9a82a3dc..c8d6338e 100644 --- a/docs/common/user_manual/releases/wePlans.html +++ b/docs/common/user_manual/releases/wePlans.html @@ -16,7 +16,7 @@ - + @@ -214,23 +214,23 @@

              Release Plans

              The following features are intended to be included in HydroUQ app in upcoming releases. These may change, depending on feedback and changing priorities, though the ones closest out are things we are actively working and will be delivered. If you have any suggestions or wish to contribute, please contact us through the SimCenter Forum.

              -
              -

              May 2024

              +
              +

              November 2024

                -

              1. Digital Wind Tunnel (1.2.5.2) - CFD models for a complex-shaped building with explicitly modeled surrounding buildings.

                2. -

              2. Surrogate support for regional assessment (1.3.6.1) - Extend surrogates developed in EE-UQ that can be utilized in R2D for wind hazard simulation.

                3. +

              3. Surrogate support for regional assessment (1.3.6.1) - Extend surrogates developed in WE-UQ that can be utilized in R2D for wind hazard simulation.

                4. +

              4. Multi-scale computational fluid dynamics framework for wind hazards.

              -
              -

              Sept 2024

              +
              +

              December 2024

              1. Aerodynamic Database (1.1.1.4) - Integrate an aerodynamic database integrating CFD simulation and experimental measurements.

              2. Digital Wind Tunnel (1.2.5.2) - Customization of the Digital Wind Tunnel models for low-rise buildings with additional application examples.

                3. -

              3. Ability to save & utilize surrogate models using advanced Surrogate-Modeling algorithms (1.2.2.2)

                4. +

              4. Ability to save and utilize surrogate models using advanced Surrogate-Modeling algorithms (1.2.2.2)

              5. Reduced order surrogates modeling for CFD simulations (1.2.2.3)

              6. Regional-scale CFD simulation integration with R2D for high-resolution damage and loss assessment of wind storms (1.2.2.3)

              @@ -253,7 +253,7 @@

              Sept 2024

              - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

              diff --git a/docs/common/user_manual/releases/weReleaseNotes.html b/docs/common/user_manual/releases/weReleaseNotes.html index 452683eb..add1a9aa 100644 --- a/docs/common/user_manual/releases/weReleaseNotes.html +++ b/docs/common/user_manual/releases/weReleaseNotes.html @@ -16,7 +16,7 @@ - + @@ -213,12 +213,43 @@

              Release Notes

              -
              -

              Version 3.3 (Current)

              +
              +

              Version 4.1 (Current)

              +

              Release date: Sept. 2024

              +

              Highlights

              +
                +

              1. Implemented new functionality to visualize and export overall/pressure loads on building for performance based wind engineering analysis.

                2. +

              2. New capability to surrogate structural responses and use the surrogate model in the workflow.

                3. +

              3. Added numerical example for simulating wind loads on a building with surroundings assuming a idealized topology.

                4. +

              4. Minor bug fixes to pre-/post-processing of the CFD-based events.

                5. +
              +
              +
              +

              Version 4.0

              +

              Release date: Aug. 2024

              +

              Highlights

              +
                +

              1. Added CFD functionality to simulate wind loads on isolated buildings without running the entire workflow in WE-UQ

                2. +

              2. Major changes required for interfacing with DesignSafe the newly released Version 3 of Tapis. Updated major version to reflect preferences needed for users to submit jobs to TACC HPC resources.

                3. +
              +
              +
              +

              Version 3.4

              +

              Release date: May. 2024

              +

              Highlights

              +
                +

              1. Simulate wind loading on structures surrounded by an array of buildings. Surrounding buildings heights may be randomized or user-defined.

                2. +

              2. Minor bug fixes in the tool.

                3. +
              +
              +
              +

              Version 3.3

              Release date: Apr. 2024

              Highlights

                +

              1. Simulate wind loading on structures surrounded by an array of buildings. Surrounding buildings heights may be randomized or user-defined.

              2. A new wind load generator module: wind-tunnel informed stochastic wind pressure generator

                3. +

              3. Empty domain simulation tool.

              diff --git a/docs/common/user_manual/troubleshooting/desktop/troubleshooting.html b/docs/common/user_manual/troubleshooting/desktop/troubleshooting.html index 70fe3e19..64b287ff 100644 --- a/docs/common/user_manual/troubleshooting/desktop/troubleshooting.html +++ b/docs/common/user_manual/troubleshooting/desktop/troubleshooting.html @@ -16,7 +16,7 @@ - + @@ -237,7 +237,7 @@

              - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

              diff --git a/docs/common/user_manual/troubleshooting/desktop/troubleshootingRunning.html b/docs/common/user_manual/troubleshooting/desktop/troubleshootingRunning.html index 970a2a98..3f862a22 100644 --- a/docs/common/user_manual/troubleshooting/desktop/troubleshootingRunning.html +++ b/docs/common/user_manual/troubleshooting/desktop/troubleshootingRunning.html @@ -16,7 +16,7 @@ - + @@ -225,7 +225,7 @@

              1. A temporary directory, tmp.SimCenter, is created in the working directory, followed by a templatedir within it.

              2. The UI processes all input panels, and workflow applications transfer necessary files to the templatedir.

                3. -

              3. A Python script, specific to the simulation type (rWHALE.py for regional simulations, sWHALE.py for individual assessments), is executed from templatedir. rWHALE serves as a wrapper, invoking sWHALE for each asset in regional assessments.

                4. +

              4. A Python script, specific to the simulation type (rWHALE.py for regional simulations, sWHALE.py for individual assessments), is executed from the templatedir. rWHALE serves as a wrapper, invoking sWHALE for each asset in regional assessments.

              5. For structural response simulations, uncertainty quantification is managed by the chosen UQ Engine (e.g., Dakota), which generates an input file (e.g., dakota.in) placed in tmp.SimCenter.

              6. The UQ engine runs the response simulation using the earlier created input file.

              7. For each structural response realization, the UQ engine creates a separate workdir folder within tmp.SimCenter.

                8. @@ -241,13 +241,24 @@

              8. No dakota.err file and no dakota.in file: the Python script in templatedir failed to create the files required to start the UQ Engine. Take a look at the workflow log file in the tmp.SimCenter folder to see if it shows any errors. These errors typically point to an incorrect setting in your input file. If no workflow log file exists, the Python script managing the workflow failed to start. This is typically caused by an issue with your Python installation. Make sure you’ve followed the instructions in the Installation guide and set up your Python environment properly.

              9. No dakota.err but dakota.in exists: Even though the required files are available, the UQ Engine failed to start. If Dakota was selected as the UQ Engine, check the Dakota installation. Also, make sure you’ve followed the instructions in the Installation guide and set up your Python environment properly.

              10. dakota.err file exists but it is empty: This means that the UQ Engine started successfully, but there was a problem during the simulation. Go to one of the workdir folders that contain individual realizations. You can run that simulation using the workflow driver file. Run the driver file from the command line to see what errors are generated during the simulation. These errors are typically related to the event or structural model description.

                11. -

              11. dakota.err file exists: Open the file and see what the error is. For example, if it says Error: at least one variable must be specified. This means no random variables have been specified. You have only one deterministic event, or you have not specified any random variables for the analysis. Do not hesitate to reach out to the developers through the Message Board if you do not understand the error messages in this file.

                12. +

              12. dakota.err file exists: Open the file and see what the error is. For example, if it says Error: at least one variable must be specified. This means no random variables have been specified. You have only one deterministic event, or you have not specified any random variables for the analysis. Do not hesitate to reach out to the developers through the github discussion page if you do not understand the error messages in this file.

            1. You ran remotely at DesignSafe and no dakota.out files came back: Go to your data depot folder at DesignSafe using your browser. Go to archive/jobs and use the job number from the table that pops up when you ask to get the job results from DesignSafe. Study both the .err and .out files in that directory for information on what went wrong.

            2. No results and you used the Site Response to create the event. You must run a simulated event in the Site Response Widget before you can submit a job to run.

              3. +

            3. Don’t Like Default Screen Layout. There are configuarion you can do for startup. In the directory in which the executable exists you can place a config.json file. At present the options are limited: You can set screen size of the application to be full screen, and you can set and change the size of the output window. A sample config .json file:

            -

            For unresolved issues, please seek assistance on the Message Board.

            +
            {
+   "screenSize":"fullScreen",
+   "outputLocation":{"position":"right","numPixels":500}
+}
+
            +
            +
            +

            Note

            +

            You can also start the application from the terminal and pass config options. These options overwrite any existing.

            +
            +

            For unresolved issues, please seek assistance on the github discussion page.

            @@ -260,7 +271,7 @@

            - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

            diff --git a/docs/common/user_manual/troubleshooting/desktop/troubleshootingStartup.html b/docs/common/user_manual/troubleshooting/desktop/troubleshootingStartup.html index 88974c1c..308ee5dc 100644 --- a/docs/common/user_manual/troubleshooting/desktop/troubleshootingStartup.html +++ b/docs/common/user_manual/troubleshooting/desktop/troubleshootingStartup.html @@ -16,7 +16,7 @@ - + @@ -239,7 +239,7 @@

            - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

            diff --git a/docs/common/user_manual/usage/desktop/Configuring_CustomUQ.html b/docs/common/user_manual/usage/desktop/Configuring_CustomUQ.html index 97322e86..bf341ba8 100644 --- a/docs/common/user_manual/usage/desktop/Configuring_CustomUQ.html +++ b/docs/common/user_manual/usage/desktop/Configuring_CustomUQ.html @@ -16,7 +16,7 @@ - + @@ -366,7 +366,7 @@

            Adding UQ Engine to Customized Backend

            - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

            diff --git a/docs/common/user_manual/usage/desktop/DakotaBayesianCalibration.html b/docs/common/user_manual/usage/desktop/DakotaBayesianCalibration.html index d2c3ed0e..85d98ff2 100644 --- a/docs/common/user_manual/usage/desktop/DakotaBayesianCalibration.html +++ b/docs/common/user_manual/usage/desktop/DakotaBayesianCalibration.html @@ -16,7 +16,7 @@ - + @@ -263,7 +263,7 @@

            DREAM

            - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

            diff --git a/docs/common/user_manual/usage/desktop/DakotaDeterministicCalibration.html b/docs/common/user_manual/usage/desktop/DakotaDeterministicCalibration.html index 89763e9b..81d1fa4a 100644 --- a/docs/common/user_manual/usage/desktop/DakotaDeterministicCalibration.html +++ b/docs/common/user_manual/usage/desktop/DakotaDeterministicCalibration.html @@ -16,7 +16,7 @@ - + @@ -286,7 +286,7 @@

            NL2SOL

            - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

          diff --git a/docs/common/user_manual/usage/desktop/DakotaGradientFreeOptimization.html b/docs/common/user_manual/usage/desktop/DakotaGradientFreeOptimization.html index 3ee05495..b263df8f 100644 --- a/docs/common/user_manual/usage/desktop/DakotaGradientFreeOptimization.html +++ b/docs/common/user_manual/usage/desktop/DakotaGradientFreeOptimization.html @@ -16,7 +16,7 @@ - + @@ -253,7 +253,7 @@

          Pattern Search

          - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

          diff --git a/docs/common/user_manual/usage/desktop/DakotaReliability.html b/docs/common/user_manual/usage/desktop/DakotaReliability.html index 59558d3b..c2291613 100644 --- a/docs/common/user_manual/usage/desktop/DakotaReliability.html +++ b/docs/common/user_manual/usage/desktop/DakotaReliability.html @@ -16,7 +16,7 @@ - + @@ -340,7 +340,7 @@

          Importance Sampling (IS)

          - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

        diff --git a/docs/common/user_manual/usage/desktop/DakotaSampling.html b/docs/common/user_manual/usage/desktop/DakotaSampling.html index 9d74fdce..41b11f53 100644 --- a/docs/common/user_manual/usage/desktop/DakotaSampling.html +++ b/docs/common/user_manual/usage/desktop/DakotaSampling.html @@ -16,7 +16,7 @@ - + @@ -249,7 +249,7 @@

      1. Gaussian Process Regression (GPR)

      2. Polynomial Chaos Expansion (PCE)

      -

      Depending on the option selected, the user must specify the appropriate input parameters. For instance, for MCS, the number of samples specifies the number of simulations to be performed, and providing a seed value for the pseudo-random number generator will produce the same sequence of random numbers allowing the user to reproduce the sampling results multiple times. The user selects the sampling method from the dropdown Dakota Method Category menu. Additional information regarding sampling techniques offered in Dakota can be found here.

      +

      Depending on the option selected, the user must specify the appropriate input parameters. For instance, for MCS, the number of samples specifies the number of simulations to be performed, and providing a seed value for the pseudo-random number generator will produce the same sequence of random numbers allowing the user to reproduce the sampling results multiple times. The user selects the sampling method from the dropdown Dakota Method Category menu. Additional information regarding sampling techniques offered in Dakota can be found here.

      Monte Carlo Sampling (MCS)

      MCS is among the most robust and universally applicable sampling methods. Moreover, the convergence rate of MCS methods is independent of the problem dimensionality, albeit the convergence rate of such MCS methods is relatively slow at \(N^{-1/2}\). In MCS, a sample drawn at any step is independent of all previous samples.

      @@ -304,7 +304,7 @@

      Polynomial Chaos Expansion (PCE)

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/DakotaSensitivity.html b/docs/common/user_manual/usage/desktop/DakotaSensitivity.html index ef7f0d8c..f9d6a329 100644 --- a/docs/common/user_manual/usage/desktop/DakotaSensitivity.html +++ b/docs/common/user_manual/usage/desktop/DakotaSensitivity.html @@ -16,7 +16,7 @@ - + @@ -286,7 +286,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/FEM.html b/docs/common/user_manual/usage/desktop/FEM.html index eb36cca5..a84dd7b4 100644 --- a/docs/common/user_manual/usage/desktop/FEM.html +++ b/docs/common/user_manual/usage/desktop/FEM.html @@ -16,7 +16,7 @@ - + @@ -341,7 +341,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/GI.html b/docs/common/user_manual/usage/desktop/GI.html index 760c6f3d..a0e0f1ae 100644 --- a/docs/common/user_manual/usage/desktop/GI.html +++ b/docs/common/user_manual/usage/desktop/GI.html @@ -16,7 +16,7 @@ - + @@ -250,7 +250,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/RV.html b/docs/common/user_manual/usage/desktop/RV.html index bbfcaaf7..1769da22 100644 --- a/docs/common/user_manual/usage/desktop/RV.html +++ b/docs/common/user_manual/usage/desktop/RV.html @@ -16,7 +16,7 @@ - + @@ -413,7 +413,7 @@

      2.7.1.2. SimCenterUQ Engine

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/SIM.html b/docs/common/user_manual/usage/desktop/SIM.html index 2814810e..926edc98 100644 --- a/docs/common/user_manual/usage/desktop/SIM.html +++ b/docs/common/user_manual/usage/desktop/SIM.html @@ -16,7 +16,7 @@ - + @@ -839,7 +839,7 @@

      2.3.6. MDOF-LU Building Model

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/SimCenterUQ.html b/docs/common/user_manual/usage/desktop/SimCenterUQ.html index bb42de30..78dc080f 100644 --- a/docs/common/user_manual/usage/desktop/SimCenterUQ.html +++ b/docs/common/user_manual/usage/desktop/SimCenterUQ.html @@ -16,7 +16,7 @@ - + @@ -234,7 +234,7 @@

      SimCenter UQ Engine

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/SimCenterUQMF.html b/docs/common/user_manual/usage/desktop/SimCenterUQMF.html index 8c2c91a9..253e3f71 100644 --- a/docs/common/user_manual/usage/desktop/SimCenterUQMF.html +++ b/docs/common/user_manual/usage/desktop/SimCenterUQMF.html @@ -16,7 +16,7 @@ - + @@ -251,7 +251,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/SimCenterUQPLoM.html b/docs/common/user_manual/usage/desktop/SimCenterUQPLoM.html index 3e1770f3..be06bf10 100644 --- a/docs/common/user_manual/usage/desktop/SimCenterUQPLoM.html +++ b/docs/common/user_manual/usage/desktop/SimCenterUQPLoM.html @@ -16,7 +16,7 @@ - + @@ -385,7 +385,7 @@

      Results and Postprocess

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/SimCenterUQSampling.html b/docs/common/user_manual/usage/desktop/SimCenterUQSampling.html index 822d1f1b..1c5516e8 100644 --- a/docs/common/user_manual/usage/desktop/SimCenterUQSampling.html +++ b/docs/common/user_manual/usage/desktop/SimCenterUQSampling.html @@ -16,7 +16,7 @@ - + @@ -296,7 +296,7 @@

      Sampling from dataset

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/SimCenterUQSensitivity.html b/docs/common/user_manual/usage/desktop/SimCenterUQSensitivity.html index 05ec542b..fbb555ed 100644 --- a/docs/common/user_manual/usage/desktop/SimCenterUQSensitivity.html +++ b/docs/common/user_manual/usage/desktop/SimCenterUQSensitivity.html @@ -16,7 +16,7 @@ - + @@ -376,7 +376,7 @@

      Results Display

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/SimCenterUQSurrogate.html b/docs/common/user_manual/usage/desktop/SimCenterUQSurrogate.html index ffe28ae9..5d659ddc 100644 --- a/docs/common/user_manual/usage/desktop/SimCenterUQSurrogate.html +++ b/docs/common/user_manual/usage/desktop/SimCenterUQSurrogate.html @@ -16,7 +16,7 @@ - + @@ -425,7 +425,7 @@

      Saving Options

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/usage/desktop/UCSD_UQ_Hierarchical.html b/docs/common/user_manual/usage/desktop/UCSD_UQ_Hierarchical.html index 0f31fc34..9941cf6c 100644 --- a/docs/common/user_manual/usage/desktop/UCSD_UQ_Hierarchical.html +++ b/docs/common/user_manual/usage/desktop/UCSD_UQ_Hierarchical.html @@ -16,7 +16,7 @@ - + @@ -255,7 +255,7 @@

    Usage

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/usage/desktop/UCSD_UQ_TMCMC.html b/docs/common/user_manual/usage/desktop/UCSD_UQ_TMCMC.html index dc620c89..be8414c8 100644 --- a/docs/common/user_manual/usage/desktop/UCSD_UQ_TMCMC.html +++ b/docs/common/user_manual/usage/desktop/UCSD_UQ_TMCMC.html @@ -16,7 +16,7 @@ - + @@ -361,7 +361,7 @@

    Additional calibration parameters

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/usage/desktop/UQ.html b/docs/common/user_manual/usage/desktop/UQ.html index 352294af..fe62ed32 100644 --- a/docs/common/user_manual/usage/desktop/UQ.html +++ b/docs/common/user_manual/usage/desktop/UQ.html @@ -16,7 +16,7 @@ - + @@ -291,7 +291,7 @@

    2.1.3. SimCenter UQ Engine

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/usage/desktop/hydro/BodiesMPM.html b/docs/common/user_manual/usage/desktop/hydro/BodiesMPM.html index d79f3a6f..71b441ca 100644 --- a/docs/common/user_manual/usage/desktop/hydro/BodiesMPM.html +++ b/docs/common/user_manual/usage/desktop/hydro/BodiesMPM.html @@ -16,7 +16,7 @@ - + @@ -256,10 +256,10 @@

    1. Isotropic Fluid with Viscous Shear Stress / J-Fluid: This is used to define a basic Newtonian fluid. The material properties include density, bulk modulus, derivative of the bulk modulus with respect to pressure, and dynamic viscosity.

    2. Fixed-Corotated / Neo-Hookean: This is used to define solid hyperelastic material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, and density.

      3. -

    3. Drucker-Prager: This is used to define solid / granular material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, density, and the Drucker-Prager parameters.

      4. -

    4. Non-Associative Cam-Clay: This is used to define solid / granular material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, density, and the Non-Associative Cam-Clay parameters.

      5. +

    5. Drucker-Prager: This is used to define solid/granular material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, density, and the Drucker-Prager parameters.

      6. +

    6. Non-Associative Cam-Clay: This is used to define solid/granular material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, density, and the Non-Associative Cam-Clay parameters.

    -

    Material properties are defined in the Material tab and are specific to the chosen constitutive law / material model. The material properties include:

    +

    Material properties are defined in the Material tab and are specific to the chosen constitutive law/material model. The material properties include:

    1. Density: This refers to the density of the material. This is defined in terms of the mass per unit volume. The units are generally in kg/m3.

    2. Young’s Modulus: This refers to the stiffness of the material. This is defined in terms of the force per unit area. The units are generally in Pa.

      3. @@ -296,7 +296,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/hydro/BoundariesMPM.html b/docs/common/user_manual/usage/desktop/hydro/BoundariesMPM.html index 8787a0fe..2947eb34 100644 --- a/docs/common/user_manual/usage/desktop/hydro/BoundariesMPM.html +++ b/docs/common/user_manual/usage/desktop/hydro/BoundariesMPM.html @@ -16,7 +16,7 @@ - + @@ -231,7 +231,7 @@

      2.4.3.3. Boundaries

      -

      There are four aspects related to the definition of boundaries, namely geometry of the ocean floor or wave flume, buildings or specimens, floating bodies, and shallow water to CFD interface.

      +

      There are four aspects related to the definition of boundaries, namely geometry of the ocean floor or wave flume, buildings or specimens, floating bodies, and shallow water to the CFD interface.

      @@ -244,7 +244,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/hydro/Boundary.html b/docs/common/user_manual/usage/desktop/hydro/Boundary.html index 6e07174b..fe0edf0f 100644 --- a/docs/common/user_manual/usage/desktop/hydro/Boundary.html +++ b/docs/common/user_manual/usage/desktop/hydro/Boundary.html @@ -16,7 +16,7 @@ - + @@ -226,7 +226,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/hydro/DakotaR.html b/docs/common/user_manual/usage/desktop/hydro/DakotaR.html index 674cb67d..ddbccb51 100644 --- a/docs/common/user_manual/usage/desktop/hydro/DakotaR.html +++ b/docs/common/user_manual/usage/desktop/hydro/DakotaR.html @@ -16,7 +16,7 @@ - + @@ -241,7 +241,7 @@

      Local Reliability MethodsWarning

      Only a single quantity of interest may be specified when using MPP

    -

    The second local reliability method available is the Mean Value method (also known as MVFOSM). It is the simplest and least-expensive reliability method because it estimates the response means, response standard deviations, and all response probability levels from a single evaluation of the response functions and their gradients at the uncertain variable means. This approximation can have acceptable accuracy when the response functions are nearly linear. Their distributions are approximately Gaussian, but can have poor accuracy in other situations.

    +

    The second local reliability method available is the Mean Value method (also known as MVFOSM). It is the simplest and least-expensive reliability method because it estimates the response means, response standard deviations and all response probability levels from a single evaluation of the response functions and their gradients at the uncertain variable means. This approximation can have acceptable accuracy when the response functions are nearly linear. Their distributions are approximately Gaussian, but can have poor accuracy in other situations.

    As shown in the figure below, the user selects either to use response levels or probability levels. The user then inputs the levels.

     diff --git a/docs/common/user_manual/usage/desktop/hydro/DakotaSa.html b/docs/common/user_manual/usage/desktop/hydro/DakotaSa.html index 7b61d437..8a4eb6df 100644 --- a/docs/common/user_manual/usage/desktop/hydro/DakotaSa.html +++ b/docs/common/user_manual/usage/desktop/hydro/DakotaSa.html @@ -16,7 +16,7 @@ - + @@ -214,7 +214,7 @@

    Forward Propagation

    -

    The forward propagation analysis provides a probabilistic understanding of output variables by producing sample realizations and statistical moments (mean, standard deviation, skewness, and kurtosis). Currently, five sampling methods are available: Monte Carlo Sampling (MCS), Latin Hypercube Sampling (LHS), Importance Sampling (IS), and sampling-based on surrogate models, including Gaussian Process Regression (GPR) and Polynomial Chaos Expansion (PCE). Depending on the option selected, the user must specify the appropriate input parameters. For instance, for MCS, the number of samples specifies the number of simulations to be performed. Providing a random seed allows the user to reproduce the sampling results multiple times. The user selects the sampling method from the dropdown Methods menu. Additional information regarding sampling techniques offered in Dakota can be found here.

    +

    The forward propagation analysis provides a probabilistic understanding of output variables by producing sample realizations and statistical moments (mean, standard deviation, skewness, and kurtosis). Currently, five sampling methods are available: Monte Carlo Sampling (MCS), Latin Hypercube Sampling (LHS), Importance Sampling (IS), and sampling based on surrogate models, including Gaussian Process Regression (GPR) and Polynomial Chaos Expansion (PCE). Depending on the option selected, the user must specify the appropriate input parameters. For instance, for MCS, the number of samples specifies the number of simulations to be performed. Providing a random seed allows the user to reproduce the sampling results multiple times. The user selects the sampling method from the dropdown Methods menu. Additional information regarding sampling techniques offered in Dakota can be found here.

    Monte Carlo Sampling (MCS)

    MCS is among the most robust and universally applicable sampling methods. Moreover, the convergence rate of MCS methods is independent of the problem dimensionality, albeit the convergence rate of such MCS methods is relatively slow at \(N^{-1/2}\). In MCS, a sample drawn at any step is independent of all previous samples.

    @@ -235,7 +235,7 @@

    Latin Hypercube Sampling (LHS)

    Importance Sampling (IS)

    -

    For problems where one is interested in the rare events rather than the whole distribution of output, such as earthquake or storm surge events, conventional sampling methods may require a considerable number of simulations to obtain an accurate estimation of tail distribution. For such problems, importance sampling (IS) bypasses conventional sampling methods (MCS or LHS). An alternative sampling distribution is introduced around the tail part of the original distribution so that the generated samples have a better resolution at the domain of interest.

    +

    For problems where one is interested in rare events rather than the whole distribution of output, such as earthquake or storm surge events, conventional sampling methods may require a considerable number of simulations to obtain an accurate estimation of tail distribution. For such problems, importance sampling (IS) bypasses conventional sampling methods (MCS or LHS). An alternative sampling distribution is introduced around the tail part of the original distribution so that the generated samples have a better resolution at the domain of interest.

    figIS shows the input panel for IS scheme. Like MCS and LHS, IS requires both the number of samples to be executed and the corresponding seed for generating such random samples. In addition, IS algorithm can be performed via three different approaches, as specified by the third input method:

    1. Basic Sampling: A sampling density is constructed in the failure region based on an initial LHS sampling, followed by generation of importance samples and weights and evaluation of the Cumulative Distribution Function.

      2. @@ -250,7 +250,7 @@

      Importance Sampling (IS)

      Gaussian Process Regression (GPR)

      -

      For the problems in which computationally expensive models are involved, conventional sampling schemes such as LHS and MCS can be highly time-consuming. A surrogate model can be constructed based on a fewer number of simulation runs in such a case. Then the surrogate model can be used to efficiently generate a required number of samples replacing the expensive simulations.

      +

      For the problems in which computationally expensive models are involved, conventional sampling schemes such as LHS and MCS can be highly time-consuming. A surrogate model can be constructed based on a fewer number of simulation runs in such a case. Then the surrogate model can be used to efficiently generate the required number of samples replacing the expensive simulations.

      Gaussian Process Regression (GPR), also known as Kriging, is a well-established surrogate technique that constructs an approximated response surface based on Gaussian process modeling and covariance matrix optimizations. figGPR shows the input panel for the GPR model that consists of training and sampling panels.

      diff --git a/docs/common/user_manual/usage/desktop/hydro/DakotaSe.html b/docs/common/user_manual/usage/desktop/hydro/DakotaSe.html index c458a8f9..1775534c 100644 --- a/docs/common/user_manual/usage/desktop/hydro/DakotaSe.html +++ b/docs/common/user_manual/usage/desktop/hydro/DakotaSe.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

      When the associated FEM model is computationally expensive, the user should consider that the actual number of the simulation runs is larger than the number of samples specified in the input panel. The exact number of simulation runs are NS*(2+NRV)

        -

      • NS = number of samples specified by user

        • +

      • NS = number of samples specified by the user

      • NRV = number of random variables

      @@ -268,7 +268,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/hydro/EVT.html b/docs/common/user_manual/usage/desktop/hydro/EVT.html index c6a8ecb2..57a7caf3 100644 --- a/docs/common/user_manual/usage/desktop/hydro/EVT.html +++ b/docs/common/user_manual/usage/desktop/hydro/EVT.html @@ -16,7 +16,7 @@ - + @@ -233,7 +233,7 @@

      2.4. EVT: Hydro Events

      The event panel presents the user with a drop-down menu with a list of available event applications.

      -

      Event applications are applications that, given the building and user supplied data inputs, will generate a list of events (i.e., typically time-dependent loads that represent natural disasters) for the building.

      +

      Event applications are applications that, given the building and user-supplied data inputs, will generate a list of events (i.e., typically time-dependent loads that represent natural disasters) for the building.

      The Hydro EVT is used to setup the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and CFD solver or using the CFD solver alone.

      The following options are available in the drop-down menu:

      @@ -259,8 +259,8 @@
    2. 2.4.2. Coupled Digital Twin @@ -284,7 +284,7 @@

      3. Note

      -

      * The new MPM module is only availble in the current release 3.1.0 as a standalone Tools app, though it is designed to be an EVT option. It will be fully-implemented as a workflow EVT in the next release.

      +

      * The new MPM module is only available in the current release 4.0.0 as a standalone Tools app, though it is designed to be an EVT option. It will be fully implemented as a workflow EVT in the next release.

      @@ -298,7 +298,7 @@

      - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

      diff --git a/docs/common/user_manual/usage/desktop/hydro/FEM.html b/docs/common/user_manual/usage/desktop/hydro/FEM.html index e212986a..80bdedff 100644 --- a/docs/common/user_manual/usage/desktop/hydro/FEM.html +++ b/docs/common/user_manual/usage/desktop/hydro/FEM.html @@ -16,7 +16,7 @@ - + @@ -215,7 +215,7 @@

      FEM: Finite Element Method

      The FEM tab will present users with a selection of FEM applications that will take a building model generated by the BIM application and the EVENT from the event application and perform a deterministic simulation of structural response. The default application is the OpenSees application.

      -

      Currently, there is one application, OpenSees. The current OpenSees implementation extends the standard OpenSees executable with a pre- and post-processor to take the BIM and EVENT files and use OpenSees to simulate the response and return it in an EDP file.

      +

      Currently, there is one application, OpenSees. The current OpenSees implementation extends the standard OpenSees executable with a pre-/post-processor to take the BIM and EVENT files and use OpenSees to simulate the response and return it in an EDP file.

      common/user_manual/usage/desktop/hydro/figures/OpenSeesFEM.png

      Options for OpenSees.

      @@ -226,7 +226,7 @@

    3. Solution Algorithm: The solution algorithm is the numerical algorithm used to solve the nonlinear equations at each time step/. The default is Newton Raphson; other options include ModifiedNewton, Newton -initial, BFGS, Linear.

    4. System: The system defines how the matrix equation \(Ax = b\) is stored in memory and solved. The default is the unsymmetric sparse solver Umfpack. Other options available include: profileSPD, BandSPD, BandGEM, Diagonal, SuperLU.

    5. Integration Scheme: The integration scheme specifies the time-stepping algorithm being employed to solve the transient problem (\(M \ddot{U}(t) + C \dot{U}(t) + Fs(U(t)) = P(t)\)). The integration scheme determined the coefficients in the \(A\) matrix, the meaning of the \(x\) and \(b\) vectors and how the nodal displacements, velocities, and accelerations should be updated given \(x\). The default is Newmark’s linear acceleration method (Newmark 0.5 0.25). Other Newmark methods can be employed by changing the \(\alpha\) and \(\beta\) terms, and other methods, HHT, CentralDifference, can be selected.

      6. -

    6. Convergence Test, the default is the norm of the unbalance force with a convergence tolerance of 1.0e-2 and a limit of 10 trial steps to achieve convergence. Other convergence criteria that can be chosen include NormDispIncr, EnergyIncrement, and the relative norms.

      7. +

    7. Convergence Test, the default is the norm of the unbalanced force with a convergence tolerance of 1.0e-2 and a limit of 10 trial steps to achieve convergence. Other convergence criteria that can be chosen include NormDispIncr, EnergyIncrement, and the relative norms.

    8. Damping Model: The pull-down menu defaults to Rayleigh Damping. The other option is Modal Damping. The theory behind the two is presented in Damping Options.

      1. Rayleigh Damping. With Rayleigh damping, the user must provide the damping ratio, \(\zeta\) and specify two modes from which the damping coefficients \(a_0\) and \(a_1\) will be determined. Mass proportional damping can be obtained by setting the Mode 2 option to 0, stiffness proportional damping by setting Mode 1 option to 0.

        2. @@ -239,7 +239,7 @@

      2. Analysis Script. This shall be left blank by default. Advanced users of OpenSees who have their preferred analysis script and wish to provide their own damping model can give it here. If this option is provided, the user in their script should use the variables numStep and dt.

      -

      A default transient analysis script is run with these inputs. It is built for Version 3.0.0+ of OpenSees and uses a divide and conquer algorithm to overcome convergence issues. This new algorithm does not work for every nonlinear problem. The actual analysis command that is created based on the defaults is the following:

      +

      A default transient analysis script is run with these inputs. It is built for Version 3.0.0+ of OpenSees and uses a divide-and-conquer algorithm to overcome convergence issues. This new algorithm does not work for every nonlinear problem. The actual analysis command that is created based on the defaults is the following:

      numberer RCM
 system Umfpack
 integrator Newmark 0.5 0.25
@@ -262,7 +262,7 @@
 
   
      
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      
diff --git a/docs/common/user_manual/usage/desktop/hydro/Geometry.html b/docs/common/user_manual/usage/desktop/hydro/Geometry.html
index d8c69385..80b52c0b 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Geometry.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Geometry.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -244,17 +244,13 @@
             
   
      
 
      2.4.1.2. Geometry
      
-
      There are four aspects related to the definition of geometry, namely geometry of the ocean floor or wave flume, buildings or specimens, floating bodies, and shallow water to CFD interface. This section discusses the setup of all aspects of geometry.
      
+
      There are four aspects related to the definition of geometry, namely geometry of the ocean floor or wave flume, buildings or specimens, floating bodies, and shallow water to the CFD interface. This section discusses the setup of all aspects of geometry.
      
 
      
 
      Bathymetry
      
 
      The geometry can be provided either in terms of the bathymetry of the ocean floor, an STL file, or the wave flume digital twin. The geometry definition is based on the type of Simulation type chosen in the Project Settings. The geometry definition for each of the simulation types has been outlined below.
      
 
      
 
-Shallow-water to CFD coupling
      
-
      
-
      
-
      
-
      
+Shallow-water to CFD coupling
      
 
      To couple high-fidelity CFD and with simplified shallow-water equations (SWE), you must input the bathymetry defining files you previously used in a SWE simulation.
      
 
      
 
      Tip
      
@@ -277,11 +273,7 @@ 
      Bathymetry
 
-Bathymetry
      
-
      
-
      
-
      
-
      
+Bathymetry
      
 
      Here the user needs to select the bathymetry files of the ocean floor. At present, HydroUQ can directly read the bathymetry provided in the GeoClaw format (Type 1) or the SimCenter format. For more information about the GeoClaw file format, check out Topography. Similarly, for the SimCenter formats, check out Topography: SimCenter.
      
 
      The other input is the direction of gravity. For this type of simulation, it is recommended to use -z for the gravity direction.
      
 
      
@@ -295,11 +287,7 @@ 
      Bathymetry
 
-STL file
      
-
      
-
      
-
      
-
      
+STL file
      
 
      The STL file format is pervasive in fluid simulation software, hence HydroUQ provides support for the format.
      
 
      To define a complex ocean bathymetry, you may use multiple STL files to replicate the ocean floor if they form a manifold when combined.
      
 
      Custom structures, boundaries, and other features may also be defined using  STL files. An example is shown in the HydroUQ UI below:
      
@@ -333,11 +321,7 @@ 
      Bathymetry
 
-Wave flume
      
-
      
-
      
-
      
-
      
+Wave flume
      
 
      This sections discusses the geometric definition for wave flume simulations. This is the first step in the description of a digital twin of an experimental set in said flume facilities.
      
 
      For instance, one of the inputs required to use a simulation to represent a real-world representation is the direction of gravity. For fluid simulations, it is often recommended to use -z, but -y is a common choice as well. Other parameters may entail wave-maker specifications, concrete wall roughness, the basic wave flume geometry height / width / depth, among others.
      
 
      Bathymetry, i.e. sloped panels that are often present in wave flumes to influence wave development, are important for replicating experiments digitally and so an adjustable bathymetry creator is present in HydroUQ. The wave flume geometry in particular is a critical parameter, as it determines whether a full wave flume simulation is done or a truncated one (i.e. if reduced values were chosen). Bathymetry, i.e. sloped panels that are often present in wave flumes to influence wave development, are likewise important and supported in HydroUQ.
      
@@ -383,7 +367,7 @@ 
      Shallow Water to CFD Interface../../../../../_images/swcfd_Interface.png
 
      Fig. 2.4.1.2.7 Uploading the .csv file that defines the interface
      
 
      
-
      Consider the problem description as shown in the Fig. 2.4.1.2.8. Consider an event (earthquake on a fault or low-pressure due to a hurricane) represented by the red line on the left. The shallow-water solvers are used over the Ocean domain. In order to provide a high-fidelity solution for the structural response, the shallow-water domain is further refined using 3D CFD. The yellow boxes represent the shallow water to CFD interfaces. This interface information is provided in a .csv file.
      
+
      Consider the problem description as shown in the Fig. 2.4.1.2.8. Consider an event (earthquake on a fault or low-pressure due to a hurricane) represented by the red line on the left. The shallow-water solvers are used over the Ocean domain. To provide a high-fidelity solution for the structural response, the shallow-water domain is further refined using 3D CFD. The yellow boxes represent the shallow water to CFD interfaces. This interface information is provided in a .csv file.
      
 
 
      
 
      
 
      Buildings and Scaled Specimens
      
-
      Buildings or specimens can be defined in the EVT. It is important here to note that there can be two types of buildings: (a) Building of interest for which the structural response is measured (b) Other neighboring buildings that impact the flow fields.
      
+
      Buildings or specimens can be defined in the EVT. It is important here to note that there can be two types of buildings: (a) The building of interest for which the structural response is measured (b) Other neighboring buildings that impact the flow fields.
      
 
      These can either be defined manually in a tabular format or parametrically as shown in Fig. 2.4.1.2.9.
      
 
      
 ../../../../../_images/Building.png
@@ -435,7 +419,7 @@ 
      Manual Definitionx , y , z) or latitude-longitude depending on the type of simulation chosen earlier in Project Settings. Suppose the simulation is based on shallow-water to CFD or bathymetry settings. In that case, the latitude and longitude need to be specified. Else, the position is input in terms of the coordinates.
      
+
    9. Center: This refers to the location of the building/specimen. This is defined in terms of the coordinates (x , y , z) or latitude-longitude depending on the type of simulation chosen earlier in Project Settings. Suppose the simulation is based on shallow-water to CFD or bathymetry settings. In that case, the latitude and longitude need to be specified. Otherwise, the position is input in terms of the coordinates.
      
 
      
 
      Note
      
 
      Here, the building position refers to the center of the bottom surface of the building.
@@ -449,7 +433,7 @@ 
      Manual Definition
      
 
      The parametric definition of the building is recommended for usage mainly for the flume. This is recommended for usage when all the buildings are of the same shape and size. Here, the buildings are automatically generated based on a set of parametric inputs. The building of interest is directly determined by the HydroUQ app by using the coordinate information from the GI tab and matching it with the nearest building. The set of parameters include:
      
 
        
-
      1. Number of buildings along the coast: This refers to the number of building in the direction orthogonal to the flow, i.e., between right and left interfaces or walls of the CFD domain.
        2. 
+
      2. Number of buildings along the coast: This refers to the number of buildings in the direction orthogonal to the flow, i.e., between right and left interfaces or walls of the CFD domain.
        3. 
 
      3. Number of buildings into the coast: This refers to the number of buildings in the flow direction, i.e., between entry and exit of the CFD domain.
        4. 
 
      4. Distance from coast: This refers to the distance of the first building from (0,0).
        5. 
 
      5. Distance between buildings (Side): This refers to the center-to-center distance between the buildings in the direction orthogonal to the flow.
        6. 
@@ -473,7 +457,7 @@ 
        Parametric Definition
 
        
 
        Debris and Floating Bodies
        
-
        Currently, HydroUQ  only supports floating bodies in the Material Point Method Event. This may expand to include OpenFOAM in an upcoming versions of HydroUQ app.
        
+
        Currently, HydroUQ  only supports floating bodies in the Material Point Method Event. This may expand to include OpenFOAM in an upcoming version of HydroUQ app.
        
 
        
 
      
 
@@ -487,7 +471,7 @@ 
      Debris and Floating Bodies
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      10. 
diff --git a/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_Bathy.html b/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_Bathy.html
index 97f857a0..d52767e7 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_Bathy.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_Bathy.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -235,7 +235,7 @@
 
   
      
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      
diff --git a/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_STL.html b/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_STL.html
index 4f84c097..54e15045 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_STL.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_STL.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -255,7 +255,7 @@
 
   
      
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      
diff --git a/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_SWCFD.html b/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_SWCFD.html
index 23fb9ce7..83b9b782 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_SWCFD.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_SWCFD.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -244,7 +244,7 @@
 
   
      
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      
diff --git a/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_WFlume.html b/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_WFlume.html
index 3ef121fc..517cf8a0 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_WFlume.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Geometry/Geom_WFlume.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -267,7 +267,7 @@
 
   
      
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      
diff --git a/docs/common/user_manual/usage/desktop/hydro/Initial.html b/docs/common/user_manual/usage/desktop/hydro/Initial.html
index 66d434fe..4fcb378f 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Initial.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Initial.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -245,7 +245,7 @@
   
      
 
      2.4.1.5. Initial conditions
      
 
      The initial settings window can be activated by selecting the option from the left panel as shown in Fig. 2.4.1.5.1. At present, this option is available only to set the initial height of the water in the domain. By default, the domain is defined to contain only air (i.e., alpha is zero). It is, thus, necessary to define a box where water is present (i.e., alpha is one).
      
-
      This is automatically set using the shallow-water solutions for simulation types involving coupling between shallow-water and CFD. This must be manually provided for all other simulation types using the tabular format shown in Fig. 2.4.1.5.1.
      
+
      This is automatically set using the shallow-water solutions for simulation types involving coupling between shallow water and CFD. This must be manually provided for all other simulation types using the tabular format shown in Fig. 2.4.1.5.1.
      
 
      
 ../../../../../_images/InitialSett.png
 
      Fig. 2.4.1.5.1 Initial settings panel available in EVT
      
@@ -266,7 +266,7 @@
 
   
      
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      
diff --git a/docs/common/user_manual/usage/desktop/hydro/MPM.html b/docs/common/user_manual/usage/desktop/hydro/MPM.html
index f1523016..fa6fb067 100644
--- a/docs/common/user_manual/usage/desktop/hydro/MPM.html
+++ b/docs/common/user_manual/usage/desktop/hydro/MPM.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -241,7 +241,7 @@
             
   
      
 
      2.4.3. Material Point Method
      
-
      The MPM event option is used to setup the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and MPM solver or using the ClaymoreUW MPM solver alone. The steps of the setup process for the event have been kept nearly similar to that often used in Finite Element Method to make it easier for researchers from structural engineering background to easily use this application. This includes SettingsMPM >> BodiesMPM >> BoundariesMPM >> SensorsMPM >> OutputsMPM. Figure HydroSteps_MPM shows the steps as selectable tab-pages in the GUI.
      
+
      The MPM event option is used to set the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and MPM solver or using the ClaymoreUW MPM solver alone. The steps of the setup process for the event have been kept nearly similar to that often used in the Finite Element Method to make it easier for researchers from structural engineering background to easily use this application. This includes SettingsMPM >> BodiesMPM >> BoundariesMPM >> SensorsMPM >> OutputsMPM. Figure HydroSteps_MPM shows the steps as selectable tab-pages in the GUI.
      
 
      
 ../../../../../_images/HydroSteps_MPM.png
 
      Fig. 2.4.3.1 The steps involved in setup of the Hydro event
      
@@ -275,7 +275,7 @@
 
   
      
     
      
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
      
   
      
diff --git a/docs/common/user_manual/usage/desktop/hydro/MaterialMPM.html b/docs/common/user_manual/usage/desktop/hydro/MaterialMPM.html
index 3a7e19e5..efea8428 100644
--- a/docs/common/user_manual/usage/desktop/hydro/MaterialMPM.html
+++ b/docs/common/user_manual/usage/desktop/hydro/MaterialMPM.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -217,10 +217,10 @@
 
        
 
      1. Isotropic Fluid with Viscous Shear Stress / J-Fluid: This is used to define a basic Newtonian fluid. The material properties include density, bulk modulus, derivative of the bulk modulus with respect to pressure, and dynamic viscosity.
        2. 
 
      2. Fixed-Corotated / Neo-Hookean: This is used to define solid hyperelastic material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, and density.
        3. 
-
      3. Drucker-Prager: This is used to define solid / granular material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, density, and the Drucker-Prager parameters.
        4. 
-
      4. Non-Associative Cam-Clay: This is used to define solid / granular material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, density, and the Non-Associative Cam-Clay parameters.
        5. 
+
      5. Drucker-Prager: This is used to define solid/granular material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, density, and the Drucker-Prager parameters.
        6. 
+
      6. Non-Associative Cam-Clay: This is used to define solid/granular material behavior under large strains. The material properties include Young’s modulus, Poisson’s ratio, density, and the Non-Associative Cam-Clay parameters.
        7. 
 
      
-
      Material properties are defined in the Material tab and are specific to the chosen constitutive law / material model. The material properties include:
      
+
      Material properties are defined in the Material tab and are specific to the chosen constitutive law/material model. The material properties include:
      
 
        
 
      1. Density: This refers to the density of the material. This is defined in terms of the mass per unit volume. The units are generally in kg/m3.
        2. 
 
      2. Young’s Modulus: This refers to the stiffness of the material. This is defined in terms of the force per unit area. The units are generally in Pa.
        3. 
@@ -240,7 +240,7 @@
 
   
        
     
        
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
        
   
        
diff --git a/docs/common/user_manual/usage/desktop/hydro/Materials.html b/docs/common/user_manual/usage/desktop/hydro/Materials.html
index 2d8b4916..b1dc33e0 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Materials.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Materials.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -267,7 +267,7 @@
 
   
        
     
        
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
        
   
        
diff --git a/docs/common/user_manual/usage/desktop/hydro/Meshing.html b/docs/common/user_manual/usage/desktop/hydro/Meshing.html
index 33f92a08..b111a30c 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Meshing.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Meshing.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -282,7 +282,7 @@
 
   
        
     
        
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
        
   
        
diff --git a/docs/common/user_manual/usage/desktop/hydro/OutputsMPM.html b/docs/common/user_manual/usage/desktop/hydro/OutputsMPM.html
index cda09eb7..06759552 100644
--- a/docs/common/user_manual/usage/desktop/hydro/OutputsMPM.html
+++ b/docs/common/user_manual/usage/desktop/hydro/OutputsMPM.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -231,7 +231,7 @@
             
   
        
 
        2.4.3.5. Outputs
        
-
        Outputs from the simulation not controlled by individual Sensors are collected in the Outputs tab. This includes choosing the output file format, checkpoint-resume file configuration, among other output related settings.
        
+
        Outputs from the simulation not controlled by individual Sensors are collected in the Outputs tab. This includes choosing the output file format, checkpoint-resume file configuration, and other settings related to output.
        
 
        
 
 
@@ -244,7 +244,7 @@
 
   
        
     
        
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
        
   
        
diff --git a/docs/common/user_manual/usage/desktop/hydro/Project.html b/docs/common/user_manual/usage/desktop/hydro/Project.html
index 54a61616..769a5508 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Project.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Project.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -251,13 +251,13 @@
 
      
 
        
 
      1. Project name and description: This is an optional parameter primarily meant for the user to identify and differentiate between projects.
        2. 
-
      2. Simulation type: This is mandatory and without a selection of the type, no other options can be set. The various simulation types available in Hydro event are as shown in Fig. 2.4.1.1.2. The differences between different simulation types are as given below.
        
+
      3. Simulation type: This is mandatory and without a selection of the type, no other options can be set. The various simulation options available in Hydro event are as shown in Fig. 2.4.1.1.2. The differences between different simulation types are as given below.
        
 
        
 ../../../../../_images/SimulationType.png
 
        Fig. 2.4.1.1.2 Simulation types available in Hydro event
        
 
        
 
          
-
        1. CFD to resolve SW (Using SW results): This setting facilitates the user to import solutions from pre-run two-dimensional shallow water solver. The user can select small portions of the shallow-water domain and setup high-fidelity three-dimensional CFD on these selected areas. For example: If one had a GeoClaw simulation for an earthquake on the Alaska fault and one is interested in the inundation in Cresant City, CA (USA). Then, the user can bring in the GeoClaw solutions and resolve the near-coast using a full three-dimensional CFD simulation.
          2. 
+
        2. CFD to resolve SW (Using SW results): This setting facilitates the user to import solutions from a pre-run two-dimensional shallow water solver. The user can select small portions of the shallow-water domain and setup high-fidelity three-dimensional CFD on these selected areas. For example: If one had a GeoClaw simulation for an earthquake on the Alaska fault and one is interested in the inundation in Cresant City, CA (USA). Then, the user can bring in the GeoClaw solutions and resolve the near-coast using a full three-dimensional CFD simulation.
          3. 
 
        3. CFD using bathymetry data: This simulation type allows the user to setup a CFD simulation using the geometry defined through the bathymetry data of the ocean floor.
          4. 
 
        4. CFD using STL file: This simulation type allows the users to setup the CFD simulation using STL files to define the geometry of the domain.
          5. 
 
        5. CFD of wave flume: This simulation type allows the user to access the Wave Flume Digital Twin.
          6. 
@@ -289,7 +289,7 @@
 
   
          
     
          
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
          
   
          
diff --git a/docs/common/user_manual/usage/desktop/hydro/SensorsMPM.html b/docs/common/user_manual/usage/desktop/hydro/SensorsMPM.html
index 66afc446..79f6ea26 100644
--- a/docs/common/user_manual/usage/desktop/hydro/SensorsMPM.html
+++ b/docs/common/user_manual/usage/desktop/hydro/SensorsMPM.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -231,7 +231,7 @@
             
   
          
 
          2.4.3.4. Sensors
          
-
          Sensors are used to measure physical quantities such as force, pressure, etc. within the simulation. Fundamentally, a sensor is a function that maps the state of the simulation within some specified space to a scalar or vector value. These functions are often “higher-order”, i.e. reduction operation such as max or add.
          
+
          Sensors are used to measure physical quantities such as force, pressure, etc. within the simulation. Fundamentally, a sensor is a function that maps the state of the simulation within some specified space to a scalar or vector value. These functions are often “higher-order”, i.e. reduction operations such as max or add.
          
 
          Defining a sensor in MPM involves specifying the sensor type, the material point variable to measure, and the region of the domain to measure. The sensor type is specified using the sensor_type parameter, and the material point variable to measure is specified using the mp_var parameter. The region of the domain to measure is specified using the region parameter. The sensor type can be one of the following:
          
 
          
 
@@ -245,7 +245,7 @@
 
   
          
     
          
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
          
   
          
diff --git a/docs/common/user_manual/usage/desktop/hydro/SettingsMPM.html b/docs/common/user_manual/usage/desktop/hydro/SettingsMPM.html
index 8b470d97..c7cfa49b 100644
--- a/docs/common/user_manual/usage/desktop/hydro/SettingsMPM.html
+++ b/docs/common/user_manual/usage/desktop/hydro/SettingsMPM.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -249,7 +249,7 @@
 
   
          
     
          
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
          
   
          
diff --git a/docs/common/user_manual/usage/desktop/hydro/Solver.html b/docs/common/user_manual/usage/desktop/hydro/Solver.html
index 6f691de2..1edb5f8f 100644
--- a/docs/common/user_manual/usage/desktop/hydro/Solver.html
+++ b/docs/common/user_manual/usage/desktop/hydro/Solver.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -271,7 +271,7 @@
 
   
          
     
          
-        © Copyright 2018-2024, The Regents of the University of California.
+        © Copyright 2020-2024, The Regents of the University of California.
 
     
          
   
          
diff --git a/docs/common/user_manual/usage/desktop/hydro/bestpractices.html b/docs/common/user_manual/usage/desktop/hydro/bestpractices.html
index 1a96325e..9a0f4fb5 100644
--- a/docs/common/user_manual/usage/desktop/hydro/bestpractices.html
+++ b/docs/common/user_manual/usage/desktop/hydro/bestpractices.html
@@ -16,7 +16,7 @@
   
   
   
-  
+  
   
   
 
@@ -51,7 +51,7 @@
     
     
     
-    
+    
 
 
 
@@ -232,7 +232,7 @@ 
          5.1. Errors and uncertainties
 
        6. The model is described by the Navier-Stokes equations. The exact N-S equations are solved when Direct Numerical Simulations (DNS) are employed. However, when the RANS approach is involved, as in HydroUQ, this involves approximations that could lead to errors and uncertainties. Thus, selecting the correct parameters is paramount.
          7. 
-
        7. If the solution shows divergence, check the boundary conditions, grid, discretization, and convergence errors. Check whether the flow is steady or unsteady and the timestep used in this regard.
          8. 
+
        8. If the solution shows divergence, check the boundary conditions, grid, discretization, and convergence errors. Check whether the flow is steady or unsteady and the time step used in this regard.
          9. 
 
        
 
      
 
      
@@ -252,7 +252,7 @@ 
      5.3. Spatial discretization
 
      5.4. Temporal discretization
      
@@ -275,10 +275,10 @@ 
      5.5. Boundary conditions
 
      5.6. SW-CFD domain sizes
      
 
        
-
      1. Note that each degree of latitude is approximately 69 miles (111 km apart). At the Equator, the distance is 68.703 miles (110.567 km); at Tropic of Cancer and Capricorn, it is 68.94 miles (110.948 km), and at the poles, it is 69.94 miles (111.699 km).
        2. 
+
      2. Note that each degree of latitude is approximately 69 miles (111 km apart). At the Equator, the distance is 68.703 miles (110.567 km); at the Tropic of Cancer and Capricorn, it is 68.94 miles (110.948 km), and at the poles, it is 69.94 miles (111.699 km).
        3. 
 
      3. 60 minutes = 1 degree
        4. 
 
      4. For a 1-minute grid used in the SW-solver, this is approximately a 2 x 2 km grid (in terms of distances). This could still be a considerably large domain for the CFD simulation, depending on the topography and bathymetry.
        5. 
-
      5. If the simulation type is SW-CFD coupling, then there can be wave reflections. Such wave reflections can lead to unphysical fluid accumulation at the boundary.
        6. 
+
      6. If the simulation type is SW-CFD coupling, then there can be wave reflections. Such wave reflections can lead to non-physical fluid accumulation at the boundary.
        7.
      10. -

    10. HydroUQ app 3.1.0 supports \(k-\epsilon\) and \(k-\omega\) SST models. These are both good choices for general applications. The \(k-\epsilon\) model is very reliable and can often be used to get initial values for more sophisticated models.

      11. +

    11. HydroUQ app 4.0.0 supports \(k-\epsilon\) and \(k-\omega\) SST models. These are both good choices for general applications. The \(k-\epsilon\) model is very reliable and can often be used to get initial values for more sophisticated models.

    12. The \(k-\epsilon\) model is inaccurate for flows with adverse pressure gradients. It does not allow integration of the conservation equations through the viscous sublayer where low Reynolds number corrections are recommended.

      13. -

    13. The \(k-\omega\) model is very sensitive to the freestream boundary conditions. However, it performs well for flows with variable pressure gradients.

      14. +

    14. The \(k-\omega\) model is very sensitive to the free-stream boundary conditions. However, it performs well for flows with variable pressure gradients.

    5.8. User errors

    1. Check for details in the geometry. Do not over-simplify the geometry without an understanding of the given problem.

      2. -

    2. Inaccurate use of boundary conditions and / or low-quality grids (e.g., poorly meshed in critical locations, inadaquate resolution for the problem) are commonly observed user errors.

      3. +

    3. Inaccurate use of boundary conditions and/or low-quality grids (e.g., poorly meshed in critical locations, inadequate resolution for the problem) are commonly observed user errors.

    4. Ensure that the timestep sizes provided are reasonable.

    @@ -344,7 +344,7 @@

    5.9. Checking results

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/usage/desktop/hydro/coupled.html b/docs/common/user_manual/usage/desktop/hydro/coupled.html index 03cd4f30..715beda5 100644 --- a/docs/common/user_manual/usage/desktop/hydro/coupled.html +++ b/docs/common/user_manual/usage/desktop/hydro/coupled.html @@ -16,7 +16,7 @@ - + @@ -130,8 +130,8 @@
  • 2.4.1. General Event (Legacy)
  • 2.4.2. Coupled Digital Twin @@ -251,8 +251,8 @@

    2.4.2. Coupled Digital TwinTable of Contents

     @@ -261,10 +261,10 @@

    2.4.2. Coupled Digital Twin2.4.2.1. Coupled Simulation Settings

    Simulation Settings

    The user is presented with a variety of settings to specify the coupled simulation. The GUI is shown in Figure EVT-CoupledSettings and individual input parameters are as follows:

    -

    Time Step: The coupling timestep for the solution. This value should be selected such that CFD model CFL criterion is satisfied, as well as the required minimum timestep for finite element analysis model stability.

    +

    Time Step: The coupling timestep for the solution. This value should be selected such that the CFD model CFL criterion is satisfied, as well as the required minimum timestep for finite element analysis model stability.

    Duration: Coupled simulation duration.

    Preload Structure w/ Gravity: Utilize the nodal masses to create a gravity loading in the -Z direction of the OpenSees model. (optional, this could be handled manually within the OpenSees script itself)

    -

    Run Preliminary Structural Analysis: Utilize the end state of the OpenSees analysis (if defined in the OpenSees script) as the initial state of structure during the coupled analysis.

    +

    Run Preliminary Structural Analysis: Utilize the end state of the OpenSees analysis (if defined in the OpenSees script) as the initial state of the structure during the coupled analysis.

    ../../../../../_images/Settings.png
    @@ -277,33 +277,33 @@

    2.4.2.1. Coupled Simulation SettingsCoupling Scheme: Implicit/Explicit. Implicit is recommended.

    Coupling Data Acceleration Method: IQN-ILS is recommended.

    Initial Relaxation Factor: The relaxation factor for FSI coupling iterations.

    -

    Maximum Coupling Iterations: Default, 100. Keep at a large value, should converge before reaching maximum iterations.

    +

    Maximum Coupling Iterations: Default, 100. Keep at a large value, and should converge before reaching maximum iterations.

    Coupling Iteration Convergence Tolerance: This is a relative convergence measure of the coupling data passed between participants within each coupling timestep. This value should be below 5e-3, but not too small. This is a measure of how much the coupling residuals change from coupling iteration to coupling iteration. Once the values have nearly approached their desired values from the interface acceleration techniques, the coupling convergence tolerance is satisfied.

    -

    Data Mapping Scheme: Nearest Neighbor is recommended. Radial-basis-function mapping is available, but is less stable and slower than nearest neighbor.

    +

    Data Mapping Scheme: Nearest Neighbor is recommended. Radial-basis-function mapping is available but is less stable and slower than the nearest neighbor.

    Output Data from Coupling Iterations: Not recommended. Intended for debugging of coupling iterations for models which are not converging.

    Coupling Iteration Output Data Frequency: A large value is recommended.

    • -
    -

    2.4.2.2. Specificy OpenSees Structural Model and an External Surface File

    +
    +

    2.4.2.2. Specify OpenSees Structural Model and an External Surface File

    OpenSees Model

    OpenSees File: Must be an OpenSeesPy script

    -

    External surface file: Must be a STL file, this is the boundary which will represent the structure within a three-dimensional CFD simulation, which will be coupled to the FEA model)

    +

    External surface file: Must be an STL file, this is the boundary that will represent the structure within a three-dimensional CFD simulation, which will be coupled to the FEA model)

    ../../../../../_images/OpenSees.png

    Fig. 2.4.2.2.1 OpenSees

    -
    -

    2.4.2.3. Specificy OpenFOAM CFD Model and Initial Conditions

    +
    +

    2.4.2.3. Specify OpenFOAM CFD Model and Initial Conditions

    OpenFOAM Model

    -

    Select a NHERI flume facility or specify the flume geometry within the text field boxes provided.

    +

    Select the NHERI flume facility or specify the flume geometry within the text field boxes provided.

    Specify a flume cell size (this is the approximate edge length size of the volumes within the CFD domain for the largest cells). The minimum flume cell size could tentatively be 8 times smaller than this value, due to mesh castellation during automatic meshing routines. Use caution when specifying this value. CFD mesh resolution is increased in the structural near field.

    ../../../../../_images/OpenFOAM.png

    Fig. 2.4.2.3.1 OpenFOAM

    Specify the flume bathymetry (STL file, or point list of x position, elevation of flume floor at x position).

    -

    If there is no bathymetry, please provide points within the point list which are outside of the boundary of the flume, or specify the bottom of the flume as a two point list with your start x location and end x location as the start and end of the flume and the flume elevation at both points as 0.

    +

    If there is no bathymetry, please provide points within the point list that are outside of the boundary of the flume, or specify the bottom of the flume as a two-point list with your start x location and end x location as the start and end of the flume and the flume elevation at both points as 0.

    ../../../../../_images/bathymetryOF.png

    Fig. 2.4.2.3.2 Bathymetry

    @@ -319,7 +319,7 @@

    2.4.2.3. Specificy OpenFOAM CFD Model an

    Fig. 2.4.2.3.4 Turbulence

    Specify the wave generation techniques for the CFD model, if waves are desired.

    -

    Paddle Generated Waves: Upload a CSV of times, displacements of the paddle at the inlet. This will create a paddle generated wave through motion of the CFD boundary at the minimum X boundary of the model.

    +

    Paddle Generated Waves: Upload a CSV of times, displacements of the paddle at the inlet. This will create a paddle-generated wave through the motion of the CFD boundary at the minimum X boundary of the model.

    Periodic Waves: Specify the wave properties to apply a periodic wave inlet boundary condition to the CFD model.

    No Waves: Steady state flow or flows without waves.

    @@ -329,7 +329,7 @@

    2.4.2.3. Specificy OpenFOAM CFD Model an

    2.4.2.4. Specify Outputs

    -

    A variety of outputs from the coupled model can be obtained through specification of the output settings.

    +

    A variety of outputs from the coupled model can be obtained through the specification of the output settings.

    Other issues

    Some of the other common tips and tricks for troubleshooting include:

    Know the objective

    -

    Before starting the simulation, it is essential to understand the intended goal of the project. This will help set up appropriate inputs. Hydro-UQ workflows already helps with this to the best extent possible. Yet, the user’s understanding of the physics is much necessary.

    +

    Before starting the simulation, it is essential to understand the intended goal of the project. This will help set up appropriate inputs. Hydro-UQ workflows already help with this to the best extent possible. Yet, the user’s understanding of the physics is much necessary.

    Mesh quality

    Most often, the quality of the mesh can be the reason for the simulation failure. Check the mesh quality. Hydro-UQ has an in-built mesher, and we continue to optimize its performance. However, this is limited and might not serve the needs of advanced researchers. It is then recommended to use external meshing tools and directly import the mesh. If the tool you used for meshing is unavailable, please submit a feature request using lblBugs.

    Units

    @@ -270,7 +270,7 @@

    Other issues

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/usage/desktop/hydro/general.html b/docs/common/user_manual/usage/desktop/hydro/general.html index 4e233f65..b14c7b28 100644 --- a/docs/common/user_manual/usage/desktop/hydro/general.html +++ b/docs/common/user_manual/usage/desktop/hydro/general.html @@ -16,7 +16,7 @@ - + @@ -242,10 +242,10 @@

    2.4.1. General Event (Legacy)

    -

    The general event option is used to setup the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and CFD solver or using the CFD solver alone. The steps of the setup process for the event have been kept nearly similar to that often used in Finite Element Method to make it easier for researchers from structural engineering background to easily use this application. This includes project settings >> geometry >> meshing >> materials >> initial conditions >> boundary conditions >> solver settings. These steps are available through a tree-structure as shown in Fig. 2.4.1.1.

    +

    The general event option is used to set the flow parameters related to the water-borne hazard event. This can either be a coupling between the shallow-water and CFD solver or using the CFD solver alone. The steps of the setup process for the event have been kept nearly similar to that often used in the Finite Element Method to make it easier for researchers from structural engineering background to easily use this application. This includes project settings >> geometry >> meshing >> materials >> initial conditions >> boundary conditions >> solver settings. These steps are available through a tree structure as shown in Fig. 2.4.1.1.

    ../../../../../_images/HydroSteps.png -

    Fig. 2.4.1.1 The steps involved in setup of the HydroUQ event

    +

    Fig. 2.4.1.1 The steps involved in the setup of the HydroUQ event

    Each of the above steps in the setup process differs depending on the type of simulation considered. They will be outlined in detail below:

    @@ -270,7 +270,7 @@

    2.4.1. General Event (Legacy)

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/usage/desktop/hydro/helpvideo.html b/docs/common/user_manual/usage/desktop/hydro/helpvideo.html index 684bcf0b..43608e1b 100644 --- a/docs/common/user_manual/usage/desktop/hydro/helpvideo.html +++ b/docs/common/user_manual/usage/desktop/hydro/helpvideo.html @@ -16,7 +16,7 @@ - + @@ -223,21 +223,13 @@

    9.1. Live Expert Tips

    -Fluid-Structure Interaction with OpenFOAM and OpenSees
    -
    -
    -
    -
    +Fluid-Structure Interaction with OpenFOAM and OpenSees
    -Coupling Regional Tsunami and Storm-Surge Simulation with Local-Scale Structural Response
    -
    -
    -
    -
    +Coupling Regional Tsunami and Storm-Surge Simulation with Local-Scale Structural Response
    @@ -254,7 +246,7 @@

    - © Copyright 2018-2024, The Regents of the University of California. + © Copyright 2020-2024, The Regents of the University of California.

    diff --git a/docs/common/user_manual/usage/desktop/hydro/releasenotes.html b/docs/common/user_manual/usage/desktop/hydro/releasenotes.html index 788ba50d..7b997a41 100644 --- a/docs/common/user_manual/usage/desktop/hydro/releasenotes.html +++ b/docs/common/user_manual/usage/desktop/hydro/releasenotes.html @@ -16,7 +16,7 @@ - + @@ -224,11 +224,7 @@

    6.1. Version 3.1

    -Version 3.1.0 (Current)
    -
    -
    -
    -
    +Version 3.1.0 (Current)

    Release date: April 1st, 2024

    Simulation Types:

    @@ -252,7 +248,7 @@

    6.1. Version 3.1

    1. Added debris modeling to MPM simulations.

      2. -

    2. Added support for complex debris geomtries (e.g. vehicles, shipping crates, composed primitives).

      3. +

    3. Added support for complex debris geometries (e.g. vehicles, shipping crates, composed primitives).

    4. Added support for advanced debris material models (e.g. Fixed-Corotated, Neo-Hookean, Drucker-Prager, Non-Associative Cam-Clay).

    @@ -284,7 +280,7 @@

    6.1. Version 3.1

    Fixed-Corotated: Hyperelastic material model for plastic and rubber-like materials.

  • Neo-Hookean: Hyperelastic material model for plastic and rubber-like materials.

  • Drucker-Prager: Applicable to granular materials, concrete, and other materials with a yield surface.

    • -

  • Non-Associative Cam-Clay: Aplicable to clays, concrete, and other topology changing material bodies

    • +

  • Non-Associative Cam-Clay: Applicable to clays, concrete, and other topology-changing material bodies

    • @@ -321,7 +317,7 @@

    6.1. Version 3.1

    Bodies may be split across multiple hardware partitions.

  • Accelerates simulation times by running multiple bodies in parallel.

  • A valid hardware partition may be a core, a GPU, or a node in an HPC cluster.

    • -

  • Each partition may hold some maximum number of bodies at once (specific to the system which the simulating tool was compiled on).

    • +

  • Each partition may hold some maximum number of bodies at once (specific to the system on which the simulating tool was compiled).

    • @@ -330,19 +326,19 @@

    6.1. Version 3.1

  • Boundaries

    -

    Any object in a simulation that is not a sensor or body is considered a Boundary. Boundaries, the collection of Boundary objects, are enforced boundary conditions which may apply to parts of the simulation (e.g. on grid-nodes or particles).

    +

    Any object in a simulation that is not a sensor or body is considered a Boundary. Boundaries, the collection of Boundary objects, are enforced boundary conditions that may apply to parts of the simulation (e.g. on grid nodes or particles).

    • Added boundaries for geometry primitives (e.g. sphere, box, cylinder).

    • Added selectable contact models (e.g. Sticky, Slip, Separable).

    • Added boundaries for the OSU LWF and WU TWB digital twin bathymetries.

    • Added boundary for the OSU LWF moving piston wave-maker.

      • -

    • Implemented array operations for boundary conditions (e.g. instace a boundary at specified spacings in X, Y, and Z).

      • +

    • Implemented array operations for boundary conditions (e.g. instance a boundary at specified spacings in X, Y, and Z).

  • Sensors

    -

    Any object in a simulation that is not a boundary condition or body is considered a Sensor. Sensors, the collection of Sensor objects, are used to monitor the simulation, collect desired data, reduce said data, and report the aggregated output as a time-series. In effect, they replicate instruments / sensors used in experiments (e.g. load-cells, wave-gauges, piezometers, velocimeters).

    +

    Any object in a simulation that is not a boundary condition or body is considered a Sensor. Sensors, the collection of Sensor objects, are used to monitor the simulation, collect desired data, reduce said data, and report the aggregated output as a time-series. In effect, they replicate instruments/sensors used in experiments (e.g. load-cells, wave-gauges, piezometers, velocimeters).