[sage-support] Re: How to send (import) any sage variable back to other software in Sage e.g. Maxima or R
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()
'sage4'
sage: maxima('sage4')
sin(_SAGE_VAR_x)
--
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-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: How to send (import) any sage variable back to other software in Sage e.g. Maxima or R
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-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: How to send (import) any sage variable back to other software in Sage e.g. Maxima or R
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:
> ---Maxima mode---
> %maxima
> x=2
> ---Sage mode---
> y=maxima('x')
>
> So the value 2 of x variable defined in Maxima appears as a value of y
> variable in Sage.
>
> Problem statement) However, I am not able to do a reverse.
> I have no idea how to send a variable from Sage to Maxima.
>
it is not clear what you mean by "sending a variable"
What are you trying to achieve?
>
> Any advice, link or comment?
>
--
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-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: Sage Crash Report
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. Different CPUs support different machine hardware commands, and compilers are able to use this to produce faster code, at expense of portability. This is why a binary distribution needs to use the most basic subset of machine commands to be useful on all x86_64s. -- 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-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Re: Sage Crash Report
On Wednesday, June 21, 2017 at 3:01:09 AM UTC-7, Dima Pasechnik wrote: > > > > On Wednesday, June 21, 2017 at 9:04:12 AM UTC+1, whit3rd wrote: >> >> Seconds after install of version 7.6, on MacOS 10.11.6 >> on a MacBook Pro (Core 2 duo, 4GB RAM) >> > > it might be that the executable you downloaded needs a better CPU (Core 2 > duo is quite old...) > What exactly have you installed, what file? > > It's "sage-7.6-OSX_10.11.6-x86_64.dmg" for the installer. Core 2 is certainly both x86 and 64-bit. This CPU is 2.26 GHz, probably Penryn P8400 or SP9300 Apple MacBook Pro 5.5 is the machine designation > As well, it might be that you have some kind of conflict with some stuff > in /sw/ you have in your PATH. > Could you temporarily rename /sw/ and try again? > That works! Don't see any reason there'd be conflict, though. Sage doesn't put anything into /sw, but /sw overrides anyhow? How might I restore the /sw directory and still keep Sage running? -- 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-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
