[Jeremy]

Hi Marisol,

The closing parenthesis at line 406 matches the open parenthesis of failure( at line 404, but you use it as if it were closing the open parenthesis of newTrial( from line 378. As a result, all the .logs that you attach to that closing parenthesis refer to the Key element on which you called failure, so you won’t get any extra column (but you should get a line for a keypress, for sure)

The same problem is repeated in the two other Template commands

Tip: the editor on the PCIbex Farm will highlight the matching parentheses when you place the caret just before or after, or if you select, the parenthesis

Jeremy

[Jeremy]

Hi,

The trials are not skipped, they are just executed very quickly, because you didn’t include any wait command. You probably want to replace .test.clicked() with .wait() in the “final” trial, and add something to your “thanks” trial so your participants have time to read the message (eg. a Button element with .wait() too) and can then move on to the next trial in your sequence, labeled “sendd”, which will send the results to the server

Jeremy

[Jeremy]

Hi,

I’m sorry, I had forgotten to update the version of PennController at https://github.com/PennController/Sync.git — it should now be 2.0

Note that you can simply download PennController.js from GitHub and then upload it manually to your project’s js_includes folder

Jeremy

[Jeremy]

Hi,

Sorry for the late reply. This is a known issue, which I tried to address with yesterday’s maintenance operation. You should be able to edit your project again, but unfortunately the main script file is now permanently lost. I apologize for that, please let me know if I can do anything to help with re-writing it

Note that the maintenance operation made the use of DebugOff optional: the debugger is now always on when running the demonstration link, and always off when running the data-collection link

Jeremy

[Jeremy]

Hello Giorgio,

1) Use the command disable to disable the Video element. Use a value of 0.01 if you want the overlay preventing participants from clicking the controls to be displayed with full transparency

(note that the experiment at your link currently does not work, and the debugger—which you should turn back on until you are ready to recruit your first real participant—throws errors like “No column named ‘VIDEO’ found in table A_FDS_noMask. Did you mean to type ‘AUDIO’?” or “No table found with name AV_FDS_cloth. Did you mean to type ‘AV_FDS_noMask’?”)

2) This must come from an extension installed on the participant’s browser, there’s no automatic translation feature in PCIbex

Jeremy

[Jeremy]

Hi,

Unfortunately that’s not something I anticipated when I designed the Tooltip element. The best you could do for now, I would say, is estimate the height of the top tooltip and apply a transform: translateY CSS rule to the bottom one, to move it below the top one. Here’s an example:

newCanvas("blue", 400,400).color('blue').print()
,
newTooltip("hello world").print( getCanvas("blue") )
,
newTooltip("bye earth").print( getCanvas("blue") ).css("transform","translateY(2.5em)")

Jeremy

[Jeremy]

Hi,

The original Ibex Farm won’t let you edit the files that come by default with new projects. However you can freely edit files you add yourself. You can use PennController.css to target PennController elements, or you can use global_z.css to write your own general CSS rules

The jump error you encounter most likely means that you are using an old version of PennController.js. Make sure to use the latest version in your project

Jeremy

[Jeremy]

Hi Stephanie,

Thanks for the feedback, I’ll look into the code that handles uploading. I have deleted the reference to rnc-1_ibex_stimuli_BE.csv, you should now be able to work on your project again

Jeremy

[Jeremy]

Hi,

You can use row. to reference cells from the current row when generating a trial from within Template( "table.csv", row =>, and you can use .log on the closing parenthesis of newTrial() to add a column to the end of each results line generated by the corresponding trial. So you can do something like this:

Template("tarefa1Alvo.csv", row =>
  newTrial("tarefa1Alvo",
    // ...
  )
  .log("acuraciaAlvoT1" , getVar("acuraciaAlvoT1"))
  .log("ParticipantID", subjID)
  .log("Estimulo", row.estimulo)
)

Jeremy

[Jeremy]

Hi Stephanie,

It looks like the file rnc-1_ibex_stimuli_BE.csv cannot be found, which is the likely source of the problem. I will need to delete its entry from the list of resources in your projects before you can edit it again

Unfortunately I don’t think there is a way to prevent such issues on your end. I am working on improving the farm’s code though, I hope that Sunday’s maintenance operations will be able to address that. I apologize for the inconvenience

Best,
Jeremy

[Jeremy]

You have correctly identified the issue: there seems to be a conflict between the initial press on spacebar for the DashedSentence controller in “in place” mode and the debugger being on for whatever reason. That being said, I have no idea what causes that conflict

In any case, the behavior you see when the debugger is off is the normal behavior, the one consistent with how the DashedSentence controller works, and the one that your participants will experience anyway. Passing a string to the blankText parameter will overwrite the two dashes: if you pass "Aperte espaço para avançar.", the text will appear on the page before the first press on Space; if you pass the empty string "" then the page will be blank until the participant presses Space

The debugger bug (ironically) skips the whole pre-spacebar display, whether it should show the standard two dashes, a custom message or just a blank page, and you will see the first word instead. I’ll work on fixing this (if I manage to identify the source of the bug) but in the meantime you should just keep it in mind when designing your experiment

Jeremy

[Jeremy]

I cannot see the URL, you can send it to support@pcibex.net if you want

Jeremy

[Jeremy]

Hi Andressa,

Do you have a link to your experiment?

Jeremy

[Jeremy]

Hi Alex,

Unfortunately, in your case, the problematic file seems to be main.js. I tried to find an older version of it in the database’s records, but have had no luck. This means that the main script file of this project is lost. Do you happen to have a copy of it somewhere?

Jeremy

[Jeremy]

Hi,

The command selector.test.selected does not take a key as an argument, but a reference to an element in the Selector element. So you could do something like this:

.test.selected({
  V: getImage("inappropriate"),
  B: getImage("infelicitous"),
  N: getImage("appropriate")
}[variable_practice.Right_Key])

There is no test.pressed command for the Selector element: https://doc.pcibex.net/selector/

Jeremy

[Author]

Posts