Run your simulation with SimSpace Weaver Local - AWS SimSpace Weaver

End of support notice: On May 20, 2026, AWS will end support for AWS SimSpace Weaver. After May 20, 2026, you will no longer be able to access the SimSpace Weaver console or SimSpace Weaver resources. For more information, see AWS SimSpace Weaver end of support.

Run your simulation with SimSpace Weaver Local

You can use SimSpace Weaver Local to run any combination of up to 24 spatial or custom apps on your local computer. The simulation clock starts after all spatial apps defined in the schema start.

To run your apps with SimSpace Weaver Local

  1. In a file chooser window, go to project-folder\buildlocal\out\RelWithDebInfo.

  2. SimSpace Weaver Local apps require a schema file named schema.yaml in the working directory of the apps. Any failure to read the required information from the schema terminates the apps.

    The schema for SimSpace Weaver Local doesn't have to be identical to project-folder\tools\project-name-schema.yaml, but you can use it as a starting point.

    Choose one of the following:

    • Copy that schema to project-folder\buildlocal\out\RelWithDebInfo\schema.yaml.

    • Set the environment variable WEAVERLOCAL_SCHEMA_PATH to the name of a schema file with a different path or file name.

      Example
      set WEAVERLOCAL_SCHEMA_PATH=c:\projects\MyProject\tools\MyProject-schema.yaml
      Note

      If you set your environment variable from the command line, that environment variable (with that value) is only accessible from that command prompt session (console window).

  3. The schema for the sample application defines a 2x2 grid, which creates 4 partitions. You will run a script that will launch 4 instances of the spatial app, to match the number of spatial apps specified in the schema. The script will also launch 1 view app. After all spatial apps launch and are assigned a partition, the simulation will automatically start ticking.

    To launch your apps

    1. At a command prompt, go to the local tools folder for your project.

      cd project-folder\tools\local

    2. Run the script to launch the apps.

      launch_simulation_locally.bat
      Note

      If you set WEAVERLOCAL_SCHEMA_PATH to the name of a schema file, you must start your spatial apps at the command line in the same session (window) that you set the environment variable.

      Important

      If you get a Windows security pop-up, choose Allow Access so that you can connect to the view app to visualize the simulation.

      Note

      You can also start your spatial and view apps manually. To do so, you must manually launch 4 instances of the spatial app and one view app.

      • Spatial app: start PathfindingSampleLocalSpatial.exe

      • View app: start PathfindingSampleLocalView.exe