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

FAILED: Log file was not created in time. FEBio likely failed prior to logfile creation! #182

Open
keilove opened this issue Nov 24, 2023 · 3 comments

Comments

@keilove
Copy link

keilove commented Nov 24, 2023

I'm using it to do a biological finite element simulation. The simulation is for a deformation problem of a composite material of a brain tissue and a tumor subjected to forces. But when I run it I get the error Log file was not created in time, I am not sure why, thanks for your help!
data_generator_1.zip

@Kevin-Mattheus-Moerman
Copy link
Member

@keilove thanks for using GIBBON and for posting this issue.

Without the actual models/files I cannot reproduce the error and study it. This is likely a small error in the formatting of the FEBio structure. To find the error yourself you can try the following:

  1. Try to increase febioAnalysis.maxLogCheckTime, e.g. 120 seconds. If you simulation takes long to start this could be the issue. Can you see if FEBio actually starts (e.g. can you identify it as a process that is running e.g. in task manager or equivalent)? If FEBio briefly starts and immediately fails/stops, then this is probably an unexpected error and FEBio crashes. If it does run but is just slow then then additional waiting time could help.
  2. Set febioAnalysis.runMode='internal' (I think you already have this, and see if there is an error message. Perhaps you have none at the moment, perhaps FEBio fails instantly without a message).
  3. Try importing the .feb file into FEBioStudio and see if it produces an error message on import there.

Let me know how you get on with the above.

@keilove
Copy link
Author

keilove commented Nov 28, 2023

@keilove thanks for using GIBBON and for posting this issue.

Without the actual models/files I cannot reproduce the error and study it. This is likely a small error in the formatting of the FEBio structure. To find the error yourself you can try the following:

  1. Try to increase febioAnalysis.maxLogCheckTime, e.g. 120 seconds. If you simulation takes long to start this could be the issue. Can you see if FEBio actually starts (e.g. can you identify it as a process that is running e.g. in task manager or equivalent)? If FEBio briefly starts and immediately fails/stops, then this is probably an unexpected error and FEBio crashes. If it does run but is just slow then then additional waiting time could help.
  2. Set febioAnalysis.runMode='internal' (I think you already have this, and see if there is an error message. Perhaps you have none at the moment, perhaps FEBio fails instantly without a message).
  3. Try importing the .feb file into FEBioStudio and see if it produces an error message on import there.

Let me know how you get on with the above.

Thank you very much for your help, but my problem is still not solved.
First when I set febioAnalysis.maxLogCheckTime to 120, FEBio starts briefly and then fails/stops immediately. Still reporting error: FAILED: Log file was not created in time. FEBio likely failed prior to logfile creation!

Location: runMonitorFEBio (line 203)
Location: data_generator_1 (line 592);
Second I have set febioAnalysis.runMode to internal'.

I am sending you my model stl file zipped hopefully it will make my question more clear to you.
Looking forward to hearing from you!
stl.zip
data_generator_1.zip

@HahSZ
Copy link

HahSZ commented Jan 24, 2024

4s.txt
Hello, I have a question about using tetgen. I inputted 1791 points, but I'm wondering why the error message refers to point 1794. This issue has been troubling me for a long time, and I would appreciate it if you could provide some guidance.
20240124172733

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

3 participants