Enum Error 

pub enum Error {
    NotEnoughCandidates,
    NotEnoughInitializationCandidates,
    NotEnoughPreFitCandidates,
    NotEnoughPostFitCandidates,
    UnknownNavigationMethod,
    MatrixMinimalDimension,
    MatrixDimension,
    MatrixFormationError,
    MatrixInversion,
    NavigationError,
    NavigationFilterInitError,
    MissingPseudoRange,
    PseudoRangeCombination,
    PhaseRangeCombination,
    UnresolvedState,
    UnresolvedStateBancroft,
    UnknownClockCorrection,
    PhysicalNonSenseRxPriorTx,
    PhysicalNonSenseRxTooLate,
    BancroftError,
    BancroftImaginarySolution,
    AmbiguityFactorization,
    AmbiguityInverse,
    FloatAmbiguitiesSolving,
    UnresolvedAmbiguity,
    Almanac(AlmanacError),
    MetaAlmanac(MetaAlmanacError),
    EarthFrame(PlanetaryDataError),
    Physics(PhysicsError),
    PostfitPrenav,
    MissingRemoteRTKObservation(Epoch, SV),
    MissingRemoteRTKObservations,
    InvalidFrequency,
    UnknownCarrierFrequency,
    RejectedTropoDelay,
    RejectedIonoDelay,
    StateUpdate,
    TimeUnderflow,
    UnknownTimeCorection,
    OutdatedTimeCorrection,
    UnknownTimescale,
    PostFitUpdate,
    UninitializedFilter,
    MaxGdopExceeded,
    MissingPhaseRange,
    SdPivotSatellite,
    RtkBaselineTooLong,
    RtkDDPostfitMissing,
}

Variants

NotEnoughCandidates

Not enough candidates were proposed, with respect to navigation parameters.

NotEnoughInitializationCandidates

Survey initialization (no apriori = internal guess) requires at least 4 SV in sight temporarily, whatever your navigation technique.

NotEnoughPreFitCandidates

PreFit (signal quality, other..) criterias have been applied but we’re left with not enough vehicles that match the navigation technique: no attempt.

NotEnoughPostFitCandidates

PostFit (state solver and other) have been resolved, but we’re left with not enough vehicles that match the navigation technique: no attempt.

UnknownNavigationMethod

Failed to parse navigation method

MatrixMinimalDimension

MatrixDimension

MatrixFormationError

MatrixInversion

Invalid orbital states or bad signal data may cause the algebric calculations to wind up here.

NavigationError

Invalid orbital states or bad signal data may cause the algebric calculations to abort.

NavigationFilterInitError

Failed to initialize navigation filter

MissingPseudoRange

PseudoRangeCombination

[Method::CPP] requires the special signal combination to exist. This require the user to sample PR on two separate frequencies.

PhaseRangeCombination

[Method::PPP] requires the special signal combination to exist. This require the user to sample PR + PH on two separate frequencies.

UnresolvedState

Each [Candidate] state needs to be resolved to contribute to any PPP resolution attempt.

UnresolvedStateBancroft

Each [Candidate] presented to the Bancroft solver needs a resolved state.

UnknownClockCorrection

When [Modeling.sv_clock_bias] is turned on and we attempt PPP resolution, it is mandatory for the user to provide [ClockCorrection].

PhysicalNonSenseRxPriorTx

Physical non sense due to bad signal data or invalid orbital state, will cause us abort with this message.

PhysicalNonSenseRxTooLate

Physical non sense due to bad signal data or invalid orbital state, will cause us abort with this message.

BancroftError

Error during surveying initialization, without apriori knowledge. The solver initialization requires a minimum of 4 SV in sight temporarily, whatever the navigation technique being used.

BancroftImaginarySolution

[Bancroft] initialization process (see [BancroftError]) will wind up here in case unrealistic or bad signal observation or orbital states were forwarded.

AmbiguityFactorization

Ambiguity factorization failed

AmbiguityInverse

Matrix inversion error during ambiguity solving process

FloatAmbiguitiesSolving

Floating Ambiguities solving issue

UnresolvedAmbiguity

PPP navigation technique requires phase ambiguity to be solved prior any attempt. It is Okay to wind up here for a few iterations, until the ambiguities are fixed and we may proceed to precise navigation. We will reject solving attempt until then. Hardware and external events may reset the ambiguity fixes and it is okay to need to rerun through this phase for a short period of time. Normally not too often, when good equipment is properly operated.

Almanac(AlmanacError)

[Solver] requires [Almanac] determination at build up and may wind-up here this step is in failure.

MetaAlmanac(MetaAlmanacError)

[Solver] uses local [Almanac] storage for efficient deployments

EarthFrame(PlanetaryDataError)

[Solver] requires to determine a [Frame] from [Almanac] and we wind-up here if this step is in failure.

Physics(PhysicsError)

Any physical non sense detected by ANISE will cause us to abort with this error.

PostfitPrenav

Post fit (pre nav) error

MissingRemoteRTKObservation(Epoch, SV)

Remote observation is required for a [Candidate] to contribute in RTK solving attempt. You need up to four of them to resolve. We may print this internal message and still proceed to resolve, as SV may go out of sight of rover or reference site.

MissingRemoteRTKObservations

In RTK resolution attempt, you need to observe all pending SV on reference site as well. If that is not the case, we abort with this error.

InvalidFrequency

UnknownCarrierFrequency

RejectedTropoDelay

RejectedIonoDelay

StateUpdate

TimeUnderflow

UnknownTimeCorection

OutdatedTimeCorrection

UnknownTimescale

PostFitUpdate

UninitializedFilter

MaxGdopExceeded

MissingPhaseRange

[Error::MissingPhaseRangeMeasurements] is returned when using PPP strategy and CP measurements were not associated to PR measurements (which is mandatory).

SdPivotSatellite

Unable to elect pivot satellite for SD algorithm, empty dataset ? (should not happen, and potentially even be reached)

RtkBaselineTooLong

RTK baseline is most liekly too long, and we are limited to short baseliens currently.

RtkDDPostfitMissing

RTK resolution non feasible: missing DD measurement postfit

Trait Implementations

impl Debug for Error

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for Error

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for Error

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0: use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0: replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl PartialEq for Error

fn eq(&self, other: &Error) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for Error