Loops versus Forms
I'm setting up a handedness questionnaire and some other questionnaires (which need to be scored) and I'm having a bit of trouble understanding the loop information. Most of the examples are for experiments. I tried to set up my handedness questionnaire as a loop but my experiment seems to skip it when it runs and moves on to the next questionnaire (see CurrentCode.txt). I'm trying to figure out how to set the score so that if the selection is left - the score is 0, if the selection is both - the score is 1, and if the selection is right - the score is 2. I would like to output a final score that gives the percentage of handedness. I have a trial sequence inside the loop but it doesn't have much in it. I also don't need 30 cycles. I only need 10. I know I could probably use a form but I would prefer to use a loop and have it scored. Is this possible?
I had the loop set up differently before (see OldCode.txt attached) with Left, Right, and Both as different options for each question_text (e.g. draw, use a toothbrush, etc.) and that set the the cycles to 10 (the correct value).
So, my questions are:
1. how do you make the loop run (my code just skips it)
2. how do you make the loop score (I'm not sure where the scores go)
3. I think I need a feedback item to display the percentage of handedness
Comments
Another questionnaire I will be using is quite complicated. I have attached a copy of it. Do you think this questionnaire would work better as a form (e.g. using rating scales for the response choices) or as a loop? I will have to score this questionnaire as well.
I'm also having a lot of trouble with the loops - they seem to arbitrarily delete, move, or add columns. Is there a reason this happens?
I think I figured out a way to do these questionnaires using the sketchpad. I'm having a problem with the response though. I've asked for a keyboard response and input the keys that are allowed but I have to hit each key twice before the next question comes up. Also, is there documentation on the logger?
You do not have to address the previous posts. I've put the remaining issues here.
I have figured out most of the loops. The problems remaining from the last few days are:
1. help with the logger
2. arbitrary deletion and moving of columns in the "loop"
3. for text input, can keyboard response be restricted. For example, for age, only allow numbers.
4. use tab to go from one text input to the next on the same form_text_input.
5. links in the forum don't work btw
6. I need to do calculations for each loop. Can I do the calculations in the feedback form if the feedback form comes right after the questionnaire? Is there a good example I can follow?
Hi,
We need more detail. What is it that you need help with?
There is some help on the documentation:
Same here. What is the problem? Does arbitary deletion happen, or do you want to be able to do it?
In the form per se, this cannot be done, but you could check the response afterwards, and rerun the form if an invalid input was given (similarly to when no response was given, as explained in the other discussion)
As far as i know this is not possible.
Yes, they are not meant to stay active forever. What we post here, might be outdated some time in the future. If you have any particular links in mind, then please share
Calculations need to be done in
inline_scripts. You can do the math there, save the results to variables (e.g.var.response) and then you can put the response into a feedback item (like that[response]).In general, it would help a lot, if you share your experiment with us, not just the text version of individual sequences.
Eduard
Dear Eduard:
The code has a problem at the moment. I can tell because the window is moved. When the code is right the popup window stays centred.
In form_text_input, there are times when it works properly as in the Age/Sex form but there are times when it doesn't as in the noisyjob form. In the Age/Sex form when you hit "enter", you can still enter information in the following fields. When you hit enter in the noisyjob form, it automatically goes to the next screen and you don't get to click the continue button.
I have attached my experiment. There are still some things that need tweaking but it's getting there.
In answer to the other questions:
Thanks for the logger information - that helps a lot.
1. arbitrary deletion and moving columns happens on its own in the loop especially if you try to change something
2. Most of the other information was addressed. It would be nice to have links to documentation instead of dead forum links. If it doesn't apply anymore, then shouldn't the link be removed? I think if the link is to documentation instead, then this will always remain and update with new versions of the documentation.
3. I'll try the python inline script for the calculations. Thanks.
I have never encountered something like that. If you can reproduce that behaviour reliably, could you file an issue on Github?
Eduard
Dear Eduard, I wouldn't know how to show that. It happened yesterday when I tried to rename a column heading but it may have just been re-sorting alphabetically.
The deletion is not happening in the new version yet.
This can be closed as well. If it happens again, I'll re-post.