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
Thanks for all of your work in putting this dataset together !
One small stumbling block that has come up in my initial iterations with @MarieStLaurent : currently, there's a field in the perTrial_annotation.tsv files that is labelled exclude_session. This is appropriately described in the accompanying JSON file as only referring to memory analyses (that is, users should filter on that flag for memory analyses) rather than for analyses more generally (e.g., in perception, where the trials should be kept).
As I'm working with the trial-averaged beta maps (available in model-fitHrfGLMdenoiseRR_stats-imageBetas_desc-zscore_statseries.h5), filtering on exclude_session incorrectly suggests that there are discrepancies between the tsv and h5 files.
Would it make sense to rename the field to refer to memory directly ? I'd suggest something like incorrect_order.
The text was updated successfully, but these errors were encountered:
Thanks for all of your work in putting this dataset together !
One small stumbling block that has come up in my initial iterations with @MarieStLaurent : currently, there's a field in the perTrial_annotation.tsv files that is labelled
exclude_session
. This is appropriately described in the accompanying JSON file as only referring to memory analyses (that is, users should filter on that flag for memory analyses) rather than for analyses more generally (e.g., in perception, where the trials should be kept).As I'm working with the trial-averaged beta maps (available in model-fitHrfGLMdenoiseRR_stats-imageBetas_desc-zscore_statseries.h5), filtering on
exclude_session
incorrectly suggests that there are discrepancies between the tsv and h5 files.Would it make sense to rename the field to refer to memory directly ? I'd suggest something like
incorrect_order
.The text was updated successfully, but these errors were encountered: