Update on 10/16

[cheny51]

After we scaled up the timeslot that serve each user, we realized that the server tends to prioritize all its time to process the one with greater arrival rate user first and then go back and process the lower arrival rate.

This is not what we wanted, we want that server to finish their tasks within the given time (i.e. 1800s) for BOTH user.

One thing we need to fix right now is to have the server stop working once it hit tfinal (1800), even if there's any packet remaining, no more processing.

Another thing would be to have the code to no longer increase age (or consider user idling) once ALL packets were finished process to show a better age accuracy for the user. (right now we made it such that the user that finished their packets early need to wait until the other user to finish and this is not what we wanted)

Then another thing would be to set in the code that prevent prioritize from happening between a low and high arrival rate user, I believe in doing the age would be much better for the high arrival rate.

[cheny51]

Another thing would be to have the code to no longer increase age (or consider user idling) once ALL packets were finished process to show a better age accuracy for the user. (right now we made it such that the user that finished their packets early need to wait until the other user to finish and this is not what we wanted)

On this, I am just now able to do this. There are couple things I observed.

For the user with high arrival rate and a user with very low arrival rate, assigning more and more slot duration to the low arrival rate user will cause the high arrival rate user to experience an increase of average age!

Also on this enhancement, I made a couple lines that would take into consideration that if we assign large resource of slot to high arrival rate, it has the opportunity to help the high arrival rate user to finish all its requested packets in less than the maximum time given to transmit (that is also by probability of course since we do not control when transmission can appear).

Also on the plot about delay. So the delay plot actually only have 1 user showing up, which is weird. And I thought about it, and I think the reason could be that delay is only considered when it is successfully being transmitted. Since low arrival rate user never really got a chance to make a transmission until their slot duration got bigger, there isn't a delay calculated for them?
The simulation here, user 1 lambda = 1/100, user 2 lambda = 1/45, mu = 1/30, slot_scalar = 6


Fig_file_image.zip