Re: [sage-support] Re: maximal integrals
Le mar. 19 févr. 2019 à 23:39, Nils Bruin a écrit :
>
> On Tuesday, February 19, 2019 at 2:04:54 PM UTC-8, slelievre wrote:
>>
>> but how does one get information in a Maxima session about settings
>> such as besselexpand, display2d, domain, keepfloat,
>
> These are just global variables, so "display2d;" will give you the value.
>
>> and loaded
>> modules such as to_poly_solve, simplify_sum, abs_integrate, diag?
>
> I think apropos(""); will usually give different results,
> depending on whether the package has been loaded or not.
Thanks for explaining. But is there a way to get the value of all global
variables, or all that don't have their default values? And to get a list of
all packages that are loaded but are not usually when Maxima starts?
It would be nice if `bug_report();` would include that information.
--
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: maximal integrals
On Tuesday, February 19, 2019 at 2:04:54 PM UTC-8, slelievre wrote:
>
> but how does one get information in a Maxima session about settings
> such as besselexpand, display2d, domain, keepfloat,
>
These are just global variables, so "display2d;" will give you the value.
> and loaded
> modules such as to_poly_solve, simplify_sum, abs_integrate, diag?
>
I think apropos(""); will usually give different results,
depending on whether the package has been loaded or not.
--
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: maximal integrals
Tue 2019-02-19 08:20:24 UTC+1, Enrique Artal:
>
> I'll do it, but anyway it is strange that the wrong result
> is not reproduced using sage -maxima.
Running `sage --maxima` (or `sage -maxima`) in a terminal
launches plain Maxima, with Maxima's default settings.
When Sage perform some symbolic computations, it starts
Maxima internally with other settings than the default ones.
In particular, most of these probably differ from standard Maxima
('complex' for sure; 'to_poly_solve' and 'abs_integrate' too, I think):
'besselexpand : true',
'display2d : false',
'domain : complex',
'keepfloat : true',
'load(to_poly_solve)',
'load(simplify_sum)',
'load(abs_integrate)',
'load(diag)'
I know `bug_report();` and `build_info();` give the following info:
```
Maxima version: "5.41.0"
Maxima build date: "2018-10-27 02:45:10"
Host type: "x86_64-apple-darwin14.5.0"
Lisp implementation type: "ECL"
Lisp implementation version: "16.1.2"
```
but how does one get information in a Maxima session about settings
such as besselexpand, display2d, domain, keepfloat, and loaded
modules such as to_poly_solve, simplify_sum, abs_integrate, diag?
--
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.
Re: [sage-support] Fwd: Sage Crash Report
This is a known issue with the conda package as the sage package hasn't been updated yet for the new compiler runtimes on conda-forge. Try, conda create -n sage sage -c conda-forge/label/cf201901 Isuru On Tue, Feb 19, 2019 at 1:11 PM Douglas Webster < douglas.webster2...@gmail.com> wrote: > > > > Operating system: See Attached file. > > I installed Sage using conda giving the following commands during the > session as per the instructions on the sage website: > > conda update --all > anaconda-navigator > conda create -n sage sage > conda activate sage > sage > > > I then removed the conda environment and reinstalled it following the > above method. The complete re-instillation session record is detailed in > the file CrashReproduction.txt. > Also included is the SystemInfo as reported by the Linux Mint app. > There are two crash reports, Sage_crash_report_1st.txt being generated > from the original installation and Sage_crash_report.txt from the > reinstallation > > I have previously installed sage successfully as a binary package. This I > removed before trying it as a conda package. > > Hopefully this will be of some help. > > Best regards > Douglas > > -- > 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. > -- 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] Fwd: Sage Crash Report
Operating system: See Attached file. I installed Sage using conda giving the following commands during the session as per the instructions on the sage website: conda update --all anaconda-navigator conda create -n sage sage conda activate sage sage I then removed the conda environment and reinstalled it following the above method. The complete re-instillation session record is detailed in the file CrashReproduction.txt. Also included is the SystemInfo as reported by the Linux Mint app. There are two crash reports, Sage_crash_report_1st.txt being generated from the original installation and Sage_crash_report.txt from the reinstallation I have previously installed sage successfully as a binary package. This I removed before trying it as a conda package. Hopefully this will be of some help. Best regards Douglas -- 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. System:Host: douglas-linux Kernel: 4.15.0-45-generic x86_64 bits: 64 compiler: gcc v: 7.3.0 Desktop: Cinnamon 4.0.9 wm: muffin dm: LightDM Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic Machine: Type: Desktop System: Gigabyte product: N/A v: N/A serial: Chassis: type: 3 serial: Mobo: Gigabyte model: H61MA-D2V v: x.x serial: UEFI: American Megatrends v: F6 date: 04/17/2013 CPU: Topology: Quad Core model: Intel Core i5-3450 bits: 64 type: MCP arch: Ivy Bridge rev: 9 L2 cache: 6144 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24742 Speed: 1638 MHz min/max: 1600/3500 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 4: 1596 Graphics: Device-1: NVIDIA GF108 [GeForce GT 430] vendor: CardExpert driver: nvidia v: 390.77 bus ID: 01:00.0 chip ID: 10de:0de1 Display: x11 server: X.Org 1.19.6 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz OpenGL: renderer: GeForce GT 430/PCIe/SSE2 v: 4.6.0 NVIDIA 390.77 direct render: Yes Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 Device-2: NVIDIA GF108 High Definition Audio vendor: CardExpert driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0bea Sound Server: ALSA v: k4.15.0-45-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: 2.3LK-NAPI port: d000 bus ID: 04:00.0 chip ID: 10ec:8168 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: Device-2: Microsoft Xbox 360 Wireless Adapter type: USB driver: xpad bus ID: 3-1:2 chip ID: 045e:0719 IF-ID-1: docker0 state: down mac: Drives:Local Storage: total: 4.31 TiB used: 2.17 TiB (50.3%) ID-1: /dev/sda vendor: Seagate model: ST4000DX001-1CE168 size: 3.64 TiB speed: 3.0 Gb/s serial: ID-2: /dev/sdb vendor: OCZ model: VERTEX3 size: 111.79 GiB speed: 3.0 Gb/s serial: ID-3: /dev/sdc vendor: Intel model: SSDSC2CT120A3 size: 111.79 GiB speed: 3.0 Gb/s serial: ID-4: /dev/sdd type: USB vendor: Seagate model: ST9500325AS size: 465.76 GiB serial: Partition: ID-1: / size: 40.71 GiB used: 25.77 GiB (63.3%) fs: ext4 dev: /dev/sdb2 ID-2: /home size: 60.69 GiB used: 47.28 GiB (77.9%) fs: ext4 dev: /dev/sdb3 ID-3: swap-1 size: 8.00 GiB used: 426.9 MiB (5.2%) fs: swap dev: /dev/sdb4 Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 51 C Fan Speeds (RPM): N/A gpu: nvidia fan: 35% Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 1: deb [arch=amd64] https: //download.docker.com/linux/ubuntu bionic stable 2: deb https: //dl.winehq.org/wine-builds/ubuntu/ bionic main 3: deb http: //apt.postgresql.org/pub/repos/apt/ bionic-pgdg main Active apt repos in: /etc/apt/sources.list.d/couchbase.list 1: deb [ arch=amd64 ] http: //packages.couchbase.com/releases/couchbase-server/enterprise/deb/ xenial xenial/main 2: deb [ arch=amd64 ] http: //packages.couchbase.com/releases/couchbase-server/community/deb/ xenial xenial/main 3: deb http: //packages.couchbase.com/ubuntu xenial xenial/main 4: deb http: //packages.couchbase.com/ubuntu bi
[sage-support] Re: solve() behavior
On Tuesday, February 19, 2019 at 8:56:50 AM UTC-8, Michael Beeson wrote: > > When I try to reproduce Eric's post, I get an error message about an > unexpected keyword argument > (maybe my version of Sage is too old.) But look at this: > > sage: solve(*2**(x+sqrt(*1*-x^*2*))-*7*,x,explicit_solutions=True) > > [1/4*I*sqrt(41) + 7/4 == -1/2*sqrt(7/2*I*sqrt(41) + 2), 1/4*I*sqrt(41) + > 7/4 == 1/2*sqrt(7/2*I*sqrt(41) + 2)] > > > That doesn't look like an "explicit solution" to me. > > How can I force solve to return only actual solutions, i.e. x = > something not containing x? > > > Here is what I see: sage: solve(2*(x+sqrt(1-x^2))-7, x) [x == -sqrt(-x^2 + 1) + 7/2] sage: solve(2*(x+sqrt(1-x^2))-7, x, explicit_solutions=True) # it can't find any explicit solutions [] sage: solve(2*(x+sqrt(1-x^2))-7, x, to_poly_solve=True) [x == -1/4*I*sqrt(41) + 7/4, x == 1/4*I*sqrt(41) + 7/4] sage: solve(2*(x+sqrt(1-x^2))-7, x, algorithm='sympy') [x == -1/4*I*sqrt(41) + 7/4, x == 1/4*I*sqrt(41) + 7/4] -- 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: solve() behavior
When I try to reproduce Eric's post, I get an error message about an unexpected keyword argument (maybe my version of Sage is too old.) But look at this: sage: solve(*2**(x+sqrt(*1*-x^*2*))-*7*,x,explicit_solutions=True) [1/4*I*sqrt(41) + 7/4 == -1/2*sqrt(7/2*I*sqrt(41) + 2), 1/4*I*sqrt(41) + 7/4 == 1/2*sqrt(7/2*I*sqrt(41) + 2)] That doesn't look like an "explicit solution" to me. How can I force solve to return only actual solutions, i.e. x = something not containing 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.
Re: [sage-support] Sage installation fails (7.6 and 8.6) with "Error: spkg file '/patch-2.7.5.tar.gz' not found."
Please supply details about your system (and note that we do not really can offer support for Sagemath 7.* versions). Did you set any SAGE-specific environment variables before starting the build? (It looks as if you set SAGE_ROOT to some value, like "/", something that you should not do) On Tue, Feb 19, 2019 at 8:48 AM A Prakash wrote: > > Dear all, > > Please find the full mesg. text below. the log file is attached. > > Best, > Akshay. > > ... > XDG_SESSION_TYPE=x11 > XDG_VTNR=1 > XMODIFIERS=@im=none > *** > make[1]: Entering directory `/home/ap/Documents/sage/sage-7.6/build/make' > make base > make[2]: Entering directory `/home/ap/Documents/sage/sage-7.6/build/make' > sage-logger -p 'sage-spkg patch-2.7.5' > '/home/ap/Documents/sage/sage-7.6/logs/pkgs/patch-2.7.5.log' > [patch-2.7.5] Found local metadata for patch-2.7.5 > [patch-2.7.5] Using cached file > /home/ap/Documents/sage/sage-7.6/upstream/patch-2.7.5.tar.gz > [patch-2.7.5] Error: spkg file '/patch-2.7.5.tar.gz' not found. > [patch-2.7.5] This shouldn't happen, it is a bug in the sage-spkg script. > make[2]: *** > [/home/ap/Documents/sage/sageBuild/var/lib/sage/installed/patch-2.7.5] Error 1 > make[2]: Leaving directory `/home/ap/Documents/sage/sage-7.6/build/make' > make[1]: *** [all-toolchain] Error 2 > make[1]: Leaving directory `/home/ap/Documents/sage/sage-7.6/build/make' > > real0m0.277s > user0m0.171s > sys0m0.126s > *** > Error building Sage. > > The following package(s) may have failed to build (not necessarily > during this run of 'make all'): > > * package: patch-2.7.5 > log file: /home/ap/Documents/sage/sage-7.6/logs/pkgs/patch-2.7.5.log > build directory: > /home/ap/Documents/sage/sageBuild/var/tmp/sage/build/patch-2.7.5 > > The build directory may contain configuration files and other potentially > helpful information. WARNING: if you now run 'make' again, the build > directory will, by default, be deleted. Set the environment variable > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > > make: *** [all] Error 1 > > -- > 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. -- 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] Sage installation fails (7.6 and 8.6) with "Error: spkg file '/patch-2.7.5.tar.gz' not found."
Dear all, Please find the full mesg. text below. the log file is attached. Best, Akshay. ... XDG_SESSION_TYPE=x11 XDG_VTNR=1 XMODIFIERS=@im=none *** make[1]: Entering directory `/home/ap/Documents/sage/sage-7.6/build/make' make base make[2]: Entering directory `/home/ap/Documents/sage/sage-7.6/build/make' sage-logger -p 'sage-spkg patch-2.7.5' '/home/ap/Documents/sage/sage-7.6/logs/pkgs/patch-2.7.5.log' [patch-2.7.5] Found local metadata for patch-2.7.5 [patch-2.7.5] Using cached file /home/ap/Documents/sage/sage-7.6/upstream/patch-2.7.5.tar.gz [patch-2.7.5] Error: spkg file '/patch-2.7.5.tar.gz' not found. [patch-2.7.5] This shouldn't happen, it is a bug in the sage-spkg script. make[2]: *** [/home/ap/Documents/sage/sageBuild/var/lib/sage/installed/patch-2.7.5] Error 1 make[2]: Leaving directory `/home/ap/Documents/sage/sage-7.6/build/make' make[1]: *** [all-toolchain] Error 2 make[1]: Leaving directory `/home/ap/Documents/sage/sage-7.6/build/make' real0m0.277s user0m0.171s sys0m0.126s *** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all'): * package: patch-2.7.5 log file: /home/ap/Documents/sage/sage-7.6/logs/pkgs/patch-2.7.5.log build directory: /home/ap/Documents/sage/sageBuild/var/tmp/sage/build/patch-2.7.5 The build directory may contain configuration files and other potentially helpful information. WARNING: if you now run 'make' again, the build directory will, by default, be deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. make: *** [all] Error 1 -- 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. Found local metadata for patch-2.7.5 Using cached file /home/ap/Documents/sage/sage-7.6/upstream/patch-2.7.5.tar.gz Error: spkg file '/patch-2.7.5.tar.gz' not found. This shouldn't happen, it is a bug in the sage-spkg script.
