Are you using WaveSurfer for closed-loop experiments? (PLEASE RESPOND!)

[Adam Taylor]

Folks,

[Please, I beg of you, respond to this email, even if you have no idea what I'm babbling about.  (If you have no idea what I'm babbling about, it probably means you're not using the closed-loop features of WaveSurfer, which is very useful information.]

I'd like to do an informal survey of how many people out there are using WaveSurfer for closed-loop experiments.  By "closed-loop", I mean experiments where you write a user class that monitors a set of inputs continuously, and then sets one or more outputs during the ongoing trace, based on the recent history of the data.  Such experiments will almost always use the user class method "samplesAcquired()" to monitor the inputs and to set the outputs.  A simple example might be to monitor the membrane potential of a neuron, and turn on a TTL whenever that potential is above a threshold (and turn it off when the potential is below the threshold).  WaveSurfer currently supports doing this kind of thing with latencies < 10 ms.

Again, please, if you get this email, let me know whether you are doing these kind of experiments.  WaveSurfer's closed-loop capabilities are very powerful, but my impression is that they are not actually used by very many users.  Dropping this feature would allow for considerable simplification of the code base, and would therefore reduce maintenance costs and the costs of future improvements.  So, I'm thinking about it, but first I'm trying to figure out if I'll be hunted down and killed by my (former) users if I do this.

Thank you all,

Adam

[David Nauen]

hi adam,

we plan to be using this capability but are not using now

thank you

---

From: waves...@googlegroups.com <waves...@googlegroups.com> on behalf of Adam Taylor <adamlyl...@gmail.com>
Sent: Tuesday, March 26, 2019 3:26:19 PM
To: WaveSurfer
Subject: Are you using WaveSurfer for closed-loop experiments? (PLEASE RESPOND!)

 

--
You received this message because you are subscribed to the Google Groups "WaveSurfer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wavesurfer+...@googlegroups.com.
To post to this group, send email to waves...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wavesurfer/71006720-5a73-4aeb-964b-f40ebed857b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mauro Pulin]

Hi,

we are not using this feature at the moment (but we might in the future).

What would now be more useful for us is the possibility to display cell parameters (input resistance, capacitance etc) like the old ephus did :)

Also, we haven't found a way to set a delay between each acquisition sweep (did we miss it?)

Thanks,

Mauro

[Taylor, Adam]

Thank you for your response (and thanks to everyone for their responses)!

The cell parameters should be avaiable soon.

If you use a counter trigger (under Protocol > Triggering...) You can
have an arbitrary time gap between sweeps.

Adam

[Alberto Perez]

Hi Adam, 

we are not using closed-loop experiments at the moment.

Cell parameters would have a higher priority for me.

Best,

Alberto

[Tobias Rose]

Hi Adam,

no closed-loop here. 

cheers,T