AnyLogic模型求助：如何通过数据库为MoveTo模块获取订单目标工位？

Hey there! Let's work through your AnyLogic manufacturing model problems step by step—this is a super common scenario when dealing with dynamic agents and Excel imports, so you’re already heading in the right direction.

1. Creating WP Agents from Excel (Populating the wps Population) #

First, let’s make sure you’re setting up your workstation agents correctly from the Excel data:

• Step 1: Confirm you’ve created a WP agent type (with fields like name, and any other parameters you need).
• Step 2: Add a Population component to your main module, name it wps (this is critical—this population will hold all your dynamic workstations).
• Step 3: In your main module’s On startup event, add code to import Excel data and create WP agents:

  // Assume your database table is named "Workstations" with columns: name, param1, param2
  List<Record> workstationData = selectFrom(Workstations).list();
  
  for (Record rec : workstationData) {
      WP newWorkstation = add_wps(); // Auto-generated method to add to the wps population
      newWorkstation.name = rec.get(Workstations.name);
      newWorkstation.param1 = rec.get(Workstations.param1);
      // Assign other parameters from the Excel record here
  }
  

  This will dynamically create all your workstations at simulation start and store them in the wps population.

2. Fixing the MoveTo Target Matching Issue #

Your earlier error likely came from two key issues: using == to compare strings (use equals() instead) and not properly accessing the global wps population. Here’s how to fix it:

Option A: Directly in the MoveTo Block #

Set the MoveTo block’s Target type to Agent, then in the Agent field, use this code:

findFirst(wps, wp -> wp.name.equals(agent.routing.get(agent.currentRouteIndex)))

• Replace currentRouteIndex with a variable in your order agent that tracks which step in the routing sequence you’re on (increment it after each move!).
• Use equals() for string comparison—== checks object reference, not actual text content, which is why your previous code couldn’t find matches.

Option B: Add a Helper Method to the order Agent #

If you prefer cleaner code in the MoveTo block, add this method to your order agent:

public WP getNextWorkstation() {
    // Assume routing is a List<String> holding workstation names in order
    String nextStationName = routing.get(currentRouteIndex);
    WP target = findFirst(wps, wp -> wp.name.equals(nextStationName));
    
    // Increment index to move to the next station in the sequence
    currentRouteIndex++;
    return target;
}

Then in the MoveTo block’s Agent field, just call:

agent.getNextWorkstation()

3. Do You Need AgentLink? #

Short answer: No, not for this specific task. AgentLink is great for establishing persistent relationships between agents (e.g., tracking which workstation an order is assigned to long-term), but for just finding the next target workstation, using findFirst() on the global wps population is simpler and more efficient.

Quick Debugging Tips #

• Verify your wps population is populated: Add traceln("Total workstations: " + wps.size()); to the end of your On startup event to confirm the count matches your Excel data.
• Check for string mismatches: Ensure the workstation names in your order routing list exactly match the names imported from Excel (no extra spaces, correct capitalization).

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