-
Notifications
You must be signed in to change notification settings - Fork 0
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
Script for plotting Queue Delay #1
Comments
ns-2 or ns-3? Because now we have an API to fetch packet sojurn time.. we could use it for plotting queue delay in ns-3. |
Both.
…On Fri, Nov 23, 2018 at 3:53 PM Vivek Jain ***@***.***> wrote:
ns-2 or ns-3?
Because now we have an API to fetch packet sojurn time.. we could use it
for plotting queue delay in ns-3.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC4PvwTe_WR6J_9aBgXiBicekI_q4DiXks5ux8yYgaJpZM4YwXiC>
.
|
It would be nice if we have a script for ns-2 also. |
For ns-2, Viyom can help I guess.
For ns-3, I was thinking to templatize our examples so as to remove code
redundancy. Also, I could prepare small snipets or better library to
automate our tasks
|
All of this is welcome!
…On Fri, Nov 23, 2018 at 3:58 PM Vivek Jain ***@***.***> wrote:
For ns-2, Viyom can help I guess.
For ns-3, I was thinking to templatize our examples so as to remove code
redundancy. Also, I could prepare small snipets or better library to
automate our tasks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC4Pv4eyu0nCX__TsMYa6sSk-_h-vCGsks5ux826gaJpZM4YwXiC>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Like we have scripts to extract results and plot throughput and queue length graphs, we must have a script that extracts and plots queue delay graph.
The text was updated successfully, but these errors were encountered: