pyephem

问题 The inferior conjunction of Venus today (while still being observable due to the northerly offset from the Sun) inspired the following research in pyEphem. Determine the date when Venus has an inferior conjunction with the Sun. Is there a search function for (inferior) conjunctions between Venus and the Sun in pyEphem? Determine the ecliptical latitude of Venus at the date. That should be easy. Do this for conjunctions for the last 100 and next 100 years. That's just a loop. I was wondering

问题 The inferior conjunction of Venus today (while still being observable due to the northerly offset from the Sun) inspired the following research in pyEphem. Determine the date when Venus has an inferior conjunction with the Sun. Is there a search function for (inferior) conjunctions between Venus and the Sun in pyEphem? Determine the ecliptical latitude of Venus at the date. That should be easy. Do this for conjunctions for the last 100 and next 100 years. That's just a loop. I was wondering

问题 I very much like having pylint tell me if I'm using a non-existent member. However, my new project is using both twisted and the ephem modules, which seem to confuse pylint. How can I get rid of these (incorrect) pylint warnings without either turning off E1101 in general, and without sprinkling warning removal comments around every relevant call? E1101: 8,0: Module 'twisted.internet.reactor' has no 'run' member E1101: 49,25:sunrise_next: Module 'ephem' has no 'Sun' member E1101: 63,26:sunset

问题 I very much like having pylint tell me if I'm using a non-existent member. However, my new project is using both twisted and the ephem modules, which seem to confuse pylint. How can I get rid of these (incorrect) pylint warnings without either turning off E1101 in general, and without sprinkling warning removal comments around every relevant call? E1101: 8,0: Module 'twisted.internet.reactor' has no 'run' member E1101: 49,25:sunrise_next: Module 'ephem' has no 'Sun' member E1101: 63,26:sunset

问题 I very much like having pylint tell me if I'm using a non-existent member. However, my new project is using both twisted and the ephem modules, which seem to confuse pylint. How can I get rid of these (incorrect) pylint warnings without either turning off E1101 in general, and without sprinkling warning removal comments around every relevant call? E1101: 8,0: Module 'twisted.internet.reactor' has no 'run' member E1101: 49,25:sunrise_next: Module 'ephem' has no 'Sun' member E1101: 63,26:sunset

问题 I am just getting started with PyEphem . My immediate task is, given a date and time compute the sub-solar point on Earth with latitude-longitude values. I'll dig into PyEphem to work this out but if someone has already done this, I'd appreciate sample code. 回答1: I cannot test actual code from where I am this morning, but: an object at declination ϕ should always ride right above the series of locations on earth that have latitude ϕ , so the latitude number is given to you directly by a body

问题 I have a need to compute the apparent azimuth and elevation angles as well as the sub-lunar lat/lon for a given date/time. The az/el angles I get generally agree with other sources (MoonCalc.org, Horizons, etc.) but there are not good comparison sources for the sub-lunar lat/lon. More importantly, I doubt the lat/lon I get using the dec/ra values because the ra barely changes over long time frames. Here is the basic call I am making: roc.date='2018/1/1 01:00:00' moon=ephem.Moon(roc) print(

问题 I am using PyEphem and want to calculate the length of a shadow (assume a stick of unit length is planted in the ground). The length will be given by cot(phi), where phi is the solar elevation angle (please correct me if I'm wrong). I'm not sure what field to use on the Sun? In the example below, I'm using the angle alt: import ephem, math o = ephem.Observer() o.lat, o.long = '37.0625', '-95.677068' sun = ephem.Sun() sunrise = o.previous_rising(sun, start=ephem.now()) noon = o.next_transit

问题 there's obviously a time module that works in combination with this problem, but I have not found it yet. I'm simply trying to use Pyephem on a Raspberry Pi to find out what time sunrise and sunset is for my latitude longitude coordinates. the code is quite simply this: import ephem import datetime import time now = datetime.datetime.now() gmNow = time.mktime(time.localtime()) Vancouver = ephem.Observer() Vancouver.lat = 49.2878 Vancouver.horizon = 0 Vancouver.lon = -123.0502 Vancouver

问题 I am trying to calculate the local solar time based on UTC hour and longitude. I have looked through the ephem package but was not able to identify a direct method to do so. Similar questions on this matter either evoke the calculation of fixed positions (sunrise, moon, sunset) (e.g. Calculating dawn and sunset times using PyEphem) or receive suggestions of simplified methods (e.g. Local solar time function from UTC and longitude). Is there any alternative to the aforementioned solutions?