Despite significant advancements in antimalarial drugs and widespread efforts to prevent transmission over the past decade, deaths from malaria remain high, particularly in younger children. New drugs with novel modes of action are urgently needed to continue reducing mortality and address drug resistance in the malaria parasite, Plasmodium falciparum. While tens of thousands of compounds have been identified as potential candidates through massive screening efforts, scalable methods for identifying the most effective compounds are needed.
Enter firefly luciferase, a dynamic reporter tool to investigate drug action. By creating transgenic P. falciparum that express the luc reporter gene, the researchers could monitor drug action over time. When the parasite is killed, it stops making the luciferase reporter. Since there is no new production of luciferase, levels fall quickly after the parasite dies, and a luciferase assay can determine how fast each drug killed the parasite.
Imagine you’re taking a refreshing night swim in the warm blue waters of Vieques in Puerto Rico. You splash into the surf and head out to some of the deeper waters of the bay, when what to your wondering eyes should appear, but blue streaks of light in water that once was clear. Do you need to get your eyes checked? Are you hallucinating? No! You’ve just happened upon a cluster of dinoflagellates, harmless bioluminescent microorganisms called plankton, that emit their glow when disturbed by movement. These dinoflagellates are known to inhabit waters throughout the world but are generally not present in large enough numbers to be noticed. There are only five ecosystems in the world where these special bioluminescent bays can be seen, and three of them are in Puerto Rico.
But you don’t have to travel to Puerto Rico or swim with plankton to see bioluminescence. There are bioluminescent organisms all over the world in many unexpected places. There are bioluminescent mushrooms, bioluminescent sea creatures—both large and small (squid, jellyfish, and shrimp, in addition to the dinoflagellates)—and bioluminescent insects, to name a few. Bioluminescence is simply the ability of living things to produce light.
When you look at our top 10 most viewed blog posts of 2020, there’s no surprise that all relate to COVID-19. We have come a long way since the beginning of the year, thanks to tireless scientists and researchers around the globe. They have led the way in COVID-19 research, treatment, and testing. Let’s take a closer look at this top 10 list:
10. Tips to Maintain Physical Distance in the Lab
The spread of COVID-19 forced us to adapt and adjust to new ways in life, in work, and for this blog post, in the lab. In response to the pandemic, some labs shut down completely. Others have stayed open, especially those involving coronavirus research. This post provides 10 helpful distancing tips for researchers to stay safe and productive while working in the lab.
9. Investigation of Remdesivir as a Possible Treatment for SARS-2-CoV (2019 nCoV)
Scientists have worked hard to determine possible treatment for COVID-19. This blog post focuses on Remdesivir (RDV or GS-5734), an encouraging treatment used for the first case in the United States. It provides an in-depth look at numerous studies and clinical trials on Remdesivir as treatment for COVID-19. One key finding is that RDV needed to be administered either before or shortly after infection to limit lung damage.
This post was contributed by guest blogger, Scott Messenger, Technical Support Scientist 2 at Promega Corporation.
It’s always an exciting time in the lab when you find a new assay to answer an important research question. Once you get your hands on the assay, it is always good to confirm it will work for your experimental setup. Repeating the control experiment shown in the technical manual is a great way to test the assay in your hands.
After running that first experiment of your assay, it looks pretty good. The trends of control and treatment are consistent. Time to get on with the experiments…but wait—the RLUs (Relative Light Units) are two orders of magnitude lower than the example data! I can’t show this data to my colleagues; it doesn’t match. What did I do wrong?
This is a concern that we in Technical Services hear frequently. The concern is real, and I had this same thought when doing some of my first experiments using luminescence. When a question like this comes in, a Technical Service Scientist will make sure the experiment was performed as we described, and in most cases it is. We then start talking about RLUs (Relative Light Units).
Developing a vaccine that is safe, effective, easily manufactured and distributed is a daunting task. Yet, that is exactly what is needed in response to the COVID-19 pandemic.
Vaccine development, safety and efficacy testing take time. The mumps vaccine is thought to be the quickest infectious disease vaccine ever produced, and its development required four years from sample collection to licensing (2). However, there are many reasons to anticipate quicker development for a COVID-19 vaccine: Researchers are collaborating in unprecedented ways, and most COVID-19 scientific publications are free for all to access and often available as preprints. As of August 11, 2020, researchers around the globe have more than 165 vaccine candidates in development, 30 of which are in some phase of human clinical trials (1). The range of vaccine formulations available to scientists has expanded to include RNA and DNA vaccines, replication-defective adenovirus vaccines, inactivated or killed vaccines and subunit protein vaccines. Equally important is that vaccine developers and researchers have greater access to powerful molecular biology tools like bioluminescent reporters that enable quicker testing and development.
Synthetic biology—genetically engineering an organism to do or make something useful—is the central goal of the iGEM competition each year. After teams conquer the challenge of cloning their gene, the next hurdle is demonstrating that the engineered gene is expressing the desired protein (and possibly quantifying the level of expression), which they may do using a reporter gene.
Reporters can also play a more significant role in iGEM projects when teams design their organism with reporter genes to detect and signal the presence of specific molecules, like environmental toxins or biomarkers. Three of the iGEM teams Promega sponsored this year opted to incorporate some version of NanoLuc® Luciferase into their projects.
NanoLuc® luciferase is a small monomeric enzyme (19.1kDa, 171 amino acids) based on the luciferase from the deep sea shrimp Oplophorus gracilirostris. This engineered enzyme uses a novel substrate, furimazine, to produce high-intensity, glow-type luminescence in an ATP-independent reaction. Unlike other molecules for tagging and detecting proteins, NanoLuc® luciferase is less likely to interfere with enzyme activity and affect protein production due to its small size.
NanoLuc® Luciferase has also been engineered into a structural complementation reporter system, NanoBiT® Luciferase, that contains a Large subunit (LgBiT) and two small subunit options: low affinity SmBiT and high affinity HiBiT. Together, these NanoLuc® technologies provide a bioluminescent toolbox that was used by the iGEM teams to address a diverse set of biological challenges.
Here is an overview of each team’s project and how they
incorporated NanoLuc® technology.
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.
No protein is an island. Within a cell, protein-protein interactions (PPIs) are involved in highly regulated and specific pathways that control gene expression and cell signaling. The disruption of PPIs can lead to a variety of disease states, including cancer.
Two general approaches are commonly used to study PPIs. Real-time assays measure PPI activity in live cells using fluorescent or luminescent tags. A second approach includes methods that measure a specific PPI “after the fact”; popular examples include a reporter system, such as the classic yeast two-hybrid system.
The stage is set. You’ve spent days setting up this experiment. Your bench is spotless. All the materials you need to finally collect data are laid neatly before you. You fetch your cells from the incubator, add your detection reagents, and carefully slide the assay plate into the luminometer. It whirs and buzzes, and data begin to appear on the computer screen. But wait!
Don’t let this dramatic person be you. Here are 8 tips from us on things to watch out for before you start your next luminescent assay. Make sure you’ll be getting good data before wasting precious sample!
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!
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.