Thanks for the suggestions, and last year I dedicated a six month trial to using those "separate-window" implementations in Chrome, but I'm very sorry to say they remained clumsy.
I group my work into topics by desktop; one browser instance per desktop, with an average total of 200+ tabs across eight windows. Restarting Firefox means sorting eight browser instances, one hotkey to snap them to half-width. Restarting Chrome required sorting sixteen browser windows, then manually aligning each primary window plus its tab window using the mouse. I tried, I really did, but that never became less of a pain.
Well, if you genuinely want a braindead alternative to `vim-conda`, you're welcome to this brittle hack I use. (For my purposes, fast-and-dirty has been an efficient solution, but I don't actually recommend this to anyone.)
Add it to your `ftplugin/python.vim`. Requires you to have activated the Conda environment before opening the Python file, uses hard-coded Python versions, doesn't work with multiple environments, doesn't bother with `os.path.join` so no Windows compatibility, etc etc. Like I said: a hack.
" Cheap trick to use the Conda environment with omnicompletion
python3 << EOF
import os
import sys
cenv = os.environ.get('CONDA_PREFIX')
if cenv is not None:
# Taken from `sys.path` as reported by ipython
sys.path.insert(0, cenv + '/lib/python3.5/site-packages')
sys.path.insert(0, cenv + '/lib/python3.5/lib-dynload')
sys.path.insert(0, cenv + '/lib/python3.5/plat-linux')
sys.path.insert(0, cenv + '/lib/python3.5')
sys.path.insert(0, cenv + '/lib/python35.zip')
sys.path.insert(0, cenv + '/bin')
EOF
set omnifunc=python3complete#Complete
edit: mentioned `os.path.join` to warn Windows users and fixed in-place bugfix.
If you are editing files inside a package, you can generate a tags file for definitions inside that package.
More useful, IMHO, is the general solution of jumping to the definition that would be resolved by the python interpreter, regardless of location. For that, the key binding will depend on the plugin. For `jedi-vim`, you use `<leader>d` [0].
Incidentally, if you're new to using VIM as a python IDE, also note the value of `jedi-vim` providing Python docstrings via the standard VIM keybinding `K`. This is also mentioned in [0].
There are different considerations for the problem: the orbiting masses involved (what is orbiting what?), orbital period (how long for the objects to complete an orbit around their center of mass), the distance of the objects to our measurement device (eg, a telescope on earth), the relative luminosity of the two objects (if they're close together, how do you resolve the darker of the two?), etc.
From all these considerations, there are two problems:
1. Measurement technique (getting the data)
2. System dynamics calculations (analyzing the data)
For measurement, the article mentions both visual and spectroscopic (wavelength) measurements; overviews of these and other techniques are discussed in [1]. You are correct, distance from the measurement device makes things interesting, especially in the presence of atmospheric distortion, but there are lots of tricks that can improve the effective resolution (eg, speckle imaging, which uses a bunch of images taken in rapid succession [2]).
As for the orbital period, think of it like measurements of a line. You don't need every point, just two. If you have several measurements of a celestial body, you can plot them on one of the (MANY) celestial coordinate systems [3] and do some estimates. Longer periods mean more observations for better accuracy, but you don't need to wait for a complete orbital period to get a decent estimate.
Hope this at least gives some useful keywords for your searches!
Awesome thanks.
I figured that you didn't actually need to view the full orbit and needed just a few points but for things so far away I thought that it would look practically stationary. Didn't even consider atmosphere...or that there were other factors. Of all the stuff that can be learned it probably isn't high on the list anyways.
