如何在AnyLogic中自定义PedWait吸引子选择并关联社交距离控制实现行人按规则就座

Hey there! I’ve worked with similar pedestrian seating logic before, so let’s walk through how to implement this step by step:

1. First, Define Your Social Distance to Seat Mapping #

Start by creating a clear mapping that links each social distance value to its allowed seat IDs. You can store this as a key-value structure (like a dictionary in most scripting languages) for easy lookup:

# Example mapping (adjust syntax to your project's scripting language)
social_distance_seats = {
    1.0: [1, 3, 5, 7, 9],
    1.5: [1, 4, 7, 10],
    2.0: [1, 5, 8]
}

This makes it super easy to fetch the correct seat list whenever the social distance changes.

2. Modify PedWait's Attractor Selection Logic #

In your PedWait component, you’ll need to override or extend the default logic that selects which attractors (seats) are available to pedestrians. Here’s how to approach it:

• Locate the function in PedWait that retrieves available attractors (usually something like getAvailableAttractors() or selectTargetSeat()).
• Add a filter step that checks the current social distance value from your EditBox, grabs the corresponding seat list from your mapping, and only keeps those attractors whose IDs match the list.
• Make sure to handle edge cases (like if the EditBox has an invalid value) — you could default to a safe set of seats (e.g., all seats) or show a warning.

For example, if you’re using C#:

public List<Attractor> GetFilteredAttractors()
{
    // Get current value from your EditBox
    float currentSocialDistance = float.Parse(yourEditBox.text);
    // Get allowed seat IDs from the mapping
    if (!socialDistanceSeats.TryGetValue(currentSocialDistance, out List<int> allowedSeats))
    {
        // Fallback if value is invalid
        return GetAllAttractors();
    }
    // Filter attractors to only those in allowedSeats
    return GetAllAttractors().Where(attractor => allowedSeats.Contains(attractor.ID)).ToList();
}

3. Link the EditBox to Trigger Attractor Updates #

You need to make sure that when the user changes the value in the EditBox, PedWait immediately updates the available attractors. Here’s how:

• Add an OnValueChanged listener to your EditBox component.
• When the value changes, call a method in PedWait that refreshes the filtered attractors.
• If there are already pedestrians waiting, you might want to trigger a re-selection for them (depending on your project’s requirements) — just loop through waiting pedestrians and have them re-evaluate their target seat.

4. Test and Validate #

• Start by testing each social distance value individually: set the EditBox to 1.0, spawn pedestrians, and confirm only seats 1,3,5,7,9 are used.
• Test dynamic switching: change the EditBox value while pedestrians are waiting or seated (if your logic allows re-seating) to ensure the seat list updates correctly.
• Check for edge cases: what if the EditBox has a non-numeric value? Or a distance you haven’t configured? Make sure your fallback logic works as expected.

That should cover all the core parts of implementing your custom seating rules! Let me know if you need help with specific syntax or component details in your setup.

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