ENG: Update Loop about orbitx HOT 6 OPEN

from orbitx.

1. What does desiderata mean

2. My thought for how to do the simulation is that we just include engineering simulation stuff in the existing physics simulation loop. The benefit is we don't have to duplicate the IMO too-intricate simulation loop logic (with its threading and such). Also,

• in a networked context (with hab/MC flight etc also running) the physics server can continue to be the centralized and authouritative server, which simplifies things for people setting up the network. (Currently with OrbitV, hab engineering is the authouritative copy for some parts of the simulation, and hab flight is authouritative for other parts, and it's just confusing!)

• in an unnetworked context i.e. singleplayer training mode, we can just run the simulation locally. Maybe we could even simulate just the hab, AYSE, and the Earth to make the simulation faster, since we won't be representing mars, Jupiter, etc in engineering training.

How does this sound? The main hangup I see is that the current simulation infrastructure relies being able to create a derivative function of the state of the universe. For physical locations, that's as simple as

d/dt(position, velocity) = (velocity, acceleration)

But I am emphatically NOT an electrical engineer, so we should make sure we can actually make such a derivative function to describe the hab and AYSE power grid. That seems like a thing that's possible though(?) But if it's not, we'll have to rethink.

from orbitx.

from orbitx.

dang, pyspice does sound cool though, but agree unfortunately :<

oh by the way, did you find the definitions of the electrical properties of all the switches and stuff in OrbitV? I seem to recall it was in orbitsej.txt but can't actually find that or a similar text file when I looked around a little bit last week. Want me to help with deciphering that code?

from orbitx.

Action item for next week:

can someone with like five phds figure out how to model the current, temperature, resistance, and voltage for the system of components. The best way would probably be to define the derivative for all four in the system.

For example:

    def our_deriv_func(orbitx_state):
        t = orbitx_state.engineering['INS'].t
        r = orbitx_state.engineering['INS'].r
        i = orbitx_state.engineering['INS'].i
        v = orbitx_state.engineering['INS'].v

        t` = eta * (i**2)*r
        r` = alpha * t`

        v` = 0(?)  # <--- figure this part out

        i` = (r`*v - r*v`)/(v^2)

from orbitx.

I'll add some accessors to implement orbitx_state.engineering['INS'] and other things like that.

from orbitx.