-
Notifications
You must be signed in to change notification settings - Fork 38
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
remove calc_error_bio in cfeature #324
Conversation
Yes, it appears that the value 250 has been used as an error code in different parts of the code, as suggested by: Line 236 in eb8c8a5
|
Oh I see. So 250.0 is the error code. Thanks |
In our use cases, we usually consider a score of 250 to be the worst possible. When something goes wrong with a feature, or if a feature has a score higher than 250, we usually just return 250. |
Thanks, I didn't know it. This function however is not used anywhere in eFEL. As far as I can see it is computing some cumulative error for a vector. |
Yes indeed. I suppose now this score calculation is done by BluePyEfe, and should not be done by efel. |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #324 +/- ##
=======================================
Coverage 57.39% 57.39%
=======================================
Files 29 29
Lines 7820 7820
Branches 3235 3235
=======================================
Hits 4488 4488
Misses 847 847
Partials 2485 2485 ☔ View full report in Codecov by Sentry. |
This code must have been used in debugging a long time ago. Otherwise
return 250.;
can't be really the general value that would fit all usages.