diff --git a/DEVELOPER_NOTES.md b/DEVELOPER_NOTES.md
new file mode 100644
index 00000000..74ca7eb5
--- /dev/null
+++ b/DEVELOPER_NOTES.md
@@ -0,0 +1,308 @@
+
+# Other stuff
+
+## Concepts
+
+### Object Oriented design
+
+Internally, Zmap has changed from a collection of scripts to
+functions and classes. Here, super briefly, is what these changes mean:
+
+* __functions__ vs __scripts__:
+ * _scripts_ work on variables in the main workspace. Everything one does may
+ affect (intentionally or not) values used by other scripts. Once the script
+ is run, then the workspace is left in an altered state. _#very script behaves
+ as though the user was typing at the MATLAB command prompt_
+ * _functions_ are routines that are self contained. They may take a list of
+ arguments (input variables), create and modify a bunch of variables internally, and then return one or more results. The behavior is well defined at the top
+ of each function
+* __classes__ : a class is a package of interrelated _functions_ (called _methods_)and _variables_ (called _properties_). A good class will either represent one
+thing, or accomplish one major goal.
+
+### major classes
+
+One can get more information about each class through the matlab help
+system. Using one of the help functions, such as `help`, `doc`, `methods`
+
+For example:
+
+```matlab
+>> doc ZmapCatalog
+```
+
+This brings up an interactive browser where you can look at the classes'
+properties (variables) and methods (functions).
+
+#### ZmapCatalog
+
+#### ZmapData
+
+#### ZmapGlobal
+
+#### ZmapGrid
+
+#### MapFeature
+
+MapFeatures are stored in ZmapGlobal.Data.features and can be looked up by name
+
+```matlab
+feat = ZmagGlobal.Data.features('borders');
+f
+feat.plot(ax);
+```
+
+#### ZmapFunction
+
+#### ZmapGridFunction < ZmapFunction
+
+#### ZmapFunctionDialog
+
+#### testing
+
+# modification notes for ZmapInABox
+
+## (Super abbreviated) Summary of major changes from earlier versions of Zmap
+
+* __Scripts are now Functions__: Previously, all routines were scripts that
+worked by modifying variables in the general workspace. Some of these were
+global.
+* __Catalogs are no longer arrays__: Catalogs are now of type `ZmapCatalog`.
+ * Catalogs now have named fields, such as _Longitude_, _Latitude_, _Date_,
+ _Depth_,and _Magnitude_. This makes working with catalogs more intuitive, so in the code, for example, all depths can be accessed as `catalog.depth` instead of `catalog(:,7)`
+ * Catalogs can now hold other types of data, such as `datetime`, `string`, and `cell` arrays as needs dictate.
+* __dates__: Zmap now uses `datetime` instead of its older decimalyear format.
+ * _decimal year_ would mean that time would compress or extend depending upon
+ leap years. The conversions were complicated, and repeated throughout the code.
+ * _datetime_ allows the use of more sophisticated (and more importantly,
+ matlab-handled) time representations. The difference between two `datetime`
+ values is a `duration` value. These are excellent because units are built-in.
+ There is no need to guess whether a value is in years, seconds, etc.
+* __workspace variables__: The results of calculations are specifically
+written to the workspace, whereas previously every value regardless of significance
+was written to the workspace.
+* __global variables__: Some values are accessed throughout the Zmap program.
+These are all kept in an object (variable) named ZmapGlobals. This:
+ * keeps them in a coherently named space,
+ * allows the values to be saved together
+* __Data import__: imported values will now be of type `ZmapCatalog`.
+ * Data can now be imported over the web via FDSN services
+* Data export
+* __user interface__: the user interfacer has been overhauled in countless
+ways.
+
+### UI Controls not showing up
+
+For `uicontrol` items, the `units` must be set to `normalized` prior to setting the `Position`, otherwise they will not show. ex. `working_dir_in`
+My solution, to avoid fixing 1000's of individual callbacks: set the system's defaultuicontrolunits to 'normalized'.
+
+`set(0,'defaultuicontrolunits','normalized')`
+
+There is some fluff around it to warn users. However any other defaults are not kept.
+
+### eval
+
+eval is (no longer/not) a recommended way to do things. Providing strings to be evaluated is generally considered unsafe, and circumvents any checking that MATLAB could do
+
+In some cases, it was used prior to "try/catch". What exists:
+
+```matlab
+do = ['risky_outcome = risky_function(''parameter'',value);']
+err = ['disp(''oops'')']
+eval(do,err);
+```
+
+which should all be converted to
+
+```matlab
+try
+ risky_outcome = risky_function('parameter', value);
+catch ME
+ error_handler(ME,'oops');
+end
+```
+
+### CallBack functions
+
+Most callback functions are implemented as strings. Ideally they would be function calls instead. The complications of determining the context makes editing these somewhat less-than straightforward.
+
+## deprecated functions
+
+Some functions are deprecated, or specific options are deprecated. These need to be changed.
+
+Some (non-exhaustive) somewhat straight-forward replacements
+
+* rand('seed',...) -> rng('shuffle')
+* TBD
+
+### strategies
+
+For some functions, an *adapter* function will be used. This makes for very simple code substitution, especially when the function is in widespread use.
+
+Example:
+
+```matlab
+[figexists, fignum] = figflag('title');
+% figflag is deprecated
+```
+
+now, I created a function named `figure_exists.m` with the same basic functionality. A global search-replace allowed me to nearluy instantaneously change these (194 occurances, spread throughout 163 files) to
+
+```matlab
+[figexists, fignum] = figure_exists('title');
+```
+
+## shadowed functions
+
+Functions which have the same name as provided matlab functions and serve the same purpose are renamed QUARENTINE_ . eg. `ginput()`
+Often the newer functions have different signatures, and shadowning produces some confusing errors.
+
+## Celso supplied functions
+
+`do_nothing` provides a function call that works as advertised.
+
+`error_handler` provides a unified location to send those pesky **case** issues. This can make tracking issues easier.
+ Depending on the paramters, it could show the error, do nothing, or show some alternate text.
+
+`figure_exists` provides a replacement for `figflag`
+*the above is severely outdated*
+
+## catalog / catalog views
+
+you load data into a `ZmapCatalog`. This is kept in `ZmapData.primeCatalog` (used to be 'a')
+You filter it via `catalog_overview` , which yields `ZmapData.Views.primary` containing a `ZmapCatalogView`. The `ZmapCatalogView` is the go-between between the catalog and the maps. Changing the view ranges will leave the primary catalog intact.
+
+A `ZmapCatalogView` can be attached either to a globally accessible `ZmapCatalog` or `ZmapCatalogView`.
+
+Layers within the plotting map are actually an array of `ZmapCatalogViews`, located in
+`ZmapData.Views.Layers`. Ranges in these views can be changed, and they will affect
+the data being displayed. I would have liked to use `linkdata` to automatically update
+the maps, but it appears to get bogged down very quickly as it is used.
+
+When a polygon is created (circle or other shape), it can be used to further filter the
+`ZmapCatalogView`. the working catalog (either newt2 or newcat, I don't remember which)
+is the current polygon applied to `ZmapData.Views.primary`
+
+To get a `ZmapCatalog` from a `ZmapCatalogView` using the `ZmapCatalogView.Catalog` function.
+
+## selections and grids
+
+# other general things to tackle project-wide
+
+* `lasterr` not recommended (88 results, 64 files) since 2009b
+* `fileparts`, remove 4th output (versn) (6 results) [done] since 2010a
+* `isstr` not recommended, use `ischar` (150 results, 68 files) [done] since 2010a [mapseis, too]
+* `str2mat` replace with `char` (4 results, 2 files) [done] zmap
+* `strread` replace usage with textscan. (97 results, 40 files) [in AddOneFiles] since 2010a
+ * ex. [a,b,c]=strread(...) => C= textscan(...); [a,b,c] = deal(C{:}) since 2010a
+* `strvcat` replace with char (4 results, 3 files) [done] since 2010a
+* `textread` replace with textscan as above, and use fopen/fclose. (31results, 3 files) since 2010a
+* `sprintf` - not necessary for error text (74 results in 14 files)
+* `eval` - replace in favor of actually doing the thing (1567 results, 364 files)
+ * `eval(do[,err])` - replace with a try/catch (174 results, 82 files)
+* `evalin` - ensure use makes sense (44 results, 14 files)
+* `NaN` - be consistent about capitalization, and do not create matrix with ones()*nan or zeros(*nan)
+* `NaN` - cannot compare with ==, use isnan() instead. only a couple places [done]
+* `error(nargchk...)` - replace with narginchk or nargoutchk [done] since 2011b
+* `hdf_funs.m` - probably outdated. matlab has built-in version hdfread, hdfinfo
+* error and warning message identifiers have changed since 2012b. info at: http://www.mathworks.com/support/solutions/en/data/1-ERAFNC/?solution=1-ERAFNC -- see pdf
+* `num2str` - for large integers, use int2str(x) instead. (manymany, but probably affects very few)
+since 2013a
+* `addParamValue` - replace with `addParameter` for an input parser. [done] r2013b
+* `flipdim` - replace with `flip` (45 in 19) [done] r2014a
+* `bitmax` - replace with `flintmax` [done]
+* `layout` gone. no replacemnt, in 1 file.
+* HitTest, Selected, and SelectionHighlight properties for several ui components shouldn't be used r2014a
+
+* remove DateStr2Num, is no longer used anywhere. cursory test shows this causes a long delay.
+* remove DateConvert. also unused
+
+* remove MacMarone - doesn't seem to be used, and is likely an unneeded layer of abstraction. Also.. requires compilation for system and has large disclaimer on web page (dated 2014).
+
+* consider new storage options where it makes sense: DateTime, table, timetable, timeseries, tscollection, containers.Map, duration, categorical arrays (especially DateTime and Catagorical Arrays)
+
+* provide help tooltips for menu items. Perhaps functions could provide their own tooltip text
+* provide description (and a REFERENCE!) for each function.
+* identify and prioritize Zmap functions for incorporation into MapSeis
+* clearly define how to convert a script from Zmap into MapSeis -->automation tool?
+* clearly define how functionality can be added to MapSeis
+
+* investigate required actions (documentation? coding? examples?) to facilitate use of MapSeis / Zmap. How do I add functionality? How do I make a script that leverages this?
+
+* assocArray() is not needed [EXCEPT FOR BACKWARDS COMPATIBILITY?] use containers.Map instead. (introduced matlab 2008b)
+
+* remove "backup" files. Let versioning system (git) take care of remembering past versions of stuff.
+
+* **remember to keep zmap compatible with mapSeis**
+
+# previous authors/contributors, and people with code incorporated into MatSeis
+
+*Stefan Wiemer* ~ca 1994-1999
+*Danijel Schorlemmer* ~ca 2003
+*Jochen Woessner*
+*Matt McDonnell* mapseis
+*David Eberhard* mapseis (after Matt?)
+*Carlos Adrian Vargas Aguillera* - cm_and_cb_utilities
+*Peter J. Acklam*
+*Denis Gilbert*
+*Morris Maynard*
+*Anders Brun*
+*Elmar Tarajan*
+*Deidre Byrne*
+*Michael W Mann*
+*Thomas van Stiphout*
+*Elvis Chen*
+*cpouillo*
+*Jiancang Zhuang*
+*Joaquim Luis* - wrote Mirone?
+*R. A. Baker* '98
+*Jan Simon* [matlab]
+*Joseph Kirk*
+*R Pawlowicz*
+*D. L. Hallman*
+*Bob Hamans*
+*R Cobb* 11/94
+*Quan Quach* 12/12/07
+*A Kim*
+*W Strumpf*
+*E Byrns*
+*L Job*
+*E Brown*
+*Annemarie*
+*M Hendrix* - calendar2.m see matlab central
+*D. Kroon*
+*Doug Harriman*
+*Brandon Kuczenski*
+*Colin Humphries*
+*Dave Mellinger*
+*Gerry Middleton* '95
+*T Debole*
+*Takeshi Ikuma*
+*Karaen Felzer* 2007
+*Ramon Zuniga*
+*Alexander Allmann*
+*Guiseppe Cardillo*
+*Dahua Lin* 2008
+*A. M. Zoubir* 1998
+*D R Iskander* 1998
+
+# Adding Focal mechanisms
+
+look at:
+Focal Mechanisms:
+https://ch.mathworks.com/matlabcentral/fileexchange/61227-focalmech-fm--centerx--centery--diam--varargin-
+
+Moment tensors can be retrieved from places like:
+http://www.isc.ac.uk/cgi-bin/web-db-v4?event_id=610635717&out_format=IMS1.0&request=COMPREHENSIVE
+http://www.isc.ac.uk/iscbulletin/search/webservices/
+and IRIS's SPUD
+http://www.isc.ac.uk/iscbulletin/search/webservices/
+
+# uncertainties, EVENT data
+
+# completeness maps precalculated on the web
+
+completenessweb.org
+
+## ADDING FUNCTIONALITY
+
+[Adding Functionality](ADDING_FUNCTIONALITY.md)
\ No newline at end of file
diff --git a/README.md b/README.md
index 125935f4..b28588ff 100644
--- a/README.md
+++ b/README.md
@@ -17,23 +17,56 @@ ZMAP version7.X represents a major rework of ZMAP.
### Some functions also require:
- Optimization toolbox.
+### About ZMAP7
+
+Nearly every aspect of the program has been modified, with the following goals in mind:
+
+* Make ZMAP compatible with modern MATLAB installations
+* Make it easer to add additional functionality
+* Make the user interfaces more consistent and interactive.
+* Make code more robust (leveraging MATLAB functions and objects)
+* Make existing code more readable and maintainable (reducing code duplication)
+* Retrieve event data from online services (FDSN web services)
+
+**Be aware, the changes in ZMAP are extensive**, and not all previously existing features may still exist. Also, you may not be able to load existing save files.
+ZMAP7 should work from Matlab 2018a upwards.
+
+**Since this is an *alpha* version, expect that there are many areas that are still under construction**. Menu items will likely move around, and figures will change. However, the basic functionality is there and should be able to help you start to explore your seismology data. We look forward to your feedback and idea for what we should include.
+
+If (when) you run into bugs, feel free to report through creating a GitHub issue. (“Report a ZMAP issue” , under the “Help” menu on the ZMAP windows. Please, do not send reports through email, as the issue list will be accessible by both whomever continues to maintain this program and the community. The issues can be properly documented, prioritized, and addressed.
+
+To get started with git, and ZMAP7, I created a few movies:
+https://www.youtube.com/playlist?list=PLXUrwVIXIt9wQ5gkCP5B96k8EHzAX6bJX
+[Note: these may already be severely out-of-date]
+
## Getting Started
+### Quick Start
+
+1. Download or clone ZMAP 7 to your computer.
+1. Start MATLAB.
+1. Change directory to the zmap directory
+1. in the MATLAB command line, type "zmap"
+
+> some sample data for Switzerland can be found in the file `zmap/resources/sample/SED_fdsn_2000_on.mat`
+
+> Video: https://www.youtube.com/embed/gONcFBy4p8U?end=79
+
### Work flow
+Most work will happen in the Main ZMAP screen.
+
### Loading data
-From the welcome screen, choose the `data` menu, where you will be presented with several options including:
-* `Load Catalog (*.mat file)` : retreive a catalog saved into a matlab data file. Some sample data can be found in zmap/resources/sample
+From the main ZMAP window, choose the `catalog` menu, then select `get/load catalog` where you will be presented with several options including:
-* `FDSN web fetch` : retrieve a catalog from an FDSN web service
+* `from (*.mat file)` : retreive a catalog saved into a matlab data file. Some sample data can be found in zmap/resources/sample
-* `Import Catalog from other formatted file` : this contains mostly unmaintained functions to import from other sources.
+* `from FDSN service` : retrieve a catalog from an FDSN web service
-Catalogs can also be imported from the `Catalog` menu on the main map interface.
+* `from other formatted file` : this contains mostly unmaintained functions to import from other sources.
-Upon importing data you may be presented with another dialog box that allows you to further constrain your data.
@@ -44,7 +77,7 @@ Clicking on the `see distributions` button will show a few histograms that may h
### Main Map Screen
-Once a catalog is loaded, you will be presented with the Main Window.
+Once a catalog is loaded, earthquakes will be plotted in the Main Window.
This is where most of the work will happen. The screen is divided into several sections. When first presented, all events will be hilighted, and the main map will take up the entirety of the left side of the window.
@@ -60,10 +93,10 @@ Several features are plotted on the map along with the earthquakes. Which ones a
Regions can be selected in a few ways. Start by right-clicking in the map. Several options related to regions will be presented including :
-* `Set Polygon: Box` : select a rectangular region by clicking on two corners to define a box.
-* `Set Polygon: Irregular Shape`: select a region by creating a polygon with the mouse. Anything other than a "normal" click will close the polygon.
-* `Set Circle` : Click and drag from the center of the circle out to some radius of interest.
-* `Clear Shape` : deletes the shape. all events are once again active.
+* `Select events in BOX` : select a rectangular region by clicking on two corners to define a box.
+* `Select events in POLYGON`: select a region by creating a polygon with the mouse. Anything other than a "normal" click will close the polygon.
+* `Select events in CIRCLE` : Click and drag from the center of the circle out to some radius of interest.
+* `Delete polygon` : deletes the shape. all events are once again active.
When any of the above choices have been made, only the events within the region (or _shape_) will be colored. All other events become grey dots. The plots to the right will also change to reflect your selection.
@@ -75,21 +108,9 @@ Once a shape is defined, then all other events fade into the background.
#### Working with a region
-Regions can be modified : scaled, dragged, points added, etc. by right-clicking on the shape itself. Here are a list of current options (as of Feb 2017):
-
-* `info...` provide basic information about this region and the shape that defines it.
+Regions can be modified : scaled, dragged, points added, etc. by interacting with the shape itself.
+See the menu item `about editing polygons` from the `Sampling` menu for a list of ways to interact with a polygon.
-* `Analyze EQ inside Shape`, `Analyze EQ outside Shape`, and
-`Compare Inside vs Outside` : all bring up a cumulative time plot window, from
-where further analysis is possible.
-
-* `edit shape` : activates the shape, allowing it to be dragged, resized (via scrollwheel), and, for some shapes, have individual points added, moved, or removed.
-Once you are done with the shape manipulations, select `Finished` from the same context menu. The changes will then be reflected in all the accompanying plots.
-
-* additional options may appear, depending upon the chosen shape. For example,
-a *circle* has:
- * `Choose Radius` : allowing you to define a specific radius by typing.
- * `Snap to N Events` : resizes the circle to encompass a specified number of events.
### Cross Sections
@@ -128,310 +149,8 @@ The binning for these plots can be changed through the axes' context menu.
These plots can all be opened in another window, available for further analysis. To do so, right click on the data line of interest. Additionally, the axes scaling for many plots can be toggled between linear and logarithmic.
-# Other stuff
-
-## Concepts
-
-### Object Oriented design
-
-Internally, Zmap has changed from a collection of scripts to
-functions and classes. Here, super briefly, is what these changes mean:
-
-* __functions__ vs __scripts__:
- * _scripts_ work on variables in the main workspace. Everything one does may
- affect (intentionally or not) values used by other scripts. Once the script
- is run, then the workspace is left in an altered state. _#very script behaves
- as though the user was typing at the MATLAB command prompt_
- * _functions_ are routines that are self contained. They may take a list of
- arguments (input variables), create and modify a bunch of variables internally, and then return one or more results. The behavior is well defined at the top
- of each function
-* __classes__ : a class is a package of interrelated _functions_ (called _methods_)and _variables_ (called _properties_). A good class will either represent one
-thing, or accomplish one major goal.
-
-### major classes
-
-One can get more information about each class through the matlab help
-system. Using one of the help functions, such as `help`, `doc`, `methods`
-
-For example:
-
-```matlab
->> doc ZmapCatalog
-```
-
-This brings up an interactive browser where you can look at the classes'
-properties (variables) and methods (functions).
-
-#### ZmapCatalog
-
-#### ZmapData
-
-#### ZmapGlobal
-
-#### ZmapGrid
-
-#### MapFeature
-
-MapFeatures are stored in ZmapGlobal.Data.features and can be looked up by name
-
-```matlab
-feat = ZmagGlobal.Data.features('borders');
-f
-feat.plot(ax);
-```
-
-#### ZmapFunction
-
-#### ZmapGridFunction < ZmapFunction
-
-#### ZmapFunctionDialog
-
-#### testing
-
-# modification notes for ZmapInABox
-
-## (Super abbreviated) Summary of major changes from earlier versions of Zmap
-
-* __Scripts are now Functions__: Previously, all routines were scripts that
-worked by modifying variables in the general workspace. Some of these were
-global.
-* __Catalogs are no longer arrays__: Catalogs are now of type `ZmapCatalog`.
- * Catalogs now have named fields, such as _Longitude_, _Latitude_, _Date_,
- _Depth_,and _Magnitude_. This makes working with catalogs more intuitive, so in the code, for example, all depths can be accessed as `catalog.depth` instead of `catalog(:,7)`
- * Catalogs can now hold other types of data, such as `datetime`, `string`, and `cell` arrays as needs dictate.
-* __dates__: Zmap now uses `datetime` instead of its older decimalyear format.
- * _decimal year_ would mean that time would compress or extend depending upon
- leap years. The conversions were complicated, and repeated throughout the code.
- * _datetime_ allows the use of more sophisticated (and more importantly,
- matlab-handled) time representations. The difference between two `datetime`
- values is a `duration` value. These are excellent because units are built-in.
- There is no need to guess whether a value is in years, seconds, etc.
-* __workspace variables__: The results of calculations are specifically
-written to the workspace, whereas previously every value regardless of significance
-was written to the workspace.
-* __global variables__: Some values are accessed throughout the Zmap program.
-These are all kept in an object (variable) named ZmapGlobals. This:
- * keeps them in a coherently named space,
- * allows the values to be saved together
-* __Data import__: imported values will now be of type `ZmapCatalog`.
- * Data can now be imported over the web via FDSN services
-* Data export
-* __user interface__: the user interfacer has been overhauled in countless
-ways.
-
-### UI Controls not showing up
-
-For `uicontrol` items, the `units` must be set to `normalized` prior to setting the `Position`, otherwise they will not show. ex. `working_dir_in`
-My solution, to avoid fixing 1000's of individual callbacks: set the system's defaultuicontrolunits to 'normalized'.
-
-`set(0,'defaultuicontrolunits','normalized')`
-
-There is some fluff around it to warn users. However any other defaults are not kept.
-
-### eval
-
-eval is (no longer/not) a recommended way to do things. Providing strings to be evaluated is generally considered unsafe, and circumvents any checking that MATLAB could do
-
-In some cases, it was used prior to "try/catch". What exists:
-
-```matlab
-do = ['risky_outcome = risky_function(''parameter'',value);']
-err = ['disp(''oops'')']
-eval(do,err);
-```
-
-which should all be converted to
-
-```matlab
-try
- risky_outcome = risky_function('parameter', value);
-catch ME
- error_handler(ME,'oops');
-end
-```
-
-### CallBack functions
-
-Most callback functions are implemented as strings. Ideally they would be function calls instead. The complications of determining the context makes editing these somewhat less-than straightforward.
-
-## deprecated functions
-
-Some functions are deprecated, or specific options are deprecated. These need to be changed.
-
-Some (non-exhaustive) somewhat straight-forward replacements
-
-* rand('seed',...) -> rng('shuffle')
-* TBD
-
-### strategies
-
-For some functions, an *adapter* function will be used. This makes for very simple code substitution, especially when the function is in widespread use.
-
-Example:
-
-```matlab
-[figexists, fignum] = figflag('title');
-% figflag is deprecated
-```
-
-now, I created a function named `figure_exists.m` with the same basic functionality. A global search-replace allowed me to nearluy instantaneously change these (194 occurances, spread throughout 163 files) to
-
-```matlab
-[figexists, fignum] = figure_exists('title');
-```
-
-## shadowed functions
-
-Functions which have the same name as provided matlab functions and serve the same purpose are renamed QUARENTINE_ . eg. `ginput()`
-Often the newer functions have different signatures, and shadowning produces some confusing errors.
+## Other help pages
-## Celso supplied functions
+[Adding Functionality](ADDING_FUNCTIONALITY.md)
-`do_nothing` provides a function call that works as advertised.
-
-`error_handler` provides a unified location to send those pesky **case** issues. This can make tracking issues easier.
- Depending on the paramters, it could show the error, do nothing, or show some alternate text.
-
-`figure_exists` provides a replacement for `figflag`
-*the above is severely outdated*
-
-## catalog / catalog views
-
-you load data into a `ZmapCatalog`. This is kept in `ZmapData.primeCatalog` (used to be 'a')
-You filter it via `catalog_overview` , which yields `ZmapData.Views.primary` containing a `ZmapCatalogView`. The `ZmapCatalogView` is the go-between between the catalog and the maps. Changing the view ranges will leave the primary catalog intact.
-
-A `ZmapCatalogView` can be attached either to a globally accessible `ZmapCatalog` or `ZmapCatalogView`.
-
-Layers within the plotting map are actually an array of `ZmapCatalogViews`, located in
-`ZmapData.Views.Layers`. Ranges in these views can be changed, and they will affect
-the data being displayed. I would have liked to use `linkdata` to automatically update
-the maps, but it appears to get bogged down very quickly as it is used.
-
-When a polygon is created (circle or other shape), it can be used to further filter the
-`ZmapCatalogView`. the working catalog (either newt2 or newcat, I don't remember which)
-is the current polygon applied to `ZmapData.Views.primary`
-
-To get a `ZmapCatalog` from a `ZmapCatalogView` using the `ZmapCatalogView.Catalog` function.
-
-## selections and grids
-
-# other general things to tackle project-wide
-
-* `lasterr` not recommended (88 results, 64 files) since 2009b
-* `fileparts`, remove 4th output (versn) (6 results) [done] since 2010a
-* `isstr` not recommended, use `ischar` (150 results, 68 files) [done] since 2010a [mapseis, too]
-* `str2mat` replace with `char` (4 results, 2 files) [done] zmap
-* `strread` replace usage with textscan. (97 results, 40 files) [in AddOneFiles] since 2010a
- * ex. [a,b,c]=strread(...) => C= textscan(...); [a,b,c] = deal(C{:}) since 2010a
-* `strvcat` replace with char (4 results, 3 files) [done] since 2010a
-* `textread` replace with textscan as above, and use fopen/fclose. (31results, 3 files) since 2010a
-* `sprintf` - not necessary for error text (74 results in 14 files)
-* `eval` - replace in favor of actually doing the thing (1567 results, 364 files)
- * `eval(do[,err])` - replace with a try/catch (174 results, 82 files)
-* `evalin` - ensure use makes sense (44 results, 14 files)
-* `NaN` - be consistent about capitalization, and do not create matrix with ones()*nan or zeros(*nan)
-* `NaN` - cannot compare with ==, use isnan() instead. only a couple places [done]
-* `error(nargchk...)` - replace with narginchk or nargoutchk [done] since 2011b
-* `hdf_funs.m` - probably outdated. matlab has built-in version hdfread, hdfinfo
-* error and warning message identifiers have changed since 2012b. info at: http://www.mathworks.com/support/solutions/en/data/1-ERAFNC/?solution=1-ERAFNC -- see pdf
-* `num2str` - for large integers, use int2str(x) instead. (manymany, but probably affects very few)
-since 2013a
-* `addParamValue` - replace with `addParameter` for an input parser. [done] r2013b
-* `flipdim` - replace with `flip` (45 in 19) [done] r2014a
-* `bitmax` - replace with `flintmax` [done]
-* `layout` gone. no replacemnt, in 1 file.
-* HitTest, Selected, and SelectionHighlight properties for several ui components shouldn't be used r2014a
-
-* remove DateStr2Num, is no longer used anywhere. cursory test shows this causes a long delay.
-* remove DateConvert. also unused
-
-* remove MacMarone - doesn't seem to be used, and is likely an unneeded layer of abstraction. Also.. requires compilation for system and has large disclaimer on web page (dated 2014).
-
-* consider new storage options where it makes sense: DateTime, table, timetable, timeseries, tscollection, containers.Map, duration, categorical arrays (especially DateTime and Catagorical Arrays)
-
-* provide help tooltips for menu items. Perhaps functions could provide their own tooltip text
-* provide description (and a REFERENCE!) for each function.
-* identify and prioritize Zmap functions for incorporation into MapSeis
-* clearly define how to convert a script from Zmap into MapSeis -->automation tool?
-* clearly define how functionality can be added to MapSeis
-
-* investigate required actions (documentation? coding? examples?) to facilitate use of MapSeis / Zmap. How do I add functionality? How do I make a script that leverages this?
-
-* assocArray() is not needed [EXCEPT FOR BACKWARDS COMPATIBILITY?] use containers.Map instead. (introduced matlab 2008b)
-
-* remove "backup" files. Let versioning system (git) take care of remembering past versions of stuff.
-
-* **remember to keep zmap compatible with mapSeis**
-
-# previous authors/contributors
-
-*Stefan Wiemer ~ca 1994-1999
-*Danijel Schorlemmer* ~ca 2003
-*Jochen Woessner*
-*Matt McDonnell* mapseis
-*David Eberhard* mapseis (after Matt?)
-*Carlos Adrian Vargas Aguillera* - cm_and_cb_utilities
-*Peter J. Acklam*
-*Denis Gilbert*
-*Morris Maynard*
-*Anders Brun*
-*Elmar Tarajan*
-*Deidre Byrne*
-*Michael W Mann*
-*Thomas van Stiphout*
-*Elvis Chen*
-*cpouillo*
-*Jiancang Zhuang*
-*Joaquim Luis* - wrote Mirone?
-*R. A. Baker* '98
-*Jan Simon* [matlab]
-*Joseph Kirk*
-*R Pawlowicz*
-*D. L. Hallman*
-*Bob Hamans*
-*R Cobb* 11/94
-*Quan Quach* 12/12/07
-*A Kim*
-*W Strumpf*
-*E Byrns*
-*L Job*
-*E Brown*
-*Annemarie*
-*M Hendrix* - calendar2.m see matlab central
-*D. Kroon*
-*Doug Harriman*
-*Brandon Kuczenski*
-*Colin Humphries*
-*Dave Mellinger*
-*Gerry Middleton* '95
-*T Debole*
-*Takeshi Ikuma*
-*Karaen Felzer* 2007
-*Ramon Zuniga*
-*Alexander Allmann*
-*Guiseppe Cardillo*
-*Dahua Lin* 2008
-*A. M. Zoubir* 1998
-*D R Iskander* 1998
-
-# Adding Focal mechanisms
-
-look at:
-Focal Mechanisms:
-https://ch.mathworks.com/matlabcentral/fileexchange/61227-focalmech-fm--centerx--centery--diam--varargin-
-
-Moment tensors can be retrieved from places like:
-http://www.isc.ac.uk/cgi-bin/web-db-v4?event_id=610635717&out_format=IMS1.0&request=COMPREHENSIVE
-http://www.isc.ac.uk/iscbulletin/search/webservices/
-and IRIS's SPUD
-http://www.isc.ac.uk/iscbulletin/search/webservices/
-
-# uncertainties, EVENT data
-
-# completeness maps precalculated on the web
-
-completenessweb.org
-
-## ADDING FUNCTIONALITY
-
-[Adding Functionality](ADDING_FUNCTIONALITY.md)
\ No newline at end of file
+[How Do I...?](HOWDOI.md)
\ No newline at end of file
diff --git a/working/lastcatalog.mat b/working/lastcatalog.mat
index b1875901..37bc89a7 100644
Binary files a/working/lastcatalog.mat and b/working/lastcatalog.mat differ