Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TransCAD generated OMX skims are not read properly in DaySim #317

Open
nsdhakar opened this issue Aug 18, 2023 · 2 comments
Open

TransCAD generated OMX skims are not read properly in DaySim #317

nsdhakar opened this issue Aug 18, 2023 · 2 comments

Comments

@nsdhakar
Copy link
Collaborator

The OMX format skim files generated by TransCAD are read incorrectly by DaySim. Used the GISDK command "CopyMatrix()" to convert TransCAD format skims into OMX format in TransCAD 9.0. DaySim reads the OMX files successfully, however, the values are read incorrectly (very large numbers) and also do not correspond to correct OD cells in skims. Note that when opened in TransCAD or an OMX viewer or a programming language, the OMX skim files look fine. But for some reason, DaySim is not able to read them correctly.

A workaround is to read TransCAD generated OMX files in a programming language (e.g., R) and re-write back in OMX format. The regenerated OMX skims are read fine in DaySim.

DaySim has been reading OMX files generated from Cube, Emme, or a programming language (e.g., R, python) without issues. This points to a potentially issue in the way TransCAD is generating OMX files. Something to coordinate with Caliper.

@jfdman
Copy link

jfdman commented Aug 18, 2023 via email

@nsdhakar
Copy link
Collaborator Author

@jfdman - yes, sent an email to Vince.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants