# 20.109(S13):Assess protein function (Day8)

## Contents

## Note

A few additions were made to the end of the introduction, as well as to the protocol, on Tuesday afternoon. Should be all set now!

## Introduction

This is it, folks! Moment of truth. Time to find out how the proteins that you worked so hard to make, purify, and test really behave. Although you should be able to produce reasonable titration curves by following the example of Nagai, the introduction/review of binding constants below may help contextualize your analysis.

Let’s start by considering the simple case of a receptor-ligand pair that are exclusive to each other, and in which the receptor is monovalent. The ligand (L) and receptor (R) form a complex (C), which reaction can be written

**Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle R + L \rightleftharpoons\ ^{k_f}_{k_r} C }**

At equilibrium, the rates of the forward reaction (rate constant = **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle k_f}**
) and reverse reaction (rate constant = **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle k_r}**
) must be equivalent. Solving this equivalence yields an equilibrium dissociation constant **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle K_D}**
, which may be defined either as **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle k_r/k_f}**
, or as **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle [R][L]/[C]}**
, where brackets indicate the molar concentration of a species. Meanwhile, the fraction of receptors that are bound to ligand at equilibrium, often called *y* or θ, is **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle C/R_{TOT}}**
, where **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle R_{TOT}}**
indicates total (both bound and unbound) receptors. Note that the position of the equilibrium (i.e., *y*) depends on the starting concentrations of the reactants; however, **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle K_D}**
is always the same value. The total number of receptors **Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle R_{TOT}}**
= *[C]* (ligand-bound receptors) + *[R]* (unbound receptors). Thus,

**Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle \qquad y = {[C] \over R_{TOT}} \qquad = \qquad {[C] \over [C] + [R]} \qquad = \qquad {[L] \over [L] + [K_D]} \qquad}**

where the right-hand equation was derived by algebraic substitution. If the ligand concentration is in excess of that of the receptor, *[L]* may be approximated as a constant, *L*, for any given equilibrium. Let’s explore the implications of this result:

- What happens when
*L*<<**Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle K_D}**?

- →Then
*y*~**Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle L/K_D}**, and the binding fraction increases in a first-order fashion, directly proportional to*L*.

- →Then

- What happens when
*L*>>

- →In this case
*y*~1, so the binding fraction becomes approximately constant, and the receptors are saturated.

- →In this case

- What happens when
*L*=

- →Then
*y*= 0.5, and the fraction of receptors that are bound to ligand is 50%. This is why you can read*[L]*) is equal to**This is a great rule of thumb to know.**

- →Then

The figures at below demonstrate how to read *L* value is associated with a particular equilbrium value of *y*, while the curve as a whole gives information on the global equilibrium constant

Of course, inverse pericam has multiple binding sites, and thus IPC-calcium binding is actually more complicated than in the example above. The

For any given mutant, things may be more complicated. Keep in mind that we are not directly measuring calcium binding, but instead are indirectly inferring it based on fluorescence (for both mutant and wild-type IPC). Said change in fluorescence requires the participation not only of calcium, but also of M13. So besides the four separate calcium binding sites in calmodulin, the M13 binding site influences apparent affinity and apparent cooperativity. In short, be careful about how you describe the meanings of our binding parameters in your reports.

Returning to the big picture: when you write your research article, be sure to consider how changes in both binding affinity and cooperativity (and even potentially raw fluorescence differences) can affect the practical utility of a sensor.

## Protocols

You will analyze your calcium titration assay data in two steps. First, you will get a rough feel for how your mutants changed (or didn't) compared to wild-type IPC by plotting the two replicate values and their average, in both raw and processed form. Second, you will take the average processed values and plug them into some MATLAB code that will more precisely tell you the affinity and cooperativity of each protein with respect to calcium.

### Part 1: Titration curve in Excel and first estimate of K_{D}

Today you will analyze the fluorescence data that you got last time. Begin by analyzing the wild-type protein as a check on your work (your curve should resemble Nagai's Figure 3L), and then move on to your mutant samples. If you are not familiar with manipulations in Excel, use the *Help* menu or ask the teaching faculty for assistance.

- Open an Excel file for your data analysis. Begin by making a column of the free calcium concentrations present in your twelve test solutions. Assuming a 1:1 dilution of protein with calcium, the concentrations are: 10 nM, 50 nM, 100 nM, 200 nM, 400 nM, 500 nM, 600 nM, 800 nM, 1 μM, 2.5 μM, 10 μM, 100 μM. Be sure to convert all concentrations to the same units.
- Now open the text file containing your raw data as a tab-delimited file in Excel (you can download the file from today's Talk page). Convert the row-wise data to column-wise data (using
*Paste Special*→*Transpose*), and transfer each column to your analysis file. Add column headers to indicate which protein is which, and analyze each replicate separately for now. Also include a column of your control samples that did not contain protein. - Begin by calculating the average of your blank samples, and bold this number for easy reference. It is the background fluorescence present in the calcium solutions and should be quite low. If necessary, subtract this background value from each of your raw data values. It may help to have a 6-column series called “RAW”, and another called “SUBTRACTED.”
- Next you should normalize your data. The maximum and minimum fluorescence values for a given titration series should be defined as 100% and 0% fluorescence, respectively, and every other fluorescence value should be expressed as a percentage in between. Think about how to mathematically express these conditions.
- First calculate the percent fluorescence for both replicates. Then make a new column and calculate the average percentage as well. Alternatively, average your data first, and then normalize the average data.
- If one data point seems really off from the other replicate and from the expected trend, you might consider it an outlier and delete it, especially if you have good reason to believe that there was a reason (error in pipetting, air bubble in that well) for the anomaly. Otherwise, you might be losing valuable information, and/or misleading anyone who tries to interpret your data.

- For each protein, plot this normalized data versus calcium concentration. Save these plots in case you want to include them in your report.
- You might plot the two replicates as points and their average value as a dashed line (see front page of this module).

- Note down the approximate inflection points of the curves, which should occur at half-saturation: these indicate the approximate values of the apparent

### Part 2: Improved estimate of K_{D} using MATLAB modeling

#### Preparation

- On the computers in 16-336, use the "Learning Biologic Genie" account. We will provide the password during class.
- Download these three files: S12_Fit_Main, Fit_SingleKD, and Fit_KDn. Move them to the username/Documents/MATLAB folder on your PC.
- Double-click on the MATLAB icon to start up this software.
- The main window that opens is called the command window: here is where you run programs (or directly input commands) and view outputs. You can also see and access the command history, workspace, and current directory windows, but you likely won’t need to today.
- In the command window, type
*more on*; this command allows you to scroll through multi-page output (using the spacebar), such as help files. - In addition to the command area, MATLAB comes with an editor. Click
*File*→*Open*and select the program**S12_Fit_Main**. It has the .m extension and thus is executable by MATLAB. Read the introductory comments (the beginning of a comment is indicated by a % sign), and then input your fluorescence data. - Read through the program, and as you encounter unfamiliar terms, return to the workspace and type
*help functioname*. Feel free to ask questions of the teaching faculty as well.- You might read about such built-in functions as
*logspace*and*nlinfit*. - You will also want to open and read
**Fit_SingleKD**– a user-defined function called by**S12_Fit_Main**– in the MATLAB editor. - If you type
*help function*you will learn the syntax for a function header. - Note that a dot preceeding an operator (such as A ./ B or A .* B) is a way of telling MATLAB to perform element-by-element rather than matrix algebra.
- Also note that when a line of code is
*not*followed by a semi-colon, the value(s) resulting from the operation will be displayed in the command window.

- You might read about such built-in functions as

#### Analysis

- Once you more-or-less follow Part 1 of the program, type
**S12_Fit_Main**in the workspace, hit return to run the program, and consider the following questions:- Why must the fluorescence data be transformed (from
*S*to*Y*) prior to use in the model? - What
- Figure 1 should display your wild type and mutant data points and model curves. How do they look in comparison to the curves you plotted in Excel?
- Figure 2 should display the residuals (difference between data and model) for your three proteins. If the absolute values are low, this indicates good agreement between the model and the data numerically. Whether or not this is the case, another thing to look for is whether the residuals are evenly and randomly distributed about the zero-line. If there is a pattern to the errors, likely there is a systematic difference between the data and the model, and thus the model does not reflect the actual binding process well. What are the residuals like for each of your modeled proteins?

- Why must the fluorescence data be transformed (from
- Now move on to Part 2 of the
**S12_Fit_Main**program. Part 2 also fits the data to a model with a single, ‘apparent’ value of- Visually, which model appears to fit your wild-type data better (Fig. 3 vs. Fig. 1)? Your mutant data?
- Do the respective residuals support your qualitative assessment (Fig. 4 vs. Fig. 2)?
- Numerically, how do the values of
*n*compare to the implicitly assumed value in Part 1? - Do you see changes in binding affinity and/or cooperativity between the wild-type, E67K/T79P/M124S, and X#Z samples? Do they match your
*a priori*predictions? **Don't forget to save any figures you want to use in your report!**If the legends are covering up your data, you can simply move them over with your mouse.

- Finally, you can skim Part 3 of the
**S12_Fit_Main**program. Don’t worry too much about the coding details, but do read through the comments.- Look at Part 1 of Figure 5: are the binding curves asymptotic, sigmoidal, or other? What does this shape indicate? You can use the zoom button to get a closer look at part of the plot, or the
*axis*command present in the code. (Don't worry too much about this question if it is unclear.) - Now look in the command window. What values of
*n*) do you get for your three proteins? How do the - Comparing the model and data points by eye (Part 2 of Figure 5), do you think it is a good model for any of your proteins? If so, which ones? What experimental limitations might prevent Hill analysis from working well, especially for some mutants?
- Why should only the transition region be analyzed in a Hill plot?
- What is the relationship between slope and
*n*, and intercept and*n*?

- Look at Part 1 of Figure 5: are the binding curves asymptotic, sigmoidal, or other? What does this shape indicate? You can use the zoom button to get a closer look at part of the plot, or the
- If your mutant proteins are not well-described by any of the models so far, what kind of model(s) (qualitatively speaking) do you think might be useful?
- Optional: If your data might be well-described by a model with two KD's (or if you are interesting in exploring some sample data that is), download and run Fit_TwoKD and Fit_TwoKD_Func.

## For next time

- Now that you have completed all of the assays for Module 2 (except for analysis), prepare a high-level outline of your results section. Specifically, you should write sub-section titles, and beneath each title write a few short phrases indicating what content will be included in that sub-section. You don't need to include any specific numbers or even specific findings (except perhaps in the titles), just the
*type*of content that you will have. Do, however, include some sense of your narrative logic -- topic sentences and transitions may be phrases rather than complete sentences, but in any case these may be the best way to clarify your plans.**Please feel free to turn this assignment in early, in order to get it back early, to improve usefulness as you write your reports.** - Please post your findings to the table on today's Talk page by 5 pm on Wednesday, April 17th -- but ideally much sooner!