>One possibility is that you may already have contaminating shifts in a
>shift list with incorrect values for those conditions (...)
>Here the solution is to delete the orphaned shifts in the BrowseResonances
>popup (...)
Tim, you were absolutely right! Seems to be working fine now (knock on wood).
May I still suggest that a visual clue about which shiftlist is associated
to what spectrum would be helpful?
For example in the 'edit assignment' popup, a peak is referred to as
<spectrum name>:<file name>:<peak list #>:<peak #>, could <shift list #> be
added? Something like ph4:hsqc10:7:1:22 instead of ph4:hsqc10:1:22 (7 being
the shift list number in this example)
A similar clue in the 'atom browser' would be nice too but I can see the
problem when several spectra are associated to the same shift list.
Thanks!
Martin
|