This blog was written by Sebastien Smick, Research Technician in Dr. Jacquin Niles’ laboratory at Massachusetts Institute of Technology (MIT)
Our lab is heavily focused on the basic biology and drug discovery of the human bloodborne pathogen Plasmodium falciparum, which causes malaria. We use the CRISPR/Cas9 system, paired with a TetR protein fused to a native translational repressor alongside a Renilla luciferase reporter gene, to conditionally knock down genes of interest to create modified parasites. We can then test all kinds of compounds as potential drug scaffolds against these gene-edited parasites. Our most recent endeavor, one made possible by Promega, is a medium-low throughput robotic screening pipeline which compares conditionally-activated or-repressed parasites against our dose-response drug libraries in a 384-well format. This process has been developed over the past few years and is a major upgrade for our lab in terms of data production. Our researchers are working very hard to generate new modified parasites to test. Our robots and plate readers rarely get a day’s rest!
This post is written by guest blogger, Amy Landreman, PhD, Sr. Product Manger at Promega Corporation.
In December of 1990, Promega first discussed the use of firefly luciferase (luc) as an emerging reporter technology in the article, Firefly Luciferase: A New Tool for Molecular Biologists. At the time, the gene coding chloramphenicol acetyltransferase (cat) was most commonly used by researchers, but it was thought that the bioluminescent properties of firefly luciferase, extreme sensitivity and rapid simple detection, could make a significant difference in how molecular biologists tackled their research. Several months later, the first firefly luciferase reporter vectors and detection reagents became available as products, making this new technology more broadly accessible to the research community. Today firefly luciferase is no longer a “new tool”, with it and many other bioluminescent reporter technologies being standard elements of the modern research toolbox.
It’s a question I’m asked probably once a week. “What wavelength do I select on my luminometer when performing a luciferase assay?” The question is a good and not altogether unexpected one, especially for those new to bioluminescent assays. The answer is that in most cases, you don’t and in fact shouldn’t select a wavelength (the exception to this rule is if you’re measuring light emitted in two simultaneous luciferase reactions). To understand why requires a bit of an explanation of absorbance, fluorescence, and luminescence assays, and the differences among them.
Absorbance, fluorescence, and luminescence assays are all means to quantify something of interest, be that a genetic reporter, cell viability, cytotoxicity, apoptosis, or other markers. In principle, they are all similar. For example, a genetic reporter assay is an indicator of gene expression. The promoter of a gene of interest can be cloned upstream of a reporter such as β-galactosidase, GFP, or firefly luciferase. The amount of each of these reporters that is transcribed into mRNA and translated into protein by the cell is indicative of the endogenous expression of the gene of interest.
I’ve got a set of experiments planned that, if all goes well, will provide me with the answer I have been seeking for months. Plus, my supervisor is eagerly awaiting the results because she needs the data for a grant application, so I don’t want to mess it up. However, I am faced with a choice for my firefly and Renilla luciferase reporter assays: Do I use the Dual-Luciferase® Reporter Assay System or Dual-Glo® Luciferase Assay System? What’s the difference? How do I decide which to use? I’m so confused! Help!
Luciferase assays are useful tools for studying a wide range of biological questions. They can be performed easily by adding a reagent that provides components necessary to generate a luminescent signal directly to cells or a cell lysate. However, once this reagent has been added, how long you wait to measure the signal becomes a key consideration in generating consistent data. Dependent on which luciferase assay you use, you may need a luminometer that can use injectors to deliver the assay reagents. The reason for this is simple, but can be confusing to new users.
By clicking “Accept All”, you consent to the use of ALL the cookies. However you may visit Cookie Settings to provide a controlled consent.
If you are located in the EEA, the United Kingdom, or Switzerland, you can change your settings at any time by clicking Manage Cookie Consent in the footer of our website.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement".
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
6 months 2 days
This cookie is set by the provider Media.net. This cookie is used to check the status whether the user has accepted the cookie consent box. It also helps in not showing the cookie consent box upon re-entry to the website.
This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
This cookie is associated with Sitecore content and personalization. This cookie is used to identify the repeat visit from a single user. Sitecore will send a persistent session cookie to the web client.
This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.
1 month 18 hours 24 minutes
This cookie is used to calculate unique devices accessing the website.
This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
1 year 24 days
Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.
5 months 27 days
This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
This cookies is set by Youtube and is used to track the views of embedded videos.
This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.