-
Notifications
You must be signed in to change notification settings - Fork 118
/
rsem-generate-ngvector
executable file
·104 lines (57 loc) · 3.39 KB
/
rsem-generate-ngvector
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
#!/usr/bin/env perl
use Getopt::Long;
use Pod::Usage;
use FindBin;
use lib $FindBin::RealBin;
use rsem_perl_utils;
use Env qw(@PATH);
@PATH = ("$FindBin::RealBin/EBSeq", @PATH);
use strict;
my $k = 25;
my $help = 0;
GetOptions("k=i" => \$k,
"h|help" => \$help) or pod2usage(-exitval => 2, -verbose => 2);
pod2usage(-verbose => 2) if ($help == 1);
pod2usage(-msg => "Invalid number of arguments!", -exitval => 2, -verbose => 2) if (scalar(@ARGV) != 2);
my $command = "";
$command = "rsem-for-ebseq-calculate-clustering-info $k $ARGV[0] $ARGV[1].ump";
&runCommand($command);
$command = "rsem-for-ebseq-generate-ngvector-from-clustering-info $ARGV[1].ump $ARGV[1].ngvec";
&runCommand($command);
__END__
=head1 NAME
rsem-generate-ngvector - Create Ng vector for EBSeq based only on transcript sequences.
=head1 SYNOPSIS
rsem-generate-ngvector [options] input_fasta_file output_name
=head1 ARGUMENTS
=over
=item B<input_fasta_file>
The fasta file containing all reference transcripts. The transcripts must be in the same order as those in expression value files. Thus, 'reference_name.transcripts.fa' generated by 'rsem-prepare-reference' should be used.
=item B<output_name>
The name of all output files. The Ng vector will be stored as 'output_name.ngvec'.
=back
=head1 OPTIONS
=over
=item B<-k> <int>
k mer length. See description section. (Default: 25)
=item B<-h/--help>
Show help information.
=back
=head1 DESCRIPTION
This program generates the Ng vector required by EBSeq for isoform level differential expression analysis based on reference sequences only. EBSeq can take variance due to read mapping ambiguity into consideration by grouping isoforms with parent gene's number of isoforms. However, for de novo assembled transcriptome, it is hard to obtain an accurate gene-isoform relationship. Instead, this program groups isoforms by using measures on read mappaing ambiguity directly. First, it calculates the 'unmappability' of each transcript. The 'unmappability' of a transcript is the ratio between the number of k mers with at least one perfect match to other transcripts and the total number of k mers of this transcript, where k is a parameter. Then, Ng vector is generated by applying Kmeans algorithm to the 'unmappability' values with number of clusters set as 3. 'rsem-generate-ngvector' will make sure the mean 'unmappability' scores for clusters are in ascending order. All transcripts whose lengths are less than k are assigned to cluster 3.
If your reference is a de novo assembled transcript set, you should run 'rsem-generate-ngvector' first. Then load the resulting 'output_name.ngvec' into R. For example, you can use
NgVec <- scan(file="output_name.ngvec", what=0, sep="\n")
. After that, replace 'IsoNgTrun' with 'NgVec' in the second line of section 3.2.5 (Page 10) of EBSeq's vignette:
IsoEBres=EBTest(Data=IsoMat, NgVector=NgVec, ...)
This program only needs to run once per RSEM reference.
=head1 OUTPUT
=over
=item B<output_name.ump>
'unmappability' scores for each transcript. This file contains two columns. The first column is transcript name and the second column is 'unmappability' score.
=item B<output_name.ngvec>
Ng vector generated by this program.
=back
=head1 EXAMPLES
Suppose the reference sequences file is '/ref/mouse_125/mouse_125.transcripts.fa' and we set the output_name as 'mouse_125':
rsem-generate-ngvector /ref/mouse_125/mouse_125.transcripts.fa mouse_125
=cut