usage: ptrepack [-h] [-v] [-o] [-R RANGE] [--non-recursive] [--dest-title TITLE]
                [--dont-create-sysattrs] [--dont-copy-userattrs] [--overwrite-nodes]
                [--complevel COMPLEVEL]
                [--complib {zlib,lzo,bzip2,blosc,blosc:blosclz,blosc:lz4,blosc:lz4hc,blosc:zlib,blosc:zstd,blosc2,blosc2:blosclz,blosc2:lz4,blosc2:lz4hc,blosc2:zlib,blosc2:zstd}]
                [--shuffle {0,1}] [--bitshuffle {0,1}] [--fletcher32 {0,1}]
                [--keep-source-filters] [--chunkshape CHUNKSHAPE] [--upgrade-flavors]
                [--dont-regenerate-old-indexes] [--sortby COLUMN] [--checkCSI] [--propindexes]
                [--dont-allow-padding]
                sourcefile:sourcegroup destfile:destgroup

This utility is very powerful and lets you copy any leaf, group or complete subtree into another
file. During the copy process you are allowed to change the filter properties if you want so.
Also, in the case of duplicated pathnames, you can decide if you want to overwrite already
existing nodes on the destination file. Generally speaking, ptrepack can be useful in may
situations, like replicating a subtree in another file, change the filters in objects and see how
affect this to the compression degree or I/O performance, consolidating specific data in
repositories or even *importing* generic HDF5 files and create true PyTables counterparts.

positional arguments:
  sourcefile:sourcegroup
                        source file/group
  destfile:destgroup    destination file/group

options:
  -h, --help            show this help message and exit
  -v, --verbose         show verbose information
  -o, --overwrite       overwrite destination file
  -R RANGE, --range RANGE
                        select a RANGE of rows (in the form 'start,stop,step') during the copy of
                        *all* the leaves. Default values are 'None, None, 1', which means a copy
                        of all the rows.
  --non-recursive       do not do a recursive copy. Default is to do it
  --dest-title TITLE    title for the new file (if not specified, the source is copied)
  --dont-create-sysattrs
                        do not create sys attrs (default is to do it)
  --dont-copy-userattrs
                        do not copy the user attrs (default is to do it)
  --overwrite-nodes     overwrite destination nodes if they exist. Default is to not overwrite
                        them
  --complevel COMPLEVEL
                        set a compression level (0 for no compression, which is the default)
  --complib {zlib,lzo,bzip2,blosc,blosc:blosclz,blosc:lz4,blosc:lz4hc,blosc:zlib,blosc:zstd,blosc2,blosc2:blosclz,blosc2:lz4,blosc2:lz4hc,blosc2:zlib,blosc2:zstd}
                        set the compression library to be used during the copy. Defaults to zlib
  --shuffle {0,1}       activate or not the shuffle filter (default is active if complevel > 0)
  --bitshuffle {0,1}    activate or not the bitshuffle filter (not active by default)
  --fletcher32 {0,1}    whether to activate or not the fletcher32 filter (not active by default)
  --keep-source-filters
                        use the original filters in source files. The default is not doing that if
                        any of --complevel, --complib, --shuffle --bitshuffle or --fletcher32
                        option is specified
  --chunkshape CHUNKSHAPE
                        set a chunkshape. Possible options are: 'keep' | 'auto' | int | tuple. A
                        value of 'auto' computes a sensible value for the chunkshape of the leaves
                        copied. The default is to 'keep' the original value
  --upgrade-flavors     when repacking PyTables 1.x or PyTables 2.x files, the flavor of leaves
                        will be unset. With this, such a leaves will be serialized as objects with
                        the internal flavor ('numpy' for 3.x series)
  --dont-regenerate-old-indexes
                        disable regenerating old indexes. The default is to regenerate old indexes
                        as they are found
  --sortby COLUMN       do a table copy sorted by the index in 'column'. For reversing the order,
                        use a negative value in the 'step' part of 'RANGE' (see '-r' flag). Only
                        applies to table objects
  --checkCSI            force the check for a CSI index for the --sortby column
  --propindexes         propagate the indexes existing in original tables. The default is to not
                        propagate them. Only applies to table objects
  --dont-allow-padding  remove the possible padding in compound types in source files. The default
                        is to propagate it. Only applies to table objects