Data compression techniques in SCADA systems - Time & Space Complexity

Time Complexity: Data compression techniques

O(n)

Understanding Time Complexity

When we compress data in SCADA systems, we want to know how the time to compress grows as the data size grows.

We ask: How much longer does compression take if the data doubles or triples?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function compressData(data) {
  let compressed = []
  for (let i = 0; i < data.length; i++) {
    let count = 1
    while (i + 1 < data.length && data[i] === data[i + 1]) {
      count++
      i++
    }
    compressed.push({value: data[i], count: count})
  }
  return compressed
}

This code compresses data by counting repeated values in a row and storing the value with its count.

Identify Repeating Operations

• Primary operation: The outer for-loop goes through each data item once.
• How many times: The inner while-loop counts repeated items, but together they cover the whole data once.

How Execution Grows With Input

As data size grows, the loops still process each item once, so time grows steadily with data size.

Input Size (n)	Approx. Operations
10	About 10 steps
100	About 100 steps
1000	About 1000 steps

Pattern observation: The time to compress grows roughly in direct proportion to the data size.

Final Time Complexity

Time Complexity: O(n)

This means the time to compress grows linearly as the data size grows.

Common Mistake

[X] Wrong: "The inner while-loop makes this code take much longer than the data size."

[OK] Correct: The inner loop only counts repeated items and together with the outer loop, each item is processed once, so time grows linearly.

Interview Connect

Understanding how loops work together to process data once is a key skill in analyzing performance for real-world systems like SCADA.

Self-Check

"What if the data was sorted before compression? How would that affect the time complexity?"

Practice

1. What is the main purpose of data compression in SCADA systems?

easy

A. To reduce the size of data for easier storage and faster transfer

B. To increase the size of data for better security

C. To convert data into a different format for display

D. To delete unnecessary data permanently

Solution

1. Step 1: Understand data compression purpose

   Data compression reduces the size of data to save space and speed up transfer.

2. Step 2: Apply this to SCADA systems

   In SCADA, smaller data means faster communication and less storage needed.

3. Final Answer:

   To reduce the size of data for easier storage and faster transfer -> Option A

4. Quick Check:

   Compression = smaller data size [OK]

Hint: Compression makes data smaller to save space and time [OK]

Common Mistakes:

• Confusing compression with encryption
• Thinking compression deletes data
• Believing compression changes data meaning

2. Which of the following is the correct syntax to compress data using a function named compress in a SCADA script?

easy

A. compressed_data = compress(data)

B. compressed_data = compress data

C. compressed_data <- compress(data)

D. compressed_data = compress[data]

Solution

1. Step 1: Identify correct function call syntax

   Functions are called with parentheses enclosing arguments, like compress(data).

2. Step 2: Check each option

   compressed_data = compress(data) uses correct syntax with parentheses and assignment.

3. Final Answer:

   compressed_data = compress(data) -> Option A

4. Quick Check:

   Function call syntax = parentheses [OK]

Hint: Use parentheses to call functions with arguments [OK]

Common Mistakes:

• Omitting parentheses in function calls
• Using wrong assignment operators
• Using brackets instead of parentheses

3. Given the following SCADA script snippet:

data = "sensor_reading_12345"
compressed = compress(data)
decompressed = decompress(compressed)
print(decompressed)

What will be the output?

medium

A. compressed data bytes

B. Error: decompress function not found

C. sensor_reading_12345

D. sensor_reading

Solution

1. Step 1: Understand compression and decompression

   compress() shrinks data, decompress() restores it to original form.

2. Step 2: Follow the script flow

   Data is compressed then decompressed, so print shows original data.

3. Final Answer:

   sensor_reading_12345 -> Option C

4. Quick Check:

   Decompress(compress(data)) = original data [OK]

Hint: Decompress reverses compress, output original data [OK]

Common Mistakes:

• Thinking print shows compressed bytes
• Assuming decompress changes data
• Ignoring function order

4. A SCADA script uses compressed = compress(data) but later decompressed = decompress(data) is called instead of decompress(compressed). What is the likely problem?

medium

A. Data will be compressed twice

B. Compression will fail because decompress is called too early

C. No problem, decompress can use original data

D. Decompression will fail or give wrong data because wrong variable is used

Solution

1. Step 1: Identify variable usage error

   Decompress must use compressed data, not original data variable.

2. Step 2: Understand effect of wrong variable

   Using original data in decompress causes failure or incorrect output.

3. Final Answer:

   Decompression will fail or give wrong data because wrong variable is used -> Option D

4. Quick Check:

   Decompress(compressed) needed, not decompress(data) [OK]

Hint: Always decompress the compressed variable [OK]

Common Mistakes:

• Passing original data to decompress
• Assuming decompress auto-detects input
• Mixing variable names

5. You need to compress SCADA data but want to keep it quickly accessible for real-time monitoring. Which compression technique is best?

hard

A. No compression to avoid delay

B. Lossless compression for exact data recovery

C. Lossy compression to reduce size drastically

D. Encrypt data instead of compressing

Solution

1. Step 1: Understand real-time monitoring needs

   Real-time needs exact data quickly without loss.

2. Step 2: Choose compression type

   Lossless compression keeps data exact and fast to decompress.

3. Step 3: Evaluate other options

   Lossy loses data, no compression wastes space, encryption is different.

4. Final Answer:

   Lossless compression for exact data recovery -> Option B

5. Quick Check:

   Real-time + exact data = lossless compression [OK]

Hint: Use lossless compression for exact, fast data access [OK]

Common Mistakes:

• Choosing lossy compression for critical data
• Skipping compression to save time
• Confusing encryption with compression