> *but the copy function doesnt seem to copy all peaks. is there a pick
> finding parameter set for copying peaks as well??
The peak list copy function has undergone some changes since the last
release, so hopefully these points will be addressed for the next release
(Friday maybe).
The original peak list copy function did not clone peaks, rather it picked
again in the same locations. It used the same peak finding parameters as
the general peak picker (Set in Crosspeaks::Peak Find Parameters). If
you've not got peaks in the expected places, this may be because the data
maxima have moved or are not present.
The next relase contains functions to copy by picking and to make an exact
clone (thanks in part to Rasmus's new Data Model copySubtree function).
> *from the main menu i have options to copy all the peaks from one spectrum
> to the other. how to i just copy selected peaks.
Currently you cannot do this. Generally the idea we have is that people
should be picking peaks based upon the data in the spectrum. Nevertheless,
I may well add this option in, with appropriate warnings so that the user
knows when a peak is assumed rather than found.
For the moment, if practical, I suggest you copy all peaks in a peak list
and delete the ones you don't want.
Tim
-------------------------------------------------------------------------------
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- -------
-------------------------------------------------------------------------------
|