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
In the configurations options' list given in the github repository, there's no parameter given as "max_pf_iterations". But when I run the example networks (say Springfield), there I find this parameter "max_pf_iterations =1" generated on the output ft_output_config.txt file. Later when I added this parameter in the input config_ft.txt file with a value equal to 2 and ran the simulation, it's throwing an error. I tried this with other networks too, but the same error kept coming for multiple pathfinding iterations in each and every case.
Can you please check what might be the reason for this unexpected error? The ft_debug.log and ft_output_config files have been attached.
The max_pf_iterations flag isn't being read. This is resolved in a PR under review right now. Until that PR is accepted, the code defaults to 10 pathfinding iterations. The key error looks different, but I can't be for sure.
In this case, it's finishing after 1 pathfinding iterations by default. I should have added that I was using the codes from the "develop" branch, if this might be one of the reasons?
In the configurations options' list given in the github repository, there's no parameter given as "max_pf_iterations". But when I run the example networks (say Springfield), there I find this parameter "max_pf_iterations =1" generated on the output ft_output_config.txt file. Later when I added this parameter in the input config_ft.txt file with a value equal to 2 and ran the simulation, it's throwing an error. I tried this with other networks too, but the same error kept coming for multiple pathfinding iterations in each and every case.
Can you please check what might be the reason for this unexpected error? The ft_debug.log and ft_output_config files have been attached.
ft_debug.log
ft_output_config.txt
The text was updated successfully, but these errors were encountered: