Hello, I am trying to run an analysis using the OpenSees problemtype and after the calculate command , when I choose to go to postprocess, this error appears :
Some errors found in the results file:
Too few numbers for local axis result in line 19 of file 'C:\Users\user\Desktop\tests\test_9.gid\test_9.post.res'.Unknown key '2', in line 20 of file 'C:\Users\user\Desktop\tests\test_9.gid\test_9.post.res'.No results found: definitions for 2 gauss points read.
The .post.res file although has the results that I expect to see in postprocess. The lines that are mentioned have nothing different from all the other similar lines in the file.
What can I do in order to visualize the results and fix this error ??
Results read error
Moderator: GiD Team
Re: Results read error
Attach a zip with the model (the whole .gid folder) to have a look.
Re: Results read error
The error is because the file has comma "," as decimal separator instead of dot "." for one of the results (the other results have number ok)
As the message said the first bug is in the line 19 of file
Result "Local_Axes" "Static" 1 LocalAxes OnGaussPoints "Line_Axes"
ComponentNames "Local-x" "Local-y" "Local-z"
Unit "kN"
Values
1 0,0000 0,0000 4,7124
...
Maybe the solver that has written this file depends on the 'Windows regional settings for number format'.
Real numbers of results must be written always with dot, independently of this setting.
As the message said the first bug is in the line 19 of file
Result "Local_Axes" "Static" 1 LocalAxes OnGaussPoints "Line_Axes"
ComponentNames "Local-x" "Local-y" "Local-z"
Unit "kN"
Values
1 0,0000 0,0000 4,7124
...
Maybe the solver that has written this file depends on the 'Windows regional settings for number format'.
Real numbers of results must be written always with dot, independently of this setting.
-
- Posts: 3
- Joined: Tue Apr 04, 2017 10:58 am
Re: Results read error
I changed the Windows Settings and everything is alright,
thank you!!!!
thank you!!!!
Re: Results read error
Thanks Enrique for the detailed info !
This issue has been fixed in the v2.0.0 update which will be released tomorrow, 8 May 2017.
This issue has been fixed in the v2.0.0 update which will be released tomorrow, 8 May 2017.