Technical Discussion: Architecture and Implementation of the Robust 3D Mask Engine

[sh1vam31]

Hi @paulojamorim

As I refine the technical design for the 'Robust 3D Mask Engine' project in the GSoC proposal (as I shared with you via email for review), I’d like to discuss the finer implementation details and ensure my technical approach aligns perfectly with the project's long-term vision.
To start, I have a strategic question regarding the Delta-Encoded Undo Engine for invesalius_rs:

The Question: Should I prioritize keeping the delta-history stack strictly in-memory (RAM) for maximum 'Undo' speed, or should I design a disk-backed 'spillover' mechanism using temporary files?

The Goal: A disk-spillover would make the 3D editor essentially 'crash-proof' even on hardware with limited RAM or during extremely long editing sessions. I want to ensure we achieve the highest level of stability possible for medical use cases.

I’m excited to dive into these implementation nuances as we move toward the summer period.
Looking forward to your thoughts.

Thank you.
Shivam Chaudhary

[paulojamorim]

Hi @sh1vam31

I believe keeping part of it on disk is a better option, especially since it is now common for computers to have storage devices with good read/write performance (SSD/NVMe) installed.