This repository contains code originally developed by Adam English for his article
- Prevalence of alternative splicing choices in Arabidopsis thaliana (2010)
The original article used EST alignments to assess support for alternative splicing variants documented in Arabidospis gene model annotations. The major result of the article was that for most annotated alternative splicing events, one form predominates. Also, when alternative splicing was more frequently observed, it tended to avoid the protein-coding region of genes. However, there were some genes that were highly variable in terms of splicing. These tended to encode genes with function related to splicing or RNA.
Later, we expanded the code base to use RNA-Seq alignments from multiple libraries to report support for annotated alternative splicing choices.
Processing RNA-Seq data for splicing support
- Gene model annotations in BED12 or BED14 format. For examples, see IgbQuickload.org
- Field 4 must contain gene model identifiers that use LOCUS.n naming convention; AltSpliceanalysis uses these identifiers to determine which transcripts belong to which genes
- Junction files generated by tophat or Loraine Lab find_junctions program, one per library
- RNA-Seq alignments in BAM format, one per libary
For an example invocation, see:
- Ann Loraine (email@example.com)
Copyright (c) University of North Carolina at Charlotte
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Also, see: http://opensource.org/licenses/MIT