usgs / shakecast

ShakeCast

Windows	Linux	Code Coverage	Code Quality

ShakeCast V4

ShakeCast, short for ShakeMap Broadcast, has a new home at the USGS GitLab site.

Checkout our GitLab repository.

shakecast's Issues

Create loading component

Create a test to look for PII in sc.json

Show shakemaps on facility page

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 upload fails with same name files

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

Request for Additional Facility Types

Submitted issue for Matthew Muto (SCE)

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.

Clock in configs occasionally breaks

Current link between the clock and the UI occasionally breaks; it should be replaces by an observable

Add service to look for server messages

Allows the ShakeCast UI to update the user when the server has digested uploaded files and completed scenario runs

File upload hangs

Occurs when server is busy; the UI must be waiting for a response from the server

Shakemap plotting doesn't associate with Event map layer

Certificate Error

urllib2 error when attempting to access an https page from within DOI

Unicode Error with event: us100087xb

https://earthquake.usgs.gov/earthquakes/eventpage/us100087xb#executive

Attempting to encode "Curaçao" causes html email generation to fail

Simplify appveyor.yml

New facility shaking entries made instead of rewriting old ones

Make inspection notification load with Jinja2

Use JS style suggestions from Codacy

Notification page loads with Jinja2 template

Upstream build failing

URLOpener throwing a 403 error

Style login page

update user info via UI

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.

Delete group from UI

Facility order in email wrong

It looks like the facilities aren't being sorted by their "rank" before being written to the email

Use preferred weight and map size when grabbing shakemap

rewrite front end in Angular2

Scenario events don't overwrite when pulled from the web

There should only be one "scenario event" present for each event id. Repulling the same event should rewrite the old event

ShakeMap disappears in facility page

Facility shaking only associated with first shakemap

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

Notifications for multiple groups aggregating with multiple events

Check user import

It looks like importing a user who is part of multiple groups might not actually make the connections

Images aren't always downloaded in mobile mail

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

User create new notification within UI

Right now, users can edit existing notifications, but cannot create new ones

Re-organize navbars and headers

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

Include distance to epicenter in notification

As an optional metric in inspection notifications

No test for proxy environement

Tests will fail during nighttime

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

Export XML or CSV from pyCast?

Decrease geoJSON database blocking

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

Update software via UI

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

Custom icons for facilities

Web server needs tests

Expand XML import functions to use UI messaging

Make notification personalization page operational

Allow users to undo an automated update

Ability to send notifications to users through UI

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

ShakeMap testing inadequite

If there hasn't been a shakemap generated within past 24 hours, there's no way to test shakemap processing code

Delete user from UI

Need to test Python on multiple versions in AppVeyor

Run Scenarios from UI

toast notification for file upload needed

Workbook Documentation

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

Notification layout a little off in web