Difference between revisions of "User:Vikram Atreya/GSoC21/Project Report"
From BRL-CAD
(created report page) |
|||
| Line 1: | Line 1: | ||
| − | Project Report | + | = Project Report = |
| − | + | *'''Student Name:''' Vikram Atreyapurapu | |
| + | *'''GSoC Project:''' Implementing UNDO | ||
| + | |||
| + | The project started with deciding which kind of undo to be implemented. Various implementations were thought about including a complete re-run approach, partial checkpoint, full checkpoint, etc as discussed in detail in my [[https://docs.google.com/document/d/1cZLgqVvxOiy7PgkUzEzeyXXhmLx1sEgRB1xw3hDFUlA/edit?usp=sharing|proposal]]. Using a version control system like libgit2 was also explored, but was found to be sub-optimal since it was occupying a lot of extra space and was also not very time efficient. | ||
| + | It was decided that the undo would be implemented using a partial checkpoint-like approach, where a change in an object at any step would be the only thing stored at that step instead of storing a full checkpoint of the .g file at that point. | ||
| + | To be continued... | ||
Revision as of 00:22, 22 August 2021
Project Report
- Student Name: Vikram Atreyapurapu
- GSoC Project: Implementing UNDO
The project started with deciding which kind of undo to be implemented. Various implementations were thought about including a complete re-run approach, partial checkpoint, full checkpoint, etc as discussed in detail in my [[1]]. Using a version control system like libgit2 was also explored, but was found to be sub-optimal since it was occupying a lot of extra space and was also not very time efficient. It was decided that the undo would be implemented using a partial checkpoint-like approach, where a change in an object at any step would be the only thing stored at that step instead of storing a full checkpoint of the .g file at that point.
To be continued...
