The interface is about to have 3 regions: the traffic flow visualizer , the manipulation buttons , the parameter setting . For now (2025.03.22), the interface is partially developed as the following image
🏆2025.03.22
| the first update
| interface initial push with start
button, pause / restart
button, visualization
regeion and frame slider
update details🚀:
- The
start
button can start the traffic simulation with the example data inExample_Data.mat
. - The
pause / restart
button can pause the whole simulation in any time when it is pushed for the first time. When it is staying at thepaused mode
, push it could be restarted by push it again exactly at its pause point. - The
visualizer
region is able to visualize the simulation process with the provided traffic data. - The
frame slider
is a marker of the simulation frames updated for now. It can dynamically update its limitations and sticks when the simulation goes on.
🏆2025.04.05
| the 2nd update
| add the back play function to the pause / resume button; add the clean_app.mlapp app script which stand for cleaned application with novel function
update details🚀:
- When
pause
button is pushed, the text of the button will be changed intoresume
and vise-versa. - The
auto-saving
capability is added into our application with frequency of 10 steps per save. - The
back-play
function is added which is activated when the application is inpause
mode and could display the history traffic condition from whenever the slide pointer designated. - The
back-play
process will use the history data rather than re-calculating them.
🏆2025.05.12
| the 3rd update
| add the Road slope
change trimmer for the 1st and 2nd road part; add the Save
and Load
button for saving / load of simulation data; add the Logger
of whole software
update details🚀:
- The 2 trimmers
Road1 slope
andRoad2 slope
are added for custom changing of road appearance with 2 modes: 1) directly change the slope number via re-typing the number in value box; 2) slightly change the slope value by using the step-by-step increase or decrease button in the step of 1 at a press time. - The function of
Save
andLoad
button is different from theauto-saving
function in the last update which is to save the simulation info of simulation in this time. To be specific, theSave
button is to let the software aware whichauto-saving
data belongs to this simulation when the user would like to take a look at his historical data. TheLoad
data is to load the historical data by user interface. - The
Logger
part is to save every button press or accomplished operations at the format of time + operation content.
This repository has 2 branches: Master
and Interface_code
. The master
branch is consisted of source code on traffic flow simulation. The Interface_code
branch is the latest branch where source code has been assemble into an interactive user interface.
To be noted that the interface_code branch also contains all useful source code in main
branch, therefore, directly download interface_code
repository should come in handy. In addition, the traffic_simulation2.m
is the runner file for the source code part.
Last but not least the files and their corresponding of interface part can be listed as:
Example_Data.mat
is the example traffic flow data used as data formulation examplary and demonstration;
app2.mlapp
is the matlab coded application with 'App Designer' module which constain all source code of the lastest release (Beta version, with newest functions but unsatble) of our software;
clean_app_*.mlapp
stand for the clean version of our software which will usually be realeased together with the 'app2.mlapp'. To be noted that the 'cn' means Chinese version interface anden
stands for its English version conterpart.
cache_data
repository is to save the automatically cached data from software.
simulation_history
repository is to manually save the simulation history from software.