Pyinstaller fails to execute because the game-win.spec is missing

C:\Users\myusername\Desktop\asteroid_impact_source_code>pyinstaller.exe game-win.spec --noconfirm
108 INFO: PyInstaller: 3.2.1
108 INFO: Python: 2.7.11
109 INFO: Platform: Windows-10-10.0.15019
112 INFO: UPX is not available.
Traceback (most recent call last):
  File "C:\Program Files\Python27\Scripts\pyinstaller-script.py", line 11, in <module>
    load_entry_point('PyInstaller==3.2.1', 'console_scripts', 'pyinstaller')()
  File "c:\program files\python27\lib\site-packages\PyInstaller\__main__.py", line 90, in run
    run_build(pyi_config, spec_file, **vars(args))
  File "c:\program files\python27\lib\site-packages\PyInstaller\__main__.py", line 46, in run_build
    PyInstaller.building.build_main.main(pyi_config, spec_file, **kwargs)
  File "c:\program files\python27\lib\site-packages\PyInstaller\building\build_main.py", line 788, in main
    build(specfile, kw.get('distpath'), kw.get('workpath'), kw.get('clean_build'))
  File "c:\program files\python27\lib\site-packages\PyInstaller\building\build_main.py", line 732, in build
    with open(spec, 'r') as f:
IOError: [Errno 2] No such file or directory: 'game-win.spec'

The parallel port feature only works with Windows operating systems and was never developed to work with Mac or Linux.

TTL triggers connected with a USB or serial port experience a small latency depending on hardware. See the "Trigger Latency" section in the HTLM documentation for more details on how to test for this on your hardware.

The visual and auditory reaction time prompts experience a small latency and this is hardware dependent. See the "Game Timing" section in the HTML documentation for more details on this latency and how to test this on your own hardware. Note, this is true of all reaction time software, and Asteroid Impact's latencies seem similar to other major experimental packages (see e.g., http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0067769). Still, it is recommended that users do their own testing on their own systems to validate the software.

Asteroid Impact does not work in macOS 10.12. Unsure what dependency is broken. Needs further investigation. If you are a Mac user, wish to use Asteroid Impact, and do not want to troubleshoot this issue, do not upgrade your software to macOS 10.12.

When using OS X 10.10.5, the "total_millis" column in the .csv output does not tick correctly (not ticking every 16ms). This is due to a known limitation in PyGame 1.9.1 and we currently do not see a workaround for this issue. To our knowledge, the log records all game events, it is just that clock is not recording the timings correctly.

On Windows systems, depending on hardware and the way your .json script is configured, you may experience issues where the timing does not tick for the standard 16ms. This usually happens on a game state change (e.g., from instructions to gameplay), and only happens once. All subsequent timing ticks are 16 ms. As far as we can tell, the overall clock is still correct, so the timing files should still be accurate. However, for users who truly require 16ms precision, we recommend additional validation.