MATLAB visualizations on ThingSpeak appear distorted and low-resolution when accessed via the public URL, despite rendering correctly when run manually

Over the past few days, I’ve observed that MATLAB visualizations on ThingSpeak are not rendering correctly when accessed via the public URL. When I run the MATLAB Visualization script manually within ThingSpeak, the resulting image has the correct resolution and aspect ratios. However, accessing the same visualization through the public URL generates a much smaller image with distorted proportions.

The script itself hasn’t been modified for a long time, and this issue has only started occurring recently. Could this be related to a recent change in the rendering engine or visualization settings on ThingSpeak?

I would appreciate any guidance or insight into what might be causing this discrepancy.

Thank you!

[Vinod]

Can you please share your channel publically and link to it so I can take a look?

[Mi He2]

https://thingspeak.mathworks.com/apps/matlab_visualizations/532592

[Mi He2]

When I opened this link, the page with the graph displayed normally according to the resolution set in the script… see the images above.

Answer 1

[Vinod]

I suspect what you're seeing is dependent on your browser window size and screen resolution. If you are embedding the graphic on your webpage, you may want to consider adding the height and width paramter to the visualization. For example:

https://thingspeak.mathworks.com/apps/matlab_visualizations/532592?height=auto&width=auto

[Mi He2]

You're a magician! The aspect ratio wasn't perfectly preserved — some text objects are slightly out of place — but it's OK. Still, I keep wondering why it suddenly stopped working... Thank you! M.

Answer 2

[Sulaymon Eshkabilov]

It is not low resolution but it is because of the axis scale and window size in the public version display as indicated by Vinod. If one looks at both graphs, he/she will see that in the grash displayed in the MATLAB environment, x-axis is zoomed in. Besides, the top two graphs are not captured at the same time.