egg changed the topic of #principia to: Logs: https://esper.irclog.whitequark.org/principia | <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|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
<queqiao-_> ⟨e​gg⟩ similar magic trick for grid interval, Google орбита "spot" "108,6 км"
<queqiao-_> ⟨e​gg⟩ > расстояние между примыкающими трассами орбиты
<queqiao-_> ⟨e​gg⟩ a bit lengthy
<queqiao-_> ⟨v​evladdd⟩ Plz don't forget про не-астрофизиков
<queqiao-_> ⟨e​gg⟩ nah, principia should turn you into an астрофизик and teach you how to speak like one
<queqiao-_> ⟨e​gg⟩ using noodles
<queqiao-_> ⟨v​evladdd⟩ Oh noodles. I went to sleep on Saturday and woke up on Friday after a pack of Chinese noodles lol
<queqiao-_> ⟨e​gg⟩ hmm,
<queqiao-_> ⟨e​gg⟩ > Расстояние между спутниковыми трассами для TOPEX/Poseidon составляет 315 км и 85 км для ENVISAT.
<queqiao-_> ⟨e​gg⟩ and
<queqiao-_> ⟨e​gg⟩ > Межвитковое расстояние по экватору для КА «Jason-2» составляет 315 км.
<queqiao-_> ⟨v​evladdd⟩ 2 is shorter — means better
<queqiao-_> ⟨e​gg⟩ nope, because it is misleading: межвитковое расстояние по экватору is used here to mean Витковое смещение на экваторе https://findpatent.ru/patent/232/2327112.html
<queqiao-_> ⟨e​gg⟩ межвитковое is not specific enough; между примыкающими трассами is nice but looooooong
<queqiao-_> ⟨e​gg⟩ it is the spacing between adjacent tracks (in space), not the spacing between one track and the next
<queqiao-_> ⟨e​gg⟩ it is the spacing between adjacent tracks (in space), not the spacing between one track and the next (in time) (edited)
<queqiao-_> ⟨e​gg⟩ that thing cites *Инженерный справочник по космической технике* so I guess I should look into that
<queqiao-_> ⟨v​evladdd⟩ Какой у вас (тебя?) уровень русского уже?
<queqiao-_> ⟨e​gg⟩ I don’t speak russian, I’m just trying to get the technical terms right :-p
<queqiao-_> ⟨e​gg⟩ (same as I did for Chinese which I don’t speak either; it’s very hard to nonspecialists to figure out what the correct terminology is for the more obscure concepts, so at some point survey a bunch of papers)
<queqiao-_> ⟨e​gg⟩ (same as I did for Chinese which I don’t speak either; it’s very hard to nonspecialists to figure out what the correct terminology is for the more obscure concepts, so at some point I just survey a bunch of papers) (edited)
<queqiao-_> ⟨e​gg⟩ > Расстояние между подспутниковыми трассами на экваторе составило около 315 км (см. рис. 2.11).
<queqiao-_> ⟨e​gg⟩ Расстояние между подспутниковыми трассами на экваторе is very correct but not exactly going to fit in the UI :-p
<queqiao-_> ⟨e​gg⟩ it looks like in Chinese I just went with a calque for grid interval instead of a term attested in that context, which is odd; but I guess I could do the same and go for интервал сетки
<queqiao-_> ⟨e​gg⟩ I like the term grid in grid interval, it is very visual
<queqiao-_> ⟨e​gg⟩ ball of yarn interval
<queqiao-_> ⟨e​gg⟩ @von Kerman FYI ascending/descending pass is восходящий/нисходящий *виток*, see http://www.dspa.ru/articles/year2018/jour18_3/jour18_3.pdf
egg|laptop|egg has quit [Remote host closed the connection]
<raptop> grid interval sounds CFD-related
UmbralRaptop has joined #principia
<queqiao-_> ⟨v​on Kerman⟩ I'm trying to find the definition of виток орбиты, and it seems to be defined as part of orbit, not a node.
<queqiao-_> ⟨v​on Kerman⟩ For example: https://www.sibsau.ru/sveden/edufiles/127957/
<queqiao-_> ⟨v​on Kerman⟩ "Поскольку виток представляет собой
<queqiao-_> ⟨v​on Kerman⟩ замкнутую кривую, то за его начало, вообще говоря, может быть принята любая
<queqiao-_> ⟨v​on Kerman⟩ характерная точка орбиты. Однако для наклонных эллиптических орбит за
<queqiao-_> ⟨v​on Kerman⟩ начало витка принято считать момент прохождения КА перигея орбиты."
<queqiao-_> ⟨v​on Kerman⟩ "As виток is a closed curve, any characteristic point of the orbit can be taken as its beginning...". etc.
<queqiao-_> ⟨v​on Kerman⟩ Восходящий виток is therefore part of orbit from the most "southern" point of orbit (over the Southern hemisphere) to the most "northern" point of orbit, if I understand it correctly.
<queqiao-_> ⟨v​on Kerman⟩ But what the orbit analyzer shows looks like the longitude of the ascending and descending node, isn't it?
<queqiao-_> ⟨v​on Kerman⟩ OK, I see the word "longitude" on the line above it, so it should be clear anyway, no questions to восходящий/нисходящий виток.
egg|laptop|egg has joined #principia
<queqiao-_> ⟨e​gg⟩ in a weird sense you could say that, but it is terrestrial longitude rather than celestial longitude so I am staying away from that phrase. In any case the English text here is not referring to the node here, but rather above where it says *equatorial crossing*
<queqiao-_> ⟨e​gg⟩ you have
<queqiao-_> ⟨e​gg⟩ Longitudes of equatorial crossings of revolution \#n
<queqiao-_> ⟨e​gg⟩ Ascending pass: [some longitude]
<queqiao-_> ⟨e​gg⟩ Descending pass: [some longitude]
<queqiao-_> ⟨e​gg⟩ so even if you wanted to put *node* somewhere, it would be instead of equatorial crossing; pass really means pass (which is indeed a chunk of a revolution)
<queqiao-_> ⟨v​on Kerman⟩ Yes, виток looks correct when I look at all three lines together
<queqiao-_> ⟨e​gg⟩ yeah, translating without context is hard
<queqiao-_> ⟨e​gg⟩ and the fact that the orbit analyser is full of super obscure things makes things even harder
<queqiao-_> ⟨e​gg⟩ indeed: the Восходящий виток is the segment where you go North, and the other one is the segment where you go south
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
<queqiao-_> ⟨e​gg⟩ @von Kerman what does отн. stand for in перицентр отн. <<1>>?
<queqiao-_> ⟨v​on Kerman⟩ относительно - relative to
<queqiao-_> ⟨e​gg⟩ (I need to add the correct case to that <<1>> but since I don’t know russian I can’t expand abbreviations)
<queqiao-_> ⟨v​on Kerman⟩ относительно Земли
<queqiao-_> ⟨e​gg⟩ so <<gen:1>>
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
<queqiao-_> ⟨e​gg⟩ oooh I am going to have fun with `#principia_FlightPlan_CoastInOrbit = Полёт на <<1>> в течение <<2>>` >_<
<queqiao-_> ⟨e​gg⟩ um
<queqiao-_> ⟨e​gg⟩ oooh I am going to have fun with `#Principia_FlightPlan_CoastInOrbit = Полёт на <<1>> в течение <<2>>` >_< (edited)
<queqiao-_> ⟨e​gg⟩ <<1>> is the description of the orbit, *e.g.*, круговая экваториальная орбита вокруг Земли
<queqiao-_> ⟨e​gg⟩ but obviously that all needs to become genitive :-p
<queqiao-_> ⟨v​on Kerman⟩ Actually, if you don't change cases at all, the text is still readable
<queqiao-_> ⟨e​gg⟩ на + nominative is incorrect, right?
<queqiao-_> ⟨v​on Kerman⟩ Yes
<queqiao-_> ⟨e​gg⟩ OK, then it’s incorrect, I don’t care if you can read it, it must be made correct
<queqiao-_> ⟨v​on Kerman⟩ Correct is Полёт на круговой экваториальной орбите вокруг Земли
<queqiao-_> ⟨e​gg⟩ eggsactly.
<queqiao-_> ⟨v​on Kerman⟩ I'm actually more concerned about "Coast" translated as "Полёт". I don't know if there is a correct term for "Coast", meaning not just "Полёт" (flight), but "flight with engines off".
<queqiao-_> ⟨e​gg⟩ in French I went with *vol* which is equally just flight (the на орбиты makes it clear that this is unpowered). For the one where there is no detected orbit, it says *vol non propulsé* (unpowered flight, lit. unpropelled flight)
<queqiao-_> ⟨e​gg⟩ But regardless, the grammar must be correct. We is not going to has UI that speak like this.
<queqiao-_> ⟨e​gg⟩ I guess to get the same thing as in French I colud
<queqiao-_> ⟨e​gg⟩ I guess to get the same (un)ambiguities as in French I could have
<queqiao-_> ⟨e​gg⟩ > Полёт без двигателей в течение <<2>>
<queqiao-_> ⟨e​gg⟩ if we cannot detect an orbit and
<queqiao-_> ⟨e​gg⟩ > Полёт на <<орбиты blah blah>> в течение <<2>>
<queqiao-_> ⟨e​gg⟩ otherwise (edited)
<queqiao-_> ⟨v​on Kerman⟩ Better "Полёт с выключенными двигателями"
<queqiao-_> ⟨e​gg⟩ lingoona madness intensifies:
<queqiao-_> ⟨e​gg⟩ ```
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_Planned = планируемый/планируемая/планируемое
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_Predicted = прогнозируемый/прогнозируемая/прогнозируемое
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_PeriapsisHeader = <<C:^m{<<3>>}>> перицентр отн. <<gen:1>>:\n<<4>> м#Principia_MapNode_ApproachHeader = <<C:^n{<<1>>}>> приближение к цели: <<2>> м
<queqiao-_> ⟨e​gg⟩ ```
<queqiao-_> ⟨e​gg⟩ lingoona madness intensifies:
<queqiao-_> ⟨e​gg⟩ ```
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_Planned = планируемый/планируемая/планируемое
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_Predicted = прогнозируемый/прогнозируемая/прогнозируемое
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_PeriapsisHeader = <<C:^m{<<3>>}>> перицентр отн. <<gen:1>>:\n<<4>> м
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_ApproachHeader = <<C:^n{<<1>>}>> приближение к цели: <<2>> м
<queqiao-_> ⟨e​gg⟩ ``` (edited)
<queqiao-_> ⟨v​on Kerman⟩ There is a way to simplify it without incorrect grammar: "Перицентр отн. Земли (план)", "Перицентр отн. Земли (прогноз)". But of course "Планируемый перицентр отн. Земли" is better.
<queqiao-_> ⟨e​gg⟩ yeah () are a cheap trick, and I think this works
<queqiao-_> ⟨e​gg⟩ lingoona is suprisingly powerful (but very badly used in stock strings)
<queqiao-_> ⟨e​gg⟩ ooooh magic: `<<gen:круговой орбита^f>>` produces круговой орбиты
<queqiao-_> ⟨v​on Kerman⟩ Yet another way to simplify, which also makes the text shorter: "Планир. перицентр отн. Земли", "Прогнозир. перицентр отн. Земли".
<queqiao-_> ⟨e​gg⟩ the very important think is to not write `<<gen:круговая орбита^f>>`, because that produces \*круговаяей орбиты
<queqiao-_> ⟨e​gg⟩ so as long as the thing you write in the source looks like garbage, you can get things to work
<queqiao-_> ⟨e​gg⟩ yeah but () are a cheap trick, and I think this works (edited)
<queqiao-_> ⟨e​gg⟩ I can probably get away with
<queqiao-_> ⟨e​gg⟩ ```
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_Planned = планируемый
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_Predicted = прогнозируемый
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_PeriapsisHeader = <<C:<<3>> перицентр^m>> отн. <<gen:1>>:\n<<4>> м
<queqiao-_> ⟨e​gg⟩ #Principia_MapNode_ApproachHeader = <<C:<<1>> приближение^n>> к цели: <<2>> м
<queqiao-_> ⟨e​gg⟩ ```
<queqiao-_> ⟨e​gg⟩ https://lingoona.com/cgi-bin/grammar#l=ru&t=%3C%3CC%3A%3C%3C1%3E%3E+%D0%BF%D0%B5%D1%80%D0%B8%D1%86%D0%B5%D0%BD%D1%82%D1%80%5Em%3E%3E.+%3C%3CC%3A%3C%3C1%3E%3E+%D0%BF%D1%80%D0%B8%D0%B1%D0%BB%D0%B8%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%5En%3E%3E.&v1=%D0%BF%D0%BB%D0%B0%D0%BD%D0%B8%D1%80%D1%83%D0%B5%D0%BC%D1%8B%D0%B9&oh=1
<_whitenotifier> [Principia] eggrobin opened issue #3235: The camera rotates in the plotting frame when KSP uses a rotating reference frame - https://git.io/JDS3H
<_whitenotifier> [Principia] eggrobin opened issue #3236: The description of the GSE reference frame in English is garbled - https://git.io/JDSGE
<_whitenotifier> [Principia] eggrobin labeled issue #3236: The description of the GSE reference frame in English is garbled - https://git.io/JDSGE
<_whitenotifier> [Principia] eggrobin commented on issue #3236: The description of the GSE reference frame in English is garbled - https://git.io/JDSnC
<queqiao-_> ⟨e​gg⟩ hmm, the fancy lingoonation doesn’t appear to work like that in game
<queqiao-_> ⟨e​gg⟩ ah, we have a pre-1.7 lingoona.
<queqiao-_> ⟨e​gg⟩ @von Kerman is there a reasonable way to make
<queqiao-_> ⟨e​gg⟩ Макс. длина истории shorter?
<queqiao-_> ⟨e​gg⟩ Not *much* shorter, since
<queqiao-_> ⟨e​gg⟩ Max. history length
<queqiao-_> ⟨e​gg⟩ Long. max. histoire
<queqiao-_> ⟨e​gg⟩ 最大历史长度
<queqiao-_> ⟨e​gg⟩ all fit
<bees> switch to fixed width font and it would take the same space as your other examples
<bees> problem: solved
<queqiao-_> ⟨v​on Kerman⟩ Maybe drop Макс. and keep only Длина истории?
<queqiao-_> ⟨v​on Kerman⟩ Or abbreviate - Макс. дл. истории, but it's less understandable
<queqiao-_> ⟨e​gg⟩ yeah dropping макс seems like a good idea, it’s not like it brings much
<_whitenotifier> [Principia] eggrobin labeled issue #3235: The camera rotates in the plotting frame when KSP uses a rotating reference frame - https://git.io/JDS3H
<_whitenotifier> [Principia] eggrobin labeled issue #3236: The description of the GSE reference frame in English is garbled - https://git.io/JDSGE
<_whitenotifier> [Principia] pleroy opened pull request #3237: Track the backstory when checkpointing - https://git.io/JDSH5
<_whitenotifier> [Principia] eggrobin labeled pull request #3237: Track the backstory when checkpointing - https://git.io/JDSH5
<_whitenotifier> [Principia] eggrobin closed pull request #3237: Track the backstory when checkpointing - https://git.io/JDSH5
<_whitenotifier> [Principia] eggrobin pushed 2 commits to Entwurf [+0/-0/±2] https://git.io/JD9gc
<_whitenotifier> [Principia] pleroy 99ab630 - Track the backstory.
<_whitenotifier> [Principia] eggrobin d34f597 - Merge pull request #3237 from pleroy/Track Track the backstory when checkpointing
<_whitenotifier> [Principia] eggrobin opened pull request #3238: Some support for nested placeholders - https://git.io/JD9wj
<_whitenotifier> [Principia] eggrobin labeled pull request #3238: Some support for nested placeholders - https://git.io/JD9wj
<_whitenotifier> [Principia] Pending. Build queued… - 
<_whitenotifier> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/5300/
<_whitenotifier> [Principia] Failure. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/5300/
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
<_whitenotifier> [Principia] pleroy labeled pull request #3238: Some support for nested placeholders - https://git.io/JD9wj
egg|laptop|egg has quit [Remote host closed the connection]
<_whitenotifier> [Principia] pleroy reviewed pull request #3238 commit - https://git.io/JDHey
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
<_whitenotifier> [Principia] eggrobin synchronize pull request #3238: Some support for nested placeholders - https://git.io/JD9wj
<_whitenotifier> [Principia] Pending. Build queued… - 
<_whitenotifier> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/5301/
UmbralRaptor has joined #principia
egg|laptop|egg has joined #principia
UmbralRaptop has quit [Ping timeout: 189 seconds]
egg|laptop|egg has quit [Remote host closed the connection]
<_whitenotifier> [Principia] Success. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/5301/
<_whitenotifier> [Principia] eggrobin closed pull request #3238: Some support for nested placeholders - https://git.io/JD9wj
<_whitenotifier> [Principia] eggrobin pushed 5 commits to master [+0/-0/±9] https://git.io/JDHtK
<_whitenotifier> [Principia] eggrobin 835f469 - Some support for nested placeholders
<_whitenotifier> [Principia] eggrobin 79c5351 - comment, raw strings
<_whitenotifier> [Principia] eggrobin f6032fa - wording
<_whitenotifier> [Principia] ... and 2 more commits.
egg|laptop|egg has joined #principia