pax_global_header00006660000000000000000000000064152121071570014513gustar00rootroot0000000000000052 comment=19d55fb7a13a7e68e7b0de35a6e31575d90c53a5 pdb-tools-2.7.0/000077500000000000000000000000001521210715700134245ustar00rootroot00000000000000pdb-tools-2.7.0/.bumpversion.toml000066400000000000000000000011561521210715700167530ustar00rootroot00000000000000[tool.bumpversion] current_version = "2.7.0" parse = "(?P\\d+)\\.(?P\\d+)\\.(?P\\d+)" serialize = ["{major}.{minor}.{patch}"] search = "{current_version}" replace = "{new_version}" regex = false ignore_missing_version = false ignore_missing_files = false tag = true sign_tags = false tag_name = "v{new_version}" tag_message = "{current_version} → {new_version}" allow_dirty = false commit = true message = "[SKIP] {current_version} → {new_version}" moveable_tags = [] commit_args = "" setup_hooks = [] pre_commit_hooks = [] post_commit_hooks = [] [[tool.bumpversion.files]] filename = "setup.py" pdb-tools-2.7.0/.gitattributes000066400000000000000000000000531521210715700163150ustar00rootroot00000000000000# Set LF for Python files *py text eol=lf pdb-tools-2.7.0/.github/000077500000000000000000000000001521210715700147645ustar00rootroot00000000000000pdb-tools-2.7.0/.github/ISSUE_TEMPLATE/000077500000000000000000000000001521210715700171475ustar00rootroot00000000000000pdb-tools-2.7.0/.github/ISSUE_TEMPLATE/bug_report.md000066400000000000000000000011531521210715700216410ustar00rootroot00000000000000--- name: Bug report about: Create a report to help us improve title: '' labels: bug assignees: '' --- **Describe the bug** A clear and concise description of what the bug is. Ex. My PDB file is blank after I use this tool! **To Reproduce** Steps to reproduce the behavior. Preferrably, a code snippet. ``` pdb_fetch.py 1xxx.pdb | pdb_oopsy.py > result cat result # result is empty! ``` **Expected behavior** The output PDB file should not be blank, but should have YY replaced! **Desktop (please complete the following information):** - OS: [e.g. Mac OS, Linux, Windows] - Python Version [e.g. 2.7, 3.6, 3.7] pdb-tools-2.7.0/.github/ISSUE_TEMPLATE/tool-request.md000066400000000000000000000014441521210715700221370ustar00rootroot00000000000000--- name: Tool request about: Suggest an idea for a new pdb-tool title: '' labels: Tool Request assignees: '' --- **Is your tool request related to a problem? Please describe.** A clear and concise description of what the problem is. Ex. I'm always trying to do [...] **Describe the solution you'd like** A clear and concise description of what you want to happen. Ex. I would like a tool that did [...] **Does any of the existing tools or a combination of them do what you want?** A clear and concise description of any alternative solutions or features you've considered. **Remember** Each `pdb-tools` should do one and one job only. If you have to describe what you want using an _and_, probably it is the job for at least _two_ tools. We want simple tools that can be combined, for flexibility. pdb-tools-2.7.0/.github/workflows/000077500000000000000000000000001521210715700170215ustar00rootroot00000000000000pdb-tools-2.7.0/.github/workflows/bump-version-on-push.yml000066400000000000000000000054551521210715700235720ustar00rootroot00000000000000--- name: bump and package on: push: branches: - master jobs: bump-version: runs-on: ubuntu-latest permissions: contents: write outputs: skip-bump: ${{ steps.determine-bump.outputs.skip-bump }} steps: - name: Checkout uses: actions/checkout@v6 - name: Setting up git config shell: bash env: GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | git config --global user.email "${GITHUB_ACTOR_ID}+${GITHUB_ACTOR}@users.noreply.github.com" git config --global user.name "$(gh api /users/${GITHUB_ACTOR} | jq .name -r)" git config -l - uses: actions/setup-python@v6 with: python-version: "3.13" - name: Install bump-my-version run: | pip install "bump-my-version==1.2.6" - name: Determine bump type id: determine-bump run: | COMMIT_MSG="${{ github.event.head_commit.message }}" echo "PR title: $COMMIT_MSG" if [[ "$COMMIT_MSG" =~ ^\[MAJOR\] ]]; then echo "bump-type=major" >> $GITHUB_OUTPUT elif [[ "$COMMIT_MSG" =~ ^\[MINOR\] ]]; then echo "bump-type=minor" >> $GITHUB_OUTPUT elif [[ "$COMMIT_MSG" =~ ^\[PATCH\] ]]; then echo "bump-type=patch" >> $GITHUB_OUTPUT elif [[ "$COMMIT_MSG" =~ ^\[SKIP\] ]]; then echo "skip-bump=true" >> $GITHUB_OUTPUT echo "::notice::Version bump skipped based on PR title" exit 0 else echo "skip-bump=true" >> $GITHUB_OUTPUT echo "::notice::Skipping - commit message does not match [MAJOR], [MINOR], [PATCH], or [SKIP]" exit 0 fi - name: Bump version if: steps.determine-bump.outputs.skip-bump != 'true' run: | bump-my-version bump --verbose ${{ steps.determine-bump.outputs.bump-type }} - name: Push changes uses: ad-m/github-push-action@master with: github_token: ${{ secrets.GITHUB_TOKEN }} branch: ${{ github.ref }} publish: if: needs.bump-version.outputs.skip-bump != 'true' name: builds and publishes to pypi needs: [bump-version] runs-on: ubuntu-latest environment: name: pypi url: https://pypi.org/p/pdb-tools permissions: id-token: write steps: - uses: actions/checkout@v6 with: ref: master - uses: actions/setup-python@v6 with: python-version: "3.13" - name: install dependencies run: | python -m pip install --upgrade pip python -m pip install --upgrade build - name: build run: | python -m build - name: Publish package distributions to PyPI uses: pypa/gh-action-pypi-publish@release/v1 pdb-tools-2.7.0/.github/workflows/ci.yml000066400000000000000000000037661521210715700201530ustar00rootroot00000000000000--- name: ci on: pull_request: types: [opened, edited, synchronize] branches: - master push: branches: - master jobs: linter: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: set up python uses: actions/setup-python@v5 with: python-version: "3.13" - name: install dependencies run: | python -m pip install --upgrade pip python -m pip install flake8 - name: Linter run: flake8 . test: name: test runs-on: ${{ matrix.platform }} strategy: matrix: platform: [ubuntu-latest, macos-latest, windows-latest] python-version: ["3.9", "3.10", "3.11", "3.12", "3.13", "3.14"] steps: - uses: actions/checkout@v4 - name: Set up Python ${{ matrix.python-version }} uses: actions/setup-python@v5 with: python-version: ${{ matrix.python-version }} - name: install dependencies run: | python -m pip install --upgrade pip python -m pip install --upgrade build twine coverage - name: build run: | python --version python -m build twine check dist/*.whl twine check dist/*.tar.gz - name: install pdb-tools run: | python -m pip install . - name: run tests run: | if [ "${{ runner.os }}" = "Linux" ]; then script -q -e -c "coverage run -m unittest discover -s tests -p 'test_*.py'" else SKIP_TTY_TESTS=true coverage run -m unittest discover -s tests -p "test_*.py" fi coverage xml shell: bash # - uses: codacy/codacy-coverage-reporter-action@v1 # if: >- # ${{ github.event_name != 'pull_request' || # github.event.pull_request.head.repo.full_name == github.repository }} # with: # project-token: ${{ secrets.CODACY_PROJECT_TOKEN }} # coverage-reports: ./coverage.xml pdb-tools-2.7.0/.github/workflows/pr-title-check.yml000066400000000000000000000015051521210715700223600ustar00rootroot00000000000000--- name: PR title check on: pull_request: types: [opened, edited, synchronize, reopened] jobs: check-title: runs-on: ubuntu-latest steps: - name: Check PR title format env: PR_TITLE: ${{ github.event.pull_request.title }} run: | echo "PR title: $PR_TITLE" if [[ "$PR_TITLE" =~ ^\[(MAJOR|MINOR|PATCH|SKIP)\] ]]; then echo "✓ PR title has valid version tag" exit 0 else echo "::error::PR title must start with [MAJOR], [MINOR], [PATCH], or [SKIP]" echo "" echo "Examples:" echo " [MAJOR] Breaking API change" echo " [MINOR] Add new feature" echo " [PATCH] Fix bug in parser" echo " [SKIP] Update documentation" exit 1 fi pdb-tools-2.7.0/.github/workflows/stale.yml000066400000000000000000000020531521210715700206540ustar00rootroot00000000000000name: "Close stale issues and PRs" on: schedule: - cron: "30 1 * * *" workflow_dispatch: jobs: stale: runs-on: ubuntu-latest permissions: contents: write issues: write pull-requests: write actions: write steps: - uses: actions/stale@v10 with: stale-pr-message: "This PR is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 15 days." stale-issue-message: "This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 15 days." close-pr-message: 'This PR was closed because it has been stalled for 15 days with no activity.' close-issue-message: 'This issue was closed because it has been stalled for 15 days with no activity.' days-before-stale: 90 days-before-close: 15 exempt-issue-labels: "bug" exempt-pr-labels: "bug" remove-stale-when-updated: true operations-per-run: 100 pdb-tools-2.7.0/.gitignore000066400000000000000000000001271521210715700154140ustar00rootroot00000000000000# Python setuptools build/ dist/ *egg-info/ *__pycache__ *.pyc .coverage coverage.xml pdb-tools-2.7.0/CODE_OF_CONDUCT.md000066400000000000000000000064411521210715700162300ustar00rootroot00000000000000# Contributor Covenant Code of Conduct ## Our Pledge In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. ## Our Standards Examples of behavior that contributes to creating a positive environment include: * Using welcoming and inclusive language * Being respectful of differing viewpoints and experiences * Gracefully accepting constructive criticism * Focusing on what is best for the community * Showing empathy towards other community members Examples of unacceptable behavior by participants include: * The use of sexualized language or imagery and unwelcome sexual attention or advances * Trolling, insulting/derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or electronic address, without explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Our Responsibilities Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. ## Scope This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at j.p.g.l.m.rodrigues@gmail.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html [homepage]: https://www.contributor-covenant.org For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq pdb-tools-2.7.0/CONTRIBUTING.md000066400000000000000000000151111521210715700156540ustar00rootroot00000000000000# Contributing to pdb-tools First off, thank you for taking the time to contribute! The tone of the following 'guidelines' might seem a bit harsh (a lot of *do nots*) but it will make everyone's life easier. Make sure you read through this at least once before issuing a pull request or opening an issue. ## What should I know before getting started? The crux of any tool of `pdb-tools` is simplicity. Simplicity both for the end-user but also for developers. You will find that the tools often repeat a lot of code, for example the `check_input` functions. While this might look ugly from a development point of view, it makes scripts simpler (fancy options will very quickly turn ugly), faster (no imports) and more understandable for old and new developers. This is also why we do not make use of `argparse`. A corolary of this simplicity is that every tool should do **one and one job only**. The only exception to this is `pdb_tidy` and it will very likely remain so. Even then, its job is to 'produce a valid PDB', despite doing multiple tasks under the hood. The tools are meant to be chained together, so if you want to have two tasks accomplished, write two tools and have them talk. Finally. **Dependencies are strictly not allowed**. Take this as an exercise to work on your Python Standard Library skills. ## How do I write an issue? If you found a problem with one of the tools, if it does not behave as expected, if you think it should do something different or something more, or if you think that there should be a tool do to something new, please do open an issue. If a tool is not working, let us know exactly what you did and what the outcome was. Whatever you tell us that helps us reproduce your workflow will make our job much easier to answer your question and provide a fix if necessary.    **Bad issue reporter** pdb_reatom.py does not work. Please fix. # believe it or not people do write this.    **Good issue reporter** I tried using pdb_reatom.py on a PDB file and it did not renumber nitrogen atoms. Here is an example: $ cat 1abc.pdb ATOM 9 N ASN A 1 22.066 40.557 1.420 1.00 1.00 ATOM 2 N ASN A 2 43.123 76.234 0.123 1.00 1.00 END $ pdb_reatom 1abc.pdb ATOM 9 N ASN A 1 22.066 40.557 1.420 1.00 1.00 ATOM 2 N ASN A 2 43.123 76.234 0.123 1.00 1.00 END I was expecting the two atoms to be consecutively renumbered from 1. I am using pdb-tools version 2.0.0: $ pip show pdb-tools Name: pdb-tools Version: 2.0.0 Location: /path/to/virtualenv/lib/python3.7/site-packages ## How do I contribute code? We welcome and will gladly review any pull request. If you have never used git or GitHub before, have a look at the [guides](https://guides.github.com/) page. To contribute to `pdb-tools`, use the *Fork* button to create your own copy of the `pdb-tools` repository. Then, download `git` on your laptop/desktop computer and proceed like the snippet below, where we pretend to add a new tool: ```bash # Clone your own fork of pdb-tools git clone https://github.com/yourusername/pdb-tools.git cd pdb-tools # Add our repository as 'upstream' to make sure you are using the latest # version of the code. git remote add upstream https://github.com/haddocking/pdb-tools.git # Pull our master to update your local version # If there are changes, you should push them to the 'master' of your fork. git pull upstream master git push origin master # Update your fork if necessary # Create a feature branch to start working on your new tool. # Name the new branch clearly and concisely after the change you are proposing # # We use feature branches to avoid conflicts in the master branch. Updating # should always be smooth and you can deal with merge conflicts in your branches git checkout -b pdb_newtool # Work on your new tool! # Include hours of work here and make sure to read the conventions below. # Also, try to add a test case too under tests/ # We can help you fleshing it out if you need it. ... # If you are making changes to an existing tool, run the test suite before # committing your changes. python setup.py test # When you have committed all your changes, run flake8 to make sure there are # no style issues. You can find our flake8 settings in `setup.cfg`. python -m pip install flake8 flake8 . # Update the documentation, if you added new tools (or changed docstrings). cd docs/ python doctools.py git add index.md && git commit -m "Updated documentation" # When there are no issues left, push to your fork on github git push origin pdb_newtool # And then, online, create a pull request. # That is it. ``` ## Conventions In an effort to try and make all tools look the same, stick to these conventions when writing a new one or modifying an existing one: ### Coding conventions Every pull request will be checked for style using Flake8. We ignore line length warnings and the use of lambdas. Do not abuse the first one though. We always try to stick to 80 characters, unless it's stupid to do so. * Do not use camelCase. Stick to snake_case. * Write docstrings and comment your code, specially if it is not obvious! * Name your variables properly, we don't charge you for a few extra lines. ### Tool design conventions * Every tool should have the same structure: `check_input`, `do_task`, `main`. Do **not** deviate from this, unless you absolutely need to. * User interfaces must follow the `pdb_tool [-option] ` paradigm. Do not try and make it `pdb_tool -opt1 -opt2 -opt3`. See `pdb_rplchain` and `pdb_wc` for good examples of how to handle multiple options. * Avoid reading the entire file in memory unless you have to. This makes it nice for people processing very large files. * Following the previous item, make use of generators (`yield`) to output the results of your tool. ## Merging Pull Requests If you are tasked with merging a pull request yourself, you should know that there is an automated job running every time a push is made to the master branch. This job will trigger a version bump and automatically publish the new package to PyPi. By default, only the patch (x.x.Y) number is incremented. If you want to trigger a minor version (x.Y.x) update, start your commit with `[FEATURE]`. Note that since we use merge commits, this means you have to edit the title of the merge commit. It is your responsibility to handle this as a package maintainer! Finally, if your last commit message starts with `[SKIP]`, the automated job does not run, so use this flag if your commits are for documentation, README, etc. pdb-tools-2.7.0/LICENSE000066400000000000000000000341251521210715700144360ustar00rootroot00000000000000 Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in Appendix 1 below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. See also Appendix 2 below for specific licensing conditions regarding a third party piece of code used in pdb-tools. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX 1: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. APPENDIX 2: Third party code from https://github.com/cctbx/cctbx_project Some of the tools in pdb-tools (pdb_reatom, pdb_tidy and pdb_fromcif) are using code from the cctbx distribution (https://github.com/cctbx/cctbx_project). The following license agreement applies to it. cctbx Copyright (c) 2006 - 2026, The Regents of the University of California, through Lawrence Berkeley National Laboratory (subject to receipt of any required approvals from the U.S. Dept. of Energy). All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: (1) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. (2) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. (3) Neither the name of the University of California, Lawrence Berkeley National Laboratory, U.S. Dept. of Energy nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. You are under no obligation whatsoever to provide any bug fixes, patches, or upgrades to the features, functionality or performance of the source code ("Enhancements") to anyone; however, if you choose to make your Enhancements available either publicly, or directly to Lawrence Berkeley National Laboratory, without imposing a separate written license agreement for such Enhancements, then you hereby grant the following license: a non-exclusive, royalty-free perpetual license to install, use, modify, prepare derivative works, incorporate into other computer software, distribute, and sublicense such enhancements or derivative works thereof, in binary and source code form. Copyright 2018 João Pedro Rodrigues Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. pdb-tools-2.7.0/MANIFEST.in000066400000000000000000000005771521210715700151730ustar00rootroot00000000000000graft pdbtools include LICENSE include README.md include citation.tex exclude .appveyor.yml exclude .bumpversion.cfg exclude .coveragerc exclude .travis.yml exclude CODE_OF_CONDUCT.md exclude CONTRIBUTING.md exclude MANIFEST.in exclude PACKING.md exclude tox.ini prune docs prune tests global-exclude *.py[cod] __pycache__/* *.so *.dylib global-exclude *.swp global-exclude tags pdb-tools-2.7.0/PACKAGING.md000066400000000000000000000021641521210715700152350ustar00rootroot00000000000000# Packaging pdb-tools This guide describes (roughly) how to package `pdb-tools` into something `pip` can handle. ## Versioning `pdb-tools` uses semantic versioning: MAJOR.MINOR.PATCH (e.g. 2.0.0). It works more or less like this: * For every new release fixing bugs, increment the PATCH counter (e.g. 2.0.1). * For every release adding minor features to tools or new tools that do not impact any of the existing ones, increment MINOR (e.g. 2.1.0). * For major changes that will most likely impact the usage of existing tools, increment MAJOR (e.g. 3.0.0). In practice, when packaging the distribution we should update the version number in `setup.py` accordingly (otherwise `twine` will give an error). ## Packaging This is a rough guide to building a distributable package: ### (1) Ensure all tests pass: ```bash python setup.py test ``` 2. Ensure there are no warnings from flake8: ```bash flake8 --ignore=E501,E731 ``` 3. Build the distributable package: ```bash python setup.py sdist bdist_wheel # Upload to PyPI: testing repo for now. #twine upload --repository-url https://test.pypi.org/legacy/ dist/* twine upload dist/* ``` pdb-tools-2.7.0/README.md000066400000000000000000000125441521210715700147110ustar00rootroot00000000000000# pdb-tools [![PyPI version](https://badge.fury.io/py/pdb-tools.svg)](https://pypi.python.org/pypi/pdb-tools) [![PyPi Downloads](https://img.shields.io/pypi/dm/pdb-tools.svg)](https://pypi.python.org/pypi/pdb-tools) [![ci](https://github.com/haddocking/pdb-tools/actions/workflows/ci.yml/badge.svg)](https://github.com/haddocking/pdb-tools/actions/workflows/ci.yml) [![DOI](https://zenodo.org/badge/27217350.svg)](https://doi.org/10.12688/f1000research.17456.1) A swiss army knife for manipulating and editing PDB files. ## Looking for the _other_ pdb-tools? The Harms lab maintains a set of tools also called `pdbtools`, which perform a slightly different set of functions. You can find them [here](https://github.com/harmslab/pdbtools). ## About Manipulating PDB files is often painful. Extracting a particular chain or set of residues, renumbering residues, splitting or merging models and chains, or just ensuring the file is conforming to the PDB specifications are examples of tasks that can be done using any decent parsing library or graphical interface. These, however, almost always require 1) scripting knowledge, 2) time, and 3) installing one or more programs. `pdb-tools` were designed to be a swiss-knife for the PDB format. They have no external dependencies, besides obviously the [Python programming language](http://www.python.org). They are the descendant of a set of old FORTRAN77 programs that had the particular advantage of working with streams, i.e. the output of one script could be piped into another. Since FORTRAN77 is a pain too, I rewrote them in Python and added a few more utilities. The philosophy of the scripts is simple: one script, one task. If you want to do two things, pipe the scripts together. Requests for new scripts will be taken into consideration - use the Issues button or write them yourself and create a Pull Request. ## Installation Instructions `pdb-tools` are available on PyPi and can be installed though `pip`. This is the recommended way as it makes updating/uninstalling rather simple: ```bash pip install pdb-tools ``` Because we use semantic versioning in the development of `pdb-tools`, every bugfix or new feature results in a new version of the software that is automatically published on PyPI. As such, there is no difference between the code on github and the latest version you can install with `pip`. To update your installation to the latest version of the code run: ```bash pip install --upgrade pdb-tools ``` ## What can I do with them? The names of the tools should be self-explanatory. Their command-line interface is also pretty consistent. Therefore, here is a couple of examples to get you started: * Downloading a structure ```bash pdb_fetch 1brs > 1brs.pdb # 6 chains pdb_fetch -biounit 1brs > 1brs.pdb # 2 chains ``` * Renumbering a structure ```bash pdb_reres -1 1ctf.pdb > 1ctf_renumbered.pdb ``` * Selecting chain(s) ```bash pdb_selchain -A 1brs.pdb > 1brs_A.pdb pdb_selchain -A,D 1brs.pdb > 1brs_AD.pdb ``` * Deleting hydrogens ```bash pdb_delelem -H 1brs.pdb > 1brs_noH.pdb ``` * Selecting backbone atoms ```bash pdb_selatom -CA,C,N,O 1brs.pdb > 1brs_bb.pdb ``` * Selecting chains, removing HETATM, and producing a valid PDB file ```bash pdb_selchain -A,D 1brs.pdb | pdb_delhetatm | pdb_tidy > 1brs_AD_noHET.pdb ``` *Note: On Windows the tools will have the `.exe` extension.* ## What _can't_ I do with them? Operations that involve coordinates or numerical calculations are usually not in the scope of `pdb-tools`. Use a proper library for that, it will be much faster and scalable. Also, although we provide mmCIF<->PDB converters, we do not support large mmCIF files with more than 99999 atoms, or 9999 residues in a single chain. Our tools will complain if you try using them on such a molecule. ## Citation We finally decided to write up a small publication describing the tools. If you used them in a project that is going to be published, please cite us: ``` Rodrigues JPGLM, Teixeira JMC, Trellet M and Bonvin AMJJ. pdb-tools: a swiss army knife for molecular structures. F1000Research 2018, 7:1961 (https://doi.org/10.12688/f1000research.17456.1) ``` If you use a reference manager that supports BibTex, use this record: ``` @Article{ 10.12688/f1000research.17456.1, AUTHOR = { Rodrigues, JPGLM and Teixeira, JMC and Trellet, M and Bonvin, AMJJ}, TITLE = {pdb-tools: a swiss army knife for molecular structures [version 1; peer review: 2 approved] }, JOURNAL = {F1000Research}, VOLUME = {7}, YEAR = {2018}, NUMBER = {1961}, DOI = {10.12688/f1000research.17456.1} } ``` ## Requirements `pdb-tools` should run on Python 2.7+ and Python 3.x. We test on Python 2.7, 3.6, and 3.7. There are no dependencies. ## Installing from Source Download the zip archive or clone the repository with git. We recommend the `git` approach since it makes updating the tools extremely simple. ```bash # To download git clone https://github.com/haddocking/pdb-tools cd pdb-tools # To update git pull origin master # To install python setup.py install ``` ## Contributing If you want to contribute to the development of `pdb-tools`, provide a bug fix, or a new tools, read our `CONTRIBUTING` instructions [here](https://github.com/haddocking/pdb-tools/blob/master/CONTRIBUTING.md). ## License `pdb-tools` are open-source and licensed under the Apache License, version 2.0. For details, see the LICENSE file. pdb-tools-2.7.0/citation.tex000066400000000000000000000017241521210715700157640ustar00rootroot00000000000000@article {Rodrigues483305, author = {Rodrigues, Jo{\~a}o P.G.L.M. and Teixeira, Jo{\~a}o M.C. and Trellet, Mika{\"e}l and Bonvin, Alexandre M.J.J.}, title = {pdb-tools: a swiss army knife for molecular structures}, elocation-id = {483305}, year = {2018}, doi = {10.1101/483305}, publisher = {Cold Spring Harbor Laboratory}, abstract = {The pdb-tools are a collection of Python scripts for working with molecular structure data in the PDB format. They allow users to edit, convert, and validate PDB files, from the command-line, in a simple but efficient manner. The pdb-tools are implemented in Python, without any external dependencies, and are freely available under the open-source Apache License at https://github.com/haddocking/pdb-tools/ and on PyPI (https://pypi.org/project/pdb-tools/).}, URL = {https://www.biorxiv.org/content/early/2018/12/04/483305}, eprint = {https://www.biorxiv.org/content/early/2018/12/04/483305.full.pdf}, journal = {bioRxiv} }pdb-tools-2.7.0/docs/000077500000000000000000000000001521210715700143545ustar00rootroot00000000000000pdb-tools-2.7.0/docs/_config.yml000066400000000000000000000005021521210715700165000ustar00rootroot00000000000000title: 'pdb-tools' headline: '' logo: /logo/pdb-tools.png show_downloads: true description: 'A swiss army knife for editing PDB files.' theme: jekyll-theme-minimal github: zip_url: https://github.com/haddocking/pdb-tools/archive/2.0.0-rc1.zip tar_url: https://github.com/haddocking/pdb-tools/archive/2.0.0-rc1.tar.gz pdb-tools-2.7.0/docs/assets/000077500000000000000000000000001521210715700156565ustar00rootroot00000000000000pdb-tools-2.7.0/docs/assets/css/000077500000000000000000000000001521210715700164465ustar00rootroot00000000000000pdb-tools-2.7.0/docs/assets/css/style.scss000066400000000000000000000004711521210715700205050ustar00rootroot00000000000000--- --- @import "{{ site.theme }}"; /* Pad image bottom */ .wrapper img { padding-bottom: 1%; } /* Remove bullets from ordered lists */ ul { list-style-type: none; padding: 0; margin: 0; } /* Make content wider */ .wrapper { width: 1200px; } section { width: 860px; } footer { width: 280px; } pdb-tools-2.7.0/docs/cookbook.md000066400000000000000000000004631521210715700165070ustar00rootroot00000000000000--- layout: default --- * Removing hydrogens, renaming `HIP` to `HIS`, and renumbering atoms, for all PDBs from a folder to a new folder: ```bash mkdir folder_new for i in folder/*pdb; do pdb_delelem -H $i | pdb_rplresname -HIP:HIS | pdb_reatom -1 | pdb_tidy > folder_new/$(basename $i); done ``` pdb-tools-2.7.0/docs/doctools.py000066400000000000000000000035201521210715700165540ustar00rootroot00000000000000#!/usr/bin/env python """ Scrapes tool headers for documentation. """ import importlib from pathlib import Path with open('index.md', 'w') as handle: with open('index.md.template') as template: print(template.read(), file=handle) import pdbtools modfile = Path(pdbtools.__file__) for f in sorted(list(modfile.parent.iterdir())): # ignore __init__.py and others. if f.stem.startswith('_') or f.suffix != '.py': continue # Dynamically import tool to get __doc__ name = f.stem try: tool = importlib.import_module(f'pdbtools.{name}') except ModuleNotFoundError: print(f'Could not import module: {name}') continue # Parse documentation from docstrings # Preserve white-space as best as possible. # First non-empty line is always short description. # Last lines are always licensing disclaimer summary = None long_description = [] doctext = tool.__doc__.replace('<', '<').replace('>', '>') for line in doctext.split('\n'): if summary is None and not line.strip(): continue if line.startswith('This program is part of the'): break elif summary is None: summary = line else: long_description.append(line) long_description = '\n'.join(long_description) print('
', file=handle) print('
', file=handle) print(f"{name}

{summary}

", file=handle) print( f'{long_description}', file=handle ) print('
', file=handle) print('
', file=handle) pdb-tools-2.7.0/docs/index.md000066400000000000000000000721301521210715700160100ustar00rootroot00000000000000--- layout: default --- A swiss army knife for manipulating and editing PDB files. ## Installation Instructions `pdb-tools` are available on PyPi and can be installed though `pip`. This is the recommended way as it makes updating/uninstalling rather simple: ```bash pip install pdb-tools ``` Because we use semantic versioning in the development of `pdb-tools`, every bugfix or new feature results in a new version of the software that is automatically published on PyPI. As such, there is no difference between the code on github and the latest version you can install with `pip`. To update your installation to the latest version of the code run: ```bash pip install --upgrade pdb-tools ``` ## What can I do with them? The purpose of each tool should be obvious from its name. In any case, [here](#list-of-tools) is a list of all the tools in the suite and their function. All tools share the same command-line interface. Below are a couple of examples to get you started. If you want to check out more examples of how to use the tools and their applications, or have any cool examples of your own, check out the [cookbook](cookbook). * Downloading a structure ```bash pdb_fetch 1brs > 1brs.pdb # 6 chains pdb_fetch -biounit 1brs > 1brs.pdb # 2 chains ``` * Renumbering a structure ```bash pdb_reres -1 1ctf.pdb > 1ctf_renumbered.pdb ``` * Selecting chain(s) ```bash pdb_selchain -A 1brs.pdb > 1brs_A.pdb pdb_selchain -A,D 1brs.pdb > 1brs_AD.pdb ``` * Deleting hydrogens ```bash pdb_delelem -H 1brs.pdb > 1brs_noH.pdb ``` * Selecting backbone atoms ```bash pdb_selatom -CA,C,N,O 1brs.pdb > 1brs_bb.pdb ``` * Selecting chains, removing HETATM, and producing a valid PDB file ```bash pdb_selchain -A,D 1brs.pdb | pdb_delhetatm | pdb_tidy > 1brs_AD_noHET.pdb ``` *Note: On Windows the tools will have the `.exe` extension.* ## What _can't_ I do with them? Operations that involve coordinates or numerical calculations are usually not in the scope of `pdb-tools`. Use a proper library for that, it will be much faster and scalable. Also, although we provide mmCIF<->PDB converters, we do not support large mmCIF files with more than 99999 atoms, or 9999 residues in a single chain. Our tools will complain if you try using them on such a molecule. ## About Manipulating PDB files is often painful. Extracting a particular chain or set of residues, renumbering residues, splitting or merging models and chains, or just ensuring the file is conforming to the PDB specifications are examples of tasks that can be done using any decent parsing library or graphical interface. These, however, almost always require 1) scripting knowledge, 2) time, and 3) installing one or more programs. `pdb-tools` were designed to be a swiss army knife for the PDB format. The philosophy of the scripts is simple: one script, one task. If you want to do two things, pipe the scripts together. Requests for new scripts will be taken into consideration - use the Issues button or write them yourself and create a Pull Request. ## Looking for the _other_ pdb-tools? The Harms lab maintains a set of tools also called `pdbtools`, which perform a slightly different set of functions. You can find them [here](https://github.com/harmslab/pdbtools). ## Citation We finally decided to write up a small publication describing the tools. If you used them in a project that is going to be published, please cite us: ``` Rodrigues JPGLM, Teixeira JMC, Trellet M and Bonvin AMJJ. pdb-tools: a swiss army knife for molecular structures. F1000Research 2018, 7:1961 (https://doi.org/10.12688/f1000research.17456.1) ``` If you use a reference manager that supports BibTex, use this record: ``` @Article{ 10.12688/f1000research.17456.1, AUTHOR = { Rodrigues, JPGLM and Teixeira, JMC and Trellet, M and Bonvin, AMJJ}, TITLE = {pdb-tools: a swiss army knife for molecular structures [version 1; peer review: 2 approved] }, JOURNAL = {F1000Research}, VOLUME = {7}, YEAR = {2018}, NUMBER = {1961}, DOI = {10.12688/f1000research.17456.1} } ``` ## Requirements `pdb-tools` should run on Python 2.7+ and Python 3.x. We test on Python 2.7, 3.6, and 3.7. There are no dependencies. ## Installing from Source Download the zip archive or clone the repository with git. We recommend the `git` approach since it makes updating the tools extremely simple. ```bash # To download git clone https://github.com/haddocking/pdb-tools cd pdb-tools # To update git pull origin master # To install python setup.py install ``` ## Contributing If you want to contribute to the development of `pdb-tools`, provide a bug fix, or a new tools, read our `CONTRIBUTING` instructions [here](https://github.com/haddocking/pdb-tools/blob/master/CONTRIBUTING.md). ## License `pdb-tools` are open-source and licensed under the Apache License, version 2.0. For details, see the LICENSE file. ## List of Tools
pdb_b

Modifies the temperature factor column of a PDB file (default 10.0).

 Usage: python pdb_b.py -<bfactor> <pdb file> Example: python pdb_b.py -10.0 1CTF.pdb
pdb_chain

Modifies the chain identifier column of a PDB file (default is an empty chain).

 Usage: python pdb_chain.py -<chain id> <pdb file> Example: python pdb_chain.py -C 1CTF.pdb
pdb_chainbows

Renames chain identifiers sequentially, based on TER records.

 Since HETATM records are not separated by TER records and usually come together at the end of the PDB file, this script will attempt to reassign their chain identifiers based on the changes it made to ATOM lines. This might lead to bad output in certain corner cases. Usage: python pdb_chainbows.py <pdb file> Example: python pdb_chainbows.py 1CTF.pdb
pdb_chainxseg

Swaps the segment identifier for the chain identifier.

 Usage: python pdb_chainxseg.py <pdb file> Example: python pdb_chainxseg.py 1CTF.pdb
pdb_chkensemble

Checks all models in a multi-model PDB file have the same composition.

 Composition is defined as same atoms/residues/chains. Usage: python pdb_chkensemble.py <pdb file> Example: python pdb_chkensemble.py 1CTF.pdb
pdb_delchain

Deletes all atoms matching specific chains in the PDB file.

 Usage: python pdb_delchain.py -<option> <pdb file> Example: python pdb_delchain.py -A 1CTF.pdb # removes chain A from PDB file python pdb_delchain.py -A,B 1CTF.pdb # removes chains A and B from PDB file
pdb_delelem

Deletes all atoms matching the given element in the PDB file.

 Elements are read from the element column. Usage: python pdb_delelem.py -<option> <pdb file> Example: python pdb_delelem.py -H 1CTF.pdb # deletes all protons python pdb_delelem.py -N 1CTF.pdb # deletes all nitrogens python pdb_delelem.py -H,N 1CTF.pdb # deletes all protons and nitrogens
pdb_delhetatm

Removes all HETATM records in the PDB file.

 Usage: python pdb_delhetatm.py <pdb file> Example: python pdb_delhetatm.py 1CTF.pdb
pdb_delinsertion

Deletes insertion codes in a PDB file.

 Deleting an insertion code shifts the residue numbering of downstream residues. Allows for picking specific residues to delete insertion codes for. Usage: python pdb_delinsertion.py [-<option>] <pdb file> Example: python pdb_delinsertion.py 1CTF.pdb # delete ALL insertion codes python pdb_delinsertion.py -A9,B12 1CTF.pdb # deletes ins. codes for res # 9 of chain A and 12 of chain B.
pdb_delres

Deletes a range of residues from a PDB file.

 The range option has three components: start, end, and step. Start and end are optional and if ommitted the range will start at the first residue or end at the last, respectively. The step option can only be used if both start and end are provided. Note that the start and end values of the range are purely numerical, while the range actually refers to every N-th residue, regardless of their sequence number. Usage: python pdb_delres.py -[resid]:[resid]:[step] <pdb file> Example: python pdb_delres.py -1:10 1CTF.pdb # Deletes residues 1 to 10 python pdb_delres.py -1: 1CTF.pdb # Deletes residues 1 to END python pdb_delres.py -:5 1CTF.pdb # Deletes residues from START to 5. python pdb_delres.py -::5 1CTF.pdb # Deletes every 5th residue python pdb_delres.py -1:10:5 1CTF.pdb # Deletes every 5th residue from 1 to 10
pdb_delresname

Removes all residues matching the given name in the PDB file.

 Residues names are matched *without* taking into consideration spaces. Usage: python pdb_delresname.py -<option> <pdb file> Example: python pdb_delresname.py -ALA 1CTF.pdb # removes only Alanines python pdb_delresname.py -ASP,GLU 1CTF.pdb # removes (-) charged residues
pdb_element

Assigns the elements in the PDB file from atom names.

 Usage: python pdb_element.py <pdb file> Example: python pdb_element.py 1CTF.pdb
pdb_fetch

Downloads a structure in PDB format from the RCSB website.

 Allows downloading the (first) biological structure if selected. Usage: python pdb_fetch.py [-biounit] <pdb code> Example: python pdb_fetch.py 1brs # downloads unit cell, all 6 chains python pdb_fetch.py -biounit 1brs # downloads biounit, 2 chains
pdb_fixinsert

Fixes insertion codes in a PDB file.

 Works by deleting an insertion code and shifting the residue numbering of downstream residues. Allows for picking specific residues to delete insertion codes for. Usage: python pdb_fixinsert.py [-<option>] <pdb file> Example: python pdb_fixinsert.py 1CTF.pdb # delete ALL insertion codes python pdb_fixinsert.py -A9,B12 1CTF.pdb # deletes ins. codes for res # 9 of chain A and 12 of chain B.
pdb_fromcif

Rudimentarily converts a mmCIF file to the PDB format.

 Will not convert if the file does not 'fit' in PDB format, e.g. too many chains, residues, or atoms. Will convert only the coordinate section. Usage: python pdb_fromcif.py <pdb file> Options: -h36: allows for hybrid36 output format for encoding >99999 atoms in the PDB file Example: python pdb_fromcif.py 1CTF.pdb
pdb_gap

Finds gaps between consecutive protein residues in the PDB.

 Detects gaps both by a distance criterion or discontinuous residue numbering. Only applies to protein residues. Usage: python pdb_gap.py <pdb file> Example: python pdb_gap.py 1CTF.pdb
pdb_head

Returns the first N coordinate (ATOM/HETATM) lines of the file.

 Usage: python pdb_head.py -<num> <pdb file> Example: python pdb_head.py -100 1CTF.pdb # first 100 ATOM/HETATM lines of the file
pdb_intersect

Returns a new PDB file only with atoms in common to all input PDB files.

 Atoms are judged equal is their name, altloc, res. name, res. num, insertion code and chain fields are the same. Coordinates are taken from the first input file. Keeps matching TER/ANISOU records. Usage: python pdb_intersect.py <pdb file> <pdb file> Example: python pdb_intersect.py 1XYZ.pdb 1ABC.pdb
pdb_keepcoord

Removes all non-coordinate records from the file.

 Keeps only MODEL, ENDMDL, END, ATOM, HETATM, CONECT. Usage: python pdb_keepcoord.py <pdb file> Example: python pdb_keepcoord.py 1CTF.pdb
pdb_merge

Merges several PDB files into one.

 The contents are not sorted and no lines are deleted (e.g. END, TER statements) so we recommend piping the results through `pdb_tidy.py`. Usage: python pdb_merge.py <pdb file> <pdb file> Example: python pdb_merge.py 1ABC.pdb 1XYZ.pdb
pdb_mkensemble

Merges several PDB files into one multi-model (ensemble) file.

 Strips all HEADER information and adds REMARK statements with the provenance of each conformer. Usage: python pdb_mkensemble.py <pdb file> <pdb file> Example: python pdb_mkensemble.py 1ABC.pdb 1XYZ.pdb
pdb_occ

Modifies the occupancy column of a PDB file (default 1.0).

 Usage: python pdb_occ.py -<occupancy> <pdb file> Example: python pdb_occ.py -1.0 1CTF.pdb
pdb_reatom

Renumbers atom serials in the PDB file starting from a given value (default 1).

 Usage: python pdb_reatom.py -<number> <pdb file> Options: -h36: allows for hybrid36 output format for encoding >99999 atoms in the PDB file Example: python pdb_reatom.py -10 1CTF.pdb # renumbers from 10 python pdb_reatom.py --1 1CTF.pdb # renumbers from -1
pdb_reres

Renumbers the residues of the PDB file starting from a given number (default 1).

 Usage: python pdb_reres.py -<number> <pdb file> Example: python pdb_reres.py -10 1CTF.pdb # renumbers from 10 python pdb_reres.py --1 1CTF.pdb # renumbers from -1
pdb_rplchain

Performs in-place replacement of a chain identifier by another.

 Usage: python pdb_rplchain.py -<from>:<to> <pdb file> Example: python pdb_rplchain.py -A:B 1CTF.pdb # Replaces chain A for chain B
pdb_rplresname

Performs in-place replacement of a residue name by another.

 Affects all residues with that name. Usage: python pdb_rplresname.py -<from>:<to> <pdb file> Example: python pdb_rplresname.py -HIP:HIS 1CTF.pdb # changes all HIP residues to HIS
pdb_seg

Modifies the segment identifier column of a PDB file (default is an empty segment).

 Usage: python pdb_seg.py -<segment id> <pdb file> Example: python pdb_seg.py -C 1CTF.pdb
pdb_segxchain

Swaps the chain identifier by the segment identifier.

 If the segment identifier is longer than one character, the script will truncate it. Does not ensure unique chain IDs. Usage: python pdb_segxchain.py <pdb file> Example: python pdb_segxchain.py 1CTF.pdb
pdb_selaltloc

Selects altloc labels for the entire PDB file.

 By default, selects the label with the highest occupancy value for each atom, but the user can define a specific altloc label to select. Selecting by highest occupancy removes all altloc labels for all atoms. If the user provides an option (e.g. -A), only atoms with conformers with an altloc A are processed by the script. If you select -A and an atom has conformers with altlocs B and C, both B and C will be kept in the output. Usage: python pdb_selaltloc.py [-<option>] <pdb file> Example: python pdb_selaltloc.py 1CTF.pdb # picks locations with highest occupancy python pdb_selaltloc.py -A 1CTF.pdb # picks alternate locations labelled 'A'
pdb_selatom

Selects all atoms matching the given name in the PDB file.

 Atom names are matched *without* taking into consideration spaces, so ' CA ' (alpha carbon) and 'CA ' (calcium) will both be kept if -CA is passed. Usage: python pdb_selatom.py -<option> <pdb file> Example: python pdb_selatom.py -CA 1CTF.pdb # keeps only alpha-carbon atoms python pdb_selatom.py -CA,C,N,O 1CTF.pdb # keeps only backbone atoms
pdb_selchain

Extracts one or more chains from a PDB file.

 Usage: python pdb_selchain.py -<chain id> <pdb file> Example: python pdb_selchain.py -C 1CTF.pdb # selects chain C python pdb_selchain.py -A,C 1CTF.pdb # selects chains A and C
pdb_selelem

Selects all atoms that match the given element(s) in the PDB file.

 Elements are read from the element column. Usage: python pdb_selelem.py -<option> <pdb file> Example: python pdb_selelem.py -H 1CTF.pdb # selects all protons python pdb_selelem.py -N 1CTF.pdb # selects all nitrogens python pdb_selelem.py -H,N 1CTF.pdb # selects all protons and nitrogens
pdb_selhetatm

Selects all HETATM records in the PDB file.

 Usage: python pdb_selhetatm.py <pdb file> Example: python pdb_selhetatm.py 1CTF.pdb
pdb_selmodel

Extracts one or more models from a PDB file.

 If the PDB file has no MODEL records, returns the entire file. Usage: python pdb_selmodel.py -<model id> <pdb file> Example: python pdb_selmodel.py -1 1GGR.pdb # selects model 1 python pdb_selmodel.py -1,3 1GGR.pdb # selects models 1 and 3
pdb_selres

Selects residues by their index, piecewise or in a range.

 The range option has three components: start, end, and step. Start and end are optional and if ommitted the range will start at the first residue or end at the last, respectively. Usage: python pdb_selres.py -[resid]:[resid]:[step] <pdb file> Example: python pdb_selres.py -1,2,4,6 1CTF.pdb # Extracts residues 1, 2, 4 and 6 python pdb_selres.py -1:10 1CTF.pdb # Extracts residues 1 to 10 python pdb_selres.py -1:10,20:30 1CTF.pdb # Extracts residues 1 to 10 and 20 to 30 python pdb_selres.py -1: 1CTF.pdb # Extracts residues 1 to END python pdb_selres.py -:5 1CTF.pdb # Extracts residues from START to 5. python pdb_selres.py -::5 1CTF.pdb # Extracts every 5th residue python pdb_selres.py -1:10:5 1CTF.pdb # Extracts every 5th residue from 1 to 10
pdb_selresname

Selects all residues matching the given name in the PDB file.

 Residues names are matched *without* taking into consideration spaces. Usage: python pdb_selresname.py -<option> <pdb file> Example: python pdb_selresname.py -ALA 1CTF.pdb # keeps only Alanines python pdb_selresname.py -ASP,GLU 1CTF.pdb # keeps (-) charged residues
pdb_selseg

Selects all atoms matching the given segment identifier.

 Usage: python pdb_selseg.py -<segment id> <pdb file> Example: python pdb_selseg.py -C 1CTF.pdb # selects segment C python pdb_selseg.py -C,D 1CTF.pdb # selects segments C and D
pdb_shiftres

Shifts the residue numbers in the PDB file by a constant value.

 Usage: python pdb_shiftres.py -<number> <pdb file> Example: python pdb_shiftres.py -10 1CTF.pdb # adds 10 to the original numbering python pdb_shiftres.py --5 1CTF.pdb # subtracts 5 from the original numbering
pdb_sort

Sorts the ATOM/HETATM/ANISOU/CONECT records in a PDB file.

 Atoms are always sorted by their serial number, meaning the original ordering of the atoms within each residue are not changed. Alternate locations are sorted by default. Residues are sorted according to their residue sequence number and then by their insertion code (if any). Chains are sorted by their chain identifier. Finally, the file is sorted by all keys, and the records are placed in the following order: - ATOM/ANISOU, intercalated if the latter exist - HETATM - CONECT, sorted by the serial number of the central (first) atom MASTER, TER, END statements are removed. Headers (HEADER, REMARK, etc) are kept and placed first. Does NOT support multi-model files. Use pdb_splitmodel, then pdb_sort on each model, and then pdb_mkensemble. Usage: python pdb_sort.py -<option> <pdb file> Example: python pdb_sort.py 1CTF.pdb # sorts by chain and residues python pdb_sort.py -C 1CTF.pdb # sorts by chain (A, B, C ...) only python pdb_sort.py -R 1CTF.pdb # sorts by residue number/icode only
pdb_splitchain

Splits a PDB file into several, each containing one chain.

 Usage: python pdb_splitchain.py <pdb file> Example: python pdb_splitchain.py 1CTF.pdb
pdb_splitmodel

Splits a PDB file into several, each containing one MODEL.

 Usage: python pdb_splitmodel.py <pdb file> Example: python pdb_splitmodel.py 1CTF.pdb
pdb_splitseg

Splits a PDB file into several, each containing one segment.

 Usage: python pdb_splitseg.py <pdb file> Example: python pdb_splitseg.py 1CTF.pdb
pdb_tidy

Modifies the file to adhere (as much as possible) to the format specifications.

 Expects a sorted file - REMARK/ATOM/HETATM/END - so use pdb_sort in case you are not sure. This includes: - Adding TER statements after chain breaks/changes - Truncating/Padding all lines to 80 characters - Adds END statement at the end of the file Will remove all original TER/END statements from the file. Usage: python pdb_tidy.py [-strict] [-h36] <pdb file> Options: -h36: allows for hybrid36 output format for encoding >99999 atoms in the PDB file Example: python pdb_tidy.py 1CTF.pdb python pdb_tidy.py -strict 1CTF.pdb # does not add TER on chain breaks python pdb_tidy.py -h36 1CTF.pdb # allows for a number of atom >99999 by using hybrid_36 format
pdb_tocif

Rudimentarily converts the PDB file to mmCIF format.

 Will convert only the coordinate section. Usage: python pdb_tocif.py <pdb file> Example: python pdb_tocif.py 1CTF.pdb
pdb_tofasta

Extracts the residue sequence in a PDB file to FASTA format.

 Canonical amino acids and nucleotides are represented by their one-letter code while all others are represented by 'X'. The -multi option splits the different chains into different records in the FASTA file. Usage: python pdb_tofasta.py [-multi] <pdb file> Example: python pdb_tofasta.py 1CTF.pdb
pdb_uniqname

Renames atoms sequentially (C1, C2, O1, ...) for each HETATM residue.

 Relies on an element column being present (see pdb_element). Usage: python pdb_uniqname.py <pdb file> Example: python pdb_uniqname.py 1CTF.pdb
pdb_validate

Validates the PDB file ATOM/HETATM lines according to the format specifications.

 Does not catch all the errors though... people are creative! Usage: python pdb_validate.py <pdb file> Example: python pdb_validate.py 1CTF.pdb
pdb_wc

Summarizes the contents of a PDB file, like the wc command in UNIX.

 By default, this tool produces a general summary, but you can use several options to produce focused but more detailed summaries: [m] - no. of models. [c] - no. of chains (plus per-model if multi-model file). [r] - no. of residues (plus per-model if multi-model file). [a] - no. of atoms (plus per-model if multi-model file). [h] - no. of HETATM (plus per-model if multi-model file). [o] - presence of disordered atoms (altloc). [i] - presence of insertion codes. Usage: python pdb_wc.py [-<option>] <pdb file> Example: python pdb_wc.py 1CTF.pdb
pdb-tools-2.7.0/docs/index.md.template000066400000000000000000000115001521210715700176140ustar00rootroot00000000000000--- layout: default --- A swiss army knife for manipulating and editing PDB files. ## Installation Instructions `pdb-tools` are available on PyPi and can be installed though `pip`. This is the recommended way as it makes updating/uninstalling rather simple: ```bash pip install pdb-tools ``` Because we use semantic versioning in the development of `pdb-tools`, every bugfix or new feature results in a new version of the software that is automatically published on PyPI. As such, there is no difference between the code on github and the latest version you can install with `pip`. To update your installation to the latest version of the code run: ```bash pip install --upgrade pdb-tools ``` ## What can I do with them? The purpose of each tool should be obvious from its name. In any case, [here](#list-of-tools) is a list of all the tools in the suite and their function. All tools share the same command-line interface. Below are a couple of examples to get you started. If you want to check out more examples of how to use the tools and their applications, or have any cool examples of your own, check out the [cookbook](cookbook). * Downloading a structure ```bash pdb_fetch 1brs > 1brs.pdb # 6 chains pdb_fetch -biounit 1brs > 1brs.pdb # 2 chains ``` * Renumbering a structure ```bash pdb_reres -1 1ctf.pdb > 1ctf_renumbered.pdb ``` * Selecting chain(s) ```bash pdb_selchain -A 1brs.pdb > 1brs_A.pdb pdb_selchain -A,D 1brs.pdb > 1brs_AD.pdb ``` * Deleting hydrogens ```bash pdb_delelem -H 1brs.pdb > 1brs_noH.pdb ``` * Selecting backbone atoms ```bash pdb_selatom -CA,C,N,O 1brs.pdb > 1brs_bb.pdb ``` * Selecting chains, removing HETATM, and producing a valid PDB file ```bash pdb_selchain -A,D 1brs.pdb | pdb_delhetatm | pdb_tidy > 1brs_AD_noHET.pdb ``` *Note: On Windows the tools will have the `.exe` extension.* ## What _can't_ I do with them? Operations that involve coordinates or numerical calculations are usually not in the scope of `pdb-tools`. Use a proper library for that, it will be much faster and scalable. Also, although we provide mmCIF<->PDB converters, we do not support large mmCIF files with more than 99999 atoms, or 9999 residues in a single chain. Our tools will complain if you try using them on such a molecule. ## About Manipulating PDB files is often painful. Extracting a particular chain or set of residues, renumbering residues, splitting or merging models and chains, or just ensuring the file is conforming to the PDB specifications are examples of tasks that can be done using any decent parsing library or graphical interface. These, however, almost always require 1) scripting knowledge, 2) time, and 3) installing one or more programs. `pdb-tools` were designed to be a swiss army knife for the PDB format. The philosophy of the scripts is simple: one script, one task. If you want to do two things, pipe the scripts together. Requests for new scripts will be taken into consideration - use the Issues button or write them yourself and create a Pull Request. ## Looking for the _other_ pdb-tools? The Harms lab maintains a set of tools also called `pdbtools`, which perform a slightly different set of functions. You can find them [here](https://github.com/harmslab/pdbtools). ## Citation We finally decided to write up a small publication describing the tools. If you used them in a project that is going to be published, please cite us: ``` Rodrigues JPGLM, Teixeira JMC, Trellet M and Bonvin AMJJ. pdb-tools: a swiss army knife for molecular structures. F1000Research 2018, 7:1961 (https://doi.org/10.12688/f1000research.17456.1) ``` If you use a reference manager that supports BibTex, use this record: ``` @Article{ 10.12688/f1000research.17456.1, AUTHOR = { Rodrigues, JPGLM and Teixeira, JMC and Trellet, M and Bonvin, AMJJ}, TITLE = {pdb-tools: a swiss army knife for molecular structures [version 1; peer review: 2 approved] }, JOURNAL = {F1000Research}, VOLUME = {7}, YEAR = {2018}, NUMBER = {1961}, DOI = {10.12688/f1000research.17456.1} } ``` ## Requirements `pdb-tools` should run on Python 2.7+ and Python 3.x. We test on Python 2.7, 3.6, and 3.7. There are no dependencies. ## Installing from Source Download the zip archive or clone the repository with git. We recommend the `git` approach since it makes updating the tools extremely simple. ```bash # To download git clone https://github.com/haddocking/pdb-tools cd pdb-tools # To update git pull origin master # To install python setup.py install ``` ## Contributing If you want to contribute to the development of `pdb-tools`, provide a bug fix, or a new tools, read our `CONTRIBUTING` instructions [here](https://github.com/haddocking/pdb-tools/blob/master/CONTRIBUTING.md). ## License `pdb-tools` are open-source and licensed under the Apache License, version 2.0. For details, see the LICENSE file. ## List of Tools pdb-tools-2.7.0/docs/logo/000077500000000000000000000000001521210715700153145ustar00rootroot00000000000000pdb-tools-2.7.0/docs/logo/pdb-tools.png000066400000000000000000002673311521210715700177410ustar00rootroot00000000000000PNG  IHDR< pHYs.#.#x?v IDATx ձ Seay>AAcJA74PWB|*q%QP$FAD6% BWsO{}߅[]N*IQ ExBEQ&' ILo(R.'$E4g$4g[r׆H4i@pLÙG p(#zN! Mٽǚ^Tm4A ;wv|/.Kz^ IR/xWqI뗥lAzB S|8j8^+8 5L65q.>I0 4 6^CƅIۋ|H)  vT^ݸi?Ѩm$ IJٙ5gI"0E?zCeeX|"{u4^]ϏAadbA{{ͺC0~sHc@&SHFa$Ia5w֫@[֩Y׉Vi>?gG\Gee7̙w_%uBB=AII|TJGg,IR~]sD?180)"=$! JU6u;vP'$6AI;f +kƛC }m`S;-[馼+H5[N5xVxw~B _P?}H׸[ \FN>v(ph{ti/f^ p$A6Y.X h=ZC߲We4Xhې&ď J -[>)  !Ə( z!rfut}$LeEnX z: dg(EaԼ[)E3ڝhAmҒ>*Do]x;h`?zj%0%hH#+N}m0A@S5o~7.mV`ageGm ,EQܶTLN`w&/i%=:7h 7 XC §N Jӎ!d2U"ӆ  -vEn#R^Sr(j:]0* iASl?,?+I@.^3)Ⱦ exv6|Dp3miIm} a4!|a;s:n  GL3^DBhמ3 %#EG(N" ?&lzsk;)'e9kWΊpr)KxG ߚc06.@{$JN92=`J|sT_r1j9*|͆gmc7!b8/KQzq+=Oۇ@;yC;%3)EKD Z. R F`|u1ɽNqroF5=t8M૿}b*y+_~}.a;S+a8(QPk7-[b#9!ڬ*Vڶ$Y~; '| +LVz&sBh,f2cr9vp [4aWo-?q3׈zW-":ܴzK"+}>ݺg/i-wdxvQskzgư؄N5;n3‹* ;޶V[)UhRPU d,CnO e.Lմ ۙm< \_~zjuF-dRN]h#I~ KA}s^:P^lP#\Zɞmm-j^wqz83lŲL(8(34 6uN`vQ;|8֛YY^{>($壦]h$|μa A;n&6ŅM[ହBtBap/1DשHӉraöA>|SӊfǂiBXYc?6r0f";66ѹànPb3ihdEߖ/<_![ɮ (;S!͊ެVt~EhDD!tF{z?MTHLU/VbԿqZs.РxLbCp eDQ{!N LO/ [uJ Ç75k Y ŒaVwH 2|h,2/>b_߲F0y񎛙:c)F an}rO3n00= /-[j؂g `˯]0IG ULI08~ \jX'ܭkޮ6'e ױP V #ӫf<- yM`H'S0e/m@7CtCbPp9ض*_S#_ƽ_3plh YhX:~isg=]w8жH :(Pv \j?X+.նκWy׋><Sd9XTW1 ku@aۅ;xI«+W>H]`a5! .~%K' 4;e?^qͰvlA*0фD6c0I_pTBa%p>Irራ$zlf6KY̶M|u}4s([ ͓']KgLH F 4jx*{~A x@,`"p׿cǎ5ܯaڵC]w8H@# ֢)L;$pWἃ4NIw \p! -wh \|M! 14I \tx@Dӝ7x,n4wU Y&rYUhD"YWFlسkǭٰФeB81VCfrveX&wYu8𔲜DlM J1Y왳K̚ U#$"XԀ:!U#IDp*LZb*I M"wcB)jlK>&dQ$1$pKHp7XĦTB$Iؒ)yZe! *m `Pnk\̸) 63ӧ j z@ ҀDkV¼%$D dڇ4 )$U{30@ hd! M*#|~ē۴ikSg>zGˇ?Ҁ!K}`.;VZ%3(K~(#ZHu)o Ҁ!f$@H8F}IH1̅|'܏GG˳1Rk>=Hn12̺P{)]EuѣGrHy^zhƍ%4!Fe^]֭JU&<+VJ~j_UhAq@="1mpjP4]P&E=$ t P $Mg?n`8WfEwB׹Mv&(Ɏ ̈:^WG\/(tFx\1 [WwJKKLQЀ.ׁzn4ZP`^T@NNݏ5[0]WQQ(i ޸?0S[`_🅣ekGfEs$٩ '$r2[i>m{ꘘ3ȿEONtu??:m3LK9:U(q*S!I/,y)?@ȿ p;A ;&+BQLr3{o:j7$/S<6\Jڵ/!c[_e={`<+?ۓZPSktݭBhm`zz(NE' !{h$p~YL$aM+X(Ji ,fl F+|waυbrg,N_sEC:9ZfO%0]Qyvi 8**IB 9m T&T2Цżq-zвڽZ,z[H'M08#ؒ"Vv]&S5G RYM1sp;u TնNbQRqQ\Z|7'VTө0 t0"ڤFEQ>*|v"B(EQ=G0,4h#@ vp$ uֿOh3HLA inLkǮ# ç@ ī%IiRnh''X%'2hOz^ܑ wn`'=35-'L\vJ(J/5]8ى)fXCD^hZ0հcBkWDݡ`MV?&,~6=Rc7#{Y2Hj;3'lj4: h:S̮\4iP3[no>}ul&p,& 㖂8Z|tmg:YXf/'ާ_ԅo`=OC7Sڜ[d@gf ,cmM"<|FG =0 2j;‡=,ezO;&Rدmh ISi6]6΄P/X'pW3VqΉ|Ʋ윶QM9}Uj=n׼f;HXa79+$m/hY6iK%"e5]Ȧ:jk48!{х`|k#ќ^x ^04a M&'m}>B;O@ g]4E3 fGEǏWd&t=>4C!JlۃŲM6e˖~fFyK:ɍ"x2?K;t#5oG&\ ͖32cMZ (|aG j>+|h'с#G +rr4Cqv$r`CDbS6rh{8f{~pm*d9or=_Ԃ" a/X4)* V~y$Ip<_:uzc̡܂V%w.qۺ FngNEQZ{=`j A0I«+W^O^4^ c[b") dĘ`˫k:AeM*± ic 8 ˅ `Áo YzNaVa&W,&v_Q& \*> ,oF嗇KMO0G\w8H/滻ECXy8ysÍ "04鑟u.Y! ẁa?oФ;$p/-PDB`M3ҦMXL!WpT!J`FԒ4XYxXqI/Dq( (,)?f)?m[W\&F}#b+ڟr1C̝֝/4H64am@é$ xw}>\f2Q L͵JJĕ!S $R$I`׸ZQ^$-zkzOf.wT";{{:/[,+X@71z=V7Jߕ *U il0k#ϐ~ +T_rL7NB[^}֭{QIU~W\ᬒvQb,_xuS,i/RD*;W g رD0@kۏF~oMa̱T%I VMP'DT3xϋgo&tL ?$ !R0OQ%7־]wNwO#iJ2H]jTU2$| f>6;]M˕~t鶚blӦ-l@XYuQ70P~yDbEω3گ]!&!ᖝ &~^~_\?toHSmڵ׭ߴ=.<>K__.0*>3XE v 2 |\^u[0a>dn: =.H * іc5a",O5b|+^}>^ 98fN*0Pv;C=Ct W~a@J ka̘H. t`WJ{}w%IM p$0HQH 40?Ax} IDAT~~`C_||6?JQ&E0 x@Ve0=5bݧ͡gHE$rݏp(-'kUO)8@=Hj]OS$5عk7,kaxقny.;ԯ__N˒U80['ESR~*BAKoEQV+&a817H˹Iv)1@&S5~ݺ=zDqo[_QLkLjyP^Z[,#K&S˯קo?2y8~5teZn>p&SŁuWevv0(#W|s(C$G{Y2_/Ķ%PU?W+ ϵmVط6o6~ᜎGe6~-0C ~_I%j@Xy:XO_NO;6vnԝ@ Vrַ^1ǥD焨4nڶm d HQ"a.obwXE* ~E3*]2JA*0>1bNA"^7?|ED8k0_`A6* a=';8V٧U:~P1ivyCS^F_{}0[O\`ZZuHP-|CX3.aZgyx_ٶfe 051 5[#6\)@~3nݚ<®jG АN-ٗameİ_ir5h>ni>8^]Nh*Id,(;a05ˆ,y˼P[ٰǣimM?-/7?d~yEi&@kKgEUdCD>zd"- ֏ 3q2vn ϙ7wM+X+̵7^ӹȸGd>ZNv|'' M!) 3K L6+ :0Ol\$fqNa2Ѝ;L;|HHHط@Xv̔hLMY [o~As3BaQqJU"tVt~8ເn X@7l7K3NR)@V8O?,q#Ǒ wnM QQ(zMNmJ~;+77Ӫl;jپu0P)Pa!/ϹXQQ[y %NvJ&Z(Iޢc ?pa7!Rx~p}UnsmDH,IUdFVWe:C 1 $%+[KNj0}YnYֿ fnQ#G, a,g%0;?L~Gkm{2zx(ӝ\dv*^]`6/` ; M"%ˠIo렺OOfb-73+0໺q([Ͽ@ /OD=tKLJQk[})AMߢ͛;:ju V)4^-u3*:슖tXi?=)2vޕϊ勦'B`y+|UrH K.o>|Ō.-Ό8ւ<{χ5H3 {폕)62T~,5hv̊˰lj.;f#fʑg)e'HP`ر_xCnBT]ie%hgة 7g9p4 9f>?S͛4IIɴS>qvGW++ྩS]ݙ; Zxi4S=+ ?5]l0Fq>v i5N=T.Q$;e?vr4z W3Kࢵ!5_p;?kE1v>@/Z>"d9ޒKiQ kVL<^]9~2tQKCpnV멚ŤMc2*Sߝȯ'G%17æwݪ1%'@ n C_h i W;ll.$fF\ΊLJ8uؒ#'AՆyV 0wahbb pBV ?V;Nʏp`QS-@ٸˡ-* nge ͦyn0tAtMD8uuCww@Cx.,g]x.r::Yf!T?!YŃ+ͬ wy{ԭESf;t^p?4Ѿ2x~݂֩Q%=!yF(e;] nXڡ,gS8?w]mGQEVywԄq*3WZPr6gnS"a(j ˛G]}B8T"V5MONR=YdP<X jEoj] QkG Ҿ)؊94ᆰ}j-iGŊ(^MJ`ݮ&?x x/O+!"D>KwݤIjE{Fj] 3 \ӟrQsX(@ 8>(˚@k\ nx}hAJ*i$t&ɫIS‘LJWi"nD(i %)M0nGYκ.UHI!JVòӞ&Nη$ԕDŨ '-qeEyM6Dć4I"B6Z"|8~JP$G$#gW%Il~HEʳH L7% ̵UiCe~tB8x 2 Y~D$Ij旔46o-$ 4R~Dȧ7Ά}GGR>K$ "A&iId$]ٯHRY~D"$) BR~Y4.#B^/,D/,?"'l%/GDQBʏ AE )? R~A%(JHcwBkog=AR(ΏH$-Z[EKH!@g pN/%Q ? Dt#Cftf!/}PHa>R~,?"QJ())—D*6jDNHCQ,b4m7*[>t})+^}]0$IZ;BvϏH*$MI|󱢛FvV-Dz+IJM)4vAXE,a]3w36"Ň$g$IsYŷ|k'?Y,dW($%ќy `asFEQD~ R~D$ }t%R:@{`qwql͟s-7ۊ?FVV*+{>#Imcfu%ˏH=Lrl)/7z#nY~A%'4U!qqh)?Ax(# G)m۶Z]EQddzUWL\9k'#3 QZ+="9rZrv[6mf;:vHƯTjLd>4-}zGIF)|H~|lv:S -IR/lbR]L6?JscXaũP T ƍOI+MʏH"UEJ0 P$L14h;ʩ$*ID |A~+>D(J$>93?#m.'4}?C,]X8tP$BjB~3aWu# w{oC)?" P1ss$I؍\s7hf_p3H"Ls 0?xPW}9nݯI.D+6_]eN_PXvJYÒgu,[lᨗ jc5Ưc{=n}ѯfR Og(V'(],Tdmt60"<$I r㘣>ɮ[JsIbo,^rSe4ϖFϽ0K`z<$NE> ~NyVP K1qlaDCawaR~- w*JDx& l \̯Ǭ]]$mx>ׇx^q6t ]6xpti/ۊE>dxILN9LNgCPA`^H姀˶kͭecR|c%aT QT|F$HA]DGGDiK?U;hc+dAi/vRP&DNXֲ dnPu7nF𒇡Dw7sog=Y{![l-\y( 5/A8e؛o ]ta7F˵ݨ^8:f'rxl}|rhJ>ԅv: bʂe03B(pC4C0EYʉ] mZAxDwrP'ߥ9ؾ3m7c-JfJǾxs0}:]ƍPݶiq槍|e^h}¬αxؗ&MykSجnW[QR{m=ό~uoN2S*@~v[S] *@ϣX!Wke~u6Q9"HCˈ̎/p[s۶jYVbt'|m howl%M啲Md9+;x~cvv?xX2Iz$I®b+YY2LYFl !0v[4`S0:-o9UfNePhuQ95 k*eqbI0 PA2>,@[$VpJu,g1SK4/uy$V3-VƑf(A3.;ԯ_`8u0T~Dq@A=mS%hg>q`= *V>n sޞ@N?p33sLUWƫCt>ð']>Z!$@ e6&ҹx֭[ G 8GƂ8/7 )9somzsk wJC N Mt|caQuw%IZʽ}1 dDpB~ 8z- 0{VU|}+^mYqQ}{аמNvx_u˂$u("Zn`jY `E&S12g춑LR˻ykZs$m/('--0`߿M8)@S l}TVf|l6^W8…&/x%KÑ$ dv(Y([`P(dT=-qh.]ndQK#Vի ' ЯVzd"RbXJ)drYjP r^me$ˏ6\0@kM8gm9>zoK24^G}GQݎfw[+C@⫷ByYN>3`7NIeKfWWRc}cp:p֖k>p3?0 ܊7  V't{xbWaNᱬ5QK.vr@0EQA. ͛Cyy)?afjz*%V-wKOw2}bX@*Ŷj~/޽{suQ~SkNiG畍W}We*K|&/\e< +ShxI{:gqAKx+ȶ;|<{yrNqC[8dkxaK<^)Pp"NQDqJҨku;DMFi0*^/ A_R)lx t߫$8ỡIouI#*`TC`c,8h3NdZ^vFNEVئϖm4άep`)?sDq~:Ňŋӎ1xUe>CU|8/1AMY*>xإA2X0Ũ7s!)n-̓1O-??t/,)_Lԇ< y䔝e^;x*4z)9>ؘ5ƎU:R;Yi[)wƶ`OI׋}.zO$Hlɩ,ot!Ζ _Ƙ񜲳kgu.0X ZU"a`q~x{f28ΐ!31O?>^nzz2kR$͆gt Ph3,xE ЪMhh79guO,#[}v S[KW7c#~A>YM,;KŇX.O*~IfM/Z[,BVY<+3`" l&1VWN 0H*Z7o1zZRPݍ#5Qȉ唝tL*C>l-7>7 82psŝ IDATeE6盭Ҳ8#.s-`e JaSvy0JR^; 3jT)' 3ecXÎlسMK*'HIF#|ş1Oŋ(|w(ĎNCPY4 <ֿ ݛ|䂵u G}\{ z.HZK blPPBkA)RLg͸47EqĶ%P0@go&&:1X S(8+e{ȋ.Sb+^o!I5\(eg)$މҪP9i]VXT~=j∪E+>p#GG1aߗ_ҭdB/fZuϽjx0=(L*w߁Ç[<J>1Vgw~,2 5#%D g15oW.mF KΓeHyn}~v AQl'z->S0wPY5;M;$a溰w҅3\ӲxXŇ֖c+,lp0'Ɋ?S|4 r5JRoYvrmo۹k秝36בTz"GwYܪ Ғ.lN::Nd@)g cCR1V?= ϭ-㺷lZb)/7!SӏLU[}Y~Q% Cׯ{iy,;>L]'QXSؙ| 3))>TP\R_BA. *լS($\XI]v.8r‚Ҟ Vn̜{-^ۇx0cGm, t^p?4x;v?}_ WuYtd":?jU2v/&B&Se:5!N>6̯)+2 iq\ EÐ^m;>O'}vhm]DT^5N-r?6~v 靶y kN3h Ahuwoξط@Њɯ;e?6Fd՝өS.h܎z KЪlg[S~3+5-y7;/i青N|؋nv'"JXФIxbv=dl|X `M C0buu &*23 _(t;YNX0S$ ;;,6NIG4Rk%̂|jD |}"hz"~oK~ Q[[ [&:^ kVǡ')YNĆAc Ώ5B*4+ɭafqhpJ ,gsI3*С/]\wNcρhWWqumj^=]z)? )շҞ$ e3|uq%5_Qns3lz}GhQ_s;F/-a vhVQW~8gdyOC UW>t=;G͕%g3"ᓽ{a+]_Km[>U^c adQ|Q(>PPMJǥY8AY:SS?@Y¡LD٢EqwA:*;uqR||FDU ; n޼95݆wcV& I't`X0fn`|r;7t>1ısY_SOmN/$|%pֽΊb9= \ &TrV)QV~^L0 [a KS[ xpTgtkjƤSՕ+ܜV&s~oCoaX% GkqqYvM37r@C$Է0>&TjXR| ѷz{gh378 {yN9! P~=:w"ôD=/^+w;XNA!j=8pK(oa^ '78eAOHIdp^k+S r$Nd2U( AB Ipt6 d7EQ(CA!dAIpb@( 3D90AD<$i$I Cf/IM%BADH41&mɸk,_ r] R AD$IXΙh’`E!C  A!b۷?XJdMPScYn@H(dA$I8Cwٙjk려$vټC8c)B"AG0j"I{FGK@uv3A1? ,:qI#_\ftUim% \~iֵ&ÿEYnk<A!4f>6;շnKAsy]S}+gg-!dAAdAǟM->H4 '$IZ%L[~? SE?dA$IFtbK "а/AO(H]lKgbCHdAK#V\/,y)Uz# lCþA>#I\ZtԝvC˲hbQ EA؅<A>(HDGmղ,n53G<A!I=3Mb@5F @? PgNf{ΐJ, 2" "$I2UW\GYO؛o4݆RD "$$IBVx%GҦMۜwu[t"IR/S?G2fYŒ ;%v7ټ/Y@q.? :TZavf-.̝/}`ú4a# Ix PC!~ڱ$I"/MG$IZ S"`F ӌzӿ$G3X7"lUY:ph@gr/ fRe)=Bhؗ "f(J^`Bl׮=TVĝ ?$I* qoAc\% ADd<+rYRwx/F/ J AA#I*\J.KN@OWy N&S5xe9va {(A$YN `B%.z# "$*z! "LzLyG? =͐Gd9G"fʉF&f]@~GAh.Kv /p[U2~q9=BŭAAkpwεС/ȑuzCͥ)/g_=Y^X 2"yT/A)> lf(2䆰 #Gw fuSO>og=coh(EQ dA$I[ *Ь[=M6! "a`T8G㢱{.Xr0Nݻw>.X( PwA A$Onkg>6~v ]Ql L$,)ӯ7hڵk XT{_#9$ڙF|[>s:v-NjBN:$8 SkQqBADL[2Ѡ# y#B-o~my3V, A1NL_uCu& $MG{BԮ4~D"!]ճ㞉`/mڴUEuVp z#Q6!cIC`Ѭ_F@g~ ;v}Υ`mp Aq%wM޸f;pх݄BG{n?V1`BQ*lI5덌gz{7spsޞ/f2ym)jo/t38JYӡ]~K$բ<дTUߌA+rg9gwߵg fp=S}b!^@iF_3mQ4CmAŎpQSZیdJX.E|=mmPUv)֚:0/FfPCy  Sa:#BNߑ"GFIj3/`O "!'AD554'X] Q23hРpWLCcɇvpZfhc”#-`FG)BF Ac.+ML;G=m`8{]AS-!۶ b 3ENyz`!~ YO 1Kllf0%~yu5x1ֲ_? z~1+b3o̞~.z̒H&u׌z Q! ,]eYD>8~,^[[E/,y _7:>koY*kgV~.?NEQhK<BEߋ[}!-Ajղ,W*,I rWYcY.Gﺶ5'!V>VÊ &R"@ ?ٮ QP "8,Dg ۹xsGT)LUՖE:v9k>xmf<0anO.y0eIrhiǶ֛T\d  ;ef?h (J@߷oX<:.;ԯ_hFYv1Z&jNYg%yƒ[Q۞RB}?'y-VAGxVݒ+=Lqgʃkgb!c ܡz$9yd`jG>m ï ?~09Tp/5N=Q_\?t޼C8cۣg6KՂ:YΦ's@XyW=HB.NMDzpxq{}ph 4'9`\h;ӇRzk$212ѰYڔfj2GHI3yVIJ"IDl$iUL Ro9hw~7WN7E޻҅-#/8 ;-fd$ zd =t3C&SʵnZ8zވ][_M'Ӑ=zgvPg,s #ϰ'YdI)$A@8!סp5RR2 {?mt ~*(~mE~x? Pz`VWol ƞ/Q<~A#ѻE_z S|,<٣Nk:kcfh]Z I7s /I8 B"2qgrH$pV 2|?;w߁Çp"PEEWt?FvR 0c ~0Z!vGy  Qsu6u:\O~WezT (2_/ IDAT'IxPjOPe]eSTlJNw`#MZ7?Aaӷ еk8?!kRhxn_Xm2,$ d"OCN۶m}>ryf5 ƟU$x-}G #kvU޺AP3189~Cot!Q m+2L#l>|qIC2-tVzbce-FїY>w܆A_CȾ 5\|vk|Ip/CҦvވHP|dd3D4h-z0&ߐ!W52 }dV^@d0=ݚ`.>I0nUȧ7Aa}/? ; _mG"Dfr_C}/}̚8@hNx$F`Ej]ƕagx+MgVu%Br1kASwゾ;GuYz td9}-Ia-_sR~_\:=(/4xpesmmW6gFEQ‰Lkm`szaK['IJiq"G&'X<"q7H嗇K^E,:() ֱ.-Տ{/Ɵ Iq~;q;w톖e-mxnv7V?Ɲdn8R>$.2]xr6vXyoμ0rİ;w30eln{K"IevmQxЦM[;A2 "mڹh(=V'!N㍿ mu Na`7("l;^l`#HQ< "a T;_"t>f^߃c %  tŇSd9;Vy>[>s:v0ۄr,9#U.pA!ϫCiO y3+]w.2AZTa$Lqo>n\)xMr+k-Z %]Ӡzpx}3\/4K˖ΓlBlv|w<EKd?lvH[ ͨb!H)bxl" qàյݑTg>6~v ﷳ7+(JsQ$f_C~bX3GZ܅nc) Mٚ0dI i1(H}^#^!i1@#L`"FtQPr=ػt4XH+_] Z%Ճm61KْpI 0D n˺"w(=^OZH`KdUA?>"DBIB9޿zMNNO=%]/}e ֆTIAO'}g0$KL_i `/BIB9Y3nzf1*ddzzLڕݒN gH}qC_¡C;{aРAhT8餓c8SVH+oYg 0P/ *BKg(]G ?0a{vӑ 0V`SEIl 'IR%9vz%%Q&^? #ҠY<+2:%4-' mO#?"|3$I EQb4+sW_K4(k g Q }/ a׼lKouV3[&[{Y2_3Tg%?;h퀳{6{clypHk?w՞׷ %b;ފ`Ԯ1To#/=X dŃ.q{oAI'~ ɚy6||i6<%P]ѷ`yŒZx鬼AyMI.{JN8`MP - tO$IFAPrQuz5Bu3۷_i|=۶D`MQa f+Ug⤜`m&P-4E)5:-ٔP$F=5̓aMr/2gmϡd >M:P>)mƨ`^=7#\3DTnX)\~%D6 %pc'%,٢ӬQbTE#G 2ixb3'w4()̈́52{>lSՈ2s^\A!5%ƟՄ)&R(ʎaxbk1YsxO΅6# jumpbfˍKX3 Qړ0dK?co7y#ybxL0Xl]/d@x^0Dg~qsZ`Z PZjlZqvYW#c*- *Oς} dmh$kcdiy&v|nQ#G4뗰7G3xlBHCV+Nebv4Aw4F\lƵ#D1$kf]:/WMs<3! UQ䤜PURX ) _Prrh V@APDH~e6n6s93n>/?=J?i dc4W$BurS*_6#%-(NY=Wl`YsZ6)VU5)lPv=; w>aeCQWQUEH:%+;4-~C/pנnAڐx:yBQEm>ڲiyWK2 GA0ז ʮ3qP܊Yu#jD,twTQ?lhSal(f&#%?W VhcQh 6 =mjd3OE>3͸J/XAiݟXA/)N{s9zUU5?W: `dJE$d#2iHOvV,Zґ͵wJExU]dOB?符.Rm6GU Xy3N?>)޻xfH%+=z6?zY65gwA&د\A~i^*VҪI 8^ӊ^9NjǼ+hp_^ӑ/՛ʋK^7Hh K m=Y;QnmGKWJt{r_P_X}"nOsZѼƉ[.[ 9 4o Ddu~D4IUՑ^/[O[x܁@!pfN[ NzDz:K!˄Ç>K{>̋c #DK$`.f=K¶61WPNN<(7W79JUՉS= ^QSz}5ta񗎢(ŵ8묳^{t٥=wA_%Ay%ϧhDSQZghVN:-SA6/ΗuEQ9Ia.3-_rc"Dh#08Ķ*6XFLo@]yקؑhKyRxG Ǒ5"D5{M_o_:w7m6b*¸3<&=."&M;3plG5=)/|ĨdnQZP/zbjGɓ];/Slo}Kkt~W::˖TxR"zv[rHjV'8+͌Ћ?:& ͗e?e^lPw*;C5S_#{(**P""M GDرi`_:֟ohw; M֐%ɛC5,F~%G`VG:Ew- x5mnTNEvd@foS+Bsd>32J_:@QWW<^ LԽ\ʿ۠]{jBHEkN,"Q%F#_e-]% b2cUUuutDR1X~9t/,$Xlب۠]Ybm6cfX"TR"$G1͛Ndşa/فW~מzeK*SrZ.4Q b4rt&Nş0Q?W~מzeK*J5qQZق(,L}OKz;5p>DYڿpecZ]`ogwِhM:M*}{Q}C{m~"~i4iv4bUU1E,tO ~=k8gfL'{< Jd<}a xY{r  A lP3aQx0mPVwAFa#^WG^]u6(~alw7%~ΖT4lPA&^֊ZǹZ<@ɖwٔ dCOXGd|tlIE$M9!'\cwޮlq-h lJewAH;kNWVWev_~ǝߩhx@fd#A/kn,HAɖT4<]IFMg=4ڠdK*ZA;ld&-O,ڳ-[[c_6(~5`m?Lv3\E/kϖ-[[c_6( ld6 D`U`. DlR?>XGݳlPT4lPd#Y.КC{9_ڳN.H![5WjבƎmjG6tlMUs;ؠ&fG2Mq_{U:Zv\:k<[ ȦwYdVwA .H&9*#8X t:xp;uBO=닳US= ޭ`Da!'8OhQ3n%; .~D&#GK޳祲y]EJwQF^zX8~?p  Y6DB,G!:?BP?p7k<h.|[!:BIɎ@ @#^oVp }E)'"i\#q jQ8p/-[iFU@P(ݒ7\hgA<ĨZ ,TN(H"`rTU>MK,ND9< DQ"ݚxYw]I7l^@QkJzZ`?MDU9rRz*۝bǴY}5w-`&ntBhQ@Ԡ|BSM%DF?8oxy N>sZկY9hN y}`Cwmμd(R&@(,u@8HM20VKG5V (2 r877@$2 \ qꪪZ@H@@PUui[FCN(ʚ]7sԜ-8]C #A4hFi5S1۱cc]EҁH@Ѽ̖Qk'WZ^=j ڸq=+5tKwfUA\PUu'Uvj"*2j׮C 6z"mkh"w?.]D bktBDG㰑sۚcC3܇_uPfy =\3sٳfu4'r! x/Ձ:e-Qk#Fޙ~_p*d.*XA7@X]@@qEI|!Isߔ Ut CUՌvY|Y3r) :<ȫW~_po1TU݌W* ,]u!. PZ-ڳ祮-qoۤ 3~A&sˊWFҪ: 9UU@$ 2^DQj ɩQEѻN̾5@6qa:tT^^s1777GQ1BӪDDTzR9іtN˳3>W[ '?鑿GRiNڷLOpA$˩{I=w떭ӹ}LUU]E!+|[~DGqJjYb%]V\\$|__L۶mK%%;t3 Enۭ}wiBD%\ǥ0"1ruTV-MYӷ۵M"#Gݕ؆S~EQ؞M`X/Jӿ۶}*VU.&( w :7n@?pԉր(D"orK?;{ +XNDeW>`3}wv.ZwtB(l_ce=ztA}9s]QEGj߭MEf4>7;Cee6)&zC5 XM5{5kqwmU"Ea75N ?/D9@@QMINΞ5z|St߽w|0"5D{_IC˖粉b @@1+8ҷjիȐB"9~E3SNx!Yԩw>(JSh ZLFK¦ެ(b/?ر=gsޥKm@Pefj8:t(\N<^f4dZ Z#JoR/8`V*q6?Oon:lW~A\,qsKVRI =BQNhh?ZUmF ߏiᖞSvj#. ,+TU颲 EQ6軼@z@W.PiMI 1.E @ҽAL0 K5wScE"2>gKiׄCy ~('xzKRIp?Fݽa[(pfu3ޫIzY-1h UUaE |W͙\h_]en%Fk wcVtND ,pDgKbE/CEf$JQ.1d}_hĀqq^пD/22O„Ds +d7 i-XEfȼ4g>(rOtkH*?:G%ꗄ##AerSX%rEQFzZa_hq'ҙEjߑ3e>Ն_kQe"׻B6o:i{ȝqjQ )[}^"a,6lq|>wsFcCx 6lG@1 RUС(JS"*[wT$4gdMAo0B g$j]{9(HW kfaa ̵К(~A͇de6q;O6]l5Gk׸ jߦ [* y%l`mʦؒҲ:s-0AiL3eϖ(LtM"Ⱦh7\BQ*mjbot9S)d*eko?] j3њ?-4UVUUQC$6n/KZWPNN[\ԫz>5[# qD&2k{S浩}餚?R}gl-?3zϨh,@W _NMX;gC뫪eC{__Bv%Kx^?;Q,\F>KިAf/Tjx>Ws(J)vj0 :,_;`ՕQ=`!d=@UV4,õTn\]eIeIX^iR>lҝg?j)$7OUUt Ƕck3- gRu8c."߁XUU=5TіtNKim<]uE.]qq9rDNկM1~c׬[7ƞ?sa3fq T~pK`޽{L?_$N݃`Y~z_J?,FNU:B>6 `5k׺~#0[(YRQë &ğ6KP*>y03HD h p>ثm&Nx#DiM͐ڗsCGBsK%1:ZӷJ@D|vJOwxYNw:E `wqݧSSUʷc4nĔ 0f @A_kTa{֙X<..Q#G*}gPiaUm Kk䴴n1* aȸ3g4txA וo9 ƒȟ0%:bH?_:zi?[cYO-,.wfJSp琊?EQF{),$BQxBe"xfg{ d 5jxvlDoM͠%"è"b~PTUwJ^;x=:Jş(™yl:? |T3/Mw^Z.~jdy$hשYoى,7G(.;!8,R6 jz}:.7yCXEKgK]?}] 4x/d`CWFDBw˖?F`$[+uT{E{L^榟)+,yQJ#{Z(T3&mf,:9-]UUU"u"KSR]wwuZ 9rbrz "ѪF wX/vg"FBǓW)XQqfiǎ'-#J]{[M֘( s.猨C FKJ ii`0 8qTbA%) $TXtF6p~M(iz GWKuCs2!!/MMǂM}q4F$E\*e\aTQE! DK2M@q=^]rfDSV-С-@ #,,Y-<\}<[P X€(,,G^tet~vԩ~{ս&ZMZd+Ңt):y5ㅞRÊlsy߁v:;?|ğ L(MdN:(?!2=ϙyř6Wن隿_4}V~p]2ۡCGY0z jt'$ f/= $o0{7 e@CN)u. 纼9btukI)^z?~2ã6iҴH6d^ڗ]ԯ(ڷk<`Zhs<&4Oל# #GSqUO5dгZ2c=ԋb_TыDVp-dI: Vq'_zK,V&)(i}]pKn4,G9%$}~Lirc2Ш#I'o>-"uB zQ14{ 0Yhaqs^b.zK@(uo[gKG5C5NPh ,~wxpC,?`QOX%m'[bRyy~[TB|Hqs&$~+`, f8J5OA[|'+zrQz AXv%_@5k4lm<^m9$khL{_ѣ_} Q?p AZ-=>Z~mk2C^^hp"D a||Lis^!mJuYOͤ i3EYI R# 1+EX mPnL9"P;]]\h6j]|,H#d`2w_(ء'R>G,V`8 z4z:ZA}&i4#bC_iUEQj)o-o.rpCkZM&Sj j/È5+KʌK8C&桷+1VK?[iNE|kR٩ֈDҜ6*OWW)h2M&"J]RLϣ3I1#/؋?%Z-ݽ@ 0!u7 u}gAoPkKMn2pIUㅹ&mTXsg`(\.$bUUM"py͚w5e)x1QIϥ;=S]bYTYuكIT옣iZ IDATU *&EIq(cEYi{mD/+jxɎGӚ&+o%"/D'fE]X(?zw9rX*{?7FA|UT/4ꥰ3P֡儕"ƨy'h59dAjI+卸9kƊ.z"ㅾ7"~H:^`i7K;u=?7MW[pBݫk{P 'bh~̣wmZ?نDANM[v{EV2г祴zkնDCOXtLt 3msƨ]TRhе. 4gXП v͟ դf6 RI7n~8ZF?DSGƍMBUUO\eG\\cKqP ?-놹UX3crk`& xR'Yg9uGUZa@K,NJ]Gט0h@]n}a~ng==Ğ`=77rbO_^ӑ?C>F93i4hsq>jǪvҿ?t#h!җ$4KEoRϿN:$:}{>|x}n]F:1gbdڔDl6b& ]fLPUV^^A99u\9^E!ͭE_FL@X:zyor ͞%OX`W[ "@h f`,V`gcBg'$tW5k1w&zggc7,uVNvErPzvLSf/e&ܴ}ܪ9v]Y=QWS.VUUbV9d.MA셈:]QbCֿ /^oznVNZMX)a~~ d_33&eT}:.xdٺ~]9*mC9YPx'L,O2gBXaK"W3*ϔ`oGVG8MK.2- F9=I{W~{07E2=ҜzZH+ *&̒BЩ IrDkP^uP#ȜtwЬUJg¶ |.)[\x0kk،`˳4W%5>77+&ׇo{aj׮C& C1?3n8; (2>Xufޮ)K 4EM<~x0V`o4Ba*<U%1!'hQ >OI+2q ]jx0,6,g9VV?W}d|J1 ZWLhbh~$#e4iӉ9gcoVOxa~I `֏Ygbo3o! OKe-' Bv.a&hG6֤4h!1QCE- OXGîm:"'K-O|2'F˵;ۅ<ȡ2d6UU}Ȟ_2m |#92E^^P9yuy-9t~lN*UF9z]eIKUU ]i,Z':|!B_:tib(HqzN}e{G_ҾX#"d~Ӑ[ E~`Z I2;Ǎ)MVq%yopǜ #\)i/Qm+C!Bx1j6 V'f[%JQ?~rsK`dA1)/"ebkLyNj+/3y4ð[m-/S;n{XUլ閊_OjrNS^3@3'I MeѩxoQL~CYDg:^`j?7K;u=aiD7l边{H숑w7,cRR[Ѻ~]z~lAf1nŖYGf e_M*[sHziYi5|?H_1_uetQG~$J[s^E v!A){]'a%ڗ$׾@'6=[p|cڵTDD"i ZdOxAX횲~< p՛+t3xJ/=.5}F3)ZEQjVX1?Քw B=jժEyy^qt_,^a˗ի_{(k>1OIk@t(@W!c[$["eFJfd\$S_ Nȑ#'?y ѬX]۶]{W!;u?W砂FrZG=zS֨_SZT||z{(J/MA95ۣ578&(7`qi zj,!׋TAV74Mh^%'pWQ>Op0Q0"]BoVMF;N/o)8:wjntJRN_'Nx5\ԩ0ʕxw<ڻ(Hֈ4?EQ&l$UU{WHǴ Tm~t:A,}LOٵyI-K_wGYl)Y-dLjógfڼ#3GZ uT2m |#"L{':qf& jD#-3Ȭrp0?͌Ѳi cY3*o鏕*F}<5xMbf[cW<ʚMWq$R?9"K8WD{0e b6x@sR('YTg zI *@ۙ"!l{YJezdt,ETlzK3/|κ=E"Pjv# \i,}eqnM 8ҚlRfMذ~@b'U'#4UcUK+9݁;YCn'?xmAhKgYJr JNh ^px~o@n5-uêߠ^=.6i_PQ"ڨc-z'bo+s離Cti ':qIҼ7=!'{IysG$Ҽzlϕ.:]QD”3Z ]WKm{,K_[UU1{^ `+DdSpFKϦћzK' sl?`Ú?3}~ ?mG `6U[gIS~0]ʚ?#';ɛg܉2;.-ى+k5\qdEzة3ˁw߽|•B*tTqnPz^rQb=ּ  ReY:P^Y㫈O+>//bĭ){ !|#pݟ]VX36/ڞ~Av!1)Kݻn1Je/@~:w/7Vtw"fb[f, v{%B۝v)s-b:V H6|fqѓP#õkك۷Hv^Ԝ1%GԬ2"OE!TKJ9GӞя7nݹUknrݕNT_E''6lJ(7XK6I8ѤjR,gAdЍŅI((gx !G˫exBW 6iOFJ~,Q=MZ b"u\ۖSKīZ>);skl4wӗ m8q9v4jH:Wgp5@JzÇPP 4ʨI<l+RZU<͚5spHO.}Vv"! _870+XŨ7UdlЧzuCFPoZGQIpTR 5uQ]~VO>#}фR*Ӿڷ=z*Q~~3!kƵr[~암gN^")ienCaUq7tgN+&ӷ<-"SQwGQL{Y4Ńj"dLDucz;Iz@xI~Ss4*"{(=\0 v9-=\sW:AZhs<.6]q;|=LEJ7ѩ)H.e'FfjϰmhQF.׷T^Dhhr߳wo;_A'5 B) ۋ((B? SA=eED]i5{v,|JfΤCkQT.%zNR7J(+ }ZL!G(4&p'n%щk2ijxeik+&FLY`QbzjN H"5zf~nXYx{aZ離Ͻ8?`1N_wYЉjNxΉuc=?~'4i?k'LEQ)GQ1inA6^3͵s=mnۣD-pG/:_ %Ŏ+nklATkƍ?YMIŨ[iEƓ(̊CY-HtįYw^+{b?C.ÿ\6& ,24جmd^~gFo۹t&T:k<}{!Y2"E"93Fܴ{{.꥝ydao.jӜ>qif2@UۯH w,?-R5liEeVd,HWj zIsi$~Z͞'boה,ܼ &#R[nG!IL艽t'gJL ]޽+t( y+UU |.\Qrʎ~h*,LM0I;Ika,`>/`¯1YWz=[!d~Q.Ov<VDPKv |ta4iqj2:qNWGN)>Y_RDduogÂc:sEMLGz^tzOUx>FZ$$+Pc_jEY}Q5a++h`"c-\>õ~7 RN̂Щʿ%%i6E~uթ]rOhVDce-M=u5bo3oyحȰS^vzP_Y#E1Ey/N 13䵞ؤy`䔵tOϥS $YǩY3=Һㅛ<p:4gh۟Lˎˡl} ;OEQ6[sϡ]O_,VbMѣܟ5D}c1u}8xN@ 6}E8MìسNyq24,^G-]wKYgyx‡=]fhŇθ%L҂RCdSc/8K܆!kom=01l!ס&\DdBp߾5\=vfēhN /#/cED=/ϊUZ-C E+֛|t*\ʕ[/$Ršɿ3 trʩԥ˅Eca)5{~>XGîu_6gȚ/ow'ev>4uLK"c$jm7ChĆ¯_U ?yw'SۛuZCQ^ԡSr>P&/o>|8KccزTncm5'+NWMWN_`G+ӡ,̈@hu'"WWb{iH]UZH&] jY[j"o-ϴ y;۴[2Ye"pi`sZ0jiB=!t e$L}yfnn.u1![8I!XJD}5M{s̮ ,6 [)b/pOeK"N[[)O$gƇ,,T>SDs֕ˢN}: IDATM!#/t7=+>}S23@k4-{f'Jho><UnERyjQ h#Vt$UUGzch-[8U'|FkEXvk ҹ#=ȫi /ҡ AHdsZ?1㼺F]B+NC@VğV'9QTU^^λۅhԐe+E Q:WA(@W +RUd쫷k>|Ƒ??SNJ$7"h1^9r09rDk.^HrF5Wׇ<;眓.H_d7ijo8FkRt 0ac.Hqȴլ'-I/]gQEu,dDclO6 :]I"K ]b!7wX7&ࠤӅ9m9h8W+MZL ɸ(ԸDoй)~, v-b;OT\zAa&-|&OpWok:&H ?5~<ͣv퓪wߟɅKYk+'XOaѦrN1_|^(!dݭMfb L <3vcE~ftщxpoOz{*Uad1mfL1ܦFN]eusD ܼWw_sAԯ_Zj&WGVA&/M4_9g+ԪU^z)oX_m%֕D)+e[,VʌVG^{- 4W6ɝ) `vsw&ҭXPTWg~蹲nf8]a9Rv7ġ.^÷Zj*l^zaFe?L))N{SL c*Ksm{gJW. ?Gi7<9i}X 5o=5,D"}d=H%#|^-2{I{f0]Kc^y՛&2]1^})OK1?pݺvuY$w,W^^A99uYTT\qOQ>Z6>XGeͅ~K2dzZ3v y_caFw&7gGY"]z!zӝ4?7-?T=^ZȀp#M=8*aoVH1`]7xp6V4S"*ʮB e*rsM5i皮҉UGE ׯ5]z-]Xx~4;)B%3gҡv;j[}X׀yf :o sk4pMһw_ڿC:&b\gƌ'l>&Q.:Qscί^CM. Y4a_^P`O?cW: { *HK l"g4Yד:%_=*Vh44'?%~zӝㅛO,_")_Xʗ$(hZ' 7Gj֬I}GnIɎDʩ0ȟ䝲ҿ GƍmRj&]Qs\s/elYz/yFux\G&F΁pbAtewul%ip[yZ:_WR5߼?QxkɤWKl:mdY-CUU/`G3 汼TU$@MG*` $#櫓ch40?4f,M]pAG:S煮}a}c>2CTni0"jM7VaVX;;rm)w)Gq, pD8Xװ,(b ۘ/r6{ -[DZmGSŶ7u.CuvIS >!> ?ƵƆ kGtL'EgتlzYgd6f޿vQ'u258y5Y!zեve{&H|Lٳ=4_6 VD~ ?ÝɔqEV睪Y&/>o@ݟwk2Zj86׏9gs4ktΕ^筻fŏa@f;AN(D'V+~/D~;bƭ=!/ڞFMS.Woۆ9==:]7pΔg>bA^;lB?7 l-Oޣ{3kKYlh'd-9.>=Q@2~3d>ڊl6hKI7Rմ}FFS8ٴרF:Wc ."M)NΆun5}\GuN38J'gN*WĖ%aQ @ ,N# Z[_X۾-}Z*.Aj 8 (IPA[Q@(EHg89g~d9 39ͬ~/ :K>{@n7W?(/m׾U?3T o=fOQ{QQŗ(E$̑?9[HUgS1sLeo^nyL.Yu8T _2c2vعЭߛ{v̨6~测PGjds7]ԏUJY)6{]۴/ʱ;cU[$eh PH/]OߚWJּ2C5~oݕޜ?ڟ>rwsẛ8T =٣-UjSOsy K͛MEz dmk+ʑ?]:?Q^Vyҷo.JaIQU5Wgv5oNot[ϏE07{ zy%)uޯIpoi)哯6{1@fKQշJ? *.ͅf苽rlCE)WELM&ˊ\zOT KsSڵľ~}U*GL {VVKsڛHy į@:QICy˞u 7fwr娍{b6Tf bnEqi.\{ ds#{~-rn\|T :3f@$zGSsẛ8T =>2)ַ}lxonߞm7C a4"6"kXGĩp^*8ltۅPOޮ~s'VoM{\*Ed٫k$q/LhTg{"Jz}a7{-7D|wQ =H/t?oqq77{g7f?E9QolJ"Ch9\_^Vyҷ_mbRfrDKsagm@fʯ@e{^\݊`[\ wmR+VU2=pW\6Ddy-_͊4ًSLM&ˊ\I\6ͭ_o xo)ZIbni*6f6{6u|cy؋Ksẛ8T =} į.N?+ޚCi좸4ݾC9jT sWi7\Dg`n:'.ͅnPf'N?o 6yoNGաۺ]oYQJ6{͞oE@ne085cwQ =m W\xHo6i\El*Ed[/~P;fX4>J/W 2.{6O7:u\؏͞E)lA͟}MyzURa_䬢ksͅ{o-gPڸ76:knJZu)M G^76Ղ/\؏͞E)la?laz7UW_#cfw:~[Km=-JY)?7{͞oEb'Bo=rjݺLfOn ҡ?! IDAT=?Refwtkj.1bR>9~szo6i\gȺ(eE~nV~-:W:YY^ܥiqɩ>{?ۗqÓr1yo@f6u{Gպ՟=FW?ZWa7{VoMÄ ؛z+Ed٫kx_=}ǃ4t#/v헗tURmiѼT_-Kˆzls='( .vofOFJnqu.Jfo_ h5 (*`)NXw%Cy{~G۷ʓ&~ G'\|~\6{36{4_D:S?MGȞnkiX:Z}Ff1u5f?kӑ*?@@o#2K߷eӴ9_.Yѭ#i)E_c+wʷ{~G #G9?o&M5#{l_DpPCzsd:c7k*Z6j$|Qa~W=[G9:LM&ˊ\Q/ Dz~E";~ZvZ!wr>7jn_ e)(ANy/'Olj#E }Tf (^j̙3W /]F?-fԯ6շnfoΜd~-φk`pɶ7+eᢧ37{@fll]JӦ՛9yLV6{$E>oEϠ7Cm.x~e^n[@91L=$eő83l@DH~CSlҭ]ʚ/?a@p37<3@AYbJ/G0twLD`*@D20 Cgl|R( u}:nKS9!# |W*"8A"c  IOQ1#u=^6m*'p|N:kSul߾#ﯮ-O|l}=Yy?.B3H& Cc]q2T "zsWWVHeEyٴ]_rR!Xp3Oz<7Nݻ Ӄ<2ZaTȩv ҽIrǻ~rm.O2U)Uc J@h) EFi]*OuoatfO~BM)U""-te:X Ɏܡif.X!}d逖UW]7F-:+rԅSӦT1N|=9a, N?#}5|2.rRjSON3 #_D_W^/37Bf?Da"rS!]3^GuLz<,'vR'\1\$L(6s<ڐ!C뮗 ԧOg=21SF@`Jr"RU.[ 6 }rx;w"\z}tvR`Ogq|.27A` N u!A@8b‹8hի9tOʄu+KeEy723‰L+ǍN*͛5}cw[mYj,Y|./8bY`y+FH7?z Ҵio۷}{ pU ;?}ͷe3V"O-/d߾} .Y>6mD?ړ#h 5jK& ystKS^O= _ޙE)U͊f$Eބd#aiC ŋ \t rv1)| ~xiQ1?p$N9oGM03ȁ|L0{5m!6CzG:I^* H5 xK~ xͷdzH௠ !iW 8^x?GfoP ӷM6$X07͂nh?A'k;2>F)UbJQ 9dj+;>Lf%+@0P PJߺte3Jd#@/WOu"s fz?E} =YA#8,%o-ysެaF`P\;qW]-1o"RJD 3#TVWs9W|`VVJ퇬"@RjȔwO.]n At tЏ3? XMg)3Mݴ]Աpt*.h00RA,HVJ)NDζoe5}ʾ}J>l@gTRJU'0tlйsYrAX l}-"R`9&(&]vH>T/n8_JPa~>2TnO:{g/~vo JW? `N:ۋvJ _4|DHT|:xɠc9-qeR V"G|fT\k ҵE>:зn8yE tg7 '8\)AO (ozKDxRjA@ զ{ `$LUJ`  `gW a_H'] ;dǎ:F2K (4}zyunݻq]*͛5N:7~x\nYw#8 g8CtCrmxd}Hxwu׌܇/H~:Fٴ] P+TW.&eA(,0V8aW͓nM!G(P ̟Mt ש~-[c*5i&eLEh=qwzt$N{zPȔN  RUY<-3اM':w" _vy񅥾>6: ̒幜 oSbݗ-8r}J)#r c:[!=k)8E뇹3LN_rRMY\{ڶm+;a2&#tiFmGt9n@=?ݷ:S?-Ns5gHOޑo2R{ť<JnLqv}c``(O>s{o8z(HmA??\J{uSO?M?jyYv_?o%GFgSe .fb8BPavb=_t oJJԀ+ɀϗKg潻@SOID0 L+WJ9!oR Ǎh2 ߩ`2spM͉ @hr^~s8'^'yq 0t \3ʶWv.l?x։ R\'=0ƈCV{ae2tvB/|!G$K| iѐOߔy3oiz**^;`?ĚA U_~}{Y? 7js9*d?@#زmC_0ZS0 C߆Y %ȱx*"ز{ědidmSZYf`7nifKUQ/4 Co';;b,Y֨Bݜ @G_P5jMo jRda,vȐxs\ရ|kzTsdu ,l*/ sP%~~:o׻0|9-ZYEP&gP+63b`u ҽI\8seɒ.F&_R8`%KoMz04vO?Faw&MI]R6T~bsB𘟺o0?cH-F j\~Lz\Vڝ!v3[K_6v1 c FUU5Zȸeu3#Sx.͛Kvw~+צ|sVkh's.rgNw K]1ec +|'~dsTT/a: ߧ{| 4 ~<~b&Q ιA#Gw7>,ꢶ( ~nl1z SٮW/Jx.@d1jsg?t9j&JTɳ`5H|-rAn.3Jm3SvZ hߝ72fÂx50 Q<_N 7K/s΂5?{eHk~ZdTagfP3f߈Go+)/g\z5mwwvҳS#9~㯱hR倬yc,Y}Wk8DI06qLԓ47 DD&dz?Ӂj=lˁ=S;_V[1&_2SQ sal}F;W}\pNi^Ʋ=%˶gȃYKV PٔGk8!e_,y~=쳣z\5j7lY>?wkIp'TrMKL{^tv uӥg%| _t0p?[˜[\gf2x|s#?#.ǽ[֭绲ߖ?e:8L޼VwRyO wVv; eriB/Uoa5{2sN=>ߛ^@,81]6j2ԴA / ސA!_˺4ۢS᥀< 90_S~_7|@'t[ IDAT P2kusowV@wnqK}mp oٴtL 1! kG1+}¨vV͐xy7)瀟p:aq4F}nM yhfR'L)A:{o>yڵ,92xSZy#.z\ qVFGgVzᗙ}a-uCM&>?zIt2 cbN@CVZ93o{umG渹OnnA.It 3[stYQ`#pQ].9@6\ Yd~d>-Cg1<>180͔yY'B|W+W2dʹ˭8B|Ҥ^s4f(vMOF/1>X}҇paBHO=;pn'ɐ!C>xc?0tv_j <=dF7< ƔR+3O?[&EF\det҉'xuѓ9h'c p$g!.27Z b'0yyzַei"PW΁?ʔ2^.y:;á! 6' N6!D~wvk}4W~%ƍ[? ہ? 2 Y۟^F;WgWڐg+ʼn7g[9%KLt? ֥C2yl̿Lǃ;26dUf_4/>ٕMdhpt0`=.h;kÀ}mF_{"?;1jͯ9;,f aT|Z, SN}:׾)Gp.^{ vA.*Z ?Y`wթlt8\J3}czTyr"矟uOkl8o뎮t`׉ aVA ð\TJ)]tFY~~~z50>g)~/o:~={̘y'9:I&gq|pg[F)^gM:Ro:>@OCԱPsεhzTq.ALA*M4ue GrWwlg?lgY TVg34~yhz\р{t}G.rRj@.sf;Aݻ}ѱfw,e~***$/Ͽɷ ur&:g'8gfg(Zs<ʓwÂ!rvzv/e]x{)>g2DI..}GxLek2{x+ǍϫeY˒ub.f`)W$_KFU z7h0PJ};K @rK9u'miٲG5r{&3U_/zJs9zb~ noEe 4Z2F~E0 |3f>f%_z|H3U!vWȴZew[u!c{:m@2YM_aImӽ/OsgahP&HH3ّ$Yf4Ne7cG'CR\w\T/&Mz6 6@7f&hkE:ب#k^[)51娶yߗsUFW乿98iK}LVҽ?mvpCjmk^F J *\wh:﮻;-E>cWjdU`~듩Ku~kEzVΝȑ?l7mQl11C_C:57^Ə/}ګm2k9쫏aN[?3VwpHj`z/*SO0de3'_*ם R3'8:##';ܕҥKKe =wD9o.aŏ.I>æ&? hfoA/0QS)ŦċI: 8hի9tק랄-򵎖즣3:u*FyzY"1\D<q MUJ{tl@\y0B}IO̳/afr~t qC/{j@4k\?iܸq ֓@,?mȹ?\:d-ߓSA3d!, Xݤ=i!tpL-Ȓߧp׸qq !Շ rkF]KYj`/[tnh sX ܠrkx'߷CS, ]+&̪fHU%ss駟ks5DJ$`=3SO-L#+dЁMrթc%ƚ?!t2fɡUV8 x߄lb'e f_1n  ,GB|cɲHJWo^Y~|ވ˥py0w{zIؕL;TkrdB)_r\&vʻ"$t,N&Kfy!<[ ۜDT%EtЁ@`.4g{Ϳ_'֙5ڦ&e @d?v[=8zf%_^V@pPm-R_n "J"K=8 [l?ճ0|rQe}ceqg\M)/[&Mȉ'v4Lhe2YF{JV?7aH;yG/0"80 ED k_.iK{z[%Er1f+r9: ޔ{z"GaGOt;ap|k"Vvog?ʚ&/TdWrhę/Nƻ!l #o~DdSkǮ]ƍ]):rԓ ?[w%q ?~A惶r5Yhd̋ ?&RD6_:I "UtvTUU֭qBC@̾lGY ɡn,< mvD/`*7 Nyu `?޶mwV5jJ Xɡh_aC~+R42@E8XX+W]zLD2huFo]v`5Ѓ9ڶmFF_%e~8 N?oR*Sh PeVXTC?6hM9\y|짜}Mzx`%PskU})=N>YNՁ^$9l߁uj@f_n_M/HJzזHيE8IgN>z}Ro18#Sڎ)'~ |kJy[LdӦwA?D@{+~B0ʂɲ^D^_Gt;vx55&T)E rsOlO'ar߅\ILw73@$ nZ {=zH'] 9PSF tٷq|?m?{~Gomir\ٮ4?4=4o-ـnw@JNT32ead^M.]WY8C|>Pu ݲ=ꥀ2{oYfR@Ԛ; qw=+^yYn|7p=j~0\Z}͗6?$E[^`F2Y61$k WZ;mvG]#G]$~tUiV9gZoW_ysu9p>#G5 ȹ֞5*|aFMiMיwk,a^ugeN{Pv WNp+3p96-z-ۀ_r)AYfɃ̲ 6@4ĕ82l%d/(AD+,%gLu{a?5HTo8ҁ.?R}O|o}-XffC=X֛D ް7O_GpHsdZuzk\ 0 Ñ;"C%SG#plmanG-|Ή#Q)iNaa]I_V,42b@^d{r􎺨?d6eDQ\K0;,˘uDvk̫zwu5LUW_m,5(1rعr-Cxm(y/ ZlT! GoX)U7 O6)Vr~- -!w#A{?E^ؕfR;K6Ȯ]2~τ7I;^z&8IfܕCW*Jga8zs.$"pr3[d|Z~.1F4/W:b=~DZ~={]ɗHny|{Ν;xQG$eiGG{+XR:vhR3{M-J`~wdx#T,lp4,R/29\oˤdΣ>6߳= .{VvTWD\XDP3?6,cϜaEd~Gwow)͙b A_ 0^iÂP|{č)^<%pAl,YfɃr#=u{+'nz%0,DaUsxdwԅ3Un/ L:0$fSs[d9M7hnP@wt0@.RU;eKKdk| qkʒ܍+c 2qQ;o$Pi;npt[K޾c\wNN0tքS'd[]uuJ=%tA ;& u^}%J@*i =jjXm2iNeި*qex#r]VJUyT|NuVN>|zF޽뮗MT2,0~Ɔ}GCR)*B n=-R|&<=f9E9dsn۩?Q °MD}om%09if߿^7,cJ#c4CRޭAqx90 >Dd}{e߾}qҤIiҤ4k\S%e82 2n [\<%}进?8|uVoa R47x)ҁ=/-_Uu"5{t1,ݻ7ӷPHљBDёX 9|k?>ymAw}'00ߡB&YRP'4Ȱ`".;ݛgoY˃? q!V"YI"QT~SɲbKKzzi2';' 5q m+GYK П{|4ɵə^Bͤ0 "q/ˠ6P)Ecv7N&Hav>\D%;rA?V{{^{IvyQɞߖ/v7>8dizRwiu䈖G=y Y30:}˂Ar­ӭrs0 C~(+-ce2t01 #>#G]$Ϻ/:W˼Odp2_"Q7&,;;u D2땗 ٳr% IDAT( άX1ӯ6ߑ !Ea\e6}5y<'Z,65J)Jʑ_P&`{^z͞4C "16C=i|ϲ=[[:9fV?X 2dL/.ݻYޔ'(Kd\fz/!n?&ƀa0+GppJ>sb ݯ *?A=Β^g|cG2hsY>1E6[]ˀ'M$}uӝwޙm9o W"倐 l&7ե,^\:^t96Uu {HYjO- 際-!X)s  ;7gȋ/L SneW_}JV_m:7@)Ui{0ї.5ܹ3HFr?A_'c/RWߒީpW]T!c>҄tݮ/f~\߿3d𘝥 E/Kؖ"BWO/d~46w&?~ɯޔӞ^k^d".-a)O޶v|pEzR[Nop|crleI  ~5yL؟"g㮺ߥuJB<`Yd{ՕoȞgN?U.dž_^ocאoNZ~4=:{O=_=k8Ä ؛Y}"9;:&$l`B  $QSYuťD\ĥ*AV K *JݰB51$ bHBB b?'q${̽羿QBf.a79/cXiu|n,amf=yUer/]l@EQl`?go4q{{mu͉`Ovle=:n#c{]fq3Bd@~ ;0%3sI¾t3x**(l9Z)c$K/`A%FVGOz#Sl4f[wO=p~o} F|G C:a>%Nl(CD؏Lc(J;6R煵înNs( VUU(EQV`Y^c~C񴪪\~& /o96\ <2^ogi]>Wdhi ,yko@-%iVh f,EΤG14R/wԦO7X(1`b/vET:lA#. ]&Ȧzz>No9}FdOikgOtB#M/5?Jz\g,\D},% v??pHcE/PTT$,LڀD>LTUuOQRo`IZ4?C/98Ȅ/I*pE;M"̩?3@?St?[MM--^o S`](,/}%nŖkM?NE横*(-?{1a/!UwU䭦țoGnǦ/:"{gNJN҆+2NJD҆sG0VVOck>2-\brriٲesu_(S4FZa›o)28TUUE-=\b zR4Vo+@&2qĦNc9HrMzmb;^~B]Jh-/-=񊢐_6"59!֭@/к#b-C*{볩2?c%^[biܷ!a52cwT}+Ul,;;,1y9׾xs]շ0g?} Os~ "n73kQvVЏ/t6n?eЪ7]&Snm ^| eZj("4sx(a_NiĭQ`¦IuqOѝuJl OB =28liggtXHpL¿SbBN7cfl>ޠ}ٝ'XO&D!}Ėk?^I7Edq#Â.-F~~>/Z/wGXRK ]^jsޕ * jN:Y.R&pD~pn"= ~uz ?X;' c}`hγ߸SS4VyM_r_0OQy"'_UUkR@4\X{7?_O;SjRUu.${m qDVV}ܾ LpgV٦mlIpc3 Ă .7 OT" ICOq({l?/g^`wŸG͚iS=IΝ{pNO)P"!mD}TP0`y,IRQ7 #רEw`yk4jc{h0姟7)]#SlG#.A-cyWE8eyM'F1אKpO[;F?>iʱ}tyh,ue.eڵkGoBH sRN4q;h 1m@n"U[UUKg65~VX()+洛WUh7EQX1Z91ȾxUtKxUUfIBF\{#2%:'|2j=IqU[?fKXԺW3%ڥ-Y6\ؽl߁Zt&}Q2Sw>ٙsiW ? gÔ u\0Ӿ> T~߫Č' D&0LSCTUuE=ˬqdW,{EFzW`jsUlXKTn',:uu-uA3 ԟ^lp]g7jcxi6UE_tEIm=CuEviK @/I`<Р_{?O-s6 - \)As)¦:|!_7lguVf̞0%Ǚ/hѢEfMw%.Wb@F\{3pj 'YфӬ҄+R#4ɸEKJ@ شqq\N#z>w мA-2_h9G~Pe:::6ɾFOm5d%ܽEDD;wPuuY{dU$huIE"-\iECi[ޣGα闪:'1邽u-BUنYe-bϩ Ύ;Nն":QUE;vHĖQfdOthĝ4jK6 m&gmNXK~̤ɷnfg8'!l$6ѷEA_cwe(-Xvo/kF_iqy^V*7\{ y06Y+{"8<ؾC +. ^{oMM{R4V Q8&}mj 1gd*Vds?VX+C.+شSRޮfі{ѽ_pAv-Ρ~+ڢ 6:OFeka&Pe6VjӀ >Mx?sCVɶWEfkRް~o@{-28~ IU~;>6dɾ~>uL={t7uJ}᫯wP~&ڹk6eMJUl@mtxw68*IE ϲPND2&s?Y&s?J Dؽ.yF G;\r{X?'pA&1O<9^pYgi.]Z!awA8=>fmՌ6btΏG>TVE hWS{ZRدh1Z1Wb6 %ZSsl2mO  BUUSE.Ėiߏ]S'߿J*)I?8LAy#W]qkw!L8TB9B CʉN{od2MtQĆk~cZK-piؔ_ڒe4БϘy/_$vB^9,GO`GZJ XݜUO݊VTShM>/Y+/v[Bvw y][yk4jl :υx2 ]vQuu$,/TDLIy7~EJ=qK[{) \i(tda*l- ENٷ?q:tP◩G3>dQeZĮa6ݷ؊xp(yM8Z})-~gU/ᴭ(}GG# Ùz'ϸ\?'witqIX00gwC}-g^֔Gfd ߊNR~dKC꛼%y7~EJ68*5ea෯@4bj] WcK.tE?Џ=;.ǟw_>0-v! !!h6vx{J]I[>ǖLo5Ӭku|uFS9S읒Bd )?~cFs_&MV{ݴiSǜ(̷)ƞ3tjL9G fiii"Ik|= x/`/%IԾ))66T/m_-BUr-Q3Cdj1TI:?2a/[|q.]3:x~Zw{QkM_[;G暶fDgo z9KW.>&MRZZm¿Ɩ˺U(}3?SFiĈKij^tچy)}P>'7RDD+G_%FDCwN`)c["+nm$ڀ#7Oh^㎺'=sȻ+,#_~fpj>,¾)Ky5VOЏٰsoˠ, 3wvA_lqHmeR_}Q&:ϫjė4"q/t6'cF7}g0k˝r=GCw|zOt/A ^TjojݳWX`>ɥ^xv_ztOnskjj;HWQXjkk4>t̲7!ޣܫ[[fc|5)*ؖnUU4SP(~nڴ"y &1[{dDk,Ă='G_5ٽg\EdϬ"zzBG޲`9Vm+UUuSqgwjzFX`gPT؈/k{KJ5 :jmOGڔ |jannN60Aa}KKKh~eS{!%l>XҥkOFߟG͚c՝ T' R[4?ѣtCW׈^_ҫg({ _dJ_ܒuAj5R1It묶)r@2Em/UoCkVl~_%77'2maV0܏^*N>h0 }RV ل Xؐ"صs/khћjށ}l?k␕gXMϭXrҡCB"sw%8177g 3 /uid^ˎ h`F4oޜ?_}07OL/BȎ lyA?G eE6-ΖjEٺm;]qK{xXq#/KE 3:&w5^Iw9NmRo- TSQuAONOى;Ŧ^W}V@֭؞wC͙{|ha(- =߃>0R؊e^ؕ `Oll'[ =e6:˓{g骪.' [Ј b _h&1lRn軸_ˇMȜ{n}%xؘ^aRTd[6wS跿XV1YrssFq@_"٩8d/.z]ox\{!1ѩ%SgW5}8h .e横$VSB`o"SoW0y Lt菿Vr Yᒋ(f 6 ~I.>ivE6]#رӖ^}nq,u?Wܜ/jǓ+(Zpp)?ߞ.4\Э[2tmm۶\6λbYgVrrt*cY?Q %܎WTqyM9@#2wwtd>: DM"#_75G7q\B`/Sm 6NƤɷn2t81=6wCէ0P2J?ut-n:RRF)! t=3.~~>3` p*7oF?fBp>2<q Ys|{EJk fTPXDv:: 9>fκӍzJFyhܜP?3`˄'?~/며sߍ_!_xEԴipse,ͩT%ZRw]p,{wEok41Çy7~EJv94!3–ov9 2H`hsQW3ס ]KSL{%V1<#srss9( W<擫S/CӾ *<= ]9{MV eiתFEQ]=(""bccNwPMM A~--u/G<) Nb3k괻iNl[nh5V TU][Y ֶ?KԞ:W l@UUK-ϟY'ON/cu7~OYZX7_W- z<}7ŎHްAtl4l)aM.ؓ?CVbA3Ī} s>ڸd !1&mҶm[5Y[_<.f{Kw6Z^Љ`8qQ+5ݻ7ZA+U"J7K$xW!=F0ovLUU3[hGþ@sWׇ-L:YB'LO`ouEh+q9eˬfnK"S{QCd4Rnߌ UUaiLxD[k޼yޘVܜQx!*d,G= q{.Z6c)@%E=M{_IJDnw۴CtGQSǼ=&<[z\`эopX}~ i&T: 111{Vxhi03;낽[PP@X'Kg9nz]{<177gI_E =2(zL`?RUUqu[)rbB>wcf蕿}9ya9~3L>(=&?8lai ŻJ]%wlKT?RKqAq[J찗"k;N1[Pl鮅w=zg*UUG<QWΥ^m,RUOJ"*D۷g'u~~ t{5++(lpD'CqȰw:({?0R$h~ny|mFOm0 }%7)>sUUux27A5)?~ #LS*umקS;JPNP|M5m-ڏmbD8z7*l kčh`O6ٗb{"ScF qs;Кxz+~_x<lpˑe^VB/2*bqIdJ_G}F5_ گa{‚Q+5u'kIJq.R-s}D{K<,v?{0x2 'Ozg˦6 X*\{5ƜڏDJ}7Ky? y{m|f8 -l/< A,߮?` ͟c~d:;_2B#_0Ƚze.I]Z{ |("ZOO}tן=vWx~{jQNTU76t0$7!ޣTZ*B?AgSOF&st,ݸNͽ`=nDFPrd JhF܈nIQz(X*3Y(!1'fZN~7]7f4I=>t lS\ri,CT&v8EQt%>j?z6]M3GULc)eBQFj &1)cF2D A0ҏ7AbcK|܇=wDX#ndz~>s{IHH Pࣁq/1 <$ρ>ZGd.ϑ$]K =a^rk)n+3e,I).{ X5E 6xYUԭȝC.)QדfL=`UU-D9 #IG'tup_Ӻg/{5ƨ]칹@EI~Dq]<hR/ Yάj?gi%tʫCqMXJeqRbK8z6ù~j(~rC<NKmqu9'Go{ouEc{-^ɻM/,h8hۂV̑=[|7l-Ò^@< h*QgunM 쑏w"*R* FE5u 0F>NҀl:M;#m>v-\Q(^-睦P?߯"}*wۯ{Rb35h#.ڏ p0m 0wll6uڷeO^xTԘt{!s6_>ư` x.! ӚRDU/aώ;]Ԏ6Xтir`vv*ӂ>,3 | ~, ozhnZu:rQtC%kسkW+6ق~:JqUAq~, 4@ Q˴RS\rX`EQR0k(b LOr-:Ka"{SRR`/]%lBS܁Jc~,€`4`@[|D?HxT#«=?;GJ7 9k/[aaOkčm"s{1=iJ@ β<]&Iȇ{T?RKq{~,lPo^\ Γmoxoۯ={ ؓ7#{no?Fz sG{\a||^|M5mye&ڏ XM@:S>L_ӱۯTÞ~F\BʴM0L xsoJ.sup=r/ؓإe{mpLBs.s{1=ğe?#={S܁J{A^撔ݥn =4&O8X4%Þֽ ؓ#nCծZ`@sDY 5+'=J+d9\–[4 lp<`rU(;~ la!kUD˃}7?i/e^|K~\F).= {(I7`n.Oh3:V~![`Md%Gmč薄`OF{`?yMUٮ{HKcڏR0mB<2hѳA~2=,sc.Z6c)@eF\Kÿ?r3X S\X{.9op r1eO~=`/c[JlRZ+ޓuGш @'n路=G;} ,iս3$q;KR45Ǵ?qx:Yۯ+`/A9A5留2r,E#.?9~Sκs_W/iݳ= qc~`?9- fY<*? `{{ ~:JqUԡ~,` S4UXuf?q;xk]칵@h!%SG>^܁J{jjR* *v,x=KؖAq~,ֈ[`?\0ư` xdO~l#JYEQ ](7Þ;v:ө%('mE4|F /tڛ`=v2kAɑ-(᧣W^@#.pA bg={;q}tݭwe0B!'C4P/ ^Zj;k-(Iu^\(JjلǺXJqR%61 ޚr;=)}?HbcMxv),i3S\aW{no?Fv}ѧg&jz! ˡX:G>,KlRZ+ޓuc)ezhCNBS8e,m;zб_|}4{lJOO eASe~>.?u {"@' _#n̏G~`dϽT*m/m{.IIt! JD -t0`{J9[uK&u-H!9؋?Dtp v}[%r6I;7I7ۃ=F]칵io\ 6UW8~[-mIU5 ~~i썿 4,{qUԡڏTv|2h:ֺ&^[|رt٥#p#p{.Z6 ڈcq Kt -%Ǩnh֋M^2h% r{PcLUB2ЙV0| AM{SXG8*umܱ-%6S)HmF\K%/+@~>?|@ BSzIAt8&&%usb;ZI;@%Jiwi)8+q \Џ NMۇXp{I&oZ/G BED+^%V叙tRΒX3{BxԎ_S-u#.=4GkV\:r(3׏L/}r{ϋw?xq3B-KR?ZaVC큩Tޖc Y=?&2#[POG):5hMTq'Ai+Qgt[Mͽ'~e9ދ\Џ NM[z,Voe{4 lp< P_`Ejjy ].l%_#n랽 m͛mpT!m{(4OF ;&~哀"؞zɸL/4{p lpL!y<ZUs0;JOO ӍMe>Y\칸,`bo x@.IItUKGrip(!E#n=}Ah{$A"@68b%=47.? 3ڈ[0Wicp<O"Zlk@wJ MMݻ'fJ5ر^6qB6 qCZEPLL tXI](JvT[[CE7[z6`mx<D T! XF\@MN#ٸCB )O`"-q`.I[̂. ( m*"(IΫ0 ث1 y<D4X T5 !9Bs ,V4BB~ IENDB`pdb-tools-2.7.0/pdbtools/000077500000000000000000000000001521210715700152525ustar00rootroot00000000000000pdb-tools-2.7.0/pdbtools/__init__.py000066400000000000000000000063701521210715700173710ustar00rootroot00000000000000#!/usr/bin/env python # -*- coding: utf-8 -*- # # Copyright 2018 João Pedro Rodrigues # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. """The pdb-tools library. A Swiss army knife for manipulating and editing PDB files. You can use pdb-tools as a library or as a series of convenient command-line applications. The complete documentation is available at: http://www.bonvinlab.org/pdb-tools/ Examples at the command-line ---------------------------- $ pdb_fetch 1brs > 1brs.pdb $ pdb_reres -1 1ctf.pdb > 1ctf_renumbered.pdb $ pdb_selchain -A,D 1brs.pdb | pdb_delhetatm | pdb_tidy > 1brs_AD_noHET.pdb Examples using pdb-tools as library ----------------------------------- You can import according to your needs: >>> import pdbtools >>> from pdbtools import * >>> from pdbtools import MODULE >>> from pdbtools import pdb_selchain Chain the different functionalities conveniently: >>> from pdbtools import pdb_selchain, pdb_selatom, pdb_keepcoord >>> with open('dummy.pdb') as fh: >>> chain_a = pdb_selchain.run(fh, ['A']) >>> only_N = pdb_selatom.run(chain_a, ['N']) >>> coords = pdb_keepcoord.run(only_N) >>> final = pdb_reres.run(coords, 5) >>> print(''.join(final)) The list of MODULEs is specified bellow. All packages have three functions: `check_input`, `main`, and `run`. The latter executes the logic of each package. `check_input` checks and prepares potential input parameters to feed `run`. Use `check_input` in case you are not sure the received input is correct. You can chain both functions: >>> MODULE.run(**MODULE.check_input(*args)) If you control the input parameters use `run` directly. In general, `run` functions are generators yielding the modified PDB data line-by-line. `main` is used solely in the context of the command-line interface. All MODULEs and `run` functions provide comprehensive documentation. >>> help(MODULE) >>> help(MODULE.run) """ __all__ = [ 'pdb_b', 'pdb_chainbows', 'pdb_chain', 'pdb_chainxseg', 'pdb_chkensemble', 'pdb_delchain', 'pdb_delelem', 'pdb_delhetatm', 'pdb_delinsertion', 'pdb_delresname', 'pdb_delres', 'pdb_element', 'pdb_fetch', 'pdb_fixinsert', 'pdb_fromcif', 'pdb_gap', 'pdb_head', 'pdb_intersect', 'pdb_keepcoord', 'pdb_merge', 'pdb_mkensemble', 'pdb_occ', 'pdb_reatom', 'pdb_reres', 'pdb_rplchain', 'pdb_rplresname', 'pdb_seg', 'pdb_segxchain', 'pdb_selaltloc', 'pdb_selatom', 'pdb_selchain', 'pdb_selelem', 'pdb_selhetatm', 'pdb_selresname', 'pdb_selres', 'pdb_selseg', 'pdb_shiftres', 'pdb_sort', 'pdb_splitchain', 'pdb_splitmodel', 'pdb_splitseg', 'pdb_tidy', 'pdb_tocif', 'pdb_tofasta', 'pdb_uniqname', 'pdb_validate', 'pdb_wc', ] pdb-tools-2.7.0/pdbtools/pdb_b.py000066400000000000000000000116421521210715700166760ustar00rootroot00000000000000#!/usr/bin/env python # -*- coding: utf-8 -*- # # Copyright 2018 João Pedro Rodrigues # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. """ Modifies the temperature factor column of a PDB file (default 10.0). Usage: python pdb_b.py - Example: python pdb_b.py -10.0 1CTF.pdb This program is part of the `pdb-tools` suite of utilities and should not be distributed isolatedly. The `pdb-tools` were created to quickly manipulate PDB files using the terminal, and can be used sequentially, with one tool streaming data to another. They are based on old FORTRAN77 code that was taking too much effort to maintain and compile. RIP. """ import os import sys __author__ = "Joao Rodrigues" __email__ = "j.p.g.l.m.rodrigues@gmail.com" def check_input(args): """Checks whether to read from stdin/file and validates user input/options. """ # Defaults option = 10.0 fh = sys.stdin # file handle if not len(args): # Reading from pipe with default option if sys.stdin.isatty(): sys.stderr.write(__doc__) sys.exit(1) elif len(args) == 1: # One of two options: option & Pipe OR file & default option if args[0].startswith('-'): option = args[0][1:] if sys.stdin.isatty(): # ensure the PDB data is streamed in emsg = 'ERROR!! No data to process!\n' sys.stderr.write(emsg) sys.stderr.write(__doc__) sys.exit(1) else: if not os.path.isfile(args[0]): emsg = 'ERROR!! File not found or not readable: \'{}\'\n' sys.stderr.write(emsg.format(args[0])) sys.stderr.write(__doc__) sys.exit(1) fh = open(args[0], 'r') elif len(args) == 2: # Two options: option & File if not args[0].startswith('-'): emsg = 'ERROR! First argument is not an option: \'{}\'\n' sys.stderr.write(emsg.format(args[0])) sys.stderr.write(__doc__) sys.exit(1) if not os.path.isfile(args[1]): emsg = 'ERROR!! File not found or not readable: \'{}\'\n' sys.stderr.write(emsg.format(args[1])) sys.stderr.write(__doc__) sys.exit(1) option = args[0][1:] fh = open(args[1], 'r') else: # Whatever ... sys.stderr.write(__doc__) sys.exit(1) # Validate option try: option = float(option) except ValueError: emsg = 'ERROR!! You provided an invalid b-factor value: \'{}\'' sys.stderr.write(emsg.format(option)) sys.exit(1) return (fh, option) def pad_line(line): """Pad line to 80 characters in case it is shorter.""" size_of_line = len(line) if size_of_line < 80: padding = 80 - size_of_line + 1 line = line.strip('\n') + ' ' * padding + '\n' return line[:81] # 80 + newline character def run(fhandle, bfactor): """ Set the temperature column in all ATOM/HETATM records to a given value. This function is a generator. Parameters ---------- fhandle : a line-by-line iterator of the original PDB file. bfactor : float The desired bfactor. Yields ------ str (line-by-line) The modified (or not) PDB line. """ _pad_line = pad_line records = ('ATOM', 'HETATM') bfactor = "{0:>6.2f}".format(bfactor) for line in fhandle: if line.startswith(records): line = _pad_line(line) yield line[:60] + bfactor + line[66:] else: yield line alter_bfactor = run def main(): # Check Input pdbfh, bfactor = check_input(sys.argv[1:]) # Do the job new_pdb = run(pdbfh, bfactor) # Output results try: _buffer = [] _buffer_size = 5000 # write N lines at a time for lineno, line in enumerate(new_pdb): if not (lineno % _buffer_size): sys.stdout.write(''.join(_buffer)) _buffer = [] _buffer.append(line) sys.stdout.write(''.join(_buffer)) sys.stdout.flush() except IOError: # This is here to catch Broken Pipes # for example to use 'head' or 'tail' without # the error message showing up pass # last line of the script # Close file handle even if it is sys.stdin, no problem here. pdbfh.close() sys.exit(0) if __name__ == '__main__': main() pdb-tools-2.7.0/pdbtools/pdb_chain.py000066400000000000000000000115331521210715700175360ustar00rootroot00000000000000#!/usr/bin/env python # -*- coding: utf-8 -*- # # Copyright 2018 João Pedro Rodrigues # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. """ Modifies the chain identifier column of a PDB file (default is an empty chain). Usage: python pdb_chain.py - Example: python pdb_chain.py -C 1CTF.pdb This program is part of the `pdb-tools` suite of utilities and should not be distributed isolatedly. The `pdb-tools` were created to quickly manipulate PDB files using the terminal, and can be used sequentially, with one tool streaming data to another. They are based on old FORTRAN77 code that was taking too much effort to maintain and compile. RIP. """ import os import sys __author__ = "Joao Rodrigues" __email__ = "j.p.g.l.m.rodrigues@gmail.com" def check_input(args): """Checks whether to read from stdin/file and validates user input/options. """ # Defaults option = ' ' fh = sys.stdin # file handle if not len(args): # Reading from pipe with default option if sys.stdin.isatty(): sys.stderr.write(__doc__) sys.exit(1) elif len(args) == 1: # One of two options: option & Pipe OR file & default option if args[0].startswith('-'): option = args[0][1:] if sys.stdin.isatty(): # ensure the PDB data is streamed in emsg = 'ERROR!! No data to process!\n' sys.stderr.write(emsg) sys.stderr.write(__doc__) sys.exit(1) else: if not os.path.isfile(args[0]): emsg = 'ERROR!! File not found or not readable: \'{}\'\n' sys.stderr.write(emsg.format(args[0])) sys.stderr.write(__doc__) sys.exit(1) fh = open(args[0], 'r') elif len(args) == 2: # Two options: option & File if not args[0].startswith('-'): emsg = 'ERROR! First argument is not an option: \'{}\'\n' sys.stderr.write(emsg.format(args[0])) sys.stderr.write(__doc__) sys.exit(1) if not os.path.isfile(args[1]): emsg = 'ERROR!! File not found or not readable: \'{}\'\n' sys.stderr.write(emsg.format(args[1])) sys.stderr.write(__doc__) sys.exit(1) option = args[0][1:] fh = open(args[1], 'r') else: # Whatever ... sys.stderr.write(__doc__) sys.exit(1) # Validate option if len(option) != 1: emsg = 'ERROR!! Chain identifiers must be a single character: \'{}\'\n' sys.stderr.write(emsg.format(option)) sys.exit(1) return (fh, option) def pad_line(line): """Helper function to pad line to 80 characters in case it is shorter""" size_of_line = len(line) if size_of_line < 80: padding = 80 - size_of_line + 1 line = line.strip('\n') + ' ' * padding + '\n' return line[:81] # 80 + newline character def run(fhandle, chain_id): """ Set the chain identifier column in all ATOM/HETATM records to a value. This function is a generator. Parameters ---------- fhandle : a line-by-line iterator of the original PDB file. chain_id : str The new chain ID. Yields ------ str (line-by-line) The modified (or not) PDB line. """ _pad_line = pad_line records = ('ATOM', 'HETATM', 'TER', 'ANISOU') for line in fhandle: if line.startswith(records): line = _pad_line(line) yield line[:21] + chain_id + line[22:] else: yield line alter_chain = run def main(): # Check Input pdbfh, chain = check_input(sys.argv[1:]) # Do the job new_pdb = run(pdbfh, chain) try: _buffer = [] _buffer_size = 5000 # write N lines at a time for lineno, line in enumerate(new_pdb): if not (lineno % _buffer_size): sys.stdout.write(''.join(_buffer)) _buffer = [] _buffer.append(line) sys.stdout.write(''.join(_buffer)) sys.stdout.flush() except IOError: # This is here to catch Broken Pipes # for example to use 'head' or 'tail' without # the error message showing up pass # last line of the script # We can close it even if it is sys.stdin pdbfh.close() sys.exit(0) if __name__ == '__main__': main() pdb-tools-2.7.0/pdbtools/pdb_chainbows.py000066400000000000000000000106061521210715700204310ustar00rootroot00000000000000#!/usr/bin/env python # -*- coding: utf-8 -*- # # Copyright 2020 João Pedro Rodrigues # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. """ Renames chain identifiers sequentially, based on TER records. Since HETATM records are not separated by TER records and usually come together at the end of the PDB file, this script will attempt to reassign their chain identifiers based on the changes it made to ATOM lines. This might lead to bad output in certain corner cases. Usage: python pdb_chainbows.py Example: python pdb_chainbows.py 1CTF.pdb This program is part of the `pdb-tools` suite of utilities and should not be distributed isolatedly. The `pdb-tools` were created to quickly manipulate PDB files using the terminal, and can be used sequentially, with one tool streaming data to another. They are based on old FORTRAN77 code that was taking too much effort to maintain and compile. RIP. """ import os import string import sys __author__ = "Joao Rodrigues" __email__ = "j.p.g.l.m.rodrigues@gmail.com" def check_input(args): """Checks whether to read from stdin/file and validates user input/options. """ # Defaults fh = sys.stdin # file handle if not len(args): # Reading from pipe with default option if sys.stdin.isatty(): sys.stderr.write(__doc__) sys.exit(1) elif len(args) == 1: if not os.path.isfile(args[0]): emsg = 'ERROR!! File not found or not readable: \'{}\'\n' sys.stderr.write(emsg.format(args[0])) sys.stderr.write(__doc__) sys.exit(1) fh = open(args[0], 'r') else: # Whatever ... emsg = 'ERROR!! Script takes 1 argument, not \'{}\'\n' sys.stderr.write(emsg.format(len(args))) sys.stderr.write(__doc__) sys.exit(1) return fh def run(fhandle): """ Set chains sequentially based on existing TER records. Follow sequence [ABC...abc...012...]. This function is a generator. Parameters ---------- fhandle : an iterable giving the PDB file line-by-line Yields ------ str (line-by-line) The modified (or not) PDB line. """ chainlist = list( string.digits[::-1] + string.ascii_lowercase[::-1] + string.ascii_uppercase[::-1] ) # 987...zyx...cbaZYX...BCA. max_chains = len(chainlist) chain_map = {} # for HETATM. curchain = chainlist.pop() records = ('ATOM', 'TER', 'ANISOU') for line in fhandle: if line.startswith(records): chain_map[line[21]] = curchain line = line[:21] + curchain + line[22:] if line.startswith('TER'): try: curchain = chainlist.pop() except IndexError: emsg = 'ERROR!! Structure contains more than {} TER records.\n' sys.stderr.write(emsg.format(max_chains)) sys.stderr.write(__doc__) sys.exit(1) elif line.startswith('HETATM'): hetchain = chain_map[line[21]] line = line[:21] + hetchain + line[22:] yield line set_chain_sequence = run def main(): # Check Input pdbfh = check_input(sys.argv[1:]) # Do the job new_pdb = run(pdbfh) try: _buffer = [] _buffer_size = 5000 # write N lines at a time for lineno, line in enumerate(new_pdb): if not (lineno % _buffer_size): sys.stdout.write(''.join(_buffer)) _buffer = [] _buffer.append(line) sys.stdout.write(''.join(_buffer)) sys.stdout.flush() except IOError: # This is here to catch Broken Pipes # for example to use 'head' or 'tail' without # the error message showing up pass # last line of the script # We can close it even if it is sys.stdin pdbfh.close() sys.exit(0) if __name__ == '__main__': main() pdb-tools-2.7.0/pdbtools/pdb_chainxseg.py000066400000000000000000000073441521210715700204320ustar00rootroot00000000000000#!/usr/bin/env python # -*- coding: utf-8 -*- # # Copyright 2018 João Pedro Rodrigues # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. """ Swaps the segment identifier for the chain identifier. Usage: python pdb_chainxseg.py Example: python pdb_chainxseg.py 1CTF.pdb This program is part of the `pdb-tools` suite of utilities and should not be distributed isolatedly. The `pdb-tools` were created to quickly manipulate PDB files using the terminal, and can be used sequentially, with one tool streaming data to another. They are based on old FORTRAN77 code that was taking too much effort to maintain and compile. RIP. """ import os import sys __author__ = "Joao Rodrigues" __email__ = "j.p.g.l.m.rodrigues@gmail.com" def check_input(args): """Checks whether to read from stdin/file and validates user input/options. """ # Defaults fh = sys.stdin # file handle if not len(args): # Reading from pipe if sys.stdin.isatty(): sys.stderr.write(__doc__) sys.exit(1) elif len(args) == 1: # Reading from file if not os.path.isfile(args[0]): emsg = 'ERROR!! File not found or not readable: \'{}\'\n' sys.stderr.write(emsg.format(args[0])) sys.stderr.write(__doc__) sys.exit(1) fh = open(args[0], 'r') else: # Whatever ... emsg = 'ERROR!! Script takes 1 argument, not \'{}\'\n' sys.stderr.write(emsg.format(len(args))) sys.stderr.write(__doc__) sys.exit(1) return fh def pad_line(line): """Helper function to pad line to 80 characters in case it is shorter""" size_of_line = len(line) if size_of_line < 80: padding = 80 - size_of_line + 1 line = line.strip('\n') + ' ' * padding + '\n' return line[:81] # 80 + newline character def run(fhandle): """ Replace the segment identifier with the contents of the chain identifier. Acts on ATOM/HETATM/ANISOU. This function is a generator. Parameters ---------- fhandle : a line-by-line iterator of the original PDB file. Yields ------ str (line-by-line) The modified (or not) PDB line. """ _pad_line = pad_line records = ('ATOM', 'HETATM', 'ANISOU') for line in fhandle: if line.startswith(records): line = _pad_line(line) yield line[:72] + line[21].ljust(4) + line[76:] else: yield line place_chain_on_seg = run def main(): # Check Input pdbfh = check_input(sys.argv[1:]) # Do the job new_pdb = run(pdbfh) try: _buffer = [] _buffer_size = 5000 # write N lines at a time for lineno, line in enumerate(new_pdb): if not (lineno % _buffer_size): sys.stdout.write(''.join(_buffer)) _buffer = [] _buffer.append(line) sys.stdout.write(''.join(_buffer)) sys.stdout.flush() except IOError: # This is here to catch Broken Pipes # for example to use 'head' or 'tail' without # the error message showing up pass # last line of the script # We can close it even if it is sys.stdin pdbfh.close() sys.exit(0) if __name__ == '__main__': main() pdb-tools-2.7.0/pdbtools/pdb_chkensemble.py000066400000000000000000000122421521210715700207320ustar00rootroot00000000000000#!/usr/bin/env python # -*- coding: utf-8 -*- # # Copyright 2018 João Pedro Rodrigues # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. """ Checks all models in a multi-model PDB file have the same composition. Composition is defined as same atoms/residues/chains. Usage: python pdb_chkensemble.py Example: python pdb_chkensemble.py 1CTF.pdb This program is part of the `pdb-tools` suite of utilities and should not be distributed isolatedly. The `pdb-tools` were created to quickly manipulate PDB files using the terminal, and can be used sequentially, with one tool streaming data to another. They are based on old FORTRAN77 code that was taking too much effort to maintain and compile. RIP. """ import itertools import os import sys __author__ = "Joao Rodrigues" __email__ = "j.p.g.l.m.rodrigues@gmail.com" def check_input(args): """Checks whether to read from stdin/file and validates user input/options. """ # Defaults fh = sys.stdin # file handle if not len(args): # Reading from pipe with default option if sys.stdin.isatty(): sys.stderr.write(__doc__) sys.exit(1) elif len(args) == 1: if not os.path.isfile(args[0]): emsg = 'ERROR!! File not found or not readable: \'{}\'\n' sys.stderr.write(emsg.format(args[0])) sys.stderr.write(__doc__) sys.exit(1) fh = open(args[0], 'r') else: # Whatever ... emsg = 'ERROR!! Script takes 1 argument, not \'{}\'\n' sys.stderr.write(emsg.format(len(args))) sys.stderr.write(__doc__) sys.exit(1) return fh def run(fhandle): """ Check if the ensemble is valid. - Same atoms in each model - Paired MODEL/ENDMDL tags Parameters ---------- fhandle : a line-by-line iterator of the original PDB file. Returns ------- int 1 if an error was found. 0 if no errors are found. """ model_open = False model_no = None model_data = {} # list of sets records = ('ATOM', 'HETATM', 'ANISOU', 'TER') for lineno, line in enumerate(fhandle): if line.startswith('MODEL'): if model_open: emsg = 'ERROR!! MODEL record found before ENDMDL at line \'{}\'\n' sys.stderr.write(emsg.format(lineno)) return 1 model_open = True model_no = int(line[10:14]) model_data[model_no] = set() elif line.startswith('ENDMDL'): if not model_open: emsg = 'ERROR!! ENDMDL record found before MODEL at line \'{}\'\n' sys.stderr.write(emsg.format(lineno)) return 1 model_open = False model_no = None # will fail to add lines if a new model is not open elif line.startswith(records): if not model_open: emsg = 'ERROR!! MODEL record missing before ATOM at line \'{}\'\n' sys.stderr.write(emsg.format(lineno)) return 1 atom_uid = line[6:27] model_data[model_no].add(atom_uid) else: if model_open: # Missing last ENDMDL emsg = 'ERROR!! ENDMDL record missing at line \'{}\'\n' sys.stderr.write(emsg.format(lineno)) return 1 # Verify all models have the same atoms bad_ensemble = False model_no_list = list(model_data.keys()) for model_i, model_j in itertools.combinations(model_no_list, 2): atoms_i = model_data[model_i] atoms_j = model_data[model_j] difference_ij = atoms_i - atoms_j difference_ji = atoms_j - atoms_i if difference_ij or difference_ji: bad_ensemble = True msg = 'Models {} and {} differ:\n' sys.stderr.write(msg.format(model_i, model_j)) if len(difference_ij): d_ij = sorted(difference_ij) msg = 'Atoms in model {} only:\n' sys.stderr.write(msg.format(model_i)) sys.stderr.write('\n'.join(d_ij)) if len(difference_ji): d_ji = sorted(difference_ji) msg = 'Atoms in model {} only:\n' sys.stderr.write(msg.format(model_j)) sys.stderr.write('\n'.join(d_ji)) if not bad_ensemble: n_models = len(model_data) msg = 'Ensemble of {} models *seems* OK\n' sys.stdout.write(msg.format(n_models)) return 0 return 1 check_ensemble = run def main(): # Check Input pdbfh = check_input(sys.argv[1:]) # Do the job status_code = check_ensemble(pdbfh) pdbfh.close() sys.exit(status_code) if __name__ == '__main__': main() pdb-tools-2.7.0/pdbtools/pdb_delchain.py000066400000000000000000000121211521210715700202150ustar00rootroot00000000000000#!/usr/bin/env python # -*- coding: utf-8 -*- # # Copyright 2018 João Pedro Rodrigues # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. """ Deletes all atoms matching specific chains in the PDB file. Usage: python pdb_delchain.py -