cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Allow User to Turn Off Automatic Deletion of Temporary Result Files on Solvers

Allow User to Turn Off Automatic Deletion of Temporary Result Files on Solvers

We've noticed when trying to use the 2017 job manager a couple of issues with getting results (in addition to previously mentioned general issues with the job manager):

 

  -Results occasionally disappear completely after the analysis is 'complete'.  Sometimes the log file is populated with all of the information and has completion times, but there are no results to match.

 

  -Temporary files don't exist after analysis completion.  When a complete set of results don't copy over correctly in 2016 and prior releases we would go to the solver and copy the files from the temporary directory to the network manually, delete the rfn files, then reopen the mpi file.  Most of the time this would make the result files show up complete as long as the analysis completed without issues.

 

We've found out that the temporary files are deleted immediately after the job is copied over to the network.  If for some reason there was an issue with the transfer of files then it deletes the files anyways and they are gone for good.  This is a MAJOR issue.  We can't even have a slight chance that results will be gone for good after running the analysis especially when a study takes 2+ hours to run.  We need to be able to go back to the temporary files and copy them to the server as a fail-safe otherwise running analysis in 2017 is too risky.

 

I understand if this is a necessary step with the cloud, but when we are running things on a local network we don't have to worry about the same security threats such as temporary files being stored.

 

My request is that there be an option to turn off the deletion of the temporary files.  Or even better, just make it so that the temp files are only deleted when the analysis was run on the cloud.  Because right now in our opinion it is not usable.

6 Comments
laura_stuart
Explorer

I've experienced the same problems and would also like temp files to remain when on internal servers/computers.

M.Brassel
Advocate
I think it's even more important to have a robust job manager that does not lose results during transfer. Shutting down one of the involved computers (either client or server) during or after simulation, before the data has been transferred, leads to problems.
Anonymous
Not applicable

Agreed.  I'm constantly trying to figure out what I can do to minimize issues... just to be safe I usually leave the analysis window open while it solves.  However, that doesn't always work.  I'm running an analysis as I type this that takes over an hour to run and the results disappeared.  The log file is still going, though, but I don't know if the results will actually transfer over.  I have to wait until this completes to know if I have to re-launch it.  Incredibly frustrating.

laura_stuart
Explorer

I'm in the same situation, except our typical studies take 12-20 hours to run, so running overnight, unattended is our only option and when we come in the next day, there are no results to show even though it says Complete in the job manager.  I've lost 75-100% overnight productivity due to this issue.  Any word from Autodesk about when/if this will be fixed?  The only thing I have heard is that it won't be fixed by R2 in October and I have not heard of any plans to fix it at all.

Anonymous
Not applicable

Laura - do you run jobs on your machine or do you launch them to solvers?  We do the latter and were wondering if the missing results issue was a data transfer issue.  That does not discount the need for temporary files to be stored.  We were just wondering what others' experiences were.

 

Also, we haven't checked R2, but you mentioned it didn't look like it was to be fixed by then.  Was there an update at all from anyone using R2?  We didn't install it yet, because we didn't see any of our issues resolved in the changelog.

laura_stuart
Explorer

We run locally and remotely.  R2 did not resolve the issue for us.  Perhaps R3 will be better.

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea