Garbage names in the cas vars menu

[rombva]

I wrote the program for the cas mode.

Code:

#cas
zf74(X,Y,γ,a,b):=
BEGIN
LOCAL f,v;
PRINT("---------------------------------");
PRINT("W#7, P#4:");
γ:=unapply(γ,x);
X:=unapply(X,{x,y});
Y:=unapply(Y,{x,y});
f:=expand(simplify(subst(X(x,y)+Y(x,y)*diff(γ(x),x),y=γ(x))));
PRINT("f(x)="+f+";");
PRINT("F(x)="+expand(simplify(∫(f,x)))+";");
v:=∫(f,x,a[1],b[1]);
PRINT(suppress("∫(f(x)"," ")+", x, "+a[1]+", "+b[1]+")="+v+when(FP(v)≠0,"="+ROUND(v,4),"")+";");
PRINT("---------------------------------");
1;
END;
#end

After a lot of runs in the CAS Vars menu the garbage or/and empty-names variables appear. This issue happens while running my other cas programs.

Command line:


Before running:


After running:


CAS Vars mem:

[Tim Wessman]

This on a calculator, emulator, etc?

[rombva]

(10-24-2019 07:04 AM)Tim Wessman Wrote:  This on a calculator, emulator, etc?

On a calculator (G2) and emulators (Win10, Android). Sometimes the run returns the input line without showing a terminal window.

[Tim Wessman]

I'd like to try and reproduce, but you have conveniently hidden your inputs in the screenshot. I see: zf74(2*x-y,-x*y,<--hidden by box---->,[2,8])

Can you copy the command line of your run in? Thanks. Also, give it a whirl on the latest 1.5.0 CAS version if you want.

[rombva]

(10-24-2019 10:06 AM)Tim Wessman Wrote:  I'd like to try and reproduce, but you have conveniently hidden your inputs in the screenshot. I see: zf74(2*x-y,-x*y,<--hidden by box---->,[2,8])

Can you copy the command line of your run in? Thanks. Also, give it a whirl on the latest 1.5.0 CAS version if you want.

Sorry. Command line: zf74(2*x-y,-x*y,2*x^2,[0,0],[2,8]).

[rombva]

(10-24-2019 10:06 AM)Tim Wessman Wrote:  ...

Can you copy the command line of your run in? Thanks. Also, give it a whirl on the latest 1.5.0 CAS version if you want.

On the beta emu (Windows, x64):

Run 01:


Run 02:


Run 03:


Run 04:


Run 05:


Run 06:


Run 07:


Run 08:


Run 09:


Run 10:

[Tim Wessman]

Thanks! Will investigate....

[FrankP]

On my Android Emu changing "∫" to "int" in line

PHP Code:

// v:=∫(f,x,a[1],b[1]);
v:=int(f,x,a[1],b[1]); 


avoided mem garbage generation. Maybe helps also in your case?

[compsystems]

This error also happened in XCAS see discussion

https://xcas.univ-grenoble-alpes.fr/foru...ile#p10348

[rombva]

(10-24-2019 09:58 PM)FrankP Wrote:  On my Android Emu changing "∫" to "int" in line

PHP Code:

// v:=∫(f,x,a[1],b[1]);
v:=int(f,x,a[1],b[1]); 


avoided mem garbage generation. Maybe helps also in your case?

That's right, thanks.

But after running the program in the cas vars menu the x variable with assumption of integration boundaries appears.

[parisse]

That's expected, because x is not declared as a local variable (add purge(x) after declaration to keep it symbolic).

[rombva]

(10-25-2019 06:00 AM)parisse Wrote:  That's expected, because x is not declared as a local variable (add purge(x) after declaration to keep it symbolic).

Thanks!

[Tim Wessman]

(10-25-2019 08:47 AM)rombva Wrote:  

(10-25-2019 06:00 AM)parisse Wrote:  That's expected, because x is not declared as a local variable (add purge(x) after declaration to keep it symbolic).

Thanks!

So just to clarify, when you changed to "int(...)" the problem basically when away? (letting us focus on the ∫(...) path exclusively to track it down)

[rombva]

(10-28-2019 01:30 AM)Tim Wessman Wrote:  

(10-25-2019 08:47 AM)rombva Wrote:  Thanks!

So just to clarify, when you changed to "int(...)" the problem basically when away? (letting us focus on the ∫(...) path exclusively to track it down)

Replacing the ∫(...) by the int(...) removed the garbage names genartion in my all cas programms.