Skip to content

Order channel lists in alarm emails. #19

Description

@alexhutko

Is the order of the breaching channels time ordered? I not, let's make it alphanumeric.

New channels out of alert:
UW.FORK.--.HHN
UW.FORK.--.HHE

All breaching channels:
UW.LEBA.--.HHN, avg: -6845970.213535067
NN.MCA06.--.HHE, avg: -124304.80751600911
NN.MCA06.--.HHZ, avg: -125286.07470153316
BK.MNDO.00.HHE, avg: 8389712.0
CI.ISA.--.HHE, avg: 418162.5878168463
NN.VCN.--.HHZ, avg: 8980479.0
BK.BARR.00.HHZ, avg: 8389692.0
BK.OAKV.00.HHN, avg: -8336268.244331578
NN.LCH.--.HHZ, avg: 52352.03425740487
BK.QRDG.00.BHZ, avg: -8274749.14466412
BK.BJES.00.HHZ, avg: -8340281.508289738
NN.MCA06.--.HHN, avg: -124855.97780
...

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions