Migrate to Visum 20
bettinardi opened this issue · 3 comments
ODOT is installing Visum 20 and will conduct tests to determine if Visum 20 creates API connection issues with the ABM, and assuming those can be resolved, if Visum 20 greatly changes / impacts model results.
Visum 2020 seems to be producing different transit skim values for set2 (premium transit). Previously Visum 18 was returning zeros for the set 2 matrices, now in Visum 2020 positive (non-zero) values are being returned.
The code has been updated to work with Visum 2020 (and get the latest SWIM external model improvements). Note that Visum 2020 is still producing non identical matrices between set 1, 2, and 3. So rounding logic was added to SOABM.py:
https://github.com/RSGInc/SOABM/blob/master/template/scripts/SOABM.py#L875
After the issue is resolved in Visum 2020, this temporary rounding logic should be removed (or at least the rounding reduced). As a reminder, the largest matrix difference was found in cell 9 (row), 20 (column) in the AM period (tap_skim_am_set1 and tap_skim_am_set2).
Since SOABM is not setup to have different skims for set 1, 2, 3, the rounding logic should be fine for this implementation, but would need to be removed before using in an area like Metro (that would use each skim set).
Missed one additional reference to Visum in:
template\inputChecker\scripts\inputChecker.py
Updated the set of two Visum pointers in that script to Visum 2020