Friday, 7 March 2014

Publish and perish? Papers, blogs, criticism and the internet.


In recent meetings, journal club members have selected blog posts alongside traditional peer reviewed papers. These often complement the topics, and can offer practical, informal supplementary material to the published papers. 

The contrast between them has led to some discussion on the place of blogs in science. Journal clubs members are adept at the technical platforms behind them; most of the journal club is organised through a complex combination of email, Facebook, mailing lists, Google Drive and determination. Many maintain their own blogs and have active social media presences, but there has been a sense of not wanting to waste material on a blog post. My personal opinion is that the more 'runs on the board', that is, the longer your lists of published papers record, the more likely you are to feel confident in blogging the work (or preview of the work) rather than publishing.

The differences between published papers and blog posts, criticism of each and the role the internet plays in all of this will be the topic this week. Note that the goal this week will not necessarily be to discuss the merits of all papers in depth. Rather, I'd like to discuss the issues raised by the following papers, blogs and social media commentary, and determine if it is possible to publish and perish, and if so, how to avoid it. 

"Quilt plot"
Paper: "Quilt Plots: A Simple Tool for the Visualisation of Large Epidemiological Data" 
Response: PLoS one comments  and a blog post with commentary on the above and relevant links to other reactions.

Networks
Papers: 
Network link prediction by global silencing of indirect correlations
Network deconvolution as a general method to distinguish direct dependencies in networks

Response:
http://liorpachter.wordpress.com/2014/02/10/the-network-nonsense-of-albert-laszlo-barabasi/
http://liorpachter.wordpress.com/2014/02/11/the-network-nonsense-of-manolis-kellis/
http://liorpachter.wordpress.com/2014/02/12/why-i-read-the-network-nonsense-papers/
http://liorpachter.wordpress.com/2014/02/18/number-deconvolution/

Rebuttal:
http://liorpachter.files.wordpress.com/2014/02/response_to_nonsense_blog_post.pdf

Wednesday, 12 February 2014

Writing Gym

Not too long ago, I was discussing that well-known academic law of "publish or perish" with a seasoned bioinformatician. I was bemoaning my feelings of poor progress in my PhD, and pointed out that I often don't feel like I have results ready to write up.

My friend (who is real---this isn't Rich Dad, Poor Dad) observed that publications are in fact not something we have any control over. Once a piece of writing lands in the lap of some publisher, all we know is it might be accepted with some probability. It is pretty much out of our our hands as of that moment. And some pretty bad writing gets accepted sometimes, so you don't need to be a perfectionist with your submissions. If the reviewers have a problem, they'll let you know, so why not just unleash your crappy writing on them and hope for the best?

Although we don't have control over publishers and reviewers, we do have control over how much we write. So our publication rate can be maximised, on average, just by writing as often as possible. My friend even opined that the writing doesn't really need to be about our specialisation all the time. So long as it's scientific and it wouldn't be too embarrassing to have it seen by strangers, that will do for starters.

This is similar to the sentiment expressed by Stephen King in On Writing: "If you want to be a writer, you must do two things above all others: read a lot and write a lot. There's no way around these two things that I'm aware of, no shortcut." And I wouldn't want to disagree with Stephen King. He might respond by writing a story about my laptop getting possessed and eating my hands. Then it would really happen, because that is one of Stephen King's powers. And then I wouldn't be able to write anymore because I wouldn't have any hands.

Anyway, at first I was kind of skeptical about whether it was really possible for mere mortals such as myself to write all that much. I took my friend's words as encouragement to kind of think about writing more, but I hoped I could squirm my way out of it. I questioned whether it would be optimal to write for an hour a day, or a day per week, or a week per month. Probably more often than a month per year. Probably.

But at about the same time I encountered two suggestive links related to the same ideas. The first was a summary of research by Robert Boice on the Tomorrow's Professor Mailing List which suggests that academics who commit to writing a little bit every day end up being a lot more prolific than researchers who "binge write". The other was a Thesis Whisperer post describing the notion of "Shut up and Write!" meetings.

With all this churning in my mind, it seemed natural to propose that we segue the BGSA Journal Club with "Shut up and Write!"-style pomodoro sessions. Well, the traditional pomodoro technique consists of multiple sessions of different lengths broken by rest-breaks, but it currently seems that a single half-hour session is best for us. The name "Writing Gym" only came later, after running our first couple of pomodoro experiments. This wasn't really intended to distinguish ourselves from "Shut up and Write!" groups. It just seemed that "Writing Gym" is a more succinct and accurate description.

The goal of Writing Gym is to help everyone both with their short-term writing goals and also to acquire habits that will lead to more prolific research careers in the long-term. Writing in a group helps with motivation (hence the word "gym"), and we can also share ideas about what sorts of things to write and how to become better writers.

There is no expectation that writing at Writing Gym should be bioinformatics specific. It probably doesn't even have to be about science. There is no expectation that anyone is writing towards some specific deadline, although you can definitely use Writing Gym for that. We encourage writing that could potentially be shared with others, therefore no emails or facebook updates. (But, you know, it's not like we're going to get angry and kick people out if they decide to quietly procrastinate.) Examples of writing done so far have been preparing blog posts, writing conference abstracts and starting work on a submission for the Taming of Chance story competition. If you get stuck for ideas, you could always summarise one of the papers from Journal Club.

Having now had a couple of sessions, it seems like people find them useful and fun, so it is likely that Writing Gym will become an ongoing activity with BGSA. Every second week we have Journal Club, and in the off weeks, Writing Gym. The format and atmosphere (and people) are mostly the same between the two.

Like Journal Club, Writing Gym is an informal breakfast event. First, we chow down and drink coffee and chit-chat for a while. When everyone has arrived and more or less finished stuffing their face, we start by going around the table and nominating our intended writing topics. Then we get stuck into the half-hour pomodoro sesh. (Well, after ordering more coffee first. This is important.) When the half-hour is up, we go around the table again and describe whether we had any success. No one cares if someone doesn't accomplish a lot: better luck next time!

Where it goes from here remains to be seen. Ideas on new things to try would always be welcome. Maybe it wouldn't hurt to precede the pomodoro sessions with micro-workshops, short discussions on things such as good writing style, document-writing languages such as LaTeX or Markdown, why text-editors are better than word processors, and how best to use git to version control a document written in natural language. But such things would depend on the interests and goals of those attending, and whether it would get in the way of drinking coffee while defending our hands from possessed laptops.

Details:

Writing Gym is held at 8am on Tuesdays, on the alternate week to the Parkville Bioinformatics Journal Club. To stay up to date on the time and location, please join the mailing list.

Tuesday, 28 January 2014

Leading a Journal Club

Leading a Journal Club

Why lead a journal club meeting?
●                  It's a great way of having everyone get to know you.
●                  It's fun (speaking from personal experience).
●                  It gives you an opportunity to read something that you wouldn't otherwise devote the time to. Maybe something outside your field.
●                  It can give you the opportunity to get feedback and perspective about a paper that you are using in your own research. Maybe a pivotal paper in your literature review.
●                  It's a great opportunity to practise your professional skills like public speaking, summarising content and critical analysis. And you can do this all in a supportive and casual setting.
●                  That warm fuzzy feeling that you get from doing something nice that you don't have to do!
Step 1: Choose your meeting
There's a link to the schedule from this page: http://parkville-bioinformatics-journal-club.blogspot.com.au/ (top right corner)
Step 2: Choose your paper(s)
You would usually choose one or two papers. If one of the papers is quite domain specific you may like to choose a review paper as well to introduce people to the topic.
Step 3: Advertise your meeting
About a week before the meeting send the paper reference(s) to the group along the with the PDF and/or any relevant links. It also might be nice to explain briefly why you chose the paper(s). You can do this yourself via the mailing list, or send the details to the organisers and they will sort it out.
Step 4: Print the paper(s)
Come with a few print outs of the paper if possible. Usually about half the people print their own, so 4 or 5 copies is usually plenty.
Step 5: Summarise the paper(s)
Give a brief verbal summary of what the paper was about. Aim for about 5 mins. Think of this as a verbal abstract, but with perhaps even less detail. The idea is to give people who haven't read it a basic idea of what the paper was about.
You may want to finish with a comment about what you thought of the paper. What were it's strengths and weaknesses? Why did you choose it?
Step 5: Note some conversation topics
Note down a few questions or comments that came up for you when you were reading the paper. This way if the conversation lags you will have some things to bring up.
On the day:
These times are a guide only to give you and idea of what to expect. If you are leading the group, you are in charge, so feel free to work at your own pace.
7:55am Leader attempts to get there first and claim the big table at Dr Dax. 8:00am People start arriving and order coffee/breakfast. Keep an eye out for new members. They will be lurking, looking uncertainly at groups of people.
8:10am Consider doing a round of introductions, particularly if there are new members. Hand out printed papers as needed.
8:15am Leader gives a quick summary of the paper and then opens the discussion up to the group. If the conversation lags the leader should bring up one of their questions/points about the paper.
8:50am Round up the discussion. Check when the next meeting is and who is speaking (or ask for a volunteer).
Optional: Write a short blog post
If you're really keen, and you want to get even more professional development out the experience, you might consider writing a blog post. You can write about whatever you like and/or reuse your notes from the meeting.

Most of all, remember to enjoy yourself. This is not a formal presentation. No one is judging you. We are just a group of newbies trying to make sense of the field.

Wednesday, 16 October 2013

Topic posts

From time to time,  journal club participants will blog about topics discussed in a particular week. This is a purely optional part of leading the journal club, and the format and content is entirely up to the journal club member.

They may appear in an order different that of the journal club; they may also precede the week they are discussed.

The first is from Harriet: http://parkville-bioinformatics-journal-club.blogspot.com/2013/09/metagenomics-hypothesis-driven-fishing.html

Friday, 27 September 2013

Metagenomics: A hypothesis-driven fishing expedition?

Salmonella Typhimurium (red) invading cultured human cells
Rocky Mountain Laboratories, NIAID, NIH
Metagenomics is big news in Bioinformatics. Its rise to fame can be traced back to 2003, when Craig Venter (of private Human Genome Project fame) started sailing around the globe, collecting and sequencing water samples. His pilot project distinguished more than 1800 species, including 148 new types of bacteria [3].

Metagenomics is the study of genetic material recovered directly from environmental samples. There are two common applications: ecological samples (e.g. soil, water, industrial sites) and host-associated microbial communities (e.g. human gut, cow rumen). The metagenomics of microbial communities has been dubbed the microbiome.


Key definitions:
Metagenomics: the study of genetic material recovered directly from environmental samples.
Microbiome: the ecological community of commensal, symbiotic, and pathogenic microorganisms associated with a host organism.


Why do we do metagenomics? According to Scholz [1], we are probably trying to answer one or both of these questions:

Who is there?
What are they doing?

The “who” might be viruses, bacteria, archaea, or small eukaryotes like fungi, protists and plants. If you’re looking at a microbiome, you’re probably going to see plenty of DNA from the host as well. Many studies will focus on one or two of these groups. For example a study of the human gut microbiome, might be most interested in bacterial populations, while a deep-sea vent may be teaming with sulphur-loving archaea.

The goal of the “who” question is ideally to detect which species are present. This detailed level of species classification of often not possible, so most studies will try to detect larger groups, say at the genus, family, or order level. In many cases there will plenty of species that have never been seen before. These will need to be grouped into more manageable categories, often by sequence similarity. Classical taxonomic groupings of sequences are often beyond the computing power of modern metagenomics experiments. More often you would cluster the sequences at a given threshold of sequence similarity and then call the group an operational taxonomic unit (often abbreviated OTU). This gets around the issue of novel sequences popping up, but can get hairy when you are trying to infer an evolutionary relationship between sequences based on similarity.


16S sequencing is a common approach to the question of “who”. There are regions of the 16S ribosomal RNA gene which are remarkably well conserved between species. These sequences can be used to determine phylogenetic relationships between sequences and build up a picture of what types of organisms are present. There are already large databases of 16S sequences which can be used to identify known organisms.

The advantage of the 16S approach is that you can focus in on sequences that are useful for classifying known types of organisms. You also don’t have to worry so much about contamination from the host organism. The disadvantage is that by focusing in like this, you can miss new or unusual sequences. For example primers used to amplify bacterial 16S sequences, will do just that. They will not detect plant, animal or fungal sequences, because they are so diverse from the bacterial ones. However if your goal is to detect known bacteria (or at least bacterial reasonably closely related to known ones), then this is a great strategy. You can also save some money on sequencing if you only need to cover a small region.


An alternative is the shotgun sequencing approach. Here you simply sequence all DNA present in the sample. Here your sequencing is no longer biased by the primers you choose. You simply see everything. Of course you are still more likely to sequence more abundant species. You will probably have to do quite a lot more sequencing to detect the same number of species compared with 16S because your sequence could come from any (potentially uninformative) part of the genome.
Shotgun Sequencing - Wooley JC, Godzik A, Friedberg I (2010) A Primer on Metagenomics. PLoS Comput Biol 6(2): e1000667. doi:10.1371/journal.pcbi.1000667
With shotgun sequencing the question of who is there can become a little trickier. One approach is to look for representative genes. Find the genes that make one species different from another and you have a way to identify them. In general you will have more trouble figuring out who is there, but suddenly you have a rich source of information about what they are doing.

So “what are they doing?” We have answered our question about which species or operational taxonomic units are there, now we want to know what they are up to. We might be interested in particular gene pathways, for example if we pick up an ocean sample near an oil spill we may be looking for genes involved in metabolising hydrocarbons. We may be interested in pathways that span species, where groups of organisms are working in symbiosis. One way to find such genes is to map our reads against databases of enzymes such as KEGG http://www.genome.jp/kegg/. These are already well annotated in terms of function.


So what is the best way answer the two questions: Who is there? What are they doing? Should you do 16S sequencing or shotgun? It really depends on which question is most important to you and much much funding you have! But here are some of the main points to consider:

16S
  • Limited to identifying taxa 
  • Requires longer reads (e.g. 454) 
  • Can miss organisms when primers don’t bind 
  • Biased towards known species 
  • Don’t amplify host DNA when studying host-associated environments

Shotgun
  • Can do gene/pathway level analysis 
  • Can use shorter reads (e.g. Illumina) 
  • Preferably use paired end for assembly 
  • Requires higher depth to detect the same number of species compared with 16S Host DNA contamination 
  • More computationally intensive

References

  1. Scholz, Matthew B., Chien-Chi Lo, and Patrick SG Chain. "Next generation sequencing and bioinformatic bottlenecks: the current state of metagenomic data analysis." Current opinion in biotechnology 23.1 (2012): 9-15.
    http://www.sciencedirect.com/science/article/pii/S0958166911007245
  2. The human microbiome project (2012). Structure, function and diversity of the healthy human microbiome. Nature, 486, 207-214.
    http://eprints.ugd.edu.mk/2482/
  3. http://www.sciencemag.org/content/304/5667/66
  4. More on ‘omics: http://www.the-scientist.com/?articles.view/articleNo/13313/title/-Ome-Sweet--Omics---A-Genealogical-Treasury-of-Words/ 

Wednesday, 11 September 2013

The Parkville Bioinformatics Journal Club

Started in July 2013, this journal club aims to be a friendly and relaxed review of recent bioinformatics publications for students, research assistants and early career researchers in the Parkville precinct.

Topics vary and are chosen by our members, who take turns leading each week.

Meetings are regularly held on a Tuesday at 8am, and we allow about 10 minutes for introductions, and to purchase a coffee/juice/breakfast if you wish - we know it's early!

If you are interested, join our mailing list.