Hi Sonya,
The GUI is independent from the running job. It closes automatically to
prevent you from having many different ones open on different machines,
which could cause problems (if you do your processing in a nomadic way).
You can just type relion again to have it come back. No worries at all.
HTH,
Sjors
> Hi Sonya,
>
> We often use the "screen" shell on our cluster to insure that the program
> runs indefinitely
> (https://www.gnu.org/software/screen/manual/screen.html).
> Additionally, you can check if your job is running with either the "top"
> command or "nvidia-smi" (if using a nvidia gpu).
>
> Another way to check if any errors have occurred within a specific job is
> to have a look at the run.err file and see if any errors were produced
> within the job.
>
>
> Hope this helps,
>
> Jillian
>
> On Tue, May 2, 2017 at 8:53 AM, Sonya James <[log in to unmask]>
> wrote:
>
>> When running a 2D Classification job the Relion GUI closed after being
>> idle for 3600 seconds. If this happens does my classification job keep
>> running? And how do I open the relion GUI again without interfering with
>> the job?
>> When I typed 'relion' into the terminal to reopen the GUI I had to
>> continue the job......
>>
>> When the job is running I have;
>>
>> Oversampleing= 1 NrHiddenVariableSamplingPoints= 201 600
>> OrientationalSampling= 6 NrOrientations= 240
>> TranslationalSampling=1 NrTranslations= 84
>>
>> Expectation iteration 2 of 25
>> 0.38/1.30 hrs...................~~(,_,''>
>>
>> The numbers at the bottom of this keep changing - does this mean the job
>> is running?
>>
>> Thanks
>> Sonya
>>
>
--
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
|