ShakeMap operations, policies, and procedures

2021 ◽  
pp. 875529302110302
Author(s):  
David J Wald ◽  
C Bruce Worden ◽  
Eric M Thompson ◽  
Michael Hearne

The US Geological Survey’s ShakeMap is used domestically and globally for post-earthquake emergency management and response, engineering analyses, financial instruments, and other decision-making activities. Recent developments in the insurance, reinsurance, and catastrophe bond sectors link payouts of potentially hundreds of millions of dollars to ShakeMap products. Similarly, building codes, post-earthquake building damage forensic evaluations, and geotechnical evaluations often rely on estimated peak response-spectral values for site-specific evaluations that may lead to costly analyses, retrofits, or other expenditures. Given such activities, financial, engineering, and other technical users demand processing specifications and a metadata trail for actuarial, escrow, and forensic purposes for each significant earthquake. Recent inquiries include how and why maps change with time, how to interpret metadata, and how to obtain the creation and update history of various map layers. Similarly, the collection of ShakeMap scenarios and historical ShakeMaps—either created in earlier versions or rerun as part of the latest version of the ShakeMap Atlas—warrant a full explanation of the inputs, processing, and archiving given their contribution to fragility curve development and loss model calibration. For these reasons, in addition to event-specific ShakeMap metadata and a comprehensive online ShakeMap Manual, we have crafted this practice paper to answer several of the most frequently asked technical questions. We also describe an application programming interface (API) for accessing site-specific shaking metrics and their uncertainties for earthquake forensic purposes in a consistent fashion. In all, we describe the advantages of employing ShakeMaps for these critical purposes as well as describe their limitations and uncertainties, offering an extensive set of instructions and disclaimers that can be referenced by ShakeMap users.

2020 ◽  
Vol 27 (10) ◽  
pp. 1606-1611
Author(s):  
Liz Amos ◽  
David Anderson ◽  
Stacy Brody ◽  
Anna Ripple ◽  
Betsy L Humphreys

Abstract The US National Library of Medicine regularly collects summary data on direct use of Unified Medical Language System (UMLS) resources. The summary data sources include UMLS user registration data, required annual reports submitted by registered users, and statistics on downloads and application programming interface calls. In 2019, the National Library of Medicine analyzed the summary data on 2018 UMLS use. The library also conducted a scoping review of the literature to provide additional intelligence about the research uses of UMLS as input to a planned 2020 review of UMLS production methods and priorities. 5043 direct users of UMLS data and tools downloaded 4402 copies of the UMLS resources and issued 66 130 951 UMLS application programming interface requests in 2018. The annual reports and the scoping review results agree that the primary UMLS uses are to process and interpret text and facilitate mapping or linking between terminologies. These uses align with the original stated purpose of the UMLS.


2018 ◽  
Vol 9 (1) ◽  
pp. 24-31
Author(s):  
Rudianto Rudianto ◽  
Eko Budi Setiawan

Availability the Application Programming Interface (API) for third-party applications on Android devices provides an opportunity to monitor Android devices with each other. This is used to create an application that can facilitate parents in child supervision through Android devices owned. In this study, some features added to the classification of image content on Android devices related to negative content. In this case, researchers using Clarifai API. The result of this research is to produce a system which has feature, give a report of image file contained in target smartphone and can do deletion on the image file, receive browser history report and can directly visit in the application, receive a report of child location and can be directly contacted via this application. This application works well on the Android Lollipop (API Level 22). Index Terms— Application Programming Interface(API), Monitoring, Negative Content, Children, Parent.


Robotica ◽  
2021 ◽  
pp. 1-31
Author(s):  
Andrew Spielberg ◽  
Tao Du ◽  
Yuanming Hu ◽  
Daniela Rus ◽  
Wojciech Matusik

Abstract We present extensions to ChainQueen, an open source, fully differentiable material point method simulator for soft robotics. Previous work established ChainQueen as a powerful tool for inference, control, and co-design for soft robotics. We detail enhancements to ChainQueen, allowing for more efficient simulation and optimization and expressive co-optimization over material properties and geometric parameters. We package our simulator extensions in an easy-to-use, modular application programming interface (API) with predefined observation models, controllers, actuators, optimizers, and geometric processing tools, making it simple to prototype complex experiments in 50 lines or fewer. We demonstrate the power of our simulator extensions in over nine simulated experiments.


2021 ◽  
Vol 40 (2) ◽  
pp. 55-58
Author(s):  
S. Tucker Taft

The OpenMP specification defines a set of compiler directives, library routines, and environment variables that together represent the OpenMP Application Programming Interface, and is currently defined for C, C++, and Fortran. The forthcoming version of Ada, currently dubbed Ada 202X, includes lightweight parallelism features, in particular parallel blocks and parallel loops. All versions of Ada, since its inception in 1983, have included "tasking," which corresponds to what are traditionally considered "heavyweight" parallelism features, or simply "concurrency" features. Ada "tasks" typically map to what are called "kernel threads," in that the operating system manages them and schedules them. However, one of the goals of lightweight parallelism is to reduce overhead by doing more of the management outside the kernel of the operating system, using a light-weight-thread (LWT) scheduler. The OpenMP library routines support both levels of threading, but for Ada 202X, the main interest is in making use of OpenMP for its lightweight thread scheduling capabilities.


Sign in / Sign up

Export Citation Format

Share Document