User Tools

Site Tools


tanszek:oktatas:techcomm:syntax

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
tanszek:oktatas:techcomm:syntax [2024/10/07 18:03] kneheztanszek:oktatas:techcomm:syntax [2025/01/31 06:14] (current) knehez
Line 12: Line 12:
  
 [[BCD encoding]] [[BCD encoding]]
 +
 +Representing each decimal digit (0-9) with a 4-bit binary sequence, BCD simplifies conversion between binary and decimal
  
 [[Fixed-Point Number Representation]] [[Fixed-Point Number Representation]]
 +
 +A method for encoding real numbers where the decimal point's position is fixed, offering hardware simplicity and uniform precision.
  
 [[Floating-Point representation]] [[Floating-Point representation]]
 +
 +Explains how real numbers are stored using the IEEE 754 standard. The number is divided into sign, exponent, and mantissa for efficient handling of large or small values.
  
 [[Parity Check]] [[Parity Check]]
 +
 +A simple error detection method used in data transmission and storage, ensuring data integrity by verifying the even or odd number of 1 bits in binary sequences.
  
 [[Error detection and correction]] [[Error detection and correction]]
  
-[[Reed-Solomon codes]] +Techniques like Elias-style block protection and Hamming codes are explained, focusing on detecting and correcting single-bit errors to maintain data integrity during transmission
- +
-[[Huffman codes]] +
- +
-[[RLE coding]] +
- +
-[[LZW coding]] +
- +
-[[Multimedia compression]] +
- +
-[[Jpeg compression]] +
- +
-[[Mpeg compression]] +
- +
-[[Character encoding]]+
  
-[[UTF-8 encoding]]+[[Luhn algortithm to protect Credit card numbers|Luhn algorithm to protect Credit card numbers]]
  
-[[Base64 coding]]+We can use the Luhn algorithm to check if a credit card number is valid. 
tanszek/oktatas/techcomm/syntax.1728324212.txt.gz · Last modified: 2024/10/07 18:03 by knehez