Post Reply 
Complex solve BUG FW 2016 04 14 (10077)
05-20-2016, 01:17 PM (This post was last modified: 05-20-2016 02:00 PM by DrD.)
Post: #12
RE: Complex solve BUG FW 2016 04 14 (10077)
Other than the direct [CAS] command line entry I mentioned previously, programmatically, this code snippet returned the expected result:

Code:

EXPORT Test()
BEGIN
  LOCAL c1:=231.0e3, c2:=0.91+i*0.012, c3:=13.2+i*97.55, c4:=400.0e6, c5:=0.9;
  CAS.csolve("(c1/c2)-(c3/c2)*c4*(1-i*tan(acos(c5)))/(3*CONJ(x))-x=0",x);
END;

Whereas, this program snippet returns empty list:

Code:

EXPORT Test()
BEGIN
  LOCAL c1:=231.0e3, c2:=0.91+i*0.012, c3:=13.2+i*97.55, c4:=400.0e6, c5:=0.9;
  CAS.csolve("(c1/c2)-(c3/c2)*c4*(1-i*tan(acos(c5)))/(3*conj(x))-x=0",x);
END;

The difference is the UPPER CASE CONJ(x) in the successful first snippet. I know this may be viewed as a bug in r10077, and a change from earlier releases, but CONJ() is a [HOME] command, shown in upper case, and described as such in the help file. It isn't a smooth operation, for sure. The lower case command is changed to upper case in the history view, so it *could* get changed during program execution, (or command line parsing), as well. It could be made to fail at compile time. It could be made to work in either case and solve things as anticipated. There are things that can facilitate the use of this command. With the many related topic discussions associated with solve, et al, it sure seems like this is a popular area seeking improvement. Maybe the gods will bless us with another release that solves solve sufficiently, soon!

-Dale-
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Complex solve BUG FW 2016 04 14 (10077) - DrD - 05-20-2016 01:17 PM



User(s) browsing this thread: 1 Guest(s)