Hi Ben,
> However, I have a minor problem with this process. If I export my peak list
> then it only keeps the peak height and not the volume which is fine, but
> when I re-import this then the peak height field is blank and the peak
> height is now a volume.
Ah... I have always assumed (as stated in the XEASY documentation) that,
in example line:
3349 1.683 3.846 1 T 3.984e+04 0.00e+00 r 0 0 0 0
the 6th column encodes the peak height/intensity, the 7th column the error
on this value, and the 8th column the type of integration method (see:
http://hugin.ethz.ch/wuthrich/software/xeasy/xeasy_m3.html#PeakList). This
could have changed in CYANA-type peak lists - let me know if that's the
case.
One question I have is whether in your case CYANA changes the integration
method in the (in this case) 8th column from the original input to the
final output file. This could explain the 'swapping' of volume/height.
The problem remains that you cannot select whether to export the height or
volume to the XEASY/CYANA peak list. I'll have to add some options to the
export menu for that, so not a quick fix, but I'll put it in for the next
release. If you really need it urgently, let me know - you can probably
replace the existing files with the updated ones without messing up the
release you're using.
Bye,
Wim
|