Sending specific forms.



Back to Contents



This tutorial is optional if you are happy with a pure random distriubtion. Also, if you are using a server which doesn't allow server side code, and are instead relying on a third party form manager like formsubmit, these next two pages should be ignored and you should go straight to the publication clean up.



First, make sure you have:

(as of June 2020)

You will learn:

  1. How to alternate between page orders rather than using pure randomization.
  2. How to Make the experiment display a specific page order.


For these code heavy tutorials, it is recommended to full screen the video and watch at 720p



Resources

Unlike previous tutorials, this one has 3 flavors:
  1. Alternate your trial order based on how much data was saved
    • Pros:
      • Easiest to write
      • Doesn't rely on a single file which can only be used by one user at a time
      • If a user doesn't complete an experiment, it doesn't throw off the cycle
    • Cons:
      • Forcing a specific order still effects the cycle
      • If multiple users start, they will all have the same order
    • Good for experiments with a slow hit rate
    • The changed files for this step can be found here.
  2. Alternate your trial order based on a file saved at the beginning.
    • Pros:
      • Allows users to start before others finish without throwing off the cycle
      • Forcing a specific order doesn't effect the cycle
    • Cons:
      • A little harder to write because it relies on file reading/writing
      • If a user loads the page and drops out, the cycle is thrown off.
      • Relies on a central file which only one user can access at a time.
    • Good for experiments where many participants start simultaneously, but few leave without completing the experiment.
    • The changed files for this step can be found here.
  3. Alternate your trial order based on a file saved after a specific page.
    • Pros:
      • Allows users to start before others finish without throwing off the cycle
      • Forcing a specific order doesn't effect the cycle
      • Users can leave before a certain point without throwing off the cycle.
    • Cons:
      • Much harder to write because it relies on a third call to the server
      • Relies on a central file which only one user can access at a time.
    • Good for experiments where many participants start simultaneously
    • The changed files for this step can be found here.


Note:
  1. The files will be slightly different from the tutorials (all versions can have a user ID and force shuffle)


Proceed to get some useful server side information and make your data less messy.