-
Notifications
You must be signed in to change notification settings - Fork 2
Use standalone version
Vinh Tran edited this page Sep 23, 2020
·
4 revisions
h1s will run smoothly with the provided sample input file infile.fa if everything is set correctly.
h1s --seqFile infile.fa --seqName test --refspec HUMAN@9606@3
The output files with the prefix test will be saved at your current working directory.
You can have an overview about the available options with the command
h1s -h
The output consist of these text files (note: test is your defined -seqName parameter)
-
test.extended.fa: a multiple FASTA file containing ortholog sequences and the query gene -
test.extended.profile: a tab-delimited file containing list of orthologous sequences and their correspoding similarity scores by comparing their feature architectures with the one of the query gene (for more info about this score, please read this document) -
test.phyloprofile: an input file for visualisation the phylogenetic profile of the query gene using PhyloProfile tool -
test_forward.domainsandtest_reverse.domains: a protein domain annotation file for all the sequences present in the orthologous group. The_forwardor_reversesuffix indicates the direction of the feature architecture comparison, in which_forwardmeans that the query gene is used as seed and it orthologs as target for the comparison, while_reverseis vice versa.
To run h1s with multiple seed sequences, one can use hms function:
hms --input /seed/folder --jobName test --refspec HUMAN@9606@3
The only difference in the options of hms and h1s is instead of --seqFile, hms takes a folder that contains multiple seed proteins as input that specified with --input, and the output files will be named based on the job name that is defined by --jobName. Other options as well as the output files are the same as h1s function.