Multiple lick inputs in go/no go

[ransona]

Not sure how you were thinking of implementing the logic of the go/no go task but I notice the Harp board has multiple lick inputs and so it would be good in terms of flexibility to be able to use them. It feels to me like we want to have several independent lick responsive behavioural objects defined by:

• Lick input (1, 2 or 3)
• Trigger threshold (i.e. number of licks)
• Phase when active (pre trial, specific time period [e.g. 1-2 secs] etc)
• Consequence (i.e. delay trial onset, give immediate reward, give airpuff, give white noise sound)

So for each trial you sort of activate the number of these contingencies that you need.

[glopesdev]

We can discuss the logic better in the meeting, but one constraint is that although each Harp board does have 3 available ports, the encoder uses one of them. In this case, unless we use more than one board per box, there will be only 2 lick ports rather than 3.