[med-svn] [Git][med-team/tigr-glimmer][master] 12 commits: Update changelog
Andreas Tille
gitlab at salsa.debian.org
Wed Apr 29 22:11:08 BST 2020
Andreas Tille pushed to branch master at Debian Med / tigr-glimmer
Commits:
5b1d5d30 by Andreas Tille at 2020-04-29T22:53:08+02:00
Update changelog
- - - - -
a47d0776 by Andreas Tille at 2020-04-29T22:53:36+02:00
routine-update: Standards-Version: 4.5.0
- - - - -
d93b430f by Andreas Tille at 2020-04-29T22:53:36+02:00
routine-update: debhelper-compat 12
- - - - -
622d8716 by Andreas Tille at 2020-04-29T22:53:39+02:00
routine-update: Secure URI in copyright format
- - - - -
a2ba7cef by Andreas Tille at 2020-04-29T22:53:40+02:00
routine-update: Add salsa-ci file
- - - - -
15856173 by Andreas Tille at 2020-04-29T22:53:40+02:00
routine-update: Rules-Requires-Root: no
- - - - -
0e1938cb by Andreas Tille at 2020-04-29T22:53:40+02:00
Trim trailing whitespace.
Fixes: lintian: file-contains-trailing-whitespace
See-also: https://lintian.debian.org/tags/file-contains-trailing-whitespace.html
- - - - -
5bb908e5 by Andreas Tille at 2020-04-29T22:53:41+02:00
Wrap long lines in changelog entries: 2.13-1.
Fixes: lintian: debian-changelog-line-too-long
See-also: https://lintian.debian.org/tags/debian-changelog-line-too-long.html
- - - - -
6489285e by Andreas Tille at 2020-04-29T22:53:42+02:00
Refer to specific version of license GPL-2+.
Fixes: lintian: copyright-refers-to-symlink-license
See-also: https://lintian.debian.org/tags/copyright-refers-to-symlink-license.html
Fixes: lintian: copyright-refers-to-versionless-license-file
See-also: https://lintian.debian.org/tags/copyright-refers-to-versionless-license-file.html
- - - - -
b35cc019 by Andreas Tille at 2020-04-29T23:01:19+02:00
Do not use docbook-to-man to create manpages
- - - - -
08d2715c by Andreas Tille at 2020-04-29T23:05:11+02:00
Rename debian/NEWS.Debian to NEWS
- - - - -
7cbfcda3 by Andreas Tille at 2020-04-29T23:09:37+02:00
Fix syntax in debian/NEWS
- - - - -
22 changed files:
- + debian/NEWS
- − debian/NEWS.Debian
- debian/changelog
- − debian/compat
- debian/control
- debian/copyright
- + debian/glimmer2_mans/tigr-anomaly.1
- − debian/glimmer2_mans/tigr-anomaly.sgml
- + debian/glimmer2_mans/tigr-build-icm.1
- − debian/glimmer2_mans/tigr-build-icm.sgml
- + debian/glimmer2_mans/tigr-extract.1
- − debian/glimmer2_mans/tigr-extract.sgml
- debian/tigr-glimmer.1 → debian/glimmer2_mans/tigr-glimmer.1
- + debian/glimmer2_mans/tigr-glimmer3.1
- − debian/glimmer2_mans/tigr-glimmer3.sgml
- + debian/glimmer2_mans/tigr-long-orfs.1
- − debian/glimmer2_mans/tigr-long-orfs.sgml
- + debian/glimmer2_mans/tigr-run-glimmer3.1
- − debian/glimmer2_mans/tigr-run-glimmer3.sgml
- debian/manpages
- debian/rules
- + debian/salsa-ci.yml
Changes:
=====================================
debian/NEWS
=====================================
@@ -0,0 +1,6 @@
+tigr-glimmer (2.13-1) unstable; urgency=low
+
+ With version 2.13-1, the binaries and man pages all have a prefix "tigr-"
+ to avoid conflicts with other programs, with extract in particular.
+
+ -- Steffen Moeller <moeller at pzr.uni-rostock.de> Wed, 10 Nov 2004 11:58:46 +0100
=====================================
debian/NEWS.Debian deleted
=====================================
@@ -1,5 +0,0 @@
-With version 2.13-1, the binaries and man pages all have a prefix "tigr-"
-to avoid conflicts with other programs, with extract in particular.
-
- -- Steffen Moeller <moeller at pzr.uni-rostock.de>, Thu, 10 Nov 2004 17:33:46 +0100
-
=====================================
debian/changelog
=====================================
@@ -1,3 +1,25 @@
+tigr-glimmer (3.02b-3) unstable; urgency=medium
+
+ [ Steffen Möller ]
+ * Updated d/u/metadata
+
+ [ Nilesh Patra ]
+ * Add autopkgtests
+
+ [ Andreas Tille ]
+ * Standards-Version: 4.5.0 (routine-update)
+ * debhelper-compat 12 (routine-update)
+ * Secure URI in copyright format (routine-update)
+ * Add salsa-ci file (routine-update)
+ * Rules-Requires-Root: no (routine-update)
+ * Trim trailing whitespace.
+ * Wrap long lines in changelog entries: 2.13-1.
+ * Refer to specific version of license GPL-2+.
+ * Do not use docbook-to-man to create manpages
+ * Rename debian/NEWS.Debian to NEWS
+
+ -- Andreas Tille <tille at debian.org> Wed, 29 Apr 2020 22:53:42 +0200
+
tigr-glimmer (3.02b-2) unstable; urgency=medium
[ Helmut Grohne ]
@@ -104,7 +126,8 @@ tigr-glimmer (2.13-1.1) unstable; urgency=low
tigr-glimmer (2.13-1) unstable; urgency=low
* New upstream release - no significant changes for Linux users.
- * Resolves conflict for "extract" binary and man page (Closes:Bug#227790,Bug#274780).
+ * Resolves conflict for "extract" binary and man page
+ (Closes:Bug#227790,Bug#274780).
-- Steffen Moeller <moeller at pzr.uni-rostock.de> Wed, 10 Nov 2004 11:58:46 +0100
@@ -114,4 +137,3 @@ tigr-glimmer (2.12-1) unstable; urgency=low
* Added man pages to upstream release
-- Steffen Moeller <moeller at pzr.uni-rostock.de> Thu, 16 Oct 2003 17:33:46 +0200
-
=====================================
debian/compat deleted
=====================================
@@ -1 +0,0 @@
-11
=====================================
debian/control
=====================================
@@ -4,12 +4,12 @@ Uploaders: Steffen Moeller <moeller at debian.org>,
Andreas Tille <tille at debian.org>
Section: science
Priority: optional
-Build-Depends: debhelper (>= 11~),
- docbook-to-man
-Standards-Version: 4.1.4
+Build-Depends: debhelper-compat (= 12)
+Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/med-team/tigr-glimmer
Vcs-Git: https://salsa.debian.org/med-team/tigr-glimmer.git
Homepage: http://ccb.jhu.edu/software/glimmer/index.shtml
+Rules-Requires-Root: no
Package: tigr-glimmer
Architecture: any
=====================================
debian/copyright
=====================================
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: Glimmer
Upstream-Contact: Art Delcher <adelcher at tigr.org>,
Steven Salzberg <salzberg at tigr.org>
@@ -20,4 +20,4 @@ Copyright: © 2003-2004 Steffen Moeller <moeller at debian.org>
© 2008-2013 Andreas Tille <tille at debian.org>
License: GPL-2+
On Debian systems, the complete text of the GNU General
- Public License can be found in `/usr/share/common-licenses/GPL'.
+ Public License can be found in `/usr/share/common-licenses/GPL-2'.
=====================================
debian/glimmer2_mans/tigr-anomaly.1
=====================================
@@ -0,0 +1,32 @@
+.TH "TIGR-GLIMMER" "1"
+.SH "NAME"
+tigr-glimmer \(em The program lacks a description
+.SH "SYNOPSIS"
+.PP
+\fBtigr-anomaly\fR [>dna-file] [>coord-file]
+.SH "DESCRIPTION"
+.PP
+.SH "OPTIONS"
+.SH "SEE ALSO"
+.PP
+tigr-glimmer3 (1),
+tigr-adjust (1),
+tigr-anomaly (1),
+tigr-build-icm (1),
+tigr-check (1),
+tigr-codon-usage (1),
+tigr-compare-lists (1),
+tigr-extract (1),
+tigr-generate (1),
+tigr-get-len (1),
+tigr-get-putative (1),
+.PP
+http://www.tigr.org/software/glimmer/
+.PP
+Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.
+.SH "AUTHOR"
+.PP
+This manual page was quickly copied from the glimmer web site by Steffen Moeller moeller at debian.org for
+the \fBDebian\fP system.
+
+.\" created by instant / docbook-to-man
=====================================
debian/glimmer2_mans/tigr-anomaly.sgml deleted
=====================================
@@ -1,124 +0,0 @@
-<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-
-<!-- Process this file with docbook-to-man to generate an nroff manual
- page: `docbook-to-man manpage.sgml > manpage.1'. You may view
- the manual page with: `docbook-to-man manpage.sgml | nroff -man |
- less'. A typical entry in a Makefile or Makefile.am is:
-
-manpage.1: manpage.sgml
- docbook-to-man $< > $@
-
-
- The docbook-to-man binary is found in the docbook-to-man package.
- Please remember that if you create the nroff version in one of the
- debian/rules file targets (such as build), you will need to include
- docbook-to-man in your Build-Depends control field.
-
- -->
-
- <!-- Fill in your name for FIRSTNAME and SURNAME. -->
- <!ENTITY dhfirstname "<firstname>Steffen</firstname>">
- <!ENTITY dhsurname "<surname>Mller</surname>">
- <!-- Please adjust the date whenever revising the manpage. -->
- <!ENTITY dhdate "<date>November 10, 2004</date>">
- <!ENTITY dhsection "<manvolnum>1</manvolnum>">
- <!ENTITY dhemail "<email>moeller at debian.org</email>">
- <!ENTITY dhusername "Steffen Moeller">
- <!ENTITY dhucpackage "<refentrytitle>TIGR-GLIMMER</refentrytitle>">
- <!ENTITY dhpackage "tigr-glimmer">
-
- <!ENTITY debian "<productname>Debian</productname>">
- <!ENTITY gnu "<acronym>GNU</acronym>">
- <!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
-]>
-
-<refentry>
- <refentryinfo>
- <address>
- &dhemail;
- </address>
- <author>
- &dhfirstname;
- &dhsurname;
- </author>
- <copyright>
- <year>2003</year>
- <holder>&dhusername;</holder>
- </copyright>
- &dhdate;
- </refentryinfo>
- <refmeta>
- &dhucpackage;
-
- &dhsection;
- </refmeta>
- <refnamediv>
- <refname>&dhpackage;</refname>
-
- <refpurpose>
-The program lacks a description
-</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>tigr-anomaly</command>
- <arg>>dna-file</arg>
- <arg>>coord-file</arg>
- </cmdsynopsis>
- </refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
-<para>
-</para>
-
- </refsect1>
- <refsect1>
- <title>OPTIONS</title>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
- <para>
-tigr-glimmer3 (1),
-tigr-adjust (1),
-tigr-anomaly (1),
-tigr-build-icm (1),
-tigr-check (1),
-tigr-codon-usage (1),
-tigr-compare-lists (1),
-tigr-extract (1),
-tigr-generate (1),
-tigr-get-len (1),
-tigr-get-putative (1),
-</para>
-<para>
-http://www.tigr.org/software/glimmer/
-</para>
-
- <para>Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.</para>
- </refsect1>
- <refsect1>
- <title>AUTHOR</title>
-
- <para>This manual page was quickly copied from the glimmer web site by &dhusername; &dhemail; for
- the &debian; system.
- </para>
-
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:nil
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
=====================================
debian/glimmer2_mans/tigr-build-icm.1
=====================================
@@ -0,0 +1,80 @@
+.TH "TIGR-GLIMMER \fB(1)\fP " "1"
+.SH "NAME"
+tigr-glimmer \(em Creates and outputs an interpolated Markov model(IMM)
+.SH "SYNOPSIS"
+.PP
+\fBtigr-build-icm\fR
+.SH "DESCRIPTION"
+.PP
+Program build-icm.c creates and outputs an interpolated Markov
+model (IMM) as described in the paper
+A.L. Delcher, D. Harmon, S. Kasif, O. White, and S.L. Salzberg.
+Improved Microbial Gene Identification with Glimmer.
+Nucleic Acids Research, 1999, in press.
+Please reference this paper if you use the system as part of any
+published research.
+.PP
+Input comes from the file named on the command-line. Format should be
+one string per line. Each line has an ID string followed by white space
+followed by the sequence itself. The script run-glimmer3 generates
+an input file in the correct format using the 'extract' program.
+.PP
+The IMM is constructed as follows: For a given context, say
+acgtta, we want to estimate the probability distribution of the
+next character. We shall do this as a linear combination of the
+observed probability distributions for this context and all of
+its suffixes, i.e., cgtta, gtta, tta, ta, a and empty. By
+observed distributions I mean the counts of the number of
+occurrences of these strings in the training set. The linear
+combination is determined by a set of probabilities, lambda, one
+for each context string. For context acgtta the linear combination
+coefficients are:
+.PP
+lambda (acgtta)
+(1 \- lambda (acgtta)) x lambda (cgtta)
+(1 \- lambda (acgtta)) x (1 \- lambda (cgtta)) x lambda (gtta)
+(1 \- lambda (acgtta)) x (1 \- lambda (cgtta)) x (1 \- lambda (gtta)) x lambda (tta)
+(1 \- lambda (acgtta)) x (1 \- lambda (cgtta)) x (1 \- lambda (gtta))
+x (1 \- lambda (tta)) x (1 \- lambda (ta)) x (1 \- lambda (a))
+.PP
+We compute the lambda values for each context as follows:
+\- If the number of observations in the training set is >= the constant
+SAMPLE_SIZE_BOUND, the lambda for that context is 1.0
+\- Otherwise, do a chi-square test on the observations for this context
+compared to the distribution predicted for the one-character shorter
+suffix context.
+If the chi-square significance < 0.5, set the lambda for this context to 0.0
+Otherwise set the lambda for this context to:
+(chi-square significance) x (# observations) / SAMPLE_WEIGHT
+.PP
+To run the program:
+.PP
+build-icm <train.seq > train.model
+.PP
+This will use the training data in train.seq to produce the file
+train.model, containing your IMM.
+.SH "SEE ALSO"
+.PP
+tigr-glimmer3 (1),
+tigr-long-orfs (1),
+tigr-adjust (1),
+tigr-anomaly (1),
+tigr-extract (1),
+tigr-check (1),
+tigr-codon-usage (1),
+tigr-compare-lists (1),
+tigr-extract (1),
+tigr-generate (1),
+tigr-get-len (1),
+tigr-get-putative (1),
+
+.PP
+http://www.tigr.org/software/glimmer/
+.PP
+Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.
+.SH "AUTHOR"
+.PP
+This manual page was quickly copied from the glimmer web site and readme file by Steffen Moeller moeller at debian.org for
+the \fBDebian\fP system.
+
+.\" created by instant / docbook-to-man
=====================================
debian/glimmer2_mans/tigr-build-icm.sgml deleted
=====================================
@@ -1,162 +0,0 @@
-<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-
-<!-- Process this file with docbook-to-man to generate an nroff manual
- page: `docbook-to-man manpage.sgml > manpage.1'. You may view
- the manual page with: `docbook-to-man manpage.sgml | nroff -man |
- less'. A typical entry in a Makefile or Makefile.am is:
-
-manpage.1: manpage.sgml
- docbook-to-man $< > $@
-
-
- The docbook-to-man binary is found in the docbook-to-man package.
- Please remember that if you create the nroff version in one of the
- debian/rules file targets (such as build), you will need to include
- docbook-to-man in your Build-Depends control field.
-
- -->
-
- <!-- Fill in your name for FIRSTNAME and SURNAME. -->
- <!ENTITY dhfirstname "<firstname>Steffen</firstname>">
- <!ENTITY dhsurname "<surname>Möller</surname>">
- <!-- Please adjust the date whenever revising the manpage. -->
- <!ENTITY dhdate "<date>Novemver 10, 2004</date>">
- <!ENTITY dhsection "<manvolnum>1</manvolnum>">
- <!ENTITY dhemail "<email>moeller at debian.org</email>">
- <!ENTITY dhusername "Steffen Moeller">
- <!ENTITY dhucpackage "<refentrytitle>TIGR-GLIMMER<title>">
- <!ENTITY dhpackage "tigr-glimmer">
-
- <!ENTITY debian "<productname>Debian</productname>">
- <!ENTITY gnu "<acronym>GNU</acronym>">
- <!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
-]>
-
-<refentry>
- <refentryinfo>
- <address>
- &dhemail;
- </address>
- <author>
- &dhfirstname;
- &dhsurname;
- </author>
- <copyright>
- <year>2003</year>
- <holder>&dhusername;</holder>
- </copyright>
- &dhdate;
- </refentryinfo>
- <refmeta>
- &dhucpackage;
-
- &dhsection;
- </refmeta>
- <refnamediv>
- <refname>&dhpackage;</refname>
- <refpurpose>Creates and outputs an interpolated Markov model(IMM)</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>tigr-build-icm</command>
- </cmdsynopsis>
- </refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
-<para>
-Program build-icm.c creates and outputs an interpolated Markov
-model (IMM) as described in the paper
- A.L. Delcher, D. Harmon, S. Kasif, O. White, and S.L. Salzberg.
- Improved Microbial Gene Identification with Glimmer.
- Nucleic Acids Research, 1999, in press.
-Please reference this paper if you use the system as part of any
-published research.
-</para><para>
-Input comes from the file named on the command-line. Format should be
-one string per line. Each line has an ID string followed by white space
-followed by the sequence itself. The script run-glimmer3 generates
-an input file in the correct format using the 'extract' program.
-</para><para>
-The IMM is constructed as follows: For a given context, say
-acgtta, we want to estimate the probability distribution of the
-next character. We shall do this as a linear combination of the
-observed probability distributions for this context and all of
-its suffixes, i.e., cgtta, gtta, tta, ta, a and empty. By
-observed distributions I mean the counts of the number of
-occurrences of these strings in the training set. The linear
-combination is determined by a set of probabilities, lambda, one
-for each context string. For context acgtta the linear combination
-coefficients are:
-</para><para>
- lambda (acgtta)
- (1 - lambda (acgtta)) x lambda (cgtta)
- (1 - lambda (acgtta)) x (1 - lambda (cgtta)) x lambda (gtta)
- (1 - lambda (acgtta)) x (1 - lambda (cgtta)) x (1 - lambda (gtta)) x lambda (tta)
- (1 - lambda (acgtta)) x (1 - lambda (cgtta)) x (1 - lambda (gtta))
- x (1 - lambda (tta)) x (1 - lambda (ta)) x (1 - lambda (a))
-</para><para>
-We compute the lambda values for each context as follows:
- - If the number of observations in the training set is >= the constant
- SAMPLE_SIZE_BOUND, the lambda for that context is 1.0
- - Otherwise, do a chi-square test on the observations for this context
- compared to the distribution predicted for the one-character shorter
- suffix context.
- If the chi-square significance < 0.5, set the lambda for this context to 0.0
- Otherwise set the lambda for this context to:
- (chi-square significance) x (# observations) / SAMPLE_WEIGHT
-</para><para>
-To run the program:
-</para><para>
- build-icm <train.seq > train.model
-</para><para>
- This will use the training data in train.seq to produce the file
- train.model, containing your IMM.
-</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
- <para>
-tigr-glimmer3 (1),
-tigr-long-orfs (1),
-tigr-adjust (1),
-tigr-anomaly (1),
-tigr-extract (1),
-tigr-check (1),
-tigr-codon-usage (1),
-tigr-compare-lists (1),
-tigr-extract (1),
-tigr-generate (1),
-tigr-get-len (1),
-tigr-get-putative (1),
- </para>
- <para>http://www.tigr.org/software/glimmer/</para>
- <para>Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.</para>
- </refsect1>
- <refsect1>
- <title>AUTHOR</title>
-
- <para>This manual page was quickly copied from the glimmer web site and readme file by &dhusername; &dhemail; for
- the &debian; system.
- </para>
-
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:nil
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
-
-
=====================================
debian/glimmer2_mans/tigr-extract.1
=====================================
@@ -0,0 +1,67 @@
+.TH "TIGR-GLIMMER" "1"
+.SH "NAME"
+tigr-glimmer \(em Fine start/stop positions of genes in genome sequence
+.SH "SYNOPSIS"
+.PP
+\fBtigr-extract\fR [genome-file \fB\fIoptions\fR\fP]
+.SH "DESCRIPTION"
+.PP
+Program extract takes a FASTA format sequence file and a file
+with a list of start/stop positions in that file (e.g., as produced
+by the long-orfs program) and extracts and outputs the
+specified sequences.
+.PP
+The first command-line argument is the name of the sequence file,
+which must be in FASTA format.
+.PP
+The second command-line argument is the name of the coordinate file.
+It must contain a list of pairs of positions in the first file, one
+per line. The format of each entry is:
+.PP
+<IDstring>> <start position> <stop position>
+.PP
+This file should contain no other information, so if you're using
+the output of glimmer or long-orfs , you'll have to cut off
+header lines.
+.PP
+The output of the program goes to the standard output and has one
+line for each line in the coordinate file. Each line contains
+the IDstring , followed by white space, followed by the substring
+of the sequence file specified by the coordinate pair. Specifically,
+the substring starts at the first position of the pair and ends at
+the second position (inclusive). If the first position is bigger
+than the second, then the DNA reverse complement of each position
+is generated. Start/stop pairs that "wrap around" the end of the
+genome are allowed.
+.SH "OPTIONS"
+.IP "\fB-skip\fP" 10
+makes the output omit the first 3 characters of each sequence, i.e., it skips over the start codon. This was the behaviour of the previous version of the program.
+.IP "\fB-l\fP" 10
+makes the output omit an sequences shorter than n characters.
+n includes the 3 skipped characters if the \-skip switch
+is one.
+
+.SH "SEE ALSO"
+.PP
+tigr-glimmer3 (1),
+tigr-long-orfs (1),
+tigr-adjust (1),
+tigr-anomaly (1),
+tigr-build-icm (1),
+tigr-check (1),
+tigr-codon-usage (1),
+tigr-compare-lists (1),
+tigr-extract (1),
+tigr-generate (1),
+tigr-get-len (1),
+tigr-get-putative (1),
+.PP
+http://www.tigr.org/software/glimmer/
+.PP
+Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.
+.SH "AUTHOR"
+.PP
+This manual page was quickly copied from the glimmer web site by Steffen Moeller moeller at debian.org for
+the \fBDebian\fP system.
+
+.\" created by instant / docbook-to-man
=====================================
debian/glimmer2_mans/tigr-extract.sgml deleted
=====================================
@@ -1,165 +0,0 @@
-<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-
-<!-- Process this file with docbook-to-man to generate an nroff manual
- page: `docbook-to-man manpage.sgml > manpage.1'. You may view
- the manual page with: `docbook-to-man manpage.sgml | nroff -man |
- less'. A typical entry in a Makefile or Makefile.am is:
-
-manpage.1: manpage.sgml
- docbook-to-man $< > $@
-
-
- The docbook-to-man binary is found in the docbook-to-man package.
- Please remember that if you create the nroff version in one of the
- debian/rules file targets (such as build), you will need to include
- docbook-to-man in your Build-Depends control field.
-
- -->
-
- <!-- Fill in your name for FIRSTNAME and SURNAME. -->
- <!ENTITY dhfirstname "<firstname>Steffen</firstname>">
- <!ENTITY dhsurname "<surname>Möller</surname>">
- <!-- Please adjust the date whenever revising the manpage. -->
- <!ENTITY dhdate "<date>November 10, 2004</date>">
- <!ENTITY dhsection "<manvolnum>1</manvolnum>">
- <!ENTITY dhemail "<email>moeller at debian.org</email>">
- <!ENTITY dhusername "Steffen Moeller">
- <!ENTITY dhucpackage "<refentrytitle>TIGR-GLIMMER</refentrytitle>">
- <!ENTITY dhpackage "tigr-glimmer">
-
- <!ENTITY debian "<productname>Debian</productname>">
- <!ENTITY gnu "<acronym>GNU</acronym>">
- <!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
-]>
-
-<refentry>
- <refentryinfo>
- <address>
- &dhemail;
- </address>
- <author>
- &dhfirstname;
- &dhsurname;
- </author>
- <copyright>
- <year>2003</year>
- <holder>&dhusername;</holder>
- </copyright>
- &dhdate;
- </refentryinfo>
- <refmeta>
- &dhucpackage;
-
- &dhsection;
- </refmeta>
- <refnamediv>
- <refname>&dhpackage;</refname>
-
- <refpurpose>
-Fine start/stop positions of genes in genome sequence
-</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>tigr-extract</command>
- <arg>genome-file <option><replaceable>options</replaceable></option></arg>
- </cmdsynopsis>
- </refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
-<para>
-Program extract takes a FASTA format sequence file and a file
-with a list of start/stop positions in that file (e.g., as produced
-by the long-orfs program) and extracts and outputs the
-specified sequences.
-</para><para>
-The first command-line argument is the name of the sequence file,
-which must be in FASTA format.
-</para><para>
-The second command-line argument is the name of the coordinate file.
-It must contain a list of pairs of positions in the first file, one
-per line. The format of each entry is:
-</para><para> <IDstring>> <start position> <stop position>
-</para><para>This file should contain no other information, so if you're using
-the output of glimmer or long-orfs , you'll have to cut off
-header lines.
-</para><para>
-The output of the program goes to the standard output and has one
-line for each line in the coordinate file. Each line contains
-the IDstring , followed by white space, followed by the substring
-of the sequence file specified by the coordinate pair. Specifically,
-the substring starts at the first position of the pair and ends at
-the second position (inclusive). If the first position is bigger
-than the second, then the DNA reverse complement of each position
-is generated. Start/stop pairs that "wrap around" the end of the
-genome are allowed.
-</para>
- </refsect1>
- <refsect1>
- <title>OPTIONS</title>
- <variablelist>
- <varlistentry>
- <term><option>-skip</option></term>
- <listitem>
- <para> makes the output omit the first 3 characters of each sequence, i.e., it skips over the start codon. This was the behaviour of the previous version of the program.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-l</option></term><listitem><para>
- makes the output omit an sequences shorter than n characters.
- n includes the 3 skipped characters if the -skip switch
- is one.
- </para></listitem>
- </varlistentry>
- </variablelist>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
- <para>
-tigr-glimmer3 (1),
-tigr-long-orfs (1),
-tigr-adjust (1),
-tigr-anomaly (1),
-tigr-build-icm (1),
-tigr-check (1),
-tigr-codon-usage (1),
-tigr-compare-lists (1),
-tigr-extract (1),
-tigr-generate (1),
-tigr-get-len (1),
-tigr-get-putative (1),
-</para>
-<para>
-http://www.tigr.org/software/glimmer/
-</para>
-
- <para>Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.</para>
- </refsect1>
- <refsect1>
- <title>AUTHOR</title>
-
- <para>This manual page was quickly copied from the glimmer web site by &dhusername; &dhemail; for
- the &debian; system.
- </para>
-
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:nil
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
-
-
=====================================
debian/tigr-glimmer.1 → debian/glimmer2_mans/tigr-glimmer.1
=====================================
=====================================
debian/glimmer2_mans/tigr-glimmer3.1
=====================================
@@ -0,0 +1,101 @@
+.TH "TIGR-GLIMMER" "1"
+.SH "NAME"
+tigr-glimmer \(em Find/Score potential genes in genome-file using the probability model in icm-file
+.SH "SYNOPSIS"
+.PP
+\fBtigr-glimmer3\fR [\fB\fIgenome-file\fR\fP] [\fB\fIicm-file\fR\fP] [\fB\fI[options]\fR\fP]
+.SH "DESCRIPTION"
+.PP
+\fBtigr-glimmer\fR is a system for finding genes in microbial DNA, especially the genomes of bacteria and archaea. \fBtigr-glimmer\fR (Gene Locator and Interpolated Markov Modeler) uses interpolated Markov models (IMMs) to identify the coding regions and distinguish them from noncoding DNA. The IMM approach, described in our Nucleic Acids Research paper on \fBtigr-glimmer\fR 1.0 and in our subsequent paper on \fBtigr-glimmer\fR 2.0, uses a combination of Markov models from 1st through 8th-order, weighting each model according to its predictive power. \fBtigr-glimmer\fR 1.0 and 2.0 use 3-periodic nonhomogenous Markov models in their IMMs.
+.PP
+\fBtigr-glimmer\fR is the primary microbial gene finder at TIGR, and has been used to annotate the complete genomes of B. burgdorferi (Fraser et al., Nature, Dec. 1997), T. pallidum (Fraser et al., Science, July 1998), T. maritima, D. radiodurans, M. tuberculosis, and non-TIGR projects including C. trachomatis, C. pneumoniae, and others. Its analyses of some of these genomes and others is available at the TIGR microbial database site.
+.PP
+A special version of \fBtigr-glimmer\fR designed for small eukaryotes, GlimmerM, was used to find the genes in chromosome 2 of the malaria parasite, P. falciparum.. GlimmerM is described in S.L. Salzberg, M. Pertea, A.L. Delcher, M.J. Gardner, and H. Tettelin, "Interpolated Markov models for eukaryotic gene finding," Genomics 59 (1999), 24-31. Click here (http://www.tigr.org/software/glimmerm/) to visit the GlimmerM site, which includes information on how to download the GlimmerM system.
+.PP
+The \fBtigr-glimmer\fR system consists of two main programs. The first of these is the training program, build-imm. This program takes an input set of sequences and builds and outputs the IMM for them. These sequences can be complete genes or just partial orfs. For a new genome, this training data can consist of those genes with strong database hits as well as very long open reading frames that are statistically almost certain to be genes. The second program is glimmer, which uses this IMM to identify putative genes in an entire genome. \fBtigr-glimmer\fR automatically resolves conflicts between most overlapping genes by choosing one of them. It also identifies genes that are suspected to truly overlap, and flags these for closer inspection by the user. These ``suspect'' gene candidates have been a very small percentage of the total for all the genomes analyzed thus far.
+\fBtigr-glimmer\fR is a program that...
+.SH "OPTIONS"
+.IP "\fB-C \fIn\fR\fP" 10
+Use n as GC percentage of independent model
+.IP "" 10
+Note: n should be a percentage, e.g., \-C 45.2
+.IP "\-f" 10
+Use ribosome-binding energy to choose start codon
+.IP "\fB+f\fP" 10
+Use first codon in orf as start codon
+.IP "\fB-g \fIn\fR\fP" 10
+Set minimum gene length to n
+.IP "\fB-i \fIfilename\fR\fP" 10
+Use \fB\fIfilename\fR\fP to select regions of bases that are off
+limits, so that no bases within that area will be examined
+
+.IP "\fB-l\fP" 10
+Assume linear rather than circular genome, i.e., no wraparound
+.IP "\fB-L \fIfilename\fR\fP" 10
+Use filename to specify a list of orfs that should
+be scored separately, with no overlap rules
+
+.IP "\fB-M\fP" 10
+Input is a multifasta file of separate genes to be scored
+separately, with no overlap rules
+
+.IP "\fB-o \fIn\fR\fP" 10
+Set minimum overlap length to n. Overlaps shorter than this
+are ignored.
+
+.IP "\fB-p \fIn\fR\fP" 10
+Set minimum overlap percentage to n%. Overlaps shorter than this percentage of *both* strings are ignored.
+
+.IP "\fB-q \fIn\fR\fP" 10
+Set the maximum length orf that can be rejected because of
+the independent probability score column to (n \- 1)
+
+.IP "\fB-r\fP" 10
+Don't use independent probability score column
+
+.IP "\fB+r\fP" 10
+Use independent probability score column
+
+.IP "\fB-r\fP" 10
+Don't use independent probability score column
+
+.IP "\fB-s \fIs\fR\fP" 10
+Use string s as the ribosome binding pattern to find start codons.
+.IP "\fB+S\fP" 10
+Do use stricter independent intergenic model that doesn't
+give probabilities to in-frame stop codons. (Option is obsolete
+since this is now the only behaviour
+
+.IP "\fB-t \fIn\fR\fP" 10
+Set threshold score for calling as gene to n. If the in-frame
+score >= n, then the region is given a number and considered
+a potential gene.
+
+.IP "\fB-w \fIn\fR \fP" 10
+Use "weak" scores on tentative genes n or longer. Weak
+scores ignore the independent probability score.
+
+.SH "SEE ALSO"
+.PP
+tigr-adjust (1),
+tigr-anomaly (1),
+tigr-build-icm (1),
+tigr-check (1),
+tigr-codon-usage (1),
+tigr-compare-lists (1),
+tigr-extract (1),
+tigr-generate (1),
+tigr-get-len (1),
+tigr-get-putative (1),
+tigr-glimmer3 (1),
+tigr-long-orfs (1)
+.PP
+http://www.tigr.org/software/glimmer/
+.PP
+Please see the readme in /usr/share/doc/glimmer for a description on how to use Glimmer.
+.SH "AUTHOR"
+.PP
+This manual page was quickly copied from the glimmer web site by Steffen Moeller moeller at debian.org for
+the \fBDebian\fP system.
+
+.\" created by instant / docbook-to-man
=====================================
debian/glimmer2_mans/tigr-glimmer3.sgml deleted
=====================================
@@ -1,246 +0,0 @@
-<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-
-<!-- Process this file with docbook-to-man to generate an nroff manual
- page: `docbook-to-man manpage.sgml > manpage.1'. You may view
- the manual page with: `docbook-to-man manpage.sgml | nroff -man |
- less'. A typical entry in a Makefile or Makefile.am is:
-
-manpage.1: manpage.sgml
- docbook-to-man $< > $@
-
-
- The docbook-to-man binary is found in the docbook-to-man package.
- Please remember that if you create the nroff version in one of the
- debian/rules file targets (such as build), you will need to include
- docbook-to-man in your Build-Depends control field.
-
- -->
-
- <!-- Fill in your name for FIRSTNAME and SURNAME. -->
- <!ENTITY dhfirstname "<firstname>Steffen</firstname>">
- <!ENTITY dhsurname "<surname>Möller</surname>">
- <!-- Please adjust the date whenever revising the manpage. -->
- <!ENTITY dhdate "<date>November 10, 2004</date>">
- <!ENTITY dhsection "<manvolnum>1</manvolnum>">
- <!ENTITY dhemail "<email>moeller at debian.org</email>">
- <!ENTITY dhusername "Steffen Moeller">
- <!ENTITY dhucpackage "<refentrytitle>TIGR-GLIMMER</refentrytitle>">
- <!ENTITY dhpackage "tigr-glimmer">
-
- <!ENTITY debian "<productname>Debian</productname>">
- <!ENTITY gnu "<acronym>GNU</acronym>">
- <!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
-]>
-
-<refentry>
- <refentryinfo>
- <address>
- &dhemail;
- </address>
- <author>
- &dhfirstname;
- &dhsurname;
- </author>
- <copyright>
- <year>2003</year>
- <holder>&dhusername;</holder>
- </copyright>
- &dhdate;
- </refentryinfo>
- <refmeta>
- &dhucpackage;
-
- &dhsection;
- </refmeta>
- <refnamediv>
- <refname>&dhpackage;</refname>
- <refpurpose>
-Find/Score potential genes in genome-file using the probability model in icm-file
-</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>tigr-glimmer3</command>
- <arg><option><replaceable>genome-file</replaceable></option></arg>
- <arg><option><replaceable>icm-file</replaceable></option></arg>
- <arg><option><replaceable>[options]</replaceable></option></arg>
- </cmdsynopsis>
- </refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
-<para>
-<command>&dhpackage;</command> is a system for finding genes in microbial DNA, especially the genomes of bacteria and archaea. <command>&dhpackage;</command> (Gene Locator and Interpolated Markov Modeler) uses interpolated Markov models (IMMs) to identify the coding regions and distinguish them from noncoding DNA. The IMM approach, described in our Nucleic Acids Research paper on <command>&dhpackage;</command> 1.0 and in our subsequent paper on <command>&dhpackage;</command> 2.0, uses a combination of Markov models from 1st through 8th-order, weighting each model according to its predictive power. <command>&dhpackage;</command> 1.0 and 2.0 use 3-periodic nonhomogenous Markov models in their IMMs.
-</para><para>
-<command>&dhpackage;</command> is the primary microbial gene finder at TIGR, and has been used to annotate the complete genomes of B. burgdorferi (Fraser et al., Nature, Dec. 1997), T. pallidum (Fraser et al., Science, July 1998), T. maritima, D. radiodurans, M. tuberculosis, and non-TIGR projects including C. trachomatis, C. pneumoniae, and others. Its analyses of some of these genomes and others is available at the TIGR microbial database site.
-</para><para>
-A special version of <command>&dhpackage;</command> designed for small eukaryotes, GlimmerM, was used to find the genes in chromosome 2 of the malaria parasite, P. falciparum.. GlimmerM is described in S.L. Salzberg, M. Pertea, A.L. Delcher, M.J. Gardner, and H. Tettelin, "Interpolated Markov models for eukaryotic gene finding," Genomics 59 (1999), 24-31. Click here (http://www.tigr.org/software/glimmerm/) to visit the GlimmerM site, which includes information on how to download the GlimmerM system.
-</para><para>
-The <command>&dhpackage;</command> system consists of two main programs. The first of these is the training program, build-imm. This program takes an input set of sequences and builds and outputs the IMM for them. These sequences can be complete genes or just partial orfs. For a new genome, this training data can consist of those genes with strong database hits as well as very long open reading frames that are statistically almost certain to be genes. The second program is glimmer, which uses this IMM to identify putative genes in an entire genome. <command>&dhpackage;</command> automatically resolves conflicts between most overlapping genes by choosing one of them. It also identifies genes that are suspected to truly overlap, and flags these for closer inspection by the user. These ``suspect'' gene candidates have been a very small percentage of the total for all the genomes analyzed thus far.
- <command>&dhpackage;</command> is a program that...</para>
- </refsect1>
- <refsect1>
- <title>OPTIONS</title>
- <variablelist>
- <varlistentry>
- <term><option>-C <replaceable>n</replaceable></option></term>
- <listitem>
- <para>Use n as GC percentage of independent model</para>
- <para>Note: n should be a percentage, e.g., -C 45.2</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>-f</term><listitem><para>Use ribosome-binding energy to choose start codon</para></listitem>
- </varlistentry>
- <varlistentry>
- <term><option>+f</option></term><listitem><para>Use first codon in orf as start codon</para></listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-g <replaceable>n</replaceable></option></term><listitem><para>Set minimum gene length to n</para></listitem>
- </varlistentry>
- <varlistentry>
-<term><option>-i <replaceable>filename</replaceable></option></term>
- <listitem>
- <para>Use <option><replaceable>filename</replaceable></option>
- to select regions of bases that are off
- limits, so that no bases within that area will be examined
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-l</option></term>
- <listitem><para>Assume linear rather than circular genome, i.e., no wraparound</para></listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-L <replaceable>filename</replaceable></option></term>
- <listitem><para>Use filename to specify a list of orfs that should
- be scored separately, with no overlap rules
- </para></listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-M</option></term>
- <listitem><para>Input is a multifasta file of separate genes to be scored
- separately, with no overlap rules
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term><option>-o <replaceable>n</replaceable></option></term>
- <listitem>
- <para>Set minimum overlap length to n. Overlaps shorter than this
- are ignored.
- </para></listitem>
-</varlistentry>
-<varlistentry>
- <term><option>-p <replaceable>n</replaceable></option></term>
- <listitem>
- <para>
- Set minimum overlap percentage to n%. Overlaps shorter than this percentage of *both* strings are ignored.
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term><option>-q <replaceable>n</replaceable></option></term>
- <listitem>
- <para>Set the maximum length orf that can be rejected because of
- the independent probability score column to (n - 1)
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term><option>-r</option></term>
- <listitem>
- <para>
- Don't use independent probability score column
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term><option>+r</option></term>
- <listitem><para>
-Use independent probability score column
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term><option>-r</option></term>
- <listitem>
- <para>
- Don't use independent probability score column
- </para> </listitem> </varlistentry> <varlistentry>
- <term><option>-s <replaceable>s</replaceable></option></term>
- <listitem><para> Use string s as the ribosome binding pattern to find start codons.</para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term><option>+S</option></term>
- <listitem>
- <para>
- Do use stricter independent intergenic model that doesn't
- give probabilities to in-frame stop codons. (Option is obsolete
- since this is now the only behaviour
- </para> </listitem>
-</varlistentry>
-<varlistentry>
- <term><option>-t <replaceable>n</replaceable></option></term>
- <listitem><para>
- Set threshold score for calling as gene to n. If the in-frame
- score >= n, then the region is given a number and considered
- a potential gene.
- </para> </listitem>
-</varlistentry>
-<varlistentry>
- <term><option>-w <replaceable>n</replaceable> </option></term>
- <listitem><para>
- Use "weak" scores on tentative genes n or longer. Weak
- scores ignore the independent probability score.
- </para></listitem>
- </varlistentry>
- </variablelist>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
- <para>
-tigr-adjust (1),
-tigr-anomaly (1),
-tigr-build-icm (1),
-tigr-check (1),
-tigr-codon-usage (1),
-tigr-compare-lists (1),
-tigr-extract (1),
-tigr-generate (1),
-tigr-get-len (1),
-tigr-get-putative (1),
-tigr-glimmer3 (1),
-tigr-long-orfs (1)
-</para>
-<para>
-http://www.tigr.org/software/glimmer/
-</para>
- <para>Please see the readme in /usr/share/doc/glimmer for a description on how to use Glimmer.</para>
- </refsect1>
- <refsect1>
- <title>AUTHOR</title>
- <para>This manual page was quickly copied from the glimmer web site by &dhusername; &dhemail; for
- the &debian; system.
- </para>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:nil
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
-
-
=====================================
debian/glimmer2_mans/tigr-long-orfs.1
=====================================
@@ -0,0 +1,137 @@
+.TH "LONG-ORFS" "1"
+.SH "NAME"
+long-orfs \(em Find/Score potential genes in genome-file using
+the probability model in icm-file
+.SH "SYNOPSIS"
+.PP
+\fBtigr-long-orgs\fR [genome-file \fB\fIoptions\fR\fP]
+.SH "DESCRIPTION"
+.PP
+Program long-orfs takes a sequence file (in FASTA format) and
+outputs a list of all long "potential genes" in it that do not
+overlap by too much. By "potential gene" I mean the portion of
+an orf from the first start codon to the stop codon at the end.
+.PP
+The first few lines of output specify the settings of various
+parameters in the program:
+.PP
+Minimum gene length is the length of the smallest fragment
+considered to be a gene. The length is measured from the first base
+of the start codon to the last base *before* the stop codon.
+This value can be specified when running the program with the \-g option.
+By default, the program now (April 2003) will compute an optimal length
+for this parameter, where "optimal" is the value that produces the
+greatest number of long ORFs, thereby increasing the amount of data
+used for training.
+.PP
+Minimum overlap length is a lower bound on the number of bases overlap
+between 2 genes that is considered a problem. Overlaps shorter than
+this are ignored.
+.PP
+Minimum overlap percent is another lower bound on the number of bases
+overlap that is considered a problem. Overlaps shorter than this
+percentage of *both* genes are ignored.
+.PP
+The next portion of the output is a list of potential genes:
+.PP
+Column 1 is an ID number for reference purposes. It is assigned
+sequentially starting with 1 to all long potential genes. If
+overlapping genes are eliminated, gaps in the numbers will occur.
+The ID prefix is specified in the constant ID_PREFIX .
+.PP
+Column 2 is the position of the first base of the first start codon in
+the orf. Currently I use atg, and gtg as start codons. This is
+easily changed in the function Is_Start () .
+.PP
+Column 3 is the position of the last base *before* the stop codon. Stop
+codons are taa, tag, and tga. Note that for orfs in the reverse
+reading frames have their start position higher than the end position.
+The order in which orfs are listed is in increasing order by
+Max {OrfStart, End}, i.e., the highest numbered position in the orf,
+except for orfs that "wrap around" the end of the sequence.
+.PP
+When two genes with ID numbers overlap by at least a sufficient
+amount (as determined by Min_Olap and Min_Olap_Percent ), they
+are eliminated and do not appear in the output.
+.PP
+The final output of the program (sent to the standard error file so
+it does not show up when output is redirected to a file) is the
+length of the longest orf found.
+.PP
+
+Specifying Different Start and Stop Codons:
+.PP
+To specify different sets of start and stop codons, modify the file
+gene.h . Specifically, the functions:
+.PP
+Is_Forward_Start Is_Reverse_Start Is_Start
+Is_Forward_Stop Is_Reverse_Stop Is_Stop
+.PP
+are used to determine what is used for start and stop codons.
+.PP
+Is_Start and Is_Stop do simple string comparisons to specify
+which patterns are used. To add a new pattern, just add the comparison
+for it. To remove a pattern, comment out or delete the comparison
+for it.
+.PP
+The other four functions use a bit comparison to determine start and
+stop patterns. They represent a codon as a 12-bit pattern, with 4 bits
+for each base, one bit for each possible value of the bases, T, G, C
+or A. Thus the bit pattern 0010 0101 1100 represents the base
+pattern [C] [A or G] [G or T]. By doing bit operations (& | ~) and
+comparisons, more complicated patterns involving ambiguous reads
+can be tested efficiently. Simple patterns can be tested as in
+the current code.
+.PP
+For example, to insert an additional start codon of CAT requires 3 changes:
+1. The line
+|| (Codon & 0x218) == Codon
+should be inserted into Is_Forward_Start , since 0x218 = 0010 0001 1000
+represents CAT.
+2. The line
+|| (Codon & 0x184) == Codon
+should be inserted into Is_Reverse_Start , since 0x184 = 0001 1000 0100
+represents ATG, which is the reverse-complement of CAT. Alternately,
+the #define constant ATG_MASK could be used.
+3. The line
+|| strncmp (S, "cat", 3) == 0
+should be inserted into Is_Start .
+.SH "OPTIONS"
+.IP "\fB-g \fIn\fR\fP" 10
+Set minimum gene length to n. Default is to compute an
+optimal value automatically. Don't change this unless you
+know what you're doing.
+.IP "\fB-l\fP" 10
+Regard the genome as linear (not circular), i.e., do not allow
+genes to "wrap around" the end of the genome.
+This option works on both glimmer and long-orfs .
+The default behavior is to regard the genome as circular.
+.IP "\fB-o \fIn\fR\fP" 10
+Set maximum overlap length to n. Overlaps shorter than this
+are permitted. (Default is 0 bp.)
+.IP "\fB-p \fIn\fR\fP" 10
+Set maximum overlap percentage to n%. Overlaps shorter than
+this percentage of *both* strings are ignored. (Default is 10%.)
+.SH "SEE ALSO"
+.PP
+tigr-glimmer3 (1),
+tigr-adjust (1),
+tigr-anomaly (1),
+tigr-build-icm (1),
+tigr-check (1),
+tigr-codon-usage (1),
+tigr-compare-lists (1),
+tigr-extract (1),
+tigr-generate (1),
+tigr-get-len (1),
+tigr-get-putative (1),
+.PP
+http://www.tigr.org/software/glimmer/
+.PP
+Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.
+.SH "AUTHOR"
+.PP
+This manual page was quickly copied from the glimmer web site by Steffen Moeller moeller at debian.org for
+the \fBDebian\fP system.
+
+.\" created by instant / docbook-to-man
=====================================
debian/glimmer2_mans/tigr-long-orfs.sgml deleted
=====================================
@@ -1,238 +0,0 @@
-<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-
-<!-- Process this file with docbook-to-man to generate an nroff manual
- page: `docbook-to-man manpage.sgml > manpage.1'. You may view
- the manual page with: `docbook-to-man manpage.sgml | nroff -man |
- less'. A typical entry in a Makefile or Makefile.am is:
-
-manpage.1: manpage.sgml
- docbook-to-man $< > $@
-
-
- The docbook-to-man binary is found in the docbook-to-man package.
- Please remember that if you create the nroff version in one of the
- debian/rules file targets (such as build), you will need to include
- docbook-to-man in your Build-Depends control field.
-
- -->
-
- <!-- Fill in your name for FIRSTNAME and SURNAME. -->
- <!ENTITY dhfirstname "<firstname>Steffen</firstname>">
- <!ENTITY dhsurname "<surname>Möller</surname>">
- <!-- Please adjust the date whenever revising the manpage. -->
- <!ENTITY dhdate "<date>November 10, 2004</date>">
- <!ENTITY dhsection "<manvolnum>1</manvolnum>">
- <!ENTITY dhemail "<email>moeller at debian.org</email>">
- <!ENTITY dhusername "Steffen Moeller">
- <!ENTITY dhucpackage "<refentrytitle>LONG-ORFS</refentrytitle>">
- <!ENTITY dhpackage "long-orfs">
-
- <!ENTITY debian "<productname>Debian</productname>">
- <!ENTITY gnu "<acronym>GNU</acronym>">
- <!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
-]>
-
-<refentry>
- <refentryinfo>
- <address>
- &dhemail;
- </address>
- <author>
- &dhfirstname;
- &dhsurname;
- </author>
- <copyright>
- <year>2003</year>
- <holder>&dhusername;</holder>
- </copyright>
- &dhdate;
- </refentryinfo>
- <refmeta>
- &dhucpackage;
-
- &dhsection;
- </refmeta>
- <refnamediv>
- <refname>&dhpackage;</refname>
-
- <refpurpose>
-Find/Score potential genes in genome-file using
-the probability model in icm-file
-</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>tigr-long-orgs</command>
- <arg>genome-file <option><replaceable>options</replaceable></option></arg>
- </cmdsynopsis>
- </refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
-<para>
-Program long-orfs takes a sequence file (in FASTA format) and
-outputs a list of all long "potential genes" in it that do not
-overlap by too much. By "potential gene" I mean the portion of
-an orf from the first start codon to the stop codon at the end.
-</para><para>
-The first few lines of output specify the settings of various
-parameters in the program:
-</para><para>
- Minimum gene length is the length of the smallest fragment
- considered to be a gene. The length is measured from the first base
- of the start codon to the last base *before* the stop codon.
- This value can be specified when running the program with the -g option.
- By default, the program now (April 2003) will compute an optimal length
- for this parameter, where "optimal" is the value that produces the
- greatest number of long ORFs, thereby increasing the amount of data
- used for training.
-</para><para>
- Minimum overlap length is a lower bound on the number of bases overlap
- between 2 genes that is considered a problem. Overlaps shorter than
- this are ignored.
-</para><para>
- Minimum overlap percent is another lower bound on the number of bases
- overlap that is considered a problem. Overlaps shorter than this
- percentage of *both* genes are ignored.
-</para><para>
-The next portion of the output is a list of potential genes:
-</para><para>
- Column 1 is an ID number for reference purposes. It is assigned
- sequentially starting with 1 to all long potential genes. If
- overlapping genes are eliminated, gaps in the numbers will occur.
- The ID prefix is specified in the constant ID_PREFIX .
-</para><para>
- Column 2 is the position of the first base of the first start codon in
- the orf. Currently I use atg, and gtg as start codons. This is
- easily changed in the function Is_Start () .
-</para><para>
- Column 3 is the position of the last base *before* the stop codon. Stop
- codons are taa, tag, and tga. Note that for orfs in the reverse
- reading frames have their start position higher than the end position..
- The order in which orfs are listed is in increasing order by
- Max {OrfStart, End}, i.e., the highest numbered position in the orf,
- except for orfs that "wrap around" the end of the sequence.
-</para><para>
-When two genes with ID numbers overlap by at least a sufficient
-amount (as determined by Min_Olap and Min_Olap_Percent ), they
-are eliminated and do not appear in the output.
-</para><para>
-The final output of the program (sent to the standard error file so
-it does not show up when output is redirected to a file) is the
-length of the longest orf found.
-</para><para>
-
-
-Specifying Different Start and Stop Codons:
-</para><para>
-To specify different sets of start and stop codons, modify the file
-gene.h . Specifically, the functions:
-</para><para>
- Is_Forward_Start Is_Reverse_Start Is_Start
- Is_Forward_Stop Is_Reverse_Stop Is_Stop
-</para><para>
-are used to determine what is used for start and stop codons.
-</para><para>
-Is_Start and Is_Stop do simple string comparisons to specify
-which patterns are used. To add a new pattern, just add the comparison
-for it. To remove a pattern, comment out or delete the comparison
-for it.
-</para><para>
-The other four functions use a bit comparison to determine start and
-stop patterns. They represent a codon as a 12-bit pattern, with 4 bits
-for each base, one bit for each possible value of the bases, T, G, C
-or A. Thus the bit pattern 0010 0101 1100 represents the base
-pattern [C] [A or G] [G or T]. By doing bit operations (& | ~) and
-comparisons, more complicated patterns involving ambiguous reads
-can be tested efficiently. Simple patterns can be tested as in
-the current code.
-</para><para>
-For example, to insert an additional start codon of CAT requires 3 changes:
-1. The line
- || (Codon & 0x218) == Codon
- should be inserted into Is_Forward_Start , since 0x218 = 0010 0001 1000
- represents CAT.
-2. The line
- || (Codon & 0x184) == Codon
- should be inserted into Is_Reverse_Start , since 0x184 = 0001 1000 0100
- represents ATG, which is the reverse-complement of CAT. Alternately,
- the #define constant ATG_MASK could be used.
-3. The line
- || strncmp (S, "cat", 3) == 0
- should be inserted into Is_Start .
-</para>
-
- </refsect1>
- <refsect1>
- <title>OPTIONS</title>
- <variablelist>
- <varlistentry>
- <term><option>-g <replaceable>n</replaceable></option></term>
- <listitem>
- <para> Set minimum gene length to n. Default is to compute an
- optimal value automatically. Don't change this unless you
- know what you're doing.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-l</option></term><listitem><para>Regard the genome as linear (not circular), i.e., do not allow
- genes to "wrap around" the end of the genome.
- This option works on both glimmer and long-orfs .
- The default behavior is to regard the genome as circular.</para></listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-o <replaceable>n</replaceable></option></term><listitem><para>Set maximum overlap length to n. Overlaps shorter than this
- are permitted. (Default is 0 bp.)</para></listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-p <replaceable>n</replaceable></option></term><listitem><para>Set maximum overlap percentage to n%. Overlaps shorter than
- this percentage of *both* strings are ignored. (Default is 10%.)</para></listitem>
- </varlistentry>
- </variablelist>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
- <para>
-tigr-glimmer3 (1),
-tigr-adjust (1),
-tigr-anomaly (1),
-tigr-build-icm (1),
-tigr-check (1),
-tigr-codon-usage (1),
-tigr-compare-lists (1),
-tigr-extract (1),
-tigr-generate (1),
-tigr-get-len (1),
-tigr-get-putative (1),
-</para>
-<para>
-http://www.tigr.org/software/glimmer/
-</para>
-
- <para>Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.</para>
- </refsect1>
- <refsect1>
- <title>AUTHOR</title>
-
- <para>This manual page was quickly copied from the glimmer web site by &dhusername; &dhemail; for
- the &debian; system.
- </para>
-
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:nil
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
=====================================
debian/glimmer2_mans/tigr-run-glimmer3.1
=====================================
@@ -0,0 +1,33 @@
+.TH "TIGR-GLIMMER" "1"
+.SH "NAME"
+tigr-glimmer \(em Apply the suite of programs within glimmer3 to a a prokaryotic or archean genome.
+.SH "SYNOPSIS"
+.PP
+\fBtigr-run-glimmer3\fR
+.SH "DESCRIPTION"
+.PP
+A shell script that wraps a set of tigr-* utilities of the glimmer package to retrieve coding regions.
+.SH "SEE ALSO"
+.PP
+tigr-glimmer3 (1),
+tigr-adjust (1),
+tigr-anomaly (1),
+tigr-build-icm (1),
+tigr-check (1),
+tigr-codon-usage (1),
+tigr-compare-lists (1),
+tigr-extract (1),
+tigr-generate (1),
+tigr-get-len (1),
+tigr-get-putative (1),
+tigr-long-orfs (1),
+.PP
+http://www.tigr.org/software/glimmer/
+.PP
+Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.
+.SH "AUTHOR"
+.PP
+This manual page was quickly copied from the glimmer web site by Steffen Moeller moeller at debian.org for
+the \fBDebian\fP system.
+
+.\" created by instant / docbook-to-man
=====================================
debian/glimmer2_mans/tigr-run-glimmer3.sgml deleted
=====================================
@@ -1,120 +0,0 @@
-<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-
-<!-- Process this file with docbook-to-man to generate an nroff manual
- page: `docbook-to-man manpage.sgml > manpage.1'. You may view
- the manual page with: `docbook-to-man manpage.sgml | nroff -man |
- less'. A typical entry in a Makefile or Makefile.am is:
-
-manpage.1: manpage.sgml
- docbook-to-man $< > $@
-
-
- The docbook-to-man binary is found in the docbook-to-man package.
- Please remember that if you create the nroff version in one of the
- debian/rules file targets (such as build), you will need to include
- docbook-to-man in your Build-Depends control field.
-
- -->
-
- <!-- Fill in your name for FIRSTNAME and SURNAME. -->
- <!ENTITY dhfirstname "<firstname>Steffen</firstname>">
- <!ENTITY dhsurname "<surname>Mller</surname>">
- <!-- Please adjust the date whenever revising the manpage. -->
- <!ENTITY dhdate "<date>November 10, 2004</date>">
- <!ENTITY dhsection "<manvolnum>1</manvolnum>">
- <!ENTITY dhemail "<email>moeller at debian.org</email>">
- <!ENTITY dhusername "Steffen Moeller">
- <!ENTITY dhucpackage "<refentrytitle>TIGR-GLIMMER</refentrytitle>">
- <!ENTITY dhpackage "tigr-glimmer">
-
- <!ENTITY debian "<productname>Debian</productname>">
- <!ENTITY gnu "<acronym>GNU</acronym>">
- <!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
-]>
-
-<refentry>
- <refentryinfo>
- <address>
- &dhemail;
- </address>
- <author>
- &dhfirstname;
- &dhsurname;
- </author>
- <copyright>
- <year>2003</year>
- <holder>&dhusername;</holder>
- </copyright>
- &dhdate;
- </refentryinfo>
- <refmeta>
- &dhucpackage;
-
- &dhsection;
- </refmeta>
- <refnamediv>
- <refname>&dhpackage;</refname>
-
- <refpurpose>
-Apply the suite of programs within glimmer3 to a a prokaryotic or archean genome.
-</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>tigr-run-glimmer3</command>
- </cmdsynopsis>
- </refsynopsisdiv>
- <refsect1>
- <title>DESCRIPTION</title>
-<para>
-A shell script that wraps a set of tigr-* utilities of the glimmer package to retrieve coding regions.
-</para>
- </refsect1>
- <refsect1>
- <title>SEE ALSO</title>
- <para>
-tigr-glimmer3 (1),
-tigr-adjust (1),
-tigr-anomaly (1),
-tigr-build-icm (1),
-tigr-check (1),
-tigr-codon-usage (1),
-tigr-compare-lists (1),
-tigr-extract (1),
-tigr-generate (1),
-tigr-get-len (1),
-tigr-get-putative (1),
-tigr-long-orfs (1),
-</para>
-<para>
-http://www.tigr.org/software/glimmer/
-</para>
-
- <para>Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.</para>
- </refsect1>
- <refsect1>
- <title>AUTHOR</title>
-
- <para>This manual page was quickly copied from the glimmer web site by &dhusername; &dhemail; for
- the &debian; system.
- </para>
-
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:nil
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
=====================================
debian/manpages
=====================================
@@ -1,2 +1 @@
-debian/*.1
debian/glimmer2_mans/*.1
=====================================
debian/rules
=====================================
@@ -2,18 +2,6 @@
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
-MANPAGES=debian/glimmer2_mans/tigr-anomaly.1 \
- debian/glimmer2_mans/tigr-build-icm.1 \
- debian/glimmer2_mans/tigr-extract.1 \
- debian/glimmer2_mans/tigr-glimmer3.1 \
- debian/glimmer2_mans/tigr-long-orfs.1 \
- debian/glimmer2_mans/tigr-run-glimmer3.1
-
-.SUFFIXES: .1 .sgml
-
-.sgml.1:
- docbook-to-man $< > $@
-
%:
dh $@
=====================================
debian/salsa-ci.yml
=====================================
@@ -0,0 +1,4 @@
+---
+include:
+ - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+ - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
View it on GitLab: https://salsa.debian.org/med-team/tigr-glimmer/-/compare/12b2e3fae99d1de55b6464e820f0b40c0d32ea7c...7cbfcda38eb8df4f369b39cea2eafd5fd8bbc149
--
View it on GitLab: https://salsa.debian.org/med-team/tigr-glimmer/-/compare/12b2e3fae99d1de55b6464e820f0b40c0d32ea7c...7cbfcda38eb8df4f369b39cea2eafd5fd8bbc149
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-med-commit/attachments/20200429/34f37251/attachment-0001.html>
More information about the debian-med-commit
mailing list