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
results in ValueError: Cannot calculate temporal response, because stimulus/percept does not have a time component, which is clearly not true (/models/base.py, line 585)
The text was updated successfully, but these errors were encountered:
This is currently by design, but is something that we could consider changing (and that error certainly is not the most helpful).
Right now it doesn't completely make sense to use it with a temporal model, because the biphasic model is already accounting for lots of temporal information (pdur, freq) in its calculations, and its not clear how this should interact with another model that also uses those features.
This is similar to the issue with the Dynaphos model (it really isnt possible to completely separate out temporal and spatial components in either of these).
From the BiphasicAxonMapSpatial docstring: .. note:: Using this model in combination with a temporal model is not currently supported and will give unexpected results
Should we consider allowing mix and match behavior? This might allow for the desired qualitative effects (e.g. phosphenes that scale with stim params and fade), but doesn't really make sense looking at the theoretic motivation / assumptions behind each model.
Also wanted to add that enabling this behavior would not be hard. The bug arises because the BiphasicAxonMapModel is designed to output a singular brightest frame, which then does not work with the temporal model. A quick fix would be to just copy this frame at every point and then use the temporal model.
I have a stimulus made exclusively of well-behaved
BiphasicPulseTrain
objects and the following model:It works just fine. But switch out
AxonMapSpatial
forBiphasicAxonMapSpatial
:results in
ValueError: Cannot calculate temporal response, because stimulus/percept does not have a time component
, which is clearly not true (/models/base.py
, line 585)The text was updated successfully, but these errors were encountered: