respec / basins Goto Github PK

Indicator bacteria should be added as one of the constituents that should be included in the constituent balance report.
Other constituents can be metals, heavy metals, pesticide etc.

HSPEXP+ should be able to generate following QA/QC Reports

1. Compare parameter values to typical limits and report any issues.
2. Calculate land use areas of all terminal reaches and calibration reaches and report their values.
3. Compare loading rates of land uses to target loading rates and report any loading rates beyond the target.
4. Report any land uses that behave inconsistently (for e.g. more surface runoff from forest than cropland).
5. Report any storage that consistently increase or decrease during the simulation period.
6. report issues with diurnal variation of DO and temperature (for e.g. temperature should be lower in the night).

Can you provide the exact reference for the equation that you used to convert radiation to equivalent evaporation at following line.

I'm sorry if I missed something very basic, but I extracted the files and folders and I can't find anything that will open for GWToolbox 1.3.3. Is there an executable file I am missing?

Installed HSPEXP+ 2.0 beta3, but the splash screen showed 2.0 beta 2

We are now using ATCoUnits.xml and therefore do not need the mdb file.

When viewing both a 'Timeseries' and 'Flow Duration' graph of the same data, the behavior of the graph when a dataset is removed in 'Select Timeseries' is different. On the 'Timeseries' graph, the curve showing the data disappears, on the 'Flow Duration' graph, the data still appears.

If a user provides CFSAEX value as 0 (for e.g. for pipes), HSPF assumes that no value has been provided, and assigns a value of 1.00 to the CFSAEX parameter of that reach.

BASINS4.5 DEM grid legend editor is very sluggish from launch (it takes a long time to fully open) to any type of interaction (such as scrolling or resizing or simply moving its window). Trial from Windows 10 OS.

WinHSPF 3.1 requires the existence of a timeseries in the output wdm before the model is run (assuming a previous output wdm exists). A workaround so far, is to run HSPF from HSPEXP+ (or other HSPF executable) and this seems to alleviate the issue.

When WinHSPF is used to generate output at a certain location in the model, winHSPF should also offer to make a graph specification file, or add to the current graph specification file so that the output can be plotted as simple time series.

Hi,
I am trying to run hydrology calibration using HSPEXP+. I added both observed and simulated flows to the WDM. When hitting start, I get an error saying the number of sites are not in the correct format.
Any insights?

Thanks
Karoline Qasem, PhD

in atcGraph the log y axis default range for a timeseries with 0 values goes too close to zero. see attached.

suggest making the default minimum 0.001 rather than 0.0000001 or displaying axis labels in exponential format with a limited number of orders of magnitude (9 in example), could be 4 or 5.

On my first run of HSPEXP+, I received this error. Any insight? Thanks!

The manual delineation plugin adds minimum and maximum elevation as an integer field. The values extracted from the DEM are also extracted in integer variables. This ends up generating 0 values for slope in small and/or flat reaches.

When BASINS is used to make a new model, the parameters such as SLSUR, LSUR, ELEV, and LAT are not generated for each individual PERLND and IMPLND. These values are calculated by BASINS for each subbasins and they are then applied to multiple PERLND. A modeler generally has to generate these values separately and update the model.

.

Using WinHSPF 3.1 to develop exs files for HSPEXP+. When saving the modified UCI file, the FTABLES that represent surface storage are stripped out. These are perfectly valid FTABLES with only 2 columns.

atcData - SARA Timeseries Utility - remember default attributes displayed on form 'Select Timeseries' between uses of program. User's may want a default set of attributes that includes something more or other than 'Scenario, Location, Constituent'

When hydrology calibration option is selected at a reach, WinHSPF should automatically offer to make a basins specification file (*.exs) file at that location.

WinHSPF should also select storm dates automagically at this step.

1. DO and Heat anomaly calculations are not dependent upon selecting the option on the interface. These calculations happen regardless.
2. DO and Heat anomaly calculations include entire period of data in the WDM file rather than the time period selected in the interface.
3. DO and Heat Diurnal analysis details page does not use the same style page as the QA/QC report.

According to the WDMutil manual, the data set numbers for precipitation is from 11 to 191.
However, I have 12 precipitation datasets, so can I use DSNs beyond 191-- 211, 231, 251, so on?

As mentioned in #24 HSPEXP+ is crashing at/near the end of printing the plots and statistics for one of the calibration gauges. Looking at the gauge calibration results calculated by HSPEXP+ it is obvious that some of the statistics are calculated without regard to missing calibration data.

See zipped up results, which indicate a very large volume error in 'ExpertSysStats-03060101-rch7.txt' and in '03060101.RCH7advice.txt', yet other statistics are calculated correctly (for example, 'AnnualFlowStats-RCH7.txt', 'MonthlyAverageFlowStats-RCH7.txt', and 'DailyMonthlyFlowStats-RCH7.txt').

Most of the stats in 'ExpertSysStats-03060101-rch7.txt' are correct, with total volume being the stand-out incorrect value. There may be others that are also incorrect; I didn't separately recalculate.

The files 'AnnualFlowStats-RCH7.txt', 'MonthlyAverageFlowStats-RCH7.txt', and 'DailyMonthlyFlowStats-RCH7.txt' indicate at the top that the end data was adjusted. There is no similar statement at the top of 'ExpertSysStats-03060101-rch7.txt' - which could solve most of the problem.

Philosophically, I don't fill in observation data. I realize that I am in a minority, but tough. The tools that I use for calibration, mainly TSPROC, does not have a problem with that. I think the ideal situation would be to appropriately work with observation data which might have missing values. I realize the complexity that might be needed to do that, so would gladly settle for automatic adjustment of analysis start/end dates to match the observed data.
Reports_201805241049.zip

POTFS has a limit of 1 – 150. It should be 0 to 10 only.
The value of KMELT should be checked only if degree-day method is active.
Initial PAKTMP can be 0 – 32.
Initial Air Temp be 0 – 40.
POTFW for ORTHOP for impervious area should be checked only if QSD is 1.
The initial value of ZOO parameters should not be checked unless zooplankton are being simulated.
The typical limit for PLNK-PARM2 CMMNP is 0.0001 to 0.028. But the default value is 0.0284 which is greater than the typical limit.

running batch run in the atcIntegratedDesignFlow project resulted in Object reference not set exception as shown below:

All the scientific journals expect SI units in the research papers, it is difficult to take HSPF modeling results directly and present in the paper. The absence of an option for unit selection in HSPF model development is a huge barrier for people who are not familiar with the English units.

When a user is creating a new project in BASINS, there should be an additional option that should ask the user about the units. If SI is selected, the final UCI file should also be in SI units. There should be a starter UCI file in SI Units as well.

.

To avoid having issue with plotting graphs, when user forgot to provide a correct size.

When calculating harmonic mean, it needs to be adjusted if the streamflow record contains zero flow values and gaps. The goal is that only non-missing values are used in harmonic mean adjustment.

This should be updated in both interactive mode and batch run mode.

The starter function is not transferring values from one UCI to another after mapping parameters.

The WinHSPF 3.1 output manager, instead of surgically inserting just what is need to work with HSPEXP+, will also remove lines, comments, and renumber PERLND, IMPLND labels. My UCI files look the way they do, because that is what I want them to look like. The WinHSPF output manager should not make edits that are only stylistic.

This function is used in Regan Plots, and the diurnal analysis of DO and Heat. However, this function returns the entire time series instead of the period selected on the main HSPEXP+ interface.

New date warning when UCI and EXS dates don't match isn't working in 1.20 Beta

Ask the user 'Are you sure want to exit?' when the main window is closed. Choosing the wrong window to close by mistake leads to loss of work.

When using the "Hydrology Calibration Statistics and Graphs" option, HSPEXP+ 2.0beta3 will crash with the following error:

Seems to complete almost everything for the first calibration point, then stops. If additional calibration points are available described in other exs files, nothing is done with them. Since the error seems to indicate a plotting problem here are the plots that are completed:

Flow_RCH7_1990log_.png
Flow_RCH7_1990.png
Flow_RCH7_1991log_.png
Flow_RCH7_1991.png
Flow_RCH7_1992log_.png
Flow_RCH7_1992.png
Flow_RCH7_1993log_.png
Flow_RCH7_1993.png
Flow_RCH7_1994log_.png
Flow_RCH7_1994.png
Flow_RCH7_1995log_.png
Flow_RCH7_1995.png
Flow_RCH7_1996log_.png
Flow_RCH7_1996.png
Flow_RCH7_1997log_.png
Flow_RCH7_1997.png
Flow_RCH7_1998log_.png
Flow_RCH7_1998.png
Flow_RCH7_1999log_.png
Flow_RCH7_1999.png
Flow_RCH7_2000log_.png
Flow_RCH7_2000.png
Flow_RCH7_2001log_.png
Flow_RCH7_2001.png
Flow_RCH7_2002log_.png
Flow_RCH7_2002.png
Flow_RCH7_2003log_.png
Flow_RCH7_2003.png
Flow_RCH7_cumDif.png
Flow_RCH7_cum.png
Flow_RCH7_dur.png
Flow_RCH7_Error_LZS.png
Flow_RCH7_Error_ObsFlow.png
Flow_RCH7_Error_UZS.png
Flow_RCH7log_.png
Flow_RCH7.png
Flow_RCH7_scatDay_log.png
Flow_RCH7_scatDay.png

My model had INTFW values ranging from 1 to 3, but the QA/QC report suggests that the values are 0.75 for all operations.

Belton_Test.txt
I had trouble generating a PET timeseries from data in a .wdm file. When I selected the min temp and max temp timeseries and clicked OK, nothing happened. It worked in BASINS 4.1 doing the same process with the same file.

It didn't work for Hamon or Jensen. It did work for Solar Radiation, though.

Here's the .wdm files (changed to .txt to upload), now with PET data calculated in BASINS, in case it helps.

Right now HSPEXP+ calculations includes only PERLND, IMPLND, and RCHRES operations.

It has been noted by Tim Cera and verified by Anurag, that when you display a time series in BASINS or SARA, it shows that the data has been shifted by one time step.

I have attached examples of outputs.

annie_export.txt
SARA_export_101.txt
wdmtoolbox_extract_101.txt
wdmutil_export_101.txt

Hey,
I created an HSPF model using BASINS. The default PWAT-PARM2 table groups operations together and I need to assign different parameters for different operations.

When I do so in WinHSPF, the table gets messed up (see the images). Any thoughts on how to ungroup operations?

Thanks a lot

Karoline

Hello, I'm having all sorts of problems with SARA. I'm unable to succesfully read my data file. Usually it crashes when it find a 0.0 value (see screenshot).

Any idea how to solve this issue ?

Thanks

HSPEXP+ has all the inbuilt tools to conduct sensitivity analysis, but it needs a proper framework that is simple, and intuitive.

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

1. Simpler to read in a text editor and edit.
2. 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.
3. Specifications are provided in a similar way in additional graphing software like R, MATLAB
4. Can be used by BASINS, SARA, HSPEXP+, or WinHSPF

Cons

1. What to do with the current format?
2. 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.

BASINS does not have the capability to extend an existing time series by appending new data.

EXP+ should look for GENER as one of the sources in Schematic or Network then find a corresponding place in TARGETS block to see if that GENER timeseries being written out. If it is, then add it as a source or warn the users to add a corresponding WDM dataset.

"Chuck Regan" plots are the plots that show the concentration of nutrients (NH4-N, NO3-N, PO4-P, chloropyll a, and Benthic Algae) in a single plot to identify any issue with unstable concentration. These plots may be made using Binary plots for the all the RCHRES for the entire simulation period.

Similarly, make a plot for TSS concentration, bed depth and flow for all the reaches to identify any instability in reaches.

HSPEXP+ should generate output files for BATHTUB and WASP Model.

The loading rates from all PERLND should show up in a simpler table with relevant statistics.

I am trying to generate watershed characterization reports using NLCD data. The process is failing with this message box.

However, the process works for GIRAS Land use data.