Skip to content
This repository was archived by the owner on Apr 13, 2021. It is now read-only.

I123 glo decoder error detector #337

Merged
merged 1 commit into from
May 6, 2016
Merged

I123 glo decoder error detector #337

merged 1 commit into from
May 6, 2016

Conversation

dt-unikie
Copy link

The commit adds error detection algorithm for GLO nav messages + unit tests.
Requires: https://github.com/swift-nav/libswiftnav/pull/329

@dt-unikie dt-unikie self-assigned this Apr 26, 2016
@coveralls
Copy link

Coverage Status

Coverage increased (+1.5%) to 56.498% when pulling 261a786 on dt-exafore:i123-glo-decoder-error-corrections into 5553330 on swift-nav:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.6%) to 56.6% when pulling d901fdb on dt-exafore:i123-glo-decoder-error-corrections into 5553330 on swift-nav:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 56.563% when pulling fa1d16d on dt-exafore:i123-glo-decoder-error-corrections into a20edb4 on swift-nav:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 56.664% when pulling f3714bd on dt-exafore:i123-glo-decoder-error-corrections into a20edb4 on swift-nav:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 56.707% when pulling 5d4e6d7 on dt-exafore:i123-glo-decoder-error-corrections into a20edb4 on swift-nav:master.

@dt-unikie
Copy link
Author

@adel-mamin, please review.


return 0; /* The string is good */

else if ((bit_set > 0 && !c_sum)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we remove 'else' here and below, since otherwise we always return?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. I'd prefer the else's removed, but it's not a big deal.

@adel-mamin
Copy link

Looks good to me.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 56.707% when pulling 8ac9a1c on dt-exafore:i123-glo-decoder-error-corrections into a20edb4 on swift-nav:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 56.707% when pulling 8ac9a1c on dt-exafore:i123-glo-decoder-error-corrections into a20edb4 on swift-nav:master.

@dt-unikie dt-unikie changed the title WIP: I123 glo decoder error detector I123 glo decoder error detector Apr 29, 2016
{
assert(n_bits <= 32 && n_bits > 0);
assert(bit_index <= 85 && bit_index > 0);
assert(bit_index <= GLO_STR_LEN && bit_index > 0);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Return error if parameters are invalid. Do not assert here.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 56.658% when pulling 9c9fea3 on dt-exafore:i123-glo-decoder-error-corrections into a20edb4 on swift-nav:master.

#include <libswiftnav/logging.h>
#include <libswiftnav/bits.h>

#ifdef UNIT_TEST
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer to move this to check_glo_decoder.c which includes this file.

#include <libswiftnav/logging.h>
#undef log_error
#define log_error(...)
#include "nav_msg_glo.c"

@gsmcmullin
Copy link
Contributor

See my inline comments, but otherwise looks good. I haven't checked the algorithm, I'll take that on faith.

@dt-unikie
Copy link
Author

Corrected. Thanks @gsmcmullin, @adel-mamin and @valeri-atamaniouk

@coveralls
Copy link

Coverage Status

Coverage increased (+0.4%) to 56.658% when pulling 53d9f31 on dt-exafore:i123-glo-decoder-error-corrections into a20edb4 on swift-nav:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 56.614% when pulling 80d90e7 on dt-exafore:i123-glo-decoder-error-corrections into a20edb4 on swift-nav:master.

@rge-exafore rge-exafore merged commit 5ae607f into swift-nav:master May 6, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants