In my effort to add costs to my transport model, I have come across what I think might be a software error. If not, I don't know how to replace it at this time.

My data method is as follows:

I have a standard 2005 petrol car Key Assumption, currently priced at 100,000 Chinese RMB. For the years towards 2017 and projections towards 2050, the price is given as a factor on the Key Assumption, dependent on the different years and technologies. The factors range between 0.8 and ~3.5.

An example of my method is this:

Current Accounts (2010-2017): Key\Transportation\Standard car device_cost[Yuan]*Interp(2005,1.09,2010,1.053,2015,1.02125)

Projection (scenarios 2018-2050): Key\Transportation\Standard car device_cost[Yuan]*Interp(2020,0.98975,2025,0.9675,2030,0.945,2035,0.91375,2040,0.88275,2045,0.852,2050,0.8215)

And here is where things get a little weird.

In Current Accounts, the Table price for the vehicle prices are now divided by 1000, so 117,000 Yuan is expressed as 117.0. I tried redefining the Key Assumption to 100 [thousand] RMB, same result. Setting the Current Accounts input to 100000 directly yields the table of 100.0, so same result. See Current Accounts.png

In the scenarios, the error is different.

Using the formula, the 2010-2017 result is now divided by 1 million, making 100,000 into 0.1 RMB.

In year 2017, the price increases to a couple thousand (e.g. 2,095.064750 for Petrol car), where after it decreases with the interpolation to the previous 1 mill. division, which carries on until 2050.

If I input 100000 directly into the scenario, year 2017-2050 is 0.1 RMB. The error seems to carry over if I compute the model in results.

These errors are shown in Device cost error.png and graph.png.

I have yet no set fuel prices, but that shouldn't influence this I presume?

Happy 4th of July to You

Gregers

Keeping in mind that Demand Costs using the "Device Cost" method for stock-turnover branches are applied only for the year in which the vehicle is sold, can you confirm that these unexpected results occur *also* in the Results view, and not just in the table or chart under Analysis view?

The table below the expression window will occasionally display values which do not properly refresh after a change is made, or which display an incorrect order of magnitude. However, these issues should not persist in the calculated results.

Taylor