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).
Bioluminescent reporter assays are an excellent choice for analyzing gene regulation because they provide higher sensitivity, wider dynamic range and better signal-to-background ratios compared to colorimetric or fluorescent assays. In a typical genetic reporter assay, cells are transfected with a vector that contains the sequence of interest cloned upstream of a reporter gene, and the reporter activity is used to determine how the target sequence influences gene expression under experimental conditions. A second control reporter encoded on the same or a different plasmid is an essential internal control. The secondary reporter is used to normalize the data and compensate for variability caused by differences in cell number, lysis efficiency, cell viability, transfection efficiency, temperature, and measurement time.
For genetic reporter assays, using a secondary control vector with a weak promoter like PGK or TK to ensures that the control does not interfere with activation of your primary reporter vector. Transfection of high amounts of the control plasmid or putting the control reporter under control of a strong promoter like CMV or SV40 often leads to transcriptional squelching or other interference with the experimental promoter (i.e., trans effects). Reporter assays can also be used to quantitatively evaluate microRNA activity by inserting miRNA target sites downstream or 3´ of the reporter gene. For example, the pmirGLO Dual-Luciferase miRNA Target Expression Vector is based on dual-luciferase technology, with firefly luciferase as the primary reporter to monitor mRNA regulation and Renilla luciferase as a control reporter for normalization.
Here in Technical Services we often talk with researchers who are just starting their project and looking for advice on designing their genetic reporter vector. They have questions like:
How much of the upstream promoter region should be included in the vector?
How many copies of a response element will be needed to provide a good response?
Does the location of the element or surrounding sequence alter gene regulation?
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.