📗
UpGrade Platform - Documentation
6.0
6.0
  • UpGrade Overview
  • Creating an Experiment
    • Unit of Assignment
    • Simple Experiment
    • Factorial Experiment
    • Inclusion and Exclusion
    • Schedule and Post-Rule
    • Exporting Experiment Data and Design
  • Creating a Feature Flag
  • How UpGrade Works
  • Researcher Guide
  • Developer Guide
    • ⚡Quick Start: Running UpGrade Locally with Docker
    • ⚡Quick Start: Running locally w/o Docker
    • UpGrade + AdapComp (Mooclet) in Docker
    • 🚶‍♀️Walkthroughs
      • Your Application and UpGrade
      • Example 1: A Quiz Web App
      • Example 2: An Online Math Game
    • 📚Reference
      • API
      • Client Libraries
        • TypeScript / JS
          • Class: UpgradeClient
          • Class: Assignment
          • SDK Interfaces
            • Interface: IMetric
            • Interface: IExperimentUser
            • Interface: IExperimentUserAliases
            • Interface: ILog
            • Interface: IMarkExperimentPoint
            • Interface: IMetric
            • Interface: IRequestOptions
            • Interface: IResponse
            • Interface: IUser
            • Interface: IUserGroup
      • Environment Variables
        • Frontend Environment
        • Backend Environment
      • Context Metadata
      • Metrics
      • Setting up Google-Auth
      • API Authorization
      • Data Architecture
    • 👨‍💻Contributing Code
      • Branching Workflow (Git-Flow)
      • Pull Request Expectations
    • 😅Troubleshooting
      • Relation ‘experiment_condition’ already exists
      • User not found. Authorization error
      • Token is not present in the request header
      • nodemon exits without explanation
      • Unable to find New Relic module configuration
      • No email received for export data
      • Opening a new tab in UpGrade prompts for re-authorization
      • Error: Cannot find module 'upgrade_types' (or a type from 'upgrade_types' does not exist)
  • Glossary
Powered by GitBook
On this page
  1. Creating an Experiment

Simple Experiment

PreviousUnit of AssignmentNextFactorial Experiment

We are setting up an experiment that compares the effectiveness of two different versions of the same lesson. To design this experiment, you have to create two conditions in the Experiment Design tab, and give each of them an assignment weight. The assignment weights should add up to 100. After the conditions, you have to define Design Points for the experiment. Each decision point is represented by its corresponding site and target. Decision point is the place or function in code where the conditional code execution happens. For more description, please refer to the following papers: and .

UpGrade: An Open Source Tool to Support A/B Testing in Educational Software
Optimizing an Educational Game Using UpGrade: Challenges and Opportunities