OOF2 crashing & work session not saved
hello;
I happened to loose the work session saved few days ago (saved on Friday, could note find on Monday). I had no choice but to start again but the application crushed in the middle of "pixel group assignment" (early on in the process) and is lost again (not saved in "my session" section).
Is this a common problem in here on the nanoHUB?
Is it common problem for the OOF2 application?
kind regards;
MK
0 Like 0 Dislike
Stephen Langer @ on
It's not a common problem with oof2, but that doesn't necessarily mean that it's not a problem with oof2. Is it repeatable? If it is, and you can tell us exactly what to do to reproduce it, then we can try to figure out what's causing it.
-- Steve
Reply Report abuse
Please login to answer the question.
0 Like 0 Dislike
em kay @ on
hello Steve;
thanks for your reply! I will keep my eyes open and will let you know if it happens again and if I will be able to observe a pattern.
best regards;
MK
Reply Report abuse
Please login to answer the question.
0 Like 0 Dislike
em kay @ on
hello Steve;
It is definitely repeatable problem, happening again and again, at least to me it does.
What is causing it? I have no idea. One day, my simulation is there, next day, it is gone. Also, features (e.g. the mesh in the skeleton module) not shown in the graphical window, refreshing or closing & starting the simulation does not seem to work. Perhaps some issues with the memory?
Simulation crashed again in the middle of work, completely lost.
At this point, I am not sure how to continue.
cheers;
M.
Reply Report abuse
Please login to answer the question.
1 Like 0 Dislike
Stephen Langer @ on
Hi M. --
To display objects in the graphics window, use the "New" command in the Layer menu. This is a change from previous versions of OOF2.
When OOF2 crashes, it saves a log file which should help to diagnose the problem. At the moment it's not possible to actually retrieve the file, but that should be fixed soon. (It requires some reconfiguration by nanoHUB.) Until then, the only thing to do is to tell me exactly what you were doing when the program crashed -- What file did you load? How did you load it? How big was it? What commands did you use?
-- Steve
Report abuse