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
<_whitenotifier-9244> [Principia] Failure. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4645/
<discord-> S​umguy. — bruh, learn to use the principia GUIs if you're using principia
<discord-> S​kylar (She/Her). — Unless its changed, principia gui takes a bit to get used to but is sufficient
<_whitenotifier-9244> [Principia] eggrobin synchronize pull request #2799: Interrupt the orbit analysis if the mission duration changes - https://git.io/Jkdu9
<_whitenotifier-9244> [Principia] Pending. Build queued… - 
<_whitenotifier-9244> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4646/
<_whitenotifier-9244> [Principia] Failure. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4646/
Mike` has quit [Ping timeout: 198 seconds]
Mike` has joined #principia
Mike` has quit [Ping timeout: 189 seconds]
egg|laptop|egg has quit [Remote host closed the connection]
Mike` has joined #principia
Mike` has quit [Ping timeout: 198 seconds]
Mike` has joined #principia
Mike` has quit [Ping timeout: 198 seconds]
Mike` has joined #principia
UmbralRaptor has joined #principia
UmbralRaptor has quit [Client Quit]
UmbralRaptor has joined #principia
raptop has quit [Read error: Connection reset by peer]
Mike` has quit [Ping timeout: 194 seconds]
Mike` has joined #principia
raptop has joined #principia
raptop has quit [Client Quit]
raptop has joined #principia
UmbralRaptor has quit [Read error: Connection reset by peer]
UmbralRaptor has joined #principia
raptop has quit [Ping timeout: 204 seconds]
UmbralRaptor has quit [Quit: Bye]
UmbralRaptor has joined #principia
raptop has joined #principia
raptop has quit [Client Quit]
raptop has joined #principia
UmbralRaptor has quit [Read error: Connection reset by peer]
<discord-> B​utcher. — Principia flight planner is pretty awesome.
<discord-> B​utcher. — Needs a way to add an orbit worth of time to manoeuvres though.
egg|laptop|egg has joined #principia
<_whitenotifier-9244> [Principia] eggrobin synchronize pull request #2799: Interrupt the orbit analysis if the mission duration changes - https://git.io/Jkdu9
<_whitenotifier-9244> [Principia] Pending. Build queued… - 
<_whitenotifier-9244> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4647/
<discord-> e​gg. — @Butcher working on it
<discord-> e​gg. — (that may mean the tax form will become tax formier though :-p)
<_whitenotifier-9244> [Principia] Success. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4647/
<discord-> B​utcher. — The collapsible manoeuvres help a lot.
<discord-> B​utcher. — @egg if I wrote something to have configurable line styles for the map view would you merge it?
<discord-> e​gg. — in principle I think we want that, at least there is an old issue about it https://github.com/mockingbirdnest/Principia/issues/869
<discord-> e​gg. — via config files I suppose ?
<discord-> B​utcher. — Yes, I think having more things in the gui would not be ideal.
<discord-> B​utcher. — I just want non-dashed predictions.
<_whitenotifier-9244> [Principia] pleroy reviewed pull request #2799 commit - https://git.io/Jkb8i
<_whitenotifier-9244> [Principia] pleroy reviewed pull request #2799 commit - https://git.io/Jkb8P
<_whitenotifier-9244> [Principia] pleroy labeled pull request #2799: Interrupt the orbit analysis if the mission duration changes - https://git.io/Jkdu9
<discord-> B​utcher. — I'll have to get Principia building again.
<discord-> e​gg. — I think you mean flight plan, not prediction
<discord-> B​utcher. — I do
<discord-> B​utcher. — For targeted landings.
<discord-> e​gg. — aah
<discord-> e​gg. — you are going to run into trouble though, because of topography
<discord-> e​gg. — the moon is really far from its 0 altitude in RSS
<discord-> e​gg. — for landings I would really want to:
<discord-> e​gg. — 1. intersect with the topography;
<discord-> e​gg. — 2. show the predicted impact point.
<discord-> e​gg. — 1. could probably be done by drawing the last segment in 3d (we used to draw the whole trajectory in 3d, but that is horrendously expensive)
<discord-> e​gg. — alternatively maybe the best way is to interrogate the game about the altitudes of the below-max-topography segments at regular intervals
<discord-> Z​eusbeer. — Or via a hotkey ingame that opens a menu, I think EVE has something like that
<discord-> Z​eusbeer. — Changeable things that can only be done via changing config files are sad
<discord-> e​gg. — who’s going to maintain the hotkey handling code and the menu drawing code
<discord-> Z​eusbeer. — I don't know how that works :)
<discord-> e​gg. — the point is that keeping features working has a cost ; this is not something that people will use a lot (I expect it to be done less often than, say, adding a J2 to Kerbin, and nobody is suggesting an Kopernicus GUI), so maintaining a UI for that is not going to happen
<discord-> Z​eusbeer. — Alright, it was just my suggestion
<discord-> Z​eusbeer. — ⛈️ 🥚
<discord-> e​gg. — the point is that keeping features working has a cost ; this is not something that people will use a lot (I expect it to be done less often than, say, adding a J2 to Kerbin, and nobody is suggesting a Kopernicus GUI), so maintaining a UI for that is not going to happen (edited)
<discord-> e​gg. — KSP config files, for all their ills, are pretty accessible, reasonably robust (and so low-maintenance for the mod), and with MM you have a great deal of flexibility; using that for little-used customization features (e.g. RSSDateTimeFormatter format choice) or complex customizability that you may want to compose with other things via MM (Kopernicus configuration, Principia & RSSDateTimeFormatter epoc
<_whitenotifier-9244> [Principia] eggrobin synchronize pull request #2799: Interrupt the orbit analysis if the mission duration changes - https://git.io/Jkdu9
<_whitenotifier-9244> [Principia] Pending. Build queued… - 
<_whitenotifier-9244> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4648/
<discord-> B​utcher. — I was not planning to write a new pop up gui anyway. 😆
<discord-> B​utcher. — Also I can cope with the topography issues if I can get a reasonable estimate of where the orbit crosses area level.
<discord-> e​gg. — yeah, I guess that can be a stopgap. I wonder how to properly address the issue longer-term though
<discord-> B​utcher. — For actually hitting a waypoint landings I do correction during descent anyway, so the requirement is being close enough for that.
<_whitenotifier-9244> [Principia] Failure. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4648/
<discord-> B​utcher. — Perhaps only do 3d plotting below the safe altitude?
<discord-> B​utcher. — Although in a low but not impacting orbit that could get expensive.
<_whitenotifier-9244> [Principia] eggrobin commented on pull request #2799: Interrupt the orbit analysis if the mission duration changes - https://git.io/Jkbru
<discord-> e​gg. — yeah, whereas asking the game for topography below the trajectory can be done as a one-off task when the flight plan changes
<_whitenotifier-9244> [Principia] Pending. Build queued… - 
<_whitenotifier-9244> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4649/
<discord-> e​gg. — (obviously there is no need to do that for histories, since those tend not to be underground)
Iskierka has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
<_whitenotifier-9244> [Principia] Success. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4649/
<_whitenotifier-9244> [Principia] Tutul- commented on issue #2788: [Question] Recommanded tool to simulate n-body to test modified system - https://git.io/Jkb17
egg|laptop|egg has joined #principia
<_whitenotifier-9244> [Principia] eggrobin closed pull request #2799: Interrupt the orbit analysis if the mission duration changes - https://git.io/Jkdu9
<_whitenotifier-9244> [Principia] eggrobin pushed 12 commits to master [+0/-0/±50] https://git.io/JkbD8
<_whitenotifier-9244> [Principia] eggrobin 3aa692e - Cancel the analysis if the mission duration changes
<_whitenotifier-9244> [Principia] eggrobin 5208b1d - make the orbit analyser interruptible
<_whitenotifier-9244> [Principia] eggrobin 3bac1c4 - flow once
<_whitenotifier-9244> [Principia] ... and 9 more commits.
<_whitenotifier-9244> [Principia] eggrobin commented on issue #2788: [Question] Recommanded tool to simulate n-body to test modified system - https://git.io/Jkbd4
<_whitenotifier-9244> [Principia] pleroy opened pull request #2800: Change the apodization functions to be centred - https://git.io/JkbFw
<_whitenotifier-9244> [Principia] Pending. Build queued… - 
<_whitenotifier-9244> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4650/
<_whitenotifier-9244> [Principia] Failure. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4650/
<_whitenotifier-9244> [Principia] pleroy synchronize pull request #2800: Change the apodization functions to be centred - https://git.io/JkbFw
<_whitenotifier-9244> [Principia] eggrobin labeled pull request #2800: Change the apodization functions to be centred - https://git.io/JkbFw
<_whitenotifier-9244> [Principia] Pending. Build queued… - 
<_whitenotifier-9244> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4651/
<_whitenotifier-9244> [Principia] Tutul- closed issue #2788: [Question] Recommanded tool to simulate n-body to test modified system - https://git.io/Jkug8
<_whitenotifier-9244> [Principia] Tutul- commented on issue #2788: [Question] Recommanded tool to simulate n-body to test modified system - https://git.io/Jkbpu
<_whitenotifier-9244> [Principia] Failure. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4651/
<_whitenotifier-9244> [Principia] pleroy commented on pull request #2800: Change the apodization functions to be centred - https://git.io/JkNvf
<discord-> e​gg. — @Butcher I am thinking of having a small blurb, e.g., « highly eccentric semisynchronous orbit » that describes the current orbit for the analyser (so that you can get some situational awareness without having the giant analysis page open at all times, and also to describe coasts when I add analysis to the flight plan—a prereq for the +1 rev. feature). Do you have any thoughts on what properties
<_whitenotifier-9244> [Principia] Pending. Build queued… - 
<_whitenotifier-9244> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4652/
<discord-> e​gg. — equatorial/nothing (probably not worth calling most orbits prograde or inclined)/polar/retrograde ? circular for e < 0.01 or so? what would be a good threshold for calling something highly eccentric?
<discord-> e​gg. — and then subsynch (specifically calling out semisynch)/synch/supersynch, and stationary if you are equatorial, circular, and synchronous?
<discord-> e​gg. — @Butcher I am thinking of having a small blurb, e.g., « highly eccentric semisynchronous Earth orbit » that describes the current orbit for the analyser (so that you can get some situational awareness without having the giant analysis page open at all times, and also to describe coasts when I add analysis to the flight plan—a prereq for the +1 rev. feature). Do you have any thoughts on what prop
<discord-> B​utcher. — I'm not sure on a good threshold for highly eccentric, I don;t use them much it has to be said, I'm normally either on a hyperbolic flyby or something much closer to circular.
<discord-> e​gg. — yeah a lot of the fancier orbits don’t have much use with the current state of career
<discord-> e​gg. — something something KC something @Sir Mortimer
<discord-> B​utcher. — Even sun synch gets used like once.
<discord-> e​gg. — yeah and probably not even because it is sun-synch
<discord-> B​utcher. — There is specific contract for sun synch, but it;s just 97° with a reasonable period, it doesn't actually have to be synched.
<discord-> e​gg. — yeah, it’s just « go to that orbit » with flavour text
<discord-> B​utcher. — As they all are really.
<discord-> e​gg. — a laudable effort, but not really interestingly about the sun-synchronicity
<discord-> e​gg. — (since the primary reasons for sun-synch in real life are lighting conditions in observation, which aren’t modelled, and power-hungry instruments, which aren’t a concern with instascience)
<discord-> e​gg. — (morning or afternoon orbits for the former, crepuscular for the latter)
<discord-> B​utcher. — Kerbalism lacks insta science so power is a concern.
<discord-> B​utcher. — But the RO way is just moar solar.
<discord-> e​gg. — lol
<discord-> e​gg. — similarly the ground track recurrence dance is of no concern if you do not need to regularly observe places, or to always have an opportunity to observe something « soon »
<discord-> B​utcher. — Indeed, the closest ground track are to an issue is doing scansat stuff, and that just requires eventual coverage.
<discord-> B​utcher. — I believe newer versions require daylight though.
<discord-> e​gg. — For equatorial/polar, would 1-degree tolerances make sense? (call sub-degree orbits equatorial, super-89 sub-91 polar)
<discord-> B​utcher. — Yes, that would be reasonable.
<discord-> B​utcher. — 1° is fairly loose, but adequate as a descriptor I think.
<discord-> l​pg. — Sadly kerbalism doesn't acknowledge sun-sync orbits for unloaded vessel solar exposure purposes
<discord-> e​gg. — huh? I thought it was supposed to?
<discord-> B​utcher. — It does in slow mode, but once you get to analytical mode it just assumes equatorial.
<discord-> e​gg. — aaaaaaa
<_whitenotifier-9244> [Principia] Failure. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4652/
egg|laptop|egg_ has joined #principia
egg|laptop|egg has quit [Ping timeout: 198 seconds]
egg|cell|egg has quit [Ping timeout: 378 seconds]
<discord-> e​gg. — @Butcher how much drift would you allow to still call an orbit « synchronous » ?
<discord-> B​utcher. — Hmm I'm not sure.
<umbralraptop> Grab the elements of some actual sats, and use their drift?
<discord-> e​gg. — so for a GPS satellite (SVN G063, in plane D, slot 2) I’m getting a drift of 0°.029 over 10 days
<umbralraptop> 1.2 milliarcsec/sec
<umbralraptop> ...I suppose we should round up if anything
<umbralraptop> also, how difficult is that to pull off with the current UI?
umbralraptop is now known as raptor
raptor is now known as umbralraptor
umbralraptor is now known as umbralraptop
<discord-> e​gg. — 0°.035 on a 北斗 GEO sat, 0°.35 北斗 IGSO sat, 0°.71 みちびき QZO, 0°.051 みちびき GEO
<discord-> B​utcher. — IGSO?
<discord-> e​gg. — Inclined GeoSynchronous Orbit
<discord-> B​utcher. — Inclined geosynch?
<discord-> e​gg. — eggsactly
<discord-> C​hatz. — I managed to impact the moon in my rp-1 career with principia, but replicating it is hard - it looks like the inclination keeps dropping. Do I just need more delta V or is there something I'm missing here?
<discord-> S​umguy. — might be procession
egg|laptop|egg_ has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
<discord-> e​gg. — not to be confused with precession https://upload.wikimedia.org/wikipedia/commons/b/b6/Lunar_standstill.GIF
<discord-> C​hatz. — Yeah, so what I'm doing is launching into the moon's LAN and lowering my inclination a couple degrees to my parking orbit - is there anything better I should be doing?
egg|laptop|egg has quit [Remote host closed the connection]
<discord-> S​umguy. — lolwhoops
<discord-> m​oar ssto. — that's some big perturbation
<discord-> [​experimentalshells?]. — launch into plane of moon, not LAN
<discord-> D​amien. — launching into plane of moon is often not possible
<discord-> [​experimentalshells?]. — then wait for when its possible
<discord-> D​amien. — once every 18yrs?
<discord-> [​experimentalshells?]. — no
<discord-> [​experimentalshells?]. — twice every month
<discord-> D​amien. — with principia?
<discord-> [​experimentalshells?]. — think of the Moon's orbit as somewhat of a plane
<discord-> [​experimentalshells?]. — it intersects the Earth through the center
<discord-> [​experimentalshells?]. — the Earth is rotating, but its axis of rotation is not normal to that plane
<discord-> C​hatz. — Yeah there's no way I can launch into the plane of the moon
<discord-> D​amien. — you can't launch directly into an orbit that is lower than your latitude, which the moon's plane often is
<discord-> D​amien. — you can intercept its orbit, but not by launching into a coplanar one
<discord-> [​experimentalshells?]. — oh, maybe I've been playing too much kourou/wenchang
<discord-> D​amien. — oh yeah from Kourou you're fine 😄
<discord-> [​experimentalshells?]. — oh, maybe I've been playing too much kourou/wenchang, whoops (edited)
<discord-> D​amien. — but from the default Cape, it's often a polar orbit transfer
<discord-> D​amien. — or some other tricky trajectory
<discord-> C​hatz. — but polar I have to park for a while, right?
<discord-> D​amien. — read up on Korolev and the Luna missions
<discord-> D​amien. — and get ready to rage at direct ascent missions
<discord-> D​amien. — and get ready to rage at direct ascent (edited)
<discord-> D​amien. — it is possible with no parking orbit, but it's lots of trial and error and timing
<discord-> D​amien. — I believe @Butcher has a script for KOS that may help
<discord-> D​amien. — If you read up on the Pioneer 0/1 missions they were lunar probes launched from the Cape
<discord-> D​amien. — failed, but the plans worked
<discord-> D​amien. — I recreated it once and then stopped playing ksp for months
<discord-> D​amien. — every 18yrs? (edited)
<discord-> B​utcher. — I do indeed.
<discord-> B​utcher. — You run that and launch immediately into the orbit specified.
<discord-> B​utcher. — It has not failed me yet.
<discord-> B​utcher. — No waiting, 3120-3150 m/s intercept trajectories.
<discord-> S​tonesmile. — I think the question was about a direct ascent to the moon, which I wouldn't recommend
<discord-> B​utcher. — Direct ascent is a pain.
<discord-> S​tonesmile. — That script otoh is *really* handy
<discord-> D​amien. — > which I wouldn't recommend
<discord-> D​amien. — agreed
<discord-> B​utcher. — I have a direct ascent script, but it's more complicated to get a good intercept and there's a limited window each month.
<discord-> B​utcher. — This script tends to work out cheaper as you can launch into less inclined parking orbits.
<discord-> l​pg. — > but polar I have to park for a while, right?
<discord-> l​pg. — this question _may_ mean "as opposed to direct ascent", but I think it's more likely that it meant "park for days instead of for at most one orbit"
<discord-> l​pg. — Because people used to launching into the plane of the moon generally don't have direct ascent in mind
<discord-> B​utcher. — Worst case you could need to park for two weeks I think?
<discord-> e​gg. — The Cape is a silly place, launch from somewhere nicer :-p
<discord-> l​pg. — if you launch into the wrong LAN, yes
<discord-> B​utcher. — From Polar I mean.
<discord-> B​utcher. — @egg I use VAFB.
<discord-> l​pg. — same thing
<discord-> B​utcher. — Next play is definitely Mahia.
* discord- e​gg. — looks that up
<discord-> e​gg. — https://fr.wikipedia.org/wiki/Mahia ??
<discord-> C​hatz. — Can you explain what this is actually doing? I don't understand
<discord-> S​tonesmile. — Mahia is onöy -40 deg, gotta do better
<discord-> S​tonesmile. — Mahia is only -40 deg, gotta do better (edited)
<discord-> S​tonesmile. — @egg Mahia is where Rocket labs launch complex in NZ is located
<discord-> e​gg. — ah
<discord-> S​tonesmile. — @Chatz It creates a plane containing three points; the rocket, the moon in four days, and the center of Earth. It then returns the inclination to launch into to get into that plane
<discord-> C​hatz. — do I still launch into the LAN of the moon?
<discord-> S​tonesmile. — You are supposed to launch as soon as the script is run, launching into the inclination it tells you
<discord-> S​tonesmile. — You can also use a script from itsRyan that warps until you can launch directly east with MJ PVG and starts the ascent; https://github.com/ryanc55/KOS-Scripts/blob/master/moonlaunchwindow.ks
egg|laptop|egg has joined #principia
<discord-> e​gg. — and 0°.029 GPS, over 10 days
<discord-> e​gg. — so per day, that is 0°.0035 on the 北斗 GEO sat, 0°.035 北斗 IGSO, 0°.071 みちびき QZO, 0°.0051 みちびき GEO, 0°.0029 GPS
<discord-> S​tonesmile. — I assume you are *not* going to use ESAs definition of a polar orbit?
<discord-> e​gg. — what is that?
<discord-> S​tonesmile. — They think that 70 deg inclination is 'polar'
<discord-> e​gg. — depends where
<discord-> e​gg. — there is a page that says 20-30 from the pole, but there also is https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-5p/orbit which calls 98.7° "high inclination" and "near-polar"
<discord-> S​tonesmile. — I guess they go by the polar circle, which is at 66 deg on that page?
<discord-> B​utcher. — No, you just launch immediately.
<discord-> C​hatz. — got it, I'll have to play around with that. The attempts I'm doing now are to launch into the LAN of the moon and ending up being 5 or 6 degrees inclination off
<discord-> B​utcher. — You end up with something like this:
<discord-> e​gg. — back to the (sub)synchronous longitudes, the criterion would be 0°.1 per day? that means, in theory, 36° drift over a year (but then a monthly control cycle is not unreasonable, and that keeps you within a couple of degrees, which is consistent with the criterion we chose for inclination)
<discord-> l​pg. — > got it, I'll have to play around with that. The attempts I'm doing now are to launch into the LAN of the moon and ending up being 5 or 6 degrees inclination off
<discord-> l​pg. — there may still be some confusion here. there's _no_ expectation, with any of these methods, to end up with any particular inclination relative to the moon.
<discord-> B​utcher. — Nor should you need to. You can launch into any lunar orbit you need with minor tweaks of earth departure velocity and timing.
<discord-> C​hatz. — understood, but if I launch into the LAN of the moon, I'd want to reduce the relative inclination, right?
<discord-> B​utcher. — e.g. I just tweaked that TLI burn shown by 0.692 m/s and 64 seconds and instead of impact I'm aiming for a high polar orbit.
Iskierka has quit [Ping timeout: 194 seconds]
<discord-> e​gg. — hmm, that 北斗 GEO satellite has an inclination of about 1°.42, so 1° is way too tight for equatoriality
<discord-> e​gg. — OK let’s say 80° to 100° for polar (this is a short description so we’re not going to explicitly say quasi, and they are definitely called at least quasi-polar in that range)
<discord-> e​gg. — OK but on the other hand, the QZSS specification says 0 ± 0.1 degrees for the latitude of their GEO satellite
<discord-> e​gg. — Capderou has the sentence
<discord-> e​gg. — > À partir de 1990, les satellites météorologiques sont sur une orbite quasi équatoriale (i < 1.5°)
<discord-> e​gg. — and
<discord-> e​gg. — > Si i = 0° (ou i = 180°, mais ce cas n'a jamais été rencontré), on parle d'orbite *équatoriale*, et pour i inférieur à 10°, d'orbite *quasi équatoriale*.
<discord-> S​tonesmile. — How far from 0° can a geo sat be before it causes issues for ground tracking? (I assume the answer is
<discord-> S​tonesmile. — How far from 0° can a geo sat be before it causes issues for ground tracking? (I assume the answer is 'it depends') (edited)
<discord-> e​gg. — probably it depends, and also not all GEO sats are GEO because of dishes on houses
<discord-> e​gg. — e.g. meteorology sats, GNSS sats, etc. don’t care about your parabolae
<discord-> e​gg. — (and house dishes are very lax aiui)
<discord-> S​tonesmile. — How set in stone are these definitions when you have implemented them? If a different consensus is reached later, could it be changed?
<discord-> e​gg. — yes, but since everything is fuzzy it would be changing a fuzzy thing to another fuzzy thing :D
<discord-> e​gg. — another way to look at it would be that the lowest-inclination doglegless launch from Kourou should probably be classified as equatorial, so 10° is not insane (Kourou is at 5°.5 or so, right?)
<discord-> S​tonesmile. — If I have understood things correctly, KC might be the driving factor for the definitions?
<discord-> e​gg. — 5°.15
<discord-> e​gg. — nah, those definitions are just to give you a little blurb in Principia to tell you what is going on
<discord-> e​gg. — the goal of KC is precisely to avoid having the contract telling you to be in such-and-such orbit, because that is silly
<discord-> e​gg. — you don’t go into a sufficiently-sun-synchronous orbit because the contract says so and says how synchronous it needs to be, you go there because you get more observation time with appropriate solar angle
Jesin has quit [Quit: Leaving]
<discord-> S​tonesmile. — Yeah, I have already read that doc, looking forward to when sirMortimer has time to put into it
Jesin has joined #principia
<discord-> B​utcher. — It's a bit like a good version of the scansat contracts
<discord-> C​hatz. — @Butcher Just tried out your script - the output was 51 degrees south - that's a couple thousand more delta V to orbit though, right?
<discord-> S​tonesmile. — Should be about 50 m/s more than east
<discord-> S​tonesmile. — (or 100 m/s)
<discord-> C​hatz. — Hmm, 51 degrees south means I put -51 degrees inclination into PVG?
<discord-> S​tonesmile. — Correct
<discord-> C​hatz. — Ok, the burn was way more expensive
<discord-> C​hatz. — it burned somewhat retrograde
<discord-> C​hatz. — let me test again
<discord-> C​hatz. — Ok this burn is looking way better
<discord-> B​utcher. — The most expensive orbit should be polar which is a few hundred m/s more than east.
<discord-> B​utcher. — It will never generate retrograde orbits.
<discord-> C​hatz. — It must have been something I messed up or PVG did then
<discord-> C​hatz. — Second attempt looks fine
<discord-> B​utcher. — Typo in pvg maybe.
<discord-> B​utcher. — Once in orbit make a flight plan of around 5 days, set 3140 m/s tangent and move the time slider until you hit the moon. Might need to tweak the dv slightly depending on where the moon is in its orbit.
<discord-> C​hatz. — These final burns are really tricky for my setup because I just spin stabilize
<discord-> S​tonesmile. — Doing unguided TLI can be done, but being unguided when you get to a parking orbit seems near impossible, if that is what you do
<discord-> C​hatz. — Yeah its the TLI that's unguided
<discord-> C​hatz. — I hit it on my first lunar mission, but have failed a few more since
<discord-> C​hatz. — I try and just plan a maneuver to use all my delta v and then fine-tune with forward/backwards rcs but sometimes I can't get the periapsis lower than a few million meters
<discord-> S​tonesmile. — That's the limitations of the early tech in RP-1