<lamont>
wb99999999: if you put RCS on that stage and have it enabled, then PEG will cut the throttle 2 ticks before you go over you target and then trim out the burn on RCS
<lamont>
and we should really support constant-accelleration phases (throttle down) and better engine programming
<awang>
MJ learns kOS?
ProjectThoth has quit [Ping timeout: 200 seconds]
<awang>
How well does the finishing a burn on RCS thing work when the upper has really high burnout TWR and RCS has really low TWR?
<awang>
Seems like it'd take a lot of RCS to compensate
<awang>
(disclaimer: Still haven't gotten around to trying it)
<lamont>
not really, and it fixes the dV and doesn’t really run PEG
<lamont>
i’ve been testing it with 10G burnout TWR titan-2s
<lamont>
even at like 100:1 ratio, 2 ticks = 0.04 secs => 4 secs of RCS
<awang>
Ah
<awang>
Good point
<lamont>
i could maybe do some tweaking to get that down to 1 tick, but i’m using constant accel math in a very non-constant accel phase of the burn, so i’d have to rub some tsiolkovsky on it
<awang>
How much TWR does RCS get on average, anyways?
<awang>
Rubbing some Tsiolkovsky on it or adding thrust integrals?
<awang>
Or both?
<lamont>
i think the numbers are in N of thrust so they’re in hundreds-ish of N?
<lamont>
just rocket eq
<lamont>
it doesn’t support turning so no thrust integrals
<lamont>
other than the first L integral which is just delta-v
<awang>
I see
<Bornholio>
lamont what is newest test version o' PEG, may have time to fly rockets over christmas
stratochief has quit [Remote host closed the connection]
<Starwaster>
lamont: So, I was looking into the gimbal/gimbal response speed issue as to how it relates to control sensitivity in MJ and I'm thinking that the problem is actually with gimbal response speed values that are just too high. That probably results in some of the PID vectors being scaled too high
<Starwaster>
I'm talking across the board for just about every mod that sets gimbal response speeds... typically 10-16 or higher when it should be 0.1 or so
<Starwaster>
I patched my gimbals to 0.1 response speed and so far it looks like less wiggling on ascent by MJ
<Starwaster>
lamont: also, (embarrassment) I set my PEG start after staging incorrectly because I totally forgot for an evening that staging numbers start HIGH not low
<lamont>
heh yeah
<Starwaster>
so that's why it was saying CONVERGED and still being stuck in unguided gravity turn. It was literally doing exactly what I told it to do
<lamont>
oh that
<lamont>
yeah
<Starwaster>
proving once again that computers do what you TELL them to do, not what you WANT them to do
<lamont>
yeah, i’m also somewhat deeply dissatisfied with my UX there
<lamont>
“start PEG *AFTER* stage” but maybe it should be at the stage
<soundnfury>
inb4 lamont adds a "DWIM" button to MJ
<Starwaster>
awang: rubbing Tsiolkovsky on it? Is that fresh ground?
<lamont>
because yeah gets into what is before/after and the number go up, so mentally after could be larger numbers, not smaller, but what i mean is time…
<Bornholio>
starwaster what code are you using to set gimbals to flat value?
<lamont>
the bit that would need tsilokovsky is the logic that tries to figure out if in the next tick you are going to add enough dV to overshoot your target or not, the core bits of PEG have it baked in
<Qboid>
[#951] title: Enhancement: Declarative Programmable Autostaging | There's a bunch of rockets that we can't fly entirely correctly with PEG or autostaging because they need special things to happen which violating the "simple" Kerbal-style autostaging rules. For example:... | https://github.com/MuMech/MechJeb2/issues/951
<awang>
"unplanned rated power readjustment"
<awang>
I was more thinking throttling down near the end of the orbital insertion burn if that helps accuracy
<lamont>
limiting acceleration would do it
<lamont>
its possible PEG could be wired up to the existing acelleration limiter
<lamont>
but lots of RO engines don’t throttle at all, so i worked on making that more accurate to begin with
<awang>
Are uppers normally throttleable?
<awang>
Or is that generally limited for boosters for max Q/acceleration limiting stuff?
<awang>
Since uppers are normally lower TWR
<lamont>
hrm talking to the wrong person
<lamont>
i would have to crack open the RO configs and go look myself
<soundnfury>
afaik in RO the late-period RL10 is about the only throttleable upper stage, unless you use an LLDE or an XLR99 as an upper stage engine I suppose
<wb99999999>
hmm
<soundnfury>
s/LL/LM
<Qboid>
soundnfury meant to say: afaik in RO the late-period RL10 is about the only throttleable upper stage, unless you use an LMDE or an XLR99 as an upper stage engine I suppose
<wb99999999>
why would he want a throttling upperstage?
<soundnfury>
awang was talking about throttling down at end of burn to get better shut-off accuracy
<wb99999999>
I'd suggest RCS
<wb99999999>
you need some for ullage anyway
Bornholio has quit [Remote host closed the connection]
ProjectThoth has joined #RO
<soundnfury>
wb99999999: apparently they already did that
wb99999999 has quit [Ping timeout: 180 seconds]
jclishman has joined #RO
<jclishman>
How far along is RP-1 development?
Wetmelon has quit [Ping timeout: 186 seconds]
<ProjectThoth>
jclishman: It was developed in the 1950s.
<jclishman>
ProjectThoth: ಠ_ಠ
wb99999999 has joined #RO
wb99999999 has quit [Ping timeout: 180 seconds]
Wetmelon has joined #RO
aradapilot has quit [Ping timeout: 207 seconds]
ferram4_ has joined #RO
ferram4 has quit [Ping timeout: 200 seconds]
<soundnfury>
jclishman: there are still outstanding bugs (mainly in 'naut training, which only NK knows how to fix), and most non-procedural tanks aren't cost/entryCost balanced
<jclishman>
alright, cool
<soundnfury>
but it's definitely playable despite that
<jclishman>
i haven't been able to find a github/forum link!