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 am trying to use plotly (offline mode) in python along with orca to export contour plots to SVG.
Given below is the function I use to create contour plots and export it to SVG
It takes roughly 20s to create an SVG every single time. Is this expected behavior?
I though maybe file IO part of the write command is causing that delay so instead of the write_image, I used the to_image to get a bytes representation of the same. That didnt help with the runtime either
I ran the orca server manually in debug mode (looked at a few posts in forums) but I dont know how to make sense of it.
Can someone help me out?
The text was updated successfully, but these errors were encountered:
Thanks for the quick reply. I did some further digging into my issue. I work behind an enterprise firewall and I suspected that gating/slowing down the orca server somehow. So I tested the same script with same data on a Mac and Win PC outside of the enterprise network and was able to always get plotly+orca to export static images in under 0.3sec.
So at this point I think orca + plotly are not to blame. They are working as they should. Thanks for the great work with orca and plotly 👍 :)
I am trying to use plotly (offline mode) in python along with orca to export contour plots to SVG.
Given below is the function I use to create contour plots and export it to SVG
It takes roughly 20s to create an SVG every single time. Is this expected behavior?
I though maybe file IO part of the write command is causing that delay so instead of the
write_image
, I used theto_image
to get a bytes representation of the same. That didnt help with the runtime eitherI ran the orca server manually in debug mode (looked at a few posts in forums) but I dont know how to make sense of it.
Can someone help me out?
The text was updated successfully, but these errors were encountered: