New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement --loose option for decode #42

Closed
bengtmartensson opened this Issue Jun 10, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@bengtmartensson
Owner

bengtmartensson commented Jun 10, 2017

Using this option, matching should be as permissive as possible accepting some strictly speaking wrong "matches". (In the sense of DecodeIR and 3FG'S teaser.)

1 Accepting junk at the end of a sequence
2. Accepting incorrect checksums etc.
3. Accepting several concatenated signals? (= invoking decoder again at non-matched junk)
4. "Overspill" between intro-, repeat-, and ending.

This is already started, with the option --loose already present.

@bengtmartensson

This comment has been minimized.

Show comment
Hide comment
@bengtmartensson

bengtmartensson Jul 19, 2018

Owner
  1. Done in 9526e06
  2. "loosened" protocol, not checking checksums, can be defined if desired. This is cleaner. Better logging facilities is a better alternative.
  3. This is #84
  4. Not a good idea, reject.
Owner

bengtmartensson commented Jul 19, 2018

  1. Done in 9526e06
  2. "loosened" protocol, not checking checksums, can be defined if desired. This is cleaner. Better logging facilities is a better alternative.
  3. This is #84
  4. Not a good idea, reject.

@bengtmartensson bengtmartensson removed this from the Milestone 2 milestone Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment