Limit same-key responses


Author
Message
agt
agt
Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)
Group: Forum Members
Posts: 42, Visits: 84
Hi there, may I find out if it is possible to limit same-key correct responses for IAT in combined tasks to less than four consecutive times? 
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 103K
atgoh - 7/8/2024
Hi there, may I find out if it is possible to limit same-key correct responses for IAT in combined tasks to less than four consecutive times? 

The short answer is no, there is no easy or straightforward way to do this.

The long answer is anything is possible if you're willing to make deep and major changes to the code.
Edited 3 Months Ago by Dave
agt
agt
Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)
Group: Forum Members
Posts: 42, Visits: 84
Hi Dave. I would like to make the change. May I find out how to do this?
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 103K
atgoh - 7/8/2024
Hi Dave. I would like to make the change. May I find out how to do this?

Look at the combined blocks as they exist now and understand how they work. That's step one.

Note down the <trial> elements that have the same correct response key in each combined block.

Note down how many trials there are of each type.

Note, too, that combined blocks always alternate between attribute and target trials.

Your easiest option is to simply spell out a fixed trial sequence that satisfiies your added constraint.

Otherwise you need to come up with an algorithm that produces random trial sequences that satisfy all the properties above and implement it. This is not trivial.

agt
agt
Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)
Group: Forum Members
Posts: 42, Visits: 84
Dave - 7/8/2024
atgoh - 7/8/2024
Hi Dave. I would like to make the change. May I find out how to do this?

Look at the combined blocks as they exist now and understand how they work. That's step one.

Note down the <trial> elements that have the same correct response key in each combined block.

Note down how many trials there are of each type.

Note, too, that combined blocks always alternate between attribute and target trials.

Your easiest option is to simply spell out a fixed trial sequence that satisfiies your added constraint.

Otherwise you need to come up with an algorithm that produces random trial sequences that satisfy all the properties above and implement it. This is not trivial.

Thanks Dave. I have noted on the number of trials for each combined blocks. It would be ideal to come up with a script to produce random trial sequence that limit not more than 4 times the same response key in each combined task. 
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 103K
atgoh - 7/9/2024
Dave - 7/8/2024
atgoh - 7/8/2024
Hi Dave. I would like to make the change. May I find out how to do this?

Look at the combined blocks as they exist now and understand how they work. That's step one.

Note down the <trial> elements that have the same correct response key in each combined block.

Note down how many trials there are of each type.

Note, too, that combined blocks always alternate between attribute and target trials.

Your easiest option is to simply spell out a fixed trial sequence that satisfiies your added constraint.

Otherwise you need to come up with an algorithm that produces random trial sequences that satisfy all the properties above and implement it. This is not trivial.

Thanks Dave. I have noted on the number of trials for each combined blocks. It would be ideal to come up with a script to produce random trial sequence that limit not more than 4 times the same response key in each combined task. 

That is what you should work on then. What you have on your hands there is a constraint satisfaction problem (cf. https://forums.millisecond.com/Topic6419.aspx ), so be prepared to spend some time on this.

agt
agt
Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)
Group: Forum Members
Posts: 42, Visits: 84
Dave - 7/9/2024
atgoh - 7/9/2024
Dave - 7/8/2024
atgoh - 7/8/2024
Hi Dave. I would like to make the change. May I find out how to do this?

Look at the combined blocks as they exist now and understand how they work. That's step one.

Note down the <trial> elements that have the same correct response key in each combined block.

Note down how many trials there are of each type.

Note, too, that combined blocks always alternate between attribute and target trials.

Your easiest option is to simply spell out a fixed trial sequence that satisfiies your added constraint.

Otherwise you need to come up with an algorithm that produces random trial sequences that satisfy all the properties above and implement it. This is not trivial.

Thanks Dave. I have noted on the number of trials for each combined blocks. It would be ideal to come up with a script to produce random trial sequence that limit not more than 4 times the same response key in each combined task. 

That is what you should work on then. What you have on your hands there is a constraint satisfaction problem (cf. https://forums.millisecond.com/Topic6419.aspx ), so be prepared to spend some time on this.

Thanks for the information. Is there a starting script or section where I can work on? I have no background on computer science/scripts so it will be great to get some advice from you.
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 103K
atgoh - 7/9/2024
Dave - 7/9/2024
atgoh - 7/9/2024
Dave - 7/8/2024
atgoh - 7/8/2024
Hi Dave. I would like to make the change. May I find out how to do this?

Look at the combined blocks as they exist now and understand how they work. That's step one.

Note down the <trial> elements that have the same correct response key in each combined block.

Note down how many trials there are of each type.

Note, too, that combined blocks always alternate between attribute and target trials.

Your easiest option is to simply spell out a fixed trial sequence that satisfiies your added constraint.

Otherwise you need to come up with an algorithm that produces random trial sequences that satisfy all the properties above and implement it. This is not trivial.

Thanks Dave. I have noted on the number of trials for each combined blocks. It would be ideal to come up with a script to produce random trial sequence that limit not more than 4 times the same response key in each combined task. 

That is what you should work on then. What you have on your hands there is a constraint satisfaction problem (cf. https://forums.millisecond.com/Topic6419.aspx ), so be prepared to spend some time on this.

Thanks for the information. Is there a starting script or section where I can work on? I have no background on computer science/scripts so it will be great to get some advice from you.

You should not start with any code. You should start with doing the math and spelling out an algorithm -- i.e. a series of precisely defined steps that will yield the desired result -- that produces trial sequences in the way you want them to. You don't need a script for that, you need a piece of paper. Once you have your algorithm worked out, you can start thinking about implementing it. It's only then that you need to concern yourself with any code.

agt
agt
Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)Associate Member (96 reputation)
Group: Forum Members
Posts: 42, Visits: 84
Dave - 7/9/2024
atgoh - 7/9/2024
Dave - 7/9/2024
atgoh - 7/9/2024
Dave - 7/8/2024
atgoh - 7/8/2024
Hi Dave. I would like to make the change. May I find out how to do this?

Look at the combined blocks as they exist now and understand how they work. That's step one.

Note down the <trial> elements that have the same correct response key in each combined block.

Note down how many trials there are of each type.

Note, too, that combined blocks always alternate between attribute and target trials.

Your easiest option is to simply spell out a fixed trial sequence that satisfiies your added constraint.

Otherwise you need to come up with an algorithm that produces random trial sequences that satisfy all the properties above and implement it. This is not trivial.

Thanks Dave. I have noted on the number of trials for each combined blocks. It would be ideal to come up with a script to produce random trial sequence that limit not more than 4 times the same response key in each combined task. 

That is what you should work on then. What you have on your hands there is a constraint satisfaction problem (cf. https://forums.millisecond.com/Topic6419.aspx ), so be prepared to spend some time on this.

Thanks for the information. Is there a starting script or section where I can work on? I have no background on computer science/scripts so it will be great to get some advice from you.

You should not start with any code. You should start with doing the math and spelling out an algorithm -- i.e. a series of precisely defined steps that will yield the desired result -- that produces trial sequences in the way you want them to. You don't need a script for that, you need a piece of paper. Once you have your algorithm worked out, you can start thinking about implementing it. It's only then that you need to concern yourself with any code.

There’s a total of 7 blocks, of which 4 blocks are combined tasks consisting of 32 and 64 trials. Within each ofthe 4 blocks, there should be not more than 4 consecutive same key responses.
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 103K
atgoh - 7/9/2024
Dave - 7/9/2024
atgoh - 7/9/2024
Dave - 7/9/2024
atgoh - 7/9/2024
Dave - 7/8/2024
atgoh - 7/8/2024
Hi Dave. I would like to make the change. May I find out how to do this?

Look at the combined blocks as they exist now and understand how they work. That's step one.

Note down the <trial> elements that have the same correct response key in each combined block.

Note down how many trials there are of each type.

Note, too, that combined blocks always alternate between attribute and target trials.

Your easiest option is to simply spell out a fixed trial sequence that satisfiies your added constraint.

Otherwise you need to come up with an algorithm that produces random trial sequences that satisfy all the properties above and implement it. This is not trivial.

Thanks Dave. I have noted on the number of trials for each combined blocks. It would be ideal to come up with a script to produce random trial sequence that limit not more than 4 times the same response key in each combined task. 

That is what you should work on then. What you have on your hands there is a constraint satisfaction problem (cf. https://forums.millisecond.com/Topic6419.aspx ), so be prepared to spend some time on this.

Thanks for the information. Is there a starting script or section where I can work on? I have no background on computer science/scripts so it will be great to get some advice from you.

You should not start with any code. You should start with doing the math and spelling out an algorithm -- i.e. a series of precisely defined steps that will yield the desired result -- that produces trial sequences in the way you want them to. You don't need a script for that, you need a piece of paper. Once you have your algorithm worked out, you can start thinking about implementing it. It's only then that you need to concern yourself with any code.

There’s a total of 7 blocks, of which 4 blocks are combined tasks consisting of 32 and 64 trials. Within each ofthe 4 blocks, there should be not more than 4 consecutive same key responses.

Yes. That is not an algorithm. That is a statement of the desired end state. You need to work out the steps that get you to that end state. If you can't do that, my advice is go for the easy option and use a fixed trial sequence, which you can construct by hand.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Explore
Messages
Mentions
Search