You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running DaySim in estimation mode to attach final skims to daysim outputs, some files crash in Reader.cs. This particularly happens when large files like full simulation daysim data like trips are loaded. The point of failure is here, where the length of the file being imported is converted to an integer: https://github.com/RSGInc/DaySim/blob/master/DaySim.Framework/Persistence/Reader.cs#L41
For large files this causes an overflow of the integer, resulting in a negative value which fails to create a proper index. We've found that the following correction of line 41 will avoid this issue by converting the value to an integer only after dividing the file length by the file's size value:
_count = (int)(file.Length / _size);
The text was updated successfully, but these errors were encountered:
In the Copenhagen version, I changed some id fields to 16 byte integers, which should also solve the problem. Will also do that for the main version.
Sent from my T-Mobile 5G Device
Get Outlook for Android<https://aka.ms/AAb9ysg>
When running DaySim in estimation mode to attach final skims to daysim outputs, some files crash in Reader.cs. This particularly happens when large files like full simulation daysim data like trips are loaded. The point of failure is here, where the length of the file being imported is converted to an integer: https://github.com/RSGInc/DaySim/blob/master/DaySim.Framework/Persistence/Reader.cs#L41
For large files this causes an overflow of the integer, resulting in a negative value which fails to create a proper index. We've found that the following correction of line 41 will avoid this issue by converting the value to an integer only after dividing the file length by the file's size value:
_count = (int)(file.Length / _size);
The text was updated successfully, but these errors were encountered: