anvi-script-gen-user-module-file

This script generates a user-defined module file from a tab-delimited file of enzymes and other input parameters..

🔙 To the main page of anvi’o programs and artifacts.

Authors

Iva Veseli

EmailTwitterGithub

Can consume

enzymes-list-for-module

Can provide

user-modules-data

Usage

Given an enzymes-list-for-module file, this script will produce a properly-formatted module file for use in anvi-setup-user-modules.

Basics

You should provide this script with an accession ID for your module (which will become the module file name) (-I); a name for the module (-n); a categorization which includes module class, category, and sub-category separated by semicolons (-c); an enzymes-list-for-module file listing the component enzymes, their annotation sources, and their functions (-e); and a definition which puts these enzymes in the proper order (-d):

Then this script will produce a properly-formatted module file, which in this case would be called UD0023 and would look like this (see enzymes-list-for-module for the example file containing these enzymes):

ENTRY       UD0023
NAME        Frankenstein pathway for demo purposes
DEFINITION  K01657+K01658 PF06603.14,(COG1362 TIGR01709.2)
ORTHOLOGY   K01657  anthranilate synthase component I [EC:4.1.3.27]
            K01658  anthranilate synthase component II [EC:4.1.3.27]
            PF06603.14  UpxZ
            COG1362  Aspartyl aminopeptidase
            TIGR01709.2  type II secretion system protein GspL
CLASS       User modules; Demo set; Frankenstein metabolism
ANNOTATION_SOURCE  K01657  KOfam
                   K01658  KOfam
                   PF06603.14  METABOLISM_HMM
                   COG1362  COG20_FUNCTION
                   TIGR01709.2  TIGRFAM
\\\

Automatically generating the module definition

The module definition parameter is not required, and if you do not provide one, the definition will be generated with each enzyme in the input file as a different ‘step’ of the module. This option may be especially appropriate for generating what KEGG calls “signature modules”, in which each enzyme is not technically part of a metabolic pathway, but instead the module represents a functionally-related set of enzymes (like all tRNA modification enzymes, for instance).

Here is an example command without the definition parameter:

And here is the module file that this would produce:

ENTRY       UD0023
NAME        Frankenstein pathway for demo purposes
DEFINITION  K01657 K01658 PF06603.14 COG1362 TIGR01709.2
ORTHOLOGY   K01657  anthranilate synthase component I [EC:4.1.3.27]
            K01658  anthranilate synthase component II [EC:4.1.3.27]
            PF06603.14  UpxZ
            COG1362  Aspartyl aminopeptidase
            TIGR01709.2  type II secretion system protein GspL
CLASS       User modules; Demo set; Frankenstein metabolism
ANNOTATION_SOURCE  K01657  KOfam
                   K01658  KOfam
                   PF06603.14  METABOLISM_HMM
                   COG1362  COG20_FUNCTION
                   TIGR01709.2  TIGRFAM
\\\

Edit this file to update this information.

Additional Resources

Are you aware of resources that may help users better understand the utility of this program? Please feel free to edit this file on GitHub. If you are not sure how to do that, find the __resources__ tag in this file to see an example.