-
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
New features for AHP after burst #131
Comments
I've implemented a first version of the feature you request in #132 The feature is called 'initburst_sahp' (there is also 'initburst_sahp_vb' for voltage_base, and 'initburst_sahp_ssse' for steady-state-stim-end). You can see the implementation here: I've made some initial changes to the eFEL to allow for features defined in pure python. For now all these features go in the file mentioned above. The getFeatureValues call stays the same, it works for both cpp features and python features. This feature could be a bit unstable because it's difficult to implement this for the general case. Let me know how it goes, or if you need something more. |
Thanks. I've also checked with those traces and the values are as expected. One issue I found in using Python-only features during optimisation is that getDistance function knows only about c++ features names. (https://github.com/BlueBrain/eFEL/blob/master/efel/api.py#L196) |
Good point, sorry forgot about that. Let me have a look at how I can solve that. |
Thanks. If it can help, I've quickly fixed it in the api.py, by adding this to distance():
And creating get_py_distance() function: `def get_py_distance(trace, featureName, mean, std, trace_check, error_dist):
However it may miss something (like what to do with trace_check and if feature calculation return error). |
Another problem I had using 'initburst_sahp' during optimization, is this error: I'm trying to see in I can output the trace and reproduce the error. |
I fixed your last issue here: |
Regarding the ValueError, I saved traces when the features calculation hits the condition here: https://github.com/BlueBrain/eFEL/blob/master/efel/pyfeatures/pyfeatures.py#L164 I'm attaching one here. |
This PR adds the python features to getDistance(): This pypi version includes that code: |
I've tried hard to implement the python getDistance function in a way so that it exactly replicates the values generated by the cpp version. Let me know if you see any discrepancies in bluepyopt etc. |
Also added @elisabettai 's trace in a test: |
* gh#130 use auto_threshold value in compute_spikecount * make Recording an abstract class * extract set_autothreshold as method
This feature should calculate the voltage (absolute value) at the points marked with "x".
Possible steps are:
I hope it's clear, feel free to add any comments.
Below the 3 traces used to produce the figure.
burst_1.txt
burst_2.txt
burst_3.txt
The text was updated successfully, but these errors were encountered: