Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem saving data #159

Open
danieljwilson opened this issue Mar 15, 2022 · 2 comments
Open

Problem saving data #159

danieljwilson opened this issue Mar 15, 2022 · 2 comments

Comments

@danieljwilson
Copy link

Version of Experiment Factory:

Latest

Expected behavior

I am running some experiments created by a collaborator (@JuneOh710) as part of a battery.

I expect at experiment completion for:

  • data to be saved
  • the completed experiment to be removed from the subject's pool of experiments to complete

Actual behavior

When I run other experiments (for example maintained by @vsoch or another collaborator of mine @juhng62) they seem to work fine. Data is saved as expected and the experiments are removed from the queue. When running those of @JuneOh710 nothing is saved and I am just stuck on the last page (i.e. it neither continues to the next experiment nor removes the completed experiment from the queue)

Steps to reproduce behavior

I have a public repo of the container build dockerfile. It contains the following experiments:

    five-item-ambition-survey \
    boredom-proneness-scale-short-survey \
    brief-sensation-seeking-survey \
    affective-conflict-resolution-task \
    berlin-numeracy-test \
    cognitive-estimation-test \
    effort-avoidance-task \
    jdm-classics \
    psychomotor-vigilance-test \

where the first three are surveys that work correctly and the last 6 are the new tasks added by @JuneOh710 that are not.

@vsoch
Copy link
Member

vsoch commented Mar 15, 2022

At quick glance, the main difference is that most of the expfactory experiments use jspsych to handle submitting data, and with a promise so that it doesn't continue until we are finished. E.g., here. The experiments here are using valid endpoints, but it's not clear we are directed to the server /next, and the format of the data maybe not be like {"data": results} e.g., here. My suggestion to debug this (if I were doing this) is to create a container with just one experiment, and do console.log before and after every action, and check data along the way. Always check the error responses of requests. I suspect the error is that something you think happening is indeed not. Once you've figured that out, you can likely fix these issues.

@vsoch
Copy link
Member

vsoch commented Oct 4, 2022

Updates here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants