Alternatives Toolkit flags DSCs as disconnected when there are no changes to nearby links

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open the DSCToolPad for certain models with mixed 
sanitary/storm/combined pipes networks (e.g. Kenton basin)
2. Allow the DSCToolPad to check for broken DSC connections
3. Observe that some DSC connections may be flagged as broken, even though 
no changes were made to the pipe network.

What is the expected output? What do you see instead?
One might think that DSC connections should not be flagged as broken if no 
changes were made to the nearby collection system.  However, there may be 
cases where the tool correctly flags broken connections.

For instance, any DSC with DiscoClass="D" must have a valid entry in the 
ToLinkStorm field.  If the DSC discharges via a storm lateral to a storm 
system outside the basin trace, the connection will be flagged as broken.  
This is correct behavior, but it may be unexpected by a user.  Another case 
could be that the Base Model DSC connection was incorrectly specified, and 
the DSCToolPad therefore determines that the connection is broken.

Users should recognize that these cases can occur, and review broken DSC 
connections that occur outside expected areas.  If the broken connections 
are acceptable, i.e. because the storm network is in an adjacent basin, the 
alt_dsc entry should be deleted.  

If the broken connection is due to an underlying data problem in the base 
model, the alt_dsc entry should be deleted and the Base Model should be 
corrected.

Original issue reported on code.google.com by john.hen...@gmail.com on 26 Jan 2010 at 8:14

[GoogleCodeExporter]

Original comment by john.hen...@gmail.com on 5 Mar 2010 at 12:33

• Changed state: WontFix

[GoogleCodeExporter]

Added label

Original comment by ArnelMan...@gmail.com on 6 Oct 2010 at 12:20

• Added labels: ALTERNATIVESTOOLKIT