dallinspencer
commented
4 years ago Here;s some documentation from the JPL Horizons page.
Keep Queries Short Keep in mind that queries are sent as URIs to the Horizons server. If you query a large number of epochs (in the form of a list), this list might be truncated as URIs are typically expected to be shorter than 2,000 symbols and your results might be compromised. If your query URI is longer than this limit, a warning is given. In that case, please try using a range of dates instead of a list of individual dates.
How many epochs were included in your list of synthetic data? I'm guessing if it's more than 50, then they ask for a range instead of a list, which we can build in, but may not be conducive to our observations, in which case doing a look could work, it just might be slow, which is fine since it's a code that should only need to run once.
benp175
https://github.com/dragozzine/multimoon/blob/3acf688c425ce8e285612b3a36f1399f824843d1/src/mm_make_geo_pos.py#L7
In this function, I get an error about the query being too long. I don't know if this is specific to my version of astroquery (which is the most up to date version avaliable). I think this will be easily solved by retrieving the ephemerides of the KBO one at a time, rather than all at once. This shouldn't be hard to implement since it really just involves looping over each observation time.