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

NMtran could not be initiated (the NMtran output file FDATA is missing) #257

Open
liangqiongyue opened this issue Feb 25, 2024 · 4 comments

Comments

@liangqiongyue
Copy link

          Make sure that you can run NONMEM correctly without PsN, i.e. try ```C:\nm7C\ver7_20100223\gf\ref\run\nmfe7 run1.mod run1.lst```

Originally posted by @rikardn in #141 (comment)

@liangqiongyue
Copy link
Author

Hello, I encountered the same problem. I followed your prompts and ran the nmfe7 run1.mod run1.lst command. You can see that it can run smoothly.

image

Please tell me what should I do next.

Thanks

@liangqiongyue
Copy link
Author

image

@rikardn
Copy link
Member

rikardn commented Mar 4, 2024

Something is fundamentally wrong with running your model. Check the run directory and see what files were generated in the NM_run directories.

Another thing: I would not use the parafile in this case. It will mix two methods of parallelization. Either use only threads or parafile together with nodes. This could even be the source of the error.

@liangqiongyue
Copy link
Author

liangqiongyue commented Jul 3, 2024

Hi rikardn,
I utilize the '-parafile=pirana_auto_mpi. pnm' option because I intend to leverage multi-core processing to expedite the model's execution time.

Following your guidance, I have combined the '-parafile=pirana_auto_mpi. pnm' with the '-nodes=32' directive, but I am encountering the same error. What steps can I take to resolve this error while still employing multi-core execution?"

微信图片_20240703153149

Something is fundamentally wrong with running your model. Check the run directory and see what files were generated in the NM_run directories.

Another thing: I would not use the parafile in this case. It will mix two methods of parallelization. Either use only threads or parafile together with nodes. This could even be the source of the error.

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