[13:57:09] NASSP Logging has been started by indy91 [13:57:11] https://i.imgur.com/CfUSpuH.png [13:57:24] two azimuths as iteration variables [13:57:40] and the resulting LOI DV [13:59:12] wait, the last solution isn't even optimum. I probably need to re-run the last case with the final input variables. [14:01:23] oh that's cool. [14:03:23] it seems to handle cases where it's basically an error return, too [14:04:24] I wonder if that also means that it could deal with PC+2 constraints [14:04:54] like, everything is fine and near optimum and the search goes one step further and it exceeds the PC+2 DV limit which is basically an error [14:05:55] the calculations are all analytical so it runs pretty fast. It has to, this search algorithm needs many iterations. [14:13:44] which TRW document is this from? [14:16:10] https://web.archive.org/web/20100525064117/http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19730064342_1973064342.pdf [14:16:44] has a lot of great routines actually [14:17:00] and the code [14:17:49] "high ellipse" is sort of like a hybrid trajectory, but not figure 8 [14:18:17] some of the same routines are in the RTCC Requirements for the moon centered RTE, TRW helped with that as well [14:18:39] I particularly like the analytic model to determine an Earth launch time to the Moon, that is some tricky geometry to solve [14:18:58] this document helped a bunch with the ATDP [14:19:12] speaking of [14:19:26] have a look at the references [14:19:48] reference 3 [14:20:09] the namesake :D [14:22:07] and the algorithm I just implemented is the routine PATERN from this [14:29:49] oh, I have that one. It's on my "yet to transcribe" folder [14:30:38] I bet [14:31:09] I am sure we have talked about it before haha [14:32:02] there must be a few other TRW documents like it which would be even more helpful with designing Apollo missions [14:32:35] maybe the original ATDP [14:33:22] but they aren't on NTRS [14:34:57] so far I have mostly reused my own code, but now the difficult part begins. Writing the code for e.g. three impulse LOI. [14:46:13] I'm sure theres a clever way to do it, but how do you even begin finding an optimized solution for that [14:46:51] it seems like all solutions would be families of solutions [14:47:36] it's probably all about a good initial guess [14:48:15] LOI-1 at perilune, LOI-2 at apolune [14:49:10] not sure how I want to treat the approach azimuth though [14:50:13] the Bellcomm document wants to iterate on true anomaly at LOI-1 (before burn), true anomaly at LOI-1 (after burn) and true anomaly of LOI-2 [14:50:47] LOI-1 DV is easily calculated from that then, with a fixed apolune radius [14:51:49] then LOI-2 position is also determined [14:52:09] but then the LOI-2 plane change...