danielbizercox
commented
6 months ago Hello,
This is a complicated portion of the model because the operating mode distributions on each link vary by source type, regulatory class, and model year (due to differences in vehicle mass and road load coefficients, as stored in the SourceUseTypePhysics table of the default database). Unfortunately, the tables involved in these calculations do not have fields for all these variables, so the intermediate calculated operating modes are stored in a very unintuitive way. To keep things more manageable, I recommend looking at this with a very simple RunSpec: ideally one link, one source type, and one model year (i.e., provide an age distribution that has one model year with an ageFraction of 1.0, with all other model years set to 0.0), and just running energy consumption.
However, that said, you can have MOVES save the operating mode distributions used on each link by checking the "Save Data" box for the "Project-Domain Operating Mode Distribution Generator (running exhaust)" component on the Advanced Features panel. Lower on the same panel, check "Copy Saved Generator Data" and give a database name. And please be aware that there are some issues in the GUI when it comes to this feature, so after saving the RunSpec, double-check that your selections actually made it into the .mrs file. It should have an entry in the <savedata> tag for LinkOperatingModeDistributionGenerator, and the <generatordatabase> tag should look like this: <generatordatabase shouldsave="true" servername="" databasename="dbnamehere" description=""/>
After running, look in the "Saved Generator Data" database that you specified for the opmodedistribution table. This will contain the actual operating mode distributions that were used for each link.
- LinkID: The linkID column contains the linkID(s) that you specified in the link table. It will also contain negative linkIDs. These negative values correspond to driving schedule IDs (see the
drivescheduletable in the default database) that were used to develop the interpolated operating mode distributions.- For example, if you had a run where linkID 1 had short-haul single unit trucks traveling at an average speed of 5 MPH on a non-restricted access road, you would have operating mode distributions for linkID 1 (the composite distribution), linkID -201 (corresponding to the MD 5mph Non-freeway drive schedule), and linkID -202 (corresponding to the MD 10mph Non-freeway drive schedule).
- OpModeID: the opModeID column contains offset opModeIDs. The last two digits represent the true opModeID, and the other digits are an arbitrary offset. Each offset corresponds to a specific regulatory class and model year range, based on the applicable rows for the source type in question in the
SourceUseTypePhysicstable.- For example, a calendar year 2024 run with a default age distribution has 18 applicable rows in
SourceUseTypePhysicsfor short-haul single unit trucks, so it will have 18 different offsets ranging from 10-27 (the offsets must be at least two digits long). OpModeID 1001 corresponds to opModeID 01 for the first regulatory class / model year range; opModeID 1101 corresponds to opModeID 01 for the second regulatory class / model year range. During a MOVES run, you can examine themovesexecutiondatabase’sSourceUseTypePhysicsMappingtable to map the offset to the regulatory class / model year range.
- For example, a calendar year 2024 run with a default age distribution has 18 applicable rows in
In summary, it is possible to review the operating mode distributions that MOVES calculates at Project Scale, but it is complicated because each link actually has multiple operating mode distributions, one for each applicable source type / regulatory class / model year range.
Hanisek
If I run links with default driving cycles (only average speed specified - no user inputs for opMode or driving cycles) in a project-level analysis (running-exhaust only), what would be a good way to see the actual opmode distributions that are used for each link (which options do I need to check to save these outputs)? I understand these distributions were interpolated based on the embedded cycles, and I just want to learn more about how to properly use rates operating mode distribution generator vs. lookup operating mode distribution generator vs. project-domain operating mode distribution generator - mostly just opMode distributions (no polProcess)..