The rpkm files in executables/source/rpkm.tar from commit
https://github.com/hallamlab/metapathways2/commit/a7a826ce4437ac78af1f58162ecbf0342193ac3a are completely unusable. Instead of the actual ORF names (as provided by the GFF file) the "ORF" name is really the contig name with a _(contig number - 1) appended to it. For example, say you have a contig named sampleG_13 and in the GFF file there are 3 ORFs attributed to that contig: sampleG_13_1, sampleG_13_2, sampleG_13_3. The output would only contain a RPKM value for sampleG_13_12 (which doesn't exist).
Hey,
The rpkm files in executables/source/rpkm.tar from commit https://github.com/hallamlab/metapathways2/commit/a7a826ce4437ac78af1f58162ecbf0342193ac3a are completely unusable. Instead of the actual ORF names (as provided by the GFF file) the "ORF" name is really the contig name with a _(contig number - 1) appended to it. For example, say you have a contig named sampleG_13 and in the GFF file there are 3 ORFs attributed to that contig: sampleG_13_1, sampleG_13_2, sampleG_13_3. The output would only contain a RPKM value for sampleG_13_12 (which doesn't exist).
The version in commit https://github.com/hallamlab/metapathways2/commit/5b9b9bf2e216bf9cc21eb7e585a6bb2be9d89a4d does seem to be working fine though, apart from the buffer-overflow, memory-leak and command-line interface issues addressed in the following commit.