4 ms·

Yes, you're right. You can of course travel on the hypotenuse even if you're not oriented along it. I was probably stuck in some fixed front wheel thinking. I w

Yes, you're right. You can of course travel on the hypotenuse even if you're not oriented along it. I was probably stuck in some fixed front wheel thinking. I would think it's a lot easier to get the the proportion of lateral speed exactly right if you're aimed along the hypotenuse though.

yellowapple 6y ago
True. Still, if you wanted to get really exact about it, you could surely work it out mathematically (i.e. by making sure your velocity components are proportional to your distance components). So for example, with the simulator loaded up in a tab right now, after lining up the rotation, I'm seeing: X | 200.0 m Y | 12.0 m Z | 30.0 m So if I then apply an X thrust of 20 m/s, Y thrust of 1.2 m/s, and Z thrust of 3.0 m/s, then I should travel along the hypotenuse and reach the docking port in 10 seconds. Likewise, a thrust of X=2,Y=0.12,Z=0.3 would get me there in 100 seconds (and X=200,Y=12,Z=30 would get me there in an insane single second). Of course, some corrections will be necessary along the way to account for small differences between my orbit and the target orbit (which is more relevant the longer it takes for you to get to the target), and the velocity change ain't instantaneous so I'll need to adjust for that, too (making 10s or 1s runs kinda implausible with the current interface, unless perhaps I do some kind of browser-level scripting to click the buttons and read the numbers). Crucially, this makes it feasible for a computer to do automatically (though automated docking tends to stop shy of actually docking from what I understand, instead using CanadArm to grab the craft and put it on the dock). You're right that aiming along the hypotenuse makes this a little bit easier to eyeball, but it also makes it a bit harder in other respects since now you'll have to adjust both rotation and translation along the way to stay along that slightly-curving hypotenuse.

yellowapple 6y ago

True. Still, if you wanted to get really exact about it, you could surely work it out mathematically (i.e. by making sure your velocity components are proportional to your distance components). So for example, with the simulator loaded up in a tab right now, after lining up the rotation, I'm seeing: X | 200.0 m Y | 12.0 m Z | 30.0 m So if I then apply an X thrust of 20 m/s, Y thrust of 1.2 m/s, and Z thrust of 3.0 m/s, then I should travel along the hypotenuse and reach the docking port in 10 seconds. Likewise, a thrust of X=2,Y=0.12,Z=0.3 would get me there in 100 seconds (and X=200,Y=12,Z=30 would get me there in an insane single second). Of course, some corrections will be necessary along the way to account for small differences between my orbit and the target orbit (which is more relevant the longer it takes for you to get to the target), and the velocity change ain't instantaneous so I'll need to adjust for that, too (making 10s or 1s runs kinda implausible with the current interface, unless perhaps I do some kind of browser-level scripting to click the buttons and read the numbers). Crucially, this makes it feasible for a computer to do automatically (though automated docking tends to stop shy of actually docking from what I understand, instead using CanadArm to grab the craft and put it on the dock). You're right that aiming along the hypotenuse makes this a little bit easier to eyeball, but it also makes it a bit harder in other respects since now you'll have to adjust both rotation and translation along the way to stay along that slightly-curving hypotenuse.