Develop specact 1

[rburghol]

Simple special ACTION integration with full STATE support (see #90). I have outlined the process and functions needed to integrate other special actions (and any advanced components) in #127

Note:

• The date matching facility is not yet implemented
• The short hand which allows users to repeat the same action for from RANGE1 to RANGE2 segments not yet implemented
  • need to decide where to do so, in the parser, in SPECL.py object loading, in a SpecialAction object creation method, or static method called from SPECL.py
• Need to discuss and decide on verbose domain specific paths are needed or not, for example:
  • Old special ACTIONS only gave a variable name, and segment ID, such as IVOL, and did not give the activity, such as HYDR, thus the function only has info to give a path like /STATE/RCHRES_R001/IVOL, which could allow for collisions.
  • Current proposed method of storing STATE for things like IVOL, use a domain specific path which includes activity, such as /STATE/RCHRES_R001/HYDR/IVOL
  • If HSPF has no name collisions, it is totally OK to use the shorter nomenclature, but it is a trade-off between extensibility and convention. To support the more verbose proposed method we would need some sort of function to perform a lookup, i.e. like def find_hspf_activity(varname)