Train Interrupt Condition for "Trains with this stop"

[bkrauscs]

TLDR

It would be cool if an interrupt condition could be used to control the number of trains with a route on a particular station. This would allow trains to reserve a route for themselves, keeping the number of trains responding to an interrupt to a reasonable amount.

Motivation

I've been diving deep into the new train interrupt system which has been getting the gears in my mind turning. What I'm trying to build is a group of trains that can address any needs in my factory without any being specifically allocated to a particular route. What I have is ~15 (for now) trains in the same group with a schedule that is only go to Depot and wait 30 seconds. Then, for my factories, each consumer station can emit a signal to a circuit network for the type of item it is requesting if it is low. I have interrupts on those signals, which will task a waiting train to get a resource from a producer and supply it to the requesting consumer.

The problem: If there are 15 bored trains waiting in the Depot, and a consumer of Iron Plates sends a signal, then 15 trains will go to the Iron Plate supply and load up, then wait because the consumer has a train limit of 1 and one of the other bunch has gotten there first. This blocks the producer from serving other trains. I also don't need all 15 to go help, just 1 will do.

What I've tried: I have set the train limit on the station to 1, but this causes other trains to wait in the prior station which blocks it. I can set the Depot as an intermediate stop between pickup and dropoff, but this means all routes will include a usually unnecessary pass through the depot, and if any wait there then they're tied up with resources they can't unload. I set the condition on the interrupt to not fire if there is a train at the consumer station, but when the signal is first sent that's not the case and all 15 can acquire the route.

What would be nice: If a condition for interrupts could be added to have a statement of "Trains with this stop" is > X given a stop. This allows me to control how many trains can claim a route, and would let me to service my factory with a very small number of trains using smart circuit signals. I think this seamlessly flows with the current interrupt logic, because once the request has been fulfilled the train no longer has the stop and the count of "Trains with this stop" goes down by 1 and if there is still a consumer need then either that train or another can start the interrupt over.

[sarge945]

This sounds like a bug/issue with the way train limits work, not something that should necessitate a new condition.

If a stop has a limit of 1, only 1 train should be dispatched to it in the first place.

[sarge945]

Okay, I think I may have solved this in some manner using Circuits.

Basically, you need a constant combinator for the train limit (which outputs the preset limit on L), then you need a decider combinator like this:

combinator.png (108.04 KiB) Viewed 1808 times

Where C is the "Read Train Count" variable of the station, L is the limit, and the Station icon is used to enable/disable the station.

Basically the way this works is that, the moment the number of trains with the station as their current destination (C) is greater than or equal to the train limit (L), it disables the station, so whenever a train wants to go there it should automatically prevent any future trains going there.

While I was there I also decided to limit the station to only being enabled when it actually has a worthwhile amount of resources to pick up as well, but this is optional.

This is at the SOURCE station (the pickup), not the destination station, although it would probably work for both

Here's a quick and dirty blueprint for it:

0eNqlW9tq6zgU/ZXgZ6foYusSOA/DMG9nGJjpWynBSdTW4EvGdjqnlPz7SHYcp613Iu1CaXRdktaWlpQt5T3aFAezb/Kqi1bv0c602ybfd3ldRavo/iVvF/YvqxbmV1buC7Nou8xlLg5tXj0vuhez2ObN9pB3i21d7XKXdxfFUW5jbbR6eI/a/LnKCoddZaWxoF2T5dWy7ep9dLQFq535Fa3o8TGOTNVZADPU6yNv6+pQbkxjC8Rj/dYBPL90S/tR2Kb2dZsP/X2PLJJI4+gtWi2Z1sdj/AWHxTP9+AoiJ5A4smPpmrpYb8xL9prXjSt0GvXaVNmmMLto1TUHE5+Tz2S4sk9503brG0Q4wrrMWYG6SLnPmqxzbUU/XHZrqt26q9d9pWj1lBWtba6PrR3E3uwuWuje9q6F17zpDpkjaeSuL7G8HxC7Aa1dF3mZd+MQLtP8IX86yMZkuxFzWx+qz5h9mj/m79HR9XOYcTY5csQUA//2H7kTTCYpJYSlWiqiFJdKE8HsDHi+nr25np25CTkzeXj4JJRzOMkZ5ylru6XFqtp93XTLjSm6GTR6d8ZL7lLLyS5vzHYoQdlMA2lgAyS0AfGxgYNdxc1zY827g5pgV5uIx7lQH7r9oYtmmpTh5Kdz5Kvgrku/rucV0HMdaA0Vag1KAlvQwS3Qjy20+yLvOpvzBTu9xPZBZvi5aufUnIUpx0NyPzqmFVyaXX4ol6awFZp8u9zXhbk+/aFeT4u2LbOiWBZ2x51B4reRRPhS4bNAMnSY8nbnpvW3M9vcLr6l3e02edXvdld2Yj639Oa25hPstAe3/YZ9EXsA92S365bGTuwl+bQpE0LcaD7Xu72FuZ3WNR64lw5HALM+lc2qXeTOSIM+eh2ttvX+7bTlPjV1uR70aTg6HB+Ps8bRfnNQ3DQzmyRpJPG6ndWVNZjMG7od8tuPYUvMeKiMrbkKa8zPqTf5j6N/bYYdj02s6qbsC306lLmE/ohjz64AnYzidRnileEhOQD5DbkkAGSCh6QA5KczjT1PmmZ2B7o8LtEvU2kOWmCgiRf05anFmGK5fTHtjeMRRIAKh4LMo70HzAMHzAkG2stMHPEdcP4YzzyZlDeNwnk4FGAUnngzJ64wN3te4SkGm/hhC7wiQVRIPCRkKOXNgApmQGOw/SyXELSSKjVPRULxkBqAZAgF7cFurvqEY6CVF3QSrKggp2k4FMSlQCio54AlBtrPTCpYnNWsgy7RwYoKGSUl4VCAUVKKENCvzM07axgGW/lhc7SSgqwmeEiI3RQhoL4MCAy2p+UkXkkFQIXCQ0oAUmMUVPqsekEw0MILmoYrKsCpYOFQAJeCYxTUb8AJBtrPTGm4OM86roUIV1TIKDIcCjKKwgio9HN0awy28MKWeLctxKrEexwgdiXDCKgnAxyD7Wc5ifdBqASgAn+volIAEuN7UInPqpfhvgdw4CrUNw2OV+M95xCmwvgc/DhU4T4HNd9HFupZBUfL8U55EDMJF2NgqiiMq0H53UIpvKsB7C7e1QCSiXE1+DKg8QoEeJT1NzwMgEdZU4yocZ8FqVGeBuYFzcP1EiIA4VmAzJNixM1vwChPg5+Zwm/r1ewVpFbhygQZBeFZgC4xCcGonOflMkE5G5gnOP4CCWbjG14GDmEmGBX1JQHlcPA1n8ALKoHY+IangUKYCiOlXlc1lKB8Dl43TJSScHGFeKUILwPEJ2UYOfUcM8rv4GcrmoRrNZ1nIA1XWJBNhKsBtLLECCr1fBmF8j4QT3CNV1aIDfYNtwNkLUYxgupJAkN5IDzN943XD1JDbCQI9ZNe9yz04h1E8BdoqaAOi2AZhAcvQ30FcLcUQvV8edTBqif1/GtDgv9CDg798rGDn78Ahgp/7gAal3OE2Em/2xTK8TdLcIcxJ73ZDj/G0X82wb0le2Axje2mQh/jB7t7pi6cjmGph7B0ZdRQ5hTmY9hK8DndmucUTmPFh7pqKs/68gOO+4iTtA+7arE1Rx+2H3E6YCbJVKYPiwE/0RdlXFgM/Rd0KtOH5SldXJRxYZX0YZcd66FdN9Sxz33YqZOLuLTYLYw+4nqhhxG4irEekNxH7E5gfcQNzX5D68O6zxjG4I57U7FTzOrVEEv7vDHmuklHPll6WXKIcXKOTf3rU0/1rJHPT0CHV4Pj4+7d9Ezwr8Ys7l1y7JI/Pho9vxxcfvgJyO3nhP3sPTV2mr3xGFhF7vnp1IE/8yovD+Xib9PWh2ZrFr+V/VPE6xBT/Xv3TnTxs//Vh5vXeWdKmzz9EiiOisyuOZv2z+n3Pn8Mv/+xOa+WmX5UqWA60TrlOkkFsSfC/wHtbasu

Copy blueprint

My train network is still relatively small, I had to start a new run for 2.0, but I haven't run into any problems so far using a generic station name like "Item Pickup" for every resource, and interrupts for dropping everything off.

Despite all this, I still feel like train limit should also affect incoming trains as well, so no more trains than the maximum train limit should be able to have the station as a stop at the same time.

For reference, here's my interrupt as well

10-24-2024, 02-37-18.png (42.16 KiB) Viewed 1807 times

[bkrauscs]

I'm shooting for a slightly different setup, the merits of which are debatable. I'd like trains to only be in motion if a factory is requesting goods. My interrupt setup (example below) has the conditions that a request for iron ore is on the circuit network, along with the station identifier (0). The other two conditions are guards against showing up somewhere with the wrong stuff. Then, the targets include where to get the items and where to drop it off.

10-23-2024, 17-38-44.png (546.34 KiB) Viewed 1753 times

Since the measure of "Read train count" is how many trains are going to the station it doesn't do well to block the interrupt on that count since any trains that pick up the interrupt schedule are going to the source first which won't show up in that number. If I block trains to go to the source from the "Read train count" of the source or destination, then I'm limiting the provider (in this example an iron mine) from serving other destinations.

This picture better describes the situation:

10-23-2024, 17-52-53.png (181.68 KiB) Viewed 1753 times

There is a train limit of 1, which is adhered to, but the Trains with this stop is at 2 and that's what I'm trying to control. The 2nd train is sitting in the iron pickup waiting for this station to be clear, stopping other trains from using the pickup station. I'd rather not have a 2nd train to begin with.

[bkrauscs]

Actually, thinking about this for an evening I might have it sorted out. It's pretty much what Sarge suggested combined with the FFF posts about the train interrupts using generic filters. The basic method is that consumers emit a 1 signal for the type they need (when stock is low) and producer stops of that type are disabled unless the total number of requests on the network for their produced type is > # trains going to that particular stop (with the separate train limit set to, say, 2).

Say I have a factory that produces iron plates with 2 stops that can load them into trains. If a request comes in for 1 train of iron, then all stops at the producer become enabled. When the first idle train sets a path to the load stop, then all other stops are disabled since all stops at the factory are wired together and share train counts. If another request comes in while the first train is loading, then 2 requests > 1 at the factory, and the 2nd stop becomes enabled again, and so on. When the first train leaves the station after loading, the consumer will subtract the number of trains going to it's stop from the number of requests being emitted, causing the request to be satisfied (unless after offloading there's still low stock).

My interrupt schedule now looks like:

10-23-2024, 20-57-19.png (275.13 KiB) Viewed 1725 times

[falconfused]

I too want this feature. How do we elevate this?
Although I think it would be faster/easier to implement just being able to have train stops output that value on the circuit network. Like it works now with "Trains with this stop - C"

[Tomeamis]

I also think this feature would enable much better train management. Unfortunately, because if there are more trains which can both process that interrupt, they will both process it in the same tick, solutions with circuit network won't work, as they always take at least one tick to update the outputs.