|
Enter a Search String | Special character and space not allowed in the query term.
Search string should be at least 2 characters long. |
Reaction List for pathway PLC_g (Pathway Number 338) in Accession Ajay_Bhalla_2004_PKM_MKP3_Tuning (Accession Number 77) | Entries are grouped according to Pathway Number and they are alternately color coded using and color.
Further ordering can be done to the table header. indicates that ordering is done according to ascending or descending order. Keq is calculated only for first order reactions.
Kd is calculated only for second order reactions. [nA+nB <->nC or nA<->nC+nD, where n is number and A,B,C,D are molecules] |
|
Reaction Name | Pathway Name / Pathway No. | Kf | Kb | Kd | tau | Reagents | 1 | Ca_act_PLC_g | PLC_g
Pathway No. 338 | 180 (uM^-1 s^-1) | 10 (s^-1) | Kd(bf) = 0.0556(uM) | - | Substrate: PLC_g Ca
Products: Ca.PLC_g
| | Nice curves from Homma et al JBC 263:14 6592-6598 1988 Fig 5c. The activity falls above 10 uM, but that is too high to reach physiologically anyway, so we'll ignore the higher pts and match the lower ones only. Half-max at 1 uM. But Wahl et al JBC 267:15 10447-10456 1992 have half-max at 56 nM which is what I'll use. | 2 | Ca_act_PLC_g* | PLC_g
Pathway No. 338 | 11.9997 (uM^-1 s^-1) | 10 (s^-1) | Kd(bf) = 0.8334(uM) | - | Substrate: Ca PLC_G*
Products: Ca.PLC_g*
| | Again, we refer to Homma et al and Wahl et al, for preference using Wahl. Half-Max of the phosph form is at 316 nM. Use kb of 10 as this is likely to be pretty fast. Did some curve comparisons, and instead of 316 nM giving a kf of 5.27e-5, we will use 8e-5 for kf. 16 Sep 97. As we are now phosphorylating the Ca-bound form, equils have shifted. kf should now be 2e-5 to match the curves. | 3 | dephosph_PLC_g | PLC_g
Pathway No. 338 | 0.05 (s^-1) | 0 (s^-1) | - | - | Substrate: Ca.PLC_g*
Products: Ca.PLC_g
|
| Database compilation and code copyright (C) 2022, Upinder S. Bhalla and NCBS/TIFR This Copyright is applied to ensure that the contents of this database remain freely available. Please see FAQ for details. |
|