psychopy 2024.1.0__py3-none-any.whl

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/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

psychopy/alerts/alertsCatalogue/4540.yaml

@@ -0,0 +1,19 @@
+
+code: 4540
+cat: Eyetracking
+msg: Window mode is set to be windowed, but eyetracking requires the window to be full screen.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Eyetracking requires window to be fullscreen
+
+synopsis: |
+  Eyetracking requires the expriment window to be fullscreen, otherwise the coordinates returned by the eyetracker won't line up with the coordinates of stimuli within your experiment
+
+details: |
+
+
+solutions: |
+  In Experiment Settings, make sure that "Full-screen window" is checked.
+
+versions: |
+  > 2021.2.0

psychopy/alerts/alertsCatalogue/4545.yaml

@@ -0,0 +1,22 @@
+
+code: 4545
+cat: Eyetracking
+msg: A monitor config is required for accurate eyetracking measurements, but none was found.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Eyetracking requires a monitor config
+
+synopsis: |
+  In order for eyetracking measurements to be accurate, the eyetracker needs to know about the monitor you are using -
+  how wide is it? How tall? What is its resolution? This is so that it can translate eye movements (in degrees of visual
+  angle) into usable data (in height, pix, etc. units). Without this information, the eyetracker can only guess and will
+  therefore give only approximate data.
+
+details: |
+
+
+solutions: |
+  Using the Monitor Centre, configure your monitor settings.
+
+versions: |
+  > 2021.2.0

psychopy/alerts/alertsCatalogue/4550.yaml

@@ -0,0 +1,19 @@
+
+code: 4550
+cat: Eyetracking
+msg: Eye tracker experiments should use 'ioHub' as the Input -> Keyboard Backend setting
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Input -> Keyboard Backend not set to 'ioHub'
+
+synopsis: |
+  Experiment is configured to use an eye tracker but Input -> Keyboard Backend experiment setting is set to 'PsychToolbox'.
+
+details: |
+  Eye trackers run using ioHub, which also handles Keyboard events, so Input -> Keyboard Backend experiment setting should be 'ioHub'.
+
+solutions: |
+  Switch the Input -> Keyboard Backend experiment setting to use 'ioHub'
+
+versions: |
+  >=2022.1

psychopy/alerts/alertsCatalogue/4605.yaml

@@ -0,0 +1,22 @@
+
+code: 4605
+cat: Audio Transcription
+msg: Audio transcription service "{transcriber}" is not supported online.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Transcription service not compatible online
+
+synopsis: |
+  Some audio transcription services can only be run online, some can only be run locally and some can be run either way.
+
+  If you are receiving this alert, it means that the audio transcription service you selected is one which either only works
+  locally, but you are trying to run your experiment online, or it is not supported at all.
+
+details: |
+
+
+solutions: |
+  To silence this alert, choose a transcription service which can be run online, such as Google or Azure.
+
+versions: |
+  >2021.2.0

psychopy/alerts/alertsCatalogue/4610.yaml

@@ -0,0 +1,22 @@
+
+code: 4610
+cat: Audio Transcription
+msg: Audio transcription service "{transcriber}" is not supported offline.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Transcription service not compatible locally
+
+synopsis: |
+  Some audio transcription services can only be run online, some can only be run locally and some can be run either way.
+
+  If you are receiving this alert, it means that the audio transcription service you selected is one which only works
+  online, but you are trying to run your experiment locally, or it is not supported at all.
+
+details: |
+
+
+solutions: |
+  To silence this alert, choose a transcription service which can be run online, such as the built-in transcriber.
+
+versions: |
+  >2021.2.0

psychopy/alerts/alertsCatalogue/4615.yaml

@@ -0,0 +1,19 @@
+
+code: 4615
+cat: Audio Transcription
+msg: Chosen transcriber '{engine}' requires an API key, please supply one in Preferences.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: API key not found
+
+synopsis: |
+  If you're receiving this alert, it means you have selected an audio transcriber which requires an API key to function but have not supplied an API key in preferences.
+
+details: |
+  Some audio transcribers work fine without a key, they're just a publicly available Python or JavaScript function which runs using your own computer's processing power, but others use algorithms which are either confidential or require huge amounts of processing power. This means that they need to be run on a server, often one which you've paid to access. If you have such a subscription, then your chosen transcription service will have provided you with an "API key" - this is a unique code, like a password, which tells their server who you are. If you are using such a transcription service within PsychoPy, then PsychoPy needs to be able to use your API key to request transcription.
+
+solutions: |
+  In PsychoPy, go to File -> Preferences -> General. Here you will find some preferences starting with `transcrKey` - in the one matching your choice of transcription service, copy and paste the API key you were given when you subscribed to that service.
+
+versions: |
+  > 2021.2.0

psychopy/alerts/alertsCatalogue/4705.yaml

@@ -0,0 +1,19 @@
+
+code: 4705
+cat: Loops
+msg: Column name '{param}' in conditions file already exists as a variable in this experiment ({category}).
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Column name from conditions file clashes with variable name
+
+synopsis: |
+  The name of a column in your conditions file already exists in this experiment.
+
+details: |
+  The name of a column in your conditions file already exists in this experiment. This means that either the existing variable will be overwritten by the value of this parameter, or that this parameter will be overwritten by the existing variable.
+
+solutions: |
+  Please choose a different column name.
+
+versions: |
+  All

psychopy/alerts/alertsCatalogue/4710.yaml

@@ -0,0 +1,19 @@
+
+code: 4710
+cat: Loops
+msg: Column name '{param}' is likely to cause name clashes. {msg}.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Column name from conditions file likely to clash with derived variable names
+
+synopsis: |
+  The name of a column in your conditions file already exists in this experiment.
+
+details: |
+  The name of a column in your conditions file already exists in this experiment. This means that either the existing variable will be overwritten by the value of this parameter, or that this parameter will be overwritten by the existing variable.
+
+solutions: |
+  Please choose a different column name.
+
+versions: |
+  All

psychopy/alerts/alertsCatalogue/5055.yaml

@@ -0,0 +1,25 @@
+
+code: 5055
+cat: Parameters not used online
+msg: Device parameter of microphone component "{name}" will not be used online.
+
+# The following are typically used for online help pages, and support reStructured Text.
+label: Microphone device not applicable online
+
+synopsis: |
+  A non-default value was given for the "device" parameter of a microphone component, this will not be used when running
+  online.
+
+details: |
+  When running experiments locally, it is useful to define a specific device for a Microphone component. For example,
+  you may want to plug in a microphone to your laptop and tell PsychoPy to use that microphone rather than the one
+  built into your laptop. For this reason, you can specify a device for a Microphone component.
+
+  However, when running online, we cannot be sure what microphone devices the participant will have connected. As such,
+  the device parameter does not apply to online experiments and will not be used online.
+
+solutions: |
+  No action needed. To silence this alert, set the device parameter of the Microphone component to be "default".
+
+versions: |
+  > 2021.2.0

psychopy/alerts/alertsCatalogue/6105.yaml

@@ -0,0 +1,18 @@
+
+code: 6105
+cat: Run nonexistent file
+msg: The file you are attempting to run does not seem to exist, the full path supplied to Runner was {path}
+
+label: Attempted to run file which does not exist...
+
+synopsis: |
+  It looks as though you tried to run a file which PsychoPy cannot find.
+
+details: |
+  When PsychoPy went looking for the file you just tried to run, it could not find it. It may have been moved or deleted from outside of PsychoPy, or it may be that PsychoPy has the correct file name but incorrect file location.
+
+solutions: |
+  Using your file browser, check that the file path in the alert message does indeed lead to the file you are trying to run. If the containing folder exists but the file does not, then the file has most likely been moved, renamed or deleted from outside of PsychoPy. If the containing folder does not exist at all, then PsychoPy may have the wrong path atogether. In either case, the easiest remedy is usually just to find the file manually and open it again in PsychoPy. If you are trying to run a newly created file, use Save As... to save the file and then try running it again. If it still cannot be found, then you may have hit upon an error in how PsychoPy searches for files, please report this `as an Issue on GitHub <https://github.com/psychopy/psychopy/issues>`_.
+
+versions: |
+  All versions.