On Thursday, June 22, 2017 at 7:40:43 PM UTC+2, kcrisman wrote:
>
> Just in general, you should be able to do
>
> f = stuff
>
> y = maxima(f)
>
> z = y._sage_() # or maybe sage(y)
>
Furthermore, results transferred to interfaces are assigned to variables
sage: U=maxima(sin(x))
sage: U.name()
'sag
Just in general, you should be able to do
f = stuff
y = maxima(f)
z = y._sage_() # or maybe sage(y)
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-suppo
On Thursday, June 22, 2017 at 10:39:58 AM UTC+1, Jozef Hanč wrote:
>
> Probably a simple task.
>
> Environment: cocalc sage worksheet
>
> PROBLEM
> Background) It seems that I understand how to send a variable from e.g.
> Maxima mode (%maxima) to Sage mode.
> e.g. using this code in CoCalc:
> -
Probably a simple task.
Environment: cocalc sage worksheet
PROBLEM
Background) It seems that I understand how to send a variable from e.g.
Maxima mode (%maxima) to Sage mode.
e.g. using this code in CoCalc:
---Maxima mode---
%maxima
x=2
---Sage mode---
y=maxi
It should be enough to run Sage in a shell session where PATH variable does not
contain anything from /sw/.
(there may be more variable that might affect running Sage, although this is
probably a bug then)
PS. it is true that Core2 duo is x86_64, but not all such CPUs are created
equal. Differ