-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time axis value is coming wrong #85
Comments
I'm sorry for the very slow response. @mleivaf can you check on this? |
Hello, The steps in the X axis are defined automatically by the plot (plot_tracer.m#L150) But you can force the plot to get the steps required by you. For example:
Create proctime plot
Now you can set the X-axis step on octave console with these commands.
Also, you can add this code here: plot_tracer.m#L150 to get always the same result. |
Hi @mleivaf Thanks for your response. When I generate tracers, created folder contains only two files like below:
tracers folder should contain proctime.mat ? As I am new to matlab coding, I added above mentioned line at https://github.com/RidgeRun/gst-shark/blob/master/scripts/graphics/plot_tracer.m#L150 and it is giving error:
error: called from Best Regards, |
Hi, The proctime.mat file is created here: gstshark-plot#L133 I am not sure if these scripts work with Matlab, but based on this link: https://www.mathworks.com/help/matlab/ref/xticks.html I recommend using GNU Octave for your tests https://www.gnu.org/software/octave/download.html Regards, |
I am able to draw different plots for tracers interlatency, proctime and etc.
But in all plot diagrams, I am getting time axis wrong.
In example diagram : https://developer.ridgerun.com/wiki/index.php?title=File:Test_proctime_plot.png, I could see time scale is 0, 0.5sec, 1sec, 1.5sec and so on.
But when I plot, I am getting time axis as 0, 41401, 41402, 41403 and so on.
How to get timescale like shown in your examples ?
I am using Ubuntu version : 18.04
Gstreamer : 1.16
Thank you
Naveen
The text was updated successfully, but these errors were encountered: