The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Install ShakeCast on AWS | Page | ## ShakeCast Cloud Installation ShakeCast V3 is shipped primarily as a pre-packaged Linux system image. Among tested distributions, CentOS (open-source equivalent of the RedHat Enterprise Linux) is the default operating system (OS). With the ready-to-use ShakeCast V3 system image, users can evaluate the software without excessive IT commitment to determine... |
| Install ShakeCast on Windows | Page | {% include tip.html content="For a better terminal emulator on Windows, use [Git Bash](https://git-for-windows.github.io/). Git Bash gives you Linux-like control on Windows." %} ## ShakeCast MS-Windows Installation A Windows Installer Package of ShakeCast V3 for Windows allows the administrator download, install, and configure the ShakeCast system. The package requires administrative privileges... |
| ShakeCast Implementation Recommendation | Page | ## Introduction ### Purpose This document presents recommendations for the technology infrastructure and setup requirements for deploying the ShakeCast V3 system at Caltrans. The contents of this report are intended for use by information technology (IT) professionals to serve as a technical reference during the deployment process. The recommendations contained... |
| System Administration | Page | The ShakeCast administrative interface is platform independent and is designed for an administrator to perform common tasks ranging from management of facili... |
| User Inventory Format | Page | Appendix A provides specifications on the format of the data files that must be supplied to customize the system to a user's facility inventory, fragilities and their user and notification information. An example of each file is provided with the V3 ShakeCast distribution in a folder found in the ShakeCast... |
| XML/JSON Metadata Formats | Page | Extensible Markup Language (known by the acronym XML) is a widely used and easily implemented method of exchanging data between disparate computer systems. The ShakeCast System receives ShakeMap information in XML from the USGS web server and uses XML to communicate all kinds of information between ShakeCast servers: - Data... |
| Utility Scripts | Page | A number of valuable Perl scripts are distributed with ShakeCast. This Appendix documents these utilities. For the most part, these scripts are internal to the system and normally users many need only a few of them, but users with complicated databases and needs may benefit at least an awareness of... |
| HAZUS MBT | Page | Relating HAZUS Structure Types to Seismic Performance |
| MBT Fragility | Page | HAZUS Model Building Fragility Table |
| Template Keywords | Page | ShakeCast Notification Template Keywords |
| System Configuration | Page | {% include tip.html content="With the introduction of the [ShakeCast Workbook](inventory_workbook.html), we highly recommend users to utilize the MS-Excel spreadshheet for inventory management. While the V3 accepts inventory in both legacy and the new XML format (workbook export), only the XML input data will take full advantage of the features offered... |
| Customization | Page | Tags provide another means of navigation for your content. Unlike the table of contents, tags can show the content in a variety of arrangements and groupings... |
| Installation Notes | Page | This guide is intended for ShakeCast system managers, operators and IT support staff. This guide is for you if you are installing, operating, or configuring ... |
| User Guide | Page | This guide is intended for ShakeCast V3 users. This guide is for you if you are using ShakeCast notifications, facility assessment or inspection reports, or ... |
| Release notes 3.0 | Page | Version 3 of ShakeCast, released October 2015. |
| System Requirements | Page | This document presents recommendations for the technology infrastructure and setup requirements for deploying the ShakeCast V3 system. The contents of this ... |
| Migrate Inventory from ShakeCast V2 to V3 | Page | This page describes steps for migrating from V2 to V3 system. |
[]: