Project Title : "Structural and functional characterization of serine biosynthetic pathway enzymes from Entamoeba histolytica"

No. of Post : 01

Qualification : Ph.D in any computational biology / bioinformatics

Desirable : 1. Experience with docking, simulations and structural biology with proof of publications is preferred. 2. National Eligibility Test cleared [CSIR/UGC] candidate is preferred.

Salary : According to CSIR rules
How to apply

The application on plain paper indicating name, date of birth/age, address, essential/technical/professional qualifications. experience, list of publications should reach The Prof. S. Gourinath, Principal Investigator, [Project Director], School of Life Sciences, Jawaharlal Nehru University, New Delhi-110067, on or before 23rd May 2016.

More at http://www.jnu.ac.in/Career/currentjobs.htm

mod_rewrite provides a flexible and powerful way to manipulate URLs using an unlimited number of rules. Each rule can have an unlimited number of attached rule conditions, to allow you to rewrite URL based on server variables, environment variables, HTTP headers, or time stamps.

mod_rewrite operates on the full URL path, including the path-info section. A rewrite rule can be invoked in httpd.conf or in .htaccess. The path generated by a rewrite rule can include a query string, or can lead to internal sub-processing, external request redirection, or internal proxy throughput.

Further details, discussion, and examples, are provided in the detailed mod_rewrite documentation.

• sudo a2enmod rewrite

• sudo systemctl restart apache2

• sudo nano /etc/apache2/sites-available/000-default.conf

Write this

<VirtualHost *:80>
    <Directory /var/www/html>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride All
        Require all granted
    </Directory>

    . . .
</VirtualHost>

Address of the bookmark: https://www.digitalocean.com/community/tutorials/how-to-rewrite-urls-with-mod_rewrite-for-apache-on-ubuntu-18-04

• dbCAN provides the capability of automated and comprehensive CAZyme annotation of a given genome submitted by the user;
• dbCAN provides an explicitly defined signature domain for each and every CAZyme family along with its location in all the relevant full-length CAZyme proteins in all sequenced genomes;
• dbCAN provides the most complete set of metagenomic CAZyme genes published so far and represents the first step towards discovering novel CAZyme catalysts in metagenomes;
• dbCAN provides a subfamily classification of the existing CAZyme families based on sequence similarities;
• dbCAN make all pre-computed data freely available to the public, including sequence alignments, hidden markov models (HMMs) and phylogenies of the signature domain regions in each and every CAZyme family and subfamily.

dbCAN is updated regularly when CAZy database created new families based on latest literature.

Address of the bookmark: http://csbl.bmb.uga.edu/dbCAN/index.php

Address of the bookmark: http://busca.biocomp.unibo.it/

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

More at

https://www.isas.de/files/redaktion/jobs/2021/18.60.1_Postdoc_deNBI_06_21_AS.pdf

https://www.isas.de/en/news/062021-post-doctoral-position-scientist-mfd-in-bioinformatics

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>

The MicroScope platform is available at this URL:

https://www.genoscope.cns.fr/agc/microscope

Address of the bookmark: http://microscope.readthedocs.org/en/latest/index.html

Eligibility : M Phil / Phd

Location : Thiruvananthapuram

Last Date : 30 Apr 2016

Hiring Process : Face to Face Interview
IISER -TVM

The Postdoctoral Fellowship/Research Associateship is a full-time, contractual position for highly qualified young scientists to carry out research at CCMS, IISER-TVM.

Research areas at the Centre

Quantum Chemistry/ Computational Fluid Dynamics/Condensed Matter Physics (Theory)/Genomics/Genetics/Gravitational Waves

Qualifications: PhD in Bioinformatics / Biophysics / Physics / Astrophysics / Chemistry / Mathematics / Engineering (Mechanical/Aerospace) Those who are in the final stages of their Ph.D. thesis submission are also eligible to apply. However, those candidates must have submitted the thesis at the time of the interview.

Experience: Applicants should have at least three peer reviewed publications and relevant experience in the research area they are applying for.

No. of positions: 5

Age limit: 35 yrs or below. A relaxation of 5 yrs will be applicable to candidates belonging to SC/ST/OBC and women candidates

Salary: The Fellowship carries a remuneration of INR Rs. 5,18,000 - Rs. 5,76,000 per annum (including HRA). The postdoctoral fellowship may not be held concurrently with any other national or international fellowships. It is also not transferable to any other fellowship
How to apply

Applications should reach the Head, CCMS, IISER Thiruvananthapuram,CET Campus, Engineering College PO,Thiruvananthapuram 695016 on or before April 30, 2016 by e-mail to ccms@iisertvm.ac.in by mentioning the research area name in the subject line.

More at http://www.iisertvm.ac.in/openings/read_opening/150.phpx