I don't think it's a bug, but rather a way of thinking about the data. The
restraint did originate from a peak when it was created, and the software
is just handling the fact that the peak is no longer there in a sensible
way.
As a general principle, I would suggest that analysis gives you a
different (richer, more flexible) way of handling peaks that you don't
want to give rise to restraints than might have been possible in other
software. So rather than deleting crosspeaks from spectra, it is probably
preferable to use the merit attribute to categorise them (and the details
field to annotate the reason for their exclusion) and regenerate restraint
lists, excluding demerited crosspeaks.
On Mon, 20 Jun 2011, Krisztina Feher wrote:
> Dear All,
>
> I generated a restraint List from a Peak List, then I deleted a peak.
> The restraint corresponding to the deleted peak In the Restraints Window
> (attached), however still shows that it has 1 Peak, only the Show Peaks
> button is now grey. If the Peaks column was correct I could just order
> the restraints according to the number peaks and weed out the restraints
> having zero in the Peaks column in one go. Now I either have generate a
> new Restraint List or go through the Restraint List and look for the
> grey Show Peaks button one by one. Is this a bug?
>
> Thanks,
> Krisztina
>
>
>
--
Dr. Brian O. Smith ------------------------ Brian Smith at glasgow ac uk
School of Life Sciences, College of Medical, Vetinerary & Life Sciences,
Joseph Black Building, University of Glasgow, Glasgow G12 8QQ, UK.
Tel: 0141 330 5167/6459/3089 Fax: 0141 330 4600
----------------------------------------------------------------------
The University of Glasgow, charity number SC004401
|