python 2.7 - Why won't PyEphem calculate the elevation of manually generated objects? -


i have been using pyephem quite while, since few days (maybe weeks?) ago, 1 of scripts won't work anymore. script calculates among other things rise , set times of asteroids, create orbital elements using callhorizons. figured out pyephem not calculate asteroids' elevation - however, calculates elevation sun.

here minimal script:

import ephem import numpy import callhorizons   this_target = '3552' body = callhorizons.query(this_target) body.set_discreteepochs(2415730.0) body.get_elements() this_target = body.export2pyephem()[0]  ### works fine sun #this_target = ephem.sun()  date = ephem.now()  this_target.compute(date)  obs = ephem.observer() obs.epoch = 2000.0 obs.lon = -111.653152/180.*numpy.pi obs.lat = 35.184108/180.*numpy.pi obs.elevation = 2738 # m obs.date = date obs.horizon = 0.  # if target '3552', this_target.alt stays constant time in numpy.arange(date, date+1, 0.1):     obs.date = time     this_target.compute(obs)     print time, this_target.alt, this_target.ra  ### if this_target '3552', results in segmentation fault print obs.next_rising(this_target) 

using self-defined target (3552 in case), pyephem won't calculate target's elevation , hence run segmentation fault when trying derive rise/set times of target.

i tried installing latest version of pyephem (3.7.6.0), didn't help. can replicate (explain?) error?

given latitude of 35 deg, fact object close jupiter above ecliptic , has period of 8 years, it's may never rise until approximately 2 or 3 more years have passed.


Comments

Popular posts from this blog

javascript - Thinglink image not visible until browser resize -

firebird - Error "invalid transaction handle (expecting explicit transaction start)" executing script from Delphi -

mongodb - How to keep track of users making Stripe Payments -