On 04/07/2010 03:12 PM, Robert Hanson wrote: > Rolf, > > I think what's happening is that the image is too complex. There is a > 2-second timeout on the refreshing request, and that is done right before > the image is created. So in general, displays take less than 2 seconds, and > we have no problem. But if a display takes more than 2 seconds, Jmol ignores > the hold and continues -- this was important because in certain situations > Jmol would make a request to the operating system for a repaint, and it > would not be returned for some reason. I'm not saying I really understand > it. But that timeout on the rendering wait fixes that. > > I believe it would work if you did this as a command line job with the -ion > flags set (silent, no console, no display). > With no display there won't be any rendering request. Please do try that. > I tried the command line job and it worked. (It took about 4.5 hours real time.)
Would it be possible to set the timeout length dynamically or at least make it manually configurable? Regards, Rolf ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
