Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: for establishing transcripts file identity #23

Open
NDHall opened this issue Oct 28, 2021 · 0 comments
Open

Suggestion: for establishing transcripts file identity #23

NDHall opened this issue Oct 28, 2021 · 0 comments

Comments

@NDHall
Copy link

NDHall commented Oct 28, 2021

First of all, this has been a great pipeline. I appreciate the obvious thought and work you have already invested in it.
While working with the code I go this error:

Loaded degradome density data from file Some.fa_dd.txt
	Transcriptome: ppv01_70/Those_transcripts.fasta
Loaded GSTAr alignment file Query.fasta_GSTAr.txt
	Transcriptome: Those.fasta
	Queries: Query.fasta
	Ranked by: MFEratio

FATAL: Transcriptome has to be the same for the degradome density file and the GSTAr alignment file!

I appreciate the spirit of Error, but in this case both files were the same even though their relative paths were different. I was able to fix this without re-running the GSTAr step, but it occurs to me that this problem could be side stepped entirely by using MD5 Checksum values. If implemented, when transcriptomes are processed they would be fed to MD5 Hash, Digested and the resulting values printed back to the header. The Transcripts field would then read

# Transcripts: 202cb962ac59075b964b07152d234b70

since the hash is created from file contents it frees the program to take in correct transcript files no matter where they are stored.

Again, great program! Keep up the good work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant