You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did a test run of the get_AUC function and compared results to the function I previously used for the 'hill' function (invitrodb_v3_5 data). The AUC's are dissimilar between methods but would need to do a full analysis with a set of curves to understand how variable the AUCs are.
For DTXSID6020226 in endpoint (aeid 2494) I found an AUC of 186.66 using the get_AUC function. I found an AUC of 109.31 using my previous function (integration based). These differences may not be surprising because different model parameters were used. I looked at a second chemical and observed a similar difference.
Goal: Analyze why we are getting different values with the get_AUC function from what Kelly previously estimated. (A) How frequently do we end up with dissimilar AUC estimates (B) Identify potential differences between Kelly's approach and ours and (C) Determine if there is a bug that needs to be fixed and/or path forward.
The text was updated successfully, but these errors were encountered:
Here is the script I wrote to test the get_AUC function and compare it to the AUC function I had previously used with invitrodb v3.5 data. The script is located in the Teams folder under files/Scripts "Testing_get_AUC_function_tcplfit2_05Oct2023_pass.R" or here.
Attaching a pdf of codes used to compare results of the 'get_AUC' function with results of previous function from Kelly. Shows how to get the same results by using log transformation. AUC-Compare Resuls.pdf
Goal: Analyze why we are getting different values with the get_AUC function from what Kelly previously estimated. (A) How frequently do we end up with dissimilar AUC estimates (B) Identify potential differences between Kelly's approach and ours and (C) Determine if there is a bug that needs to be fixed and/or path forward.
The text was updated successfully, but these errors were encountered: