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
Technicially I suppose it is well done to read in prt5 data either by Fortran or python, but visualizing trajactory of evac agents is more difficult because there are many different scenarios in evac simulation.
So far this python program deals with one-floor scenario because it dispays agents' trajactories in 2D space. It is not difficult to extend the program to select on which floor the agents are to be displayed if there are multiple floors in simulation, but I do not have much time to complete this task. It is also probably feasible to extend the data content in prt5 files to display more features of agents (e.g., velocity and acceleration). Anyway, if anyone is interested and wants to help me to do that, I will be very glad to complete these tasks with them. @chraibi
Add a small GUI (e.g., tkinter or wxpython)
Select the agents data in prt5 file for different floors (MESH height variable z)
Comment or suggestion are much welcome!
The text was updated successfully, but these errors were encountered:
Technicially I suppose it is well done to read in prt5 data either by Fortran or python, but visualizing trajactory of evac agents is more difficult because there are many different scenarios in evac simulation.
So far this python program deals with one-floor scenario because it dispays agents' trajactories in 2D space. It is not difficult to extend the program to select on which floor the agents are to be displayed if there are multiple floors in simulation, but I do not have much time to complete this task. It is also probably feasible to extend the data content in prt5 files to display more features of agents (e.g., velocity and acceleration). Anyway, if anyone is interested and wants to help me to do that, I will be very glad to complete these tasks with them. @chraibi
Comment or suggestion are much welcome!
The text was updated successfully, but these errors were encountered: