diff options
Diffstat (limited to 'test/data/qprf-t6.json')
| -rw-r--r-- | test/data/qprf-t6.json | 197 |
1 files changed, 197 insertions, 0 deletions
diff --git a/test/data/qprf-t6.json b/test/data/qprf-t6.json new file mode 100644 index 0000000..46ab12d --- /dev/null +++ b/test/data/qprf-t6.json @@ -0,0 +1,197 @@ +{ + "meta": { + "description": "qprf report", + "title": "qprf report", + "qprf_version": "1.1", + "date": "" + }, + "visible": true, + "singleCalculations": { + "Date": "2016/08/21", + "Disclaimer and Instructions": "Please fill in the fields of the QPRF with information about the prediction and the substance for which the prediction is made. The information that you provide will be used to facilitate considerations on the adequacy of the prediction (model result) in relation to a defined regulatory purpose. The adequacy of a prediction depends on the following conditions: a) the (Q)SAR model is scientifically valid: the scientific validity is established according to the OECD principles for (Q)SAR validation; b) the (Q)SAR model is applicable to the query chemical: a (Q)SAR is applicable if the query chemical falls within the defined applicability domain of the model; c) the (Q)SAR result is reliable: a valid (Q)SAR that is applied to a chemical falling within its applicability domain provides a reliable result; d) the (Q)SAR model is relevant for the regulatory purpose: the predicted endpoint can be used directly or following an extrapolation, possibly in combination with other information, for a particular regulatory purpose. A (Q)SAR prediction (model result) may be considered adequate if it is reliable and relevant, and depending on the totality of information available in a weight-of-evidence assessment (see Section 4 of the QPRF).", + "Time": "", + "Title": "My QPRF Report", + "Version": "2.1" + }, + "arrayCalculations": { + "1. Substance": { + "colNames": [ + "Title", + "Value" + ], + "values": { + "General": [ + "Instructions", + "This section is aimed at defining the substance for which the (Q)SAR prediction is made." + ], + "1.1": [ + "CAS number", + "7732-18-5" + ], + "1.2": [ + "EC number", + "Report the EC number." + ], + "1.3": [ + "Chemical name", + "Report the chemical names (IUPAC and CAS names)." + ], + "1.4": [ + "Structural formula", + "Report the structural formula." + ], + "1.5 General": [ + "Structure codes", + "Report available structural information for the substance, including the structure code used to run the model. If you used a SMILES or InChI code, report the code in the corresponding field below. If you have used any another format (e.g. mol file), please include the corresponding structural representation as supporting information." + ], + "1.5 a.": [ + "SMILES", + "Report the SMILES of the substance (indicate if this is the one used for the model prediction)." + ], + "1.5 b.": [ + "InChI", + "Report the InChI code of the substance (indicate if this is the one used for the model prediction)." + ], + "1.5 c.": [ + "Other structural representation", + "Indicate if another structural representation was used to generate the prediction. Indicate whether this information is included as supporting information. Example: 'mol file used and included in the supporting information'." + ], + "1.5 d.": [ + "Stereochemical features", + "Indicate whether the substance is a stereo-isomer and consequently may have properties that depend on the orientation of its atoms in space. Identify the stereochemical features that may affect the reliability of predictions for the substance, e.g. cis-trans isomerism, chiral centres. Are these features encoded in the structural representations mentioned above?" + ] + } + }, + "2. General information": { + "colNames": [ + "Title", + "Value" + ], + "values": { + "General": [ + "Instructions", + "General information about the compilation of the current QPRF is provided in this section." + ], + "2.1": [ + "Date of QPRF", + "Report the date of compilation of the QPRF. Example: “01 January 2007”." + ], + "2.2": [ + "QPRF author and contact details", + "Report the contact details of the author of the QPRF." + ] + } + }, + "3. Prediction": { + "colNames": [ + "Title", + "Value" + ], + "values": { + "General": [ + "Instructions", + "The information provided in this section will help to facilitate considerations on the scientific validity of the model (as defined in the OECD Principles for the validation of (Q)SAR models) and the reliability of the prediction. Detailed information on the model are stored in the corresponding QMRF which is devised to reflect as much as possible the OECD principles. Remember that the QMRF and the QPRF are complementary, and a QPRF should always be associated with a defined QMRF." + ], + "3.1 General": [ + "Endpoint", + "(OECD Principle 1)" + ], + "3.1 a.": [ + "Endpoint", + "Define the endpoint for which the model provides predictions (this information should correspond to the information provided in the QMRF under fields 3.2 and 3.3). Example: 'Nitrate radical degradation rate constant KNO3'." + ], + "3.1 b.": [ + "Dependent variable", + "Report the dependent variable for which the model provides predictions including any transformations introduced for modelling purposes (note that this information should correspond to the information provided in the QMRF under field 3.5). Example: '-log (KNO3)'." + ], + "3.2 General": [ + "Algorithm", + "(OECD Principle 2)" + ], + "3.2 a.": [ + "Model or submodel name", + "Identify the model used to make the prediction and possibly report its name as stored in the corresponding QMRF; in the QMRF the model name is reported in the field QSAR identifier. Examples: “BIOWIN for Biodegradation”; “TOPKAT Developmental Toxicity Potential”. If applicable identify the specific submodel or algorithm applicable to the specific chemical Examples: 'BIOWIN '; 'TOPKAT Skin Irritation Acyclics (Acids, Amines, Esters) MOD v SEV Model'; 'ECOSAR esters model'." + ], + "3.2 b.": [ + "Model version", + "Identify, where relevant, the version number and/or date of the model and submodel." + ], + "3.2 c.": [ + "Reference to QMRF", + "Provide relevant information about the QMRF that stores information about the model used to make the prediction. Possible useful pieces of information are: availability, source, reference number (if any) of the QMRF. Examples: 'The corresponding QMRF named -BIOWIN for Biodegradation- has been downloaded from the JRC QSAR Model Database'; 'The corresponding QMRF named -TOPKAT Skin Irritation Acyclics (Acids, Amines, Esters) MOD v SEV Model- has been newly compiled'." + ], + "3.2 d.": [ + "Predicted value (model result)", + "Report the predicted value (including units) obtained from the application of the model to the query chemical. For an expert system such as Derek for Windows, report the alert triggered together with the reasoning. Example: ' aromatic amine - mutagenicity, plausible'." + ], + "3.2 e.": [ + "Predicted value (comments)", + "If the result is qualitative (e.g. yes/no) or semi-quantitative (e.g. low/medium/high), explain the cut-off values that were used as the basis for classification. In reporting the predicted value, pay attention to the transformations (e.g. if the prediction is made in log units, apply anti-logarithm function)." + ], + "3.2 f.": [ + "Input for prediction", + "Specify what kind of input was used to generate the prediction (SMILES, mol file, graphical interface etc). Please provide the structure code used to generate the prediction (unless already provided in section 1.5)." + ], + "3.2 g.": [ + "Descriptor values", + "Where appropriate, report the values (experimental or calculated data) for numerical descriptors and indicate which values were used for making the prediction." + ], + "3.3 General": [ + "Applicability domain", + "(OECD principle 3)" + ], + "3.3 a.": [ + "Domains", + "Discuss whether the query chemical falls in the applicability domain of the model as defined in the corresponding QMRF (section 5 of QMRF, Defining the applicability domain - OECD Principle 3). If additional software/methods were used to assess the applicability domain then they should also be documented in this section. Include a discussion about: i. descriptor domain ii. structural fragment domain (e.g., discuss whether the chemical contains fragments that are not represented in the model training set) iii. mechanism domain (discuss whether the chemical is known or considered to act according to the mechanism of action associated with the used model) iv. metabolic domain, if relevant" + ], + "3.3 b.": [ + "Structural analogues", + "List the structural analogues that are present in the training or test sets, or accessible from other sources (in this case you should explain how the structural analogue was retrieved1) and why they are considered analogues). For each analogue, report the CAS number, the structural formula, the SMILES code, and the source (e.g., training set, test set or other source). For an expert system (like Derek for Windows or TOPKAT), the example compounds or structurally related analogues with their experimental data should be provided here." + ], + "3.3 c.": [ + "Considerations on structural analogues", + "Discuss how predicted and experimental data for analogues support the prediction of the chemical under consideration. " + ], + "3.4": [ + "The uncertainty of the prediction (OECD principle 4)", + "If possible, comment on the uncertainty of the prediction for this chemical, taking into account relevant information (e.g. variability of the experimental results). " + ], + "3.5": [ + "The chemical and biological mechanisms according to the model underpinning the predicted result (OECD principle 5)", + "Discuss the mechanistic interpretation of the model prediction for this specific chemical. For an expert system based on structural alerts (e.g. Derek for Windows, OncologicTM) the rationale for the structural alert fired should be provided." + ] + } + }, + "4. Adequacy (Optional)": { + "colNames": [ + "Title", + "Value" + ], + "values": { + "General": [ + "Instructions", + "The information provided in this section might be useful, depending on the reporting needs and formats of the regulatory framework of interest. This information aims to facilitate considerations about the adequacy of the (Q)SAR prediction (result) estimate. A (Q)SAR prediction may or may not be considered adequate ('fit-for-purpose'), depending on whether the prediction is sufficiently reliable and relevant in relation to the particular regulatory purpose. The adequacy of the prediction also depends on the availability of other information, and is determined in a weight-of-evidence assessment." + ], + "4.1": [ + "Regulatory purpose", + "Explain the regulatory purpose for which the prediction described in Section 3 is being used." + ], + "4.2": [ + "Approach for regulatory interpretation of the model result", + "Describe how the predicted result is going to be interpreted in light of the specific regulatory purpose (e.g. by applying an algorithm or regulatory criteria). This may involve the need to convert the units of the dependent variable (e.g. from log molar units to mg/l). It may also involve the application of another algorithm, an assessment factor, or regulatory criteria, and the use or consideration of additional information in a weight-of-evidence assessment. " + ], + "4.3": [ + "Outcome", + "Report the interpretation of the model result in relation to the defined regulatory purpose." + ], + "4.4": [ + "Conclusion", + "Provide an assessment of whether the final result is considered adequate for a regulatory conclusion, or whether additional information is required (and, if so, what this additional information should be)." + ] + } + } + }, + "figures": { + }, + "_id": "" +}
\ No newline at end of file |