Thanks for pointing this out, Matt! Indeed, this is not a crash: it is
intended behaviour. The GUI locks some files for read/write operations
and sometimes people log on on multiple different machines and leave
their GUIs open. To prevent locking problems with too many open
instances of the GUI, the GUI automatically closes itself after one hour
of idleness. However, the jobs are not affected at all.
HTH,
Sjors
Matthew Franklin wrote:
> Hi Cody -
>
> What Takanori meant was to invoke Relion (from the Unix command line) with that idle-time option. In other words, if you usually type "relion" to start the program, you would type "relion --idle 9999999". (Note the double-hyphen.) If you normally start Relion by clicking on an icon, or from some other program, this may not work.
>
> I should also point out that the GUI does not *crash* after 3600 seconds of idle time, it simply closes itself. All Relion jobs are still running; they do not need the GUI to continue. You can simply start the GUI up again, and everything will be there, just as it was. The Relion GUI closes on me all the time, and this is what I do.
>
> Thanks,
> Matt
>
>
--
Sjors Scheres
MRC Laboratory of Molecular Biology
Francis Crick Avenue, Cambridge Biomedical Campus
Cambridge CB2 0QH, U.K.
tel: +44 (0)1223 267061
http://www2.mrc-lmb.cam.ac.uk/groups/scheres
########################################################################
To unsubscribe from the CCPEM list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=CCPEM&A=1
|