Invalid Floating Point Operation
Invalid Floating Point Operation
(OP)
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.
RE: Invalid Floating Point Operation
This problem occurs only for zero areas when the surface description includes the "% imp" text. Descriptions without this text can handle a zero area without any problems. So it is only the "% imp" items that you will need to remove.
This is a known problem in HydroCAD 8.0, related to the new reporting of pervious vs. impervious areas. It was never intended that a subcat would include zero-area surface descriptions, however, this capability will be restored in the next replease. Also note that HydroCAD-8 includes a new "Area Listing" report for project-wide reporting of CN usage, which may eliminate your need to include zero entries.
For further details, a complete list of status bulletins is always available by selecting Help | Check for Update in HydroCAD. This item is covered by bulletin 108.
RE: Invalid Floating Point Operation