You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been playing around with holoviews and datashader operation, and discovered some changes between v1.14.9 and v1.15.0.
I usually build custom datashader operations for dynamic visualisation of big dataset, and i have to optimize operations for the visualisation to be smooth.
Before 1.14.9, when the holoviews.core.operation.Operation._process function was called, every print method was sent to the browser console log.
With holoviews >= 1.15.0, it seems print are no longer in the browser console.
example gif with holoviews 1.14.9 :
same example with holoviews 1.15.0 :
with upgrading 1.14.9 => 1.15.0, I noticed that the number of call to holoviews.core.operation.Operation._process was reduced for pane movement, the holoviews object wait till the click is released which i agree is a massive improvement (callbacks no longer stacks). Same for zooming which wait until the zoom is finished instead of computing the image every zoom done.
I noticed in the changelog that there was changes made with javascript callbacks (pull #4329) and some commits are about javascript, but i did not dig deeper about it because my javascript knowledge is limited.
Is the delete of print in webbrowser console log something wanted ? Is there a way to have both print in logs AND improvements about callbacks number and stacking ?
For now, i have to develop my functions in 1.14.9 in order to have logs when i play with panning and zooming, to see how many times my function take to rasterize for example, or some logs.
Then i deploy those function in an conda env with holoviews >= 1.15.0.
Thanks
The text was updated successfully, but these errors were encountered:
(I used spread operation only for visualisation purpose, or the points won't be big enough for the gif. The problem still occur without this operation)
Hi,
I've been playing around with holoviews and datashader operation, and discovered some changes between v1.14.9 and v1.15.0.
I usually build custom datashader operations for dynamic visualisation of big dataset, and i have to optimize operations for the visualisation to be smooth.
Before 1.14.9, when the
holoviews.core.operation.Operation._process
function was called, everyprint
method was sent to the browser console log.With holoviews >= 1.15.0, it seems print are no longer in the browser console.
example gif with holoviews 1.14.9 :
same example with holoviews 1.15.0 :
with upgrading 1.14.9 => 1.15.0, I noticed that the number of call to
holoviews.core.operation.Operation._process
was reduced for pane movement, the holoviews object wait till the click is released which i agree is a massive improvement (callbacks no longer stacks). Same for zooming which wait until the zoom is finished instead of computing the image every zoom done.I noticed in the changelog that there was changes made with javascript callbacks (pull #4329) and some commits are about javascript, but i did not dig deeper about it because my javascript knowledge is limited.
Is the delete of print in webbrowser console log something wanted ?
Is there a way to have both print in logs AND improvements about callbacks number and stacking ?
For now, i have to develop my functions in 1.14.9 in order to have logs when i play with panning and zooming, to see how many times my function take to rasterize for example, or some logs.
Then i deploy those function in an conda env with holoviews >= 1.15.0.
Thanks
The text was updated successfully, but these errors were encountered: