navo-workshop
navo-workshop copied to clipboard
NASA-NAVO
Tutorial notebooks for how to use PyVO to access NASA and other data in Python.
Some output cells can be long (e.g. [this](https://nasa-navo.github.io/navo-workshop/QuickReference.html#table-search)). It will be useful to make them scrollable.
Section 2 tells the user to see the file QuickReference.md (which does not exist) - should that be QuickReference.ipynb?
I am wondering if it is necessary to include the code block that defines the function "getrow" in the UseCase_III notebook. I think there are easier ways to search for...
In Exercise_I, the user is asked to use Cutout2D, but that was not demonstrated in the the Quick Reference guide nor in the CS files
In UseCase_I, step 10, we use `.title` and `.bandpass_id` to see attributes of the result rows. This is right after showing the results as a VOTable which does not use...
Exercise_II suggests writing the data to the disk, but it is not demonstrated in the Quick Reference guide nor the CS files.
Currently, the tracebacks are dumped in separate logfiles and a WARNING is raised, so not much to go by for debugging the actual issue without ssh-ing, etc. Ideally all tracebacks...
- [ ] SIA:size, SSA:diameter, SCS:radius, astroquery:radius|width|height. Common pyvo option that converts as needed? [hard] - [ ] Expose TAPService.tables in RegistryResource [easy?] - [ ] Expose TAPService.examples in RegistryResource...
TBD how the tags should be listed or maintained. Tags could be characteristics like image access, TAP, filtering, etc.