Mathias

The event file looks good from a first glance. Maybe share your data file so I can try to reproduce the error..

Hi, not sure why this happens. Have you tried without the filter? Downsampling should already filter a lot. Also, do you have enough smapling rate after downsampling? Should be at least 20-30Hz, minimum 10 , I guess.

Hi Nadja you can consider editing the batchmode script yourself by adding these lines towards the end together with handing over the filename as variable where this should be saved so it does not overwrite.

Mean or sum are the same as long the event-window is of the same size for all conditions/particiapnts. In doubt, I recommend to take mean.

Yes, phasic data comes in muS, no further transformation applied. I had a quick look t the file, which looks good to me. Responses are rather small but can be realistic as there are substantial individual differences in the amplitude of EDA responses. Not sure why you want to use the max of phasic data rather than its mean (SCR) or sum (ISCR) but there sure are different approaches.

This could be done with the script variable_era.m, which you find in the root directory of Ledalab, which allows you to specify variable durations of your events (see help in the script). So, you need to hand over the resulting durations (i.e. compute the time 10 sec after event-onset to start of next event - this cannot be done automatically) and then can specify the response window as [10, 4] which would result in a response window starting 10 sec after event onset, and end 4 sec after event-offset...

Looks god so far, but you can a plot the slightly smoothed leda2.analysis.driver, which is depicted in the bottom of the GUI

Yes, probably. To separate events in the analysis it is helpful to give them different ids, but you can also group them post-hoc in the analysis I guess