![]() ![]() However, building a Carbon Skimmer works just as well. The pipe always gets precedence over the source.Īny source can push packets through an "orphaned" pipe (one that has lost its source), but the bridge is one of the most popular sources for draining a pipe section, because it's fairly cheap to build. Unlike pipe-based merges, the merging is *not* "fair". Just like pure pipe-based merges, a source can "top up" the pipe flow passing by it. They can "exit the source" if the pipe section connected to the source is empty or has a partial packet of the same element. Packets will exit the source if they can, and block if they cannot. If a shut-off is disabled, it will stop accepting packets.you get the idea. ![]() If a reservoir is full, it will stop accepting packets, causing overflow on the input. This will cause packets to overflow onto the input pipe. Since the bridge is a static building, the only time its sink cannot accept a packet is if the downstream pipe is blocked. Packets will enter the sink if they can, and continue on the pipe if they cannot. This is D above, and works exactly the same if you replace the bridge with a shut-off, valve, reservoir, etc. Every 3rd merge, both packets will merge cleanly, and the source lines will have an average flow velocity of 0.75 m/s. If you have two lines sending 750 g/s of H2 into a merged line, they will do a "partial merge" where one source will get to send a whole packet, and the other will get to "fill" the packet with 250 g/s, then they will swap. The average flow velocity of the source lines will be 0.5 m/s. Also, the animation shows this behavior clearly. You can confirm by checking the output temps, if the inputs are different. If you have two lines sending 10 kg/s of H2O into a merged line, they will alternate, because even though both sources are H2O, the sink line can still only handle 10 kg/s. *However*, if they are sending the same element, then the flows can merge completely, with no blocking in any segment, as long as there is sufficient pipe capacity.įor instance, if you have two pumps sending 500 g/s of O2 into a merged line, they will merge "cleanly" into a single 1000 g/s stream to the sink, with no blocking. If the sources send different elements, then the packets are always forced to alternate. Packets are "fairly" alternated onto the sink line, conversely to 4 above. This is the E/F case above, and works the same with or without the bridge. The split never divides a packet and sends half down both sides. ![]() In each case, the entire packet only goes down one branch or the other. That is, even if the flow is sporadic, each packet will alternate between top and bottom, which is equivalent to the split pipe "remembering" which output it sent the last packet on, no matter how long ago. Packets are switched between each sink in a "fair" alternation, regardless of flow rate. This is the A case above, but works the same with or without the bridge. Packets flow from source to sink at 1 m/s, if present. Source connected to sink on isolated pipe segment: the trivial case. And sometimes you need to stop the flow just to get at the bad packet. Most folks have "deconstruct" on a higher priority than "plumbing", so deleting a pipe segment will usually happen faster than clearing out the bad packet on the fly. Very useful if you need to stop a "bad" packet from damaging some equipment. Packets just sit in the pipe because they don't know where to go. But, for completeness, I'll cover all the cases: More importantly, the interesting behavior does not happen when a source or sink occur in a single isolated segment. And *all* sources and sinks exhibit this behavior, whether they are on a bridge, a shutoff, a refinery, a pump, etc. The green outlet box is a "source", and the white inlet box is a "sink". The key to understand is that this behavior is not about *bridges*. I was going to write a post on this topic, but since you already started one, I'll make a few comments here. Technically, the bridges in A and F are completely redundant, and you should get exactly the same split/merge behavior if you take them out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |