We're updating the issue view to help you get more done. 

autoNGC - create point functions for lunar lander use case

Description

Definition of done: Point functions and their derivatives are coded and checked.

  • Reuse math and code from existing sources wherever possible

  • Follow paradigm set by Josh on LISA work for where to place functions, how to make functions applicable to other use cases, etc.

Determine what point functions are needed
Code point functions
Code derivatives of point functions
Check functions
Check derivatives

Environment

None

Activity

Show:
Noble Hatten
November 3, 2020, 6:20 PM

Josh: Is there a branch I can check out to take a look at your LISA work so I can use the same strategy?

Noble Hatten
November 10, 2020, 7:31 PM
Edited

Discussion point: Is there a viable path to re-using code from GmatOptimalControlFunction, GmatPoint/PathConcatenator, etc. when using CSALT without the GMAT interface? For example, it would be very nice to have access to things like FullStateLinkage when working in CSALT itself rather than through GMAT scripting.

Discussion: GMAT is baked into things like FullStateLinkage and would take some work to extract, but it is doable.

Noble Hatten
November 10, 2020, 7:32 PM

I have re-written out what point functions are needed after switching from the human lander to the robotic lander use case.

Noble Hatten
November 10, 2020, 7:55 PM

Got branches to look at LISA stuff: LISACodeConversion, LISACodeConversion-internal.

Last commit looks like it is from June 11 – Does that seem right? Am I missing something? Can you point me to the files I should be looking at? Thanks!

Noble Hatten
November 17, 2020, 7:32 PM

Participated in meeting with Josh and others about the UserFunctionUtils Josh has created. That’s where I’ll want to the building blocks of these functions.

Assignee

Noble Hatten

Reporter

Noble Hatten

Time tracking

0m

Time remaining

16h

Components

Fix versions

Priority

P1
Configure