Hey Jiannan, great question—since the Pedestrian Library is built specifically for pedestrians, that 0-10 m/s speed cap makes total sense, but it's totally fixable when you're repurposing it for vehicles like you are. Let's break down your options:

1. Directly Modify the Pedestrian Agent's Speed Parameter Range #

If you have access to the Pedestrian Library's source (which you do with most commercial AnyLogic licenses), you can permanently adjust the speed limit for all pedestrian agents in your model:

• Open the Project Explorer pane, navigate to Libraries > Pedestrian Library > Agents > PedestrianAgent.
• Find the comfortableSpeed parameter (usually under the agent's "Parameters" section).
• Edit its value range from [0, 10] to something larger that covers your needs—like [0, 50] to easily handle highway speeds.
• Save the changes, and you'll be able to set 19.44 m/s (which converts to 70 km/h) directly in the parameter without errors.

2. Bypass the Limit with Code (No Library Edits Needed) #

If you don't want to tweak the library itself, you can override the speed programmatically in your model:

• Instead of relying on the comfortableSpeed parameter to control movement, use the setSpeed() method directly in your agent's behavior. For example, add this code to your pedestrian agent's onStartup event:

  setSpeed(19.44); // 70 km/h converted to m/s
  

• If you still want to use the comfortableSpeed logic (like having the agent vary speed around that value), you can reset the parameter's range at runtime. Add this to your main agent's onStartup event:

  // Replace "VehicleAgent" with your actual pedestrian agent type name
  VehicleAgent.comfortableSpeed.setRange(0, 50);
  

  Then you can set comfortableSpeed to 19.44 without hitting the error.

3. Consider Switching to the Vehicle Library (Optional) #

Quick side note: AnyLogic has a dedicated Vehicle Library built for simulating cars, trucks, etc.—it includes lane management, traffic signals, and built-in speed handling that's way more aligned with vehicle behavior. If your simulation doesn't require pedestrian-specific logic, switching might save you from workarounds like this. But if you have a specific reason to stick with the Pedestrian Library, the above two methods work perfectly.

Hope that gets you up and running with your 70 km/h agents!

内容的提问来源于stack exchange，提问作者Jiannan