pedronachtigall / CodAn

CDS prediction in transcripts
Other
23 stars 5 forks source link

Your software is too dependent and hard to install #5

Closed Trandamere closed 4 years ago

Trandamere commented 4 years ago

version GLIBC_2.15 not found

Trandamere commented 4 years ago

./tops-viterbi_decoding: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by ./tops-viterbi_decoding) ./tops-viterbi_decoding: /lib64/libstdc++.so.6: versionGLIBCXX_3.4.21' not found (required by ./tops-viterbi_decoding)

ayoshiaki commented 4 years ago

Hi Trandamere,

I am really sorry that our software is hard to install. I agree that we need to simplify the installation requirements.

To solve your problem, you can try the solution described at Stack Overflow:

https://stackoverflow.com/questions/16605623/where-can-i-get-a-copy-of-the-file-libstdc-so-6-0-15

Best regards, André.

Trandamere commented 4 years ago
FG4G37170T4 CodAn   CDS 114 404  -584.01    +   0   gene_id "CodAn.1"; transcript_id "CodAn.1";

Can you output my gene number and chromosome number as it is? This will bring a lot of trouble to the follow-up analysis

ayoshiaki commented 4 years ago

Can you give me a small sample of your input file and the output you need?

pedronachtigall commented 4 years ago

Dear @Trandamere,

You did not provide the differences from the id in your input fasta and the id present at CodAn output. But I believe such differences may be related to the presence of a "space" (" ") in the fasta header. In fasta format, all the content after the "space" is considered the description and is not included as the sequence id. So, if you want that all content present in the fasta header represents your sequence id ("gene number and chromosome number as it is"). Please, change the "space" to other characters such as "underscore" ("_"), "dot" (".") or "pipe" ("|"). Choice the one that will be better for your downstream analysis.

You can easily do it by using the "sed" command at your terminal:

Let us know if your have any other issues regarding CodAn usage.

Best regards, Pedro

Trandamere commented 4 years ago

Hi Pedro: I have solved this problem, thank you very much.