Group print hierarchy

[alimanfoo]

Consider implementing a method on the Group class like "describe" or "ls" which will print whole hierarchy for a given hierarchy depth.

[jakirkham]

Maybe something like a visitor pattern ( https://github.com/alimanfoo/zarr/issues/92 ) would help with this.

[alimanfoo]

Yep that could be useful. I was just thinking to produce some ASCII art showing the hierarchy down to a specified level, with node names and node types (Array/Group) as a minimum.

…

On Wednesday, November 30, 2016, jakirkham ***@***.***> wrote: Maybe something like a visitor pattern ( #92 <https://github.com/alimanfoo/zarr/issues/92> ) would help with this. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/alimanfoo/zarr/issues/82#issuecomment-263967668>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAq8QiKa8pKAvmzS4-jJZRIG4KKeU9p8ks5rDcxLgaJpZM4KQ6jg> .

-- Alistair Miles Head of Epidemiological Informatics Centre for Genomics and Global Health <http://cggh.org> The Wellcome Trust Centre for Human Genetics Roosevelt Drive Oxford OX3 7BN United Kingdom Email: [email protected] Web: http://purl.org/net/aliman Twitter: https://twitter.com/alimanfoo Tel: +44 (0)1865 287721

[jakirkham]

Sure, that would be good too. Maybe diagrams could be made akin to those used in Dask's graphs. Wonder if @mrocklin has any suggestions.

[mrocklin]

I would personally stick to ASCII. I would look at what PyTables does as well as bash tools like tree

mrocklin@carbon:~/workspace$ tree zarr
zarr
├── appveyor.yml
├── bench
│   ├── compress_normal.py
│   └── compress_normal.txt
├── build.cmd
├── c-blosc
├── cpuinfo.py
├── docs
│   ├── api
│   │   ├── codecs.rst
│   │   ├── core.rst
│   │   ├── creation.rst
│   │   ├── hierarchy.rst
│   │   ├── storage.rst
│   │   └── sync.rst
│   ├── api.rst
│   ├── conf.py
│   ├── index.rst
│   ├── Makefile
│   ├── release.rst
│   ├── spec
│   │   ├── v1.rst
│   │   └── v2.rst
│   ├── spec.rst
│   ├── _static
│   │   └── donotdelete
│   └── tutorial.rst
├── LICENSE
├── MANIFEST.in
├── notebooks
│   ├── blosc_microbench.ipynb
│   ├── dask_2d_subset.ipynb
│   ├── dask_copy.ipynb
│   ├── dask_count_alleles.ipynb
│   ├── genotype_benchmark_compressors.ipynb
│   └── zip_benchmark.ipynb
├── README.rst
├── release.txt
├── requirements_rtfd.txt
├── requirements_test.txt
├── requirements.txt
├── setup.py
├── tox.ini
└── zarr
    ├── attrs.py
    ├── blosc.c
    ├── blosc.pyx
    ├── codecs.py
    ├── compat.py
    ├── core.py
    ├── creation.py
    ├── errors.py
    ├── hierarchy.py
    ├── __init__.py
    ├── meta.py
    ├── meta_v1.py
    ├── storage.py
    ├── sync.py
    ├── tests
    │   ├── __init__.py
    │   ├── test_attrs.py
    │   ├── test_codecs.py
    │   ├── test_core.py
    │   ├── test_creation.py
    │   ├── test_filters.py
    │   ├── test_hierarchy.py
    │   ├── test_meta.py
    │   ├── test_storage.py
    │   ├── test_sync.py
    │   └── test_util.py
    └── util.py

9 directories, 62 files

[jakirkham]

This may be an option. ( https://github.com/mbr/asciitree )

[alimanfoo]

mbr/asciitree looks good. Already on conda-forge too I see.

…

On Wed, 30 Nov 2016 at 21:49, jakirkham ***@***.***> wrote: This may be an option. ( https://github.com/mbr/asciitree ) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/alimanfoo/zarr/issues/82#issuecomment-264006526>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAq8QsYv3KLzFXhxDQOSFor4GKoVu2-mks5rDe9ygaJpZM4KQ6jg> .

[jakirkham]

If you want to go the standard library way, maybe pprint would work. Though IMHO asciitree still looks pretty good.

[alimanfoo]

Yep asciitree looks good. Can be configured to produce output very similar to linux tree command:

>>> box_tr = LeftAligned(draw=BoxStyle(gfx=BOX_LIGHT, horiz_len=2, label_space=1))
>>> print(box_tr(tree))
asciitree
 ├── sometimes
 │   └── you
 ├── just
 │   └── want
 │       ├── to
 │       └── draw
 ├── trees
 └── in
     └── your
         └── terminal

[jakirkham]

Wanted to see how easy this would be now that we have visitor-style methods. Went ahead and threw together PR ( https://github.com/alimanfoo/zarr/pull/140 ). FWICT it seems to work ok.

That said, I don't know that I will be able to do lots of iteration on it near term. So if you are wanting to get it in quickly, please feel free to run with it.