My own guess is that this is a problem related to sky subtraction, not grouping, For one thing, "allstar" does not use the standard grouping used by NSTAR
(and, I believe, by PSF). So, it might be an issue related to sky determination.
You might try setting daopars.fitsky to "yes".But, if you want to experiment with the grouping issue, you can readily
set the maximum number of stars in a group to > 100. I don't think this makes
sense, but you can do it. Simply do a daopars.maxgroup.p_maximum=300 (say)and then you will be able to epar daopars and set maxgroup to a larger value.
But, I don't think this is going to get you where you want to go.The only stars that are going to affect the PSF are those within a PSFrad. I've never heard of restricting this to only 3 pixels, but I sure hope you don't have
>100 stars within 3 pixels of a star you're picking for a PSF star!javascript:emoticon('
')Is there really no light coming from the brightest star you're interested in
beyond 3 pixels? If there is, you need to make the PSFrad to whatever this value is. Sounds like your data is horribly undersampled, and that daophot
isn't a good solution.---phil