Skip to main content
1-Visitor
February 1, 2012
Question

Bug in Symbolics or ignorance on my part?

  • February 1, 2012
  • 5 replies
  • 10436 views

Can anybody explain, why the variable x is not known by the symbolics machine? Is this a bug or am I doing something wrong?

In my original file x would be a much larger list of more or less arbitrary numbers which can not be derived by a function. I mention this, because defining x.i:=3*i would not produce that error.

Regards

WR

Symb_Err.png

5 replies

24-Ruby IV
February 1, 2012

An other variant:

SymSum.png

24-Ruby IV
February 1, 2012

I think we cannot use this operator in symbolic calculation:

SunProdSym.png

19-Tanzanite
February 1, 2012

It doesn't like the way you have defined the vector "a". I'm not sure if the way you are doing that is officially supported or not (I have seen it before, but I can't find it anywhere in the documentation). If it is, then it's a bug. If not, then arguably it isn't. If you define your vector using insert matrix or insert data table, it works.

1-Visitor
February 1, 2012

The construct is a comma-separated vector.

Mona

19-Tanzanite
February 1, 2012

OK, it is documented

So the fact that the symbolics will not recognize it is a bug.

1-Visitor
February 1, 2012

I think it is a bug. Frequently I get that message (Undefined variable) and I solve the problem only by deleting the variable and typing it again in the affected equation.

19-Tanzanite
February 1, 2012
I think it is a bug. Frequently I get that message (Undefined variable) and I solve the problem only by deleting the variable and typing it again in the affected equation.

I tihnk that is something different. Next time it happens please post the worksheet here.

12-Amethyst
February 6, 2012

I don't think the symbolic algorithm should be able to do a summation on a range variable. Range variables are for indexes. Valery has shown how everything works if you create a real vector. The "comma separated vector" appears to be still a range variable, not a vector. I wouldn't regard this as a bug.