Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot override period type during import #154

leonardo-calcagno opened this issue Feb 24, 2015 · 1 comment


None yet
2 participants
Copy link

commented Feb 24, 2015

This issue makes it impossible to simulate a model with a starting period of 1. When you want to simulate a model with a period named 1, you get an error message stating that the variable period is a boolean. Specifying it is an integer in the fields section before simulation does not solve this. Usually you would solve this by specifying the type of the "period" variable when importing the dataset. But if you want to specify it you get the error message "two fields with the same name", since the period field is automatically added by LIAM2 (which assumes it is a boolean).
It is a small bug, the workaround being naming your period with any number greater than 1 (since LIAM2 automatically recognises it is an integer when doing so), but still a bug.

@gdementen gdementen added the bug label Feb 25, 2015

@gdementen gdementen self-assigned this Feb 25, 2015


This comment has been minimized.

Copy link

commented Feb 25, 2015

The fact the period is considered boolean is normal, because it sees a column with only 1. The fact that you cannot override it is the actual bug.

@gdementen gdementen changed the title When first period is 1, the period variable is mistaken with boolean Cannot override period type during import Feb 25, 2015

@gdementen gdementen modified the milestone: 0.10 Mar 24, 2015

@gdementen gdementen closed this in 3315ba5 May 19, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.