<?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/23838?offset=60</link>
	<atom:link href="https://bioinformaticsonline.com/related/23838?offset=60" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/44559/metagraph-ultra-scalable-framework-for-dna-search-alignment-assembly</guid>
	<pubDate>Sat, 08 Jun 2024 16:15:25 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/44559/metagraph-ultra-scalable-framework-for-dna-search-alignment-assembly</link>
	<title><![CDATA[MetaGraph: Ultra Scalable Framework for DNA Search, Alignment, Assembly]]></title>
	<description><![CDATA[<p><span>The MetaGraph framework</span><span>&nbsp;is designed to work with a wide range of input data sets, indexing from a few samples up to the contents of entire archives with hundreds of thousands of records. The indexing workflow always follows the same principle, transforming single input samples into error-removed, refined sample graphs, which are then merged into a joint metagraph index. Each input sample is annotated in the joint index as a subgraph. This graph index enriched with metadata can then be used for downstream applications such as&nbsp;</span><a href="https://metagraph.ethz.ch/#query">sequence search</a><span>&nbsp;or&nbsp;</span><a href="https://metagraph.ethz.ch/#assembly">differential assembly</a><span>.</span></p>
<p><span>Searcg link&nbsp;https://metagraph.ethz.ch/search&nbsp;</span></p>
<p><span>Pre-print&nbsp;https://www.biorxiv.org/content/10.1101/2020.10.01.322164v4&nbsp;</span></p><p>Address of the bookmark: <a href="https://metagraph.ethz.ch/" rel="nofollow">https://metagraph.ethz.ch/</a></p>]]></description>
	<dc:creator>Abhi</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/file/view/42693/dna-rna-meme</guid>
	<pubDate>Thu, 28 Jan 2021 11:23:14 -0600</pubDate>
	<link>https://bioinformaticsonline.com/file/view/42693/dna-rna-meme</link>
	<title><![CDATA[DNA RNA MEME]]></title>
	<description><![CDATA[<p>Explain the DNA and RNA with picture ...</p>]]></description>
	<dc:creator>Neel</dc:creator>
	<enclosure url="https://bioinformaticsonline.com/file/download/42693" length="41627" type="image/jpeg" />
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/videolist/watch/4155/genetics-for-fun-and-profit-andrew-hessel-at-tedxvilnius</guid>
	<pubDate>Sun, 01 Sep 2013 19:15:06 -0500</pubDate>
	<link>https://bioinformaticsonline.com/videolist/watch/4155/genetics-for-fun-and-profit-andrew-hessel-at-tedxvilnius</link>
	<title><![CDATA[Genetics for Fun and Profit: Andrew Hessel at TEDxVilnius]]></title>
	<description><![CDATA[<iframe width="" height="" src="https://www.youtube-nocookie.com/embed/A2h_JW7X_HE" frameborder="0" allowfullscreen></iframe>Andrew Hessel co-chairs the Bioinformatics and Biotechnology track at the Singularity University, an institution founded by futurist Ray Kurzweil and X Prize Foundation CEO Peter Diamandis, with sponsorship from world-leading organizations that include Google, Autodesk, and NASA. He is also the founder of the Pink Army Cooperative, a venture aiming to make open source personalized cancer therapies. His work has been featured in The New York Times, Futurist Magazine, H+, and Wired News.

In the spirit of ideas worth spreading, TEDx is a program of local, self-organized events that bring people together to share a TED-like experience. At a TEDx event, TEDTalks video and live speakers combine to spark deep discussion and connection in a small group. These local, self-organized events are branded TEDx, where x = independently organized TED event. The TED Conference provides general guidance for the TEDx program, but individual TEDx events are self-organized.* (*Subject to certain rules and regulations)]]></description>
	
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/fun/view/14036/introduction-to-programming-write-short-programs-that-generate-graphics-and-animation</guid>
	<pubDate>Thu, 14 Aug 2014 23:29:04 -0500</pubDate>
	<link>https://bioinformaticsonline.com/fun/view/14036/introduction-to-programming-write-short-programs-that-generate-graphics-and-animation</link>
	<title><![CDATA[Introduction to programming. Write short programs that generate graphics and animation.]]></title>
	<description><![CDATA[<p>Introduction to programming. Write short programs that generate graphics and animation.</p><p>http://funprogramming.org/</p>]]></description>
	<dc:creator>Ram Yash Pal</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/file/view/38029/biologist-versus-computational-biologist</guid>
	<pubDate>Mon, 29 Oct 2018 04:23:24 -0500</pubDate>
	<link>https://bioinformaticsonline.com/file/view/38029/biologist-versus-computational-biologist</link>
	<title><![CDATA[Biologist versus computational biologist !]]></title>
	<description><![CDATA[<p>This is how it work :)</p>]]></description>
	<dc:creator>Abhimanyu Singh</dc:creator>
	<enclosure url="https://bioinformaticsonline.com/file/download/38029" length="69305" type="image/png" />
</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/bookmarks/view/34482/ribbon-visualizing-complex-genome-alignments-and-structural-variation</guid>
	<pubDate>Wed, 29 Nov 2017 07:40:22 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/34482/ribbon-visualizing-complex-genome-alignments-and-structural-variation</link>
	<title><![CDATA[Ribbon: Visualizing complex genome alignments and structural variation:]]></title>
	<description><![CDATA[<p>Ribbon can be used for long reads, short reads, paired-end reads, and assembly/genome alignments. Instructions for each data format are available by clicking on "instructions" in each tab on the right.</p>
<p>Local installation:</p>
<p>You can install Ribbon locally from Github by following the instructions here:&nbsp;<a href="https://github.com/MariaNattestad/ribbon" target="_blank">https://github.com/MariaNattestad/Ribbon</a></p><p>Address of the bookmark: <a href="http://genomeribbon.com/" rel="nofollow">http://genomeribbon.com/</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/34567/jobtree-based-python-wrapper-to-run-the-genome-simulation-tool-suite-evolver</guid>
	<pubDate>Fri, 08 Dec 2017 16:26:32 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/34567/jobtree-based-python-wrapper-to-run-the-genome-simulation-tool-suite-evolver</link>
	<title><![CDATA[jobTree based python wrapper to run the genome simulation tool suite Evolver]]></title>
	<description><![CDATA[<p><span>evolverSimControl</span><span>&nbsp;(</span><span>eSC</span><span>) can be used to simulate multi-chromosome genome evolution on an arbitrary phylogeny (</span><a href="http://evolution.genetics.washington.edu/phylip/newicktree.html">Newick format</a><span>). In addition to simply running evolver,&nbsp;</span><span>eSC</span><span>&nbsp;also automatically creates statistical summaries of the simulation as it runs including text and image files. Also included are convenience scripts to: check on a running simulation and see detailed status and logging information; extract fasta sequence files from the leaf nodes of a completed simulation; extract pairwise multiple alignment files (</span><a href="http://genome.ucsc.edu/FAQ/FAQformat.html#format5">.maf</a><span>) from leaf and branch nodes from a completed simulation and with the help of&nbsp;</span><a href="https://github.com/dentearl/mafTools/">mafJoin</a><span>, join them together into a single maf covering the entire simulation.</span></p><p>Address of the bookmark: <a href="https://github.com/dentearl/evolverSimControl" rel="nofollow">https://github.com/dentearl/evolverSimControl</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/34620/mash-fast-genome-and-metagenome-distance-estimation-using-minhash</guid>
	<pubDate>Tue, 12 Dec 2017 17:30:12 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/34620/mash-fast-genome-and-metagenome-distance-estimation-using-minhash</link>
	<title><![CDATA[Mash: fast genome and metagenome distance estimation using MinHash]]></title>
	<description><![CDATA[<p>Mash is normally distributed as a dependency-free binary for Linux or OSX (see&nbsp;<a href="https://github.com/marbl/Mash/releases">https://github.com/marbl/Mash/releases</a>). This source distribution is intended for other operating systems or for development. Mash requires c++11 to build, which is available in and GCC &gt;= 4.8 and OSX &gt;= 10.7.</p>
<p>See&nbsp;<a href="http://mash.readthedocs.org/">http://mash.readthedocs.org</a>&nbsp;for more information.</p><p>Address of the bookmark: <a href="https://github.com/marbl/Mash/releases" rel="nofollow">https://github.com/marbl/Mash/releases</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>

</channel>
</rss>