|
Enter a Search String | Special character and space not allowed in the query term.
Search string should be at least 2 characters long. |
Molecule Parameter List for E.S2_in | The statistics table lists the distribution of a molecule acting either as a substrate, product, enzyme or as a molecule within the network. The text color of a molecule is highlighted by color. | Statistics |
E.S2_in participated as | Molecule | Sum total of | Enzyme | Substrate of an enzyme | Product of an enzyme | Substrate in Reaction | Product in Reaction | No. of occurrences | 1 | 0 | 0 | 0 | 0 | 0 | 1 |
Accession and Pathway Details | |
Accession Name | Accession No. | Accession Type | Pathway Link | luciferase | 36 | Pathway | luciferase | This model is based on L. Yu. Brovko et al 1994, Biochemistry (Moscow) 59(2):195-201, 1994. The model replicates reaction scheme 3, and uses rates from table 2, but there are discrepancies in simulated results both with their simulations (fig 4) and with their experimental data. The overall time-course and luciferase dependence of luminiscence (Figs 1, 2, 3a) are reasonable semi-quantitative matches. |
E.S2_in acting as a Molecule in luciferase Network
Name | Accession Name | Pathway Name | Initial Conc. (uM) | Volume (fL) | Buffered | E.S2_in | luciferase Accession No. : 36 | luciferase Pathway No. : 186 | 0 | 999980000000 | No | |
E.S2_in acting as a Product in a reaction in luciferase Network
Kd is calculated only for second order reactions, like nA+nB <->nC or nA<->nC+nD, where n is number and A,B,C,D are molecules, where as for first order reactions Keq is calculated.
Kd for higher order reaction are not consider. |
Name | Accession Name | Pathway Name | Kf | Kb | Kd | tau | Reagents | k5_3 | luciferase Accession No. : 36 | luciferase Pathway No. : 186 | 0 (s^-1) | 0 (s^-1) | - | - | Substrate E.S2
Product E.S2_in
|
| 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. |
|