write simulation

[Sauron754]

Name says it all. (this is vaguely defined more infos coming soon)

[Sauron754]

which computational time unit are we using? (seconds, minutes)?? or maybe shall we use big units for celestial bodys (like minutes) and short units for the flights (like seconds, miliseconds)

[taragor]

i'd go for SI units (seconds)

[Sauron754]

eaven for the orbital positions? cause it might become a cramp in the ass when calculating this precisely

[taragor]

what is the desired tick rate?

[taragor]

besides we dont need to update every second even if we use seconds as time unit (what makes calculating a lot more easy)

[Sauron754]

jeah you are correct; in that case i would say 20 ticks and celestial body update every 1 or 2 secs

[Sauron754]

i just entered the line which returns the parent object at <line 8>

[taragor]

changes already pushed??

[Sauron754]

i believe so

[taragor]

found some usefull stuff to calculat keplerian elements form velocity https://space.stackexchange.com/questions/1904/how-to-programmatically-calculate-orbital-elements-using-position-velocity-vecto

[Sauron754]

NICE! will you be able to calculate orbital periods and apsis heights?

[Sauron754]

just finished the work on the midParser; check into the issue for more info

[taragor]

just found some great shit for solving our transformation problem http://pythonhosted.org/OrbitalPy/

[Sauron754]

nice shit but we would need to ask them for permission

2017-05-05 10:26 GMT+02:00 taragor notifications@github.com:

just found some great shit for solving our transformation problem http://pythonhosted.org/OrbitalPy/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Sauron754/SpaceScript/issues/4#issuecomment-299409769, or mute the thread https://github.com/notifications/unsubscribe-auth/APsTuHXomtYWG8KsS60B8Bc613vlj1Ugks5r2t1BgaJpZM4M_pEU .

[Sauron754]

maybe we can ask him if he wants to contribute

2017-05-05 10:29 GMT+02:00 Sauron754s Code advancedcode754@gmail.com:

nice shit but we would need to ask them for permission

2017-05-05 10:26 GMT+02:00 taragor notifications@github.com:

just found some great shit for solving our transformation problem http://pythonhosted.org/OrbitalPy/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Sauron754/SpaceScript/issues/4#issuecomment-299409769, or mute the thread https://github.com/notifications/unsubscribe-auth/APsTuHXomtYWG8KsS60B8Bc613vlj1Ugks5r2t1BgaJpZM4M_pEU .

[taragor]

its mit licenced on github

[taragor]

running into problems using this method: https://space.stackexchange.com/questions/1904/how-to-programmatically-calculate-orbital-elements-using-position-velocity-vecto

if we use the suggested formulas for a/p (apoapsis and periapsis) it sets the apoapsis at inf only for parabolic orbits/flybys (is there such a thing like an parabolic "orbit" technically its no orbit, is it??) not for hyperbolic ones(e>1), what makes no sence imo, scince hyperbolic orbits have also an indefinite apoapsis heigth

[Sauron754]

now i might be wrong but i think that there is no real "hyperbolic" orbit because hyperbolic and parabolic orbits are the same; so if it works for one it should work for both

[taragor]

is xhat (x with that circumflex hat thingy above it) the english/internationnal writing for the unity vector of x??

EDIT: if true we need vectoralgebra for generating unityvectors

[Sauron754]

not sure but ill add a unitvector generation function anyway in the vectorAlgebra.py

[Sauron754]

okay done! its called unitVector and returns (no shit) the unitVector