-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not support STK12 #7
Comments
Yes you are right. Thanks for raising the issue! If you have the GUID for STK12, please let me know, I can add that into ORBITM quickly just by adding an extra mode and line in the code snippet from the STK integration Python file. Below is the code snippet for STK10/11
|
thanks for such a quick response! |
looking at the table, it looks like the GUID associated with the STK 11 one you have above is: FEAEF02E-48CE-42AE-B99B-FB9871A69E4B |
Ooooh thanks! It seems for Astrogator, it is I will try to do a commit sometime this week to include that in the GUI, in the mean time, if you are in urgent need to automate STK12 using ORBITM, maybe you can try to manually replace the GUID for STK11 in the file
|
I get an "error in running! DeltaVVector" using that hack. don't worry about rushing it. Work and school come first :) |
Oooh that actually sounds like an error coming from STK12 because DeltaVVector is a sub-class of the Maneuver object in STK... I don't have STK12 unfortunately, so I'm not able to replicate this error, but is there a chance you can share a print out of the full error log (if any) so I can understand what happened? My guess is that STK12 Integration and Astrogator probably had changes to their Integration API as they upgraded from 10 -> 11 -> 12. |
Current version does not support STK 12
The text was updated successfully, but these errors were encountered: