WCST card manipulation

Comments

• Fab

  September 2023

  Hi @schmer,

  Thanks for reaching out. Your query is a litte too generic to suggest anything specific. Generally speaking, modifying task characteristics on the go typically requires programming (in Python or in Javascript), though it can sometimes also be achieved using the "Run if" parameter of sequence objects. More prcesie advice would require that you described in detail how you implement your task and the selection of stimuli, and possibly that you upload a basic version of your task. If you are new to Open Sesame, I also recommend that you follow the various tutorials and consult the documentation to get familiar with all the basic features before ventiuring into more complicated issues such as coding (the latter might require that you first become familiar with some basics of Python or Javascript).

  Best,

  Fabrice.

  
• schmer

  September 2023

  Hi Fabrice,

  Thanks a lot for your answer!

  So far I have the general experiment running. In addition to the tutorial online and with the help of the forum I added a new variabe to count perseverant response and error.

  I want to increase the chances of specific cards being shown after a perseverant error is made, for example show color1 twice as much as color2.

  here is what i got so far:

  MWCST.OS.osexp

  Thank you so much! Looking forward to a reply!
• schmer

  September 2023

  Hi,

  I now have the experiment running as I want it inOPenSesame, but when trying to run it in OSWeb I get the following error:

  too many values to unpack (expected too many values to unpack (expected 2)Traceback (most recent call last):

   File "C:\Program Files (x86)\OpenSesame\Lib\site-packages\libqtopensesame\extensions\_extension_manager.py", line 159, in fire

    return_value = ext.fire(event, **kwdict)

            ^^^^^^^^^^^^^^^^^^^^^^^^^

   File "C:\Program Files (x86)\OpenSesame\Lib\site-packages\libqtopensesame\misc\base_subcomponent.py", line 56, in fire

    return getattr(self, u'event_%s' % event)(**kwdict)

        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   File "C:\Program Files (x86)\OpenSesame\Lib\site-packages\opensesame_extensions\osweb\oswebext\oswebext.py", line 277, in event_osweb_run

    index_path = convert.exp_to_html(

           ^^^^^^^^^^^^^^^^^^^^

   File "C:\Program Files (x86)\OpenSesame\Lib\site-packages\osweb\convert.py", line 370, in exp_to_html

    _, script, pool_paths = _extract_script_and_pool_paths(exp)

                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   File "C:\Program Files (x86)\OpenSesame\Lib\site-packages\osweb\convert.py", line 608, in _extract_script_and_pool_paths

    script = OSWebWriter(osweb_exp, fd.name).script

         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   File "C:\Program Files (x86)\OpenSesame\Lib\site-packages\libopensesame\osexpfile\_osexpwriter.py", line 49, in __init__

    self._write_tarfile()

   File "C:\Program Files (x86)\OpenSesame\Lib\site-packages\libopensesame\osexpfile\_osexpwriter.py", line 72, in _write_tarfile

    fd.write(self.script)

         ^^^^^^^^^^^

   File "C:\Program Files (x86)\OpenSesame\Lib\site-packages\osweb\oswebwriter.py", line 71, in script

    _, (item, cond), _ = self.parse_cmd(m.group('cmd'))

      ^^^^^^^^^^^^

  ValueError: too many values to unpack (expected 2)

  does anybody knoiw how to deal with this or knows where it comes from?

  Thanks in advance!
• Fab

  September 2023

  Hi @schmer,

  Did you check the compatibilty check in the OSWeb control panel? This would flag out the most obvious issues. Please remember that not all functionalities ofs Open Sesame are supported in OSWeb (and then it differs a little between OSWeb 1.4 and OSWeb 2.0). The most likely explanation is that your task contains objects or code that is not compatible with OSWeb. If your experiment is a version of that you upladed earlier, if would not work OSWeb because the latter does not support Python code. You need to replace that code with code written in Javascript in inline_javascript objects. Generally speaking, if you aim to develop a task to run in a browser, the recommended method is to go testing it through your browser from the onset so that you can build it progressively while detecting possible compatibility issues early (using OSWeb 2.0 offers greater functionalities to collect data from the browser locally in case you do not necessarily plan to deploy your task using JATOS).

  Best,

  Fabrice.