Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • T threshold
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar

Admin message

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
  • Sagar R Pandav
  • threshold
  • Issues
  • #23

Discussion: Level of parameters

Created by: peilingjiang

As mentioned in EasyEyes/control-panel#1, there are two levels of parameters: experiment (e.g., if use RC), block (e.g., if display fixation). Experiment-level params should be parsed at the beginning of the experiment and block-level params should be parsed at the beginning of each block (now within every trial). Should we add an extra column in the input sheet to identify the level of params?

Assignee
Assign to
Time tracking