I think a more optimal way to do piston extenders for n blocks is to use modular arithmetic. ([x mod y] is the remainder when x is divided by y, e.g. 35 mod 10 = 5) [these brackets aren't required, i just use them for clarity] basically, you push the first [n mod 12] blocks ([n mod 12] -> 1), then [12 + n mod 12], and repeat until you get to n. this is actually a generalization of @abugidaiguess's method for 13 pistons. If n mod 12 = 0 (i.e. n is divisible by 12), then it saves no extra steps. But otherwise, it saves exactly [n - (ceil(n / 12)) * (n mod 12)] over what is shown in the video! some examples: 13 pistons (video): 12 -> 1, 13 -> 1; 12 + 13 = 25 steps 13 pistons (modular): 1, 13 -> 1; 1 + 13 = 14 steps steps saved: 25 - 14 = 11 30 pistons (video): 12 -> 1, 24 -> 1, 30 -> 1; 12 + 24 + 30 = 66 steps 30 pistons (modular): 6 -> 1, 18 -> 1, 30 -> 1; 6 + 18 + 30 = 54 steps steps saved: 66 - 54 = 12 500 pistons (video): 12 -> 1, 24 -> 1, ..., 492 -> 1 (that's 12 * 41, btw), 500 -> 1; 12 * (1 + 2 + ... + 41) + 500 = 10832 steps 500 pistons (modular): 8 -> 1, 20 -> 1, 32 -> 1, ..., 488 -> 1, 500 -> 1; 8 * 42 + 12 * (1 + 2 + ... + 41) = 10668 steps saved: 10832 - 10668 = 164 (that's a lot!) btw I used a computer program to generate the number of steps for that last one, so it may not be 100% accurate!
nice, that makes sense! for all cases other than multiples of 12, this way of doing it produces a shorter sequence. funnily enough, this is actually what gets implemented in the redstone version! In game, I always forced the subsequences to line up with the back, because that way I can change the number of pistons without having to shift the redstone. notice how at 19:09 it starts with 4 -> 1 because its a 40 piston extender mind if I pin this comment? would be nice to share this info with everyone! and it could serve as a thread for more discussion about this in the replies
@@mattbatwings yeah that would be awesome! i'm totally fine with being pinned :) interesting that the redstone ends up producing the shorter sequence anyway. and i'm not much of a redstone guy, so those builds you make always blow my mind, even after all the explanations! also i just joined the discord server and it looks great ^^
@mattbatwings yeeeaaahh I fel smerter that Matt it took me like 1 sec to figure out this anyway I hope this little mistake didn't make this video feel less professional, since you could have made a program that tested all possibilities, knowing that there is a finite and small number of them for a 13-long extender. This way you could have seen that this method was more optimal. no worries though, you can't be the best at redstone computing and door making.
This is the second video I've seen on that, but the first I've actually watched and I have no idea what it is. (the other being mate in Omega, the chess one)
@@burningnetherite4206 Summit of Math Education is competiton to foster the creation math content online. Anyone could join competition until 19th August. Now you can't join as a participant but you can still join as a judge
The way you parallelized this is actually really similar to how CPUs are optimized. Cpus have several stages they have to do, and they used to have to every stage before the clock cycle. But modern cpus will only do one stage per clock cycle, but will run them all in parallel by starting a new instruction on each clock cycle.
For a 13 piston extender 1 , 13 -> 1 is more optimal than 12->1, 13->1. Further for a n-piston extender rather than iterating 12->1, 24->1 … n->1 you can simply do (n mod 12) -> 1, (n mod 12) + 12 -> 1, (n mod 12) + 24 -> 1 … n -> 1
@@profx33this method optimizes the number of piston extensions, however it can still be run in parallel so asymptotically it would take the same amount of time per extension as the method proposed in the video, simply with fewer extensions hence less time. Additionally the use of zero tick mechanics can be used to improve the time between piston firing.
13->1 does not move all the blocks. Remember there is iron (or some other block) in front and the index of a piston is equal to the number of blocks in front of it. Pistons can only push 12 blocks, so piston 13 can’t activate since it has 13 blocks in front of it.
I've gotta give you props for this. This is gotta be one of the most clear explanations I've seen. No crazy music; and straight to the point, and showing the steps behind each thought and conclusion. Subbed.
I feel like this is exactly the type of video that 3b1b loves to see with this SoME. I love how gaming communities can go together like this with the math community.
In the case of minecraft, all the people that are serious about redstone builds (talking about "technical" minecraft players) are on the smarter side of the gaming community and are not afraid of crunshing numbers and investing more time doing math about the game than actually playing it. I always like it, when I catch myself calculating growth of supplies, output of farms, speed of a vehicle, damage over time, and so on, in the middle of a gaming session 😅
Looked at the profile of the video creator just now, and in fact, it is not a math guy doing minecraft, but a minecraft guy doing math 😂 Technical player right there.
haha, the minecraft community (specifically the redstone community) is intertwined with the maths community. There's just too much overlap for it not to be the case.
For the record, short (1TP/0TP) pulses will also retract blocks, *if* the block was in the extended position when the pulse was produced - so can also be time-optimised in that way
My programmer brain has the same problem, but I guess you could see the iron block as position zero? Feels a bit wrong considering it doesn't do anything, but it's better than a list starting at 0
after finding that dispensers are a dynamical system I'm not surprised you've found some math surrounding piston extenders that warrants a whole math explanation vid, excited to see what you've put together and best of luck with your submission
(This comment was made before the premiere) My guess for the video is gonna be deriving an algorithm for finding the order in which pistons need to be fired to close/open an nth long piston extender That and/or deriving the correct timings to do such
@@austinclees9252extender designs are simpler than that, my prediction is that it's gonna be about the observer + 2tick-repeater design which is infinitely expandable and uses just a clock and a timer to get all the pulses, it's a really smart design because although the inputs are kinda intuitive, the piston sequence isn't but in the end it all somehow manages to work
EXTENSION PARALLELIZATION is exactly what GPU's do comparatively to CPU's ... and there are engineers called CUDA programmers their job is to find a way to parallelize chunks of repetitive codes in order to take advantage of the shear amount of cuda cores that can parallelize process data
for a 13 piston extender, you can just do 1, 13 → 1 saves 11 extensions, and should be fairly simple to generalise up until 24 at least edit: as a few replies have pointed out, it actually doesn't really matter which piston is extended first. i just happened to choose 1 in my head edit 2: wow okay so it turns out the method i thought of has since been generalised by the pinned commenter (who actually called it "@abugidaiguess's method"!) i honestly didn't put much thought into the comment beyond the specific case for a 13 piston extender, so i'm really glad other people did! :D
A detailed analysis of the optimal extension sequence: Consider the total cost of an n-extension. We can consider the total cost to move all required blocks 1 block forward, 2 blocks forward, 3 blocks forward etc. separately, because each extension pushes a subset of the pistons/block which have all currently been moved forward the same amount of times (i.e. it is impossible to simultaneously push two pistons that have moved a different number of times each, because there will be an air gap in between). The first set of blocks (that needs to be moved forward once) has size n, then the next set (that moves forward twice) n - 1, then n - 2 and so on until there is only 1 block that must be moved n times. The kth of these has size (n - k + 1) and requires ceil[(n - k + 1) / 12] extensions as each extension can only push at most 12 blocks. So the total cost is the sum from k=1 to n of ceil[(n - k + 1) / 12]. Notice, however, that this is equivalent to ceil[(n - 1 + 1) / 12] + cost(n - 1), that is, ceil(n / 12) + cost(n - 1), with cost(0) = 0. This can therefore be expressed as cost(n) = ceil(n/12) * (6 + n - 6*ceil(n/12)). Also note that this lower bound is achievable because we can simply do the process one step at a time, moving forward the first n-1 pistons in ceil(n/12) steps, then the next n-2 in ceil((n-1)/12), etc. The most interesting piston extender math (in my opinion) is that of "hipster" extenders, which are piston extenders that extend beyond the wiring itself. This means in order to power pistons beyond the wiring, movable power sources such as redstone blocks or observers must be extended and retracted themselves. This makes the analysis of the optimal sequence slightly more tricky. Every distance extended/retracted beyond the wiring requires recursively using the distances 1, 2 or 3 blocks before it one or more times (in order to extend and retract the power source, and move the piston back 1 block), leading to exponential growth in the length of the sequence.
Yes, what we care about most is the length of the sequence (not the actual sequence itself), so I defined the function cost(n) to be the length of an optimal n-extension.
Solution "may" not be optimal. It "may" be the case that somewhere in an optimal solution, a piston extension is used in both the moving of the 7th block and also the 10th which could make a better solution than the one you propose. I put "may" because I think you're right, but you didn't prove this "may" had to be wrong.
@@viktort9490No, this solution is rigorous. In fact, what you say is true (a piston extension IS used in the moving of both the 7th and 10th blocks) - the point is that it can be used to move BOTH those blocks if and only if they have moved the same amount of times so far, or there would be an air gap between and only the 10th block would be moved. This then leads to the independence of each distance moved and the rest of the proof.
So I had an idea at around 8:12, and that's that the 13 block extension could be done more simply than 12->1, 13->1. I believe that the sequence 12, 13, 12->1 would also work but with less repetition. Therefore, this disproves that the formula for sequences of individual extensions does not necessarily always give an optimal result. Edit: Well it's not something unique I've came up with, but it is still true so I'll take that. Great video as always
i was thinking the exact same thing and was like, someone else HAD to have thought of it already, right? i mean it's just so obvious! and you did, so thanks. :)
3Blue1Brown--Grant Sanderson is one of my most watched channels on youtube. You are an absolute legend for sharing with the world the wonders of Maths and Minecraft, Mattbatwings. Thank you for all that you do; this is incredible!
the formula does allow for an infinitely expandable and modular design to an extender though. using the most optimal number of pushes would require different extenders to have their own different redstone circuits.
@@Drawliphantyou don't need to push an expanded piston. You do a quick pulse with one of the first 12 pistons. It will push everything forward and not have time to pull it back. Then the gap created means 13 can now fire to fill that gap and then you can just go down the line.
Just found your channel through this video and Holy shit your videos have been the highlight of my week! Absolutely amazing videos that give me the same feeling as watching Ben Eater videos. Keep it up!
I'm not a redstone nerd, but I am a math nerd and I love doing random stuff in Minecraft. I liked this video a lot, such a creative entry to the contest!
The true infinite piston extender: A flying machine Edit: How did this get 600 likes? wow. If anything i thought i'd get criticised for dodging the video's topic
The proof for the Retracrion only needs a small addition to be valid for any number of blocks: -6 is proven to be ideal for a 3 piston retraction -any extra piston adds n (new number of pistons) block movements, because every block in the old chain (n-1 pistons + 1 block upfront) needs to move back one more block each -any extra piston adds n ( new number of pistons) retractions in this algorythm, becase n->1 is added at the end of it => the required block movements and the number of retractions start at the same number and rise by an equal amount for each itteration of n, therefore both numbers are equal for any given n Q.E.D.
@@anon1963First of all, higher level math is beautiful and not boring in its own right. Second, there are millions of applications of many, if not most, areas of math
As someone who studies advanced level mathematics and physics at school and also plays videogames like Minecraft for fun, i always considered gaming and my studies to be completely separate from each other and not at all connected. Gaming is always little more than a fun leisure activity whilst my studies in physics and maths is more important and mandatory schoolwork. However, watching this video has opened my eyes fact that there are likely many different connections between maths (and maybe even physics) and the games that i play.
@@czechmateyoulost1755 I mean A Level maths and physics. It's the qualifications you take at age 16 and 17 in the UK where you usually pick 3 or 4 subjects of your choice that you want to study before you use your grades in your subjects after the end of 2 years of study once you've done your final exams to enrol at university
There is a way to think about piston extenders which I would like to share! 1. Think about the blocks being moved to be air block, instead of pistons. 2. When an air block is in a certain location, movement on the two sides doesn't interfere with each other. 3. We can look at only a single air at a time, we can simply assume the movement in the back to happen first, until the air space is filled. 4. When extending, there are N air blocks to be moved. The first air block moves N meter, and the N'th air block moves 1 meter. 5. Moving air K meter to the back takes at least K/12 piston movements, rounded up, which is written as ⌈k/12⌉. This is because air moves a maximum distance of 12 blocks per piston movement. 6. Since this is always possible, the minimal amount of piston movements for an extension of N meter is the sum of ⌈k/12⌉, from k=1 to k=N. 7. This logic works the same for retraction; the minimal amount of movements is the sum of ⌈k/1⌉=k, from k=1 to k=N, which is actually just equal to ½N(N+1), or the N'th triangular number. Personally, I think my proof is very elegant, hope this helps!
This is the most elegant proof I've seen so far - thank you for sharing! I saw your note about winning IMO - that's absolutely incredible, congratulations!
@@mattbatwings Thank you, but I didn't 'win' the International Mathematical Olympiad; multiple people win gold medals every year. In all of the Olympiads, half of the competitors wins a medal, and the ratio between gold, silver and brons is 1 : 2 : 3. 100 countries send their six best competitors to the IMO, so a little less than 50 people win a gold medal. I was 19th.
This video unironically made math interesting to me. Your visuals are really easy to follow, I only backtracked like once (I usually backtrack a lot in videos). I like how you started simple and gradually went more complex leading to formulas. I'm definitely subbing!
Very nice how contraction parallelization enables you to have it work with a log of blocks in adequate amount of time. So instead of n! steps you just need 2n-1. Every for small amount like 10 blocks the difference is incredible 10! = 3628800, 2*10-1 = 19
9:05 You can find a quadratic lower bound on the number of elements in your extension sequence as follows. Your initial state with n pistons can be represented by a sequence P^(n+1) H^n where P denotes a piston (or the block to push) and H a "hole", i.e., air. Your final state is (P H)^n P Note that both states have the same length. All your moves, i.e., individual piston extensions, will just swap P's and H's around in the state. So this means that the n holes must be moved somehow such that they appear in the even (2nd, 4th and so on) positions, by means of piston extensions. Observe that every move must take a clump P^l H with l
This is the best video I've seen in a while. Obviously math and redstone relate quite heavily, but somehow with the animations and explanation, it was very clear and concise. Thank you for your inspiration.
i have 0 interest in redstone and hardly any interest in math but you explain this in such an interesting way that i cannot stop paying attention. its so easy to understand because of the visuals and how well you explain everything, i love this.
Something that I find very cool about this is that it kinda resembles liquid travel through a narrow tube, or low resolution fluid simulations. The spaces between the blocks look like air bubbles floating up and out as they break the surface tension of the water above them.
This is actually a great way to introduce mathematical induction, that I've never thought of as a huge maths and redstone nerd! Ty again mattbattwings and best of luck !!
It is just amazing work. I have very much respect to people like you, because you made whole video which have a lot of details and explains in easy way smart, little tricky and interesting thing
Extending two pistions (and having one pushing the other) at the same time (in the same game tick) is possible. I uploaded a short video showing in which cases this is possible, because there are some limitations to that. I don't know if this can be used to speed up pistion extenders even more.
Bro I swear if 20 years from now we gonna see math problems like this asking like “If we have a piston extension with 30 pistons how long is the length from the back piston to the block when activated”
Love this, math isn't exactly the _last_ thing I think of when I think of minecraft, so it's cool to see a deep dive into one of the game's most versatile mechanics!
Loved this video! Another interesting bit of minecraft math that I've been looking into is an algorithm for generating piston sequences for a piston door of any size
I see that some people want piston 1 to push the block right in front of it, and then do [13,1], but I feel like starting as close to the next chunk as possible would be a bit more optimal, as in, for 13 pistons, piston 12 pushes, then you do [13,1]. For 25 pistons, you'd do 12, then 24, then [25,1], so you always end up only doing the n->1 pushes when you can push for the entire chain, instead of having any sub-chain pushes that aren't a single push that moves 12 pistons 1 step forward to free up pistons further back in the chain. To further extrapolate: Make every multiple of 12, starting from 12*1 and working up towards 12*m < n, push the 12 blocks in front of it, and when you reach 12*(m+1) >= n, just do the n->1 push chain.
The extension sequence you describe is not optimal for every length piston extender. For example, with the 13 extender, you can have any one of the pistons 1-12 fire, creating a gap, then just extend from 13 to 1. However, I think this is just as fast as the sequence you named with parallelization, although requiring more piston extensions. Yours is probably easier to wire though (at least smaller) because you can just repeatedly power the same line from the back.
I see a lot of people with the optimal solution for piston extension but not a formal proof, so I figure I might give one. Apologies if someone else already did so. I'm going to generalize the problem slightly to be "each piston can move at most 'm' blocks". Just take m=12 for the specific solution. To describe an optimal optimal solution, define q, r as non-negative integer s.t. n=q * m + r, r < m (quotient and remainder) TLDR, an optimal solution is to move block m, 2m, 3m until qm, then if r != 0 move the nth block. After this process the leftmost piston should be followed by a gap followed by the other n-1 pistons next to each other. Then repeat this solution recursively on the n-1 pistons. You can prove this is optimal using induction and by showing that any other opt sequence is at least as good as this one by reordering steps in the sequence. --- Lemma 1: Lower bound for optimal sequence is (n - 1). Pf: Define a component to be a collections of pistons next to each other that are not interrupted by gaps. The problem starts of with 1 components (of size n), and ends up with n components (each of size 1, each individual piston is it's own component). When a piston is pushed in the rightmost component the number of components increases by 1, otherwise it stays the same since the block of pistons being split off joins the component directly after it. So at least (n-1) steps are needed to get to the final state. ---- In your video you showed examples of (n-1) length sequences for n S_j and there must be a gap after the S_i+y piston, so swapping them in our sequence doesn't change the blocks they push out, and after applying both steps swapped we end up in the same configuration as before. With the above, we can keep moving primitive steps before non-primitive ones and end up with a new sequences Q_1, ... Q_K where all the the primitive steps of the original sequence are done before the non-primitive ones (in the same order; aside another way to put this is that the subsequences are independent to the action of piston pushing - there's some group theory way to formalize this if you want). The primitive steps at the beginning must be strictly increasing, since each step decreases the size of the leftmost component, and it must end with a step where the left-most piston is extended, since we need to end up with a leftmost component of size 1 by the end. Now notice that there's always two components here, except for the initial state which has one component. This is because we're only acting on the leftmost component, we can only increase the number of components if we act on the rightmost component, and the only time the left and rightmost components are the same is at the start. The most that any operation can push out is 'm' pistons, and pushing out in our case means transferring from the left component to the right component. By the end of process you will up with a left component of size one and a right component of size n (we started with n+1 pistons). This means that we need at least ceiling(n+1/m) primitive steps. The sequence from the TLDR does this, but if there's a remainder then there's a lot of other solutions too since you could move the remainder first (like some other solution here do, or mix and match etc.). Once you do this you have the leftmost piston by itself and the remaining piston is a single component of length n, so we just use our inductive hypothesis and repeat the same procedure to the remaining parts. --- So yeah, there you have it. Hopefully I didn't make any mistakes there.
On extension optimality: Your sequence is sub-optimal in *two* ways: [edit: never mind, you mentioned the second improvement at 9:14.] As others have pointed out, in your 13 piston example, you can extend only piston 1 and then do the 13->1 sequence. And for a 14-piston extender, you _COULD_ do 2->1 first and then 14->1. But you can now do some operations *simultaneously*: You do 2 first, then 1 and 14 at the same time, then 13->1. For 25, you do 1 in the first "tick", then the second "tick" start the 13->1 sequence, then the third "tick" start the 25->1 sequence. And so on. I think that's the optimum. It adds only a single "tick" for every group of 12 that the pistons need to be split into.
Very nice! Also some clarifications: • pistons don't need a long pulse to retract, they can retract with a normal single pulse. Technically you can get away with zero tick stuff to push multiple pistons in sequence at the same time but that gets very glitchy with update order shenanigans and you really don't wanna mess with that. • as others have pointed out, the reason you can't prove that the repeated steps are optimal is cause they aren't: the modular method is! • the act of sticky Pistons leaving behind a block when powered for a single tick is called "block spitting" and it was originally a bug, much like some other redstone features (quasi-connectivity comes to mind) • we technically have infinite piston extenders and retractors, though it's a bit cheaty to call then "extenders" since those are their own category of redstone tech: if you place a piston to push something that drags a sticky piston (facing backwards) with itself - such as a slime block - and then that triggers this piston to pull the other one along, you'd have a self-dragging contraption that moves infinitely until it encounters an obstacle. You can make the movement itself trigger pistons by using observer blocks. TA-DA! You have made a *redstone flying machine*! And fun fact, observers triggering when they move is ALSO a bug that became a feature! Aaaaah Minecraft...
Something that didnt get said here but i think is mathematically interesting is that the retraction system is just the reverse of the push system when the push limit is 1 block.
I love this kind of video, hope you will continue to make them after SoME3. The incorporation and application of mathematics into minecraft was really well done. My one minor piece of constructive criticism is that, while I could feel that it worked, the proof that you showed for the retraction being optimal needed to be completed. Thank you so much for this great video.
this is mathematically and visually elegant and beautiful. never seen piston extenders explained in such an approachable way. i sure wish this kinda thing existed before slime flying machines!
Started watching in the background while playing minecraft, just for background audio, but I have now spent the last 15 minutes just watching the video, standing still in minecraft. Nice work, very entertaining, and awesome :)
As someone who is currently in their first year of uni learning computational thinking and someone who grew up loving Minecraft, this is such a cool video and quite inspiring actually. Thank you for this! Keep up the great work
The extension sequence is definitely not optimal because there is a solution with fewer extensions. For a 13 piston extension your solution does a total of 25 extensions. If you do the sequence: 12, 13, 12->1 then you only do a total of 14 extensions.
BRO YOU ARE RIGHT!!! I thought you were just trying to make fun of us with the "Just be good" thing, so i whipped out my sketch book, drew from a reference, and IT LOOKS SO FUCKING GOOD!!!!!! imma try to keep up with this.
That was great, i love MC maths an 3b1b even tho i stumbled upon this video randomly, its great that when you made assumptions that you didnt know how to prove you let it be a conjecture and not a false statement, great explanations that go through the basis of both minecraft and maths while being concize.
It's not optimal: for a 13 piston extender, you have 1, 13->1. (14 steps; clearly less than 12->1, 13->1 with 25 steps). In general we have that n%12->1, 12+(n%12)->1, 24+(n%12)->1, ..., n->1 is a valid solution. e.g. for 25: 1, 13->1, 25->1 Your solution takes n + 6((n//12)^2 + n//12) steps (where // is floor division) mine takes (n%12)(n//12 + 1) + 6((n//12)^2 + n//12). n//12 = (n - n%12)/12 n%12 < 12 => (n%12)(n//12 + 1) = (n%12)((n - n%12)/12) + (n%12) < 12((n - 12)/12) + 12 = n - 12 + 12 = n Hence (n%12)(n//12 + 1) < n Hence (n%12)(n//12 + 1) + 6((n//12)^2 + n//12) < n + 6((n//12)^2 + n//12) So my solution is more efficient in general.
For the extender, it's better to think about trying to activate the backmost piston as soon as possible, similar to how it worked without a push limit. As it's only possible to move 12 blocks at a time, start with piston 12. Next, the furthest behind 12 that can successfully activate is 24, then 36, etc. Activate all the multiples of 12 until piston n can activate, then activate all the multiples of 12 until (n-1) can activate, repeat for all pistons in the extender. So the method for an n-piston extender, in pseudocode, looks like: let k = n while k > 0 let j = 12 while j < k { push j let j = j + 12 } push k let k = k - 1 } This sequence for the 40-piston extender is: 12, 24, 36, 40, 12, 24, 36, 39, 12, 24, 36, 38, 12, 24, 36, 37, 12, 24, 36, 12, 24, 35, 12, 24, 34, 12, 24, 33, 12, 24, 32, 12, 24, 31, 12, 24, 30, 12, 24, 29, 12, 24, 28, 12, 24, 27, 12, 24, 26, 12, 24, 25, 12, 24, 12, 23, 12, 22, 12, 21, 12, 20, 12, 19, 12, 18, 12, 17, 12, 16, 12, 15, 12, 14, 12, 13 -> 1 which has 88 pushes, while your method uses 112 pushes. It's unfortunately not nearly as neat to write the sequence out nor capable of parallelization, but it definite saves pushes. I believe this is optimal, though I don't know how to go about proving it. Though it seems @arcycatten already came up with a different solution that agrees on number of pushes, has a neater sequence, and is parallelizable.
the way you have the parallel pisron firing reminds me of a smarter every day video called STRANGE but GENIUS Caterpillar Speed Trick with caterpillars that ride each other like a wave
8, 16, 24, 32, 40, 48, 56, 64, 72, 80, 88, 96, 104, 112, 120, 128, 136, 144, 152, 160, 168, 176, 184, 192, 200, 208, 216, 224, 232, 240, 248, 256 Yeah, memorized 8 times tables because of Minecraft, did all these off memory, stopped at 256 because didn't want to go forever, and realistically, it does repeat the cycle every 200.
A brilliant explanation, i love it. The visuals are helping a lot. Yet i still can miss something from there... I actually really want to understand redstone, like how should you look at it, and seeking math is the right thing. This video kinda opened my eyes on how piston extenders work. Now, i should check more of your videos (and maybe I'll finally get smarter)
CHECK OUT PART 2 for corrections and more math! :D ruclips.net/video/6emS04mkRGs/видео.htmlsi=RLGIBlMooxlgN848
I am your enemy. 👿
😢
Is it mathematical induction?
I don’t think about everything in detail nut if n is 13 why not 12, 13 -> 1 it has 14 extensions while 12 ->1, 13-> 1 has much more @mattbatwings
why is matt here
I think a more optimal way to do piston extenders for n blocks is to use modular arithmetic. ([x mod y] is the remainder when x is divided by y, e.g. 35 mod 10 = 5) [these brackets aren't required, i just use them for clarity]
basically, you push the first [n mod 12] blocks ([n mod 12] -> 1), then [12 + n mod 12], and repeat until you get to n.
this is actually a generalization of @abugidaiguess's method for 13 pistons.
If n mod 12 = 0 (i.e. n is divisible by 12), then it saves no extra steps.
But otherwise, it saves exactly [n - (ceil(n / 12)) * (n mod 12)] over what is shown in the video!
some examples:
13 pistons (video): 12 -> 1, 13 -> 1; 12 + 13 = 25 steps
13 pistons (modular): 1, 13 -> 1; 1 + 13 = 14 steps
steps saved: 25 - 14 = 11
30 pistons (video): 12 -> 1, 24 -> 1, 30 -> 1; 12 + 24 + 30 = 66 steps
30 pistons (modular): 6 -> 1, 18 -> 1, 30 -> 1; 6 + 18 + 30 = 54 steps
steps saved: 66 - 54 = 12
500 pistons (video): 12 -> 1, 24 -> 1, ..., 492 -> 1 (that's 12 * 41, btw), 500 -> 1; 12 * (1 + 2 + ... + 41) + 500 = 10832 steps
500 pistons (modular): 8 -> 1, 20 -> 1, 32 -> 1, ..., 488 -> 1, 500 -> 1; 8 * 42 + 12 * (1 + 2 + ... + 41) = 10668
steps saved: 10832 - 10668 = 164 (that's a lot!)
btw I used a computer program to generate the number of steps for that last one, so it may not be 100% accurate!
nice, that makes sense! for all cases other than multiples of 12, this way of doing it produces a shorter sequence.
funnily enough, this is actually what gets implemented in the redstone version! In game, I always forced the subsequences to line up with the back, because that way I can change the number of pistons without having to shift the redstone. notice how at 19:09 it starts with 4 -> 1 because its a 40 piston extender
mind if I pin this comment? would be nice to share this info with everyone! and it could serve as a thread for more discussion about this in the replies
@@mattbatwings yeah that would be awesome! i'm totally fine with being pinned :)
interesting that the redstone ends up producing the shorter sequence anyway. and i'm not much of a redstone guy, so those builds you make always blow my mind, even after all the explanations!
also i just joined the discord server and it looks great ^^
Damn, nice funny words Mr magic man!
0_0
@mattbatwings
yeeeaaahh I fel smerter that Matt it took me like 1 sec to figure out this
anyway I hope this little mistake didn't make this video feel less professional, since you could have made a program that tested all possibilities, knowing that there is a finite and small number of them for a 13-long extender. This way you could have seen that this method was more optimal.
no worries though, you can't be the best at redstone computing and door making.
14:05 The little touch with the empty blocks accentuated by the glass texture is so aesthetically pleasing!
It's so cool that #SoME3 is getting some really creative entries even from the channels you wouldn't expect to join.
This is the second video I've seen on that, but the first I've actually watched and I have no idea what it is.
(the other being mate in Omega, the chess one)
@@TyphoonBeam It's a yearly competition organized by 3Blue1Brown (a yt channel) to support smaller educational and other math related creators
What’s SoME3?
@@burningnetherite4206 Summit of Math Education is competiton to foster the creation math content online. Anyone could join competition until 19th August. Now you can't join as a participant but you can still join as a judge
@@burningnetherite4206third edition of the summer of math exposition
The way you parallelized this is actually really similar to how CPUs are optimized. Cpus have several stages they have to do, and they used to have to every stage before the clock cycle. But modern cpus will only do one stage per clock cycle, but will run them all in parallel by starting a new instruction on each clock cycle.
For a 13 piston extender 1 , 13 -> 1 is more optimal than 12->1, 13->1. Further for a n-piston extender rather than iterating 12->1, 24->1 … n->1 you can simply do (n mod 12) -> 1, (n mod 12) + 12 -> 1, (n mod 12) + 24 -> 1 … n -> 1
This saves you floor(n/12)*(12 - (n mod 12) total steps on the extension. Correct me if I’m wrong but this is provably optimal
@@rohiem7554 now prove that this is the fastest :D
@@profx33this method optimizes the number of piston extensions, however it can still be run in parallel so asymptotically it would take the same amount of time per extension as the method proposed in the video, simply with fewer extensions hence less time. Additionally the use of zero tick mechanics can be used to improve the time between piston firing.
13->1 does not move all the blocks. Remember there is iron (or some other block) in front and the index of a piston is equal to the number of blocks in front of it. Pistons can only push 12 blocks, so piston 13 can’t activate since it has 13 blocks in front of it.
@@peterbullard8040thats why they activated 1 first.
I've gotta give you props for this. This is gotta be one of the most clear explanations I've seen. No crazy music; and straight to the point, and showing the steps behind each thought and conclusion.
Subbed.
I feel like this is exactly the type of video that 3b1b loves to see with this SoME. I love how gaming communities can go together like this with the math community.
In the case of minecraft, all the people that are serious about redstone builds (talking about "technical" minecraft players) are on the smarter side of the gaming community and are not afraid of crunshing numbers and investing more time doing math about the game than actually playing it. I always like it, when I catch myself calculating growth of supplies, output of farms, speed of a vehicle, damage over time, and so on, in the middle of a gaming session 😅
Looked at the profile of the video creator just now, and in fact, it is not a math guy doing minecraft, but a minecraft guy doing math 😂 Technical player right there.
As a math nerd and minecraft fan, I am very happy with this video
haha, the minecraft community (specifically the redstone community) is intertwined with the maths community. There's just too much overlap for it not to be the case.
Justwatched 3b1b SoME3 recommendations. Sadly didn't see this in the 25, but did see it in the comments. So came here to watch it. Again. Good job. 👍
For the record, short (1TP/0TP) pulses will also retract blocks, *if* the block was in the extended position when the pulse was produced - so can also be time-optimised in that way
Which is what every single demonstration after that explanation uses. So yeah, that's some crucial information.
i was gonna say that
Thing is the system measures time in extensions/retractions, not in tick speed.
@@LineOfThy that is because as far as i know a 0/1t pulse still takes 2t to move the block
@@hunorfekete7413 Ye but it's still one extension/retraction
My programmer brain makes me unable to digest the fact that the piston next to the block is called 1 instead of 0 at 2:45...
My programmer brain has the same problem, but I guess you could see the iron block as position zero? Feels a bit wrong considering it doesn't do anything, but it's better than a list starting at 0
after finding that dispensers are a dynamical system I'm not surprised you've found some math surrounding piston extenders that warrants a whole math explanation vid, excited to see what you've put together and best of luck with your submission
(This comment was made before the premiere)
My guess for the video is gonna be deriving an algorithm for finding the order in which pistons need to be fired to close/open an nth long piston extender
That and/or deriving the correct timings to do such
@@austinclees9252extender designs are simpler than that, my prediction is that it's gonna be about the observer + 2tick-repeater design which is infinitely expandable and uses just a clock and a timer to get all the pulses, it's a really smart design because although the inputs are kinda intuitive, the piston sequence isn't but in the end it all somehow manages to work
Which vid was this?
@@NickGarcia1519it's just a dispenser math video, can look it up on yt
EXTENSION PARALLELIZATION is exactly what GPU's do comparatively to CPU's ... and there are engineers called CUDA programmers their job is to find a way to parallelize chunks of repetitive codes in order to take advantage of the shear amount of cuda cores that can parallelize process data
for a 13 piston extender, you can just do 1, 13 → 1
saves 11 extensions, and should be fairly simple to generalise up until 24 at least
edit: as a few replies have pointed out, it actually doesn't really matter which piston is extended first. i just happened to choose 1 in my head
edit 2: wow okay
so it turns out the method i thought of has since been generalised by the pinned commenter (who actually called it "@abugidaiguess's method"!)
i honestly didn't put much thought into the comment beyond the specific case for a 13 piston extender, so i'm really glad other people did! :D
Came here to say this.
This
I was thinking 12, 13→1 which works basically the same way
I had the same idea only just starting from the back. (12,13→1)
Edit: eivindhamre3026 wrote the same thing 30s before me
@@kajatoth9151 too slow
Yoooooo, kinda sick you're submitting to SoM3. Didn't see it coming, but it's very welcome
It appears 3Blue1Brown has reached the Minecrafters
Yeah i like both
This is probably one of the most intriguing and entertaining Redstone videos I've ever watched
A detailed analysis of the optimal extension sequence:
Consider the total cost of an n-extension. We can consider the total cost to move all required blocks 1 block forward, 2 blocks forward, 3 blocks forward etc. separately, because each extension pushes a subset of the pistons/block which have all currently been moved forward the same amount of times (i.e. it is impossible to simultaneously push two pistons that have moved a different number of times each, because there will be an air gap in between). The first set of blocks (that needs to be moved forward once) has size n, then the next set (that moves forward twice) n - 1, then n - 2 and so on until there is only 1 block that must be moved n times. The kth of these has size (n - k + 1) and requires ceil[(n - k + 1) / 12] extensions as each extension can only push at most 12 blocks. So the total cost is the sum from k=1 to n of ceil[(n - k + 1) / 12]. Notice, however, that this is equivalent to ceil[(n - 1 + 1) / 12] + cost(n - 1), that is, ceil(n / 12) + cost(n - 1), with cost(0) = 0. This can therefore be expressed as cost(n) = ceil(n/12) * (6 + n - 6*ceil(n/12)).
Also note that this lower bound is achievable because we can simply do the process one step at a time, moving forward the first n-1 pistons in ceil(n/12) steps, then the next n-2 in ceil((n-1)/12), etc.
The most interesting piston extender math (in my opinion) is that of "hipster" extenders, which are piston extenders that extend beyond the wiring itself. This means in order to power pistons beyond the wiring, movable power sources such as redstone blocks or observers must be extended and retracted themselves. This makes the analysis of the optimal sequence slightly more tricky. Every distance extended/retracted beyond the wiring requires recursively using the distances 1, 2 or 3 blocks before it one or more times (in order to extend and retract the power source, and move the piston back 1 block), leading to exponential growth in the length of the sequence.
So wait you boiled the extension process down to a function? I could be very wrong because i am dog ass at math, nice explanation though!
Yes, what we care about most is the length of the sequence (not the actual sequence itself), so I defined the function cost(n) to be the length of an optimal n-extension.
@@sammyuri ah okay thanks for clarifying
Solution "may" not be optimal. It "may" be the case that somewhere in an optimal solution, a piston extension is used in both the moving of the 7th block and also the 10th which could make a better solution than the one you propose.
I put "may" because I think you're right, but you didn't prove this "may" had to be wrong.
@@viktort9490No, this solution is rigorous. In fact, what you say is true (a piston extension IS used in the moving of both the 7th and 10th blocks) - the point is that it can be used to move BOTH those blocks if and only if they have moved the same amount of times so far, or there would be an air gap between and only the 10th block would be moved. This then leads to the independence of each distance moved and the rest of the proof.
Honestly this is a great vid, the topic is interesting and presented very well.
So I had an idea at around 8:12, and that's that the 13 block extension could be done more simply than 12->1, 13->1. I believe that the sequence 12, 13, 12->1 would also work but with less repetition. Therefore, this disproves that the formula for sequences of individual extensions does not necessarily always give an optimal result.
Edit: Well it's not something unique I've came up with, but it is still true so I'll take that. Great video as always
i was thinking the exact same thing and was like, someone else HAD to have thought of it already, right? i mean it's just so obvious! and you did, so thanks. :)
This was an incredible video, the visuals were super helpful and the math was impressive. Great job!
3Blue1Brown--Grant Sanderson is one of my most watched channels on youtube. You are an absolute legend for sharing with the world the wonders of Maths and Minecraft, Mattbatwings. Thank you for all that you do; this is incredible!
oh my god this was the most beautiful math video i've ever seen
The formula at 9:11 doesn't produce optimal results every time. Take the 13 piston extender, you could do 1, 13->1 and that's 14 pushes insted of 25
the formula does allow for an infinitely expandable and modular design to an extender though. using the most optimal number of pushes would require different extenders to have their own different redstone circuits.
the formula ends up being the same after parrelisation
@@Drawliphant You need to 1 tick piston 1, or honestly any piston other than 13, and then extend all pistons 13 -> 1
@@Drawliphantyou don't need to push an expanded piston. You do a quick pulse with one of the first 12 pistons. It will push everything forward and not have time to pull it back. Then the gap created means 13 can now fire to fill that gap and then you can just go down the line.
Just found your channel through this video and Holy shit your videos have been the highlight of my week! Absolutely amazing videos that give me the same feeling as watching Ben Eater videos. Keep it up!
This is the intersection of multiple internal Venn Diagrams I have. Math, Redstone, etc. What a video! Hope your SoME3 sub wins!
I'm not a redstone nerd, but I am a math nerd and I love doing random stuff in Minecraft. I liked this video a lot, such a creative entry to the contest!
I didn't think you would participate SoME3 ! This was definitely a surprise, but a pleasant one =)
n < 13: n --> 1, n> 13: 1 + (Number of pistons - 13) ---> (Result of the past equation ) - 1, n --> 1 (One at a time)
The footage of you actually building the contraptions is really nice, please continue to do this
This brings me back to mumbo jumbo building triple piston extenders
The true infinite piston extender: A flying machine
Edit: How did this get 600 likes? wow. If anything i thought i'd get criticised for dodging the video's topic
Flying mashine go brrrrrr😂😅😂😅
@@davidmunizwessels8520 “
Frfr
To easy
till the chunk it is in hides
The proof for the Retracrion only needs a small addition to be valid for any number of blocks:
-6 is proven to be ideal for a 3 piston retraction
-any extra piston adds n (new number of pistons) block movements, because every block in the old chain (n-1 pistons + 1 block upfront) needs to move back one more block each
-any extra piston adds n ( new number of pistons) retractions in this algorythm, becase n->1 is added at the end of it
=> the required block movements and the number of retractions start at the same number and rise by an equal amount for each itteration of n, therefore both numbers are equal for any given n
Q.E.D.
I’m so excited.
SoME has been a great way for a pure math undergrad like myself to pass the summer. Cant wait to see how you take things :D
even just a middle schooler like me!
why math bruh it's so boring when you don't have anything to apply it to
@@anon1963 frick you! Maths is the best
@@anon1963some people just find it fun.😊😊😊😊
@@anon1963First of all, higher level math is beautiful and not boring in its own right. Second, there are millions of applications of many, if not most, areas of math
As someone who studies advanced level mathematics and physics at school and also plays videogames like Minecraft for fun, i always considered gaming and my studies to be completely separate from each other and not at all connected. Gaming is always little more than a fun leisure activity whilst my studies in physics and maths is more important and mandatory schoolwork. However, watching this video has opened my eyes fact that there are likely many different connections between maths (and maybe even physics) and the games that i play.
what counts as advanced level mathematics?
@@czechmateyoulost1755 I mean A Level maths and physics. It's the qualifications you take at age 16 and 17 in the UK where you usually pick 3 or 4 subjects of your choice that you want to study before you use your grades in your subjects after the end of 2 years of study once you've done your final exams to enrol at university
@@ShaneB24642 Oh okay, i thought you were studying math at university
0:16 this "me lmao" guy is pretty insane
Nice job this gives me some great inspiration for some new machines.
There is a way to think about piston extenders which I would like to share!
1. Think about the blocks being moved to be air block, instead of pistons.
2. When an air block is in a certain location, movement on the two sides doesn't interfere with each other.
3. We can look at only a single air at a time, we can simply assume the movement in the back to happen first, until the air space is filled.
4. When extending, there are N air blocks to be moved. The first air block moves N meter, and the N'th air block moves 1 meter.
5. Moving air K meter to the back takes at least K/12 piston movements, rounded up, which is written as ⌈k/12⌉.
This is because air moves a maximum distance of 12 blocks per piston movement.
6. Since this is always possible, the minimal amount of piston movements for an extension of N meter is the sum of ⌈k/12⌉, from k=1 to k=N.
7. This logic works the same for retraction; the minimal amount of movements is the sum of ⌈k/1⌉=k, from k=1 to k=N, which is actually just equal to ½N(N+1), or the N'th triangular number.
Personally, I think my proof is very elegant, hope this helps!
This is the most elegant proof I've seen so far - thank you for sharing! I saw your note about winning IMO - that's absolutely incredible, congratulations!
@@mattbatwings Thank you, but I didn't 'win' the International Mathematical Olympiad; multiple people win gold medals every year.
In all of the Olympiads, half of the competitors wins a medal, and the ratio between gold, silver and brons is 1 : 2 : 3.
100 countries send their six best competitors to the IMO, so a little less than 50 people win a gold medal.
I was 19th.
@@caspermadlener4191I appreciate your work to the Minecraft community and I Hope, One day, to see your name in the podium of the IMO👏
@@Lumyx_x Thank you, but I was already on the IMO podium in 2022, and the IMO is ment for people before university.
@@caspermadlener4191 In every case, your explanation was perfect, even if I am not a great mathematical Person, i clearly understood It, thx
This video unironically made math interesting to me. Your visuals are really easy to follow, I only backtracked like once (I usually backtrack a lot in videos). I like how you started simple and gradually went more complex leading to formulas. I'm definitely subbing!
Just casually scrolling through for all of the people who think they are smart and found the more optimal Extention method
That's really cool! I always love seeing all the SoM videos. Yours in particular is super well editing with great pacing and great explanations.
0:02 *cries* The first tutorial World I ever played…
sameeeee
@@ajmod73 YAY!
Very nice how contraction parallelization enables you to have it work with a log of blocks in adequate amount of time. So instead of n! steps you just need 2n-1. Every for small amount like 10 blocks the difference is incredible 10! = 3628800, 2*10-1 = 19
9:05
You can find a quadratic lower bound on the number of elements in your extension sequence as follows.
Your initial state with n pistons can be represented by a sequence
P^(n+1) H^n
where P denotes a piston (or the block to push) and H a "hole", i.e., air. Your final state is
(P H)^n P
Note that both states have the same length. All your moves, i.e., individual piston extensions,
will just swap P's and H's around in the state.
So this means that the n holes must be moved somehow such that they appear in the even
(2nd, 4th and so on) positions, by means of piston extensions.
Observe that every move must take a clump
P^l H with l
i love this video! the editing was fantastic and i love the math behind it.
10:30 oooh that's a wrong combination of numbers :)
This is the best video I've seen in a while. Obviously math and redstone relate quite heavily, but somehow with the animations and explanation, it was very clear and concise. Thank you for your inspiration.
Funfact: retraction doesnt need a long pulse. With a sticky piston and a block on it. You can use 2 short pulses to extract and then retract
Sometimes it's better to assume cows are spheres in a vaccum.
@@atlascove1810 This makes me remember the science diagram of a cow's aerodynamics.
i have 0 interest in redstone and hardly any interest in math but you explain this in such an interesting way that i cannot stop paying attention. its so easy to understand because of the visuals and how well you explain everything, i love this.
mattbatwings and 3blue1brown crossover is not something I know I needed, but holy crap I'm all here for it O.O
if only
its not really a crossover. Its just a video for 3b1bs math video contest
Lol
Something that I find very cool about this is that it kinda resembles liquid travel through a narrow tube, or low resolution fluid simulations. The spaces between the blocks look like air bubbles floating up and out as they break the surface tension of the water above them.
This is actually a great way to introduce mathematical induction, that I've never thought of as a huge maths and redstone nerd! Ty again mattbattwings and best of luck !!
I feel like RUclips is listening to my lectures when I see videos that directly apply what I just learned😅
Very good visuals! Sloimay made very cool animations. But I'd like to see more on retraction parallelization, it seemed quite glossed over.
it’s not that complicated! each retraction of n pistons takes exactly 2n - 1 steps with parallelization, and n(n + 1)/2 steps without it
It is just amazing work. I have very much respect to people like you, because you made whole video which have a lot of details and explains in easy way smart, little tricky and interesting thing
Extending two pistions (and having one pushing the other) at the same time (in the same game tick) is possible. I uploaded a short video showing in which cases this is possible, because there are some limitations to that. I don't know if this can be used to speed up pistion extenders even more.
Bro I swear if 20 years from now we gonna see math problems like this asking like “If we have a piston extension with 30 pistons how long is the length from the back piston to the block when activated”
Love this, math isn't exactly the _last_ thing I think of when I think of minecraft, so it's cool to see a deep dive into one of the game's most versatile mechanics!
Loved this video! Another interesting bit of minecraft math that I've been looking into is an algorithm for generating piston sequences for a piston door of any size
but spacewalker 46 piston extender >>>>
Crafty!! Hi :)
And btw avogadoo’s infinite extendable instant piston extender >>>>>>>>>>> :)
I see that some people want piston 1 to push the block right in front of it, and then do [13,1], but I feel like starting as close to the next chunk as possible would be a bit more optimal, as in, for 13 pistons, piston 12 pushes, then you do [13,1].
For 25 pistons, you'd do 12, then 24, then [25,1], so you always end up only doing the n->1 pushes when you can push for the entire chain, instead of having any sub-chain pushes that aren't a single push that moves 12 pistons 1 step forward to free up pistons further back in the chain.
To further extrapolate:
Make every multiple of 12, starting from 12*1 and working up towards 12*m < n, push the 12 blocks in front of it, and when you reach 12*(m+1) >= n, just do the n->1 push chain.
Couldnt you in a 13 piston seqience just start with 12 then 13 and then 12-1, instead of 12-1 then 13-1
15:54 TRIANGLE NUMBERS!
I ran into a lot of these number sequences when doing abstract math for fun a while ago
Fantastic video :D
The extension sequence you describe is not optimal for every length piston extender. For example, with the 13 extender, you can have any one of the pistons 1-12 fire, creating a gap, then just extend from 13 to 1. However, I think this is just as fast as the sequence you named with parallelization, although requiring more piston extensions. Yours is probably easier to wire though (at least smaller) because you can just repeatedly power the same line from the back.
This helped me make a one sided stackable piston extender using coppet bulbs and I just wanted to say thank you for simplifying these things for us!
for a 13 piston extender can't you just do 12 then 13->1 for the extension
You have to give a pulse, wich maked it more complicated
@@huseyinemreeken3024 but it still would be the fastest way without grouping
I see a lot of people with the optimal solution for piston extension but not a formal proof, so I figure I might give one. Apologies if someone else already did so.
I'm going to generalize the problem slightly to be "each piston can move at most 'm' blocks". Just take m=12 for the specific solution.
To describe an optimal optimal solution, define q, r as non-negative integer s.t. n=q * m + r, r < m (quotient and remainder)
TLDR, an optimal solution is to move block m, 2m, 3m until qm, then if r != 0 move the nth block. After this process the leftmost piston should be followed by a gap followed by the other n-1 pistons next to each other. Then repeat this solution recursively on the n-1 pistons.
You can prove this is optimal using induction and by showing that any other opt sequence is at least as good as this one by reordering steps in the sequence.
---
Lemma 1: Lower bound for optimal sequence is (n - 1).
Pf: Define a component to be a collections of pistons next to each other that are not interrupted by gaps. The problem starts of with 1 components (of size n), and ends up with n components (each of size 1, each individual piston is it's own component). When a piston is pushed in the rightmost component the number of components increases by 1, otherwise it stays the same since the block of pistons being split off joins the component directly after it. So at least (n-1) steps are needed to get to the final state.
----
In your video you showed examples of (n-1) length sequences for n S_j and there must be a gap after the S_i+y piston, so swapping them in our sequence doesn't change the blocks they push out, and after applying both steps swapped we end up in the same configuration as before.
With the above, we can keep moving primitive steps before non-primitive ones and end up with a new sequences Q_1, ... Q_K where all the the primitive steps of the original sequence are done before the non-primitive ones (in the same order; aside another way to put this is that the subsequences are independent to the action of piston pushing - there's some group theory way to formalize this if you want). The primitive steps at the beginning must be strictly increasing, since each step decreases the size of the leftmost component, and it must end with a step where the left-most piston is extended, since we need to end up with a leftmost component of size 1 by the end. Now notice that there's always two components here, except for the initial state which has one component. This is because we're only acting on the leftmost component, we can only increase the number of components if we act on the rightmost component, and the only time the left and rightmost components are the same is at the start. The most that any operation can push out is 'm' pistons, and pushing out in our case means transferring from the left component to the right component. By the end of process you will up with a left component of size one and a right component of size n (we started with n+1 pistons). This means that we need at least ceiling(n+1/m) primitive steps. The sequence from the TLDR does this, but if there's a remainder then there's a lot of other solutions too since you could move the remainder first (like some other solution here do, or mix and match etc.). Once you do this you have the leftmost piston by itself and the remaining piston is a single component of length n, so we just use our inductive hypothesis and repeat the same procedure to the remaining parts.
---
So yeah, there you have it. Hopefully I didn't make any mistakes there.
10:30 twin towers
Lmao
bruh
On extension optimality: Your sequence is sub-optimal in *two* ways: [edit: never mind, you mentioned the second improvement at 9:14.]
As others have pointed out, in your 13 piston example, you can extend only piston 1 and then do the 13->1 sequence.
And for a 14-piston extender, you _COULD_ do 2->1 first and then 14->1. But you can now do some operations *simultaneously*: You do 2 first, then 1 and 14 at the same time, then 13->1.
For 25, you do 1 in the first "tick", then the second "tick" start the 13->1 sequence, then the third "tick" start the 25->1 sequence.
And so on.
I think that's the optimum. It adds only a single "tick" for every group of 12 that the pistons need to be split into.
Thank you for helping fellow youtubers by putting the music you use in the description, well all appreciate it
I've been playing with redstone for the last 11 years, and only now do I understand how to generalize piston extenders. This is so cool!
Very nice! Also some clarifications:
• pistons don't need a long pulse to retract, they can retract with a normal single pulse. Technically you can get away with zero tick stuff to push multiple pistons in sequence at the same time but that gets very glitchy with update order shenanigans and you really don't wanna mess with that.
• as others have pointed out, the reason you can't prove that the repeated steps are optimal is cause they aren't: the modular method is!
• the act of sticky Pistons leaving behind a block when powered for a single tick is called "block spitting" and it was originally a bug, much like some other redstone features (quasi-connectivity comes to mind)
• we technically have infinite piston extenders and retractors, though it's a bit cheaty to call then "extenders" since those are their own category of redstone tech: if you place a piston to push something that drags a sticky piston (facing backwards) with itself - such as a slime block - and then that triggers this piston to pull the other one along, you'd have a self-dragging contraption that moves infinitely until it encounters an obstacle. You can make the movement itself trigger pistons by using observer blocks. TA-DA! You have made a *redstone flying machine*! And fun fact, observers triggering when they move is ALSO a bug that became a feature! Aaaaah Minecraft...
Something that didnt get said here but i think is mathematically interesting is that the retraction system is just the reverse of the push system when the push limit is 1 block.
0:05 ayo sb needs to tag ChuckkNasty on this
I love this kind of video, hope you will continue to make them after SoME3. The incorporation and application of mathematics into minecraft was really well done. My one minor piece of constructive criticism is that, while I could feel that it worked, the proof that you showed for the retraction being optimal needed to be completed. Thank you so much for this great video.
this is mathematically and visually elegant and beautiful. never seen piston extenders explained in such an approachable way. i sure wish this kinda thing existed before slime flying machines!
Started watching in the background while playing minecraft, just for background audio, but I have now spent the last 15 minutes just watching the video, standing still in minecraft. Nice work, very entertaining, and awesome :)
Bro is The Best Maths Teacher in the world...
Change My Mind
As someone who is currently in their first year of uni learning computational thinking and someone who grew up loving Minecraft, this is such a cool video and quite inspiring actually. Thank you for this! Keep up the great work
The extension sequence is definitely not optimal because there is a solution with fewer extensions. For a 13 piston extension your solution does a total of 25 extensions. If you do the sequence: 12, 13, 12->1 then you only do a total of 14 extensions.
First 15 seconds and I already see footage from Hermitcraft (Doc's killer butterflies). :)
BRO YOU ARE RIGHT!!! I thought you were just trying to make fun of us with the "Just be good" thing, so i whipped out my sketch book, drew from a reference, and IT LOOKS SO FUCKING GOOD!!!!!! imma try to keep up with this.
That was great, i love MC maths an 3b1b even tho i stumbled upon this video randomly, its great that when you made assumptions that you didnt know how to prove you let it be a conjecture and not a false statement, great explanations that go through the basis of both minecraft and maths while being concize.
This video was everything I was hoping it'd be from the premise. Very nice
Amazing video! Great editing and clever solutions!
A short pulse can also pull a block, if it's detached from the piston already.
The explanation of redstone and specifically the piston was done so well and allows people who haven’t even played Minecraft to get into the video.
What a nice video. Very cool :-]
It's not optimal: for a 13 piston extender, you have 1, 13->1. (14 steps; clearly less than 12->1, 13->1 with 25 steps).
In general we have that n%12->1, 12+(n%12)->1, 24+(n%12)->1, ..., n->1 is a valid solution.
e.g. for 25: 1, 13->1, 25->1
Your solution takes n + 6((n//12)^2 + n//12) steps (where // is floor division) mine takes (n%12)(n//12 + 1) + 6((n//12)^2 + n//12).
n//12 = (n - n%12)/12
n%12 < 12
=> (n%12)(n//12 + 1) = (n%12)((n - n%12)/12) + (n%12) < 12((n - 12)/12) + 12 = n - 12 + 12 = n
Hence (n%12)(n//12 + 1) < n
Hence (n%12)(n//12 + 1) + 6((n//12)^2 + n//12) < n + 6((n//12)^2 + n//12)
So my solution is more efficient in general.
Your design is so clean, simple, and infinitely expandable!
I’m so happy to see you participating is #SoME3
You did a fantastic job with this one!
bro a SOME video by you is just such a crazy crossover i didn’t even suspect could happen. it makes sense tho 🔥
I didn't know I needed this video, but I'm glad I watched it, really interesting!
Math AND Minecraft?! LOVE IT!😍🥳
For the extender, it's better to think about trying to activate the backmost piston as soon as possible, similar to how it worked without a push limit.
As it's only possible to move 12 blocks at a time, start with piston 12. Next, the furthest behind 12 that can successfully activate is 24, then 36, etc. Activate all the multiples of 12 until piston n can activate, then activate all the multiples of 12 until (n-1) can activate, repeat for all pistons in the extender.
So the method for an n-piston extender, in pseudocode, looks like:
let k = n
while k > 0
let j = 12
while j < k {
push j
let j = j + 12
}
push k
let k = k - 1
}
This sequence for the 40-piston extender is:
12, 24, 36, 40, 12, 24, 36, 39, 12, 24, 36, 38, 12, 24, 36, 37, 12, 24, 36, 12, 24, 35, 12, 24, 34, 12, 24, 33, 12, 24, 32, 12, 24, 31, 12, 24, 30, 12, 24, 29, 12, 24, 28, 12, 24, 27, 12, 24, 26, 12, 24, 25, 12, 24,
12, 23, 12, 22, 12, 21, 12, 20, 12, 19, 12, 18, 12, 17, 12, 16, 12, 15, 12, 14, 12, 13 -> 1
which has 88 pushes, while your method uses 112 pushes.
It's unfortunately not nearly as neat to write the sequence out nor capable of parallelization, but it definite saves pushes. I believe this is optimal, though I don't know how to go about proving it.
Though it seems @arcycatten already came up with a different solution that agrees on number of pushes, has a neater sequence, and is parallelizable.
10:20 it's the same principle used in CPUs to parallelize instructions, it's called "instruction pipelining"
the way you have the parallel pisron firing reminds me of a smarter every day video called STRANGE but GENIUS Caterpillar Speed Trick with caterpillars that ride each other like a wave
8, 16, 24, 32, 40, 48, 56, 64, 72, 80, 88, 96, 104, 112, 120, 128, 136, 144, 152, 160, 168, 176, 184, 192, 200, 208, 216, 224, 232, 240, 248, 256
Yeah, memorized 8 times tables because of Minecraft, did all these off memory, stopped at 256 because didn't want to go forever, and realistically, it does repeat the cycle every 200.
A brilliant explanation, i love it. The visuals are helping a lot. Yet i still can miss something from there... I actually really want to understand redstone, like how should you look at it, and seeking math is the right thing. This video kinda opened my eyes on how piston extenders work. Now, i should check more of your videos (and maybe I'll finally get smarter)