JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CCPEM Archives


CCPEM Archives

CCPEM Archives


CCPEM@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CCPEM Home

CCPEM Home

CCPEM  October 2014

CCPEM October 2014

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Refinment

From:

Qiu-Xing Jiang <[log in to unmask]>

Reply-To:

Qiu-Xing Jiang <[log in to unmask]>

Date:

Mon, 6 Oct 2014 13:40:22 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (116 lines)

Thanks Sjors.
Then we are doing it similarly to what you suggested. We have been
limiting one thread per core in Relion, and the refinement process we have
been running is using 20 processors from 5 computer, where each processor
has 32GB RAM and each computer has 128 GB RAM and 32 processors. We found
that 16GB per processor is the minimum so that the last step of the
refinement would not quit due to insufficient memory. A test process we
ran in 5 machines with 8 processors per machine (16GB per processor) was
found to scale down and become slower per iteration. It appears that the
RAM per processor is a key factor.
Another question is that when the refinement quits in the last step due to
insufficient memory, is it possible to redo memory distribution and
reassign processors by MPI and let relion continue from the last iteration
instead of from the beginning?

Thanks for the clarification of the parameter T in classification. We
probably donıt need to do it.

Best, 
Qiu-Xing


On 10/6/14, 2:19 AM, "Sjors Scheres" <[log in to unmask]> wrote:

>Dear Qiu-Xing,
>The more cores the faster relion will run, but it does matter how you
>divide these cores among MPI and threads. Up to say 50-100 MPI processes,
>MPI scales much better than threads in relion-1.3 (this will probably
>change in relion-1.4). This means it may be worth to run more MPIs and
>fewer threads, but that would be provided your reconstructions fit in RAM.
>If you mean to day you have 20-core nodes with only 32Gb of RAM each, then
>running 20 threads may be necessary with that image size, as otherwise you
>run out of RAM.
>
>About the angular accuracy: yes this is normal in the beginning but it
>should go away in a few iterations. The parameter T is explained in
>Scheres JMB 2012, it is a user-controlled parameter to prevent overfitting
>in classification runs, where gold-standard FSCs are not possible. This
>remark of using T and 3D-classification with a single reference is only
>true for VERY difficult data sets, in general you should not have to worry
>about this. From the box size I infer your particle is rather big, so if
>you've collected good data, it should refine fine.  (If you use a very
>small pixel size and stay well below half Nyquist, you may also consider
>to downscale the particles upon extraction, so your runs will go faster.)
>
>HTH,
>S
>
>
>
>> Dear all,
>> We have been running a refinement process for a dataset that is about
>> 50,000 particles and each image 384x384. We found that the refinement
>> speed has been fairly slow. For a 20 core parallel run, each core was
>> assigned 32 GB RAM, each iteration takes about 12 Hrs. The question is
>> whether adding more processors will make it run faster and whether the
>> RAM
>> assignment needs to follow certain rule of thumb.
>> Also at the beginning of the runs, the accuracy angles > 10 degrees and
>> Relion complained about poor accuracy. Is this usual? Also Relion
>> suggests
>> that " Sometimes it is better to tune resolution yourself by adjusting T
>> in a 3D-classification with a single classİ÷. What is the reasoning
>> behind
>> tuning resolution by adjusting T in 3D classification?
>>
>> Thanks.
>> Qiu-Xing
>>
>>
>>
>> On 10/3/14, 6:31 AM, "Sjors Scheres" <[log in to unmask]> wrote:
>>
>>>Hi Joel,
>>>As explained in the eLife paper, we used MOTIONCORR first and then did
>>>the polishing in RELION for gamma-secretase. Polishing still improved
>>>resolution from 4.9 to 4.5A. We now often take this approach, also for
>>>larger complexes.
>>>HTH,
>>>S
>>>
>>>On 10/02/2014 10:31 PM, Joel Meyerson wrote:
>>>> Hi Sjors,
>>>> Can you comment on whether particle polishing should be used on data
>>>> that was pre-aligned using a routine such as UCSF motioncorr? My
>>>> concern is that using pre-aligned data would later perturb the motion
>>>> modeling done for particle polishing.
>>>>
>>>> Thanks,
>>>> Joel
>>>
>>>--
>>>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
>>
>>
>> ________________________________
>>
>> UT Southwestern Medical Center
>> The future of medicine, today.
>>
>
>
>-- 
>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
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager