> > The underlying problem is that a peak list without any picked peaks was
> > used for generating distance constraints.
>
> Wasn't, either!
Well that was still a potential problem, and a seemingly obvious one from
the trace.
It still looks like an empty peak list was used internally, irrespective
of what may have been chosen. I wasn't trying to blame the user.
This may be a gui problem, e.g. if there is something missing in an update
and an obsolete list was used. More information on how to reproduce this
error would be helpful.
T.
-------------------------------------------------------------------------------
Dr Tim Stevens Email: [log in to unmask]
Department of Biochemistry [log in to unmask]
University of Cambridge Phone: +44 1223 766022 (office)
80 Tennis Court Road +44 7816 338275 (mobile)
Old Addenbrooke's Site +44 1223 364613 (home)
Cambridge CB2 1GA WWWeb: http://www.bio.cam.ac.uk/~tjs23
United Kingdom http://www.pantonia.co.uk
-------------------------------------------------------------------------------
------ +NH3CH(CH(CH3)OH)C(O)NHCH(CH(CH3)CH2CH3)C(O)NHCH(CH2CH2SCH3)CO2- -------
-------------------------------------------------------------------------------
|