Bug #4190
closedDogPicker has two maxsize flags
0%
Description
Dear all,
The new DogPicker generates an additional --maxsize flag, thus creating an error when running it. Removal of the tag solves the problem.
/opt/myamisnap/bin/appion dogPicker.py --kfactor=1.2 --runname=dogrun1 --rundir=/gpfs/appion/yztan/16may15a/extract/dogrun1 --commit --preset=enn-a --projectid=211 --session=16may15a --no-rejects --no-wait --continue --pdiam=80 --lpval=10 --hpval=0 --medianval=2 --pixlimit=4 --binval=4 --planereg --invert --minthresh=0.4 --maxthresh=1.5 --maxpeaks=1500 --peaktype=centerofmass --maxsize=1.2 --overlapmult=1.5 --maxsize=1.2 --expid=2119 --jobtype=dogpicker
Updated by Anchi Cheng over 8 years ago
- Status changed from New to In Test
- Assignee changed from Anchi Cheng to Yong Zi Tan
- Target version set to Appion/Leginon 3.3
- Affected Version changed from Appion/Leginon 3.2 to Appion/Leginon 3.3
Interesting bug. Looks like it has been there for a while. With the default set at the same value as in the python file, we will just not to add the special case.
Yong Zi, please check if the behavior of the dogPicker is the same as you intended.
Updated by Anchi Cheng over 7 years ago
- Status changed from In Test to Closed
stabe for a while now.