For questions, use https://discourse.holoviz.org/ instead! This chat is for informal discussions and debugging sessions with developers of the HoloViz.org tools (HoloViews, Datashader, Panel, hvPlot, GeoViews, Param, etc.), but user questions should go to the HoloViz Discourse site so that others won't have to ask them again.
In my experience from a quant and trading environment there will be a lot of apps and people will search for information like where is the app, where is the documentation, who wrote this. who has access, what can I use this to, where is the code I want to code something similar? So the gallery is really for providing easy access to the apps and also for all kinds of meta data information.
In general I think the jinja templating is under communicated. A lot of the struggles I've been having for creating awesome looking apps is because I've been trying to use the Panel Layout. It's fine for exploration and initial work. But in the end a custom Jinja Template can make the difference.
I've "stolen" the awesome looking header image from some unknown data shader example. I guess it's by one of you guys. Let me know if that is a problem :-)
And the search function is just so awesomely fast and responsive. Check it out in the video here https://twitter.com/MarcSkovMadsen/status/1308801288830963714?s=20
Maybe HoloViz could use a gallery like that across all the different galleries for hvPlot, HoloViews, Panel, .....?
:-) Why do I have to navigate to the galleries in each of the sites if I don't know which or if I'm really trying to use several libraries together. I actually feel on the discourse there increasingly are questions on how to use the different libraries in combination or where the answer really is based an having a combined understanding. This combined understanding is not something many have (I claim) and something that the existing documentation does not focus on.
I don't know which header image that Datashader shot is, but I suspect it's from someone other than me, as that's not one of my usual colormaps. But at least I don't have any objection!
You can try out the gallery here https://awesome-panel.org/gallery. It loads a bit slow. I need to find out why. And then I need to fill in the data.
@MarcSkovMadsen Your gallery looks great. Could you make an issue with suggestions on how to improve the main Panel gallery?
Has anyone else seen this bug?
VM10348:52 Python failed with the following traceback:
/Users/kcp/.conda/envs/lbm/lib/python3.8/site-packages/pyviz_comms/__init__.py _handle_msg L316
/Users/kcp/.conda/envs/lbm/lib/python3.8/site-packages/holoviews/plotting/bokeh/callbacks.py on_msg L146
/Users/kcp/.conda/envs/lbm/lib/python3.8/site-packages/holoviews/plotting/bokeh/callbacks.py _process_msg L1203
/Users/kcp/.conda/envs/lbm/lib/python3.8/site-packages/holoviews/plotting/bokeh/callbacks.py <listcomp> L1203
ValueError: invalid literal for int() with base 10: 'dtype'It's cropped up in my code this week. I thought I had it narrowed down and reported it here holoviz/holoviews#4626 but now I noticed it on a completely different plot unrelated to annotators.
Thank you
Hi @sameerCoder . I can see you have posted on Discourse https://discourse.holoviz.org/t/how-we-cann-save-panel-plot-holoview-plot-bokeh-plot-in-geotiff-format/1234. Thanks. That is the right place for questions.
I'm dealing with a memory leak from hv.RGB. I've traced it back to the matplotlib backend (even though I'm running hv with the bokeh backend). It's possibly related to this mpl issue matplotlib/matplotlib#8519 . It may be related to this issue as well which has been labeled a bug holoviz/hvplot#501 .
Is there a workaround for NOT using mpl as the backend for hv.RGB?
So it should be able to stay with bokeh?
This is the tracemalloc:
[ Top 10 ]
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/site-packages/matplotlib/image.py:1663: size=402 MiB, count=6, average=66.9 MiB
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/posixpath.py:368: size=445 KiB, count=3417, average=133 B
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/linecache.py:137: size=336 KiB, count=3244, average=106 B
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/inspect.py:753: size=144 KiB, count=1, average=144 KiB
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/inspect.py:750: size=144 KiB, count=1, average=144 KiB
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/site-packages/IPython/core/builtin_trap.py:63: size=9248 B, count=1, average=9248 B
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/site-packages/IPython/core/compilerop.py:101: size=5446 B, count=96, average=57 B
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/json/decoder.py:353: size=3479 B, count=44, average=79 B
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/site-packages/param/parameterized.py:271: size=2184 B, count=13, average=168 B
/Users/kcp/miniconda3/envs/lbm/lib/python3.8/site-packages/tornado/gen.py:191: size=2088 B, count=8, average=261 BWith the bokeh ext loaded
Surprised plt.imread would create a figure.
maybe it's just using this function https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/image.py#L1642 to create the array?
And then make a PR to HoloViews to use that in RGB.load_image.
Right I have no idea why that would leak memory.
Right. so when I run the above, I can watch my machine memory increase incrementally every ttime and it never drops until I shutdown the kernel