Changes from 2.9
- Avoid failing when no notes are provided
- Adjusted for R version 4.3 and changes in bmd codes
Changes from 2.8
A compliance check of the reporting template is conducted initially. If your table has dfferent columns names (case sensitive!) and or columns are missing, a list of errors is provided.
Changes from 2.7
Fixed a but when no p-values for trend test could be generated
(in case of all effect values = 0)
Changes from v2.6:
Adopted workflow so that it can handle data and tables with no effects in any concentration (on the expense that it is a bit slower than previos version).
This workflow uses data from an input file compliant with a dedicated PrecisionTox template
with the same version number and will automatically generate concentration-response modelling data and a reporting file with raw and modelled data.
# PT_BMD_summary file naming
the format of the file name is: "PT_BMD_summary_(species)_(four-digit-number)"
for each of the six organism used in PrecisionTox, the reporting template file is numbered from 0001 onwards, that is, 0001-9999. The number represents a consecutive number that reflects a batch of analysis and does not relate the the PrecisionTox chemical ID.
examples of the PT_BMD_summary file names: "PT_BMD_summary_hsa_0001.xls", "PT_BMD_summary_dme_0011.xls", "PT_BMD_summary_dma_0250.xls"
All data must be in a form that values increase with higher concentration (in case the compound is provoking an effect). Hence, you may have to transform data in advance (coding would be very demanding to allow increasing and decreasing data types).
Data that can be modelled by a Hill (log-logistic) equation, are identified by comparison of the AIC to a linear model with slope 0.
Furthermore, the percent variance reduction is calculated as an intuitive indicator whether the curve fitting is approximating the data.
Note: It is important that you upload a table with the same structure as in the template. It is possible to only upload one experiment or one replicate.
To check for compliance of workflow and template refer to the appropriate version number at the end of the file name and workflow. E.g. template files and workflows ending with v2.3 are compliant which each other.
Template file location on sharepoint:
Documents\General\Data Management Plan Working Group\Metadata_Templates
stefan.scholz@ufz.de
To use this workflow in KNIME, download it from the below URL and open it in KNIME:
Download WorkflowDeploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!