Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with block number in the TaskSwitching protocol #2

Open
abidi-wq opened this issue Jan 22, 2022 · 4 comments
Open

Problem with block number in the TaskSwitching protocol #2

abidi-wq opened this issue Jan 22, 2022 · 4 comments

Comments

@abidi-wq
Copy link

Hello,
I successfully run the whole program, but there is only 2 blocks of 64 trials, however, in the paper of McCormick, they said that participants completed four blocks of 64 trials each.
How can I add the two missing blocks please?
Best regards,
Malek

@a-hurst
Copy link
Member

a-hurst commented Jan 23, 2022

Hi Malek,

Good catch! The number of blocks is specified by the experiment's params.py file in this section here:

#########################################
# Experiment Structure
#########################################
multi_session_project = False
trials_per_block = 64
blocks_per_experiment = 2
conditions = ['endo', 'exo']
table_defaults = {}

No idea why it was set to 2 for the GitHub version, I just double-checked our data files and participants did indeed run 4 blocks of 64 trials each, I must have set that locally on the testing computers and forgot to update it in my local development copy... at any rate, changing the blocks_per_experiment field from 2 to 4 in the above file should make it match the version run in the manuscript.

Cheers,

Austin

@abidi-wq
Copy link
Author

Hello, many thanks, it works. I have another question please; when I export data, in the signal type colomn, I found only "exo condition", whereas there must be both conditions (exo and endo).
what should i do to get both. I need it to compare the RT between conditions.

Thanks

@a-hurst
Copy link
Member

a-hurst commented Jan 23, 2022

Endo/exo is a between-subjects factor, so you need to specify the condition at launch for different participants. It's documented in the README:

To choose which condition to run, launch the experiment with the --condition or -c flag, followed by either exo or endo. For example, if you wanted to run the endogenous signal condition on a computer with a 19-inch monitor, you would run

klibs run 19 --condition endo

If no condition is manually specified, the experiment program defaults to running the exogenous signal condition.

Hope that helps!

@abidi-wq
Copy link
Author

abidi-wq commented Feb 7, 2022

Hello, Many thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants