Lagrang3

@bmorris3: Hi. I am glad someone replied at last. > Would you mind entering a changelog entry, and a test Sure. I'll do it.

This snippet ``` T = astropy.time.Time('2020-04-10 20:00',location=polse.location) print(polse.altaz(T,target).alt) ``` prints `16d30m12.0672s`, which corresponds to the actual altitude at 22:00.

Uh... At 20:00 astropy.time says it corresponds to Julian Day `2458950.3333333335`, when actually it should be `2458950.41667`. I see the astropy.time object is giving back a time point corresponding to...

Hi @wtgee, thank you for the clarification. Then I must assume that the `T`: ``` T = astropy.time.Time('2020-04-10 20:00',location=polse.location) ``` is meant UTC. Then what do you make up of...

In my opinion some of the constraint classes are interpreting the time in the input with respect to UTC while other are assuming them as relative to the observer.

In fact in the [code](https://github.com/astropy/astroplan/blob/001a1e123500d96979287db3a817d891cb87bd11/astroplan/constraints.py#L750) the `timezome` is copied from the `observer` but then it is not used at all.

Here's a full example. ``` #!/usr/bin/env python3 import astroplan, astropy.time import astropy.units as u import datetime, pytz polse=astroplan.Observer( latitude= 46+(28+9.1/60)/60, longitude= 13+(0+42.6/60)/60, elevation= 750*u.meter, timezone= pytz.timezone('Europe/Rome')) target = astroplan.FixedTarget.from_name('Aldebaran') T...

Would it make a difference if `dest` opens a channel with `randomnode` instead of the other way around and then depleting it?

It seems that the path-finder hit a channel with `htlc_max=0`. I believe there is no other explanation. Does that make sense?

I can patch this by disabling channels with `htlc_max` less than some threshold. Let me investigate.