<?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: All site blogs]]></title>
	<link>https://bioinformaticsonline.com/blog/all?offset=160</link>
	<atom:link href="https://bioinformaticsonline.com/blog/all?offset=160" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/22995/bioinformatics-phd-postdoc-job-rejection</guid>
	<pubDate>Thu, 02 Jul 2015 08:52:46 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/22995/bioinformatics-phd-postdoc-job-rejection</link>
	<title><![CDATA[Bioinformatics PhD / PostDoc / Job Rejection]]></title>
	<description><![CDATA[<div><p>While your PhD or PostDoc application, it is more common that you got rejected by many professors. Don't disappoint reply it calmly.</p><p><img src="http://bioinformaticsonline.com/mod/photo/rejected1.png" alt="image" style="border: 0px; border: 0px;"></p><p>In grad school, I shared a house with three Bioinformatics PhD students. One, when he applied to a particular professor, received a letter that said, essentially, "If you are applying because you want to enrich yourself, great. If you are applying because you want a job, you should know that you won't get one." I am trying to tell you this is because if you, with a good background in Bioinformatics, are passing up opportunities, you must be a strong candidate in many areas. Enrich yourself.<br /><br /> So, my suggestion is take a deep breath, forgot about all. Don&rsquo;t take it personally. It's been usual processes while hunting for a good lab and professor. Take is positive, I am not sure why they reject, but don't worry perhaps the lab don't deserve you. Always remember there are billions of reasons not to hire someone for projects, especially in a research sector.<br /><br /> My suggestion, please do not whine about how you were a great research candidate for the post, and you just can't understand why they were so stupid as to have rejected you! This feeling will not win you any points in research, community. Especially, when in todays socially connected era everyone is linked. Remember, a nice E-mail saying, "I really wished to working with you on this project and I hope we cross paths again," is all you need to send to the professor. Send a thank you note to the professor. Thank them for the time they spend to judge you. In the future, If you and the professor (of your dream) are attending a bioinformatics conference, invite him/her to lunch (please remember to pay the bill). In today evolving scientific ere, always remember to build your solid network in order to get a job of interest. Join all possible networking sites like LinkedIn, ResearchGate, Acamedia, FB for the same reason. You as a researcher always build a bridge with student/researcher/colleague/professor who have the research potential to lead in research and hire you. Just because you didn't get this project, doesn't mean there isn't another that will open up in couple of month.<br /><br /> Mostly, jobs that are hard to get are hard to get. Only you can decide if the continued sacrifices are worth the expected payout. If it is, keep on plowing. Build relationships. Attend conferences.</p><p>Image ref @ JaSonYa</p></div>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/22454/one-page-r-survival-guide</guid>
	<pubDate>Thu, 28 May 2015 21:10:12 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/22454/one-page-r-survival-guide</link>
	<title><![CDATA[One page R survival guide !!]]></title>
	<description><![CDATA[<p><span style="font-style: normal; color: #000000; float: none;">There any many of the documents have been developed and tested by scientist around the world. I found this one really useful. The data used is available for download as<span>&nbsp;</span></span><a href="http://onepager.togaware.com/data.zip">data.zip</a><span style="font-style: normal; color: #000000; float: none;">.</span></p><p><span style="font-style: normal; color: #000000; float: none;">Reference@http://www.datasciencecentral.com/profiles/blogs/one-page-r-a-survival-guide-to-data-science-with-r</span></p><ul>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Templates for the Data Scientist<ol style="margin: 0px; padding: 0px 0px 0px 1.5em; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">A Template for Preparing Data:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/DataO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/DataO.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">A Template for Building Models:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/ModelsO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/ModelsO.R">R</a></li>
</ol></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Getting Started as a Data Scientist<ol style="margin: 0px; padding: 0px 0px 0px 1.5em; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Getting Started with R and Rattle:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/StartL.pdf">Lecture</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/StartG.pdf">Laboratory</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Introducing and Interacting with R:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/IntroRL.pdf">Lecture</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/IntroRR.pdf">Laboratory</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">BasicR - OnePage(R) - Writing R scripts</li>
</ol></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Dealing With Data<ol style="margin: 0px; padding: 0px 0px 0px 1.5em; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Read Data into R:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/ReadO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/ReadO.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Explore and Summarise Data:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/SummaryO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/SummaryO.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Transform Data:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/TransformO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/TransformO.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><a href="http://togaware.com/onepager/DateTimeRB"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Dealing with Dates and Time:</span></a><span>&nbsp;</span>(<a href="http://onepager.togaware.com/DateTimeR.pdf">PDF</a>,<span>&nbsp;</span><a href="http://onepager.togaware.com/DateTimeR.R">R</a>) Dates and Time</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Visualising Data with GGPlot2:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/GGPlot2O.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/GGPlot2O.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Visualising Data with Maps</span><span>&nbsp;</span>*<a href="http://togaware.com/onepager/MapsO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/MapsO.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Spatial<span>&nbsp;</span>(R) Spatial Analysis</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Handling Big Data</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/BigDataO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/BigData.R">R</a></li>
</ol></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Descriptive Analytics<ol style="margin: 0px; padding: 0px 0px 0px 1.5em; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Cluster Analysis:</span><span>&nbsp;</span>*<a href="http://togaware.com/onepager/ClustersL.pdf">Lecture</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/ClustersO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/Clusters.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Association Analysis:</span><span>&nbsp;</span>*<a href="http://togaware.com/onepager/ARulesL.pdf">Lecture</a></li>
</ol></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Predictive Analytics<ol style="margin: 0px; padding: 0px 0px 0px 1.5em; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Decision Trees:</span><span>&nbsp;</span>*<a href="http://togaware.com/onepager/DTreesL.pdf">Lecture</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/DTreesO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/DTreesO.R">R</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/DTreesG.pdf">Rattle</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Ensembles of Decision Trees:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/EnsemblesL.pdf">Lecture</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/EnsemblesO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/EnsemblesO.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">SVM (R)</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">KernLab (R)</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">NeuralNetworks (R)</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">NNet (R)</li>
</ol></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Model Delivery<ol style="margin: 0px; padding: 0px 0px 0px 1.5em; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Evaluating Models:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/EvaluationO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/EvaluationO.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Evaluation (R)</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Scoring (R)</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">PMML (R) Exporting Models for Deployment</li>
</ol></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Advanced Topics<ol style="margin: 0px; padding: 0px 0px 0px 1.5em; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Text Mining:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/TextMiningO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/TextMiningO.R">R</a></li>
</ol></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Advanced R Topics<ol style="margin: 0px; padding: 0px 0px 0px 1.5em; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><a href="http://togaware.com/onepager/PlotsB"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Plots</span></a><span>&nbsp;</span>(<a href="http://onepager.togaware.com/Plots.pdf">PDF</a>,<span>&nbsp;</span><a href="http://onepager.togaware.com/Plots.R">R</a>) Miscellaneous Plots</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><a href="http://togaware.com/onepager/FunctionsB"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Functions</span></a><span>&nbsp;</span>(<a href="http://onepager.togaware.com/Functions.pdf">PDF</a>,<span>&nbsp;</span><a href="http://onepager.togaware.com/Functions.R">R</a>) Writing Functions in R</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><a href="http://togaware.com/onepager/ParallelB"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Parallel</span></a><span>&nbsp;</span>(<a href="http://onepager.togaware.com/Parallel.pdf">PDF</a>,<span>&nbsp;</span><a href="http://onepager.togaware.com/Parallel.R">R</a>) Parallel Execution</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Packaging (R) Pulling it Together into a Package</li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Doing R with Style:</span><span>&nbsp;</span>*<a href="http://onepager.togaware.com/StyleO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/StyleO.R">R</a></li>
<li style="margin: 0px; padding: 0px; border: 0px currentColor; font-style: inherit; font-weight: inherit; vertical-align: baseline;"><span style="margin: 0px; padding: 0px; border: 0px none currentcolor; font-style: inherit; font-weight: inherit; vertical-align: baseline;">Literate Data Mining with KnitR:</span><span>&nbsp;</span>*<a href="http://togaware.com/onepager/KnitRL.pdf">Lecture</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/KnitRO.pdf">OnePageR</a><span>&nbsp;</span>- *<a href="http://onepager.togaware.com/KnitRO.R"></a></li>
</ol></li>
</ul>]]></description>
	<dc:creator>Rahul Nayak</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/21257/bioinformatics-phds-cover-letter</guid>
	<pubDate>Mon, 16 Feb 2015 12:48:52 -0600</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/21257/bioinformatics-phds-cover-letter</link>
	<title><![CDATA[Bioinformatics PhDs - Cover Letter]]></title>
	<description><![CDATA[<p><strong>Overview</strong><br />The reception your cover letter will receive is more varied and unpredictable than the other elements of your application packet.&nbsp; Some readers, especially at large research universities, will skip it entirely, and focus instead on more direct indicators of your academic achievements and potential: the CV, letters, and writing sample.&nbsp; Most often, however, your cover letter works in tandem with your CV, and represents your best opportunity to communicate directly with your target audience prior to an interview.<br /><br />The cover letter should not simply repeat the information contained in the CV; rather it should elaborate and frame the aspects of your academic training and background that you want search committee members to have uppermost in their minds as they consider your candidacy.&nbsp; At a minimum, it should contain a clear statement of your research and teaching interests, and how your qualifications match the requirements of the job description. Many disciplines have their own conventions and protocols for application materials including the cover letter. Be sure to show a draft of your letter to your chair or the department's placement advisor.<br /><br />There is no perfect or even preferred style of cover letter save that tone should be that of a confident professional.&nbsp; Departments aren't interested in hiring graduate students (they already have enough of those).&nbsp; They are looking for serious scholars/teachers who will make interesting, congenial, and productive colleagues. While it is probably not a good use of your time to tailor your letter for each opening, you will probably need at least two base versions that emphasize different elements (You would not want to use the same cover letter to apply to Oberlin as UC Irvine). You may want to customize the letters for the three to five jobs most attractive to you.<br /><br />Your cover letter should not exceed a page and a half or two at the most.&nbsp; No one will read a four-page letter, and your apparent inability to communicate your credentials in a concise manner is not to your advantage. Every line of your letter should serve a demonstrable purpose. Some people have gotten excellent jobs with a brief, boilerplate letter containing no more than a short intro, a paragraph on their research, and a couple of sentences on their teaching. Others use letters that discuss in very specific terms how they, their research, and their teaching would "fit" within the existing department and institutional setting. The choice of style is up to you, and should reflect what makes you feel most comfortable and most positive about your credentials.<br /><br />There are, however, circumstances where a longer, more annotated version is more likely to be helpful. The issues you should take into account when making this decision are:<br /><br />&nbsp;&nbsp;&nbsp; The size of the department/institution<br />&nbsp;&nbsp;&nbsp; The extent to which your research is mainstream and its significance readily apparent<br />&nbsp;&nbsp;&nbsp; The extent to which your qualifications diverge from those mentioned in the job ad<br />&nbsp;&nbsp;&nbsp; The extent to which the institution to which you are applying differs from UC Berkeley and the relative importance of teaching versus research<br />&nbsp;&nbsp;&nbsp; Unusual circumstances or career paths<br /><br />Size matters. The larger the department, the less detailed your letter needs to be.&nbsp; If there are already six people working in your sub-field, they can assess and translate the significance of your work to others in the department.&nbsp; If, however, you will be the only history of science person or the only physical anthropologist in the department, the search committee and others will likely need more help from you to understand the import of your work.&nbsp; Remember, if they are searching for your specialty they are understaffed in your area, and even if there is more than one person in your sub-field she/he may be on leave or otherwise uninvolved in the search.<br /><br />Similarly, smaller departments are more likely to be concerned than larger ones about the specific courses you are prepared to teach.&nbsp; If there are certain core courses your position needs to cover, make it unambiguously clear that you are prepared to do so even if you haven't taught them already.<br /><br />As a rule of thumb, the more your profile diverges from the specifics of the job description (or the norm, such that it exists), the more likely you will want to say more about why you are nonetheless a strong candidate.&nbsp; By doing so you can turn a question mark into an advantage.&nbsp; Highlight your strengths, and if you have time perform a little research on the department (see below) so you can explain how you would add to the department in ways that they might otherwise not have considered.&nbsp; Job descriptions are not always etched in stone. If you're very interested in the job, call the department and ask to speak to someone on the search committee.&nbsp; If that's too intimidating, call the departmental assistant or secretary. They can at least tell you if it&rsquo;s a new position or replacement which in turn can indicate whether they really need someone who can teach The Politics of Southern Africa or if Middle Eastern Politics would do just as well.&nbsp; They may well be willing to sacrifice a course in an area that the ad specified in order to get the extra teaching experience or innovative research that you have to offer, but only if you give them the opportunity and explain what they'd get in return.<br /><br />&nbsp;If you've taken an unusually long time to finish because you spent three years learning a new language in order to prepare for two years of original research or some other factor that enriches what you have to offer as a teacher or a scholar, let them know about it.&nbsp; Learning a new language, for example, is an indicator of your commitment to serious scholarship.&nbsp; Think of a way to put a positive valence on an aspect of your CV that you believe is likely to raise questions or doubts.<br /><br />As hard as it may be for not-yet-employed-but-soon-to-be academics like yourselves to believe, there are some individuals and departments that are intimidated by you and your institutional pedigree.&nbsp; There are many fine schools and departments that are convinced that every Berkeley graduate student is only interested in a position at Harvard, Princeton, or (hold your nose) Stanford.&nbsp; If it is a small liberal arts college, they may also assume that you view teaching and advising undergraduates strictly as a necessary evil. Ergo, why interview someone who will either look down their nose at us, and/or desert us for greener pastures as soon as their third book has been published and Yale comes calling.&nbsp; They often don't seem to realize that Berkeley graduate students are sincerely interested in a wide range of academic settings for a variety of reasons personal and professional, and, perhaps more to the point, Yale rarely "comes calling."&nbsp; An even greater burden of proof exists if a quick scan of your CV reveals that your all of your experience in higher education has occurred in a large, elite, research-oriented setting. How can you overcome this potential obstacle especially if you're very interested in a school that you have reason to believe may be suspicious of Berkeley PhDs?<br /><br />It's probably not advisable to write in a cover letter that they shouldn't be intimidated by lil' old you (i.e., "I'm really not very good; in fact, my advisor says I'm her worst graduate student in twenty years."), but there are ways to indicate a sincere interest in their department.&nbsp; One means is to do a little research, and briefly discuss how you might fit into the department and the institutional community-at-large.&nbsp; There are numerous articles written by faculty about the search process that state explicitly the positive impact it can have on their impression of a candidate to see evidence that that he/she has taken the time to learn something about them. Researching a department and its associated programs/research centers has never been easier.&nbsp; Virtually all colleges and universities are online, and their web addresses can be easily located using Education/Universities link.<br /><br />A second way to address fears of imminent flight is to provide evidence of ties to the area, the university, or lifestyle.&nbsp;&nbsp; If you are from the Midwest, have family nearby, or even if you just spent an enjoyable summer there, add a line about it and your desire to return to your cover letter for Purdue or Wayne State.&nbsp; If you did your undergraduate work at a similar type of institution, draw their attention to that link.&nbsp; Don't assume that they will notice where you got your BA on your CV, and make the connection.<br /><br />If you are applying to small, liberal arts colleges, don't just list the courses you've taught with a line of boilerplate about how important you take your teaching responsibilities to be. These days, a good, small college has a list price of about $30,000 a year, and close contact with people like you is one of their key selling points to parents and potential students. You are expected to be more than a lecturer, and your ability to convey your recognition of that fact and a sincere interest in working closely with students matters. Advising, participating in non-academic activities, watching your students grow and mature inside the classroom and out (and having an influence on that process) can be among the most rewarding aspects of the profession.&nbsp; If you value these broader elements of being a professor, let them know. In particular, if your own experience has been limited to large universities, think about describing an episode where you had a positive impact on the development of a student and the satisfaction you derived from helping him or her. At many small colleges, and large universities (including Berkeley) as well, one of the most significant pedagogical trends is fostering greater student involvement in faculty research.&nbsp; If you can articulate how this might occur for you and their students in a brief but thoughtful manner, it can alleviate some of the concerns occasioned by your Berkeley background.<br /><br />Your letter typically will have four segments: the introduction, research, teaching, and the closing.<br /><br /><strong>Introduction</strong><br />Be sure to identify the position you are applying for by rank and sub-field in the first sentence or two.&nbsp; It is not uncommon for departments to be engaged in more than one search in a given year, and large departments may have more than one in your sub-field.&nbsp; If it is an open rank position and you are applying as an assistant professor, in most cases you and your record of accomplishments will not be directly compared with those of more experienced candidates applying for it at the associate or full professor level.&nbsp; Rather, applicants are assessed based on where they are in their career path, and you have every chance of successfully competing against them.<br /><br />If you have finished, mention it up front. If not, state when you expect to file - no later than June 2003.&nbsp; Many readers will view your optimistic prediction with a skeptical eye, and anything you can say that makes the claim appear more credible (e.g., "I have written and my chair has reviewed four of the six chapters.") can help mitigate their concerns.&nbsp; You can put such a statement in the introduction or wait until you discuss the dissertation itself.<br /><br />If your discipline holds its annual meeting in the summer or early fall (i.e., before application deadlines) and you had an excellent conference interview, make reference to it in the cover letter including the names of the faculty with whom you spoke.&nbsp; By the time people actually start to read files, months may have passed and even the strongest of impressions can fade.&nbsp; But they can be rehabilitated and revived, especially if you can remind them of a specific strength, ability, or issue that seemed particularly salient during the interview.<br />Research<br />Unless you are applying to a school that cares only about your teaching (increasingly rare), a description of your research generally follows next.&nbsp; The challenge here is not simply to describe your research, but to frame it in terms of your sub-field and discipline. The search committee, hasn't lived, eaten and breathed Post-Edwardian Hermeneutics for the past five years the way you have. And they haven't been there every step of the torturous process like your friends and significant others. So forgive them for not immediately recognizing your research at first blush for the path-breaking work that it is.<br /><br />Departments want to know that in hiring you, they are adding someone who will make a future contribution to the discipline and enhance the reputation of the department. However, they are often ill-equipped to understand exactly how that will be true in your particular case. Many disciplines are sufficiently broad that leading or cutting-edge research in one sub-field is barely intelligible to those in others.&nbsp; In addition, when you became a candidate for the short list, your file will be read by department members outside your specialty, and, oftentimes later on in the process, by individuals outside your discipline as well. You need to describe the forest in which your tree resides, and explain why it matters in terms of the broader trends and issues within your discipline. Obviously, if your work is focused on one of the classic conundrums of your field, much less in the way of providing perspective is necessary than if you are addressing an emergent issue or employing an unconventional approach.<br /><br />If your research is particularly novel or cutting-edge, any markers of broader acceptance by other, more established scholars or scholarly organs in your field can ameliorate possible concerns about its relevance and potential importance.&nbsp; In discussing your work, note the recognition it has received in the form of competitive grants, awards, publications in refereed journals, and/or presentations at major conferences.<br /><br />It is also important to mention where you expect your research to go after the completion of your dissertation and the publications that will flow from it.&nbsp; They, especially at research-oriented institutions, want to know at least in broad terms where you expect to go from here.&nbsp; They want to see evidence of a scholarly agenda that extends beyond the dissertation.&nbsp; You don't need to have pages written or titles blocked out, but you need to tell them in a paragraph, (two at the most) about what questions intrigue you, and how you expect to go about finding the answers to them.&nbsp; These questions for future research may have been generated by the findings of your dissertation, unusual data uncovered during your fieldwork, or interesting side issues that you were forced to put off in order to keep your dissertation taut and focused.&nbsp; Think twice about mentioning future projects that appear entirely unrelated to your current work. Departments will want you to be firmly established in one area before you go off into another.<br /><br />The relative importance of teaching versus research is a continuous and not a discrete variable.&nbsp; Even schools that emphasize teaching in their job listing will generally want evidence of scholarly engagement and publishing potential. It is a very competitive market for students out there, and virtually all institutions are under pressure to sell themselves via the quality of their faculty to the limited number of good students in the applicant pool.&nbsp; A good marker for the relative importance of teaching versus research is the teaching load.&nbsp; An institution with a 3-2 teaching load (a total of five courses taught per two-semester year) will expect more in the way of and value research more highly than one with a 3-3 load.<br /><br />If you work in a capital-intensive area, mention your track record of gaining grants and other sources of external funding.<br /><strong>Teaching</strong><br />In a similar fashion, the more the institution you are applying to diverges from Berkeley and the more your profile differs from the job description, the more expansive you should be in talking about your teaching and what you have to offer their students.&nbsp; If you have won a teaching award at Berkeley, don't make them wait until they read your CV to discover that fact.<br /><br />For letters sent to large universities where you will be expected to teach large, lecture courses and graduate seminars, little is needed except to convey that you have the necessary experience and/or background.&nbsp; Since the dominant pedagogical style is the same as that found at Berkeley, it will be assumed that you will be able to do the same for them.<br /><br />If you have TA'd some of the courses that (based on the job description) you would be expected to offer, let them know.&nbsp; If you have not had that opportunity, but your fields and research fall within the domain of the job description, you may want to add a line about how well prepared you are to teach such courses based on your training and research.<br /><br />If your profile does not correspond exactly to the description found in the job announcement, but you believe that you could nonetheless teach the required courses, explain the basis for your confidence. What strength would you bring to the department that would more than make up for your "otherness"?&nbsp; Departments may decide that they don't "need" another conventional European historian if you can convince them that you can handle the core courses and offer something new that they don't currently cover as well. In this case especially, think about doing some research so you can speak in more specific terms about how you would fit into and enhance the department's offerings. Help them visualize how you would strengthen them as a department.<br /><br />Small colleges will want to know that you are able to teach on a more intimate basis and are prepared to take the time to do it well. If you give them three generic lines about how "important" you consider your teaching responsibilities, don't expect much of a positive response.&nbsp; Spend a couple of paragraphs describing your teaching experience and philosophy, and how you would take advantage of the opportunity to create you own courses.<br /><br />If you've had the opportunity to design and teach your own course, tell them, briefly, how you went about it and the choices you made. Don't just say you're a good teacher, tell them why. Look over your teaching evaluations and pick out one or two consistent strengths to highlight. Drawing on your experience, talk about how you engage students and enhance their skills (especially writing) and intellectual development.<br /><br />For good, small colleges, the quality of the teaching offered to students is their stock-in- trade.&nbsp; Even the most research-oriented, small colleges take teaching undergraduates very seriously. You need to demonstrate that you take it seriously as well, and can talk about it using more than vague generalities and shop-worn cliches.<br />Closing/Enclosures<br />Wrap it up quickly.&nbsp; If you are going to be traveling for any significant portion of the job search season be sure to let them know how they can contact you (email, cellphone and/or a Pacific Bell message center account are particularly good options).<br /><br />Before closing, include a sentence where you list the materials you have enclosed (e.g., CV, dissertation abstract, transcripts, teaching statement/portfolio, writing samples, etc.) and are having sent separately (letters of recommendation).&nbsp; You will often be assembling multiple packets at the same time (as in midnight October 14th, midnight November 14th, etc.) for jobs that ask for different combinations of enclosures.&nbsp; In addition to telling them what they should have received, it serves as a handy list for you to check before sealing the envelope.<br /><br />Should you send a writing sample, even if they haven't asked for one? Unless the norm in your discipline is to never send more than they ask for, if you've been smart and have already run off thirty copies at two cents per page (that's only sixty cents for a thirty page chapter) by all means send it.&nbsp; That way it's in the file should someone become interested in you and want to read more.</p>]]></description>
	<dc:creator>Martin Jones</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/21096/how-to-prepare-your-bioinformatics-cv</guid>
	<pubDate>Mon, 09 Feb 2015 01:50:01 -0600</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/21096/how-to-prepare-your-bioinformatics-cv</link>
	<title><![CDATA[How to Prepare your Bioinformatics CV ?]]></title>
	<description><![CDATA[<p>Preparing a CV is also an art as well as a requirement for a person applying for a job .<br /> Curriculum Vitae is the first impression on the employer so it should be the best.How It can be the best can be learnt.Here is a link where you can get guidelines on how CV can be prepared and a sample also. Preparing your own Curriculum Vitae can seem a daunting task, quite apart from what to put in and what to leave out, describing your own strengths and abilities isn't easy. What we have tried to do with the following guidelines is to make the whole process a much easier one and ensure that you end up with a professional document which shows you how to pitch your skills and stand out from the crowd. In the current economic and employment climate, employers are looking to consistently improve on productivity and match a prospective employee's skills and experience with the job needs, both now and in the future.<br /> <strong><br /> Presentation and layout</strong><br /> Always ensure that your CV is laser-printed on white, good quality paper, use a clean typeface and don't go smaller than 12 point.<br /> The use of sub-headings (e.g. Personal details, career history, etc.) will help potential employers glean the information they require with ease.<br /> There should be clear spaces between category headings for easy clarification and definition.<br /> Your name, address and phone number(s) should form the start of the document. If you are giving a work number add the following - 'please use with discretion.'<br /> Commencing with your present or most recent employer, state your career history. Then list your professional qualifications. If you have been working for many years list your academic qualifications and a very brief mention as to your college or schooling.<br /> If you are just commencing your working life, having previously been a student, provide more in depth knowledge regarding your academic achievements to date.<br /> <br /> <strong>Content</strong></p><p>Starting with your current or most recent employment provide details of your position as follows:</p><ul>
<li>A chronological CV should be arranged in reverse chronological order. It should be apparent immediately where you are now.</li>
<li>Remember that an application form is limited to the few things that a particular institution wants to know about everybody. A CV lets you give information that is unique to you. Add all your key accomplishments and activities in the initial draft. In subsequent drafts, you can remove information that may not be pertinent.</li>
<li>Resist the temptation to append explanatory sentences or language, which will distract the reader from the basic information being presented. The language of a CV is abbreviated and succinct. When applying for residency training, you will have the opportunity to express yourself in a personal or biographical statement. In the future, when applying for a job or some other type of position, you will want to include an appropriate cover letter with your CV to explain your particular qualifications and strengths for the position.</li>
<li>Don&rsquo;t despair if your CV doesn&rsquo;t resemble those of other students who are applying to the same residency program. Everybody&rsquo;s CV is different. Even if everyone used the same format suggested in this section, your CV will not resemble others&rsquo; because it doesn&rsquo;t have the same content. No residency program director is looking for a specific CV style. You will receive points for neatness, and readability.</li>
<li>Be honest. If you haven&rsquo;t accomplished anything in a particular category, leave it out. Don&rsquo;t create accomplishments to fill in the spaces. You can be specific about your level of participation in a project or activity, but don&rsquo;t be misleading (i.e., you can say you coordinated membership recruitment for your AMSA chapter, but don&rsquo;t say you were &ldquo;president&rdquo; unless you were).</li>
</ul><ul>
<li>Job title - time that you have held this position</li>
<li>The key tasks and responsibilities that comprise this role's requirements - notable achievements whilst in the role</li>
<li>Where possible quantify your achievements with precise facts and figures, e.g. managed junior staff, handled department budget, prepared management reports</li>
<li>Expand on the skills you are using in your current job which you believe will be valuable in the position(s) for which you are applying</li>
</ul><p>It is not necessary to state the reason you are leaving your current position. This will be a topic for conversation when you are invited for interview or can be covered in your letter of application.<br /> For all previous employment, unless one appointment was more significant than your current or last position, keep details brief i.e. the name of the company, job title, period of employment and the job.<br /> Be sure there are no gaps in your career history - unless for example you took a year out to travel, in which case make reference to this under Interests/Hobbies.<br /> If you are a student just starting work, give any evidence you can to demonstrate your practical skills e.g. school prefect, event organisation, member of sports team, contributor to college magazine or voluntary work.<br /><br /> You are under no obligation to disclose marital status, age or whether or not you have children unless these are specific criteria for selection for a position that you are interested in.<br /> Consider what examples (interests/ hobbies) you can give to show that you match the selection criteria.<br /><br /> If they want someone to work as part of a large team, remember to say if you belong to a local organisation or if you are part of a sports team.<br /><br /> If they want someone who will work on their own for large periods of time, make reference to an Open University course you are considering undertaking.<br /><br /> Your primary objective is to convince the prospective employer that you have the requisite skills, experience and hunger to do the job.<br /><br /> Your CV should be no more than two A4 pages and as every employer is different remember to customise your CV to every job you go after.</p><p>There are abundant books on the contents and presentation of a general CV. A BMJ article published in 1978, offering doctors guidance on how to prepare a CV, has been reprinted in the widely read How to do it series.1 2 A survey among postgraduate deans and training advisers at regional colleges found that the contents and presentation of a model CV for doctors in training has been published.3 It is perhaps surprising to note that these models differ significantly from one another. Although they may be useful as starting points, their differences tend to create confusion and anxiety among students. I would argue that these differences exist because the content and presentation of the "ideal" CV vary considerably among individual applicants, the stage of their careers, and the purposes for which the CV is used. It is impossible to create a generic CV. I have therefore not attempted to draw up another model CV. Rather, the purpose of this article is to outline the general principles and important practical points in preparing a good CV. General principles on contents Before finalising your CV for a particular purpose you must be sure of your objectives, whether it is used as an initial screening or the only selection instrument, and the criteria against which it is judged. What details, and how many of them, to include in your CV depends on these factors. I shall illustrate with examples relevant to medical students.&nbsp;<br /> <br /> (1) Job application Your objective is to get the job. In a job application, the CV is used for two purposes: as an initial screening instrument for shortlisting candidates and as a framework for discussion during the interview. The explicit criteria used for shortlisting are usually given in the job advertisement. For some organisations, separate lists of essential and desirable criteria are given. Alternatively, you can get a good idea of the basic requirements from the job description. Your CV must clearly highlight these criteria, preferably on the first page. These usually include: formal qualifications; registration with the General Medical Council; and the prescribed experience. It is sometimes easy to forget to mention items specifically asked for in the job description (for example, a valid driving licence). The implicit criteria are less easy to pinpoint. For example, how much detail on your BSc dissertation and publications should you include? Should you make a long list of extracurricular activities, interests outside medicine, and positions of responsibility? If you admit to a wide range of extracurricular activities and interests, would you be considered as a candidate with a well balanced mature personality or will it be interpreted to mean that you will have little time or interest to do your job? There are no easy answers. Common sense might tell you that BSc dissertation and publications are more important in application for teaching hospital or research posts, but less important for district hospital posts. Conversely, you might think that interests outside medicine are more important for posts in district hospitals or in general practice. This is, however, not always true. A few consultants at district hospital are highly academic. Information gathered from students and doctors working under the professor or consultant concerned may be vital. Alternatively, it is worth while doing your homework by looking up your prospective consultant in the medical directory. This may occasionally prompt you to include information that you might otherwise have left out. For example, you may find that the consultant qualified in Scotland and has previously worked in Scotland for a considerable time, and you may decide to add in your CV that you studied in a Scottish secondary school. Since the CV is only used as for initial screening, you need not go into your previous experience or extracurricular activities in too much detail. Highlight only the most significant points, and leave the details for the interview. If you are applying for a clinical post, one of your referees should be a consultant for whom you have worked as a student. You should ask for permission to use his/her name before submitting your application.&nbsp;<br /> <br /> (2) Application for research scholarship or PhD studentship The CV and application form are sometimes used as the sole selection instrument, and you must make enquiries before you submit your application. Clearly, academic ability is the main criterion for selection, and you should include as much information relevant to your academic ability and interests as you can. Examples are your A levels, your BSc dissertation, any publications (even in the form of a letter in newspaper), any experience as an editor (for example, for your school magazine). Your extracurricular activities are less important, and you can simply give a short list. At least one of the referees should be an academic - for example, your previous supervisor in your BSc degree.<br /> &nbsp;<br /> (3) Application to join a clinical course in another medical school Preclinical students who have completed an intercalated degree often have the option of applying to join a clinical course in another medical school, although it may become more difficult to do so with the introduction of the new GMC curriculum. Your CV is usually used for shortlisting candidates for interview. The criteria differ slightly among medical schools, but both academic ability and contribution to university life are important. Hence, not only should you highlight your academic achievements but you must also highlight your participation in the university (for example, in sports or music).&nbsp;<br /> <br /> (4) For the information of your tutor or counsellor For most medical schools, you are allocated a tutor who provides both academic and non-academic support and monitors your progress throughout your study on a confidential basis. Students are sometimes asked to submit their up to date CV to their tutors for information. Assuming that the tutors are helpful there is little to gain from over emphasising your strengths or hiding your weaknesses. Once you become a doctor in training after you qualify you will need to undergo an annual assessment of your progress. It serves to certify that you have reached a satisfactory standard, but it is also used as an aid to identify and help with your weaknesses. You may find it difficult to balance these two purposes in presenting your CV. General principles on presentation Now that all students are computer literate, there should be few problems in preparing a well presented CV. The following list serves as a reminder on how to present your CV effectively: Spelling or grammar mistakes - do not rely purely on the spell check on your computer. Ask friends to proofread your CV for you. Consistency - The use of punctuation to open and close sentences, justification, and fonts should be consistent. Readability - The headings should be clear. The font size should be no less than 12 point. Basic criteria - The basic criteria should be easily located, preferably on the first page. Length - The length of your CV increases as you progress up the professional ladder. For students, it should generally be no more than three pages. Quality of print - The CV should be printed on good quality paper, preferably using a laser printer. Practical points In this article, I argue that different versions of a CV may be required for different purposes. Even applications for different posts in the same specialty may require slightly different versions. Also, CVs need to be updated regularly. This would have been time consuming to achieve in the past, but it is now quite simple, with the aid of a basic word processing package. A master CV containing all relevant information should be prepared and saved as a computer file. This should be continuously kept up to date. When the need for a CV arises, it can be tailormade by editing the master document. It is important to save each of these edited versions separately, with the file names indicating the date when it was created and the purpose. It is also important to prepare a cover letter to go with the CV. Key messages A good CV is essential for successful progression up the medical professional ladder The contents of the CV should be tailormade for the purpose it is used for and the criteria against which it is judged. It is important to gather information about these criteria first The CV must be technically well presented, with the basic criteria easily located Information technology has made it simple to regularly update our CVs and allows preparation of different versions of a CV for different purposes with relative ease.</p><p><strong>Reference:</strong></p><p>Prepare a curriculum vitae. BMJ 1978;25(2):1478-9.<br /> O'Brien E. Prepare a curriculum vitae. In: Reece D, ed.&nbsp;<br /> How to do it. Vol 1. London: BMJ Publishing Group, 1995 Chambler AF, Chapman-Sheath PJ, Pearse MF.&nbsp;<br /> A model curriculum vitae: what are the trainers looking for? Hosp Med 1998;59(4):324-6.</p>]]></description>
	<dc:creator>Neel</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/20328/research-article-publiaction</guid>
	<pubDate>Fri, 09 Jan 2015 18:50:17 -0600</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/20328/research-article-publiaction</link>
	<title><![CDATA[Research article- Publiaction]]></title>
	<description><![CDATA[<p>Dear All,</p><p>I am Lalit, Working as SRF In Haffkine Institute. I would like to publish research article related to protein modeling and docking which in cludes MD as final step.</p><p>I am currently working on protein modeling and docking area.&nbsp;</p><p>Those who are interested . Kindly contact me on this email id:samantlalit@gmail.com</p>]]></description>
	<dc:creator>LALIT SAMANT</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/14011/dynamic-chromosome-breakpoints</guid>
	<pubDate>Wed, 13 Aug 2014 18:38:10 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/14011/dynamic-chromosome-breakpoints</link>
	<title><![CDATA[Dynamic chromosome breakpoints !!!]]></title>
	<description><![CDATA[<p>Cell division involves the distribution of identical genetic material, DNA, to two daughters&rsquo; cells. During this process, duplicated deoxyribonucleic acid (DNA) goes through a condensation and decondensation process. This is followed by nuclear envelope dissolution, mitotic spindle assembly, migration of the sister chromatid pairs to the metaphase plate, division and segregation of identical sets of chromosomes into daughter nuclei and nuclear envelope reformation.</p><p>The vital metaphase stage of cell division, when the sister chromatids migrated to the centre and lined up in a row, and pulled apart using attached microtubules in such a way that half the DNA ends up in each daughter cell. However, before the mitotic spindle‐mediated movement gets start and pulled DNA apart, the chromosomes are free to undergo <strong>recombination </strong>which involves the exchange of genetic material either between multiple chromosomes or between different regions of the same chromosome.</p><p><img src="http://www.sciencelearn.org.nz/var/sciencelearn/storage/images/contexts/uniquely-me/sci-media/images/chromosomes-crossing-over/464438-1-eng-NZ/Chromosomes-crossing-over.jpg" alt="image" width="504" height="342" style="border: 0px; border: 0px;"></p><p>During recombination, the precise breakage of each strand, exchange between the strands, and sealing of the resulting recombined molecules happens. The &ldquo;<strong>chromosomal breakpoints</strong>&rdquo; refers to these places where they break. Mostly, this process occurs with a high degree of accuracy at high frequency in both eukaryotic and prokaryotic cells. But occasionally this &ldquo;break and sealing/ break and reattach&rdquo; process goes wrong and the reattachment happens in the wrong place which usually create disaster (with few exceptions).These chromosome disaster or abnormalities involve the gain, loss or rearrangement of visible amounts of genetic material during cell division. These abnormalities are of two type, the first one is numerical abnormalities &nbsp;where severe disorders are caused by the loss or gain of whole chromosomes, which affect the copy number of hundreds or even thousands of genes. The second are structural abnormalities which can be unbalanced or balanced. The former are similar to numerical abnormalities in that genetic material is either gained or lost. The natural defects in chromosome segregation are linked to cancer and several genetic diseases (http://en.wikipedia.org/wiki/List_of_genetic_disorders). Therefore, the enzymes involved in regulating cell division are still the attractive drug targets for many diseases.</p><p>&nbsp;</p><p>&nbsp;</p><p><img src="http://upload.wikimedia.org/wikipedia/commons/4/4a/Chromosomal_translocations.svg" alt="image" width="424" height="331" style="border: 0px; border: 0px;"></p><p>&nbsp;</p><p>Apart from certain chromosome abnormalities, these &ldquo;crossing over&rdquo; of segments of maternal and paternal chromosomes to form hybrid chromosomes have some evolutionary importance and considered as a driver of genetic variation. Moreover, the chromosome breakage in evolution is considered to be non-random in nature(http://www.ploscompbiol.org/article/info%3Adoi%2F10.1371%2Fjournal.pcbi.0020014). In addition the study of breakpoint regions and non-breakpoint (stable) regions of chromosomes indicates both the regions evolved in distinctly different ways ( http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2675965/). These breakage may lead to genetic diseases or participate to chromosomal rearranmgnets and contributed in development of new species.</p><p>I will try to explain the genome hotspots/Evolutionary Breakpoint Regions(EBRs)/fragile regions/weak fragments/&nbsp; in my next blog.</p><p><strong>Software for recombination detection:</strong></p><p><strong>RAT</strong> http://cbr.jic.ac.uk/dicks/software/RAT/</p><p><strong>Breakpointer</strong> https://github.com/ruping/Breakpointer</p><p><strong>DRP</strong> http://web.cbio.uct.ac.za/~darren/rdp.html</p><p><strong>RB-finder</strong> http://www.ncbi.nlm.nih.gov/pubmed/18707535</p><p><strong>LDhat2.0</strong> http://ldhat.sourceforge.net/LDhat2.0/instructions.shtml</p><p><strong>Reference:</strong></p><p>http://www.nature.com/scitable/topicpage/genetic-recombination-514#</p><p>Image: Wikipedia , sciencelearn.org.nz</p><p><strong>Recommended Articles:</strong></p><p>http://www.friendshipcircle.org/blog/2012/05/22/13-chromosomal-disorders-youve-never-heard-of/</p><p>http://web.udl.es/usuaris/e4650869/docencia/segoncicle/genclin98/recursos_classe_%28pdf%29/revisionsPDF/chromosyndromes.pdf</p><p>http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2775595/table/T2/</p><p>http://learn.genetics.utah.edu/content/disorders/chromosomal/</p><p>http://www.ncert.nic.in/html/learning_basket/biology/cc&amp;cd.pdf</p>]]></description>
	<dc:creator>Jitendra Narayan</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/13025/the-5-reasons-to-mistakes-at-bioinformatics-work</guid>
	<pubDate>Thu, 24 Jul 2014 02:51:41 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/13025/the-5-reasons-to-mistakes-at-bioinformatics-work</link>
	<title><![CDATA[The 5 reasons to mistakes at bioinformatics work !!!]]></title>
	<description><![CDATA[<p>When you're just starting out with biological programming, it's easy to run into complex problems that make you wonder how anyone has ever managed to write a program. There are some problems that trip up nearly every bioinformatician--everything from getting started understanding the biological problems to dealing with program design. Some random mistakes are so prominent that even experienced biological programmers do it. The 8 years in bioinformatics and my few random observations, most of them are snarky. These reasons will always take longer than expected and compel you to postpone your project deadline.</p><p><strong>1.Stupid for biologist:</strong> Biology is so complex that it will make bioinformatician feel stupid. There are no any universal fixed rules; it can surprise you any time. So be nice to biologists who ask questions and resolve your biological puzzles. Sometime you will have no idea what the hell you were doing either.<br /><br /><strong>2.Puzzling why:</strong> Do not hesitate to ask question. Especially. at the beginning of project you will have to ask a lot of questions. Instead of puzzling it out at end check out and clear your doubt even for a single error. It may can leads to wrong conclusion.<br /><br /><strong>3.Running marathon:</strong> The most of the biological software&rsquo;s documentation is always incomplete. In other word they are no more than 95 percent complete. Sometime a single problem can halt your entire project for months. Compilation and running the pipelines in tedious because almost all are interdependent and need proper configuration. I face the same kind of problem with Evolver :( &hellip; <br /><br /><strong>4.Folders missing:</strong> The pipelines generate lots of data, and we keep them in several folders for future use. But sometime we delete them by mistake and move to recovery&hellip;<br /><br /><strong>5.Digging deeper:</strong> Digging deeper is fruitful, but some time it can be catastrophic. You may get frustrated or direction less. So keep a biologist with you for rescue &hellip;. Sometime an expert computer programmer to handle your server. Remember, the server will always go down when you need it the most.<br /><br />The most common frustrating&nbsp; common line: Why do we do this again?</p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/11592/xampp-starting-apache-fail-ubuntu</guid>
	<pubDate>Sat, 07 Jun 2014 05:52:35 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/11592/xampp-starting-apache-fail-ubuntu</link>
	<title><![CDATA[XAMPP: Starting Apache fail Ubuntu]]></title>
	<description><![CDATA[<p>Once you install XAMMP on linux, the most common problem you face is Apache failure. To fix the issues please use following command to first stop and then again start it.</p><p>sudo /etc/init.d/apache2 stop</p><p>sudo /etc/init.d/mysql stop</p><p>sudo /etc/init.d/proftpd stop</p><p>sudo /opt/lampp/lampp start</p><p>&nbsp;</p><p><strong>PhpMyAdmin &ldquo;Wrong permissions on configuration file, should not be world writable!&rdquo;</strong></p><p>Once the Xammp is installed, it might be possible to set up the configuration file in writable mode. Try the following steps:</p><p>Just chmod 0755 the file</p><pre>sudo chmod 0755 config.inc.php</pre>]]></description>
	<dc:creator>Ram Yash Pal</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/8987/the-dna-of-a-successful-bioinformatician-decoded</guid>
	<pubDate>Wed, 12 Mar 2014 13:41:26 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/8987/the-dna-of-a-successful-bioinformatician-decoded</link>
	<title><![CDATA[The DNA of a Successful Bioinformatician decoded !!!]]></title>
	<description><![CDATA[<p>Many blogs exist about successful bioinformatician, but this blog so far now is my personal view on characteristics of successful bioinformatician or computational biologist. &nbsp;Hmm &hellip; of course these views are subjective to my own personal experiences and therefore I don't claim that the view listed here is complete. As a human, I don&rsquo;t take them too serious. The success must not be the only target of your work. The target is to work on your own virtues; some of those virtues are the topic of this blog.</p><p><img src="http://bioinformaticsonline.com/mod/photo/genome_decode.png" alt="image" width="509" height="458" style="border: 0px; border: 0px;"><br /> <br /> <strong>1. Update new things continuously<br /></strong>As per my personal experience, it&rsquo;s not always easy to work as a bioinformatician! &nbsp;There are couple of reasons to say that; First computational part of biology make our life&rsquo;s a little harder compared to other professional categories. The fact - for instance - that the technology cycle in the bioinformatics world is very short, the actual knowledge becomes outdated in a few months or years. Therefore, we need to learn continuously - new things get important. Second, to stay on top of things we really need the strong will to be good at our job. That's probably the most important characteristic to bioinformatician. They are usually an excellent knowledge worker with great technical abilities, and have the will to be that over decades!<br /> <br /> <strong>2. Avoid the sentence </strong><strong>"I did not know what to do!"</strong><br /> In our computational biology lab, we generally face lots of technical problems. But as you know, it's impossible to know everything to do the computational biology jobs ( Yup.. because you need diverse and multidisciplinary knowledge to understand biological problems and resolve their respective solutions), therefore it's absolutely necessary that a bioinformatician finds its way through a new topic. How I typically do that is I use google and I talk to other experts in our laboratory or online biostar community to find out what they think. "I did not know what to do!" should not be an argument for us.<strong><br /><br /> <strong>3. To make oneself useful</strong></strong><br /> Several time it does happen, you finished our task earlier than expected; in such cases if you have some time left then: Take a coffee and play chess; reversi, etc. In my case I take a rest. Afterwards I think about what I could do that helps the team to achieve its targets, 'cause some of my team mates probably didn't finish! (at least if I didn't met them at coffee bar !!)</p><p><strong>4. Care for all</strong><br /> During my rigorous research duration; I attended several workshop organized by my University departments. I had a discussion with other research fellow, professors; I generally ask &hellip; what it really takes to make a team successful or to be a successful research leader. They always said: "Well, you need some caring people!" I think there is a lot truth in that statement. If we do not care about quality, timelines, good team culture, respectful communication (!!), clean code, if all this doesn&rsquo;t matter to us, then I believe the probability is higher that we fail in research and analysis. <br /> <br /> <strong>5. Be good with people</strong><br /> Because bioinformatician and computational biologist jobs typically involves to work in a (most wanted J cross-departmental!) team, therefore it's important that we're (more or less) good in dealing with other individuals. Everyone have their own strengths and weaknesses, just like us. It's important to treat all the research team mates with respect, regardless of their technical competence or contributions. Of course, sometimes people deserve a clear statement (!!!), but try to do these things one-on-one. Make sure nobody loses his face. Attend the meetings at the coffee bar; be good at table top soccer and go out once in a while to have a beer with your team. You know what I'm talking about.</p><p>At the end of a week I look back and I ask myself what I have produced. This could be paperwork, community days or (best!!) programming code. Always remember there is always a solution to a problem. Most of the times there are at least three solutions. So, don&rsquo;t just blame, suggest a solution.<br /> <br /> That's it. I am looking forward to your thoughts and comments!</p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/8798/list-of-gene-ontology-software-and-tools</guid>
	<pubDate>Sun, 09 Mar 2014 14:48:19 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/8798/list-of-gene-ontology-software-and-tools</link>
	<title><![CDATA[List of gene ontology software and tools]]></title>
	<description><![CDATA[<p>The Gene Ontology (GO) is a set of associations from biological phrases to specific genes that are either chosen by trained curators or generated automatically. GO is designed to rigorously encapsulate the known relationships between biological terms and and all genes that are instances of these terms. These Gene Ontology has become an extremely useful tool for the analysis of genomic data and structuring of biological knowledge. Several excellent software tools for navigating the gene ontology have been developed.</p><p><img src="http://ohnosequences.com/images/GoSlimBlog.svg" alt="image" width="500" height="380" style="border: 0px; border: 0px;"></p><p>The GO provides core biological knowledge representation for modern biologists, whether computationally or experimentally based. GO resources include biomedical ontologies that cover molecular domains of all life forms as well as extensive compilations of gene product annotations to these ontologies that provide largely species-neutral, comprehensive statements about what gene products do. Although extensively used in data analysis workflows, and widely incorporated into numerous data analysis platforms and applications, the general user of GO resources often misses fundamental distinctions about GO structures, GO annotations, and what can and can not be extrapolated from GO resources. Here are ten quick tips for using the Gene Ontology.</p><p>Read "Ten Quick Tips for Using the Gene Ontology" at http://www.ploscompbiol.org/article/info%3Adoi%2F10.1371%2Fjournal.pcbi.1003343</p><p>Following are the most commonly used old and new GO term enrichment determination tools. These tools are recommended to people working in a wet-lab.</p><p><strong>CLASSIFI (Department of Pathology, UT Southwestern Medical Center)</strong></p><p>CLASSIFI (Cluster Assignment for Biological Inference) is a data-mining tool that can be used to identify significant co-clustering of genes with similar functional properties (e.g. cellular response to DNA damage). Briefly, CLASSIFI uses the Gene OntologyTM (GO) gene annotation scheme to define the functional properties of all genes/probes in a microarray data set, and then applies a cumulative hypergeometric distribution analysis to determine if any statistically significant gene ontology co-clustering has occurred.</p><p><a href="http://pathcuric1.swmed.edu/pathdb/classifi.html">http://pathcuric1.swmed.edu/pathdb/classifi.html</a></p><p><strong>EasyGO (China Agricultural University)</strong></p><p>EasyGO is designed to automate enrichment job for experimental biologists to identify enriched Gene Ontology (GO) terms in a list of microarray probe sets or gene identifiers (with expression information for PAGE analysis). Also EasyGO is also a GO annotation database, especially focus on agronomical species, supporting 30 species. It is user friendly, with advanced result browsing format and in-time update.</p><p><a href="http://bioinformatics.cau.edu.cn/neweasygo/">http://bioinformatics.cau.edu.cn/neweasygo/</a></p><p><a href="http://bioinformatics.cau.edu.cn/easygo/">http://bioinformatics.cau.edu.cn/easygo/</a></p><p><strong>g:GOSt (Institute of Computer Science, University of Tartu)</strong></p><p>g:GOSt retrieves most significant Gene Ontology (GO) terms, KEGG and REACTOME pathways, and TRANSFAC motifs to a user-specified group of genes, proteins or microarray probes. g:GOSt also allows analysis of ranked or ordered lists of genes, visual browsing of GO graph structure, interactive visualisation of retrieved results, and many other features. Multiple testing corrections are applied to extract only statistically important results.</p><p><a href="http://biit.cs.ut.ee/gprofiler/">http://biit.cs.ut.ee/gprofiler/</a></p><p><strong>DAVID</strong> : Gene Functional Classification (Laboratory of Immunopathogenesis and Bioinformatics, NIAID)</p><p>The Functional Classification Tool provides a rapid means to organize large lists of genes into functionally related groups to help unravel the biological content captured by high throughput technologies.</p><p><a href="http://david.abcc.ncifcrf.gov/gene2gene.jsp">http://david.abcc.ncifcrf.gov/gene2gene.jsp</a></p><p><a href="http://david.abcc.ncifcrf.gov/">http://david.abcc.ncifcrf.gov/</a></p><p>API <a href="https://github.com/chrisamiller/davidapi">https://github.com/chrisamiller/davidapi</a></p><p><strong>GOEAST</strong> (Institute of Genetics and Developmental Biology, Chinese Academy of Sciences)</p><p>GOEAST is web based software toolkit providing easy to use, visualizable, comprehensive and unbiased Gene Ontology (GO) analysis for high-throughput experimental results, especially for results from microarray hybridization experiments. The main function of GOEAST is to identify significantly enriched GO terms among give lists of genes using accurate statistical methods.</p><p><a href="http://omicslab.genetics.ac.cn/GOEAST/">http://omicslab.genetics.ac.cn/GOEAST/</a></p><p><strong>GOstat</strong> (Walter and Eliza Hall Institute of Medical Research)</p><p>Find statistically overrepresented GO terms within a group of genes</p><p><a href="http://gostat.wehi.edu.au/">http://gostat.wehi.edu.au/</a></p><p><strong>GOrilla</strong> (Technion - Laboratory of Computational Biology , Israel Institute of Technology)</p><p>GOrilla is a tool for identifying and visualizing enriched GO terms in ranked lists of genes.<br /> It uses two approaches, first by searching for enriched GO terms that appear densely at the top of a ranked list of genes&nbsp; or by searching for enriched GO terms in a target list of genes compared to a background list of genes.</p><p><a href="http://cbl-gorilla.cs.technion.ac.il/">GOrilla</a> makes nice pictures !!!!</p><p><a href="http://cbl-gorilla.cs.technion.ac.il/">http://cbl-gorilla.cs.technion.ac.il/</a></p><p><strong>Gene Ontology for Functional Analysis (GOFFA)</strong></p><p>GOFFA is a tool developed for ArrayTrack&trade; that takes a list of genes and identifies terms in Gene Ontology (GO) disclaimer icon associated with those genes.</p><p>It provides several tools to view/access the GO term hierarchy, full listing of GO terms annotated with the genes associated with a given term with statically useful report.</p><p><a href="http://www.fda.gov/ScienceResearch/BioinformaticsTools/ucm233315.htm">http://www.fda.gov/ScienceResearch/BioinformaticsTools/ucm233315.htm</a></p><p><strong>GOAT</strong> (The University of Manchester)</p><p>The aim of the GOAT project is to create an application that will guide users, especially biomedical researchers, in the annotation of gene products with terms from the <a href="http://www.geneontology.org">Gene Ontology</a>.</p><p><a href="http://goat.man.ac.uk/">http://goat.man.ac.uk/</a></p><p>Script <a href="https://github.com/tanghaibao/goatools/">https://github.com/tanghaibao/goatools/</a></p><p><strong>REVIGO</strong> ( Rudjer Boskovic Institute, Croatia)</p><p>REViGO is a web server that can take long lists of Gene Ontology terms and summarize them by removing redundant GO terms. The remaining terms can be visualized in semantic similarity-based scatterplots, interactive graphs, or tag clouds.</p><p><a href="http://revigo.irb.hr/">http://revigo.irb.hr/</a></p><p><strong>QuickGo</strong> (EMBL-EBI Institute)</p><p>It uses extensive computational filters to allow the generation of specific subsets of GO annotations, mapped to sequence identifiers of your choice. Then GO slims are used which is collective list of GO full set of terms available from the Gene Ontology project.</p><p><a href="http://www.ebi.ac.uk/QuickGO/">http://www.ebi.ac.uk/QuickGO/</a></p><p><strong>GOLEM</strong></p><p>An interactive graph-based gene-ontology navigation and analysis tool. GOLEM is a userful tool which allows the viewer to navigate and explore a local portion of the <a href="http://www.geneontology.org/">Gene Ontology</a> (GO) hierarchy.</p><p><a href="http://reducio.princeton.edu/GOLEM/">http://reducio.princeton.edu/GOLEM/</a></p><p><strong>BGI Web Gene Ontology (WEGO)</strong> Annotation Plot (Beijing Genomics Institute)</p><p>WEGO () is a useful tool for plotting GO annotation results. It has been widely used in many important biological research projects, such as the rice genome project [<a href="http://wego.genomics.org.cn/pubs/rice_indica.pdf">Yu, J. et al. Science 296, 79-92 (2002);</a> <a href="http://wego.genomics.org.cn/pubs/rice_finish.pdf">Yu, J. et al. PLoS Biol 3, e38 (2005)</a>] and the silkworm genome project [<a href="http://wego.genomics.org.cn/pubs/combine_silkworm.pdf">Xia, Q. et al. Science 306, 1937-40 (2004)</a>]. It has become one of the daily tools for downstream gene annotation analysis, especially when performing comparative genomics tasks. WEGO along with two other tools, namely <a href="http://wego.genomics.org.cn/cgi-bin/wego/External2GO.pl">External to GO Query</a> and <a href="http://wego.genomics.org.cn/cgi-bin/wego/GOArchive.pl">GO Archive Query</a>, are freely available for all users. Any suggestions are welcome at <a href="mailto:%20wego@genomics.org.cn">wego@genomics.org.cn</a>. Here is a sample output generated by WEGO</p><p><a href="http://wego.genomics.org.cn/cgi-bin/wego/index.pl">http://wego.genomics.org.cn/cgi-bin/wego/index.pl</a></p><p><strong>GeneGO MetaCore</strong> (MIT)</p><p>GeneGo is a leading provider of data mining &amp; analysis solutions in systems biology. MetaCore, GeneGo's flapship product, is an integrated software suite for functional analysis of experimental data. MetaCore is based on a curated database of human protein-protein, protein-DNA interactions, transcription factors, signaling and metabolic pathways, disease and toxicity, and the effects of bioactive molecules.</p><p><a href="https://portal.genego.com/">https://portal.genego.com/</a></p><p><strong>GOEx</strong> (Stony Brook University)</p><p>GOEx facilitates organism-specific studies by leveraging GO and providing a rich graphical user interface. It is a simple to use tool, specialized for biologists who wish to analyze spectral counting data from shotgun proteomics.</p><p><a href="http://pcarvalho.com/patternlab">http://pcarvalho.com/patternlab</a></p><p><strong>GOssTo</strong></p><p>GOssTo and GOssToWeb are tools to calculate the <a href="https://en.wikipedia.org/wiki/Semantic_similarity#Biomedical_Informatics">semantic similarity</a> between genes or terms in the <a href="http://www.geneontology.org/">Gene Ontology</a>.</p><p><a href="http://www.paccanarolab.org/gosstoweb/">http://www.paccanarolab.org/gosstoweb/</a></p><p><strong>GO Workbench</strong></p><p>The Gene Ontology Analysis Viewer allows direct browsing of the Gene Ontology, and also the visualization of GO Term analysis results.</p><p><a href="http://wiki.c2b2.columbia.edu/workbench/index.php/Gene_Ontology_Viewer">http://wiki.c2b2.columbia.edu/workbench/index.php/Gene_Ontology_Viewer</a></p><p>Some other useful list of GO software and tools is available at <a href="http://www.geneontology.org/GO.tools.shtml#browser">http://www.geneontology.org/GO.tools.shtml#browser</a></p><p>Yet another useful webpage with list of GO tools at <a href="http://neurolex.org/wiki/Category:Resource:Gene_Ontology_Tools">http://neurolex.org/wiki/Category:Resource:Gene_Ontology_Tools</a></p><p>&nbsp;</p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>

</channel>
</rss>