Example Error

technical aspects of .dri file generation (e.g. debug mode ) etc...
Post Reply
SteelOx
Posts: 11
Joined: Mon Dec 07, 2020 10:17 am
anti_bot: 333

Example Error

Post by SteelOx » Wed Dec 09, 2020 11:16 am

Hi All,

I'm trying just to run the example T009_CastIronDentriteNodules, But i cannot run it unchanged, does anybody know why and how to solve this problem?

Thanks for the help
Regards

David
Attachments
MICRESS Error.PNG
MICRESS Error.PNG (65.94 KiB) Viewed 4289 times

ralph
Posts: 167
Joined: Wed Apr 27, 2011 4:42 pm
anti_bot: 333

Re: Example Error

Post by ralph » Wed Dec 09, 2020 12:12 pm

This is a copy&paste bug left in this training file for version 6.4.
Just delete the 'smooth 30.0' option which does not make sense here and run it again.

Best,
Ralph

chewyx
Posts: 1
Joined: Wed May 31, 2017 3:51 pm
anti_bot: 333

Re: Example Error

Post by chewyx » Fri May 07, 2021 4:17 pm

I am trying to simulate the example file A006_CMSX4 but I got the error: Please specify a simulation name in your driving file. I am not sure what it means. Please assist. Thanks a lot for your help.

Chew Youxiang

Bernd
Posts: 1504
Joined: Mon Jun 23, 2008 9:29 pm

Re: Example Error

Post by Bernd » Sat May 08, 2021 11:09 pm

Dear Chew,

Welcome to the MICRESS forum.

Without seeing the output you got it is difficult to find out what could have gone wrong. Are you sure that the version of the executable is consistent with the version of example A006? If you get this error when using MICpad, it could be that the "Run Configuration" was preset wrongly and points to a wrong MICRESS version. Or perhaps you try to run an older version of A006 with version 7.0 of MICRESS...

Which version of MICRESS do you have? Can you show the screen output you get?

Bernd

ralph
Posts: 167
Joined: Wed Apr 27, 2011 4:42 pm
anti_bot: 333

Re: Example Error

Post by ralph » Mon May 10, 2021 9:33 am

This is an error message coming from MICpad. The editor was not able to find the specifified output location in this case.
If you use MICpad 7, you can check the syntax of your driving file from the (see main menu).

Note, that MICpad 6 cannot parse syntax of MICRESS 7. You can always pass the driving file to the MICRESS application itself to get the underlying error message.

Best,
Ralph

Post Reply