Title: Equilibrium Path Sampling Data for Two Glycosynthetic Reactions of Thermatoga maratima Alpha-L-Fucosidase D224G Open Access Deposited
|Citations to related material|
(2019). Equilibrium Path Sampling Data for Two Glycosynthetic Reactions of Thermatoga maratima Alpha-L-Fucosidase D224G [Data set]. University of Michigan - Deep Blue. https://doi.org/10.7302/f2ht-xw04
Files (Count: 4; Size: 677 GB)
ï»¿This is a brief documentation of the files stored in this directory. These files were produced in the course of research that resulted in the following publication:
Burgin, T. and Mayes, H. B. 2019. âMechanism of oligosaccharide synthesis via a mutant GH29 fucosidase.â Reaction Chemistry & Engineering 4: 402-9
This project aimed to discover and analyze the molecular mechanism of synthesis of two particular fucosylated oligosaccharide products in a mutant enzyme whose wild type performs the opposite reaction (cleavage of fucosyl glycosidic bonds). Discovery of the mechanism was performed using an unbiased simulations method known as aimless shooting, whereas analysis of the mechanism in terms of the energy profile was performed using a separate method known as equilibrium path sampling (EPS). The data in this directory concerns the latter method.
Files in this directory are first grouped into two subdirectories: eps_working and alpha13_eps_working. Each of these directories represents the complete dataset for equilibrium path sampling for a particular reaction pathway. The former concerns the reaction mechanism wherein a bond is formed connecting the fucosyl donor C1 to the acceptor O4, whereas the latter concerns a very similar mechanism but connecting the donor C1 to the acceptor O3. Experimental work by Cobucci-Ponzano et al. (see above paper for full citation) had revealed that both mechanisms were possible with roughly equal probability.
Within each of these subdirectories, files are grouped according to name. A full description of the details of EPS is beyond the scope of this document, but in short, the dataset consists of âforwardâ (âfwdâ) and âbackwardâ (âbwdâ) trajectories (.nc files) beginning from a shared âinitialâ (âinitâ) coordinate file (.rst or .rst7). The input files for these simulations are named as âeps[1-10].inâ depending on the length of the simulation. End-point restart files for each trajectory are also retained. Each pair of fwd and bwd trajectories is checked for its value along the reaction coordinate detailed in the paper, and the resulting data files in each directory âeps_results.outâ represent the collection of these results. These results can be translated into free energy profiles along the reaction coordinate using any number of methods, though this author would recommend Michael Shirtsâs MBAR approach.
The simulations in this study were conducted using the Amber 16 molecular simulations software package. As such, files are in Amber format. The corresponding Amber parameter/topology file for each of the coordinate/trajectory files is âts_guess.prmtopâ. A full inventory of the files is not included herein; however, the reader is directed to the âstatus.txtâ file in each subdirectory. This file enumerates each of the independent âthreadsâ of simulations in the following format:
[thread_name] acceptance ratio: X/Y, or Z%
Here, thread_name is the base name of the thread, of which there are Y âmovesâ. These moves are named as: [thread_name]_[y] (for y from 1 to Y), and each move should have a corresponding initial, forward, and backward trajectory/coordinate file as described above named as: [thread_name]_[y]_[init/fwd/bwd].[rst/rst7/nc]. The number of accepted trajectories X corresponds to the number of threads out of the total Y that contained at least one frame inside the target window of reaction coordinate ranges (again, see paper for a more detailed description of and references for EPS). The status line indicates the last-known status of the thread including met termination criteria if applicable. A history file for each thread can be found in the âhistoryâ subdirectory if more detailed acceptance information for each thread is desired.
Finally, a log file for each subdirectory is included, âas.logâ. This file contains a detailed log of the underlying work done by the script that was used to automate EPS.