Tuesday, March 8, 2016
March 08, 2016 at 04:01AM
Today I Learned: 1) Addgene (and probably other companies) sells libraries of DNA parts in golden braid formats. The only catch is that they're almost certainly not compatible with libraries developed by other labs (including ours) so now there are at least several and possibly many non-compatible libraries siloed by their cut sites. So close, yet so far.... 2) ...a bit about the state of neuroscience from Dawna Bagherian I don't think I can summarize it better than her, so I quote: "I'm going [to a particular neuroscience talk] but I feel like I've heard this talk a thousand times. Every month someone has the revelation that cortical units don't necessarily encode one dimensional information and it's so surprising." Thanks Dawna Bagherian! 3) A tasty recipe: peanut butter, whey powder, honey, and oatmeal, in some reasonable amounts. Mix. Roll into balls. Eat or store for a while. Now to find a vegan substitute for whey powder.... Thanks to Suzannah Fraker for teaching me this!
Sunday, March 6, 2016
March 06, 2016 at 09:13PM
Today I Learned: 1) There are anti-fouling paints for oceangoing ships that use capsaicin or chemical analogues to keep molluscs off. Clinging to a ship covered in hot sauce is apparently Not Very Fun. There's something odd about this, though -- why is it that capcaisin is painful to mammals and to molluscs but not to birds? Maybe it's a matter of delivery, so that if you rubbed capcaisin on a bird wound it would hurt just as much, but bird mouths don't absorb it? 2) I've heard wildly varying reports about the profitability of vaccines. On one hand, I've heard conspiratorial claims that companies make a lot of money off of vaccines, and are therefore trying to hide any evidence of deleterious effects of vaccination. On the other hand, I've heard that vaccines essentially don't make any money, and the companies that make them do so as a service more than a means of profit. Which is true? I'm not *completely* sure, but a little Googling suggests to me that it's... kind of both. First off, it seems that, for a number of reasons, vaccines have historically been wildly *un*profitable, particularly compared to drugs and other medical tech. The number of vaccine-producing companies has been shrinking since the 50s as companies have gotten out of the business, resulting in frequent vaccine shortages since the late 1990s. Source: http://ift.tt/16EogQd. However (and be aware that the following information is based off a single Atlantic secondary article (http://ift.tt/1TCF4Nm), making this paragraph one of the most poorly-researched paragraphs I've put out to date), vaccines have become a LOT more profitable since 2000, largely because of massively expanded access to vaccines in developing countries. So now there's a lot more money involved. 3) Wedding rings are not risk-free. According to a report by the Commission de la Sécurité des Consummateurs (http://ift.tt/1I1C865 WARNING: due to the nature of the report there's some highly disturbing imagery here) wedding rings are responsible for something like 300 cases per year over a roughly 60 million person population, which some quick estimates of mine (and some numbers off wiki) suggest is about TEN TIMES more than the rate of shark attacks in Australia. Most occur during everyday activity, and most cause serious damage requiring some form of microsurgery. Related, for all of you out there considering being doctors (*cough* Caroline Golino *cough*): http://ift.tt/1TCF2oJ
March 06, 2016 at 03:35AM
Today I Learned: 1) Apparently I've been cooking garlic wrong this whole time! 2) Tree rings are used to calibrate carbon dating. We know that a tree grows a new ring every year, so we can measure the carbon-14 fraction in different rings to calibrate how much decay to expect over different times (in woody tissues, at least). 3) For reasons I still don't entirely understand, flying at the speed of sound is much, much rougher and more unstable than either flying well below *or* well above the speed of sound. As a result, supersonic aircraft are designed to quickly accelerate through mach 1 to at least mach 1.05.
Friday, March 4, 2016
March 05, 2016 at 01:52AM
Today I Learned: 1) New trick for cooking with garlic -- instead of adding it to the pan as the last ingredient, just a minute or two before serving, add it as the *first* ingredient, cook it for about a minute (until it just starts to brown), take it out, and add it back at the end. Advantages: the garlic gets very well cooked through, and it... maybe adds some garlic flavor to the rest of the meal? Only tried this once so far, and it seemed to add a nice aftertaste. Need more sample size. Disadvantages: you have to pay close attention while the garlic cooks, which means it's hard to be preparing other ingredients in parallel. Also, taking out the garlic is messy, and there's some loss in whatever container you use to hold the garlic. Speaking of which, you end up having to wash whatever dish you hold the garlic in, which is one more thing to wash. Overall, I'm not entirely sold, but I may want to try it a few more times to get a better feel for the effect it has on flavor. Tip from Erik Jue! 2) There are purple fluorescent proteins. Of course there are purple fluorescent proteins. There's a purple fluorescent protein called mPlum. Of course it's called mPlum. 3) Primer design and primer overhang extension is a lot to teach someone who isn't an experienced biologist at once, if you expect them to immediately be able to apply that information.
Thursday, March 3, 2016
Wednesday, March 2, 2016
March 03, 2016 at 02:35AM
Today I Learned: 1) The story of the competition race the Human Genome Project (HGP funded by NIH, making it a public project) and Celera (a private company run by Craig Venter) is quite fascinating, and it's a really fun story to pick sides on and argue about who "won". You can really go back and forth on it: HGP published the first assembled draft something like a few days before Celera, making it technically the first project to publish; but HGP had an eight-year head start on Celera, so Celera was really the spiritual victor (though it should be noted that even the public project finished under budget and two years ahead of schedule), especially because the public project draft wasn't particularly complete; but Celera was trying to essentially patent the important parts of the human genome and sell it, while HGP was going to make everything open access (and did, which massively accelerated research in many fields of biology), so HGP was the ethical victor; but Celera developed super-powerful sequencing techniques that totally revolutionized genomic sequencing (and which allowed HGP to finish on time...), *and* they completed the project for about a tenth the money as the public project, so Celera was clearly the technologic and scientific victor. Today I learned a new piece of the story. To explain this, I'll need to explain genomic assembly, which requires explaining shotgun sequencing, which is the technique invented by Celera and eventually adopted by HGP to finish the project. If you already know how shotgun sequencing works and what assembly is, you can skip the next three paragraphs. Before shotgun sequencing, there was Sanger sequencing. Sanger sequencing works like this: you amplify a stretch of DNA with PCR (a technique for producing lots of DNA from a targeted template sequence) but you also randomly incorporate special fluorescent versions of C, G, T, and A that terminate amplification. That gives you a bunch of fragments of the target DNA of different lengths, with a fluorescent nucleotide on the end of each. The color of the nucleotide depends on the letter at that nucleotide. You then run this mix on an gel, which separates the fragments by length. You look at the color of each band, and that tells you which nucleotide is at the end of the fragment of that length. You can read colors right down the line of bands. (technically that isn't *quite* how Sanger sequencing was done in the early days of the project, but it's close enough). The problem with this technique is that you have to know the sequence of the DNA at at least one end of the thing you're trying to sequence for the PCR to work, and preferably you should know both ends. This is a problem when the whole point is to figure out what the sequence of the DNA is. What the HGP did was to sequence from some known bit of the human genome, then use the new sequence to amplify the next bit, then the next bit, and a few hundred nucleotides at a time they could eventually sequence it all. Shotgun sequencing uses the same idea, except that before the Sanger reaction to add fluorescent nucleotides, you shear the DNA you want to sequence in to bazillions of little fragments of a few hundred bases each, which you can then clone into a ton of plasmids. You amplify each plasmid in bacteria, then sequence the plasmid. Since you know the sequence of most of the plasmid, it's trivial to amplify. This way, you don't have to bootstrap your way through the genome -- you can just sequence thousands or millions of fragments at once. Combined with new machines for performing the sequencing reactions more efficiently, shotgun sequencing allowed Celera to churn through the genome ridiculously faster than the HGP could with Sanger sequencing. There's a bit of a catch, though. With Sanger sequencing, you get a bunch of slightly overlapping sequences, in order, which you can easily string together into a whole genome. With shotgun sequencing, you get millions of *randomly selected* fragments, with no information about where they came from other than "somewhere in the genome". With enough random fragments, you can find overlapping fragments and stitch them together into entire chromosomes... but that's a computationally difficult puzzle to solve. This is the problem of assembly. This is where UCSC comes in (that's the University of California Santa Cruz). David Haussler, a professor at UCSC, was tasked with assembling the fragments from the public genome project. I think there were others involved, but Haussler is the only one I know of, and he ended up being the most critical. Anyway, one of Haussler's graduate student, an industrious fellow named Jim Kent, was particularly interested in the assembly project and came up with an assembly algorithm, then wrote up an assembler in about four weeks of intense coding. During that time, he also wrote the world's first interactive web-based genome browser, which was released with the public genome project draft as the UCSC Genome Browser, probably the most popular single tool in the world for retrieving data about the human genome (with the possible exception of BLAST?). Kent and Haussler deployed the assembler on a hastily-assembled cluster of about 100 Pentium III desktops. Now, this was 2000, and Pentium IIIs weren't as laughable as they are now, but for reference consider that a typical Pentium III is slower and less powerful than your average cell phone processor today. Admittedly, there were 100 of them... but Celera was using rather more powerful computers, better optimized for the kind of string comparisons required for assembly, and they had THOUSANDS of them. Haussler and Kent released their first assembled genome three days before Celera. 2) DNA sequences, espeically for populations are really more naturally viewed as graphs than as strings. The standard way to represent a DNA sequence (say, the human genome) and its variants (say, YOUR genome in all of its quirky variation) is to have a canonical reference sequence against which you align all sequences, and individual variants are noted against the reference. For humans, there is one public reference genome, which is now on its 38th version, against which all human genome assembly is performed. If you were to get sequenced, your genome would be mapped against this reference, and you would essentially get a list of differences between your genome and the reference. Instead, you can think of a set of sequences as a graph of connected short sequences. This is way easier to explain with pictures, but I run a text-only TIL, gosh darnit, so here goes. Consider these four example genomes of a very, very small organism: 1) ATTGTTTTGCGCA 2) ATTCTTATGCGCA 3) ATTGTTTTGCGCA 4) ATTCTTCCCCCTTGCGCA The traditional way to think about these genomes would be to build a "consensus sequence" that best represents the common elements of all of them, which would probably be "ATTGTTTTGCGCA". Genomes 1 and 3 are exactly the reference sequence; genome 2 has a mutation in the 7th nucleotide; genome 4 has an insertion "CCCCC" in between the 7th and 8th nucleotides. Alternatively, you could represent these sequences collectively as a graph where each node is a short sequence and directed edges between nodes means "that sequence follows this one" with a weight proportional to the frequency at which those two sequences go together. So the graph would start with the node "ATTGTT"; that node would point to each of the nodes "T", "A", and "CCCCC", with weights of 2, 1, and 1, respectively; and each of those nodes would point to the sequence "GCGCA". If you trace any path through the graph from beginning to end, it spells out a sequence. You do lose some information in this representation, like which mutations are associated with which other mutations, but there are advantages too. For one thing, it's a natural way to visualize the variation within a population. It's also helpful for assembly -- any variations from the reference sequence mess up the assembly process, but using a graph representation, you know what the most common variations are and can account for them. The graph representation also gives you a clear idea of what the most variable regions of the genome are, and which ones tend to stay constant. 3) A liquid biopsy is when you take blood from a cancer patient, filter out all the cells, and sequence all of the bits of DNA you can find floating around. It's not a very efficient way of sequencing a cancer, but it *is* highly uninvasive and easy to perform, and apparently there's usually enough cancer DNA floating around to get a good idea of what cancer it is.
Tuesday, March 1, 2016
March 02, 2016 at 02:40AM
Today I Learned: 1) Unstructured proteins are not the same as denatured proteins. The term "unstructured protein" is a rather glaring misnomer. Unstructured proteins almost always have structure, and well-defined structure at that. The "unstructured" tag just means that they aren't made of standard protein building blocks like alpha helixes and beta sheets. One way to think of it is that if anyone but an experienced protein scientist/engineer looked at a snapshot of an unstructured protein, they wouldn't be able to tell whether or not it was denatured, because it wouldn't have any of the usual protein structural features, BUT if you looked at a million copies of that protein, it would always look more or less the same. A "denatured protein", on the other hand, truly isn't structured. Denatured proteins flop all over the place; if you looked a million copies of the same denatured protein, they would all have different shapes. Thanks to Jeanne Morin-Leisk for teaching me about unstructured/denatured proteins! 2) When inserting DNA into plasmid vectors, it's a good idea to run a control reaction that doesn't insert anything. This screens for whole, uncut plasmids contaminating your vector -- if your control transformation has a lot of colonies, that means you can expect a lot of your actual transformations to be uncut vector, not your actual construct. If you have just as many control colonies as experimental ones, then you probably don't have any good colonies and you don't need to bother screening. A caveat: Gibson reactions tend to produce a lot of colonies in control reactions, even when the main reactions work just fine. ...I realize that the above paragraph won't mean much if you haven't done cloning before. For those of you, the tldnr is: today I learned a potentially useful control condition to use when performing certain common cloning reactions. Also, to be clear, here and in the rest of molecular biology, "cloning" just means "making DNA from other pieces of DNA", and has nothing to do with copying organisms. 3) Mimiviruses! Mimiviruses are MASSIVE viruses that infect amoeba*. How massive? Well, they were thought to be bacteria for a long time, because they kind of look like bacteria under a microscope (they're between 400 and 600 nanometers across, depending on how you measure, which is about half the length of a typical E. coli cell). Mimiviruses (obligatory: mimiviri?) also have a LOT of DNA -- the mimivirus genome is more than a megabase, encoding almost 1,000 genes, which is significantly larger than some bacteria (though still smaller than most, to my knowledge). More interestingly yet, mimiviruses carry several genes for amino acid and nucleotide synthesis, making them significantly more self-sufficient than your average virus and arguably more self-sufficient than some parasitic bacteria (I'm guessing mimiviruses can replciate their own DNA, but they definitely don't have their own ribosomes, so they can't produce proteins on their own). Mimiviruses are a contentious topic among scientists-that-know-about-mimiviruses. There's a lot of question about how mimiviruses came to be -- are they descended from parasitic bacteria that gradually lost their cytoplasm and cell walls, developing protein coats in their place? Or are they viruses that incrementally incorporated host genes for metabolism to gain more and more functionality? Or was it a virus that independently evolved genes for metabolism? Some scientists even been claim that mimiviruses, along with other closely-related viruses, meet criteria for life** and should be considered a fourth domain of life alongside prokarya, eukarya, and archaea. Questions about evolutionary origins like this are very difficult to answer (as Mengsha Gong can attest!), and we will likely never definitively know how mimivirus came to be. * Appropriately enough -- things related to amoeba seem to have a weird habit of being disproportionately large. Check out Chaos carolinense. Also, how big do you think a typical amoeba's genome is? For reference, a human genome is ~6,000,000 base pairs, bacterial genomes range from a couple hundred thousand base pairs to tens of millions of bases, and flu viruses have about 14,000 base pairs. Take a guess. Now go look up the genomes of Amoeba dubia and Amoeba proteus (for those without the ability to look it up, my apologies, but this really is a better exercise if you have to look it up yourself than if I post the answer). ** Personally, I think *all* viruses should be considered "alive", but that's a personal crusade of mine and it's not like it matters anyway.
Edit: A couple more things I learned yesterday but forgot to write down:
Edit: A couple more things I learned yesterday but forgot to write down:
1) Mimiviruses have their own viruses. That's not the first virus-infecting virus I've heard of -- adeno-associated viruses, or AAVs, are human adenovirus parasites that only infect human cells also infected by adenoviruses. AAVs are among the most popular vectors for viral gene therapy right now, in part because they can't replicate on their own. I also learned that a virus that requires another virus is called a "viriophage", which roughly translates to "virus eater".
2) It looks like mimiviruses have an immune system against their viriophages, which probably acts much like the CRISPR system of bacteria that has given us Cas9, which I've written about at some length in other posts. Seehttp://www.nature.com/.../crispr-like-immune-system..., if it's not behind a paywall.
Subscribe to:
Posts (Atom)