OPSIM-1189: Remove unused attributes from Conditions object #100
Conversation
yoachim
force-pushed
the
tickets/OPSIM-1189
branch
4 times, most recently
from
ab73565
to
7493754
Compare
|
Oh wow, I really thought something was using the seasons information in the conditions object -- however, I looked at all of the features which I thought were using it and no .. they hold it internally. Maybe it was at some intermediate point of development? Maybe some of the footprint basis functions did at some point? Anyway, it's good to clear it out. I'm pretty sure nothing in ts_fbs_utils uses these, but if you could double-check that would be helpful. (I don't actually know if we would see any failures, unless you also try to run the schedulers it creates though). |
| @@ -572,7 +520,7 @@ def az_to_antisun(self): | |||
| return self._az_to_antisun | |||
|
|
|||
| def __repr__(self): | |||
| return f"<{self.__class__.__name__} mjd_start='{self.mjd_start}' at {hex(id(self))}>" | |||
| return f"<{self.__class__.__name__} at {hex(id(self))}>" | |||
There was a problem hiding this comment.
It might be useful to have this print the current time (not sure why it was mjd_start before, but conditions.mjd might be a good shortcut).
yoachim
force-pushed
the
tickets/OPSIM-1189
branch
from
7493754
to
4d7ba50
Compare
rhiannonlynne
changed the title
Remove unused attributes from
Conditionsobject.