FigureOuter
Civil/Environmental
- Dec 19, 2005
- 2
In earlier versions, for each specific site we were able make a "template subcat" that contained all possible soil/CN combinations, leaving the "Area" column at zero. As we assemble the model, the template subcat is copied, renumbered and its areas entered in the area column. If a particular soil/CN condition was not contained within that particular subcat then we'd leave the zero in the Area Column.
Now version 8.0 doesn't allow this: when calculating a subcat, the error message "invalid floating point operation" appears. We have determined that this error is caused by the "zeros" in the Area Column of the subcat. The work through is to edit each and every subcat by laboiously deleting the "zero area" soil/CN combinations.
Unless there is a way to rectify this already that I am not aware of, I suggest that the software developers consider allowing zeros within the Area Column and red flag with the "invalid floating point operation" error message only if the SUM of the Area Column is zero. This would make our job in the practice more efficient.
Thank you.
Now version 8.0 doesn't allow this: when calculating a subcat, the error message "invalid floating point operation" appears. We have determined that this error is caused by the "zeros" in the Area Column of the subcat. The work through is to edit each and every subcat by laboiously deleting the "zero area" soil/CN combinations.
Unless there is a way to rectify this already that I am not aware of, I suggest that the software developers consider allowing zeros within the Area Column and red flag with the "invalid floating point operation" error message only if the SUM of the Area Column is zero. This would make our job in the practice more efficient.
Thank you.