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
Issue:
The transit skimming process in tm2py generates skim files with the naming convention as trnskmAM_KNR_TRN_WLK.omx. However, there is a second set of transit skim files, named transit_skims_period.omx, which are stored in the transit skim folder. These files are no longer produced but are still used by certain UECs in CT-RAMP. They are being carried around in all the latest model runs to get through this issue.
Details:
The WalkTransitWalkSkims and WalkTransitDriveSkims UECs in CT-RAMP uses the transit_skims_{period}.omx files. These UECs are initialized here and here in the code but appears that these UEC objects may no longer be necessary.
Fix:
Attempts to delete the transit_skims_{period}.omx files have shown that the model crashes without those files in place. To resolve this, Java code changes are required. Specifically:
If the UECs are not needed downstream, we should avoid initializing the corresponding UEC classes.
If the UECs are necessary, the code should be updated to use the correct set of transit skim file.
Issue:
The transit skimming process in tm2py generates skim files with the naming convention as trnskmAM_KNR_TRN_WLK.omx. However, there is a second set of transit skim files, named transit_skims_period.omx, which are stored in the transit skim folder. These files are no longer produced but are still used by certain UECs in CT-RAMP. They are being carried around in all the latest model runs to get through this issue.
Details:
The WalkTransitWalkSkims and WalkTransitDriveSkims UECs in CT-RAMP uses the transit_skims_{period}.omx files. These UECs are initialized here and here in the code but appears that these UEC objects may no longer be necessary.
Fix:
Attempts to delete the transit_skims_{period}.omx files have shown that the model crashes without those files in place. To resolve this, Java code changes are required. Specifically:
cc @DavidOry
The text was updated successfully, but these errors were encountered: