Ah, ok, I missed that point in the first email! I'll have to ask Tim (but
he might not see his email that quickly). So it looks like in the code it
will color things blue when some spinSystem has that residue, and the code
looks simple enough that I can't see how that could be going wrong. It's
possible we'll need to take a look at your project.
Wayne
On Tue, 1 Jun 2010, Marcel Jurk wrote:
> Thank you for your answer.
>
> Unfortunately, the problem is that analysis does not discriminate, in this
> table, between assigned and unassigned sequence positions any longer.
> Everything is marked as assigned (blue). I can perfectly ignore it - because
> the probability for a correct suggestion seems indeed quite low until you
> haven't got a unique stretch - and assign an aa to a sequence position via
> the "Spin Systems" panel as I did before. It just seemed a little bit strange
> to me that the "Sequence Locations" table does not work correctly any more.
>
> Regards,
> Marcel
>
>
> Wayne Boucher wrote:
>> Hello,
>>
>> The "Sequence Locations" table is a suggestion of where in the sequence the
>> selected spin system might belong, so in your case it thinks that spin
>> system {60} might be 187 Asp. That is based on how well the shifts within
>> the spin system match the chemical shifts in the RefDB database (I don't
>> know the detail, although Tim does). So it is not based on the current
>> assignment (the way I understand it). (Tim and Rasmus are in Portugal this
>> week giving a course so hard to ask them.)
>>
>> If you don't want to use that prediction then you can just ignore it. (I
>> don't know how high the score has to be before one might believe it.) So
>> you can just use the "Set Seq Link" functionality in the middle table.
>>
>> Wayne
>>
>> On Tue, 1 Jun 2010, Marcel Jurk wrote:
>>
>>> Hi everyone,
>>>
>>> I am, once again, encountering a strange problem during the course of
>>> assignment. Since this morning, analysis shows all sequence positions as
>>> already assigned in the "Sequence Locations" menu on the bottom left on
>>> the "Protein Sequence Assignment" panel (assign_locations.tiff), although
>>> none of these positions is actually assigned. Assignment status is
>>> displayed correctly under "Chart-->Assignment Graph" (see
>>> assign_graph.tiff).
>>> If a new spin system is assigned to one of the positions with misassigned
>>> status, analysis considers it indeed as assigned and asks for a merge of
>>> both spin systems (non-existing and new). Upon this, sequential links are
>>> disrupted regardless of choosing merge or no merge.
>>>
>>> Everything ran smoothly until today. I installed all the latest updates
>>> last Sunday but hadn't had a problem yesterday. Any suggestions as towards
>>> the root of this evil are very much appreciated.
>>>
>>> Many thanks in advance.
>>>
>>> Regards,
>>> Marcel
>>>
>>> --
>>> Marcel Jurk
>>>
>>> Leibniz Institut fuer Molekulare Pharmakologie (FMP)
>>> Solution NMR (AG Schmieder)
>>> Robert-Roessle-Str. 10
>>> 13125 Berlin
>>> Germany
>>>
>>> eMail: [log in to unmask]
>>> Phone: +49-30-94793223
>>> Fax: +49-030-94793169
>>>
>>>
>
> --
> Marcel Jurk
>
> Leibniz Institut fuer Molekulare Pharmakologie (FMP)
> Solution NMR (AG Schmieder)
> Robert-Roessle-Str. 10
> 13125 Berlin
> Germany
>
> eMail: [log in to unmask]
> Phone: +49-30-94793223
> Fax: +49-030-94793169
>
|