Changes between Initial Version and Version 1 of Ticket #19201, comment 2


Ignore:
Timestamp:
Oct 21, 2025, 10:53:38 AM (4 days ago)
Author:
Eric Pettersen

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #19201, comment 2

    initial v1  
    1 It seems like this would need to be wedged into "info chains" somehow, since the "open" command only knows about models, not chains, and doesn't ask for JSON info for the models.  I mean it could do that, the atomic model could include then include the UniProt info , but realistically it should put in a lot more info than just the UniProt chain annotations, which would duplicate much of the effort already put into the "info" command.
     1It seems like this would need to be wedged into "info chains" somehow, since the "open" command only knows about models, not chains, and doesn't ask for JSON info for the models.  I mean it could do that, the atomic model could include then include the !UniProt info , but realistically it should put in a lot more info than just the !UniProt chain annotations, which would duplicate much of the effort already put into the "info" command.
    22
    33Specifically, "info chains /a attr features" almost gets you there now, but Sequence.features is a method.  Some property for getting UniProt annotations would need to be added, that in turn calls Sequence.features(...)