Extexpr issue

[Ben]

Hello,

I can't seem to make extexpr work for n > 2, even though the extexpr test in `liam2/tests/functional/simulation.yml` works well.

Attached is a minimal working example that reproduces the issue on my computer. Using extexpr with aither a global array or a filepath leads to the following error:

ERROR: {values of array a} is ambiguous (valid in a, b)
when evaluating: extexpr('table.csv')

In the example attached, the error is thus:

ERROR: [ True  True  True] is ambiguous (valid in a, b)
when evaluating: extexpr('table.csv')

Any idea about what may be wrong? It seems to me that `table.csv` has the same structure as the `regr_test*.csv` files.

Thanks.

By the way, I don't know if the appropriate channel for troubleshooting questions (ie neither bugs nor enhancements) would be github issues or here.

Best,
Benjamin

[Gaëtan de Menten]

This is what you get from working on the development version 😊. It is known issue and is on my TODO list to fix this before the release.

 

The problem is that it currently matches axes of the "extexpr array" with the variables of your entity based on the values they have. This is both inefficient and leads to a problem if some labels are the same on several axes, like in your case the a and b axes both have True and False values.

 

Gaëtan

 

--
You received this message because you are subscribed to the Google Groups "liam2-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liam2-users...@googlegroups.com.
To post to this group, send email to liam2...@googlegroups.com.
Visit this group at https://groups.google.com/group/liam2-users.

Disclaimer: This e-mail may contain confidential information which is intended only for the use of the recipient(s) named above.
If you have received this communication in error, please notify the sender immediately and delete this e-mail from your system.
Please note that e-mail messages cannot be considered as official information from the Federal Planning Bureau.

[Ben]

Ok, thanks for the answer. I'll create a Github issue as this looks like a bug, and not an error on my side.

Best,
Benjamin