I have a Marc version 15 input file which gives me an error when i submit it manually using run_marc -jid. However in Mentat 2023 everything is OK when submitting the job. What is the difference?
I have a Marc version 15 input file which gives me an error when i submit it manually using run_marc -jid. However in Mentat 2023 everything is OK when submitting the job. What is the difference?
Input file version 15 should work with Marc 2020 and later versions. Which version of Marc you are using in the run_marc command ? Also what is the error message ?
I have the latest version of Marc and Mentat, 2023. In the log file I have
*** error - no material assigned to element number 17
*** error - no material assigned to element number 18
*** error - no material assigned to element number 19
*** error - no material assigned to element number 20
*** error - no material assigned to element number 21
*** error - no material assigned to element number 22
*** error - no material assigned to element number 23
*** error - no material assigned to element number 24
*** error - no material assigned to element number 25
*** error - no material assigned to element number 26
error message suppressed for 6 items
When submitting with Mentat there is no such error. I checked and everything seems fine. Do I need another option when using run_marc -jid ? Is Mentat using more options? Is it related to table-driven input? In Mentat you have to tell old style or table-driven input in the job options.
The actual problem is I have to modify the input file without using Mentat and I have to compile it manually. For some particular options in the hydrodynamics field you cannot use Mentat.
There are keywords required in the command when certain features such as user subroutine, pre state , restart etc.. are used. If you are using a user subroutine, then you need to call the subroutine file using use " -u usersubname"
ex: ...\run_marc -j e2x4 -user u2x4
Table driven input / old style is mentioned in the .dat file. can you share the marc input file here or via a support ticket ?
I could run it using command successfully. Here are the files and command window screen capture for your reference. I renamed the file to make the file name short and placed it in a directory with short path.
Is there a limit for the file length and for the path？And why it gives me an error on the material？It should write file name too long or path too long.
I found the problem. I have also an older version installed and the PATH variable was on the old version. Thank you! I couldn't have seen the error without your help.
