HI Jenna,
In Project Implicit's current server, the names of the tasks in the study are saved in the "sessionTasks.txt" file. In that file, the name of each task is saved in the task_id column. The order is saved in task_number. The column task_creation_date is the time that the task was requested by the participant, so it can be used to measure how much time the participant spent in each task.
If a manipulation in a study used different task names for each condition, then one can learn the condition of each participant from the task names. Most researchers use different tasks for different conditions, so usually, that will be the place to look for the conditions.
However, sometimes a study condition is assigned by other means. For example, one can use code in the manager file, to randomly choose stimuli or even conditions. For example this code:
var demandCond = API.shuffle(["assimilative", "contrast", "both", "none"])[0];
That code uses the API's shuffle function to shuffle the order of the array and then read only the first cell of that array into the variable demandCond. Later, other code will use demandCond for the manipulation.
In this case, the condition is not saved unless you save it. For that, the function API.save is the current best method to save a variable. For example, with the following code, I saved a bunch of conditions for each participant, in the manager file:
API.save({
commit:commit,
demandCond:demandCond,
cspos1:cspos1,
cspos2:cspos2,
csneg1:csneg1,
csneg2:csneg2,
csneu:csneu
});
One general note: always analyze the data saved by your study before running the study. That is a part of the study testing before deploying it. Not doing so does not only waste your time, it also wastes the participants' contribution of time and effort.
I hope that helps,
Yoav