I'm not an expert on this part of the data model, but looking at the code,
it is trying to match up the one-bond transfer isotopes of the root
experiment and the target experiment, and since HNCO has H bound to N and
N bound to C my guess is that the code by accident is picking up H and C
or N and C as the two isotopes to do the matching rather than H and N.
But Tim and/or Rasmus would have to confirm this. Well, this is what
could give rise to the immediate problem you have. If that was fixed
there possibly might be another problem downstream, but Tim would be
the best person to know about whether the code was intended to work for
HNCO or not.
On Wed, 27 Jan 2010, Rodolfo Rasia wrote:
> Hi everybody,
> I tried to use an HNCO peak list as root to pick my other triple resonance
> spectra (I upgraded from analysis 2.0 to 2.1 just to get that feature). I
> get this message: "Could not find equivalent dims in spectra XXX & YYY". It
> does work OK when using the hsqc list as root. I also found that when I
> select a root it navigates to all 3 dimensions in the spectrum being
> assigned, not only HN and N, so I am out of the "interesting" region (let's
> say the CA/CB region). What am I doing wrong?
> Another question, is there a way to create a 2D peaklist from a 3D one (to
> get the peaks from the HNCO to the HSQC)
> Thanks in advance
> Rodolfo Rasia