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

Add more frames to cover common tasks #72

Closed
18 tasks done
kimberscott opened this issue Jul 16, 2019 · 3 comments
Closed
18 tasks done

Add more frames to cover common tasks #72

kimberscott opened this issue Jul 16, 2019 · 3 comments

Comments

@kimberscott
Copy link

kimberscott commented Jul 16, 2019

Build out the library of experimental components to include more easy-to-use frames for common tasks:

  • Remove extraneous docs (e.g. deprecated physics-only frames) to reduce confusion
  • Frame to display the user's webcam, intended for a break / position check. Customize text.
  • Add video examples of existing frames
  • Frame to do alternation/change-detection task.
    • image lists A and B for left and right.
    • whether to start A or B
    • whether to order all randomly within lists.
    • total duration
    • wait for pre-load of all images
    • duration on and off in ms
    • whether to show border
    • whether to do attn-grabber at all
    • store appropriate data but reduce overall event data stored
    • fix fetch behavior in expandAssets to notify upon any missing files
    • add docs ideally w video
  • exp-lookit-preview, exp-lookit-preview-explanation: combine so that there isn't the odd need to put them right next to each other for them to work properly. Make the preview-explanation optional. (absorbing Combine exp-lookit-preview-explanation and exp-lookit-preview frames #108 )
  • Set up video-config frame to require checking for persistent permissions (see screenshots/notes from @jchu10 )
  • Improvements to consent form:
  • Frames to show image and/or audio. Create general underlying frame plus extensions with simplified options for expected use cases:
    • Create general frame as starting point
    • Variant 1: Show one image. Choose next button or auto-advance after time. Region for parent-text. Specify position to fill image area OR provide height/width and top/left values. Optional whether should have region for parent-text (may be same frame)
    • Variant 2: Frame to show image + audio. As above; choose next button or auto-advance after audio. Optional replay.
    • Variant 3: Frame to show N images with defaults for center, left, right placement. Optional audio. Auto-advance after time.
    • Variant 4: Frame to show N options (images) and require clicking on one. Optional confirm or immediately proceed. Optional audio.
    • Variant 5: As above, but limit set of choices. Allow specifying timing of appearance of any image. (Intended for standard reaction time experiments)
    • Variant 6: "Training" version of below per comment
    • Add back in the "highlighting" timing from exp-lookit-story-page since it seems like it might be more generally useful. Documentation with videos for all frames.
  • Frame to do just calibration and/or attention-grabber (wait for session recording to start if needed)
  • Frame to show a video and optional audio. Choose proceed automatically or next button. Allow specification of video size (incl. fill). Choose proceed automatically after video, proceed automatically after audio, proceed automatically after N seconds, or next button. Choose loop audio, loop video.
  • Frames for easy starting/stopping session recording, as alternative to including parameters on functional frames.

Feedback about what would be most helpful to you for your study designs is very welcome! Comment below.

You can also try out frames in progress by updating your experiment runner to the most recent commit of this branch. Changes aren't reflected in the frame docs yet, though, so you'd have to dig a little in the code to see parameters to use.

@kimberscott kimberscott changed the title Add "simple" frames Add more frames to cover common tasks Mar 18, 2020
@qianmiao90
Copy link

qianmiao90 commented Apr 9, 2020

For your component "Frame to show N options (images) and require clicking on one. Optional confirm or immediately proceed. Optional audio." Would it be possible to set such condition, so that
if clicking on the correct image, it proceeds;
else if clicking on the incorrect one, an error message appears and it proceeds only after clicking the correct image.
In both cases, accuracy and response time need to be recorded.

@kimberscott
Copy link
Author

kimberscott commented Apr 10, 2020

@qianmiao90 Yes, the sequence of selections & timing will be recorded regardless.

The more general version I might propose is the following: along with each image, you specify (a) whether clicking it should advance to the next frame, (b) an optional audio file to play upon clicking it (during which time nothing else can be clicked on), (c) optional text to display upon clicking it (have to think about where and for how long it's displayed). But happy to consider special-case versions or extensions depending on other expected uses - if you'd also use this frame or want to do something similar, please chime in here!

@kimberscott
Copy link
Author

May add start/end session recording "placeholder" frames to make writing sequence more straightforward, although this can also still be done within individual frames

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