Supported Input Formats¶
There are many different programs that utilize a gff or gtf style format. Each has its own inclusion rules and formatting guidelines. Therefore, a true universal gff/gff3/gtf file converter that requires no user input may be an impossible task. gFACs requires the user to define the application source and version. If you do not find you input format, look into the support script format_diagnosis.pl. If your file is made up of many different formats merged together, I suggest breaking it apart. If you want a format added (especially if it is a well-known one) let me know and I will likely create one!
The format is specified in the gFACs command by a -f [code] flag. It is a mandatory flag and the code will fail without it. These codes are listed out below with notes and can also be seen in the command line manual. For an example of the command with a proper format flag, see any of the sample runs!
- Braker format augustus.gff/gff3/gft:
braker_2.1.2_gtf - Works for 2.1.0-2.1.5
- Braker format braker.gtf:
Maker may provide other information such as blastx and protein2genome information. Currently, only maker models of genes and exons will be considered.
You can input a gene table from gFACs, any version. However, the prefix on the input will NOT be retained.
refseq_gff - only CDS taken.
For those who are curious, each format has a special conversion script that transitions the input into the gene table. These are the scripts found in the format_scripts folder that comes along with gFACs. If you are feeling adventurous, you can make your own conversion script that creates the gene table and simply run gFACs with the gene table format code.