Windows | Linux | Code Coverage | Code Quality |
---|---|---|---|
ShakeCast, short for ShakeMap Broadcast, has a new home at the USGS GitLab site.
Checkout our GitLab repository.
ShakeCast
License: Other
Windows | Linux | Code Coverage | Code Quality |
---|---|---|---|
ShakeCast, short for ShakeMap Broadcast, has a new home at the USGS GitLab site.
Checkout our GitLab repository.
One a user has a selected a facility, they should be able to select from a list of events that have affected the facility and have them plotted along side
File uploads in flask are numbered when their names overlap; file upload should overwrite the existing file, or give the new file a unique name
I’d like to request consideration of additional facility types for inclusion in future versions of ShakeCast. Facility types that would be of immediate use to SCE include:
GAS Gas generation facilities
HYDRO Hydropower generation facilities
SUB Electrical substations
We do not have specific fragility information for these facilities, but being able to distinguish these categories would assist us in our notification process. I believe these facility types might also be useful to other utility owners.
Current link between the clock and the UI occasionally breaks; it should be replaces by an observable
Allows the ShakeCast UI to update the user when the server has digested uploaded files and completed scenario runs
Occurs when server is busy; the UI must be waiting for a response from the server
urllib2 error when attempting to access an https page from within DOI
https://earthquake.usgs.gov/earthquakes/eventpage/us100087xb#executive
Attempting to encode "Curaçao" causes html email generation to fail
URLOpener throwing a 403 error
This allows admin to use a default password for users when the account is created. The the users that wish to access the ShakeCast UI can use the default password to access the UI and update their account to use a personalized password.
It looks like the facilities aren't being sorted by their "rank" before being written to the email
There should only be one "scenario event" present for each event id. Repulling the same event should rewrite the old event
From @dslosky-usgs on July 20, 2016 0:18
We need to process shakemaps as long as they fall within a monitoring region; the logic to determine whether a notification is sent should take place after facility processing. This will fix this issue and allow us to determine when an revised notification should be sent
Copied from original issue: dslosky-usgs#4
It looks like importing a user who is part of multiple groups might not actually make the connections
Add a random string to the ShakeMap and new event capture cid before attaching them to an email. This should improve the mobile mail application's ability to link specific images with specific emails
Right now, users can edit existing notifications, but cannot create new ones
Combine general and admin navbars using a router to determine which is displayed
Move all header code into Navbar allowing the header component to be just the title of each page
As an optional metric in inspection notifications
Tests require all earthquakes to be processed, but by default small earthquakes aren't processed at night. Tests should first check that only small earthquakes are left unprocessed, then configurations should be adjusted so all earthquakes are processed
By comparing event update times; reducing query period to 1 hour from 1 day for most geoJSON runs will also help. 1 Day queries should still run once or twice per day
Code updates should be placed on a public facing USGS server (FTP site or DMZ)
Cron job should check USGS server (same FTP or DMZ) for a JSON feed with update information
JSON feed is interpreted; when an update is required an email is sent to admin users
Admin logs into UI and authorizes the update
ShakeCast uses information from the JSON feed to update existing source
Users should subscribe to blog, but it should also be possible to display a notification in users' UI. This could be done the same way we're thinking about alerting ShakeCast systems to update their software
If there hasn't been a shakemap generated within past 24 hours, there's no way to test shakemap processing code
Documentation lacks...
Import/Export info
Data requirements
XML structure
Maybe explanation of Groups? Actually defining facilities, groups, and users alongside data requirements and XML structure might help give users a better idea of how everything works...
AEBM workbook information
Add others as comments
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.