You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that, when there is a Greencube (IO-117) pass in progress, its next pass isn't listed in Look4Sat. Hitting the refresh button while the pass is ongoing doesn't help. Once the pass is over, hitting the refresh button brings the next pass to the list. I am certain about the next pass' existence because several other prediction tools, such as Gpredict or Amsat.org online prediction tool, whose predictions usually agree with those of Look4Sat,
all list them. LEO hamradio satellites don't seem to be affected by this issue.
The text was updated successfully, but these errors were encountered:
Update: it isn't just the next pass while one is visible. It appears that the 2nd next pass is affected.
kconkas
changed the title
IO-117 (greencube) next pass not listed when current pass is in progress
IO-117 (greencube) 2nd next pass is not listed
Mar 9, 2024
Hey @kconkas! Sorry for such a late reply. There was a data related issue #126 that was resolved in the latest app version v3.1.4. If you still observe the same issue, I'd suggest to play with the passes filter dialog in the bottom left of the passes page.
The precision of passes calculation is +/- 5 sec and that slightly affects all the other pass data like the max elevation for example. It is possible that it just goes below and above your set filter and dissappears from the list. Maybe one day I'll go through the pass calculation process and set it to use monotonic time, that should improve the precision and fix this once and for all.
I noticed that, when there is a Greencube (IO-117) pass in progress, its next pass isn't listed in Look4Sat. Hitting the refresh button while the pass is ongoing doesn't help. Once the pass is over, hitting the refresh button brings the next pass to the list. I am certain about the next pass' existence because several other prediction tools, such as Gpredict or Amsat.org online prediction tool, whose predictions usually agree with those of Look4Sat,
all list them. LEO hamradio satellites don't seem to be affected by this issue.
The text was updated successfully, but these errors were encountered: