Got an error on every example file " string was not recognized as a valid date time"

[Muhammad Rehan Anis]

I could not open any file I got this error on every file what I did wrong with MODSIM setting ????

[Bob Lounsbury]

All I can think of is that this is likely an issue with Region/Language/Date and Time configuration on your machine: http://windows.microsoft.com/en-us/windows/change-dates-times-currency-measurements-display#1TC=windows-7

Does setting the Region Format to English (United States) help?

If you create a new network. Do you also see this error?

What is your current Region Format? Maybe I can reproduce the error and figure out how to correct it.

[Muhammad Rehan Anis]

Thank you the error is now clear. The only error left in Prineville8_1.xy file and the error is "Error reading node forecasr: Line number 2296. The specified label (/) could not be parsed into ModsinUnits."

[Bob Lounsbury]

How did you resolve the error? Is there something we can improve in MODSIM to handle the region/date/time issue or whatever the issue was?

For the last error, open Prineville8_1.xy in any text editor and change line number 2296 to "units acre-ft" (no quotes). Later versions of MODSIM are more rigorous in checking model units before loading the model in the GUI (although I noticed the model does still load, so I may fix that too).

[Muhammad Rehan Anis]

Yes all previous errors are removed now and I got new error in Prineville8_1.xy file and the error is "line number 2292 Can not get TimeSpan on undefined Modsim User defined TimeStep Type""

[Bob Lounsbury]

Sounds like another region/date/time issue. I do not get that error on my machine, so it's pretty difficult to help out here. If you provide your region settings, maybe I can use those and reproduce the error on my machine. Then I can more easily find a solution.

[Muhammad Rehan Anis]

so all the setting in one jpeg

[Bob Lounsbury]

This file corrects the issues Muhammad reported.

[Muhammad Rehan Anis]

thanks yes it works but what was the error

[Bob Lounsbury]

A picture is worth a thousand words, glad you included the xy file in a text editor. Line 2292 should not have quotes around the units it should be units acre-ft/month also line 2296 is still incorrect is should be units acre-ft.

Just use the network I attached to this issue. I also corrected a duplicate link name that was blocking MODSIM from producing output.

We'll update the network in the Tutorials. Thanks for the report.

[Bob Lounsbury]

What was your Region Format previously set to? Although setting it to English is a solution, we might want to look into making MODSIM more internationally friendly.

[Muhammad Rehan Anis]

I have only change the date format all other setting was similar. Please also told me how to see MODSIM output

this output is in MODSIM tutorial page 104

[Muhammad Rehan Anis]

ok I found it on the DEMAND graph

[Bob Lounsbury]

Do you remember what date format you changed? I'd like to see if we can fix your original error.

[Muhammad Rehan Anis]

yes in short date I have changed dd-MMM-yy in to M/d/yyyy

rest was similar

[Bob Lounsbury]

Closes #33. Unable to convert string to proper datetime with non-default Microsoft Windows Short Date Region Format setting. MODSIM now ignores the machine setting. Removed milisecond timestep.

→ <<cset 949eac2cce1e>>

[Muhammad Rehan Anis]

do you have Manual for MODSIM 8.4.3??

[Bob Lounsbury]

Sorry, no, resources are scarce. The MODSIM 8.1 manual available here is still perfectly adequate, not much has changed in the intended operation of MODSIM between then and now.