psychopy 2025.2.4__py3-none-any.whl

psychopy/alerts/alertsCatalogue/3110.yaml

@@ -0,0 +1,25 @@
+# The first key-value pair is used for the alerts package
+
+code: 3110
+cat: Timing
+msg: Your stimulus {type} time of {time} is less than a screen refresh for a {Hz}Hz monitor.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Stimulus duration is less than one screen refresh
+
+synopsis: |
+  Your stimulus is scheduled to last for a duration that can't be achieved with a normal 60 Hz monitor. Duration will implicitly be round up (probably) to the next frame duration.
+  
+  Requested start or stop times of visual components cannot be presented for times requested.
+  Accurate presentation times must be in increments of your screen refresh rate.
+
+details: |
+  Stimuli can only be presented for a fixed number of screen refreshes. If you screen has a refresh rate of 60 Hz (common for standard monitors) then each screen refresh period lasts 1/60 s (roughly 16.6667 ms). That means you can present your stimulus for 16.7 ms but not for, say, 5 ms because that would require the stimulus to be presented for half of one screen refresh period.
+
+solutions: |
+  We recommend for brief stimuli that you simply specify your stimulus duration in terms of the number of frames it should be presented (e.g. 1, 2, 3, for 16.7, 33.3 and 50 ms respectively). That reminds you of what is possible and means that PsychoPy won't have to guess about what to do when the desired duration isn't achievable.
+
+  If you need stimuli to be presented for briefer durations than 16.7 ms then you should look into high-frame-rate displays (100, 120 and 144 Hz displays are all available). There are also now vraiable-frame-rate monitors that can vary the duration of each frame within limits. If you are *already* using a high- or variable-rate monitor then this alert may not be relevant to you.
+
+versions: |
+  All versions.

psychopy/alerts/alertsCatalogue/3115.yaml

@@ -0,0 +1,24 @@
+# The first key-value pair is used for the alerts package
+
+code: 3115
+cat: Timing
+msg: >-
+    Your stimulus {type} time of {time} seconds cannot be accurately presented for {time} on a {Hz}Hz monitor.
+
+# The following are typically used for online help pages, and support reStructured Text.
+
+label: Stimulus duration is not possible on a standard monitor refresh
+
+synopsis: |
+  If using a 60Hz or 100Hz monitor, then for accurate presentation of visual stimuli, components must be presented in valid multiples of screen refresh for 60 Hz or 100 Hz.
+
+details: |
+  When presenting stimuli at, say, 60 Hz you stimulus can be presented for 1 frame (1/60 s = 16.667 ms), 2 frames (2/60 s = 33.333 ms) but not for intervening periods (20 ms is not possible because the stimulus would have to be presented for a little more than 1 frame, which isn't physically possible on standard fixed-framerate monitors.
+
+solutions: |
+  We recommend for brief stimuli that you simply specify your stimulus duration in terms of the number of frames it should be presented (e.g. 1, 2, 3, for 16.7, 33.3 and 50 ms respectively). That reminds you of what is possible and means that PsychoPy won't have to guess about what to do when the desired duration isn't achievable.
+
+  If you need stimuli to be presented for briefer durations than 16.7 ms then you should look into high-frame-rate displays (100, 120 and 144 Hz displays are all available). There are also now vraiable-frame-rate monitors that can vary the duration of each frame within limits. If you are *already* using a high- or variable-rate monitor then this alert may not be relevant to you.
+
+versions: |
+  All versions.

psychopy/alerts/alertsCatalogue/3210.yaml

@@ -0,0 +1,27 @@
+# The first key-value pair is used for the alerts package
+
+code: 3210
+cat: Audio
+msg: Speaker {deviceName} is set to "Exclusive low latency" mode. As resampling is enabled, this mode has little benefit over "Shared low latency" mode, with some drawbacks.
+
+# The following are typically used for online help pages, and support reStructured Text.
+
+label: Exclusive latency mode
+
+synopsis: |
+  Speaker is set to "Exclusive low latency" mode. As resampling is enabled, this mode has little benefit over "Shared low latency" mode, with some drawbacks.
+
+details: |
+  "Exclusive low latency" mode differs from "Shared low latency" mode in two ways:
+  - PsychoPy will take exclusive control of the speaker, meaning that other apps won't be able to access it while your experiment is running, and may crash.
+  - Because of this exclusive control, we have more flexibility in the range of sample rates which we can play on the speaker.
+
+  However, if "resampling" is ticked, then audio is automatically resampled to match the speaker's sample rate anyway, so "Exclusive low latency" offers little benefit over "Shared low latency".
+
+solutions: |
+  If you actively want to prevent the speaker from being used by other applications (for example, you want to make sure the participant isn't playing music in the background), then no action is required and you can ignore this alert.
+
+  If you don't want this, then you most likely want "Shared low latency" mode instead.
+
+versions: |
+  >2025.1.0

psychopy/alerts/alertsCatalogue/3610.yaml

@@ -0,0 +1,19 @@
+
+code: 3610
+cat: Validation
+msg: Multiple Components in the same Routine are validated by {validator}, please ensure that the timing of these Components do not overlap.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Multiple Components in same Routine validated by same validator
+
+synopsis: |
+  A validator can only validate one stimulus at a time, but it looks like you have multiple stimuli in the same Routine which are validated by the same validator. This may be fine, but you will need to be sure that they don't overlap in their timing.
+
+details: |
+  A validator can only validate one stimulus at a time, as they only respond True/False for whether there's light/sound, not distinguishing between different sources. If you have two stimuli at the same time, then they will obscure the start/stop times of one another, meaning your validator will give the wrong results. 
+
+solutions: |
+  This may be fine! You just need to make sure that the multiple Components in the same Routine which are validated by the same validator aren't overlapping in their timing. If they're not, you can ignore this!
+
+versions: |
+  >2025.1.0

psychopy/alerts/alertsCatalogue/4051.yaml

@@ -0,0 +1,19 @@
+
+code: 4051
+cat: Experiment configuration
+msg: Experiment was built in a future version of PsychoPy ({version}), we recommend either updating PsychoPy or changing the "Use Version" setting in Experiment Settings to this version.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Experiment from future version
+
+synopsis: |
+  It looks like you're trying to open an experiment built in a newer version of PsychoPy than you currently have installed. This can cause problems, your experiment may run differently to how you expect or may not run at all.
+
+details: |
+  Between different version of PsychoPy, we make a number of changes to improve usability and performance, but which mean that newer experiments may contain code which older versions do not know how to handle. We always try to maintain "backwards compatibility" - so that experiments built in older versions run the same in newer versions. However, we cannot predict what changes we will make years down the line, so cannot guarantee "forwards compatibility" in the same way. This means that experiments built on newer versions of PsychoPy may run differently on older versions, or may not run at all.
+
+solutions: |
+  To fix this, we recommend updating to the newest version of PsychoPy. Or, if you need an older version for other reasons, you can set this specific experiment to run in a different version by changing the "Use Version" parameter in Experiment Settings to the version it was created in (or a newer version).
+
+versions: |
+  Any

psychopy/alerts/alertsCatalogue/4052.yaml

@@ -0,0 +1,19 @@
+
+code: 4052
+cat: Experiment configuration
+msg: Experiment was built in a past version of PsychoPy ({version}), saving it in this version may add parameters which cannot be parsed.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Experiment fixed to past version
+
+synopsis: |
+  It looks like your experiment is set to run in a version before 2021.1.0, the version of PsychoPy you have currently installed is newer than this, so saving the experiment in your current version may add new types of parameters which the version it is set to cannot interpret.
+
+details: |
+  Between different version of PsychoPy, we make a number of changes to improve usability and performance, but which mean that newer experiments may contain code which older versions do not know how to handle. We always try to maintain "backwards compatibility" - so that experiments built in older versions run the same in newer versions. However, we cannot predict what changes we will make years down the line, so cannot guarantee "forwards compatibility" in the same way. This means that experiments built in the current version of PsychoPy but set to run in an older version may not run as expected, or at all. This is a particular issue between 2020.2.10 and 2021.1.0 as between the two we added several new types of parameter, meaning if you run in 2020.2 PsychoPy will not recognise them.
+
+solutions: |
+  To fix this, we recommend setting the experiment version in the Experiment Settings menu to be 2021.1.0 or newer, as these will have the ability to recognise the new parameter types.
+
+versions: |
+  >2021.1.0

psychopy/alerts/alertsCatalogue/4105.yaml

@@ -0,0 +1,18 @@
+# The first key-value pair is used for the alerts package
+
+code: 4105
+cat: Timing
+msg: Your stimulus start {type} exceeds the stop {type}. Consider using a {type} duration.
+
+# The following are typically used for online help pages, and support reStructured Text.
+
+label: Component start time exceeds its stop time
+
+synopsis: |
+  A component start time/frame exceeds the stop time/frame. This means that the component starts *after* it is due to finish and the stimulus will most likely not be shown at all.
+
+solutions: |
+  Check your start and stop time carefully, including the units being used. For example your stimulus might be set to start at a certain `time` (say 36 seconds) rather than frame number 36.
+
+versions: |
+  All versions.

psychopy/alerts/alertsCatalogue/4115.yaml

@@ -0,0 +1,21 @@
+# The first key-value pair is used for the alerts package
+
+code: 4115
+cat: Timing
+msg: Your stimulus {type} type {frameType} must be expressed as a whole number.
+
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Component start/stop in units of frames must be whole numbers
+
+synopsis: |
+  Component start and stop times/durations in frames must be given as whole numbers.
+
+details: |
+  Since it isn't possible to start or stop a stimulus part-way through a screen refresh it would be unwise to request that PsychoPy attempts that.
+
+solutions: |
+  Check your stimulus start/stop time and set to an integer value instead of a decimal value.
+
+versions: |
+  All versions.

psychopy/alerts/alertsCatalogue/4120.yaml

@@ -0,0 +1,19 @@
+
+code: 4120
+cat: Timing
+msg: Component {component} has stop time set as a duration, but doesn't have a start time
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Component stop duration with no start time
+
+synopsis: |
+  In order for stop time to be set as a duration, PsychoPy needs to know the time at which the component started. When there's no start time, stop time will be calculated from the duration as if start time were 0s.
+
+details: |
+
+
+solutions: |
+  You can either add a start time to this component, or change the stop time to be set in a different way (e.g. `time (s)`)
+
+versions: |
+  > 2022.1.0

psychopy/alerts/alertsCatalogue/4125.yaml

@@ -0,0 +1,23 @@
+
+code: 4125
+cat: Timing
+msg: Microphone component `{name}` given blank stop time, using max duration allowed by buffer size ({stopVal}s).
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Microphone component given blank stop time
+
+synopsis: |
+  Mircophone components can't record forever - there is a "buffer" with a finite size which will eventually fill up. As 
+  you requested for a Microphone component to continue recording forever (by leaving the Stop field blank), PsychoPy 
+  has substituted in the maximum time which you Microphone can record for, given the size of its buffer and the sample 
+  rate it records at.
+
+details: |
+  
+
+solutions: |
+  No action is needed! Your Mircophone component will record for as long as it is able. To silence this alert, simply 
+  give your Microphone component a duration.
+
+versions: |
+  >2023.1.0

psychopy/alerts/alertsCatalogue/4130.yaml

@@ -0,0 +1,19 @@
+
+code: 4130
+cat: Timing
+msg: Static Component `{name}` given infinite stop time
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Static Component given infinite stop time
+
+synopsis: |
+  Static Component pauses the frame loop while it's active, meaning that unlike other Components, it needs to have a fixed stop time to know when to finish. Otherwise, the experiment will simply stall forever, even if there's code in the Each Frame tab of a Code Component to end the experiment / stop the Static Component (as the frame loop is paused, so Each Frame code isn't happening). You won't even be able to end the experiment with the ESCAPE key as this is checked each frame!
+
+details: |
+  The only instance where you might want an infinite Static Component is if you're using threading, as threaded operations don't rely on a frame loop to execute their code. In this case, you can ignore this message. However, this is a rare and fairly advanced use case, so if the previous sentences sounded like jibberish, you almost certainly don't want an infinite Static Component!  
+
+solutions: |
+  Give your Static Component a fixed duration.
+
+versions: |
+  All

psychopy/alerts/alertsCatalogue/4160.yaml

@@ -0,0 +1,25 @@
+
+code: 4160
+cat: Timing validation
+msg: Cannot validate stop time for `{name}` as it stops on final frame of Routine
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Cannot validate stop time if stimulus ends on final frame
+
+synopsis: |
+  Timing validation works by asking a light/sound sensor, on the frame *after* a stimulus started/stopped, when it detected a stimulus start/stopping. If a stimulus ends on the final frame of a Routine, then there isn't a frame after so its stop time can't be validated.
+
+details: |
+  The timeline of a validation is as follows:
+
+  * Stimulus is asked to start/stop
+  * Frame loops
+  * Validation device is asked when it detected a stimulus starting/stopping
+
+  If the frame on which a stimulus is asked to stop is the final frame of a Routine, then there is no subsequent frame for the validator to be asked on. This means that your validated stop time will be `None`.
+
+solutions: |
+  This may be fine! You may only be interested in validating the stimulus' start time. If so, you can ignore this alert. If you do want stop time validation however, the Routine will need to be at least 1 frame longer than the validated stimulus.
+
+versions: |
+  All

psychopy/alerts/alertsCatalogue/4205.yaml

@@ -0,0 +1,19 @@
+
+code: 4205
+cat: Coding
+msg: Python Syntax Error in '{codeTab}' tab. See '{code}' on line number {lineNumber} of the '{codeTab}' tab.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Probable syntax error detected in your Python code
+
+synopsis: |
+  Python syntax error found in your code component.
+
+details: |
+  This *may* be spurious in that the code check may have failed to understand something that is a valid syntax (syntax in Python can change according to version) but this will become clear if you run your experiment and it fails to run. 
+
+solutions: |
+  Check the code carefully at the indicated line and on the few lines above. Check especially for things like un-matched parentheses or quote symbols.
+
+versions: |
+  All versions.

psychopy/alerts/alertsCatalogue/4210.yaml

@@ -0,0 +1,19 @@
+
+code: 4210
+cat: Coding
+msg: JavaScript Syntax Error in '{codeTab}' tab. See '{lineNumber}' in the '{codeTab}' tab.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Probable syntax error detected in your JavaScript code
+
+synopsis: |
+  JavaScript syntax error found in your code component.
+
+details: |
+  This alert *may* be spurious in that the code check may have failed to understand something that is a valid syntax (syntax in JavaScript can change according to version) but this will become clear if you run your experiment and it fails to run. 
+
+solutions: |
+  Check the code carefully at the indicated line and on the few lines above. Check especially for things like un-matched parentheses or quote symbols.
+
+versions: |
+  All versions.

psychopy/alerts/alertsCatalogue/4305.yaml

@@ -0,0 +1,21 @@
+
+code: 4305
+cat: Components
+msg: The component {name} is currently disabled and will not be written to your experiment script.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Component is currently disabled in your experiment
+
+synopsis: |
+  You have a disabled Component in your experiment. This alert is created to inform users that
+  disabled components will not be written to your experiment script. This may not be intentional,
+  and will therefore affect your desired outcome.
+
+details: |
+  Most likely you disabled the Component deliberately while testing things out, but this Alert is making sure you remember that it isn't currently operational.
+
+solutions: |
+  Re-enable the Component in the Builder view (component dialog boxes each have a "testing" tab: unselect the "Disable component" setting there). Otherwise just ignore this Alert if you intended it to be disabled.
+
+versions: |
+  >= 3.1.0

psychopy/alerts/alertsCatalogue/4310.yaml

@@ -0,0 +1,21 @@
+
+code: 4310
+cat: Components
+msg: Cannot calculate parameter.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Builder cannot check your parameter further
+
+synopsis: |
+  This alert is received when an integrity check has failed to calculate a parameter.
+  Most commonly, this is because a variable from code, or a conditions file, has been encountered,
+  and the value of the variable is not available to the integrity checking system.
+
+details: |
+  Longer description with optional links to further information
+
+solutions: |
+  This alert is for information only, and does not require any action.
+
+versions: |
+  >= 3.2.3

psychopy/alerts/alertsCatalogue/4315.yaml

@@ -0,0 +1,21 @@
+
+code: 4315
+cat: Components
+msg: Builder cannot interpret value "{param.val}" of {param.label} for {component.type} component "{component.params[name].val}" as a dollar sign has been used incorrectly.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Invalid dollar sign syntax.
+
+synopsis: |
+  This alert is received when a dollar sign has been used incorrectly in a stimulus parameter.
+
+details: |
+  By putting a dollar sign at the beginning of a parameter value, you can indicate that the parameter should be interpreted as code rather than as a string. However, a dollar sign should not appear anywhere else in the parameter value, unless it is either:
+  - After a `#` when the parameter is interpreted as code (meaning it will be commented out)
+  - Immediately after a `\`, an escape character (escaped dollar signs are only valid when the parameter is not interpreted as code, or within quotation marks if it is)
+
+solutions: |
+  If the dollar sign is a part of a string, you should add an escape character (`\`) immediately before it. If it is supposed to be in a comment, it must appear after a `#`. Otherwise, remove any dollar signs which are not at the very beginning of the value.
+
+versions: |
+  All

psychopy/alerts/alertsCatalogue/4320.yaml

@@ -0,0 +1,19 @@
+
+code: 4320
+cat: Components
+msg: Font `{param.val}` not found locally, will check Google Fonts on next run.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Non-local font.
+
+synopsis: |
+  This alert is received when a font has been specified which PsychoPy cannot find on your local machine.
+
+details: |
+  Google Fonts is a repository of thousands of free fonts, which PsychoPy is able to access on-the-fly, allowing you to use any font within the Google Fonts library (fonts.google.com) as if it were installed on your machine. However, retrieving this font requires PsychoPy to connect to the internet and send/receive some data, so we raised this alert to give you some warning that this will happen. Font files are tiny, so in most cases this will not noticeable, however if you are on a strictly metered connection or you are not connected to the internet at all then this may cause some issues.
+
+solutions: |
+  If your computer is connected to the internet and you don't have any limits on how much data you can send/receive, then no action is needed! PsychoPy will happily go off and find this font for you. However, if you are running offline or you have strict data limits, then you should install this font locally instead. Google Fonts can be downloaded for free from fonts.google.com as .ttf files, once downloaded these can be copied to a memory stick and installed on any machine you need by simply opening the file and clicking "Install".
+
+versions: |
+  All

psychopy/alerts/alertsCatalogue/4325.yaml

@@ -0,0 +1,23 @@
+
+code: 4325
+cat: Components
+msg: Font `{font} {style}` not available in weight `{weight}`, component `{name}` will default to Open Sans Regular.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Font not available
+
+synopsis: |
+  The font you requested could not be found in the weight and style you requested, this alert is to warn you that your component will use Open Sans Regular (fonts.google.com/specimen/Open+Sans)
+
+details: |
+  There are a few reasons why you might be receiving this alert:
+  1. The font you requested does not exist at all, there may be a typo in the font name.
+  2. The font is one which is not installed on your local machine or available on Google Fonts.
+  3. The font you requested exists, but not in the style you requested (bold, italic, etc.). For example, if you requested the font Raleway Dots (fonts.google.com/specimen/Raleway+Dots) in bold, you will always receive this error as this font only exists in regular.
+  4. The font you requested exists on Google Fonts, but could not be retrieved, for example if you are connected to the internet.
+
+solutions: |
+  The first things to check are that the name of the font is spelled correctly, that the font exists and that you are connected to the internet. You can check which fonts are installed on your machine through the Settings for your operating system, you can check whether the font exists on Google Fonts by going to fonts.google.com and searching for it. If the font exists, you can check (either on Google Fonts or your operating system's font manager) what weights and styles it exists in. If `bold` is ticked in Builder, then the requested font weight is 700 (Bold), if not then the requested weight is 400 (Regular). You can set the font weight more precisely by supplying a numeric font weight to the component rather than just True or False, for example if you wanted the font to be Extra-Light you could supply the value 200.
+
+versions: |
+  All

psychopy/alerts/alertsCatalogue/4330.yaml

@@ -0,0 +1,19 @@
+
+code: 4330
+cat: Components
+msg: Recording device '{device}' not found, using default device instead.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Recording device not found
+
+synopsis: |
+  The recording device specified in your Microphone component could not be found on your current machine, so when writing the Python code for this experiment to run, the default device will be used instead.
+
+details: |
+  When writing Python code for Microphone components, PsychoPy needs to know the numeric index of its recording device. If the device isn't connected, then this information isn't available, so the Python code is written with the default device index instead.
+
+solutions: |
+  The information in your `.psyexp` file won't be changed, just the compiled Python file. If you open the same `.psyexp` file on a machine with the device connected, the Python code generated will contain that device's index, so if you're just testing the experiment on a different machine to the one it will run on then you can ignore this alert.
+
+versions: |
+  > 2021.2.0

psychopy/alerts/alertsCatalogue/4335.yaml

@@ -0,0 +1,19 @@
+
+code: 4335
+cat: Components
+msg: The component or routine '{comp}' is only implemented online, so will do nothing when running locally.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Component or routine not implemented in Python
+
+synopsis: |
+  This component is not yet implemented in Python, meaning that it will do nothing in local experiments.
+
+details: |
+  You are receiving this alert as you are compiling an experiment to JavaScript, but the experiment contains a component which only works in JavaScript.
+
+solutions: |
+  No action required.
+
+versions: |
+  > 2022.1.0

psychopy/alerts/alertsCatalogue/4340.yaml

@@ -0,0 +1,19 @@
+
+code: 4340
+cat: Components
+msg: The component or routine '{comp}' is only implemented locally, so will do nothing when running online.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Component or routine not implemented in JavaScript
+
+synopsis: |
+  This component is not yet implemented in JavaScript, meaning that it will do nothing in online experiments.
+
+details: |
+  You are receiving this alert as you are compiling an experiment to JavaScript, but the experiment contains a component which only works in Python.
+
+solutions: |
+  No action required.
+
+versions: |
+  > 2022.1.0

psychopy/alerts/alertsCatalogue/4405.yaml

@@ -0,0 +1,24 @@
+
+code: 4405
+cat: Conflicts
+msg: Editable textbox component {textbox} and keyboard component {keyboard} in the same routine may compete for keypresses
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Textbox and keyboard conflict
+
+synopsis: |
+  As editable Textbox components and Keyboard components both listen for key presses, the two can often come into
+  conflict and cause problems.
+
+details: |
+  As editable Textbox components and Keyboard components both listen for key presses, the two can often come into
+  conflict and cause problems. For example, if a Keyboard component is listening for `Enter` to end the routine, what
+  happens when the participant presses `Enter` to start a new line?
+
+solutions: |
+  In general, we recommend ending routines containing editable textboxes using a Button, Mouse or ROI component rather than
+  Keyboard. If you are trying to gather keyboard responses as well as text input, consider splitting the two into
+  separate routines to avoid conflicts.
+
+versions: |
+  > 2020.1.0

psychopy/alerts/alertsCatalogue/4505.yaml

@@ -0,0 +1,22 @@
+
+code: 4505
+cat: Eyetracking
+msg: Experiment includes components or routines which use eyetracking, but no eye tracker is configured.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Eyetracking not configured
+
+synopsis: |
+  Experiment includes components or routines which use eyetracking, but no eye tracker is configured.
+
+details: |
+  In order for an Eyetracker Record, Eyetracker Calibrate or Eyetracker Validate routine to work, there needs to be an
+  eyetracker set up in Experiment Settings.
+
+solutions: |
+  Either remove any eyetracking components and routines from the experiment flow or set up an eyetracker in the
+  Eyetracker tab of Experiment Settings. If you are testing an eye tracking experiment but do not have an eye tracker
+  connected, you can use MouseGaze to simulate eye movements with the mouse.
+
+versions: |
+  >2021.2

psychopy/alerts/alertsCatalogue/4510.yaml

@@ -0,0 +1,25 @@
+
+code: 4510
+cat: Eyetracking
+msg: A {eyetracker} eye tracker has been configured, but no calibration routine is present.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Eyetracker not calibrated
+
+synopsis: |
+  The experiment is set up to use an eye tracker, but there is no calibration routine in the experiment flow.
+
+details: |
+  In order to get accurate readings, an eye tracker needs to know what points on the screen correspond to what eye
+  movements. It learns this during a "calibration" routine - in which the participant looks at different points on the
+  screen whose positions are known to the eye tracker. While an eyetracker can sometimes guess, readings will be much
+  more accurate if the eyetracker has been calibrated.
+
+solutions: |
+  Either set the `Eyetracker` setting in `Experiment Settings` to be `None` (no eye tracking) or `MouseGaze` (use the
+  mouse as if it were an eye tracker) so that no calibration is needed, or add a calibration routine to the experiment
+  flow. You can find the button to create a calibration routine in the Eyetracking section of the Components panel and
+  can add it to the flow via the Add Routine button.
+
+versions: |
+  >2021.2

psychopy/alerts/alertsCatalogue/4520.yaml

@@ -0,0 +1,26 @@
+
+code: 4520
+cat: Eyetracking
+msg: As {brand} eyetrackers do not support animations in their calibration routine, animation
+  values have not been used in your calibration routine.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Animation params not used
+
+synopsis: |
+  Some eyetrackers do not support animations between target stimuli in their calibration routine, so although you
+  have enabled animation in your calibration routine, due to the limitations of the eyetracker you are using any
+  settings for animation will not be used.
+
+details: |
+
+
+solutions: |
+  If you are only using the current eyetracker to test an experiment and will be using one which supports target
+  animations, then you don't need to do anything. This alert will stop appearing when you use the other
+  eyetracker.
+
+  Otherwise, you just need to be aware that the settings you've specified for animation will not have any effect.
+
+versions: |
+  > 2021.2.0

psychopy/alerts/alertsCatalogue/4530.yaml

@@ -0,0 +1,23 @@
+
+code: 4530
+cat: Eyetracking
+msg: Eyetrackers by {brand} do not support manual pacing
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Auto pace param not used
+
+synopsis: |
+  Some eyetrackers do not support manual pacing for calibration, as pacing is always handled automatically. If you have
+  set "Auto-Pacing" to False while using one of these eyetrackers, this setting will be ignored.
+
+details: |
+
+
+solutions: |
+  If you are only using the current eyetracker to test an experiment and will be using one which supports manual pacing,
+  then you don't need to do anything. This alert will stop appearing when you use the other eyetracker.
+
+  Otherwise, you just need to be aware that pacing will be automatic.
+
+versions: |
+  > 2021.2.0