“It’s like a subway map,” she said, “but for DNA.”

That idea is exactly what Sequence Tube Map brings to life.

Instead of showing a genome as one long, confusing sequence, it displays different genomic paths like routes on a metro map. Where sequences are shared, the paths travel together. Where genetic variation occurs, they branch into different routes and may join again later.

This makes complex genome graphs much easier to explore.

Maya could now see how different haplotypes moved through the same genomic region and where they took different paths. She could even view sequencing reads mapped onto the graph, helping her understand what was happening in regions with genetic variation.

What once looked like a tangled network now looked like a journey.

Sequence Tube Map turns the complexity of graph genomes into a visual story—making it easier for scientists to see how DNA can take different routes.

Read more at  https://github.com/vgteam/sequencetubemap 

and

https://academic.oup.com/bioinformatics/article/35/24/5318/5542397

Demo at https://vgteam.github.io/sequenceTubeMap/

Instead of asking only whether two genes occur together across genomes, CORGIAS asks a deeper question: did these genes actually evolve together, repeatedly gaining or losing their presence in concert, or are they merely travelling together because of their inherited history? The framework introduces two complementary approaches, Ancestral State Adjustment (ASA) and the Simultaneous EVolution test (SEV), which incorporate evolutionary information into the search for gene associations. This distinction becomes increasingly important as genome sequencing continues to uncover enormous numbers of microbial genomes, many from organisms that have never been cultured and whose genes remain functionally mysterious. In this growing genomic landscape, simply finding a gene is no longer enough—we need clues about what that gene might be doing. CORGIAS approaches this problem almost like a genomic detective: rather than treating every association as evidence, it reconstructs the evolutionary story behind the association and asks whether the evidence survives that history. By doing so, it offers a way to separate coincidence from biological connection and potentially uncover functional relationships hidden within the vast microbial genomic landscape. The broader message is beautifully simple: genes do not evolve in isolation, and understanding what they do may require us to look beyond where they are today and reconstruct how they arrived there. Sometimes, the most important clue in a genome is not the gene itself, but the evolutionary journey it has taken.

More at https://academic.oup.com/nargab/article/7/4/lqaf182/8377910?

Address of the bookmark: https://bioinfo.noble.org/GWASPRO/

Compare structural and functional annotations of proteins between sequenced genomes.

Address of the bookmark: http://frodock.chaconlab.org/

More at http://bmbl.sdstate.edu/DMINDA2/

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4086085/

Address of the bookmark: http://bmbl.sdstate.edu/DMINDA2/

Address of the bookmark: http://huanglab.phys.hust.edu.cn/hnadock/

The following table shows SLURM commands on the SOE cluster.

For more information, run man on the commands above. See some examples below.

1. Info about the partitions and nodes
List all the partitions available to you and the nodes therein:

sinfo

Nodes in state idle can accept new jobs.

Show a partition configuratuin, for example, SOE_main

scontrol show partition=SOE_main

Show current info about a specific node:

scontrol show node=<nodename>

You can also specify a group of nodes in the command above. For example, if your MPI job is running across soenode05,06,35,36, you can execute the command below to get the info on the nodes you are interested in:

scontrol show node=soenode[05-06,35-36]

An informative parameter in the output to look at would be CPULoad. It allows you to see how your application utilizes the CPUs on the running nodes.

2. Submit scripts
The header in a submit script specifies job name, partition (queue), time limit, memory allocation, number of nodes, number of cores, and files to collect standard output and error at run time, for example

#!/bin/bash

#SBATCH --job-name=OMP_run     # job name, "OMP_run"
#SBATCH --partition=SOE_main   # partition (queue)
#SBATCH -t 0-2:00              # time limit: (D-HH:MM) 
#SBATCH --mem=32000            # memory per node in MB 
#SBATCH --nodes=1              # number of nodes
#SBATCH --ntasks-per-node=16   # number of cores
#SBATCH --output=slurm.out     # file to collect standard output
#SBATCH --error=slurm.err      # file to collect standard errors

If the time limit is not specified in the submit script, SLURM will assign the default run time, 3 days. This means the job will be terminated by SLURM in 72 hrs. The maximum allowed run time is two weeks, 14-0:00.
If the memory limit is not requested, SLURM will assign the default 16 GB. The maximum allowed memory per node is 128 GB. To see how much RAM per node your job is using, you can run commands sacct or sstat to query MaxRSS for the job on the node - see examples below.
Depending on a type of application you need to run, the submit script may contain commands to create a temporary space on a computational node - see the discussion about using the file systems on the cluster.
Then it sets the environment specific to the application and starts the application on one or multiple nodes - see sbatch sample scripts in directory /usr/local/Samples on soemaster1.hpc.rutgers.edu.
You can submit your job to the cluster with sbatch command:

sbatch myscript.sh

3. Query job information
List all currently submitted jobs in running and pending states for a user:

squeue -u <username>

Command squeue can be run with format options to expose specific information, for example, when pending job #706 is scheduled to start running:

squeue -j 706 --format="%S"

START_TIME
2015-04-30T09:54:32

More info can be shown by placing additional format options, for example:

squeue -j 706 --format="%i %P %j %u %T %l %C %S"

JOBID PARTITION   NAME    USER STATE   TIMELIMIT  CPUS START_TIME
706   SOE_main  Par_job_3 mike PENDING 3-00:00:00 64   2015-04-30T09:54:32

To see when all the jobs, pending in the queue, are scheduled to start:

squeue --start 

List all running and completed jobs for a user

sqlog -u <username>

or

sqlog -j <JobID>

The following appreviations are used for the job states:

       CA   CANCELLED      Job was cancelled.

       CD   COMPLETED      Job completed normally.

       CG   COMPLETING     Job is in the process of completing.

       F    FAILED         Job termined abnormally.

       NF   NODE_FAIL      Job terminated due to node failure.

       PD   PENDING        Job is pending allocation.

       R    RUNNING        Job currently has an allocation.

       S    SUSPENDED      Job is suspended.

       TO   TIMEOUT        Job terminated upon reaching its time limit.

You can specify the fields you would like to see in the output of sqlog:

sqlog --format=list

The command below, for example, provides Job ID, user name, exit state, start date-time, and end date-time for job #2831:

sqlog -j 2831 --format=jid,user,state,start,end

List status info for a currently running job:

sstat -j <jobid>

A formatted output can be used to gain only a specific info, for example, the maximum resident RAM usage on a node:

sstat --format="JobID,MaxRSS" -j <jobid>

To get statistics on completed jobs by jobID:

sacct --format="JobID,JobName,MaxRSS,Elapsed" -j <jobid>

To view the same information for all jobs of a user:

sacct --format="JobID,JobName,MaxRSS,Elapsed" -u <username>

To print a list of fields that can be specified with the --format option:

sacct --helpformat

For example, to get Job ID, Job name, Exit state, start date-time, and end date-time for job #2831:

sacct -j 2831 --format="JobID,JobName,State,Start,End"

Another useful command to gain information about a running job is scontrol:

scontrol show job=<jobid>

4. Cancel a job
To cancel one job:

scancel <jobid>

To cancel one job and delete the TMP directory created by the submit script on a node:

sdel <jobid>

To cancel all the jobs for a user:

scancel -u <username>

To cancel one or more jobs by name:

scancel --name <myJobName>

CDSA is pleased to announce a 4 days hands-on training program on “Essentials of Statistics and Data Analysis using R” at ICGEB, Aruna Asaf Ali Road, New Delhi on December 1 – 4, 2015. This will involve developing and enhancing skills to understand basic principles of statistics for summarizing data and use of appropriate statistical tests as well as providing an understanding of data analysis using R. Didactic lectures with practical sessions will be delivered by experienced faculties from AIIMS and Novartis. Live classroom with power point presentations, case studies, mock exercise, practical sessions on R, group work with time for discussion and Q&A sessions are added advantages of this workshop.

Please contact gayatrivishwakarma.cdsa@thsti.res.in or vineetabaloni.cdsa@thsti.res.in for program and registration details.

Please nominate personage or register yourself on or before November 6, 2015 along with the electronic transfer of registration fee.

Staff Scientists

Specialization: Applicant should have a Ph.D. with excellent academic credentials along with the track record of scientific productivity evidenced by publications/patents/products in the frontier areas of Plant Biology such as, Computational Biology, Genome Analysis and Molecular Mapping, Molecular Mechanism of Abiotic Stress Responses, Nutritional Genomics, Plant Development and Architecture, Plant Immunity, Molecular Breeding, Transgenics for crop improvement and other emerging areas based on plant genomics.

Remuneration: The length of experience and scientific accomplishments/quality of scientific productivity record will be major factors in deciding the level of appointment as Staff Scientist as well as starting salary in the Pay Bands of Rs 15,600-39,100 (with grade pay of 5400), and Rs 37,400-67,000 (with grade pay of 8,700 and 8,900) plus usual allowances admissible to the Central Government employees. However, NIPGR reserves the right to select candidates in the lower grade against the foregoing posts depending upon the qualifications and experience of the candidate. Reservation of posts shall be as per Govt. of India norms. Five posts (SC-2, ST-1, OBC-2) in the Pay Band of Rs 15,600-39,100 with Grade Pay of Rs 5400, are reserved.

More at http://www.nipgr.res.in/careers/vacancies_latest.php#

Apply online at http://www.nipgr.res.in/nipgr_recu/nipgr_recu.php

Form http://www.nipgr.res.in/files/careers/Application_Performa_2015.doc