BOL

How can I generate a Venn diagram in R? by UCLA is also useful http://www.ats.ucla.edu/stat/r/faq/venn.htm

Six-way Venn diagram

https://stackoverflow.com/questions/32440128/nice-looking-five-sets-venn-diagrams

Bioinformatics funding for Japan

Promoting science and technology is a key engine to materialize a bright future of Asia and it is vitally important to enhance the exchange of youths in Asian countries and Japan who will play a crucial role in the field of science and technology.

Based on this concept, “Japan-Asia Youth Exchange Program in Science” (SAKURA Exchange Program in Science) is the program for enhancing exchanges between Asia and Japan of the youths who will play a crucial role in the future field of science and technology through the close collaboration of industry-academia-government by facilitating short-term visits of competent Asian youths to Japan. This program aims at raising the interest of Asian youths toward the leading Japanese science and technologies at Japanese universities, research institutions and private companies.

More at http://www.ssp.jst.go.jp/EN/outline/index.html

The Arturo Falaschi ICGEB Fellowship Programmes for PhD, PostDoc and Short term courses

The Arturo Falaschi ICGEB Fellowships programme offers long and short-term fellowships for scientists who are nationals of ICGEB Member States to perform research in Trieste, New Delhi or Cape Town.

More at http://www.icgeb.org/fellowships.html

Try this https://www.birac.nic.in/big.php if you dream ur company

https://www.uniraj.ac.in/uic/

Reapr is a tool trying to find explicit errors in the assembly based on incongruently mapped reads. It is heavily based on too low span coverage, or reads mapping too far or too close to each other. The program will also break up contigs/scaffolds at spurious sites to form smaller (but hopefully correct) contigs. Reapr runs pretty slowly, sadly,

Reapr is a bit fuzzy with contig names, but luckily it’s given us a tool to check if things are ok before we proceed! The command reapr facheck <assembly.fasta> will tell you if everything’s ok! in this case, no output is good output, since the only output from the command is the potential problems with the contig names. If you run into any problems, run reapr facheck <assembly.fasta> <renamed_assembly.fasta>, and you will get an assembly file with renamed contigs.

Once the names are ok, we continue:

The first thing we reapr needs, is a list of all “perfect” reads. This is reads that have a perfect map to the reference. Reapr is finicky though, and can’t use libraries with different read lengths, so you’ll have to use assemblies based on the raw data for this. Run the command reapr perfectmap to get information on how to create a perfect mapping file, and create a perfect mapping called <assembler>_perfect. This should take about a minute.

The next tool we need is reapr smaltmap which creates a bam file of read-pair mappings. Do the same thing you did with perfectmap and create an output file called <assembler>_smalt.bam. This should take about twenty minutes.

Finally we can use the smalt mapping, and the perfect mapping to run the reapr pipeline. Run reapr pipeline to get help on how to run, and then run the pipeline. Store the results in reapr_<assembler>. This should take about ten minutes.

There are several checks you can do after running Reapr (detailed here) but for now we’ll stick to looking at the split output file, called 04.break.broken_assembly.fa. Use this file together with the original assembly to generate a quast report. How does the results look after reapr?