I have a protocol with 45 subjects. Lots of different files and conditions (each sub has 5 sessions x 4 runs , 4 conditions, plus all sorts of variants and processing steps on the way, obviously).
In order to create some averages, I try using the search feature in the database, but it is extremely slow.
I first try to select only files that contain "WAvg" in name, and are of type "Source". It takes 80s to run, which makes fine-tuning a search pretty impractical...
I ran a profiler specifically around a search, and tracked down the longest time spent ( to
panel_protocols>ActiveSearch that is ran 280,000 times and takes 31s.
Do you see any way to improve this?
@filipa this if for your protocol