NOvel SpEcies Identification Pipeline
Computational Systems Biology Lab · IIT Madras
-
Pipeline modules aren't available on this machine yet, so runs will fail until this is fixed. This means you don't have git access to the private NOSE repository configured here (or git itself isn't set up). Ask a maintainer for access to github.com/RamanLab/NOSE, make sure git can authenticate as you, then restart nose-ui -- it retries automatically.
NOSE Pipeline Overview
From assembled genomes to novel species · quality → novelty → placement → prevalence → function → metabolism
NOSE - Novel Species Identification Pipeline
An automated, reproducible workflow that takes assembled genome(s) and identifies and characterizes potential novel species across six sequential/branching modules. Developed at the Computational Systems Biology Lab, IIT Madras.
Documentation ↗
Server setup reference
Full install instructions (Conda/Miniconda, pip install nose-pipeline) are in the Installation guide. Once installed, this dashboard only depends on two things at runtime:
1
Conda/mamba on PATH - each module pulls its own tool environment on first run Checking…
Show command
conda --version
Launch the dashboard (reachable from other machines on your network) Already done - you're here
Show command
nose-ui --host 0.0.0.0 --port 5050
From install to result, in one line: once the dashboard is running, open it in a browser, fill each module's genome/database paths under its Config tab (or use the sidebar's "Genome Source" + Apply to All Modules), then either run modules one at a time or click Run Full Pipeline. The diagram below shows exactly what happens next - M1 checks quality, M2 decides which genomes are novel, and that novelty gate is what feeds M3, M5 and M6. Live progress and finished results for each run show up further down under Module Status.
Credentials & Licenses
A quick note before you fill in Config: every key and license below is yours - NOSE doesn't ship or share any of them.
This dashboard runs locally on your machine - nothing leaves it except calls to the services you configure below.
N
NCBI API Key & Email Required · Free
Resolves real organism names from GCA/GCF accessions. Grab a free key at ncbi.nlm.nih.gov/account/settings → API Key Management, then drop it into the sidebar's Credentials section - it applies to all 6 modules. See the full NCBI setup guide for step-by-step instructions.
C
CPLEX (Module 6 solver) Your own license
Point CPLEX Library Path in Module 6's Config - or the same field on the Full Pipeline Run page under M6 · CarveMe Settings - at your own licensed installation (e.g. via the IBM Academic Initiative). NOSE never bundles or redistributes CPLEX itself.
D
Reference databases Free & public
GTDB-Tk, CheckM2, antiSMASH, COG/CDD, geNomad, BLAST 16S - download to your own server via each module's Config tab. You'll always be asked to confirm before a download starts. Not bundled with NOSE.
How it works - pipeline workflow
Click any module to open its config
Idle Running Done Failed Dashed box = novelty gate (ANI < 95% only)
Module Status
Live results and run status for each module - no workflow explanation here, see Overview for that
-
Total genomes (M2)
-
Novel · ANI < 95%
-
Known species
0/6
Modules completed
Per-module report
Loading module status…
Full Pipeline Run
Fill in every module's settings below, save once, then run all six modules end to end
▶ Pipeline
Pipeline configuration - all modules
▼ End of config
Workflow & Backend
Loading WORKFLOW.md…
Downloading database

Make sure you have enough free disk space and a stable connection before starting - this cannot be safely paused once it begins.

Module started

You can safely close this tab or navigate away. The run continues on the server - nothing stops. Reopen this dashboard anytime and click the module's Log tab to see live progress, or check its status badge on the Overview page.

Don't show this again
N
Welcome to NOSE

No novel candidates found

Every screened genome matched a known species (ANI ≥ 95%). Modules 3-6 all need Module 2's novel candidates, so there's nothing for them to process -- the pipeline stopped here rather than run them on nothing.

Want to run any of them anyway, on the known-species genomes?