⇤ ← Revision 1 as of 2008-01-24 05:33:40
Size: 781
Comment:
|
Size: 1266
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
I have run refine2d.py on different datasets with different number of particles (2000 to 4000) as follow: | '''Q: '''I have run refine2d.py on different datasets with different number of particles (2000 to 4000) as follow: |
Line 13: | Line 13: |
'''A: ''' The first iteration of refine2d always produces 10 iterations, but after that it should have how ever many you specified. Are you seeing iter.1.hed/img iter.2.hed/img, etc. files ? Are you looking at iter.final.hed ? The EMAN2 v1.9 message is a typo in the software. Are you using the 1.8 release version or a nightly snapshot version ? If you are using 1.8, try a snapshot and see if the problem is fixed. If not, submit additional info on this page... |
Q: I have run refine2d.py on different datasets with different number of particles (2000 to 4000) as follow:
refine2d.py start.hed --iter=8 --ninicls=30
As a result it was produced always 10 classes for each dataset I have tested. Even I changed ninitcls= to 50 , 5, or 20 always 10 classes were created. According wiki there is possible to specify number of classes.
I am using EMAN v1.8. After running refine2d.py --version the output is: EMAN2 v1.9.
On other linux box I have installed EMAN v1.7 and in this case the syntax is little bit different: I can specify number of classes as --ncls= together with number of initial classes --ninitcls. And the calculated number of classes are according specified --ncls=.
Do you have any idea how to fix this problem?
A: The first iteration of refine2d always produces 10 iterations, but after that it should have how ever many you specified. Are you seeing iter.1.hed/img iter.2.hed/img, etc. files ? Are you looking at iter.final.hed ?
The EMAN2 v1.9 message is a typo in the software. Are you using the 1.8 release version or a nightly snapshot version ? If you are using 1.8, try a snapshot and see if the problem is fixed. If not, submit additional info on this page...