Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve proof compression via diffs rather than snapshots #317

Open
3 tasks
James-Oswald opened this issue Dec 16, 2023 · 0 comments
Open
3 tasks

Improve proof compression via diffs rather than snapshots #317

James-Oswald opened this issue Dec 16, 2023 · 0 comments
Labels
API-Break Will break test results or backwards compatibility. Leftmost number in semantic versioning Enhancement New feature
Milestone

Comments

@James-Oswald
Copy link
Member

Currently proof (and AEG file) compression does not exist, we just use the entire JSON representation of the tree at each step for proofs. A better option is to do what git does and represent each inference rule application in the proof file by only listing the changes made at each step (what nodes were created? where?). This would significantly reduce proof size.

  • Create a JSON schema for the new proof file format
  • Implementation of saving proofs as just the set of changes
  • Implementation for constructing proofs from a set of changes
@James-Oswald James-Oswald added the Enhancement New feature label Dec 16, 2023
@James-Oswald James-Oswald changed the title Improve proof compression via Improve proof compression via diffs rather than snapshots Dec 16, 2023
@James-Oswald James-Oswald added this to the PMH 2.0.0 milestone Dec 16, 2023
@RyanR712 RyanR712 added the API-Break Will break test results or backwards compatibility. Leftmost number in semantic versioning label Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API-Break Will break test results or backwards compatibility. Leftmost number in semantic versioning Enhancement New feature
Projects
None yet
Development

No branches or pull requests

2 participants