___________________________________________________________________________________________________________________
*TIMELINE FOLLOWBACK TEMPLATE (last 30 days) - Example: Cannabis*
___________________________________________________________________________________________________________________
Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 05-20-2013
last updated: 03-02-2022 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC
Script Copyright © 03-02-2022 Millisecond Software
___________________________________________________________________________________________________________________
BACKGROUND INFO
___________________________________________________________________________________________________________________
This script implements a Cannabis Timeline Follow-Back calendar.
For more information about Timeline Follow-Backs at:
http://www.nova.edu/gsc/online_files.html#time_followback
___________________________________________________________________________________________________________________
TASK DESCRIPTION
___________________________________________________________________________________________________________________
Participants are asked to fill out a calendar with their cannabis use for the last 30 days,
starting with yesterday.
___________________________________________________________________________________________________________________
DURATION
___________________________________________________________________________________________________________________
the default set-up of the script takes appr. 5 minutes to complete
___________________________________________________________________________________________________________________
DATA FILE INFORMATION
___________________________________________________________________________________________________________________
The default data stored are:
Data file: 'timelinefollowback*.iqdat' (a separate file for each participant)
inquisit.version: Inquisit version run
computer.platform: the platform the script was run on (win/mac/ios/android)
startdate: date script was run
starttime: time script was started
subjectid: assigned subject id number
groupid: assigned group id number
sessionid: assigned session id number
elapsedtime: time it took to run script (in ms); measured from onset to offset of script
completed: 0 = script was not completed (prematurely aborted);
1 = script was completed (all conditions run)
yesterday_date: stores yesterday's date as a string (e.g. 5/20/2013)
yesterday_weekday: stores yesterday's weekday as an integer (e.g. 1 for Monday, ..., 7 for Sunday)
leapyear: stores whether the year is a leap year
totalamount: sums up all the quantities that participants reported over the 30 day span; regardless of method
mean_amount: mean daily quantity consumed (over 30 days); regardless of method
count_nouse: sums up how often a participant has checked the nouse checkbox
+all individual data points
date11: individual dates of each of the calendar boxes (e.g. 11 = 1st row, 1st column....61 = 6th row, 1st column)
...
date61 = ""
___________________________________________________________________________________________________________________
SET-UP
___________________________________________________________________________________________________________________
1. Screen that asks for information input about start day ("yesterday") -> year, leap year, month, day, weekday
2. Screen that displays instructions (edit instructions under EDITABLE CODE -> Editable Instructions)
3. Calendar Display: a calendar display with the last 30 days filled in with the appropriate days
(all 30 days are displayed on one page)
=> each days asks for a) quantity b) method or c) No use checkbox
=> a screenshot is taken of the filled in calendar (default; works on Inquisit Lab only)
=> computer totals the quantities and calculates mean quantity for the last 30 days
=> computer totals the number of times participants select "no use"
___________________________________________________________________________________________________________________
EDITABLE CODE
___________________________________________________________________________________________________________________
check below for (relatively) easily editable parameters, stimuli, instructions etc.
Keep in mind that you can use this script as a template and therefore always "mess" with the entire code
to further customize your experiment.
