You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you know HSPEXP+ has a functionality to generate graphs automatically based on the specifications provided in a graph specification file (*.csv). Brian and I have used it in MPCA, Illinois River Watershed, Fort Benning, and Fort AP Hill projects. I have used it in BASINS/HSPF workshop as well. Based on my experience at the workshop and interacting with some clients, I learned that the graph specification file is not easy to understand, edit and reuse. It has a steep learning curve. However, clients do like this functionality (Dino, Chuck etc.).
To overcome these issues, I am proposing a new graph specification file format; BASINS Graph Specification File (*.bgrf). An example of that is attached. I have listed the Pros and Cons of this format below.
Most specifications are optional. This means that the user can provide a bare minimum input. Also gives us the ability to add more options later without breaking the format.
Specifications are provided in a similar way in additional graphing software like R, MATLAB
Can be used by BASINS, SARA, HSPEXP+, or WinHSPF
Cons
What to do with the current format?
Need additional money to work on it (EPA, SARA, and may be MPCA have shown interest)
Please read through the attached file and let me know what you think.
The text was updated successfully, but these errors were encountered:
As you know HSPEXP+ has a functionality to generate graphs automatically based on the specifications provided in a graph specification file (*.csv). Brian and I have used it in MPCA, Illinois River Watershed, Fort Benning, and Fort AP Hill projects. I have used it in BASINS/HSPF workshop as well. Based on my experience at the workshop and interacting with some clients, I learned that the graph specification file is not easy to understand, edit and reuse. It has a steep learning curve. However, clients do like this functionality (Dino, Chuck etc.).
To overcome these issues, I am proposing a new graph specification file format; BASINS Graph Specification File (*.bgrf). An example of that is attached. I have listed the Pros and Cons of this format below.
GraphSpecificationFileFormatForHSPEXPPlus.txt
Pros
Cons
Please read through the attached file and let me know what you think.
The text was updated successfully, but these errors were encountered: