raptop changed the topic of #principia to: READ THE FAQ: http://goo.gl/gMZF9H; The current version is Gateaux. We currently target 1.8.1, 1.9.1, and 1.10.1. <scott_manley> anyone that doubts the wisdom of retrograde bop needs to get the hell out | https://xkcd.com/323/ | <egg> calculating the influence of lamont on Pluto is a bit silly… | <egg> also 4e16 m * 2^-52 is uncomfortably large
Raidernick has quit [Read error: Connection reset by peer]
Raidernick has joined #principia
egg|cell|egg has quit [Ping timeout: 194 seconds]
egg|cell|egg has joined #principia
egg|laptop|egg has quit [Read error: Connection reset by peer]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
Mike` has quit [Ping timeout: 198 seconds]
Mike` has joined #principia
egg|cell|egg has quit [Ping timeout: 194 seconds]
egg|cell|egg has joined #principia
<discord->
FabioKevin. — Hey, what are ways to notice when you change The sphere of influence of a planet? I have tried the Kerbal Alarm clock method of making an alarm for it, but it might be further behind by a bunch of days. Any ways to deal with this?
<discord->
Butcher. — Just keep an eye on it?
<discord->
Butcher. — Or set an alarm a reasonable distance from the planet by eye.
<discord->
FabioKevin. — Ok, I found out I was using the wrong button for the alarm
<discord->
[experimentalshells?]. — ... why are we discussing changing spheres of influence when this is #principia?
<discord->
FabioKevin. — Well, I needed to get a picture of Minmus in my current ksp save, and I didn't want to accidentally miss it.
<discord->
FabioKevin. — Also so i know when it switches biome for Kerbalism science stuff.
<discord->
FabioKevin. — Also so i know when it switches planet for Kerbalism science stuff. (edited)
<discord->
Butcher. — Hmm, crashy, clicked rebase, principia died with `F1202 09:23:16.854111 15292 discrete_trajectory_body.hpp:644] Check failed: t_min() <= time (-1.02650377386963987e+09 s vs. -nan(ind) s)`
<discord->
Butcher. — On the upside, torque calcs for my ships seem to be working, so I should have fewer problems with slow turns for manoeuvres.
<_whitenotifier-9244>
[Principia] pleroy labeled pull request #2803: Make ephemeris flows interruptible and stop unused prognosticators - https://git.io/JIveT
egg|cell|egg has quit [Ping timeout: 198 seconds]
<discord->
FabioKevin. — Hey, should one go for an inertially fixed point of view when trying to impact something like The Mun?
<discord->
FabioKevin. — Cause I wasn't able to hit Minmus
<discord->
FabioKevin. — Though a bunch of correction burn did help fixing it.
<discord->
FabioKevin. — But I though that the execute manuever in principia would probably have done it with ease.
<discord->
Damien. — @FabioKevin mun centered kerbin aligned when planning the transfer then switch to mun centered inertial to fine tune is how I'd do it
<discord->
FabioKevin. — i'm not doing Mun, I'm doing Minmus in JNSQ, also would the Minmus centered basically be with the view fixed on Minmus, cause that was how I was doing it, though I guess I didn't switch to Minmus centered inertial later on, so I guess I just need to split the manuever?
<discord->
FabioKevin. — @Damien So, do I basically have to split the manuever?
<discord->
Damien. — just, just switch reference frames while you plan it
<discord->
FabioKevin. — Oh, ok
<discord->
Damien. — just switch reference frames while you plan it (edited)
<discord->
Damien. — if you want to hit a specific part of the surface you'd fine tune it with minmus surface fixed
<discord->
Damien. — it's all the same maneuver, you're just viewing it from different perspectives
<discord->
Butcher. — I normally set the manoeuvre frame to kci them plan as @Damien suggests.
<discord->
FabioKevin. — Is it normal to miss by somewhat the target maneuver node trajectory when executed by mechjeb? Asking out of curiosity.
<discord->
Damien. — can't help there, I don't use MJ to execute burns
<discord->
Stonesmile. — MJ Principia node execution assumes no ignition delay, which can cause you to miss
<discord->
FabioKevin. — Wait, non RO Engines have ignition delay?
<discord->
FabioKevin. — Cause I'm currently playing in the JNSQ system
<discord->
Stonesmile. — No, they don't, didn't look close enough 😅
<discord->
FabioKevin. — Any chances there is something that could improve MJ Principia node execution?
<discord->
FabioKevin. — Cause I honestly don't wanna do it by hand
<discord->
Stonesmile. — Not really, MJ can only read the dV of the node and times
<discord->
Stonesmile. — (As far as I know)
<discord->
FabioKevin. — Aw man, that means I will have to pretty much remove Principia from my game and possibly have to restart my career due to planets switching places which ends up messing up the Kerbalism science.
<discord->
Stonesmile. — A node executor should be fairly close, so you should be able to fix the error with RCS or similar
<discord->
FabioKevin. — Then I guess I'll add RCS.
<discord->
FabioKevin. — Though lowering the Engine thrust also does the same, and faster.
<discord->
DRVeyl. — Sounds like your problem isn't "MJ is not accurate enough", it is "that engine is too powerful to easily hit a 2m/s margin." TWR of 3, so missing by 2.7m/s is a 0.1 second error. The minimum -possible- error time is 0.02s.
<discord->
DRVeyl. — (So maybe there's something else there, if MJ shouldn't miss by more than 1 frame's time.)
<discord->
FabioKevin. — Well, lowering the engine Thrust through that engine limiter slider does help.
<discord->
FabioKevin. — Though, I don't know what one would do if they didn't have the luxury of lowering the engine Thrust through the engine limiter.
<discord->
FabioKevin. — Though, I don't know what one would do if they didn't have the luxury of lowering the engine Thrust through the engine limiter in Principia (edited)
<discord->
DRVeyl. — They would correct/fine-tune with RCS. Or mid-course correction burn later in the trajectory. You'd have trouble hitting that burn target in stock, or by hand, if you couldn't limit engine thrust/use tiny amount of throttle also.
<discord->
DRVeyl. — (tiny amount of throttle becomes a different problem -- that the burn wasn't spread out over the time period as expected. Irrelevant on a correction burn in the middle of nowhere, more important when you're slinging around a planet.)
<discord->
DRVeyl. — ~~(tiny amount of throttle becomes a different problem -- that the burn wasn't spread out over the time period as expected. Irrelevant on a correction burn in the middle of nowhere, more important when you're slinging around a planet.)~~ Have to think about that some more. On one hand, vast majority of the burn was done as expected. OTOH, erroring by "spool-up time" producing a significant resul
<discord->
lpg. — Better Time Warp with a <1x warp factor will help with the "1 frame's time" aspect
<discord->
FabioKevin. — I don't know how to timewarp below 1x
<discord->
scimas. — "Better Time Warp" that's a mod
<discord->
FabioKevin. — Completely forgot to install that
egg|cell|egg has quit [Ping timeout: 198 seconds]
<_whitenotifier-9244>
[Principia] pleroy opened pull request #2804: Use Clenshaw-Curtis in the piecewise Poisson series inner product - https://git.io/JIL3l
<_whitenotifier-9244>
[Principia] pleroy synchronize pull request #2804: Use Clenshaw-Curtis in the piecewise Poisson series inner product - https://git.io/JIL3l
egg|laptop|egg has quit [Remote host closed the connection]
egg|cell|egg has joined #principia
egg|laptop|egg has joined #principia
<_whitenotifier-9244>
[Principia] eggrobin labeled pull request #2804: Use Clenshaw-Curtis in the piecewise Poisson series inner product - https://git.io/JIL3l
<_whitenotifier-9244>
[Principia] pleroy closed pull request #2804: Use Clenshaw-Curtis in the piecewise Poisson series inner product - https://git.io/JIL3l
<_whitenotifier-9244>
[Principia] pleroy pushed 11 commits to master [+0/-0/±37] https://git.io/JILuf