Skip to content

PRRoid26/length_of_burst_error

View on GitHub ↗Related repositories →

In order to detect burst errors of length "t" a code word is generated by appending "t" parity bits at the end (or beginning) of the message. The parity bits will be generated by doing an XOR of all of the bits separated by t bits. At the receiving end t equations are used to check the parity of the received codeword.

active 2023-11-19 → 2023-11-19 (UTC)

Complete coverage28,287 / 28,287 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-11-05 (UTC)
Events
3
Pushes
1
Pull requests
0
Issues
0
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 1 days from 2023-11-19 to 2023-11-19. Pushes: 1 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 0 total, peak 0 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
PRRoid261100

Recent activity

Latest issues, pull requests and releases

No issue or PR events — this repo's activity is pushes only.

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.