Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BiG-SCAPE BiG-SCAPE
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • medema-group
  • BiG-SCAPEBiG-SCAPE
  • Wiki
  • domain prediction

domain prediction · Changes

Page history
domain prediction.md: removed math formula that looked bad authored Apr 01, 2018 by Jorge Navarro Muñoz's avatar Jorge Navarro Muñoz
Hide whitespace changes
Inline Side-by-side
domain prediction.md
View page @ 8a04701f
......@@ -14,4 +14,4 @@ The coordinates used for extracting and handling the domain sequences are the en
> (“env from” and “env to”) define the envelope of the domain’s location on the target sequence. The envelope is almost always a little wider than what HMMER chooses to show as a reasonably confident alignment. As mentioned earlier, the envelope represents a subsequence that encompasses most of the posterior probability for a given homologous domain, even if precise endpoints are only fuzzily inferrable.
After domain prediction, a step of filtering is performed where overlapping domains are discarded based on the per-domain score. When comparing pairs of domains within the same CDS, domain filtering will be triggered if the amino acid overlap percentage of any of the domain's sequences (i.e. $`overlap in amino acids / the domain length`$) is higher than `overlap_cutoff` (set by the `--domain_overlap_cutoff` parameter), which is $`0.1`$ by default.
After domain prediction, a step of filtering is performed where overlapping domains are discarded based on the per-domain score. When comparing pairs of domains within the same CDS, domain filtering will be triggered if the amino acid overlap percentage of any of the domain's sequences (i.e. overlap in amino acids / domain length) is higher than `overlap_cutoff` (set by the `--domain_overlap_cutoff` parameter), which is $`0.1`$ by default.
Clone repository
  • Alignment Modes
  • GCFs and GCCs
  • anchor file
  • big scape classes
  • domain prediction
  • Home
  • input
  • installation
  • output
  • parameters