Not setting an Attribute value results in an index out of bounds exception during planning about burlap HOT 3 CLOSED

Yeah that makes sense; in the past it's even been an error that's caused me some temporary confusion. I'll add it soon.

from burlap.

Is there a reason why values can't be negative, except that it would interfere with your unset feature? Could you just assume that if not set, it's default value is 0?

from burlap.

The reason disc values are not negative is because it represents an index into a categorical list which is a list of strings that you can name (e.g., red, blue). I should note that you can have "negative" values in that your categorical values represent negative values, but the actual underling data value would still be non-negative.

I thought about defaulting the discrete value to zero, but in the past I liked it being set to -1 because it would break the code, and I found it's usually a good idea to have the code break if you didn't initialize your values.

That said, I've also considered splitting up the discrete attribute into two different possible types: discrete numeric and discrete categorical. Discrete numeric would allow negatives and discrete categorical would be like it is now. Discrete numeric would have utility in that it can be unbound in values. That said, I haven't gotten around to implementing it yet because I haven't had a strong need to do so.

from burlap.