You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
changing the way we report the scores: instead of labeling the scores as dot_easy and dot hard, like we have in our documentation (see Scene conditions), he suggests to use possible_scrambled and impossible_scrambled, to match the labels in their paper.
I don't think it's an issue for the behavioral data we will send with the paper, however, I am wondering how should we publish this behavioral data in our documentation, if we should keep the original labels we've given to match the conditions list and file names or if we should publish them with the author's suggestions.
The text was updated successfully, but these errors were encountered:
ferponcem
changed the title
Scene conditions
Scene conditions and scores labels
Jan 26, 2024
Thx.
I propose to keep the author's suggestion for the paper. But we'll have to do some file renaming to run to match the changes required by the authors. This will be visible in the next release of the data on NeuroVault /EBrains.
When preparing the paper, the author of the Scene task suggested two things:
dot_easy
anddot hard
, like we have in our documentation (see Scene conditions), he suggests to usepossible_scrambled
andimpossible_scrambled
, to match the labels in their paper.I don't think it's an issue for the behavioral data we will send with the paper, however, I am wondering how should we publish this behavioral data in our documentation, if we should keep the original labels we've given to match the conditions list and file names or if we should publish them with the author's suggestions.
The text was updated successfully, but these errors were encountered: