pstrope
commented
1 month ago Hi,
Please look at the docs where it says:
- If you are using your local reads, then the FASTA/FASTQ headers need to be in the following format:
Closed Artifice120 closed 1 month ago
pstrope
commented
1 month ago Hi,
Please look at the docs where it says:
- If you are using your local reads, then the FASTA/FASTQ headers need to be in the following format:
pstrope
commented
1 month ago @Artifice120 We will look into the part where a gff file was not produced, and yet it was called "completed". Thank you for reporting. Pooja
Artifice120
commented
1 month ago I see,
Sorry I thought that it was referring to allowing @ or > in header.
Will parse headers with sed and awk and update you later.
Is it okay if I use the raw sequencer prefix "AS131" as the prefix for the file and header names or does it have to be a valid SRR ID ?
Thanks.
pstrope
commented
1 month ago Raw sequencer prefix is OK, and does not have to be a valid SRR id.
My colleague says your headers should have worked. Maybe try with '@' instead of > in your fastq first?
Artifice120
commented
1 month ago It was the '>' symbol that was giving it issues.
The headers were originally '@' must have swapped it out earlier.
It is running fine now.
Thanks.
Artifice120
commented
1 month ago Once again the e-gapx results seem to be better than my Braker results having the same Busco completeness score (98.1) but with half the amount of predicted genes which is much closer to the expected value.
Afternoon,
After running egapx with local rna seq reads I received the following completion message.
However;
These are the outputs
When I use the resume.sh command I just get the same completion message immediately.
This is the YAML file I used
this is the format of the rna-seq reads I used
Many thanks,
Joseph T