Successfull translating from excel to c, but getting many failure test

[kubido]

Hi @tamc

I'm using the calculator (the old one) for indonesia here (http://calculator2050.esdm.go.id)
we made some changes to the model.xlsx (here)
when trying to translate the model into c, it getting many test failures. log file

My assumption it's a excel version issue?

Regards

[tamc]

The simplest possible cause is that the Excel had not been recalculated before it was saved. It is worth triggering a manual recalculation in the excel, saving it, and running the conversion again.

If that isn’t the reason, then the next possibility is that it is some failure in the conversion process. I can take a look, but not until later in the week.

All the btest

Tom

On 28 Mar 2016, at 19:18, Rifki Fauzi [email protected] wrote:

Hi @tamc

I'm using the calculator (the old one) for indonesia here (http://calculator2050.esdm.go.id)
we made some changes to the model.xlsx (here)
when trying to translate the model into c, it getting many test failures. log file

My assumption it's a excel version issue?

Regards

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[kubido]

Hi Tom,
after tracing the values. I dunno why it seems it's load wrong vector.

for example
we defined in "electricity_f77" will be pointed into vector 'E.01 / column_V5' in sheet 2011.
but it return wrong column in model.c it pointed to another vector.. let's called 'C.02 / column_X5'

what's the possiblitiy of this? is that something we missed in the excel model?

[tamc]

Ok. I will take a look. Though may not get to it until the weekend.

On 31 Mar 2016, at 09:43, Rifki Fauzi [email protected] wrote:

Hi Tom,
after tracing the values. I dunno why it seems it's load wrong vector.

*for example: *
we defined in "electricity_f77" will be pointed into vector 'E.01 / column_V5' in sheet 2011.
but it return wrong column in model.c it pointed to another vector.. let's called 'C.02 / column_X5'

what's the possiblitiy of this? is that something we missed in the excel model?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[tamc]

The first thing I have found is this:

On sheet XII.a, cell N16 and similar, it has:
=INDEX(INDIRECT("'"&XII.a.Inputs[#Headers]&"'!Year.Matrix"),MATCH("SubTotal."&$A$2,INDIRECT("'"&XII.a.Inputs[#Headers]&"'!Year.Modules"),0),MATCH([Vektor],INDIRECT("'"&XII.a.Inputs[#Headers]&"'!Year.Vectors"),))

Which the excel to C translation gets wrong.

It expects the arguments to MATCH to be made explicitly, i.e., by using a ,0) rather than ,) as in:

=INDEX(INDIRECT("'"&XII.a.Inputs[#Headers]&"'!Year.Matrix"),MATCH("SubTotal."&$A$2,INDIRECT("'"&XII.a.Inputs[#Headers]&"'!Year.Modules"),0),MATCH([Vektor],INDIRECT("'"&XII.a.Inputs[#Headers]&"'!Year.Vectors”),0))

Changing those gets the number of errors down to 18. I will look at what is causing those next.

Best wishes

Tom

On 28 Mar 2016, at 19:18, Rifki Fauzi [email protected] wrote:

Hi @tamc

I'm using the calculator (the old one) for indonesia here (http://calculator2050.esdm.go.id)
we made some changes to the model.xlsx (here)
when trying to translate the model into c, it getting many test failures. log file

My assumption it's a excel version issue?

Regards

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[tamc]

Ok. That seems to be it. If I replace all the times that the Excel uses ,) with ,0) then the translation happens without errors.

[Pistorius]

hi @tamc Im working in the Calculator from Chile and im getting problems trying to convert my xlsx file. I have an issue here

Greetings