forked from samplchallenges/SAMPL7
-
Notifications
You must be signed in to change notification settings - Fork 0
/
pKa-DanielleBergazinExampleFile-1.csv
We can make this file beautiful and searchable if this error is corrected: Illegal quoting in line 75.
178 lines (168 loc) · 7.44 KB
/
pKa-DanielleBergazinExampleFile-1.csv
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
# RELATIVE FREE ENERGY PREDICTIONS (for pKa prediction)
#
# This file will be automatically parsed. It must contain the following four elements:
# predictions, name of method, software listing, and method description.
# These elements must be provided in the order shown with their respective headers.
#
# Any line that begins with a # is considered a comment and will be ignored when parsing.
#
# PREDICTION SECTION
#
# It is mandatory to submit relative free energy (RFE) predictions for all 22 molecules. Incomplete submissions will not be accepted.
# Please report RFE standard error of the mean (SEM) and RFE model uncertainty.
#
# The data in each prediction line should be structured as follows:
# Microstate ID of reference state, Microstate ID of the predicted microstate, total charge, RFE, RFE SEM, RFE model uncertainty
#
# If you have evaluated additional microstates, include the following:
# Microstate ID of reference state, Microstate ID of the predicted microstate, total charge, RFE, RFE SEM, RFE model uncertainty, SMILES string of the predicted microstate
#
# The molecule ID of the other microstate needs to be in the format: `SMXX_extra001` (number can vary)
# Also email us the `.mol2` file of your microstate with explicit hydrogens and correct bond orders,
# Please send the `.mol2` file to the email listed on the instructions page.
#
# The list of predictions must begin with the 'Predictions:' keyword as illustrated here.
Predictions:
SM25_micro000,SM25_micro001,-1,2.25,0.02,0.02
SM25_micro000,SM25_micro002,0,1.01,0.08,0.02
SM25_micro000,SM25_micro003,-1,4.32,1.02,0.02
SM26_micro000,SM26_micro001,-1,4.21,0.12,0.02
SM26_micro000,SM26_micro002,0,7.01,0.58,0.02
SM26_micro000,SM26_micro003,-1,4.35,1.95,0.02
SM27_micro000,SM27_micro001,0,2.25,0.02,0.02
# Example of including an extra microstate
SM27_micro000,SM27_extra001,-1,2.25,0.02,0.02,CC1(COC1)[N-]S(=O)(=O)CCc2ccccc2
SM28_micro000,SM28_micro001,-1,2.25,0.02,0.02
SM28_micro000,SM28_micro002,0,1.01,0.08,0.02
SM28_micro000,SM28_micro003,-1,4.32,1.02,0.02
SM29_micro000,SM29_micro001,-1,2.12,0.02,0.02
SM30_micro000,SM30_micro001,-1,3.89,0.02,0.02
SM31_micro000,SM31_micro001,-1,1.67,0.02,0.02
SM32_micro000,SM32_micro001,-1,2.25,0.02,0.02
SM33_micro000,SM33_micro001,-1,2.36,0.02,0.02
SM34_micro000,SM34_micro001,-1,3.32,0.02,0.02
SM35_micro000,SM35_micro001,-1,1.76,0.02,0.02
SM35_micro000,SM35_micro002,0,1.01,0.08,0.02
SM35_micro000,SM35_micro003,1,3.02,0.38,0.32
SM36_micro000,SM36_micro001,-1,2.25,0.02,0.02
SM36_micro000,SM36_micro002,0,1.01,0.08,0.02
SM36_micro000,SM36_micro003,1,1.01,0.08,0.02
SM37_micro000,SM37_micro001,+1,2.25,0.02,0.02
SM37_micro000,SM37_micro002,0,1.01,0.78,0.02
SM37_micro000,SM37_micro003,0,1.41,0.08,0.33
SM37_micro000,SM37_micro004,-1,1.41,0.08,0.02
SM37_micro000,SM37_micro005,+1,1.06,0.08,0.01
SM38_micro000,SM38_micro001,-1,2.25,0.02,0.07
SM39_micro000,SM39_micro001,-1,2.23,0.12,0.04
SM40_micro000,SM40_micro001,-1,2.25,0.32,0.03
SM40_micro000,SM40_micro002,+1,1.01,0.08,0.05
SM41_micro000,SM41_micro001,-1,2.25,0.02,0.22
SM41_micro000,SM41_micro002,+1,1.05,0.89,0.54
SM42_micro000,SM42_micro001,-1,2.25,0.02,0.23
SM42_micro000,SM42_micro002,+1,1.03,0.45,0.77
SM43_micro000,SM43_micro001,-1,2.25,0.02,0.54
SM43_micro000,SM43_micro002,+1,1.01,0.08,0.99
SM43_micro000,SM43_micro003,+2,3.76,0.76,0.21
SM44_micro000,SM44_micro001,-1,2.25,0.02,0.34
SM44_micro000,SM44_micro002,+1,1.45,0.08,0.12
SM45_micro000,SM45_micro001,-1,3.25,0.45,0.02
SM45_micro000,SM45_micro002,+1,1.32,0.08,0.87
SM46_micro000,SM46_micro001,-1,2.89,0.02,0.44
SM46_micro000,SM46_micro002,+1,1.01,0.21,0.02
SM46_micro000,SM46_micro003,+2,1.67,0.08,0.56
#
#
# Please list your name, using only UTF-8 characters as described above. The "Participant name:" entry is required.
Participant name:
Teresa Danielle Bergazin
#
#
# Please list your organization/affiliation, using only UTF-8 characters as described above.
Participant organization:
University of California Irvine
#
#
# NAME SECTION
#
# Please provide an informal but informative name of the method used.
# The name of the method should not exceed 40 characters.
# The 'Name:' keyword is required as shown here.
Name:
RFE-prediction-method-name
#
#
# COMPUTE TIME SECTION
#
# Please provide the average compute time across all of the molecules.
# For physical methods, report the GPU and/or CPU compute time in hours.
# For empirical methods, report the query time in hours.
# Create a new line for each processor type.
# The 'Compute time:' keyword is required as shown here.
Compute time:
28 hours, CPU
5.5 hours, GPU
#
# COMPUTING AND HARDWARE SECTION
#
# Please provide details of the computing resources that were used to train models and make predictions.
# Please specify compute time for training models and querying separately for empirical prediction methods.
# Provide a detailed description of the hardware used to run the simulations.
# The 'Computing and hardware:' keyword is required as shown here.
Computing and hardware:
All the simulations were performed on two GeForce GTX 1080 on a single machine hosting an Intel Xeon Processor E5-2697 v4.
The replicas were divided into two sets of the same size and propagated in parallel on the two GPUs, while the exchange
stage was performed serially. We estimate the total wall-clock time spent doing parallel/serial work to be
approximately 95%/5% respectively.
# SOFTWARE SECTION
#
# List all major software packages used and their versions.
# Create a new line for each software.
# The 'Software:' keyword is required.
Software:
OpenMM 7.1.1
OpenMMTools 0.13.4
YANK 0.19.4
# METHOD CATEGORY SECTION
#
# State if your prediction method is better classified as an
# experimental database lookup (DL), linear free energy relationship (LFER),
# quantitative structure-property relationship or machine learning (QSPR/ML),
# quantum mechanics without empirical correction (QM) model, quantum mechanics with
# linear empirical correction (QM+LEC), and combined quantum mechanics and molecular
# mechanics (QM+MM), or Other, using the following category labels:
# `DL`, `LFER`, `QSPR/ML`, `QM`, `QM+LEC`, `QM+MM` or `Other`.
#
# Pick only one category label.
# The `Category:` keyword is required.
Category:
QSPR/ML
# METHOD DESCRIPTION SECTION
#
# Methodology and computational details.
# Level of details should be roughly equivalent to that used in a publication.
# Please include the values of key parameters with units.
# Please explain how statistical uncertainties were estimated.
# Use as many lines of text as you need.
#
# We strongly encourage you to submit your predicted macro pKa values in this section in consecutive lines following this format:
# compound name, macro pKa, initial formal charge, formal charge after transition, e.g.:
# SM25, 3.5, 0, +1
# This will allow us to check that our analysis of your free energies leads to the same endpoint as your analysis.
#
# All text following the 'Method:' keyword will be regarded as part of your free text methods description.
Method:
Free text methods section describing the approach and calculations in full detail.
Macro pKa values (these are purely an example and have no bearing on reality)
SM25, 3.5, 0, +1
SM26, 9.8, -1, 0
...
SM45, 11.0, 0, +1
#
#
# All submissions must either be ranked or non-ranked.
# Only one ranked submission per participant is allowed.
# Multiple ranked submissions from the same participant will not be judged.
# Non-ranked submissions are accepted so we can verify that they were made before the deadline.
# The "Ranked:" keyword is required, and expects a Boolean value (True/False)
Ranked:
True