Add memory-mapped support for Kinetics-skeleton data converter #516
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.
Description
This pull request introduces an updated data converter script for Kinetics-skeleton data. By default, the script continues to use the original in-memory approach (
gendata
). However, users can now enable memory-mapped numpy arrays (open_memmap
) by passing the--use_mmap
flag. This enhancement significantly reduces peak RAM usage for large datasets by processing data in configurable chunks (--chunk_size
).Key Changes
New Function:
gendata_mmap
open_memmap
to write data in chunks directly to disk.Command-line Flag:
--use_mmap
gendata
(in-memory) andgendata_mmap
(memory-mapped) approaches.Chunk Size:
--chunk_size
open_memmap
.128
.Testing
--use_mmap
and without) produce equivalent .npy and .pkl results.spatio_temporal_gcn_learner.py
script and the ST-GCN model.