ARM Radar Toolkit Viewer
ARTview is an interactive GUI viewer that is built on top of the Py-ART toolkit. It allows one to easily scroll through a directory of weather radar data files and visualize the data. All file types available in Py-ART can be opened with the ARTview browser.
You can interact with data files through "Plugins". Many functions from the Py-ART package can be selected. In addition, ARTview plugins allow querying data by selecting regions or points visually.
](http://dx.doi.org/10.5281/zenodo.27358)
With ARTview you can:
Dynamically switch fields (variables) and tilt angles via drop down menu.
Dynamically switch tilt angle via radio button selection. Also easily change
by using the up/down arrow keys.
Browse a directory by advancing with drop down "Next" and "Previous" menus or
by arrow left/right key.
View surface-based or (some) airborne radar files.
View (and switch between) PPI, sector or RHI type file scans.
Change display parametets such as scaling, title, units labels, colormap,
and add range rings.
Save output images from a drop-down menu (Or Ctrl+s on linux, Cmd+S on MacOS)
A toolbox which allows Zooming/Panning, find point values, select regions,
interface with Py-ART routines and select a custom tools a user creates.
The default two windows can be configured to share parameters or operate independently.
Hand-edit data files.
Write your own plugins to use.
Hand editing of radar data files is possible through the GateFilter and SelectRegion tools. Further functionality coming.
ARTView has become and installable package! It is still undergoing further functionality development, so keep an eye out for new features. It has performed well in internal testing, but we're sure there are bugs in there and we appreciate your help in finding and addressing them.
The single stream, original version is still available in the scripts directory. It is much more limited in scope than the full version.
##Tutorials Paul Hein has put together a brief introduction. Anderson Gama has made a video introduction to ARTview.
python setup.py install
or for a single user install
python setup.py install --user
Either cd into the installed folder and run:
python artview -d /some/directory/you/want/to/point/to
Or it can be run from anywhere with the following:
artview
A specific file can be loaded:
artview -F /some/directory/you/want/to/point/to/filename
A specific field (e.g. reflectivity) can be loaded:
artview -f 'reflectivity'
Use a different start-up script with -s
artview -s radar
There are several predefined scripts that you can use, but you can also write your own.
To see other command line options:
artview -h
ARTview should be able to recognize and correctly handle PPI, RHI and airborne files.
The default startup uses radar reflectivity and checks for a few common names. If you find a file with a field that does not load, let us know and we can add it to the list.
Py-Art >= 1.5
matplotlib >= 1.1.0
Basemap >= 0.99
PyQt4 >= 4.6
Make sure that matplotlib
is loading PyQt4
as backend, for testing that execute python test/qt.py
.
Also for a more smooth user experience we recomend to configure pyart to match the kind of files used as well as persornal preferences.
Developed on Python 2.7.7 and 2.7.9 :: Anaconda 2.0.1 and 2.1.0
ARTView has been tested on: MacOSX 10.9.4, 10.10.2, 10.10.4 Linux Debian (Jessie) Linux Red Hat (RHEL6)
##Contributors
Anderson Gama
Nick Guy (nick.guy@uwyo.edu)
Paul Hein
Timothy Lang
NOTE:: This is open source software and contributions are very welcome! This is not a primary project for any of the contributors, so please be patient if you have questions/suggestions. In addition it needs to be stated that no responsibility is taken by the author for any adverse effects.
There has not been extensive testing, but seems reasonably stable. We are always looking for feedback.
It is strongly encouraged to use Python 2.7 or above. There are minor issues with Python 2.6 operability. Some are taken care of with internal tests, however we do not intend to continue support for 2.6 for long.
Please contact Nick Guy at above email or preferably open an Issue with any problems you encounter.