Differences

This shows you the differences between two versions of the page.

--- functional_annotation_with_the_funannotate_pipeline [2025/01/28 10:29] – 134.190.225.16
+++ functional_annotation_with_the_funannotate_pipeline [2025/12/09 13:02] (current) – [EggNOG mapping] 134.190.190.181
@@ Line 12: / Line 12: @@
 In my experience it was easiest to do a separate InterProScan search, EggNOG mapping and SignalP prediction, and then pointing to each of these resulting outfiles in the final ''funannotate annotate'' step.
+**Important note!!!**
+Before proceeding you need to check your gff3 file for errors by running ''validate_gene_models_in_gff3.py''. (Activate the gffutils environment to run this script, you may also have to comment out the ''import regex as re'' line if you're not checking Blastocystis genomes.
+This script will locate errors in your gff3 file that often occur due to manual editing (premature stop codons, incorrect exon numbering, missing start and stop codons, start or stop location not matching exon location, etc).  Incorrect phase designation for an exon can lead to premature stop codons so keep that in mind when looking for causes of premature stops.
 ==== Pre-step to prepare files =====
 To get the results from InterProScan, EggNOG mapper and SignalP to integrate into funannotate annotate results you need to prepare the gff3 file and protein data using the two funannotate scripts below
-**Important note!!!**
-Before proceeding you need to check your gff3 file for errors by running validate_gene_models_in_gff3.py
-This script will locate errors in your gff3 file that often occur due to manual editing (premature stop codons, incorrect exon numbering, missing start and stop codons, start or stop location not matching exon location, etc).  Incorrect phase designation for an exon can lead to premature stop codons so keep that in mind when looking for cause of premature stops.
@@ Line 96: / Line 97: @@
 #$ -cwd
 #$ -q 256G-batch
-#$ -m bea
-#$ -M joran.martijn@dal.ca
 #$ -pe threaded 40