Bubble Can Fail to have Any Hijacked Vehicles

[Gamenot]

The current implementation of Bubble class limits the number of newly hijacked vehicles to all the vehicles in both airlock and the bubble proper.

While this is useful for performance reasons, it is not particularly intuitive since vehicles can just sit in the airlock and not contribute to the simulation.

See:

SMARTS/smarts/core/bubble_manager.py

Lines 135 to 153 in fe7bd75

	if self._limit is not None:
	# Already hijacked (according to VehicleIndex) + to be hijacked (running cursors)
	current_hijacked_or_shadowed_vehicle_ids = {
	v_id
	for v_id in vehicle_ids_in_bubbles[self]
	if index.vehicle_is_hijacked(v_id) or index.vehicle_is_shadowed(v_id)
	}
	per_bubble_veh_ids = BubbleManager.vehicle_ids_per_bubble(
	frozenset(running_cursors)
	)
	running_hijacked_or_shadowed_vehicle_ids = per_bubble_veh_ids[self]
	all_hijacked_or_shadowed_vehicle_ids = (
	current_hijacked_or_shadowed_vehicle_ids
	| running_hijacked_or_shadowed_vehicle_ids
	) - {vehicle_id}
	if len(all_hijacked_or_shadowed_vehicle_ids) >= self._limit:
	return False

AC:

• Bubble limit applies to the current number of unreleased vehicles the bubble has currently captured.
• Bubble tries to have the given number of agents hijacked.