By AndrewJSchoen - 6/15/2016
We have a couple different studies in the works in which we are trying to implement Inquisit. I am tasked with recreating our old tasks in your framework. Based on the benefits of modularization with batches, and the fact that many of our studies use identical tasks, but not identical collections of those tasks, I thought I would try to create study-specific batch scripts separate from the tasks. Ideally, I would like to create a directory on our computer with a repository of those tasks, and just point the batch script to the task files as needed. Finally I would like to place the data in a study-specific location, as opposed to a communal dumping ground.
I had hoped that by defining a value in the batch (output_prefix), that variable file would be available within the scope of the individual file elements, but it looks like it is not the case. Do you have any suggestions on how to get the desired behavior, while maintaining as much modularity as possible (and reducing redundancy)?