Introduce TensorTreeIO and reorganize tensor tree - #137
Merged
Conversation
Introduced mechanism to serialize a tensor tree. The default implementation is pkl.
benikm91
approved these changes
Aug 2, 2026
benikm91
left a comment
benikm91
left a comment
Collaborator
There was a problem hiding this comment.
Nice, looks very good. I like the TensorFormat abstraction and Pickle default implementation.
Merged
Draft
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is split in 2 commit (which should be looked at separately when reviewing).
The first moves tensor tree related files into a tensortree package. It currently is in autodiff, which is not the appropriate place, as tensortrees started to be an important abstraction throughout dimwit.
The second PR adds a TensorTreeIO object, which allows to serialize a tensor tree. A default implementation is provided that uses Python pkl. This choice was mainly done because it is simple and does not introduce new dependencies. The definition makes it possible for libraries that build on it to use other serialization formats (zarr, hdf5, ...).