This notebook demonstrates how to display data included in the lmatools repository.
If you haven't yet, process and view sample data included with lmatools
python ~/code/lmatools/testing/test_sklearn.py /path/to/output/files/Then, edit the data_path in the second cell to include /path/to/output/files/ as defined above. Run all the cells prior to the "Charge Analysis" and try interacting with the plot. You should see some data.
In [1]:
%matplotlib qt4
# import matplotlib
# matplotlib.use('nbagg')
#import matplotlib.pyplot as plt
from brawl4d.brawl4d import B4D_startup, redraw
import os
In [2]:
data_path = '/data/DC3/flash_sort/'
lma_file = os.path.join(data_path, 'h5_files/2012/Jun/02/LYLOUT_120602_204001_0600.dat.flash.h5')
In the cell below, note that the basedate has been set to match the dataset we specified above.
If you are not using data from the WTLMA, then you'll also need to pass ctr_lon=value and ctr_lat=value to B4D_startup.
In [3]:
from datetime import datetime
panels = B4D_startup(basedate=datetime(2012,6,2), ctr_lat=40.4463980, ctr_lon=-104.6368130)
In [4]:
import matplotlib.pyplot as plt; plt.show()
Below, set a valid path to lma_file. IPython will tab-complete paths, like the shell.
In [5]:
from brawl4d.LMA.controller import LMAController
lma_ctrl = LMAController()
d, post_filter_brancher, scatter_ctrl, charge_lasso = lma_ctrl.load_hdf5_to_panels(panels, lma_file)
In [6]:
h,m,s,dt = 20, 40, 0, 60
panels.panels['tz'].axis((h*3600 + m*60 + s, h*3600 + m*60 + s+dt, 1, 18))
panels.panels['xy'].axis((-150, 150, -150, 150))
Out[6]:
In [7]:
from brawl4d.LMA.widgets import LMAwidgetController
from IPython.display import display
from brawl4d.LMA.controller import LMAController
lma_tools = LMAwidgetController(panels, lma_ctrl, scatter_ctrl, charge_lasso, d)
display(lma_tools.tools_popup)
The cell above contains and combines all functions of Brawl4d into a single .py file. This allows all tools to be activiated simultaneously, while also enabling a centralized container for all active widgets for convienence.
LMA Tools Contained:
Number of Stations: Specify accordingly with data file (min=1; max=11)
Max Chi2: Values for chi2 obtained from the data file (min=0.0; max=1.0)
Charge Selection: Selection for Negative (-1), Neutral (0), and Positive (1) charge for charge selection and analyzation in the browser. The draw button activates the lasso tool enabling charge selection; re-clicking the draw button is necessary upon each selection made.
Color By: Allows the display of LMA data by chi2, time, or charge; selecting one will redraw the plot in the browser.
Animation Time: Allows for animation of the LMA data in the browser for charge polarity determination made by Charge Selection. The slider allows the user to select a desired time for total animation duration (min=1s, max=30s). Clicking Animate will then animate the data after a desired time has been selected.
Zoom in on a few cells of interest. The smaller, western and northern cells here are anomalously electrified, while the larger cluster is normally electrified.
In [15]:
h,m,s,dt = 20, 40, 0, 60
panels.panels['tz'].axis((h*3600 + m*60 + s, h*3600 + m*60 + s+dt, 1, 18))
panels.panels['xy'].axis((-50, 70, -140, -60))
Out[15]:
In [8]:
h,m,s,dt = 20, 40, 0, 5*60
panels.panels['tz'].axis((h*3600 + m*60 + s, h*3600 + m*60 + s+dt, 1, 18))
panels.panels['xy'].axis((-60, 50, -60, 50))
Out[8]:
This cell has a few large flashes. The flash at 2041:54.4 is the sort of flash that could make a +CG, though the NLDN didn't think it did so. It initaites a second negative leader branch at :55.3, and exhibits some retracing activity in the few hundred ms before that.
In [22]:
%%bash
cat /data/DC3/20120602/hereford_storm/june_02-03_nldn.txt | grep "20:41:5"
If you're using an HDF5-format LMA data file, the analyzed charge is automatically written to the HDF5 file. The results of the operation can be queried by looking for the points that have had their charge set to the value defined above.
In [ ]:
chg = d.data['charge']
wh = np.where(chg > 0)
print d.data[wh]['time']
In [ ]:
# A reference to the current data in the view is cached by the charge lasso.
current_data = charge_lasso.cache_segment.cache[-1]
# Manually set the color limits on the flash_id variable
scatter_ctrl.default_color_bounds.flash_id =(current_data['flash_id'].min(), current_data['flash_id'].max())
# Color by flash ID.
scatter_ctrl.color_field = 'flash_id'
redraw()
If the LMA controller found flash data, then it's possible to get a live update of flashes in the current view. current_events_flashes is an analysis pipeline branchpoint, which will send events and flashes to another analysis pipeline segment that can be specified with current_events_flashes.targets.add(target). Behind the scenes, it's hooked up to an segment that receives the events and flashes, and prints the average flash area of all flashes that have more than a threshold number of points.
Change the view a few times and you'll see updated flash stats below.
In [8]:
current_events_flashes = lma_ctrl.flash_stats_for_dataset(d, scatter_ctrl.branchpoint)
In [8]:
In [9]:
from scipy.spatial import Delaunay
from scipy.misc import factorial
import numpy as np
from stormdrain.pipeline import coroutine
class LMAEventStats(object):
def __init__(self, GeoSys):
""" GeoSys is an instance of
stormdrain.support.coords.systems.GeographicSystem instance
"""
self.GeoSys = GeoSys
def ECEF_coords(self, lon, lat, alt):
x,y,z = self.GeoSys.toECEF(lon, lat, alt)
return x,y,z
def _hull_volume(self):
tri = Delaunay(self.xyzt[:,0:3])
vertices = tri.points[tri.vertices]
# This is the volume formula in
# https://github.com/scipy/scipy/blob/master/scipy/spatial/tests/test_qhull.py#L106
# Except the formula needs to be divided by ndim! to get the volume, cf.,
# http://en.wikipedia.org/wiki/Simplex#Geometric_properties
# Credit Pauli Virtanen, Oct 14, 2012, scipy-user list
q = vertices[:,:-1,:] - vertices[:,-1,None,:]
simplex_volumes = (1.0 / factorial(q.shape[-1])) * np.fromiter(
(np.linalg.det(q[k,:,:]) for k in range(tri.nsimplex)) , dtype=float)
self.tri = tri
# The simplex volumes have negative values since they are oriented
# (think surface normal direction for a triangle
self.volume=np.sum(np.abs(simplex_volumes))
@coroutine
def events_flashes_receiver(self):
while True:
evs, fls = (yield)
x,y,z = self.ECEF_coords(evs['lon'], evs['lat'], evs['alt'])
t = evs['time']
self.xyzt = np.vstack((x,y,z,t)).T
self._hull_volume()
print "Volume of hull of points in current view is {0:5.1f}".format(
self.volume / 1.0e9) # (1000 m)^3
In [10]:
stats = LMAEventStats(panels.cs.geoProj)
stat_maker = stats.events_flashes_receiver()
In [11]:
current_events_flashes.targets.add(stat_maker)
In [14]:
print current_events_flashes.targets
In [13]:
@coroutine
def events_flashes_printer():
while True:
evs, fls = (yield)
print evs['lon'], evs['lat']
info_printer = events_flashes_printer()
current_events_flashes.targets.add(info_printer)
This will receive the events and flashes from the current 2D view, and update an interactive 3D view.
It should be possible to use the scatter_ctrl.branchpoint and the mappablerangeupdater setup by scatter_ctrl instead of the raw events flashes. This would permit synchronization with the same vmin, vmax, which is already being figured out.
In [9]:
from brawl4d.brawl4d import redraw
import mayavi.mlab as mvlab
from stormdrain.pipeline import coroutine
class MayaviOutlet(object):
def __init__(self, panels, ev_fl_broadcaster):
self.ev_fl_broadcaster = ev_fl_broadcaster
self.ev_fl_broadcaster.targets.add(self.rx())
self.p3d = mvlab.points3d([0], [0], [0], [0], scale_factor=5e-5)
self.scene = self.p3d.scene
self.scene.background = (0,0,0)
self.panels=panels
# Force a reflow of data
redraw(panels)
# move camera to see everything after data are plotted
self.scene.reset_zoom()
@coroutine
def rx(self):
while True:
ev, fl = (yield)
# self.ev = ev
# self.fl = fl
evx, evy, evz, evt = ev['x'], ev['y'], ev['z'], ev['time']
self.p3d.mlab_source.reset(x=evx, y=evy, z=evz, scalars=evt)
current_events_flashes = lma_ctrl.flash_stats_for_dataset(d, scatter_ctrl.branchpoint)
mvo = MayaviOutlet(panels, current_events_flashes)
In [10]:
mvo.p3d.scene.reset_zoom?
In [11]:
panels.bounds.limits()
Out[11]:
In [ ]: