Comments (10)
@nqthqn you're right, we can drop the probeIndex
.
from craconweb.
uint64 id DB generated unique id for trial
uint64 gsessionId id to the game session (contains start and end times)
uint64 fixation onset time of fixation cross
uint64 selection onset time of users selection w/ keyboard or mouse
uint64 instruct onset time of instructions block
uint64 pictures onset time of pictures
uint64 redcross onset time of cross (red cross indicating incorrect response)
uint64 probe onset time of probe (dot)
uint64 border onset time of border
uint64 timeout onset time of timeout
uint32 width width of matrix for visual search
uint32 height height of matrix for visual search
bool blue was the border blue?
bool dash was the border dash?
uint32 probeIndex
uint32 targetIndex
uint32 selectedIndex
uint32 startIndex
uint64[] images ["1","2","3","4"] -- array of image ids
# gsession
uint64 seed -- add seed
from craconweb.
I think @daved would want this to be less "dynamic" and more static/relational. example: maybe event_id
(FK to table of events) instead of eventName
(magic slug string). But I think it's fine.
We have a time crunch and other features — game data download, badges, participant usage summaries — depend on the shape of this data. If we could come to a decision by Monday that would be great.
from craconweb.
@abadi199 could you explain these four fields? (Aren't probeIndex
& actualIndex
redundant?)
probeIndex:
type: integer
desired:
type: boolean
expectedIndex:
type: integer
actualIndex:
type: integer
from craconweb.
message GcycleResp {
uint64 id = 1;
uint64 gsessionId = 2;
uint64 report = 3;
uint64 fixation = 4;
uint64 selection = 5;
uint64 instruct = 6;
uint64 jitter = 7;
uint64 pictures = 8;
uint64 filler = 9;
uint64 cross = 10;
uint64 picnobord = 11;
uint64 picbord = 12;
uint32 xCoords = 13;
uint32 yCoords = 14;
bool blue = 15;
uint64 reasonId = 16;
}
from craconweb.
uint64
s are time. When did pictures
occur in this trial?
gcycle = trial
from craconweb.
to add:
bool dashed
int correctIndex
int selectedIndex
from craconweb.
my comments
uint64 id DB generated unique id for trial
uint64 gsessionId id to the game session (contains start and end times)
uint64 report onset time of reporting
uint64 fixation onset time of fixation cross
uint64 selection onset time of users selection w/ keyboard or mouse
uint64 instruct onset time of instructions block
uint64 jitter onset time of jitter
uint64 pictures onset time of pictures
uint64 filler onset time of filler (no need?)
uint64 cross onset time of cross (red cross indicating incorrect response)
uint64 picnobord ??
uint64 picbord ??
uint32 xCoords width of matrix for visual search
uint32 yCoords height of matrix for visual search
bool blue was the border blue?
uint64 reasonId what was the associated trial action (the reason the trial ended)
possible reasons:
- correct
- incorrect
- timeout
from craconweb.
Notes
For the new games that you design, we should add the staircase to the data field.
Instead of picture number, we should do food category in all the new games.
Staircasing (average
Required
RT relative to onset of events (single key press or single mouse click)
Onset all events (trials, tones, frame)
Whats on screen (images in matrix) and where (layout of matrix)
Whats selected (an image in the matrix)
Context
subjectID, condition, session#, date, valuation
Derived
Average response time per session (to see learning over time)
Stop-signal
Variables:
- Trial type (food response training: healthy, unhealthy; control: birds, flowers)
- Picture name
- Go or no-go picture
- picname
Data:
- response time
- correct response or not
- average response time (per block)
- info: subjectID, condition (food response training or control), session, date
- pic onset time
- frame onset time
Go/no-go
Variables:
- Trial type (food response training: healthy, unhealthy, water; control: birds, flowers, mammals)
- Pic number
- Go or no-go picture
- Left or right
- Picname
Data:
- Response time
- Correct response or not
- Average response time (per block)
- Info: subjectID, condition, session, date
Respond-signal:
Variables:
- Trial type (food response training: healthy, unhealthy, water; control: birds, flowers, mammals)
- Picture number
- Go or no-go picture
- Delay of tone
Data:
- Response time
- Correct response or not
- Average response time (per block)
- Picture name
- Info: subjectID, condition, session#, date
Dot-probe:
Variables:
- Probe on left or right side
- Pic number: healthy food (or birds in control group)
- Pic number: unhealthy food (or flowers in control group)
Data:
- Response time
- Correct response or not
- Average response time ( per block)
- Pic name: healthy food (or birds in control group)
- Pic name: unhealthy food (or flowers in control group)
- Info: subjectID, condition, session#, date
Visual search:
Variables:
- Picture number: healthy food (or birds in control group)
- Location of healthy food
- Picture number: unhealthy food (or flowers in control group)
Data:
- Response time
- Correct response or not
- Average response time (per block)
- Info: subjectID, condition, session#, date
from craconweb.
Thanks everyone for the input on this!
from craconweb.
Related Issues (20)
- FMRI Stop Signal HOT 18
- add touch capability for dot probe, stop signal, go/no-go HOT 2
- add game play overview to user in admin
- send abadi filesrv static assets
- blocks HOT 2
- Add login text
- fMRI Stop Signal Changes HOT 2
- fix link
- fix for smaller screens HOT 1
- add 5 second rest, increase session to 10 minutes, post onset rest gcycle HOT 6
- mes changes HOT 5
- User messages "jitter" field HOT 7
- fMRI GUI improvement. HOT 3
- Please banish usage of "grey". This ain't no British colony. HOT 1
- probe index != target index HOT 3
- Gcycle "gray" field not being reported.
- Width is incorrectly reported by 2x1 games (dotprobe and gonogo).
- stopsignal gray border missing.
- Time logging accuracy improvement. HOT 2
- Limited vertical windows clip game area.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from craconweb.