Visual search tests

Post Reply New Topic

These visual search tests are fun: LINK

Is there difference between feature and conjunction search for you?

Does target pop out whenever it is present?

Interesting test. The targeted object jumped out at me almost every time. I have no idea what those numbers mean so I can't answer you second question.

I did the one with the lines oriented a certain direction. The target was immediately visible for me.

Conjugation was how many features you had to sort through visually to identify the target among directors. There was for me the potential to have lines of different widths, and in different directions. For most people they sort those two attributes separately, where I see the target as a single unit.

They pop out. Seeing the features in conjunction makes them pop out easier.

I can't do it. The test does not recongize the "/"key.

it is the "a" key "h" key and the "'" (apostrophe) key.

I'm slower with conjunction - target absent, particularly on the 32 object trial, and a little bit slower with conjunction - target present but only for the 16 - 32 object trials.

What is the "feature" search and what is the "conjunction" search? What's the difference?



Yes, most of the time.

Feature search is look for blue triangle in red triangles or blue triangle in blue squares, search for only color or shape.

Conjunction is search for both color and shape, like look for blue triange in red triangles and blue squares.

In nts, feature search speed stays same for increasing numbers of items (flat line), but conjunction search speed increases as number of items increases.

If target pops out right away, then you should get approximately flat line.

In target absent condition, you should get nearly flat line also, if target pops out, since no pop-out right away means it's not there.

In studies, autistic people got lower slopes than nts in present and absent conditions.

Thank you for the explanation.

That boggles my mind. How can you get faster when you're processing more information?



I start looking for it when I don't see it right away -- thinking I missed it. LIke double-checking work even when you're pretty sure you have the right answer. Still, it seems my slower-ness on the conjunction - target present at higher numbers means it doesn't pop out at me in the way you mean.

Last edited by animalcrackers on 06 Aug 2013, 5:30 pm, edited 1 time in total.

I'm worse at conjunction-target absent at 32. Otherwise I'm pretty reliably the same.

Oh, oops, sorry about error, I meant that conjunction search speed decreases as number of items increases.

That makes more sense.

So, what kind of actual speeds did you average? On the graph it said I was getting around 400-800ms depending on which bit it was, averaging about 500ms I'd say.

I just flicked my eyes across the screen and the target jumped out every time. It was fast enough to have a sort of rhythm going, with almost no time between the picture appearing and me going with it.

500 ms is verry merry berry normal time for eberryone.

There is approx 400 ms for seeing image and pressing buttons, and rest is search time.

Baseline speeds vary, but adults start around 500 ms in literature.

The important data is not reaction time, but trend in reaction time as number of items increases.

Flat line or low slope < 5 ms/item is efficient search, rising slope > 10 ms/item is inefficient search, I guess on this easy search task.

I am stable around 500ms for all of them except for conjunction at 32, which shoots up to around 900ms for present, and 1200 for absent.

Do you mean, that any of these keys can be used instead of "/" key? The "Z" key works.