BOL: Related items

ANItools web: a web tool for fast genome comparison within multiple bacterial strains

Jit — Wed, 14 Nov 2018 04:34:23 -0600

ANItools is a software package written by PERL scripts that can be run in a Linux/Unix system. If you want to compare bacterial genomes and calculate their average nucleotide identity (ANI), you could download and run this program directly. Or you could send us the genome sequence by email. Then we will do the analysis work for you.

https://academic.oup.com/database/article/doi/10.1093/database/baw084/2630454

Address of the bookmark: http://ani.mypathogen.cn/

Dash: a web application framework that provides pure Python abstraction around HTML, CSS, and JavaScript.

Jit — Tue, 05 Nov 2019 06:39:48 -0600

Dash is a web application framework that provides pure Python abstraction around HTML, CSS, and JavaScript.

Dash Bio is a suite of bioinformatics components that make it simpler to analyze and visualize bioinformatics data and interact with them in a Dash application.

The source can be found on GitHub at plotly/dash-bio.

These docs are using Dash Bio version 0.1.4.

Address of the bookmark: https://dash.plot.ly/dash-bio

GSP4PDB: a web tool to visualize, search and explore protein-ligand structural patterns

Neel — Sun, 15 Mar 2020 03:41:12 -0500

GSP4PDB is a user-friendly and efficient application to search and discover new patterns of protein-ligand interaction.

GSP4PDB is part of the services provided by the Bioinformatic Group of the University of Talca

http://gdblab.com/gsp4pdb/gsp4pdb2/

https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-020-3352-x

Address of the bookmark: http://gdblab.com/gsp4pdb/gsp4pdb2/

Firecrawl: The Web Data API for AI - Turn entire websites into LLM-ready markdown or structured data

BioStar — Thu, 28 Aug 2025 02:34:28 -0500

Firecrawl is an API service that takes a URL, crawls it, and converts it into clean markdown or structured data. We crawl all accessible subpages and give you clean data for each. No sitemap required. Check out our documentation.

Pst. hey, you, join our stargazers :)

Address of the bookmark: https://github.com/firecrawl/firecrawl

List of cancer genomics research web resources !

biogeek — Wed, 27 Dec 2017 20:33:09 -0600

Major web resources for cancer genomics research

CGHub
https://cghub.ucsc.edu/
Comprehensive data repository; huge data size

EGA
https://www.ebi.ac.uk/ega/
Comprehensive data repository; huge data size

COSMIC
http://cancer.sanger.ac.uk
Largest somatic mutation database; genome sequencing paper curation

CPRG
http://www.broadinstitute.org/software/cprg
Interface for cancer program resources

GDAC
http://gdac.broadinstitute.org/
Data analysis; automatic pipelines; user-friendly reports

SNP500Cancer
http://snp500cancer.nci.nih.gov
Sequence and genotype verification of SNPs

canEvolve
www.canevolve.org/
Comprehensive analysis of tumor profile; Data from 90 studies involving more than 10,000 patients

MethyCancer
http://methycancer.psych.ac.cn
Relationship among DNA methylation, gene expression and cancer

SomamiR
http://compbio.uthsc.edu/SomamiR/
Correlation between somatic mutation and microRNA; genome-wide displaying

cBioPortal
http://www.cbioportal.org/public-portal/
Graphical summaries; gene alteration; processed data; visualization

UCSC Cancer Genomics Browser
https://genome-cancer.soe.ucsc.edu/
Clinical information; gene expression; copy number variation; visualization

CGWB
https://cgwb.nci.nih.gov/
Visualization; gene mutation and variation; automated analysis pipeline

GDSC
http://www.cancerrxgene.org
Drug sensitivity information; drug response information

canSAR
https://cansar.icr.ac.uk/
Multidisciplinary information; drug discovery

NONCODE
http://www.noncode.org/ ncRNAs;
lncRNAs; up-to-date and comprehensive resource

Five unique traits of effective computational biologist

Jitendra Narayan — Thu, 11 Jul 2013 13:12:51 -0500

Bioinformatics research is driven by large set of software, scripts, and tools to analyse gigantic biological data. Being a great biological programmer or bioinformatician involves more than writing code that works. The biological programmers who rise to the top ranks of their profession are not only good programmer but also expert in biological stuff. Moreover, In order to be a good and effective biological programmer, you need to possess a combination of traits that allow your computational as well as biological skill, experience, and knowledge to produce working code. There are some technically skilled biological programmers who will never be effective because they lack the other important traits needed. Here are top five traits that are necessary to become a great biological programmer.

1. Learn and get updated

Some of the bad biological programmers only learn new technical or non-technical things when it’s absolutely necessary. The good biological programmers learn new technical skills proactively. But great biological programmers not only learn new technical skills on their own but also learn non-technical skills, and have an open mind to sources of knowledge that others may shut out.

In other concrete term, the bad biological programmer learn Perl's regular expression when they started a project on comparative genomics; the good biological programmer learned it a year before because it looked interesting; and the great biological programmer also read about the BioPerl packages, genomics, DNA string, genomic theories, or some similar course of study so that they could understand the results and explain it biologically.

2. Not a merely coder!!!

I often encountered with biological programmer who call themself a hard-core computer programmer and avoid biology. I can almost guarantee that if you are one of them then you are not doing research but merely writing "dry" codes.

According to my supervisor most of the computational biologist, don't know what they are doing biologically. Even they struggle to explain their own programs output and results. Therefore, It is highly advisable to learn basic of biology which can assist you to explain the result and understand your discovery. Always remember you are a researcher not a coder.

3. Be Social with biologist

The computational biologist spends most of the time in from of computers, writing codes. They always think their job is to produce working codes, not technical research perfections. But, they are completely wrong. You should not forget that apart from your computational skills you also need some biologist, other than your supervisor, to explain and make you understand the complex biological mechanism.

I highly recommend your to interact with biotech researchers and learn how do they explain their one graph (which they generally produce after one year of work) biologically. Remember, the origin of your research project is complex biological phenomenon, which is more complex than that of your limited programming rules.

4. Do not search, research for answers

Researching for answers means more than typing several keywords into a search engine or posting a question at Stack Overflow or the BioStars forums. I have entered problems into search engines that generate no results, and every question I posted on Stack Overflow or the BioStars forums never got anything resembling an answer, yet I solved the issues and moved on. I’m not a magician — I just know how to find answers or discover root causes.

Many problems are situational, and if you depend on search engines and forums, you can waste a lot of time going down a rabbit hole and possibly never getting a solution. Learn to perform root cause analysis, learn enough about the underlying system to look for other clues and solutions, and learn to take a long distance view of an issue before deep diving into it.

5. Love and defend your research

You cannot rise to the top in this research profession without loving your work. There are some very good “it’s just a job” biological programmers (I’ve been one at times), but if that is your outlook, you won’t be willing to do whatever it takes to succeed. This idea gets a lot of folks in a huff, because they feel it is a personal insult. “I’m a good programmer, but I have other priorities and can’t make work my life.” I understand completely; I have other priorities too. As much as I hate to say it, when I am passionate about my work, I am willing (though not eager) to abandon my other priorities to finish the job. It is not an insult to say that if you aren’t willing to pull out all the stops you can’t be the best, it is a fact.

You must be passionate about more than programming — you must also be excited about your research, the tools and technology you are using, and so on. I have seen very good and even great biological programmers operating at mediocre levels because something was not a good fit, such as they hated the project or were using a technology they disliked. Therefore, like your research project and get excited about your discoveries. You have not only to discover but also defend your finding with scientific words.

Thanks to all of you for reading.

Perl in a day !!

Jitendra Narayan — Sat, 10 Aug 2013 21:14:03 -0500

This pdf based tutorial in good resource to understand the basic of Perl in a day

http://ritg.med.harvard.edu/training/perl/RC_Perl_Intro.pdf

Which Perl distribution should I choose for bioinformatics study : ActivePerl, Strawberry Perl, DWIM Perl, Citrus Perl ?

Manshi Raghubanshi — Wed, 14 Aug 2013 15:43:06 -0500

I'm new to bioinformatics and recently started learning Perl. I found several rival distributions available for Windows platform, which confuse me at the begining.

I google it and found that Strawberry comes with additional dev tools to compile CPAN modules if necessary. Whereas ActivePerl has a lot of prepackaged modules which are easier to install with PPM. In addition, DWIM Perl contains the standard Perl and a lot of extension and Citrus Perl is a binary distribution of Perl created for GUI application developers.

Now, I wonder what should I pick to get started?

Note: I am going to use BioPerl in near future.

http://dwimperl.com/

http://www.activestate.com/activeperl

http://www.citrusperl.com/

http://strawberryperl.com/

Clean the FASTA file

Jit — Thu, 03 Oct 2013 14:19:14 -0500

Mostly FASTA file contain NNN characters, which can be replace by random A T G C character with this perl script. It also print the FASTA sequence name, N's counts, nucleotide count and percentage details at command prompt/standard output.

Perl One liner basics !!

Abhimanyu Singh — Sun, 24 May 2015 09:28:33 -0500

Perl has a ton of command line switches (see perldoc perlrun), but I'm just going to cover the ones you'll commonly need to debug code. The most important switch is -e, for execute (or maybe "engage" :) ). The -e switch takes a quoted string of Perl code and executes it. For example:

$ perl -e 'print "Hello, World!\n"'
Hello, World!

It's important that you use single-quotes to quote the code for -e. This usually means you can't use single-quotes within the one liner code. If you're using Windows cmd.exe or PowerShell, you must use double-quotes instead.

I'm always forgetting what Perl's predefined special variables do, and often test them at the command line with a one liner to see what they contain. For instance do you remember what $^O is?

$ perl -e 'print "$^O\n"'
linux

It's the operating system name. With that cleared up, let's see what else we can do. If you're using a relatively new Perl (5.10.0 or higher) you can use the -E switch instead of -e. This turns on some of Perl's newer features, like say, which prints a string and appends a newline to it. This saves typing and makes the code cleaner:

$ perl -E 'say "$^O"'
linux

Pretty handy! say is a nifty feature that you'll use again and again.