Hello @WardLT

Thanks for your suggestion. Sorry for the delay - I was on paternity leave until this week.

You're describing a pretty common case that we've run into with many of our models. The recommended solution for this is to include your control input in the state vector. This is referred internally as a "pass-through input".

There's a few reasons for this:

1. We made a design decision early on that the state of the system (used to derive outputs, event states, threshold met, etc.) be completely described by the state vector to simplify and clean model design
2. Many of the tools we've built rely on this assumption.

I've looked through our public models and cant find an example of passthrough inputs, but it's present in a few of the nasa-internal models.

It would look something like this:

class MyModel:
	def next_state(self, x, u, dt):
		... # Logic of model
		next_x['some_input'] = u['some_input'] # passthrough input

	def output(self, x):
		# use x['some_input']

Is this an adequate solution to your problem? Let me know if this doesn't solve it and we can talk more about your proposed solution.

First, congrats!

Second, passthrough inputs makes sense and I don't forsee it becoming a problem. I'll go ahead and close my PR then find out if I can make this work with our models.