-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2019-11-20 tc010 M1SD test case variant with All FLGEXAUC set to 1, i.e. exclude all data points from AUC computations crashes computation engine #35
Comments
UpdateI can replicate this error for all test cases involving a partial AUC (tc010, tc011, tc015 & tc071). It does not occur for tc012, tc013, tc014 or tc016. When partial AUCs are added to the mct of tc012, tc013, tc014 (using historic commit 066fa5d) or tc016 this error can be replicated. When setting FLGEXAUC to 1 in tc013 without partial AUCs added a unique error is experienced outlined in issue #41 . |
UpdateIt appears that this issue is strongly related to #6. tc013 can be run without error with the following changes from the base testcase:
The partial AUCs listed are interpolated points to extrapolated points. By turning off extrapolation the error no longer occurs. Therefore, it appears that with exclusion of all data points from being used to determine AUC, all partial AUC points are considered extrapolated points. This makes this the same issue, partial AUCs for extrapolated to extrapolated points causing a "subscript out of bounds" error. |
This issue was addressed in 02b2470, please let me know if it still occurs. |
UpdateThis no longer occurs for 02b2470. |
This WAS working appropriately in current master branch, i.e. expectation is that all parameters other than AUCs are computed as expected. Requested AUCs are set to NA.
The text was updated successfully, but these errors were encountered: