Diesel-only NR runs with imported fuels produces no output #6
Labels
bug
Something isn't working
Milestone
Comments
|
A workaround for this issue until we release MOVES3.0.1 is to import a gasoline fuel supply and fuel formulations, even though they should not be used for your diesel-only run. To do so, add a gasoline equipment sector to your RunSpecand export the default fuels. Include the gasoline rows in both the fuel supply and the fuel formulations when you import the fuels data. After importing and getting a green check, you can remove the gasoline equipment from the RunSpec. |
danielbizercox
added a commit
that referenced
this issue
Jan 21, 2021
For the NR LF/AvgHP: The Go calculator is implicitly splitting both emissions and activity by fuelSubTypeID when that output is requested by the user. The issue is that the LF and AvgHP activity values shouldn't be split, but should be duplicated. Since it is happening implicitly in the Go calculator, we decided to simply recombine the LF and AvgHP values as soon as the Go calculator results are loaded by the Java, instead of adding a separate edge case in the Go. For NR diesel-only runs: When the user exports the default fuels, it only includes fuel types selected in the runspec. So when these fuels are reimported, there are no rows about gasoline. Unlike other tables, the nrfuelsupply table completely overwrites the default table (instead of being combined with the default table), so at runtime, there is no gasoline information. When the Java code is setting up the NR Fortran inputs, it doesn't have gasoline information, so it supplies 0 RVP. When the Fortran starts, it performs a validity check on the inputs, including valid RVP values (regardless if they will be used or not), and it quits when it sees an RVP of 0. The solution is to provide the Fortran with the default fuelFormulationID 10 RVP and sulfur levels when no gasoline values can be found. A warning is emitted when this occurs, so the user is aware and can make changes if this is unintentional.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you do a diesel-only nonroad run with imported fuels (i.e., you select only diesel equipment, and then you create a NR input database, export the default fuels, and then re-import them), you will get an error about RVP being out of range and you won't get output.
The text was updated successfully, but these errors were encountered: