Metadata-Version: 2.4
Name: alphafold3-seqvis-toolkit
Version: 0.2.1
Summary: Visualization & analysis toolkit for AlphaFold3 outputs.
Project-URL: Homepage, https://github.com/MaybeBio/AlphaFold3-SeqVisToolkit
Project-URL: Issues, https://github.com/MaybeBio/AlphaFold3-SeqVisToolkit/issues
Author-email: Joe Hoye Dow <luxunisgod123@gmail.com>
License:                     GNU GENERAL PUBLIC LICENSE
                               Version 3, 29 June 2007
        
         Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
         Everyone is permitted to copy and distribute verbatim copies
         of this license document, but changing it is not allowed.
        
                                    Preamble
        
          The GNU General Public License is a free, copyleft license for
        software and other kinds of works.
        
          The licenses for most software and other practical works are designed
        to take away your freedom to share and change the works.  By contrast,
        the GNU General Public License is intended to guarantee your freedom to
        share and change all versions of a program--to make sure it remains free
        software for all its users.  We, the Free Software Foundation, use the
        GNU General Public License for most of our software; it applies also to
        any other work released this way by its authors.  You can apply it to
        your programs, too.
        
          When we speak of free software, we are referring to freedom, not
        price.  Our General Public Licenses are designed to make sure that you
        have the freedom to distribute copies of free software (and charge for
        them if you wish), that you receive source code or can get it if you
        want it, that you can change the software or use pieces of it in new
        free programs, and that you know you can do these things.
        
          To protect your rights, we need to prevent others from denying you
        these rights or asking you to surrender the rights.  Therefore, you have
        certain responsibilities if you distribute copies of the software, or if
        you modify it: responsibilities to respect the freedom of others.
        
          For example, if you distribute copies of such a program, whether
        gratis or for a fee, you must pass on to the recipients the same
        freedoms that you received.  You must make sure that they, too, receive
        or can get the source code.  And you must show them these terms so they
        know their rights.
        
          Developers that use the GNU GPL protect your rights with two steps:
        (1) assert copyright on the software, and (2) offer you this License
        giving you legal permission to copy, distribute and/or modify it.
        
          For the developers' and authors' protection, the GPL clearly explains
        that there is no warranty for this free software.  For both users' and
        authors' sake, the GPL requires that modified versions be marked as
        changed, so that their problems will not be attributed erroneously to
        authors of previous versions.
        
          Some devices are designed to deny users access to install or run
        modified versions of the software inside them, although the manufacturer
        can do so.  This is fundamentally incompatible with the aim of
        protecting users' freedom to change the software.  The systematic
        pattern of such abuse occurs in the area of products for individuals to
        use, which is precisely where it is most unacceptable.  Therefore, we
        have designed this version of the GPL to prohibit the practice for those
        products.  If such problems arise substantially in other domains, we
        stand ready to extend this provision to those domains in future versions
        of the GPL, as needed to protect the freedom of users.
        
          Finally, every program is threatened constantly by software patents.
        States should not allow patents to restrict development and use of
        software on general-purpose computers, but in those that do, we wish to
        avoid the special danger that patents applied to a free program could
        make it effectively proprietary.  To prevent this, the GPL assures that
        patents cannot be used to render the program non-free.
        
          The precise terms and conditions for copying, distribution and
        modification follow.
        
                               TERMS AND CONDITIONS
        
          0. Definitions.
        
          "This License" refers to version 3 of the GNU General Public License.
        
          "Copyright" also means copyright-like laws that apply to other kinds of
        works, such as semiconductor masks.
        
          "The Program" refers to any copyrightable work licensed under this
        License.  Each licensee is addressed as "you".  "Licensees" and
        "recipients" may be individuals or organizations.
        
          To "modify" a work means to copy from or adapt all or part of the work
        in a fashion requiring copyright permission, other than the making of an
        exact copy.  The resulting work is called a "modified version" of the
        earlier work or a work "based on" the earlier work.
        
          A "covered work" means either the unmodified Program or a work based
        on the Program.
        
          To "propagate" a work means to do anything with it that, without
        permission, would make you directly or secondarily liable for
        infringement under applicable copyright law, except executing it on a
        computer or modifying a private copy.  Propagation includes copying,
        distribution (with or without modification), making available to the
        public, and in some countries other activities as well.
        
          To "convey" a work means any kind of propagation that enables other
        parties to make or receive copies.  Mere interaction with a user through
        a computer network, with no transfer of a copy, is not conveying.
        
          An interactive user interface displays "Appropriate Legal Notices"
        to the extent that it includes a convenient and prominently visible
        feature that (1) displays an appropriate copyright notice, and (2)
        tells the user that there is no warranty for the work (except to the
        extent that warranties are provided), that licensees may convey the
        work under this License, and how to view a copy of this License.  If
        the interface presents a list of user commands or options, such as a
        menu, a prominent item in the list meets this criterion.
        
          1. Source Code.
        
          The "source code" for a work means the preferred form of the work
        for making modifications to it.  "Object code" means any non-source
        form of a work.
        
          A "Standard Interface" means an interface that either is an official
        standard defined by a recognized standards body, or, in the case of
        interfaces specified for a particular programming language, one that
        is widely used among developers working in that language.
        
          The "System Libraries" of an executable work include anything, other
        than the work as a whole, that (a) is included in the normal form of
        packaging a Major Component, but which is not part of that Major
        Component, and (b) serves only to enable use of the work with that
        Major Component, or to implement a Standard Interface for which an
        implementation is available to the public in source code form.  A
        "Major Component", in this context, means a major essential component
        (kernel, window system, and so on) of the specific operating system
        (if any) on which the executable work runs, or a compiler used to
        produce the work, or an object code interpreter used to run it.
        
          The "Corresponding Source" for a work in object code form means all
        the source code needed to generate, install, and (for an executable
        work) run the object code and to modify the work, including scripts to
        control those activities.  However, it does not include the work's
        System Libraries, or general-purpose tools or generally available free
        programs which are used unmodified in performing those activities but
        which are not part of the work.  For example, Corresponding Source
        includes interface definition files associated with source files for
        the work, and the source code for shared libraries and dynamically
        linked subprograms that the work is specifically designed to require,
        such as by intimate data communication or control flow between those
        subprograms and other parts of the work.
        
          The Corresponding Source need not include anything that users
        can regenerate automatically from other parts of the Corresponding
        Source.
        
          The Corresponding Source for a work in source code form is that
        same work.
        
          2. Basic Permissions.
        
          All rights granted under this License are granted for the term of
        copyright on the Program, and are irrevocable provided the stated
        conditions are met.  This License explicitly affirms your unlimited
        permission to run the unmodified Program.  The output from running a
        covered work is covered by this License only if the output, given its
        content, constitutes a covered work.  This License acknowledges your
        rights of fair use or other equivalent, as provided by copyright law.
        
          You may make, run and propagate covered works that you do not
        convey, without conditions so long as your license otherwise remains
        in force.  You may convey covered works to others for the sole purpose
        of having them make modifications exclusively for you, or provide you
        with facilities for running those works, provided that you comply with
        the terms of this License in conveying all material for which you do
        not control copyright.  Those thus making or running the covered works
        for you must do so exclusively on your behalf, under your direction
        and control, on terms that prohibit them from making any copies of
        your copyrighted material outside their relationship with you.
        
          Conveying under any other circumstances is permitted solely under
        the conditions stated below.  Sublicensing is not allowed; section 10
        makes it unnecessary.
        
          3. Protecting Users' Legal Rights From Anti-Circumvention Law.
        
          No covered work shall be deemed part of an effective technological
        measure under any applicable law fulfilling obligations under article
        11 of the WIPO copyright treaty adopted on 20 December 1996, or
        similar laws prohibiting or restricting circumvention of such
        measures.
        
          When you convey a covered work, you waive any legal power to forbid
        circumvention of technological measures to the extent such circumvention
        is effected by exercising rights under this License with respect to
        the covered work, and you disclaim any intention to limit operation or
        modification of the work as a means of enforcing, against the work's
        users, your or third parties' legal rights to forbid circumvention of
        technological measures.
        
          4. Conveying Verbatim Copies.
        
          You may convey verbatim copies of the Program's source code as you
        receive it, in any medium, provided that you conspicuously and
        appropriately publish on each copy an appropriate copyright notice;
        keep intact all notices stating that this License and any
        non-permissive terms added in accord with section 7 apply to the code;
        keep intact all notices of the absence of any warranty; and give all
        recipients a copy of this License along with the Program.
        
          You may charge any price or no price for each copy that you convey,
        and you may offer support or warranty protection for a fee.
        
          5. Conveying Modified Source Versions.
        
          You may convey a work based on the Program, or the modifications to
        produce it from the Program, in the form of source code under the
        terms of section 4, provided that you also meet all of these conditions:
        
            a) The work must carry prominent notices stating that you modified
            it, and giving a relevant date.
        
            b) The work must carry prominent notices stating that it is
            released under this License and any conditions added under section
            7.  This requirement modifies the requirement in section 4 to
            "keep intact all notices".
        
            c) You must license the entire work, as a whole, under this
            License to anyone who comes into possession of a copy.  This
            License will therefore apply, along with any applicable section 7
            additional terms, to the whole of the work, and all its parts,
            regardless of how they are packaged.  This License gives no
            permission to license the work in any other way, but it does not
            invalidate such permission if you have separately received it.
        
            d) If the work has interactive user interfaces, each must display
            Appropriate Legal Notices; however, if the Program has interactive
            interfaces that do not display Appropriate Legal Notices, your
            work need not make them do so.
        
          A compilation of a covered work with other separate and independent
        works, which are not by their nature extensions of the covered work,
        and which are not combined with it such as to form a larger program,
        in or on a volume of a storage or distribution medium, is called an
        "aggregate" if the compilation and its resulting copyright are not
        used to limit the access or legal rights of the compilation's users
        beyond what the individual works permit.  Inclusion of a covered work
        in an aggregate does not cause this License to apply to the other
        parts of the aggregate.
        
          6. Conveying Non-Source Forms.
        
          You may convey a covered work in object code form under the terms
        of sections 4 and 5, provided that you also convey the
        machine-readable Corresponding Source under the terms of this License,
        in one of these ways:
        
            a) Convey the object code in, or embodied in, a physical product
            (including a physical distribution medium), accompanied by the
            Corresponding Source fixed on a durable physical medium
            customarily used for software interchange.
        
            b) Convey the object code in, or embodied in, a physical product
            (including a physical distribution medium), accompanied by a
            written offer, valid for at least three years and valid for as
            long as you offer spare parts or customer support for that product
            model, to give anyone who possesses the object code either (1) a
            copy of the Corresponding Source for all the software in the
            product that is covered by this License, on a durable physical
            medium customarily used for software interchange, for a price no
            more than your reasonable cost of physically performing this
            conveying of source, or (2) access to copy the
            Corresponding Source from a network server at no charge.
        
            c) Convey individual copies of the object code with a copy of the
            written offer to provide the Corresponding Source.  This
            alternative is allowed only occasionally and noncommercially, and
            only if you received the object code with such an offer, in accord
            with subsection 6b.
        
            d) Convey the object code by offering access from a designated
            place (gratis or for a charge), and offer equivalent access to the
            Corresponding Source in the same way through the same place at no
            further charge.  You need not require recipients to copy the
            Corresponding Source along with the object code.  If the place to
            copy the object code is a network server, the Corresponding Source
            may be on a different server (operated by you or a third party)
            that supports equivalent copying facilities, provided you maintain
            clear directions next to the object code saying where to find the
            Corresponding Source.  Regardless of what server hosts the
            Corresponding Source, you remain obligated to ensure that it is
            available for as long as needed to satisfy these requirements.
        
            e) Convey the object code using peer-to-peer transmission, provided
            you inform other peers where the object code and Corresponding
            Source of the work are being offered to the general public at no
            charge under subsection 6d.
        
          A separable portion of the object code, whose source code is excluded
        from the Corresponding Source as a System Library, need not be
        included in conveying the object code work.
        
          A "User Product" is either (1) a "consumer product", which means any
        tangible personal property which is normally used for personal, family,
        or household purposes, or (2) anything designed or sold for incorporation
        into a dwelling.  In determining whether a product is a consumer product,
        doubtful cases shall be resolved in favor of coverage.  For a particular
        product received by a particular user, "normally used" refers to a
        typical or common use of that class of product, regardless of the status
        of the particular user or of the way in which the particular user
        actually uses, or expects or is expected to use, the product.  A product
        is a consumer product regardless of whether the product has substantial
        commercial, industrial or non-consumer uses, unless such uses represent
        the only significant mode of use of the product.
        
          "Installation Information" for a User Product means any methods,
        procedures, authorization keys, or other information required to install
        and execute modified versions of a covered work in that User Product from
        a modified version of its Corresponding Source.  The information must
        suffice to ensure that the continued functioning of the modified object
        code is in no case prevented or interfered with solely because
        modification has been made.
        
          If you convey an object code work under this section in, or with, or
        specifically for use in, a User Product, and the conveying occurs as
        part of a transaction in which the right of possession and use of the
        User Product is transferred to the recipient in perpetuity or for a
        fixed term (regardless of how the transaction is characterized), the
        Corresponding Source conveyed under this section must be accompanied
        by the Installation Information.  But this requirement does not apply
        if neither you nor any third party retains the ability to install
        modified object code on the User Product (for example, the work has
        been installed in ROM).
        
          The requirement to provide Installation Information does not include a
        requirement to continue to provide support service, warranty, or updates
        for a work that has been modified or installed by the recipient, or for
        the User Product in which it has been modified or installed.  Access to a
        network may be denied when the modification itself materially and
        adversely affects the operation of the network or violates the rules and
        protocols for communication across the network.
        
          Corresponding Source conveyed, and Installation Information provided,
        in accord with this section must be in a format that is publicly
        documented (and with an implementation available to the public in
        source code form), and must require no special password or key for
        unpacking, reading or copying.
        
          7. Additional Terms.
        
          "Additional permissions" are terms that supplement the terms of this
        License by making exceptions from one or more of its conditions.
        Additional permissions that are applicable to the entire Program shall
        be treated as though they were included in this License, to the extent
        that they are valid under applicable law.  If additional permissions
        apply only to part of the Program, that part may be used separately
        under those permissions, but the entire Program remains governed by
        this License without regard to the additional permissions.
        
          When you convey a copy of a covered work, you may at your option
        remove any additional permissions from that copy, or from any part of
        it.  (Additional permissions may be written to require their own
        removal in certain cases when you modify the work.)  You may place
        additional permissions on material, added by you to a covered work,
        for which you have or can give appropriate copyright permission.
        
          Notwithstanding any other provision of this License, for material you
        add to a covered work, you may (if authorized by the copyright holders of
        that material) supplement the terms of this License with terms:
        
            a) Disclaiming warranty or limiting liability differently from the
            terms of sections 15 and 16 of this License; or
        
            b) Requiring preservation of specified reasonable legal notices or
            author attributions in that material or in the Appropriate Legal
            Notices displayed by works containing it; or
        
            c) Prohibiting misrepresentation of the origin of that material, or
            requiring that modified versions of such material be marked in
            reasonable ways as different from the original version; or
        
            d) Limiting the use for publicity purposes of names of licensors or
            authors of the material; or
        
            e) Declining to grant rights under trademark law for use of some
            trade names, trademarks, or service marks; or
        
            f) Requiring indemnification of licensors and authors of that
            material by anyone who conveys the material (or modified versions of
            it) with contractual assumptions of liability to the recipient, for
            any liability that these contractual assumptions directly impose on
            those licensors and authors.
        
          All other non-permissive additional terms are considered "further
        restrictions" within the meaning of section 10.  If the Program as you
        received it, or any part of it, contains a notice stating that it is
        governed by this License along with a term that is a further
        restriction, you may remove that term.  If a license document contains
        a further restriction but permits relicensing or conveying under this
        License, you may add to a covered work material governed by the terms
        of that license document, provided that the further restriction does
        not survive such relicensing or conveying.
        
          If you add terms to a covered work in accord with this section, you
        must place, in the relevant source files, a statement of the
        additional terms that apply to those files, or a notice indicating
        where to find the applicable terms.
        
          Additional terms, permissive or non-permissive, may be stated in the
        form of a separately written license, or stated as exceptions;
        the above requirements apply either way.
        
          8. Termination.
        
          You may not propagate or modify a covered work except as expressly
        provided under this License.  Any attempt otherwise to propagate or
        modify it is void, and will automatically terminate your rights under
        this License (including any patent licenses granted under the third
        paragraph of section 11).
        
          However, if you cease all violation of this License, then your
        license from a particular copyright holder is reinstated (a)
        provisionally, unless and until the copyright holder explicitly and
        finally terminates your license, and (b) permanently, if the copyright
        holder fails to notify you of the violation by some reasonable means
        prior to 60 days after the cessation.
        
          Moreover, your license from a particular copyright holder is
        reinstated permanently if the copyright holder notifies you of the
        violation by some reasonable means, this is the first time you have
        received notice of violation of this License (for any work) from that
        copyright holder, and you cure the violation prior to 30 days after
        your receipt of the notice.
        
          Termination of your rights under this section does not terminate the
        licenses of parties who have received copies or rights from you under
        this License.  If your rights have been terminated and not permanently
        reinstated, you do not qualify to receive new licenses for the same
        material under section 10.
        
          9. Acceptance Not Required for Having Copies.
        
          You are not required to accept this License in order to receive or
        run a copy of the Program.  Ancillary propagation of a covered work
        occurring solely as a consequence of using peer-to-peer transmission
        to receive a copy likewise does not require acceptance.  However,
        nothing other than this License grants you permission to propagate or
        modify any covered work.  These actions infringe copyright if you do
        not accept this License.  Therefore, by modifying or propagating a
        covered work, you indicate your acceptance of this License to do so.
        
          10. Automatic Licensing of Downstream Recipients.
        
          Each time you convey a covered work, the recipient automatically
        receives a license from the original licensors, to run, modify and
        propagate that work, subject to this License.  You are not responsible
        for enforcing compliance by third parties with this License.
        
          An "entity transaction" is a transaction transferring control of an
        organization, or substantially all assets of one, or subdividing an
        organization, or merging organizations.  If propagation of a covered
        work results from an entity transaction, each party to that
        transaction who receives a copy of the work also receives whatever
        licenses to the work the party's predecessor in interest had or could
        give under the previous paragraph, plus a right to possession of the
        Corresponding Source of the work from the predecessor in interest, if
        the predecessor has it or can get it with reasonable efforts.
        
          You may not impose any further restrictions on the exercise of the
        rights granted or affirmed under this License.  For example, you may
        not impose a license fee, royalty, or other charge for exercise of
        rights granted under this License, and you may not initiate litigation
        (including a cross-claim or counterclaim in a lawsuit) alleging that
        any patent claim is infringed by making, using, selling, offering for
        sale, or importing the Program or any portion of it.
        
          11. Patents.
        
          A "contributor" is a copyright holder who authorizes use under this
        License of the Program or a work on which the Program is based.  The
        work thus licensed is called the contributor's "contributor version".
        
          A contributor's "essential patent claims" are all patent claims
        owned or controlled by the contributor, whether already acquired or
        hereafter acquired, that would be infringed by some manner, permitted
        by this License, of making, using, or selling its contributor version,
        but do not include claims that would be infringed only as a
        consequence of further modification of the contributor version.  For
        purposes of this definition, "control" includes the right to grant
        patent sublicenses in a manner consistent with the requirements of
        this License.
        
          Each contributor grants you a non-exclusive, worldwide, royalty-free
        patent license under the contributor's essential patent claims, to
        make, use, sell, offer for sale, import and otherwise run, modify and
        propagate the contents of its contributor version.
        
          In the following three paragraphs, a "patent license" is any express
        agreement or commitment, however denominated, not to enforce a patent
        (such as an express permission to practice a patent or covenant not to
        sue for patent infringement).  To "grant" such a patent license to a
        party means to make such an agreement or commitment not to enforce a
        patent against the party.
        
          If you convey a covered work, knowingly relying on a patent license,
        and the Corresponding Source of the work is not available for anyone
        to copy, free of charge and under the terms of this License, through a
        publicly available network server or other readily accessible means,
        then you must either (1) cause the Corresponding Source to be so
        available, or (2) arrange to deprive yourself of the benefit of the
        patent license for this particular work, or (3) arrange, in a manner
        consistent with the requirements of this License, to extend the patent
        license to downstream recipients.  "Knowingly relying" means you have
        actual knowledge that, but for the patent license, your conveying the
        covered work in a country, or your recipient's use of the covered work
        in a country, would infringe one or more identifiable patents in that
        country that you have reason to believe are valid.
        
          If, pursuant to or in connection with a single transaction or
        arrangement, you convey, or propagate by procuring conveyance of, a
        covered work, and grant a patent license to some of the parties
        receiving the covered work authorizing them to use, propagate, modify
        or convey a specific copy of the covered work, then the patent license
        you grant is automatically extended to all recipients of the covered
        work and works based on it.
        
          A patent license is "discriminatory" if it does not include within
        the scope of its coverage, prohibits the exercise of, or is
        conditioned on the non-exercise of one or more of the rights that are
        specifically granted under this License.  You may not convey a covered
        work if you are a party to an arrangement with a third party that is
        in the business of distributing software, under which you make payment
        to the third party based on the extent of your activity of conveying
        the work, and under which the third party grants, to any of the
        parties who would receive the covered work from you, a discriminatory
        patent license (a) in connection with copies of the covered work
        conveyed by you (or copies made from those copies), or (b) primarily
        for and in connection with specific products or compilations that
        contain the covered work, unless you entered into that arrangement,
        or that patent license was granted, prior to 28 March 2007.
        
          Nothing in this License shall be construed as excluding or limiting
        any implied license or other defenses to infringement that may
        otherwise be available to you under applicable patent law.
        
          12. No Surrender of Others' Freedom.
        
          If conditions are imposed on you (whether by court order, agreement or
        otherwise) that contradict the conditions of this License, they do not
        excuse you from the conditions of this License.  If you cannot convey a
        covered work so as to satisfy simultaneously your obligations under this
        License and any other pertinent obligations, then as a consequence you may
        not convey it at all.  For example, if you agree to terms that obligate you
        to collect a royalty for further conveying from those to whom you convey
        the Program, the only way you could satisfy both those terms and this
        License would be to refrain entirely from conveying the Program.
        
          13. Use with the GNU Affero General Public License.
        
          Notwithstanding any other provision of this License, you have
        permission to link or combine any covered work with a work licensed
        under version 3 of the GNU Affero General Public License into a single
        combined work, and to convey the resulting work.  The terms of this
        License will continue to apply to the part which is the covered work,
        but the special requirements of the GNU Affero General Public License,
        section 13, concerning interaction through a network will apply to the
        combination as such.
        
          14. Revised Versions of this License.
        
          The Free Software Foundation may publish revised and/or new versions of
        the GNU General Public License from time to time.  Such new versions will
        be similar in spirit to the present version, but may differ in detail to
        address new problems or concerns.
        
          Each version is given a distinguishing version number.  If the
        Program specifies that a certain numbered version of the GNU General
        Public License "or any later version" applies to it, you have the
        option of following the terms and conditions either of that numbered
        version or of any later version published by the Free Software
        Foundation.  If the Program does not specify a version number of the
        GNU General Public License, you may choose any version ever published
        by the Free Software Foundation.
        
          If the Program specifies that a proxy can decide which future
        versions of the GNU General Public License can be used, that proxy's
        public statement of acceptance of a version permanently authorizes you
        to choose that version for the Program.
        
          Later license versions may give you additional or different
        permissions.  However, no additional obligations are imposed on any
        author or copyright holder as a result of your choosing to follow a
        later version.
        
          15. Disclaimer of Warranty.
        
          THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
        APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
        HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
        OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
        THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
        PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
        IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
        ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
        
          16. Limitation of Liability.
        
          IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
        WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
        THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
        GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
        USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
        DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
        PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
        EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
        SUCH DAMAGES.
        
          17. Interpretation of Sections 15 and 16.
        
          If the disclaimer of warranty and limitation of liability provided
        above cannot be given local legal effect according to their terms,
        reviewing courts shall apply local law that most closely approximates
        an absolute waiver of all civil liability in connection with the
        Program, unless a warranty or assumption of liability accompanies a
        copy of the Program in return for a fee.
        
                             END OF TERMS AND CONDITIONS
        
                    How to Apply These Terms to Your New Programs
        
          If you develop a new program, and you want it to be of the greatest
        possible use to the public, the best way to achieve this is to make it
        free software which everyone can redistribute and change under these terms.
        
          To do so, attach the following notices to the program.  It is safest
        to attach them to the start of each source file to most effectively
        state the exclusion of warranty; and each file should have at least
        the "copyright" line and a pointer to where the full notice is found.
        
            <one line to give the program's name and a brief idea of what it does.>
            Copyright (C) <year>  <name of author>
        
            This program is free software: you can redistribute it and/or modify
            it under the terms of the GNU General Public License as published by
            the Free Software Foundation, either version 3 of the License, or
            (at your option) any later version.
        
            This program is distributed in the hope that it will be useful,
            but WITHOUT ANY WARRANTY; without even the implied warranty of
            MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
            GNU General Public License for more details.
        
            You should have received a copy of the GNU General Public License
            along with this program.  If not, see <https://www.gnu.org/licenses/>.
        
        Also add information on how to contact you by electronic and paper mail.
        
          If the program does terminal interaction, make it output a short
        notice like this when it starts in an interactive mode:
        
            <program>  Copyright (C) <year>  <name of author>
            This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
            This is free software, and you are welcome to redistribute it
            under certain conditions; type `show c' for details.
        
        The hypothetical commands `show w' and `show c' should show the appropriate
        parts of the General Public License.  Of course, your program's commands
        might be different; for a GUI interface, you would use an "about box".
        
          You should also get your employer (if you work as a programmer) or school,
        if any, to sign a "copyright disclaimer" for the program, if necessary.
        For more information on this, and how to apply and follow the GNU GPL, see
        <https://www.gnu.org/licenses/>.
        
          The GNU General Public License does not permit incorporating your program
        into proprietary programs.  If your program is a subroutine library, you
        may consider it more useful to permit linking proprietary applications with
        the library.  If this is what you want to do, use the GNU Lesser General
        Public License instead of this License.  But first, please read
        <https://www.gnu.org/licenses/why-not-lgpl.html>.
License-File: LICENSE
Keywords: alphafold3,bioinformatics,contact-map,protein-structure,visualization
Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Requires-Python: >=3.9
Requires-Dist: biopython>=1.85
Requires-Dist: matplotlib>=3.10.7
Requires-Dist: numpy>=2.2.0
Requires-Dist: pandas>=2.3.1
Requires-Dist: seaborn>=0.13.2
Requires-Dist: typer>=0.20.0
Provides-Extra: dev
Requires-Dist: build; extra == 'dev'
Requires-Dist: pytest; extra == 'dev'
Requires-Dist: pytest-cov; extra == 'dev'
Requires-Dist: twine; extra == 'dev'
Description-Content-Type: text/markdown

# AlphaFold3 SeqVis Toolkit


[![GitHub stars](https://img.shields.io/github/stars/MaybeBio/AlphaFold3-SeqVisToolkit.svg?style=social&label=Star)](https://github.com/MaybeBio/AlphaFold3-SeqVisToolkit/stargazers/)
[![GitHub forks](https://img.shields.io/github/forks/MaybeBio/AlphaFold3-SeqVisToolkit.svg?style=social&label=Fork)](https://github.com/MaybeBio/AlphaFold3-SeqVisToolkit/network/)
[![GitHub issues](https://img.shields.io/github/issues/MaybeBio/AlphaFold3-SeqVisToolkit.svg)](https://github.com/MaybeBio/AlphaFold3-SeqVisToolkit/issues)
[![PR's Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat)](http://makeapullrequest.com) 


[![PyPI version](https://img.shields.io/pypi/v/alphafold3-seqvis-toolkit.svg?logo=pypi&logoColor=white)](https://pypi.org/project/alphafold3-seqvis-toolkit/)
[![Python Versions](https://img.shields.io/pypi/pyversions/alphafold3-seqvis-toolkit.svg?logo=python&logoColor=white)](https://pypi.org/project/alphafold3-seqvis-toolkit/)
[![Downloads](https://static.pepy.tech/badge/alphafold3-seqvis-toolkit)](https://pepy.tech/project/alphafold3-seqvis-toolkit)

[![License: GPL v3](https://img.shields.io/badge/License-GPL%20v3-blue.svg)](https://www.gnu.org/licenses/gpl-3.0) 

A lightweight toolkit for visualizing and analyzing AlphaFold3 prediction outputs.

![alt text](./Figs/visual.png)


## 📑 Table of Contents
- [Modules](#modules)
  - [Confidence Metrics](#1-confidence-metrics-plotting)
  - [Contact Map Visualization](#2-contact-map-visualization)
  - [Structure Comparison](#3-two-structures-comparison)
  - [Feature Tracks](#4-sequence-based-feature-tracks-intergrated)
  - [PyMOL Extension](#5-pymol-extension-to-color-alphafold-structures-by-confidence-plddt)
- [Installation](#how-to-install-it-)
- [Usage](#how-to-use-it-)
- [CLI Reference](#cli)
- [Test Cases](#test-cases)
- [TODOs](#-todos)

## Modules

### 1, Confidence Metrics Plotting

It is designed to visualize all confidence metrics, and we categorize the confidence metrics produced by AlphaFold3 into 2 types: 
one is the global confidence metric, and the other is the local confidence metric. 

For details about every metric below, please refer to [Interpreting results from AlphaFold Server](https://www.ebi.ac.uk/training/online/courses/alphafold/alphafold-3-and-alphafold-server/alphafold-server-your-gateway-to-alphafold-3/interpreting-results-from-alphafold-server/)  | [Frequently asked questions about AlphaFold](https://alphafold.ebi.ac.uk/faq#faq-12)

⚠️ Note: There may be NULL values in the following metrics, so we will convert them to NaN (these values may appear as NA when output, and this handling also applies to plotting). Therefore, if you are confused about the output, it is recommended to first check your original data.

#### **global confidence metrics** 

In **`fold_{YOUR_JOB_NAME}_summary_confidences_{i}.json`** file

---
| Metric | Description | Visualization | Insight |
|--------|-------------|---------------|---------|
|chain_iptm|A [num_chains] array that gives the average confidence (ipTM) in the interfaces between each chain and all other chains | Output in a tsv file, and Visualized as a Line/Bar plot | This can be used for ranking predicted structures for a specific chain, when you care about where the chain binds to the rest of the complex and you do not know which other chains you expect it to interact with. This is often the case with ligands, each of which the system treats as a separate chain | 
|chain_pair_iptm|A square [num_chains, num_chains] array representing pairwise ipTM scores. The off-diagonal element (i, j) of the array contains the ipTM restricted to tokens from chains i and j. The diagonal element (i, i) contains the pTM restricted to chain i|Visualized as a heatmap| The array can be used for ranking predictions of a structure by the accuracy of a specific interface between two chains that you know interact, e.g. antibody-antigen interactions. As these values are calculated based on tokens, this metric also encompasses small molecules and chemically-modified residues and nucleotides | 
|chain_pair_pae_min|A square [num_chains, num_chains] array of PAE values. Element (i, j) of the array contains the lowest PAE value across rows restricted to chain i and columns restricted to chain j|Visualized as a heatmap| This has been found to correlate with whether or not two chains interact, so **it can be used to distinguish interacting and non-interacting molecules**. As these values are calculated based on tokens, this metric also encompasses small molecules and chemically-modified residues and nucleotides | 
|chain_ptm|A [num_chains] array. Element i contains the pTM restricted to chain i|Output in a tsv file, and Visualized as a Line/Bar plot| This can be used for ranking the predicted structures of individual chains when you are most interested in the structure of that chain, rather than its cross-chain interactions | 
|fraction_disordered| A scalar in the range 0-1 that indicates what fraction of the prediction structure is disordered, as measured by accessible surface area | Output in a tsv file| | 
|has_clash| A Boolean, i.e. a yes/no value, indicating if the structure has a significant number of clashing atoms (more than 50% of a chain, or a chain with more than 100 clashing atoms) | Output in a tsv file mentioned above| | 
|iptm| A scalar in the range 0-1 indicating predicted interface TM-score (confidence in the predicted interfaces) for all interfaces in the structure | Output in a tsv file mentioned above| | 
|num_recycles| An integer number that represents the total number of recycles | Output in a tsv file mentioned above| | 
|ptm| A scalar in the range 0-1 indicating the predicted TM-score for the full structure | Output in a tsv file mentioned above| | 
|ranking_score| A scalar ranging from -100 to 1.5 that can be used for ranking predictions. It combines ptm, iptm, fraction_disordered and has_clash into a single number with the following equation: 0.8 × ipTM + 0.2 × pTM + 0.5 × disorder − 100 × has_clash | Output in a tsv file mentioned above| |
---

In **`fold_{YOUR_JOB_NAME}_full_data_{i}.json`** file

---
| Metric | Description | Visualization | 
|--------|-------------|---------------| 
|pLDDT distribution|Proportion of Each pLDDT Confidence Region by Chain and All|Output in a tsv file| 
|Average pLDDT|Avergae plDDT score by Chain and All|Output in a tsv file mentioned above| 
---

#### **local confidence metrics**

In **`fold_{YOUR_JOB_NAME}_full_data_{i}.json`** file

---
| Metric | Description | Visualization | 
|--------|-------------|---------------|
|contact_probs|A square [num_tokens, num_tokens] array. Element (i, j) indicates the predicted probability that token i and token j are in contact, where “in contact” is defined as a maximum distance of 8Å between a system-defined representative atom for each token|Visualized as a heatmap; by default, all chains are included, and you can also select specific chains to display|
|atom_plddts|A [num_atoms] array. Element i indicates the predicted local distance difference test (pLDDT) for atom i in the prediction|Visualized as a line plot, with a pLDDT color coding for area under the curve; by default, all chains are included, and you can also select specific chains to display|
|pae|A square [num_tokens, num_tokens] array. Element (i, j) indicates the predicted aligned error (PAE) in the position of token j, when the prediction is aligned to the ground truth using the frame of token i|Visualized as a heatmap; by default, all chains are included, and you can also select specific chains to display|
| atom_chain_ids | A [num_atoms] array indicating the chain IDs corresponding to each atom in the prediction | | 
| token_chain_ids | A [num_tokens] array indicating the chain IDs corresponding to each token in the prediction | |
| token_res_ids | A [num_res] array | |

---

For pLDDT color coding

![alt text](./Figs/plddt.png)

colors are defined below, for details, please refer to [I want to render my own images of the predicted structures, how do I color by pLDDT?](https://github.com/sokrypton/ColabFold?tab=readme-ov-file#faq)

```
set_color n0, [0.051, 0.341, 0.827]
set_color n1, [0.416, 0.796, 0.945]
set_color n2, [0.996, 0.851, 0.212]
set_color n3, [0.992, 0.490, 0.302]
color n0, b < 100; color n1, b < 90
color n2, b < 70;  color n3, b < 50
```
  
Notably, AlphaFold 3 calculates a pLDDT score for every individual atom in the structure. This differs from AlphaFold 2, which calculates pLDDT for each amino acid residue.

⚠️ Note: This module is alphafold3-DEPENDENT, cause the input data needed (confidence json file) is generated by alphafold3.
### 2, Contact Map Visualization

This module allows you to generate residue-residue contact heatmaps directly from an mmCIF file. It supports complex structures, enabling you to visualize interactions within the entire complex or focus on a specific chain by specifying its ID.

And we also support the **1D feature track stacking (1D-to-2D stacking)** for the relevant chain; please refer to **MODULE 4** below for specific implementation details.

Here we introduce 2 modes:
* `contact-map-vis --mode no-track` for ordinary visualization,
* `contact-map-vis --mode track` for 1D Track-integrated visualization.

⚠️ Note: This module is alphafold3-INDEPENDENT, cause the input data needed (an mmCIF file) is NOT NECESSARILY generated by alphafold3.
### 3, Two Structures Comparison

Our tool currently supports `comparing the structures of monomers/multimers generated from the same sequence — under two different conditions`, with a focus on analyzing the differences between these molecules across conditions.

For example, in the case of `monomers`: Taking a specific transcription factor as an instance, our tool enables the observation of its structural changes under two scenarios—when it is bound to DNA and when it is not bound to DNA.

For `multimers`: Consider a protein complex composed of CTCF, RAD21, and NIPBL. When comparing the complex in its treated state (with no sequence alterations within the complex itself) versus its untreated state, our tool allows users to identify changes in inter-protein features (such as protein interfaces), which differs from the focus on intramolecular changes (within individual proteins) when analyzing monomers.

And our tool enables you to `draw a green box or select a region to highlight in areas you are interested in—even across different chains`! For example, if you want to view region 234:455 in Chain A compared with region 880:910 in Chain B, our tool can easily do this!

Currently, our comparison module only supports `structures with identical sequences`. This is because we require matching sequence indices to perform alignment between the pre- and post- states, thereby avoiding potential bias. 

⚠️ Note: This module is AlphaFold3-INDEPENDENT, as the required input data—two mmCIF files (under two different conditions, containing the same protein sequence)—is not necessarily generated by AlphaFold3.

### 4, Sequence-based feature tracks intergrated

Since proteins have numerous sequence-level features (e.g., Shannon entropy, domain annotations, intrinsically disordered region (IDR) annotations, etc.), we intend to add a dimension of sequence feature information to structure-related 2D plots for comparative visualization.

Here, we roughly categorize the input feature tracks into two classes: NUMERICAL and CATEGORICAL. Specifically, for the former (NUMERICAL features), a line plot is generally used for visualization; for the latter (CATEGORICAL features), a bar plot or strip plot is adopted. Additionally, these two types of feature tracks differ in both annotation color configurations and track size. When displayed, the feature tracks are symmetrically placed on the top and left sides of the 2D matrix plot.

For track-intergrated plotting, here we take the command `contact-map-vis --mode track` as an example.

There are 2 files needed: `Bed for Track info and Json for Track color config`

- Track bed file: 5-column TSV format —— [Chain, TrackName, Start, End, Value]. This format is designed to integrate and standardize feature-related data.
  - 0-indexed
  - must have a column name row
  - value must be a numerical type or a catrgorical string

    We present a simulated track bed file generated by script [SIMULATED TRACK SCRIPT](./tests/test_data/Multi_protein_complex/simulated_tracks.py)  here: [SIMULATED TRACK FILE](./tests/test_output/visualization/track/simulated_tracks.bed)

    ```bash
    chain_id	track_name	start	end	value
    A	Disorder	0	9	0.1939202398057196
    A	Disorder	10	19	0.2661143003553823
    A	Disorder	20	29	0.09356952954622577
    A	Disorder	30	39	0.7224995256611805
    A	Disorder	40	49	0.21211383891211832
    ...
    ```

- Color config file: We strongly recommend you to use a JSON file.
  - Using {TrackName : Color config} format
  - TrackName must be consitent with "TrackName" column in Track bed file above
  - For Numerical-type Track, we recommend using single color (like "orange" or "#FF1010"), or a colormap (like "tab20")
  - For Categorical-type Track, if you know the exact number of categories and wish to assign a specific color to each category, we recommend using a detailed color dictionary. If you do not have this information (or do not need custom color assignments), we suggest using a colormap—note that the number of colors in the colormap you provide must exceed the number of categories in the track. Examples of suitable colormaps like "tab20", and we will automatically assign distinct colors from the colormap to each category for you.

    We present a simulated track color config file here: [SIMULATED COLOR CONFIG FILE](./tests/test_output/visualization/track/simulated_tracks_color_config.json)
    ```python
    import json

    color_config = {
        "Disorder": "orange",
        "Domains": {
            "N-Term": "green",
            "DNA-Binding": "red",
            "Zinc-Finger": "purple",
            "C-Term": "blue",
            "Linker": "gray"
        }
    }

    # Save color configuration
    with open("./tests/test_output/visualization/track/simulated_tracks_color_config.json", "w") as f:
        json.dump(color_config, f)
    ```

For the demonstration of results, please refer to [Test case4](#-case-4-visualizing-protein-sequence-based-feature-track-in-residue-residue-contact-map)

⚠️ Note: This module is AlphaFold3-INDEPENDENT

### 5, PyMOL extensions/plugins for Visualization

For open source Pymol installations, please refer to https://github.com/schrodinger/pymol-open-source
#### 1️⃣PyMOL extension to color AlphaFold structures by confidence (pLDDT)

Test case see [Test Case2](#-case-2-visualizing-structural-confidence-of-molecules-in-pymol), and Colors definition see Module 1 above.

#### 2️⃣A PyMOL plugin to visualize interface residues is coming soon !

## How to install it ?

## Install (dev)

```bash
git clone https://github.com/MaybeBio/AlphaFold3-SeqVisToolkit.git
cd AlphaFold3-SeqVisToolkit
pip install -e .
```


## How to use it ?

First have a look at the help message !

```bash
❯ af3-vis --help
                                                                                                                                          
 Usage: af3-vis [OPTIONS] COMMAND [ARGS]...                                                                                               
                                                                                                                                          
 AlphaFold3 SeqVis Toolkit                                                                                                                
                                                                                                                                          
╭─ Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --install-completion          Install completion for the current shell.                                                                │
│ --show-completion             Show completion for the current shell, to copy it or customize the installation.                         │
│ --help                        Show this message and exit.                                                                              │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ confidence         Plot global (ipTM/pTM etc.) and/or local (PAE/contact/atom pLDDT) confidence metrics.                               │
│ contact-map-diff   Compare contact maps between two AlphaFold3/General mmCIF structures (for the same molecule with an identical       │
│                    sequence), and plot the distance/diff matrices. Supports both monomer and multimer modes.                           │
│ contact-map-vis    Visualize contact map from an AlphaFold3 mmCIF structure or a general mmCIF structure. Supports 'no-track' (simple) │
│                    and 'track' (custom annotation) modes.                                                                              │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
```

* As you can see, our toolkit currently supports 3 modules talked above


### For Confidence Metrics Plotting
```bash
❯ af3-vis confidence --help
                                                                                                                                                                                         
 Usage: af3-vis confidence [OPTIONS]                                                                                                                                                     
                                                                                                                                                                                         
 Plot global (ipTM/pTM etc.) and/or local (PAE/contact/atom pLDDT) confidence metrics.                                                                                                   
                                                                                                                                                                                         
 Notes:                                                                                                                                                                                  
 - 1, Use --mode to control the scope:                                                                                                                                                   
     - 'all' (default): Plots everything possible based on provided JSON files. If only one file is provided, it plots that one.                                                         
     - 'global': Only plots global metrics (requires --global-json).                                                                                                                     
     - 'local': Only plots local metrics (requires --full-json).                                                                                                                         
 - 2, [--chains] option is only effective for LOCAL metrics (PAE, contact probs, atom pLDDT).                                                                                            
 - 3, There may be NULL values in the above metrics produced by AlphaFold3, so we will convert them to NaN (these values may appear as NA when output, and this handling also applies to 
 plotting). Therefore, if you are confused about the output, it is recommended to first check your original data.                                                                        
 - 4, All residue indices in this module are 0-based logic driven.                                                                                                                       
                                                                                                                                                                                         
 Examples:                                                                                                                                                                               
 - 1, Plot EVERYTHING (Global + Local) for a job:                                                                                                                                        
 af3-vis confidence --global-json summary_confidences.json --full-json full_data.json -o out_path                                                                                        
 - 2, Only plot Global metrics:                                                                                                                                                          
 af3-vis confidence --mode global --global-json summary_confidences.json -o out_path                                                                                                     
 - 3, Only plot Local metrics for specific chains:                                                                                                                                       
 af3-vis confidence --mode local --full-json full_data.json -c A -c B -o out_path                                                                                                        
                                                                                                                                                                                         
╭─ Options ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --help          Show this message and exit.                                                                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Input ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --global-json        TEXT  fold_{YOUR-JOB-NAME}_summary_confidences_{i}.json (Required for global/all mode)                                                                           │
│ --full-json          TEXT  fold_{YOUR-JOB-NAME}_full_data_{i}.json (Required for local/all mode)                                                                                      │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Output ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --output-path  -o      TEXT  Directory for outputs, default is current directory [default: .]                                                                                         │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Mode ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --mode  -m      TEXT  Analysis mode: 'all' (default), 'global', or 'local'. [default: all]                                                                                            │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Local Plot Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --chains     -c      TEXT     Repeatable: chain IDs for local subset. Only used in 'local' or 'all' mode with --full-json.                                                            │
│ --tick-step          INTEGER  Residue tick step for local plots [default: 100]                                                                                                        │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
```


### For Contact Map Visualization
```bash
❯  af3-vis contact-map-vis --help
                                                                                                                                                                                         
 Usage: af3-vis contact-map-vis [OPTIONS]                                                                                                                                                
                                                                                                                                                                                         
 Visualize contact map from an AlphaFold3 mmCIF structure or a general mmCIF structure. Supports 'no-track' (simple) and 'track' (custom annotation) modes.                              
                                                                                                                                                                                         
 Notes:                                                                                                                                                                                  
 - 1, Use --mode to switch between 'no-track' (default) and 'track' visualization.                                                                                                       
 - 2, 'no-track' mode: Generates a standard contact map.                                                                                                                                 
 - 3, 'track' mode: Generates a contact map with custom annotation tracks (e.g., domains, IDRs).                                                                                         
      - Requires --track-bed-file.                                                                                                                                                       
      - Tracks can be numerical (line plot) or categorical (bar/strip plot).                                                                                                             
      - The track bed file must be 0-based indexed!                                                                                                                                      
 - 4, By default, all chains in the mmCIF file are included. Use --chains to specify particular chains if needed.                                                                        
 - 5, A color configuration file can be provided to customize the colors of categorical tracks (only for 'track' mode).                                                                  
 - 6, Modify the tick_step parameter to adjust the spacing of residue ticks on the axes as needed.                                                                                       
                                                                                                                                                                                         
 Examples:                                                                                                                                                                               
 - 1, Basic contact map visualization (Default no-track):                                                                                                                                
 af3-vis contact-map-vis --mmcif-file model.cif -o out_path                                                                                                                              
 - 2, Contact map with custom annotation tracks:                                                                                                                                         
 af3-vis contact-map-vis --mmcif-file model.cif --mode track --track-bed-file custom_tracks.bed --color-config color_config.json -o out_path                                             
                                                                                                                                                                                         
╭─ Options ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --help          Show this message and exit.                                                                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Input ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ *  --mmcif-file          TEXT  Path to mmCIF file [required]                                                                                                                          │
│    --chains      -c      TEXT  Repeatable: chain IDs to include, default is all chains                                                                                                │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Output ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --out-path  -o      TEXT  Directory for outputs, default is current directory [default: .]                                                                                            │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Mode ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --mode  -m      TEXT  Visualization mode: 'no-track' (default) or 'track'. [default: no-track]                                                                                        │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Custom Tracks ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --track-bed-file        TEXT  Path to BED file for custom tracks, e.g., domains、IDRs (Required if mode is 'track')                                                                   │
│ --color-config          TEXT  Path to color config file (JSON) or colormap name (Only used if mode is 'track') [default: tab10]                                                       │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Plot Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --tick-step        INTEGER  Step size for ticks on the axes [default: 100]                                                                                                            │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
```


### For Contact Map Comparison
```bash
❯ af3-vis contact-map-diff --help
                                                                                                                                                    
 Usage: af3-vis contact-map-diff [OPTIONS]                                                                                                          
                                                                                                                                                    
 Compare contact maps between two AlphaFold3/General mmCIF structures (for the same molecule with an identical sequence), and plot the              
 distance/diff matrices.Supports both monomer and multimer modes.                                                                                   
                                                                                                                                                    
 Notes:                                                                                                                                             
 - 1, Designed for comparing the same protein sequence under different conditions.                                                                  
 - 2, Regions are 0-based and inclusive: 'start:end' means [start, end].                                                                            
 - 3, If region_2 is omitted, region_1 is applied symmetrically.                                                                                    
 - 4, We strongly recommend using --region-pair for multiple region comparisons, as it is more flexible and clearer.                                
 And you can also use --region-pair to replace the legacy --region-1/--region-2 options.                                                            
 - 5, Use --mode to switch between 'monomer' and 'multimer' (default) comparison logic.                                                             
 - 6, All residue indices in this module are 0-based logic driven.                                                                                  
 - 7, chain_a and chain_b should strictly align in order with same sequence! E.g., in multimer mode, if chain_a is "A,B,C", chain_b is "D,E,F",     
 then it should be A aligns with D, B aligns with E, and C aligns with F.                                                                           
                                                                                                                                                    
 Examples:                                                                                                                                          
                                                                                                                                                    
 - 1, Basic diff on one region (Multimer default):                                                                                                  
 af3-vis contact-map-diff --mmcif-a A.cif --mmcif-b B.cif --region-1 0:200 --chain-a A --chain-b A --out-path .                                     
                                                                                                                                                    
 - 2, Diff between two regions (Monomer mode):                                                                                                      
 af3-vis contact-map-diff --mmcif-a A.cif --mmcif-b B.cif --region-1 0-200 --region-2 300-500 --chain-a A --chain-b A --mode monomer --out-path .   
                                                                                                                                                    
 - 3, Multiple region pairs (Multimer, Chain A vs Chain A):                                                                                         
 af3-vis contact-map-diff --mmcif-a A.cif --mmcif-b B.cif --region-pair 265:576,0:15 --region-pair 265:576,42:54 --region-pair 265:576,83:93        
 --region-pair 265:576,170:189 --region-pair 265:576,214:241 --region-pair 265:576,578:589 --region-pair 265:576,606:639 --region-pair              
 265:576,691:720 --chain-a A --chain-b A --out-path .                                                                                               
                                                                                                                                                    
 - 4, Multimer Complex (Chain A,B vs Chain A,B) with specific chain regions: (🌟 RECOMMENDED IN ANY CASE!)                                          
 af3-vis contact-map-diff --mmcif-a complex_v1.cif --mmcif-b complex_v2.cif --chain-a A,B --chain-b A,B --region-pair A:10:50,B:10:50 --region-pair 
 A:100:150,A:100:150 --out-path .                                                                                                                   
                                                                                                                                                    
╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --include-nonstandard    --no-include-nonstandard      Include non-standard amino acid residues [default: no-include-nonstandard]                │
│ --help                                                 Show this message and exit.                                                               │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Inputs ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ *  --mmcif-a        TEXT  Path to mmCIF file A [required]                                                                                        │
│ *  --mmcif-b        TEXT  Path to mmCIF file B [required]                                                                                        │
│ *  --chain-a        TEXT  Chain ID(s) for mmCIF file A. Monomer mode: single chain (e.g. 'A'). Multimer mode: one or more chains (e.g. 'A' or    │
│                           'A,B').                                                                                                                │
│                           [required]                                                                                                             │
│ *  --chain-b        TEXT  Chain ID(s) for mmCIF file B. Must align with chain-a (⚠️  same number and sequence!). [required]                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Legacy ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --region-1        TEXT  (Legacy) Select a region to focus on/compare (highlighted with a green box). In multimer mode, supports                  │
│                         'Chain:Start:End'.                                                                                                       │
│ --region-2        TEXT  (Legacy) Select a second region to compare against region-1.                                                             │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Regions ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --region-pair        TEXT  Repeatable region pair(s) selected to focus on/compare (highlighted with green boxes): 'Start:End,Start:End' format   │
│                            like 'a:b,c:d' or 'a-b,c-d' for monomer mode, Chains-specified 'Chain:Start:End' format like 'A:a:b,B:c:d' or         │
│                            'A:a-b,B:c-d' for multimer mode. Use multiple --region-pair to add more.                                              │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Color scaling ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --vmax                    FLOAT  vmax for distance heatmap                                                                                       │
│ --vmax-percentile         FLOAT  Percentile used if vmax is not set [default: 95.0]                                                              │
│ --vdiff                   FLOAT  Max abs value for diff heatmap (0-centered)                                                                     │
│ --vdiff-percentile        FLOAT  Percentile used if vdiff is not set [default: 95.0]                                                             │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Output ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --out-path        TEXT  Directory to save figure files (png/pdf), default is current directory [default: .]                                      │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Mode ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --mode  -m      TEXT  Comparison mode: 'multimer' (default) or 'monomer'. [default: multimer]                                                    │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Plot Options ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --tick-step        INTEGER  Step size for ticks on the axes (multimer mode only) [default: 100]                                                  │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
```

## CLI

```bash
af3-vis --help
af3-vis contact-map-diff --help
...
```

## Programmatic API (Under Development)

```python
from alphafold3_seqvis_toolkit import contact_map_diff
```




## Test Cases

The following examples are provided to help you get started quickly.


### 🧬 Case 1: Validating DNA-Protein Complexes

**❓ The Question:**
How to validate AlphaFold3's DNA-protein complex predictions for chain A (protein) and M+N (DNA)?

> *   Should we prioritize **pLDDT scores** for chain A's protein domains and **ipTM** for M/N-DNA interfaces?
> *   What confidence thresholds matter most—chain A's local pLDDT (>90?) or M+N interface PAE (<10Å)?
> *   Can we trust predicted interactions between chain A (residues 1-300) and M/N if their interface pLDDT drops below 70?
> *   Do AF3's pLDDT/ipTM scores validate chain A-M/N interactions?

**✅ The Solution:**
Run the confidence analysis module to generate global and local metrics for these specific chains:

```bash
af3-vis confidence --global-json ./tests/test_data/CTCF_withDNA/fold_flznwitha6csedna_summary_confidences_0.json --full-json ./tests/test_data/CTCF_withDNA/fold_flznwitha6csedna_full_data_0.json -o ./tests/test_output/confidence -c A -c M -c N
```
In output directory, there will be several files generated, you can see them at [`./tests/test_output/confidence`](./tests/test_output/confidence)

For images, in addition to pdf format output, we also provide png format.

```bash
❯ tree -h ./tests/test_output/confidence
[4.0K]  ./tests/test_output/confidence
├── [ 22K]  flznwitha6csedna_global_confidence_chain_pair_iptm_heatmap.pdf
├── [ 20K]  flznwitha6csedna_global_confidence_chain_pair_pae_min_heatmap.pdf
├── [ 14K]  flznwitha6csedna_global_confidence_chain_ptm_iptm_barplot.pdf
├── [ 16K]  flznwitha6csedna_global_confidence_chain_ptm_iptm_lineplot.pdf
├── [ 201]  flznwitha6csedna_global_confidence_chain_ptm_iptm.tsv
├── [ 107]  flznwitha6csedna_global_confidence_SCALAR_measures.tsv
├── [322K]  flznwitha6csedna_local_confidence_atom_plddt_selected_chains_A_M_N.pdf
├── [ 84K]  flznwitha6csedna_local_confidence_contact_probability_matrix_selected_chains_A_M_N.pdf
├── [ 723]  flznwitha6csedna_local_confidence_overall_atom_plddt_statistics.tsv
└── [446K]  flznwitha6csedna_local_confidence_PAE_matrix_selected_chains_A_M_N.pdf

1 directory, 10 files
```

The above results are presented in order below:

<img src="./tests/test_output/confidence/flznwitha6csedna_global_confidence_chain_pair_iptm_heatmap.png" width="400" />

<img src="./tests/test_output/confidence/flznwitha6csedna_global_confidence_chain_pair_pae_min_heatmap.png" width="400" />

<img src="./tests/test_output/confidence/flznwitha6csedna_global_confidence_chain_ptm_iptm_barplot.png" width="400" />

<img src="./tests/test_output/confidence/flznwitha6csedna_global_confidence_chain_ptm_iptm_lineplot.png" width="400" />

```
Chain_Index	Chain_ipTM_Score	Chain_pTM_Score
A	0.91	0.38
B	0.57	nan
C	0.46	nan
D	0.49	nan
E	0.57	nan
F	0.64	nan
G	0.64	nan
H	0.55	nan
I	0.4	nan
J	0.63	nan
K	0.32	nan
L	0.33	nan
M	0.37	0.27
N	0.31	0.27
```

```
Fraction Disordered	0.58
Has Clash	0.0
ipTM	0.74
Number of Recycles	10.0
pTM	0.43
Ranking Score	0.97
```

<img src="./tests/test_output/confidence/flznwitha6csedna_local_confidence_atom_plddt_selected_chains_A_M_N.png" width="600" />

<img src="./tests/test_output/confidence/flznwitha6csedna_local_confidence_contact_probability_matrix_selected_chains_A_M_N.png" width="600" />

```
Chain_ID	Mean_pLDDT	Median_pLDDT	Std_pLDDT	Fraction_Very_High(>90)	Fraction_High(90-70)	Fraction_Low(70-50)	Fraction_Very_Low(<=50)
All	63.73	64.24	22.04	0.13	0.33	0.17	0.38
A	60.30	51.05	23.26	0.17	0.24	0.11	0.49
B	94.32	94.32	0.00	1.00	0.00	0.00	0.00
C	81.83	81.83	0.00	0.00	1.00	0.00	0.00
D	82.27	82.27	0.00	0.00	1.00	0.00	0.00
E	88.09	88.09	0.00	0.00	1.00	0.00	0.00
F	93.53	93.53	0.00	1.00	0.00	0.00	0.00
G	94.12	94.12	0.00	1.00	0.00	0.00	0.00
H	92.41	92.41	0.00	1.00	0.00	0.00	0.00
I	74.64	74.64	0.00	0.00	1.00	0.00	0.00
J	92.16	92.16	0.00	1.00	0.00	0.00	0.00
K	62.98	62.98	0.00	0.00	0.00	1.00	0.00
L	70.34	70.34	0.00	0.00	1.00	0.00	0.00
M	75.49	78.63	12.07	0.03	0.62	0.35	0.00
N	74.75	77.10	10.78	0.00	0.63	0.37	0.00
```
<img src="./tests/test_output/confidence/flznwitha6csedna_local_confidence_PAE_matrix_selected_chains_A_M_N.png" width="600" />



### 🧬 Case 2: Visualizing Structural Confidence of Molecules in PyMOL

**❓ The Question:**
How can I visualize and check the confidence score of each specific structural region in PyMOL?

**✅ The Solution:**
Run the ./pymol_utils/af3_plddt_color.py script:

1. Load YOUR prediction output file into pymol. In the pymol command prompt:
```bash
load fold_{YOUR_JOB_NAME}_model_{i}.cif, model_name
```

![alt text](./Figs/pymol1.png)

2. Load our script into pymol. In the pymol command prompt:

```bash
run ./utils/af3_plddt_color.py 
```

![alt text](./Figs/pymol2.png)

3. Invoke the script in the pymol command prompt as so:

```bash
af3_plddt_color  model_name
```

![alt text](./Figs/pymol3.png)

![alt text](./Figs/pymol4.png)

4. You can also select a specific chain to visualize:

For example, we want to color only the A chain within this CTCF-DNA complex

```bash
select CTCF_DNA_A_chain, chain A
af3_color_plddt(selection="CTCF_DNA_A_chain")

# or format like
af3_color_plddt(selection="CTCF_DNA and chain A+M+N")
```

![alt text](./Figs/pymol5.png)
![alt text](./Figs/pymol6.png)
![alt text](./Figs/pymol7.png)



### 🧬 Case 3: Visualizing Structural Changes of Protein CTCF under TWO conditions

**❓ The Question:**
How to visualize and analyze the structural changes of the CTCF protein in two states: when it is bound to DNA, and when it is in an unbound (free) state?

> *   For example, we are interested in some specific regions, and we want to know the change of these regions, how can we visualize that?

**✅ The Solution:**
Run the contact map comparison module to CHECK the DIFFERENCE, this may give you some insight.

```bash
af3-vis contact-map-diff --mmcif-a ./tests/test_data/CTCF_withoutDNA/fold_humanwithzn_model_0.cif  --mmcif-b ./tests/test_data/CTCF_withDNA/fold_flznwitha6csedna_model_0.cif  --region-pair 265:576,0:15 --region-pair 265:576,42:54 --region-pair 265:576,83:93 --region-pair 265:576,170:189 --region-pair 265:576,214:241 --region-pair 265:576,578:589 --region-pair 265:576,606:639 --region-pair 265:576,691:720 --chain-a A --chain-b A --out-path ./tests/test_output/comparison
```

The regions to be compared are given symmetrically by green boxes

<img src="./tests/test_output/comparison/humanwithzn_A_vs_flznwitha6csedna_A_265:576,0:15_265:576,42:54_265:576,83:93_265:576,170:189_265:576,214:241_265:576,578:589_265:576,606:639_265:576,691:720.png" width="600" />

Our tools even support multi-chains!
```bash
af3-vis contact-map-diff  --mmcif-a ./tests/test_data/Multi_protein_complex/fold_ctcf_2_nodna_model_0.cif  --mmcif-b ./tests/test_data/Multi_protein_complex/fold_ctcf_2_dna_model_1.cif  --chain-a A,B --chain-b A,B --out-path ./tests/test_output/comparison
```
<img src="./tests/test_output/comparison/ctcf_2_nodna_A_B_vs_ctcf_2_dna_A_B_None.png" width="600" />

And region selection!
```bash
af3-vis contact-map-diff  --mmcif-a ./tests/test_data/Multi_protein_complex/fold_ctcf_2_nodna_model_0.cif  --mmcif-b ./tests/test_data/Multi_protein_complex/fold_ctcf_2_dna_model_1.cif  --chain-a A,B --chain-b A,B  --region-pair A:265:576,B:0:15 --region-pair B:265:576,B:42:54 --out-path ./tests/test_output/comparison
```
<img src="./tests/test_output/comparison/ctcf_2_nodna_A_B_vs_ctcf_2_dna_A_B_A:265:576,B:0:15_B:265:576,B:42:54.png" width="600" />

### 🧬 Case 4: Visualizing Protein Sequence-based Feature Track in residue-residue contact map

**❓ The Question:**
How can I determine which segment of a protein sequence interacts most strongly in a protein-DNA complex, what characteristics this region possesses, and whether there are any unique features of this region?

**✅ The Solution:**
Run the contact map visualization module to CHECK the interaction details, this may give you some insight.

Here, I will take a structure of [(2 CTCFs with 2 DNA strands and 22 Zn2+)](./tests/test_data/Multi_protein_complex/fold_ctcf_2_dna_model_1.cif) as an example. 
This structure has 26 chains, where chain A and chain B are protein CTCF, chain Y and chain Z are DNAs, and the remaining chains are all ion Zn2+. I just want to see how DNA and proteins interact, so we only need to see Chain A/B/Y/Z

```bash
A/B: 2 CTCF 
C~X: Zn2+
Y/Z: 2 DNA srtand
```

simply run
```bash
af3-vis contact-map-vis --mmcif-file ./tests/test_data/Multi_protein_complex/fold_ctcf_2_dna_model_1.cif \ 
-c A -c B -c Y -c Z \
-o ./tests/test_output/visualization/notrack
```
and the output figure is like below

![](./tests/test_output/visualization/notrack/ctcf_2_dna_contact_map.png)

Another beautiful example see here

![](./tests/test_output/visualization/notrack/7W1M_contact_map.png)

Regardless, assuming we possess sequence-derived feature annotations for these two proteins, our primary interest lies in exploring the structural basis underlying these features.

So we can use track information to seek further, as for `contact-map-vis --mode track` command, 

there are 2 files needed:

- Track bed file: 5-column TSV format —— [Chain, TrackName, Start, End, Value].This format is designed to integrate and standardize feature-related data.
  - 0-indexed
  - must have a column name row
  - value must be a numerical type or a catrgorical string

    We present a simulated track bed file generated by script [SIMULATED TRACK SCRIPT](./tests/test_data/Multi_protein_complex/simulated_tracks.py)  here: [SIMULATED TRACK FILE](./tests/test_output/visualization/track/simulated_tracks.bed)

    ```bash
    chain_id	track_name	start	end	value
    A	Disorder	0	9	0.1939202398057196
    A	Disorder	10	19	0.2661143003553823
    A	Disorder	20	29	0.09356952954622577
    A	Disorder	30	39	0.7224995256611805
    A	Disorder	40	49	0.21211383891211832
    ...
    ```

- Color config file: We strongly recommend you to use a JSON file.
  - Using {TrackName : Color config} format
  - TrackName must be consitent with "TrackName" column in Track bed file above
  - For Numerical-type Track, we recommend using single color (like "orange" or "#FF1010"), or a colormap (like "tab20")
  - For Categorical-type Track, if you know the exact number of categories and wish to assign a specific color to each category, we recommend using a detailed color dictionary. If you do not have this information (or do not need custom color assignments), we suggest using a colormap—note that the number of colors in the colormap you provide must exceed the number of categories in the track. Examples of suitable colormaps like "tab20", and we will automatically assign distinct colors from the colormap to each category for you.

    We present a simulated track color config file here: [SIMULATED COLOR CONFIG FILE](./tests/test_output/visualization/track/simulated_tracks_color_config.json)
    ```python
    import json

    color_config = {
        "Disorder": "orange",
        "Domains": {
            "N-Term": "green",
            "DNA-Binding": "red",
            "Zinc-Finger": "purple",
            "C-Term": "blue",
            "Linker": "gray"
        }
    }

    # Save color configuration
    with open("./tests/test_output/visualization/track/simulated_tracks_color_config.json", "w") as f:
        json.dump(color_config, f)
    ```

Now, we can simply run
```bash
af3-vis contact-map-vis --mode track --mmcif-file ./tests/test_data/Multi_protein_complex/fold_ctcf_2_dna_model_1.cif \ 
--track-bed-file ./tests/test_output/visualization/track/simulated_tracks.bed \ 
--color-config ./tests/test_output/visualization/track/simulated_tracks_color_config.json \ 
-c A -c B -c Y -c Z \ 
-o ./tests/test_output/visualization/track

```
and the output figure is like below

![](./tests/test_output/visualization/track/ctcf_2_dna_contact_map.png)

Now we can check the Disorder and Domain annotations in the regions we are interested in!


## 📝 TODOs 

<details>
<summary><b>Module 1: Confidence Metrics Plotting</b></summary>

> - [ ] Plotting details and token index details: 0-index for differnet chains in atom plddt figure
> - [ ] Find/mapping from mmCIF: residue/token mapping to allow residue_plddts figure. 
> 
>   Cause we do not have a residue_plddts data, and we currently did not find a way mapping atom index to residue/token index (maybe from mmCIF parser), so there is no residue_plddts figure currently
> - [ ] Scoring function for interprotein interactions in AlphaFold2 and AlphaFold3 UPDATED: We are going to use [IPSAE](https://github.com/DunbrackLab/IPSAE)

</details>

<details>
<summary><b>Module 2: Contact Map Visualization</b></summary>

> - [ ] Region Selection Box: see in module3-Two Structures Comparison
> - [ ] Identify local HOT SPOT rgeion (residue set whose distance < DIST threshold)
> - [ ] Index within different chains overlap with each other, especially for index 0 in following chain and end index in previous chain, maybe we can rotate the xticks_labels.
> - [ ] If single chain present, there is no need to draw chain bars.
>
>   Our tool currently will draw chain bars whenever the structure poesses one single chain or multiple chains.

</details>

<details>
<summary><b>Module 3: Two Structures Comparison</b></summary>

> - [x] Should consider multi-proteins complex, and we can select which chain to compare
>
> **💡Solution:** Done. Supporting both monomer mode and multimer mode.
> - [x] In addition to proteins, other type of molecules holding the same sequence index before and after some treatment should also be taken consideration into comparing.
>
> **💡Solution:** Done. Supporting multi molecule type.
> - [x] For multimers, in addition to choose which chain to compare, we should also enable which region in which chain to focus(highlight in green box or something)
> 
> **💡Solution:** Done. Supporting Different rgeions from dofferent chains to compare for multimers.
> - [ ] Mutation analysis: Like deletion, insertion, substitution and Order inversion. 
>
>   Currently, our comparison module only supports `structures with identical sequences`. This is because we require matching sequence indices to perform alignment between the pre- and post- states, thereby avoiding potential bias. 
>   For deletion events, a false gap will be inserted at the position of the missing residue to optimize visualization. Currently, we have not identified further avenues to deepen the mutation analysis. If you have any ideas and tricks, please feel free to contact us!
>  - [ ] Sequence-based feature tracks intergrated, see Module2
>  - [ ] Structure alignment: Maybe we can compare those regions which can be aligned in same index and then we feed these sliced regions into heatmap construction (e.g. for deletion, we can only compare the regions to be indexed identically other than introducing a gap). Or do we actually really need regions with identical index? I mean, structure alignments themselves may not necessarily be converted into heatmap visualization, we can transform them in another way?
</details>

<details>
<summary><b>Module 4: Sequence-based feature tracks intergrated</b></summary>

> - [x] What file format should we input? BED or json?
>
> **💡Solution:** We utilize a customized BED format for the input of track annotations; please refer to the INPUT Details in Module 2 for further information.
> - [x] For multi-protein complexes, each constituent protein should have a dedicated sequence-based feature track. 
> 
>   Currently, in visualizations such as residue Contact maps(module2)/PAE heatmaps(module1) and so on, our tool only supports the display of a single sequence-based feature track for one protein. Thus, it is necessary to upgrade the tool’s functionality from supporting **one protein with one track** to enabling **multiple proteins with multiple tracks**.
>
> **💡Solution:** Done in module2.

</details>

<details>
<summary><b>Module 5: Pymol Extension</b></summary>

> - [ ] Scripts to help visualize Structures in Pymol/ChimeraX including: pLDDT(Finished)/Chain/Molecule type/low PAE contacts and so on

</details>

<details>
<summary><b>Others: Maybe NEW module?</b></summary>

> - [ ] AlphaMissense predicted pathogenicity scores intergrated 
> - [ ] Mutation analysis: Like deletion, insertion, substitution and Order inversion. 
> 
>   For deletion events, a false gap will be inserted at the position of the missing residue to optimize visualization. Currently, we have not identified further avenues to deepen the mutation analysis. If you have any ideas and tricks, please feel free to contact us!
> - [ ] Free energy of folding analysis
> - [ ] mmCIF parser and further analysis —— [Bio.PDB](https://biopython.org/docs/latest/Tutorial/chapter_pdb.html)
> - [ ] Structure Alignment or Similarity search Using FoldSeek or [rcsb-embedding-model](https://github.com/rcsb/rcsb-embedding-model)

</details>


### 🤩 We warmly welcome contributions from the community to enhancing visualization for this project! If you have ideas for expanding modules above like mutation analysis, creative insights to enhance visualization, specific feature requests (e.g., PR support, workflow optimizations, or additional analytical modules), or any other suggestions to improve this work, please feel free to reach out via GitHub Issues, submit a Pull Request, or start a discussion in the Comments section. Your input will be invaluable in advancing this project!