<?xml version='1.0'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
	<title><![CDATA[BOL: Related items]]></title>
	<link>https://bioinformaticsonline.com/related/30440?offset=1080</link>
	<atom:link href="https://bioinformaticsonline.com/related/30440?offset=1080" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/pages/view/9028/linux-for-bioinformatician</guid>
	<pubDate>Thu, 13 Mar 2014 16:59:26 -0500</pubDate>
	<link>https://bioinformaticsonline.com/pages/view/9028/linux-for-bioinformatician</link>
	<title><![CDATA[Linux for bioinformatician !!!]]></title>
	<description><![CDATA[<p>Linux, free operating system for computers, provides several powerful admin tools and utilities which will help you to manage your systems effectively and handle huge amount of genomic/biological data with an ease. The field of bioinformatics relies heavily on Linux-based computers and software. Although most bioinformatics programs can be compiled to run. If you don&rsquo;t know what these no so user-friendly tools are and how to use them, you could be spending lot of time trying to perform even the basic admin tasks. The focus of this linux series is to help you understand system admin as well as basic tools, which will help you to become an effective bioinformatician and computational biologist.<br /><br /></p><p>For knowledge about Linux and their importance amongst bioinformatician plesae read this article "<a href="http://www.ualberta.ca/~stothard/downloads/linux_for_bioinformatics.pdf">An introduction to Linux for bioinformatics</a>" by Paul Stothard.</p><p>Linux cheat sheet at http://bioinformaticsonline.com/file/view/87/linux-cheat-sheet</p><p>Please browse for futher useful linux pages on right hand side ...</p>]]></description>
	<dc:creator>Rahul Nayak</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/44495/exrec-exclusion-of-recombined-dna</guid>
	<pubDate>Wed, 27 Mar 2024 20:48:26 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/44495/exrec-exclusion-of-recombined-dna</link>
	<title><![CDATA[ExRec: Exclusion of Recombined DNA]]></title>
	<description><![CDATA[<p><span>ExRec (Exclusion of Recombined DNA) is a Python pipeline that implements the four-gamete test to filter out recombined DNA sites from up to thousands of DNA sequence loci. The pipeline consists of five standalone applications: the first two convert folders of NEXUS or PHYLIP files into the standard input file for the main program that conducts the four-gamete filtering procedures. The pipeline outputs recombination-filtered data in concatenated NEXUS and PHYLIP formats and a tab-delimited table containing descriptive statistics for all loci and the results. This software also allows the user to output the longest non-recombined sequence blocks from loci (current best practice) or randomly select non-recombined blocks from loci (a newer approach). Two other applications in the package convert the recombination-filtered data into single-locus NEXUS or PHYLIP files. The ExRec package can thus facilitate species delimitation, species tree, and historical demography studies by providing loci that better meet the no-recombination assumption in coalescent-based analyses.</span></p>
<p><span>Link to the article:&nbsp;</span><a href="https://academic.oup.com/bioinformaticsadvances/article/3/1/vbad174/7455250?searchresult=1" target="_blank">https://academic.oup.com/bioinformaticsadvances/article/3/1/vbad174/7455250?searchresult=1</a><br><br><span>Link to the software:</span><br><a href="https://github.com/Sammccarthypotter/ExRec" target="_blank">https://github.com/Sammccarthypotter/ExRec</a></p><p>Address of the bookmark: <a href="https://github.com/Sammccarthypotter/ExRec" rel="nofollow">https://github.com/Sammccarthypotter/ExRec</a></p>]]></description>
	<dc:creator>LEGE</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/pages/view/9204/keep-your-important-ssh-session-running-when-you-disconnect-from-server</guid>
	<pubDate>Sat, 15 Mar 2014 21:39:17 -0500</pubDate>
	<link>https://bioinformaticsonline.com/pages/view/9204/keep-your-important-ssh-session-running-when-you-disconnect-from-server</link>
	<title><![CDATA[Keep Your Important SSH Session Running when You Disconnect from Server !!!]]></title>
	<description><![CDATA[<p>As a Bioinformatician/ Computational biologist we swim in the ocean of genomic/proteomics data, and play with them with an ease. In our day to day simulation, analysis, comparative study we do need to run exhaustive programs, which might take more than a week. In such cases we do need to disconnect from sever in a way that our program/session should not get terminated. To do so there are lots of software, tools such as tmux ( <a href="http://tmux.sourceforge.net/">http://tmux.sourceforge.net/</a>, nohup (<a href="http://ss64.com/bash/nohup.html">http://ss64.com/bash/nohup.html</a>) , byobu (<a href="https://help.ubuntu.com/10.04/serverguide/byobu.html">https://help.ubuntu.com/10.04/serverguide/byobu.html</a>) and other commands (disown -a &amp;&amp; exit), but following are the ones I use the most.</p><p>Screen is like a window manager for your console. It will allow you to keep multiple terminal sessions running and easily switch between them. It also protects you from disconnection, because the screen session doesn&rsquo;t end when you get disconnected.<br /><br />You&rsquo;ll need to make sure that screen is installed on the server you are connecting to. If that server is Ubuntu or Debian, just use this command:<br /><br />sudo apt-get install screen<br /><br />Now you can start a new screen session by just typing screen at the command line. You&rsquo;ll be shown some information about screen. Hit enter, and you&rsquo;ll be at a normal prompt.<br /><br /><strong>To disconnect (but leave the session running)</strong><br /><br />Hit Ctrl + A and then Ctrl + D in immediate succession. You will see the message [detached]<br /><br /><strong>To reconnect to an already running session</strong><br /><br />screen -r<br /><br /><strong>To reconnect to an existing session, or create a new one if none exists</strong><br /><br />screen -D -r<br /><br /><strong>To create a new window inside of a running screen session</strong><br /><br />Hit Ctrl + A and then C in immediate succession. You will see a new prompt.<br /><br /><strong>To switch from one screen window to another</strong><br /><br />Hit Ctrl + A and then Ctrl + A in immediate succession.<br /><br /><strong>To list open screen windows</strong><br /><br />Hit Ctrl + A and then W in immediate succession</p>]]></description>
	<dc:creator>Jitendra Narayan</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/45338/dna-in-pieces-survival-in-progress-the-rotifer%E2%80%99s-incredible-secret</guid>
	<pubDate>Fri, 18 Sep 2026 03:07:47 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/45338/dna-in-pieces-survival-in-progress-the-rotifer%E2%80%99s-incredible-secret</link>
	<title><![CDATA[DNA in Pieces, Survival in Progress: The Rotifer’s Incredible Secret]]></title>
	<description><![CDATA[<p>A creature smaller than a grain of sand has discovered a surprising method of surviving damage that can break its DNA apart. It lives in the mosses and lichens, in the thin films of water that show up after rain and disappear when the area dries out. Although it has no hard armor, no sharp claws, and no venom, it is still able to survive even when its chromosomes are shattered by radiation and can pass on some of that damaged DNA to its offspring so that the repair process can go on for several generations. The animal in question is a bdelloid rotifer named Adineta vaga, and its unusual method of survival is providing scientists with new ideas regarding how DNA damage can be repaired.</p><p>Bdelloid rotifers are small animals well known for their ability to survive in harsh conditions. They can endure extreme dehydration by entering a state of dormancy and then revive when water becomes available again. Scientists have always been interested in the degree to which these animals resist radiation, since radiation can severely damage DNA by causing both of its strands to break. Interestingly, Adineta vaga's ability to survive radiation may be connected to the way in which it tolerates drying out, as dehydration can also damage DNA. The rotifer probably evolved strong DNA protection and repair mechanisms primarily as a response to its severe environment. Its resistance to radiation is merely a byproduct of adapting to the cycles of drying and rehydration.</p><p>In order to find out more about this ability, the researchers subjected A. vaga to proton radiation and then examined what effect it had on its chromosomes. The radiation caused serious damage, resulting in hundreds of breaks in the DNA. For the vast majority of organisms, such extensive chromosome damage would be disastrous; it's similar to going through an instruction manual in a shredder and ending up with a large number of separate fragments. The scientists believed that the rotifers would repair their chromosomes before producing offspring. However, what they discovered was unexpected: some of the broken pieces of chromosome did survive and were passed on to the next generations, where the repair process continued.</p><p>The discovery took on even greater interest when the scientists examined the offspring of the irradiated rotifers. Rather than observing the same DNA damage in all the generations, they found different sized sections missing and evidence that some of the genetic regions which had been lost were being slowly restored. The researchers proposed that the rotifers use a repair mechanism known as Break-Induced Homologous Extension Repair, or BIHER. In simple terms, a broken piece of DNA can locate a matching sequence on the other chromosome and use it as a guide to rebuild itself. If the damage is beyond what can be repaired in one generation, the repair process can continue in the next.</p><p>What makes the rotifer's method of repairing DNA so unusual is that, normally, we consider DNA repair to take place immediately after damage has occurred, with the cell rapidly repairing the damaged DNA. In A. vaga, however, the repair process can be a lot longer. Certain pieces of chromosome survive the initial damage, are inherited, and then serve as the basis for further repairs in later generations. It's as if one generation begins mending a broken book, the next one continues the work, and another eventually completes the job until all the missing parts have been restored.</p><p>One reason why this might work is that bdelloid rotifers have holocentric chromosomes. Rather than having a single point, as most chromosomes do, which controls movement during cell division, the ability to move is distributed along the entire length of their chromosomes. As a result, fragments of chromosomes are sometimes able to retain the parts that are necessary for them to move and divide, and this may account for how broken pieces of chromosome can last long enough to be passed on and then repaired.</p><p>This finding could have implications that go beyond those concerning rotifers. Scientists are interested in understanding how genomes cope with severe chromosome damage, for example in the case of chromothripsis, where chromosomes break and are then reassembled in new configurations. Investigating A. vaga could help us to learn how cells manage large genetic issues. Moreover, its high resistance to radiation might also prove useful in research into extreme environments, such as the radiation hazards encountered on long space missions. However, these are ideas for future investigation; at present the rotifer's DNA repair mechanism cannot be used to protect people from radiation.</p><p>What is perhaps the most interesting aspect of this discovery is that the rotifer's remarkable ability could have developed for a very simple reason. Since an animal living in moss constantly undergoes periods of drying out and then getting wet again, the same mechanisms that protect its DNA when it is dehydrated might also enable it to survive radiation which would damage most other animals. Therefore, the rotifer probably did not evolve solely in order to resist radiation; instead, it became extremely good at coping with the difficult conditions it encounters, and radiation resistance was just a byproduct.</p><p>The case of Adineta vaga demonstrates that survival does not always mean avoiding damage; on some occasions it involves being able to recover from damage which appears to be impossible to repair. This small animal can survive having its chromosomes broken into many pieces, retain some of those pieces, pass them on to its offspring, and continue to repair them over successive generations. Although we generally regard DNA as something fragile that must always remain intact, the rotifer indicates an alternative possibility: perhaps a genome does not have to be perfect in order to survive, since sometimes the pieces last long enough for life to reassemble them, bit by bit, generation after generation.</p><p>Ream more at&nbsp;https://www.science.org/doi/10.1126/sciadv.aee0891</p>]]></description>
	<dc:creator>Jitendra Narayan</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/pages/view/9242/check-the-size-of-a-directory-free-disk-space</guid>
	<pubDate>Mon, 17 Mar 2014 02:35:32 -0500</pubDate>
	<link>https://bioinformaticsonline.com/pages/view/9242/check-the-size-of-a-directory-free-disk-space</link>
	<title><![CDATA[Check the Size of a directory &amp; Free disk space.]]></title>
	<description><![CDATA[<p>The amount of databases we bioinformatician deal are just HUGE &hellip; In such cases, we always need to check our server for free spaces etc. I planned this article to explains 2 simple commands that most bioinformatician want to know when they start using Linux / BioLinux. First: Size of a directory (du) and and second: free disk space that exists on your machine (df).</p><p><br /><strong>'du' &ndash; Check the size of a directory</strong></p><p><br />$ du<br />This command ( du) gives you a list of directories that exist in the current working directory along with their sizes in kilobytes (default). The last line of the output gives you the total size of the current directory including its subdirectories. <br /><br />$ du /home/jin1<br />The above command would give you the directory size of the directory /home/david<br /><br />$ du -h<br />The same &ldquo;du&rdquo;command with some flag gives you a better output than the default one. The option '-h' stands for human readable format. Therefore, in order to print the sizes of the files / directories in your desire notation use this time suffixed with a 'k' if its kilobytes and 'M' if its Megabytes and 'G' if its Gigabytes.<br /><br />$ du -ah<br />If you are interested in checking everything present in a folder use above mentioned command. It gives us not only the directories but also all the files that are present in the current directory. The &ldquo;-a&rdquo; flag displays the filenames along with the directory names in the output. <br /><br />$ du -c<br />This gives you a grand total as the last line of the output. So if your directory occupies 30MB the last 2 lines of the output would be 30M.<br /><br />$ du -s<br />Use this command to displays a summary of the directory size. It is the simplest way to know the total size of the current directory.<br /><br />$ du -S<br />This would display the size of the current directory excluding the size of the subdirectories that exist within that directory. So it basically shows you the total size of all the files that exist in the current directory.<br /><br />$ du --exculde=mp3<br />Several times it required to exclude some directory in our size calculation. In such cases the above command would display the size of the current directory along with all its subdirectories, but it would exclude all the files having the given pattern present in their filenames.</p><p><br /><strong>'df' - finding the disk free space / disk usage</strong><br /><br />$ df<br />Hmmm &hellip; now &ldquo;df&rdquo; command is really useful, and I guess you are going to use it over time. Typing the above command, outputs a table consisting of 6 columns. All the columns are very easy to understand. Remember that the 'Size', 'Used' and 'Avail' columns use kilobytes as the unit. The 'Use%' column shows the usage as a percentage which is also very useful.<br /><br />$ df -h<br />Displays the same output as the previous command but the '-h' indicates human readable format. Hence instead of kilobytes as the unit the output would have 'M' for Megabytes and 'G' for Gigabytes.<br /><br />Example: Linux installed on /dev/hda1<br />$ df -h | grep /dev/hda1</p><p><br />All right, this is not the only option to check the sizes and free spaces but there are a few more options that can be used with 'du' and 'df' . I will discuss it later.<br /><br /></p>]]></description>
	<dc:creator>Jitendra Narayan</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/42987/public-databases-for-bioinformatics</guid>
	<pubDate>Tue, 23 Mar 2021 05:32:15 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/42987/public-databases-for-bioinformatics</link>
	<title><![CDATA[Public Databases for Bioinformatics !]]></title>
	<description><![CDATA[<pre>https://www.nature.com/articles/s41467-020-17155-y<br><br>Server Infrastructure:

File Server:

dhara: Synology 3614 Storage Appliance
4 Core Xeon
108TB disk storage
10Gb ethernet to SCG3
Access atx: dhara:5000
Has btsync server (try it - its much better than dropbox)

Compute Servers:

nandi: Kundaje and Phi Server
24 intel cores
256GB RAM
500GB of SSD storage 
36TB RAID6 local storage
4 Intel Phi's (space for 4 more GPU's)


durga: Montgomery and sensitive data
24 intel cores
256GB RAM
500GB of SSD RAID0 storage 
60TB RAID6 local storage

mitra: Bassik and Web/DB Server
24 core
256GB RAM 
500GB of SSD RAID0 storage 
36TB RAID6 local storage

vayu: Kundaje GPU server
4 core
64GB RAM 
200GB of SSD storage 
8TB RAID10 local storage
4 Nvidia GTX 970 4GB GPUs

amold: Bickel and SGE server
32 AMD core
128GB RAM 
200GB of SSD storage 
12TB RAID5 local storage

wotan: Bickel and SGE server
64 AMD core
256GB RAM 
200GB of SSD storage 
12TB RAID5 local storage

Filesystem:

/users/$USER
default home directory
full backups nightly 
nfs mount to dhara
should store code, papers, and other highly processed data here

/mnt/data/
globally accessible data
should store common data here
e.g. genomes and indexes, annotations, ENCODE data  
if you dont want this to count towards your quote you must chown

/mnt/lab_data/$LAB/
lab accessible data
should store lab project data here 
e.g. ATAC-seq prediction data, enhancer prediction, motif calls

/srv/scratch/$USER
fast local storage
not backed up, but on raid and data will never be deleted
most analysis should be performed here

/srv/persistent/$USER
fast local storage
synced nightly, but not backed up
       ie if the hard drives fail or you delete something and notice 
       within 24 hours we can recover. Otherwise not. (vs home which is 
       properly backed up )  
intermediate analysis products that would be hard to recover should be stored here 
       e.g. stochastic analysis results that need to be kept so that paper 
       results can be reproduced

/srv/www/$LABNAME/
web accessible from mitra.stanford.edu
*NOT BACKED UP*

Some parallel programming patterns:

# gzip a bunch of files
parallel gzip -- *.FILESTOGZIP

# fork example in python:
(for more detailed examples look at 
 https://github.com/nboley/grit/ grit/lib/multiprocessing_utils.py)

import os
import time
import random

import multiprocessing

class ProcessSafeOPStream( object ):
    def __init__( self, writeable_obj ):
        self.writeable_obj = writeable_obj
        self.lock = multiprocessing.Lock()
        self.name = self.writeable_obj.name
        return
    
    def write( self, data ):
        self.lock.acquire()
        self.writeable_obj.write( data )
        self.writeable_obj.flush()
        self.lock.release()
        return
    
    def close( self ):
        self.writeable_obj.close()

def worker(queue, ofp):
    # Try without this
    random.seed()
    while True:
        i = queue.get()
        if i == 'FINISHED': return
        # simulate an expensive function
        x = random.random()
        time.sleep(x/10)
        print i, x
        ofp.write("%i\t%s\n" % (i, x))

NSIMS = 10000
NPROC = 25

# populate queue
todo = multiprocessing.Queue()
for i in xrange(NSIMS): todo.put(i)
for i in xrange(NPROC): todo.put('FINISHED')

ofp = ProcessSafeOPStream( open("output.txt", "w") )

pids = []
for i in xrange(NPROC):
    pid = os.fork()
    if pid == 0:
       worker(todo, ofp)
       os._exit(0)
    else:
       pids.append(pid)  

for pid in pids:
    os.waitpid(pid, 0)

ofp.close()

print "FINISHED"<br><br></pre>
<p>For use case 1 we obtained the following ENCODE and ROADMAP datasets&nbsp;<a href="https://www.encodeproject.org/files/ENCFF446WOD/@@download/ENCFF446WOD.bed.gz">https://www.encodeproject.org/files/ENCFF446WOD/@@download/ENCFF446WOD.bed.gz</a>,&nbsp;<a href="https://www.encodeproject.org/files/ENCFF546PJU/@@download/ENCFF546PJU.bam">https://www.encodeproject.org/files/ENCFF546PJU/@@download/ENCFF546PJU.bam</a>,&nbsp;<a href="https://www.encodeproject.org/files/ENCFF059BEU/@@download/ENCFF059BEU.bam">https://www.encodeproject.org/files/ENCFF059BEU/@@download/ENCFF059BEU.bam</a>. Blacklisted regions were obtained from&nbsp;<a href="http://mitra.stanford.edu/kundaje/akundaje/release/blacklists/hg38-human/hg38.blacklist.bed.gz">http://mitra.stanford.edu/kundaje/akundaje/release/blacklists/hg38-human/hg38.blacklist.bed.gz</a>. The human genome version hg38 was obtained from&nbsp;<a href="http://hgdownload.cse.ucsc.edu/goldenPath/hg38/bigZips/hg38.fa.gz">http://hgdownload.cse.ucsc.edu/goldenPath/hg38/bigZips/hg38.fa.gz</a>.</p>
<p>For use case 2 we used the set of narrowPeak files summarized in&nbsp;<a href="https://github.com/wkopp/janggu_usecases/tree/master/extra/urls.txt">https://github.com/wkopp/janggu_usecases/tree/master/extra/urls.txt</a>&nbsp;(archived version v1.0.1). The human genome version hg19 was obtained from&nbsp;<a href="http://hgdownload.cse.ucsc.edu/goldenPath/hg19/bigZips/hg19.fa.gz">http://hgdownload.cse.ucsc.edu/goldenPath/hg19/bigZips/hg19.fa.gz</a></p>
<p>For use case 3 we used the ENCODE datasets&nbsp;<a href="https://www.encodeproject.org/files/ENCFF591XCX/@@download/ENCFF591XCX.bam">https://www.encodeproject.org/files/ENCFF591XCX/@@download/ENCFF591XCX.bam</a>,&nbsp;<a href="https://www.encodeproject.org/files/ENCFF736LHE/@@download/ENCFF736LHE.bigWig">https://www.encodeproject.org/files/ENCFF736LHE/@@download/ENCFF736LHE.bigWig</a>,&nbsp;<a href="https://www.encodeproject.org/files/ENCFF177HHM/@@download/ENCFF177HHM.bam">https://www.encodeproject.org/files/ENCFF177HHM/@@download/ENCFF177HHM.bam</a>&nbsp;as we as the GENCODE annotation v29 from&nbsp;<a href="ftp://ftp.ebi.ac.uk/pub/databases/gencode/Gencode_human/release_29/gencode.v29.annotation.gtf.gz">ftp://ftp.ebi.ac.uk/pub/databases/gencode/Gencode_human/release_29/gencode.v29.annotation.gtf.gz</a>.</p><p>Address of the bookmark: <a href="http://mitra.stanford.edu/" rel="nofollow">http://mitra.stanford.edu/</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>

<item>
  <guid isPermaLink='true'>https://bioinformaticsonline.com/opportunity/view/9441/jrf-at-gautam-buddha-university</guid>
  <pubDate>Thu, 27 Mar 2014 03:53:57 -0500</pubDate>
  <link></link>
  <title><![CDATA[JRF at Gautam Buddha University]]></title>
  <description><![CDATA[
<p>Gautam Buddha University (GBU) Noida invites applications for the follow posts<br />2014 March Advertisement from Gautam Buddha University (GBU)<br />Junior Research Fellow (JRF)<br />No. of Positions:  01<br />Educational Qualifications:<br />Master degree in any discipline of Life Science with NET qualified or valid GATE score. Desirable Qualification: Preference will be given to candidates having research experience in Bioinformatics<br />Experience:</p>

<p>(details of experience required)<br />Pay Scale:<br />INR Rs.12000/-P.M. + HRA<br />Category:<br />Science and Research Jobs<br />How To Apply:<br />The interested candidates should report for the Interview on 31st<br />March, 2014 at 10:00 am in the Conference Room of Dean, School of Biotechnology, First floor, Gautam Buddha University, Greater<br />Noida. Interested candidates may also send their resume to undersigned by post-mail/e-mail shaktis@gbu.ac.in or shaktisahi@gmail.com. No TA and DA will be paid for appearing for the interview<br />Download Official Notification:</p>

<p>http://www.gbu.ac.in/Recruitment/JRF_advertisement_DSTProject_Shakti_24March14.pdf</p>
]]></description>
</item>

<item>
  <guid isPermaLink='true'>https://bioinformaticsonline.com/opportunity/view/9598/junior-research-fellowship-at-gb-pant-university</guid>
  <pubDate>Thu, 03 Apr 2014 12:29:46 -0500</pubDate>
  <link></link>
  <title><![CDATA[Junior Research Fellowship at G.B. PANT UNIVERSITY]]></title>
  <description><![CDATA[
<p>DEPARTMENT OF MOLECULAR BIOLOGY &amp; GENETIC ENGINEERING<br />COLLEGE OF BASIC SCIENCE AND HUMANITIES<br />G.B. PANT UNIVERSITY OF AGRICULTURE AND TECHNOLOGY<br />PANTNAGAR -263145, UTTARAKHAND</p>

<p>No. CBSH/MBGE/356</p>

<p>Subject: Advertisement for the award of Junior Research Fellowship.</p>

<p>Applications are invited for award of one Junior Research Fellowship on a consolidated fellowship of Rs. 12,000/- pm in the project “Bioinformatics Sub-DIC ”, under the Coordinatorship Dr. Anil Kumar. The fellowship is purely temporary and may continue till the duration of the project or maximum three years which ever is earlier. The appointment shall be given on six monthly review basis.</p>

<p>ESSENTIAL QUALIFICATION</p>

<p>M.Sc. Bioinformatics having research experience on In silico experimentation.</p>

<p>Candidates possessing the above qualifications may submit their application on<br />plain paper in the following format to the undersigned latest 18 April, 2014 the interviews will be held on 19 April, 2014 at 11.00 AM in the office of the undersigned. No separate letter for interview will be issued or any TA/DA will be paid for attending the interview.</p>

<p>Advertisement: http://www.gbpuat.ac.in/01042014_18april14_Advertisement%20for%20JRF%20Position,%20BI.pdf</p>
]]></description>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/34519/bandage-interactive-visualization-of-de-novo-genome-assemblies</guid>
	<pubDate>Mon, 04 Dec 2017 10:09:37 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/34519/bandage-interactive-visualization-of-de-novo-genome-assemblies</link>
	<title><![CDATA[Bandage: interactive visualization of de novo genome assemblies]]></title>
	<description><![CDATA[<p>Bandage (a Bioinformatics Application for Navigating&nbsp;<em>De&nbsp;novo</em>&nbsp;Assembly Graphs Easily) is a tool for visualizing assembly graphs with connections. Users can zoom in to specific areas of the graph and interact with it by moving nodes, adding labels, changing colors and extracting sequences. BLAST searches can be performed within the Bandage graphical user interface and the hits are displayed as highlights in the graph. By displaying connections between contigs, Bandage presents new possibilities for analyzing&nbsp;<em>de novo</em>&nbsp;assemblies that are not possible through investigation of contigs alone.</p>
<p><strong>Availability and implementation:</strong>&nbsp;Source code and binaries are freely available at&nbsp;<a href="https://github.com/rrwick/Bandage" target="pmc_ext">https://github.com/rrwick/Bandage</a>. Bandage is implemented in C++ and supported on Linux, OS X and Windows. A full feature list and screenshots are available at&nbsp;<a href="http://rrwick.github.io/Bandage" target="pmc_ext">http://rrwick.github.io/Bandage</a>.</p><p>Address of the bookmark: <a href="http://rrwick.github.io/Bandage/" rel="nofollow">http://rrwick.github.io/Bandage/</a></p>]]></description>
	<dc:creator>Shruti Paniwala</dc:creator>
</item>

<item>
  <guid isPermaLink='true'>https://bioinformaticsonline.com/opportunity/view/9859/bioinformatics-jrfsrf-position-at-university-of-hyderabad</guid>
  <pubDate>Tue, 15 Apr 2014 20:07:52 -0500</pubDate>
  <link></link>
  <title><![CDATA[Bioinformatics JRF/SRF position at University of Hyderabad]]></title>
  <description><![CDATA[
<p>UNIVERSITY OF HYDERABAD SCHOOL OF LIFE SCIENCES </p>

<p>Applications are invited from qualified individuals for a JRF/SRF position (sponsored by DBT/DST) at Prof. Jagan Pongubala’s laboratory, University of Hyderabad. Dr. Pongubala’s laboratory is investigating the molecular pathways that control the development of innate and adaptive immune cell types utilizing a combination of genetic, molecular and computational approaches.</p>

<p>JRF/SRF</p>

<p>Masters degree in Bioinformatics  (M.Sc./M.Tech.)</p>

<p>Rs. 12,000+HRA<br />Rs. 16,000+HRA</p>

<p>Initial appointment is for one year and  subjected to renewal up to 2 years</p>

<p>Candidates selected for the above position would have a choice to work on computational biology or experimental  biology. Candidates interested to work on computational biology are expected to perform high-throughput sequencing  (NGS) data analysis and should have a strong background in Bioinformatics &amp; Computational Biology, good  programming skills particularly Perl, Python, R and work experience in Linux environment.</p>

<p>Candidates interested to work on experimental biology should have work experience in techniques that are routinely  used in molecular biology and mammalian cell culture. A basic knowledge of bioinformatics is also desired. </p>

<p>Applicants for the above positions should have a Masters degree (M.Tech/M.Sc) with an aggregate marks greater  than 70% or a 7.5 CGPA. Candidates having JRF-fellowship through CSIR/UGC/ICMR/DBT will be encouraged  to enroll into Ph.D. program. The interested candidates having excellent organizational skills and the ability to work  in a team environment with an aspiration to learn new techniques and explore new scientific areas are requested to generate their resume using the link https://cvmkr.com/CV/new#0 and forward to pongubalajagan@gmail.com</p>

<p>Review of applications will begin immediately and continue until the position is filled. Eligible candidates will be called for an interview. No TA/ DA will be paid for attending the interview or at the time of joining the post. Applicants should note that the appointment is purely temporary and subjected to renewal up to three years and there is no Right to Claim for any regular appointment with the University.</p>

<p>Corresponding address: Jagan Pongubala, Ph.D.<br />Department of Animal Sciences<br />School of Life Sciences, Room:S44<br />University of Hyderabad<br />Gachibowli, Hyderabad 500046</p>

<p>Advertisement: https://www.uohyd.ac.in/images/recruitment/jrf-srf_130414.pdf</p>
]]></description>
</item>

</channel>
</rss>