-
based on a previous reply, I edited my node.csv and link.csv so that the ids are floats in both and I also used path4gmns==0.9.4. This got me through the first issue and i get the following warning output from 3.1
I am not sure if these issues stem from downgrading to 0.9.4 or if there is another problem with my data. thanks for your help! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Those warnings and exceptions are not errors of Path4GMNS. They are part of the internal validation which indicate what went wrong with the input data and what the possible fixes are. Take the first two warnings for example, Path4GMNS warns you that settings.yml is missing, and it will set up the run using the default values for demand period and agent type. You can find details on settings.yml in the tutorial under session 4.1 and in the Use Cases. Then the next one (i.e., KeyError: 'zone_id') informs you that the column of zone_id is missing from zone.csv. There is a column with header activity_zone_id rather than zone_id in your zone file. The last one is related to the length unit of links. As mentioned in the tutorial, Path4GMNS uses mile and mile per hour (mph) as the default units for length and speed in its internal calculation and all outputs. Links presented in your link.csv have large values in length, which do not make sense if mile is the unit. As the demand synthesis is subjected to a time budget (the default value is 120 min), no OD pairs are connected / reachable given this time budget and no demand is synthesized (see Synthesize Zones and OD Demand for details). Therefore, you got the last warning from Path4GMNS (i.e., "NO VALID OD VOLUME!! Double check your demand.csv and make sure there is zone info in node.csv'") as your demand_from tutorial.csv is empty. You can get around this issue by specifying the length unit as meter (or bumping up the time budget to a very large number). |
Beta Was this translation helpful? Give feedback.
Those warnings and exceptions are not errors of Path4GMNS. They are part of the internal validation which indicate what went wrong with the input data and what the possible fixes are.
Take the first two warnings for example, Path4GMNS warns you that settings.yml is missing, and it will set up the run using the default values for demand period and agent type. You can find details on settings.yml in the tutorial under session 4.1 and in the Use Cases.
Then the next one (i.e., KeyError: 'zone_id') informs you that the column of zone_id is missing from zone.csv. There is a column with header activity_zone_id rather than zone_id in your zone file.
The last one is related to the length unit of …