Skip to content

Latest commit

 

History

History
48 lines (33 loc) · 2.62 KB

README.md

File metadata and controls

48 lines (33 loc) · 2.62 KB

Documentation Status Pypi Downloads Stars

AltAnalyze 3

AltAnalyze3 is an advanced Python3 workflow for long-read (LR) and short read splicing analysis. The software can integrate results across single-cell and bulk technological platforms, aligning to a common gene model for splice junction- (MultiPath-PSI) and isoform-based analyses (TPM or ratio). Both supervised and unsupervised (splice-ICGS) analyses are supported. Workflows can be run in a fully automated manner with or step-by-step with extensive customization. See tutorials for examples or the https://altanalyze.org.

schema

Tutorials and Installation

Read the full documentation. AltAnalyze 3 has been tested in python>=3.11 on MacOS and Linux. To install:

pip install AltAnalyze3

The source code is in src folder

The documentation is in doc folder

The testing examples and code are in test folder

Contribution rules

If you are a member of the development team, to contribute, please follow the steps below:

# if you haven't cloned before
git clone https://github.com/SalomonisLab/altanalyze3.git
git checkout -b <your_branch_name>  # please replace "frank" with your token
# if you already have the local repository
git checkout main
git pull origin main
# do the same things for your branch as well
git checkout <your_branch_name>
git pull origina <your_branch_name>
# then make the changes in your branch locally, after finished, push them to the correpsonding branch on GitHub
git push origin HEAD:<your_branch_name>

Then, on the GitHub, go to your branch, and click contribute, issue a pull request with clear messages on what you have changed. Then the managers will review your pull requests and deciding whether to merge to the main branch or not (At each standing meeting).

If you are not a member of development team, to contribute, please follow the steps below:

  1. fork the repository to your account
  2. make the changes in your forked repository
  3. create a pull request
  4. the managers will review your codes and decide how to merge into the main branch (At each standing meeting)