Need to handle the column that denotes the trial condition within the task.
ACE Nexus now calls this column trialCondition (trial_condition after converting to pothole case) for all modules. We need to make sure we correctly map the old ancestor columns from each ACE Explorer module to the new trial_condition column, so that proc_by_module() gets the right column info.
Where possible/sensible, I will have aceR rename the ACE Explorer columns in question to trial_condition to harmonize with ACE Nexus. It has to be trial_condition because condition IS a column in ACE Explorer, which frustratingly only contains trial_condition information for a subset of tasks (see below).
For my own tracking, here is a list of where trial_condition information lives for each of the modules' Explorer iterations.
[ ] ADP
[ ] ACE Explorer: aceR generates it from combining expression (the non-neutral one) and cue_expression
[ ] Span tasks
[ ] ACE Explorer: object_count
[ ] Boxed
[ ] ACE Explorer: condition
[ ] BRT
[ ] ACE Explorer: condition
[ ] Color selection (called Color picking in Nexus)
[ ] ACE Explorer: condition is NA, no within-task conditions to subset performance by
[ ] ACE Nexus: trial_condition should also be rendered as NA
[ ] For both of these, condition should be discarded/disregarded
[ ] Filter
[ ] ACE Explorer: condition
[ ] Flanker
[ ] ACE Explorer: trial_type
[ ] Ishihara color blindness
[ ] ACE Explorer: condition is NA, performance was previously calculated only by using rg_color_deficiency or trial_correct, which carries the information of correct_button
[ ] ACE Nexus: trial_condition now has some trial information but I need to check whether it should be used for analysis at all
[ ] SAAT (impulsive, sustained, combined)
[ ] ACE Explorer: condition (Both the old combined impulsive+sustained files, and the split files. The split files simply have one value through the whole column)
Need to handle the column that denotes the trial condition within the task.
ACE Nexus now calls this column
trialCondition(trial_conditionafter converting to pothole case) for all modules. We need to make sure we correctly map the old ancestor columns from each ACE Explorer module to the newtrial_conditioncolumn, so thatproc_by_module()gets the right column info.Where possible/sensible, I will have aceR rename the ACE Explorer columns in question to
trial_conditionto harmonize with ACE Nexus. It has to betrial_conditionbecauseconditionIS a column in ACE Explorer, which frustratingly only containstrial_conditioninformation for a subset of tasks (see below).For my own tracking, here is a list of where
trial_conditioninformation lives for each of the modules' Explorer iterations.expression(the non-neutral one) andcue_expressionobject_countconditionconditionconditionis NA, no within-task conditions to subset performance bytrial_conditionshould also be rendered as NAconditiontrial_typeconditionis NA, performance was previously calculated only by usingrg_color_deficiencyortrial_correct, which carries the information ofcorrect_buttontrial_conditionnow has some trial information but I need to check whether it should be used for analysis at allcondition(Both the old combined impulsive+sustained files, and the split files. The split files simply have one value through the whole column)trial_typetrial_typetaskswitch_statecondition