-
Notifications
You must be signed in to change notification settings - Fork 20
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
PR - Mission Data Downloader #78
Conversation
t push origin master Resolving conflicts from my last PR (estimation folder spliting into ADVANCED/BASIC examples)
Merge branch 'master' of https://github.com/luigigisolfi/tudatpy-examples especially if it merges an updated upstream into a topic branch.
… mission_data_downloader_class.py) ready for PR
@luigigisolfi Thanks for opening this PR! I think this functionality is going to make a lot of difference in setting up more complicated Tudat applications :) I have a question/request, could we split it into two, with:
I can already go through the code and make comments/suggestions, so the two processes can run in parallel. If needed, someone (@alfonsoSR , @alopezrivera ?) could help out in how/where to add this to tudatpy. I think having this in the tudatpy.data submodule would be the most suitable. Your new functionality is all (?) contained inside a set of classes right? |
Yes, that's correct. As it is now, users only need to import the required modules defined in the class file via: This solution works for me! And yes, I could use some help from @alfonsoSR or @alopezrivera :) |
What do you need help with? :) |
This PR adds the following files:
mission_data_downloader.ipynb
mission_data_downloader.py
mission_data_downloader_class.py
To the tudatpy-examples/estimation/ folder.
Users can now download:
Spice Kernels, Radio Science Files, Ancillary Data Files
For the following supported missions:
MRO (Spice Kernels, Radio Science Files, Ancillary Data Files)
MEX (Spice Kernels, Radio Science Files, Ancillary Data Files)
JUICE (Spice Kernels only. Others are not available yet, but will be in the future.)