Currently when findEph() is called, that returns null for all sorts of reasons, for example because when the Health status of a satellite for a given timestamp is != 0 (not healthy).
For that reason it's hard to know why findEph() has failed, was the file not there? or rather that file was there but the satellite was unhealthy.
Those are very different cases and currently we have no easy way to discriminate between the two.
If an observation contains, say, 4 sats and one is unhealthy (really unlucky but it can happen), there should be a way to know so we can mark that fix as failed.
ZiglioUK
commented
7 years ago
Currently when findEph() is called, that returns null for all sorts of reasons, for example because when the Health status of a satellite for a given timestamp is != 0 (not healthy). For that reason it's hard to know why findEph() has failed, was the file not there? or rather that file was there but the satellite was unhealthy. Those are very different cases and currently we have no easy way to discriminate between the two. If an observation contains, say, 4 sats and one is unhealthy (really unlucky but it can happen), there should be a way to know so we can mark that fix as failed.