sam hatchett bd62f399f9 fake data was being written to the binary file. if a link element is nominally closed, even if there's actually flow calculated there, the flow is disregarded upon writing results. so when the flow is read back in, it's zero -- which is different than it would have been if it had stayed in memory. i wonder what that does to mass balance?
this version works, at least with Net3, simplenet, and SampleTown -- but the results are non-canonical, as the current workaround for the issue above writes tiny flow values to the binary file for closed elements. presumably we should check for closed status in the transport() function.
2013-03-09 09:46:12 -05:00
2013-02-04 21:28:27 -05:00
2013-02-05 09:49:59 -05:00
Description
No description provided
11 MiB
Languages
C 78.8%
C++ 8.6%
C# 2.5%
Visual Basic 6.0 1.9%
Visual Basic .NET 1.9%
Other 6.3%