Skip to content

Commit ae8fdfd

Browse files
committed
modified: Documentation/README.html
modified: README.md
1 parent 537d6f8 commit ae8fdfd

2 files changed

Lines changed: 5 additions & 7 deletions

File tree

Documentation/README.html

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -757,16 +757,14 @@ <h3 id="one-pass-approach-with-full-trajectory-caching">One-Pass Approach with F
757757
</li>
758758
</ul>
759759
<h3 id="one-pass-approach-with-limited-memory-usage-chunked-or-no-caching">One-Pass Approach with Limited Memory Usage (Chunked or No Caching)*</h3>
760-
<p>Description: These approaches attempt to reduce memory consumption by either processing the trajectory in chunks or not caching trajectory points at all. However, since the full trajectory extents are unknown at the outset, each variation faces the same limitation: pixel mappings require recalculating as the trajectory's range in continuous space will generally evolve, except in edge cases.</p>
761-
<p>Chunked: The trajectory is divided into manageable chunks, each cached temporarily.<br>
762-
No Caching: Points are computed and mapped to pixels directly without storing them.</p>
760+
<p>Description: These approaches aim to reduce memory usage by either processing the trajectory in chunks (temporarily cached) or directly computing and mapping points to pixels without storing them. However, without knowing the full trajectory extents upfront, previously mapped pixels may require recalculation as the trajectory range in continuous space generally evolves, except in edge cases.</p>
763761
<ul>
764762
<li>
765-
<p>Advantages: Limits memory usage.</p>
763+
<p>Advantages: Significantly reduces memory usage.</p>
766764
</li>
767765
<li>
768-
<p>Disadvantages: Both approaches become impractical due to the following major limitations:
769-
Data Loss and Inaccuracy: As previously computed floating-point values are irrecoverably mapped to integer pixel coordinates, it becomes impossible to retrieve the exact values for remapping, leading to data loss and inconsistencies.</p>
766+
<p>Disadvantages:<br>
767+
Data Loss and Inaccuracy: Previously computed floating-point values are irrecoverably mapped to integer pixel coordinates, making it impossible to retrieve the exact values for remapping. This leads to data loss and inconsistencies.</p>
770768
</li>
771769
</ul>
772770
<p>*This also applies analogously to any versions that only process floating point values.</p>

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -539,7 +539,7 @@ Description: These approaches aim to reduce memory usage by either processing th
539539

540540
- Advantages: Significantly reduces memory usage.
541541

542-
- Disadvantages:
542+
- Disadvantages:
543543
Data Loss and Inaccuracy: Previously computed floating-point values are irrecoverably mapped to integer pixel coordinates, making it impossible to retrieve the exact values for remapping. This leads to data loss and inconsistencies.
544544

545545
*This also applies analogously to any versions that only process floating point values.

0 commit comments

Comments
 (0)