Re: [sage-support] Interface to 4ti2

[Jeroen Demeyer]

On 2019-03-20 05:21, 'benyamin alizade' via sage-support wrote:

When I run |sage -i 4ti2, it returns that -i is an unknown option for sage.


What happens *exactly*?

--
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] Interface to 4ti2

['benyamin alizade' via sage-support]

I use SageMath 8.6 on Ubuntu 18.04 and want to interface to 4ti2 which is 
already installed on mt system.
Unfortunately I can not run any of the commands of 
http://doc.sagemath.org/html/en/reference/interfaces/sage/interfaces/four_ti_2.html.

When I run sage -i 4ti2, it returns that -i is an unknown option for sage. 

Would you please help me to make this interface. 

Best regards,

-- 
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] Re: A case of immaculate conception...

[Isuru Fernando]

If the sage preparser did something like,

__tmp__ = SR.var("x, y"); __tmp_g__ = lambda x, y:
symbolic_expression(x+y**Integer(2)).function(x,y); f = __tmp_g__(*__tmp__)

for

f(x, y)  = x + y ** 2

you wouldn't have this problem and it should be easy enough to change in
the preparsesr.

Isuru

On Tue, Mar 19, 2019 at 12:38 PM john_perry_usm  wrote:

> Apologies for the pedantry, but unless the indeterminates so generated are
> free of all bugs, then strictly speaking this is not immaculate conception;
> it is spontaneous generation, or perhaps virginal conception. ;-)
>
> john perry
>
> On Tuesday, March 19, 2019 at 6:52:19 AM UTC-5, Emmanuel Charpentier wrote:
>>
>> Defining a symbolic function seems to declare its arguments. Case
>> illustrated in this sagecell example
>> 
>>  :
>>
>> reset()
>> Id1=set(show_identifiers())
>> foo(p,a,b)=p^(a-1)*(1-p)^(b-1)
>> Id2=set(show_identifiers())
>> Id2 - Id1
>>
>> which happily prints :
>>
>> {'Id1', 'a', 'b', 'foo', 'p'}
>>
>>
>> Is this expected ?
>>
>>
>>
>> --
> 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.

Re: [sage-support] Re: A case of immaculate conception...

[henri.gir...@gmail.com]

Hi John,

What is the difference between virginal conception and immaculate 
conception ?


I notice that sagemath can even cogitate in philosophy : Really a swiss 
knife ?


I don't believe in spontaneous generation ! lol

Henri

Le 19/03/2019 à 18:38, john_perry_usm a écrit :
Apologies for the pedantry, but unless the indeterminates so generated 
are free of all bugs, then strictly speaking this is not immaculate 
conception; it is spontaneous generation, or perhaps virginal 
conception. ;-)


john perry

On Tuesday, March 19, 2019 at 6:52:19 AM UTC-5, Emmanuel Charpentier 
wrote:


Defining a symbolic function seems to declare its arguments. Case
illustrated in this sagecell example


 :


reset()
Id1=set(show_identifiers())
foo(p,a,b)=p^(a-1)*(1-p)^(b-1)
Id2=set(show_identifiers())
Id2 - Id1

which happily prints :

{'Id1', 'a', 'b', 'foo', 'p'}

Is this expected ?

--
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.

Re: [sage-support] yasm can not be installed/compiled

['Florian Hanisch' via sage-support]

Hi, 

just want to confirm that after going to the local disk and having 
perl-ExtUtils-MakeMaker as well as yasm added to the system, sage could be 
compiled without any further difficulties. Thanks again for your advice !

On Monday, March 18, 2019 at 10:19:15 PM UTC, Florian Hanisch wrote:
>
> Hi,
>
>
> many thanks for that hint, this may indeed be the issue. I will request 
> access to the local disk and try it again. 
>
>
> Best,
>
> Florian
>
> Btw: @John: I was running make again but there were no files in the 
> future. 
>
> On Monday, March 18, 2019 at 10:12:09 PM UTC, Dima Pasechnik wrote:
>>
>> On Mon, Mar 18, 2019 at 10:05 PM John H Palmieri  
>> wrote: 
>> > 
>> > What are the modification dates and times for the files in the 
>> directory 
>> > 
>> >   
>>  /apps/srv01/pmt/pmtfh/sage/sage-8.6/local/var/tmp/sage/build/yasm-1.3.0.p0 
>> > 
>> > Maybe you should run 'make' again, which will regenerate this 
>> directory, and then check the times on the files. Are any of them in the 
>> future? 
>>
>> there could also be funny things happening if /apps/srv01/pmt/pmtfh/ 
>> resides on 
>> an NFS or other network filesystem rather than on a local disk. 
>> Please do all the builds on a local disk... 
>>
>> > 
>> > 
>> > 
>> > On Monday, March 18, 2019 at 2:38:43 PM UTC-7, Dima Pasechnik wrote: 
>> >> 
>> >> You may also ask your sysadmins to install yasm (it's an assembler for 
>> x86_64) 
>> >> (cf e.g. 
>> https://centos.pkgs.org/7/epel-x86_64/yasm-1.2.0-4.el7.x86_64.rpm.html) 
>> >> 
>> >> On Mon, Mar 18, 2019 at 9:18 PM Dima Pasechnik  
>> wrote: 
>> >> > 
>> >> > On Mon, Mar 18, 2019 at 9:10 PM 'Florian Hanisch' via sage-support 
>> >> >  wrote: 
>> >> > > 
>> >> > > Thanks, my system clock matches the local time quite accurately 
>> (including the year), I just checked it again. I can / could not make any 
>> sense of this comment in the log that you quoted. 
>> >> > 
>> >> > This is a quite standard test in configure files generated by GNU 
>> autotools. 
>> >> > 
>> >> > I don't find much relevant on this on the net, except perhaps 
>> >> > 
>> https://serverfault.com/questions/136186/what-steps-can-you-take-to-ensure-sane-build-environments-when-compiling-softwar
>>  
>> >> > 
>> >> > Do you by any chance have "ls" aliased to something ? 
>> >> > 
>> >> > 
>> >> > > 
>> >> > > 
>> >> > > On Monday, March 18, 2019 at 8:56:31 PM UTC, Dima Pasechnik wrote: 
>> >> > >> 
>> >> > >> In the log you see 
>> >> > >> 
>> >> > >> checking whether build environment is sane... configure: error: 
>> newly 
>> >> > >> created file is older than distributed files! 
>> >> > >> Check your system clock 
>> >> > >> 
>> >> > >> So it seems that your system clock is off by a considerable 
>> interval 
>> >> > >> (probably, years!) 
>> >> > >> This might be a problem... 
>> >> > >> 
>> >> > >> Does the output of "date" in the terminal match the wall clock in 
>> any way? 
>> >> > >> 
>> >> > >> 
>> >> > >> On Mon, Mar 18, 2019 at 8:37 PM 'Florian Hanisch' via 
>> sage-support 
>> >> > >>  wrote: 
>> >> > >> > 
>> >> > >> > Dear all, 
>> >> > >> > 
>> >> > >> > this might be a question for the developers groups. But before 
>> joining the dev-group just to be able to post one question, I decided to 
>> ask here first. 
>> >> > >> > 
>> >> > >> > I am trying to compile sage 8.6 on Centos 7 (intel core i5, 8GB 
>> Ram) but the process stops with the following message 
>> >> > >> > 
>> >> > >> > > Error building Sage. 
>> >> > >> > > 
>> >> > >> > > The following package(s) may have failed to build (not 
>> necessarily 
>> >> > >> > > during this run of 'make all-start'): 
>> >> > >> > > 
>> >> > >> > > * package: yasm-1.3.0.p0 
>> >> > >> > >   log file: 
>> /apps/srv01/pmt/pmtfh/sage/sage-8.6/logs/pkgs/yasm-1.3.0.p0.log 
>> >> > >> > >   build directory: 
>> /apps/srv01/pmt/pmtfh/sage/sage-8.6/local/var/tmp/sage/build/yasm-1.3.0.p0 
>> >> > >> > 
>> >> > >> > I attached the log-file mentioned above to my post. I know that 
>> the package perl-ExtUtils-MakeMaker is not installed on my computer 
>> >> > >> > (unfortunately, I am not root on the computer I am using). Is 
>> this a possible reason for the problem ? Or do I have to look for a 
>> "deeper" problem ? 
>> >> > >> > 
>> >> > >> > Thanks, 
>> >> > >> > 
>> >> > >> > Florian 
>> >> > >> > 
>> >> > >> > P.S. If this question should be posted at sage-devel, plaese 
>> let me know, I will subscribe and post then. 
>> >> > >> > 
>> >> > >> > -- 
>> >> > >> > 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...@googlegroups.com. 
>> >> > >> > To post to this group, send email to sage-s...@googlegroups.com. 
>>
>> >> > >> > Visit this group at 
>> https://groups.google.com/group/sage-support. 
>> >> > >> > For more options, visit https://groups.google.com/d/optout. 
>> >> > > 
>> >> > > -- 
>> >> > > Yo

[sage-support] Re: A case of immaculate conception...

[john_perry_usm]

Apologies for the pedantry, but unless the indeterminates so generated are 
free of all bugs, then strictly speaking this is not immaculate conception; 
it is spontaneous generation, or perhaps virginal conception. ;-)

john perry

On Tuesday, March 19, 2019 at 6:52:19 AM UTC-5, Emmanuel Charpentier wrote:
>
> Defining a symbolic function seems to declare its arguments. Case 
> illustrated in this sagecell example 
> 
>  :
>
> reset()
> Id1=set(show_identifiers())
> foo(p,a,b)=p^(a-1)*(1-p)^(b-1)
> Id2=set(show_identifiers())
> Id2 - Id1
>
> which happily prints :
>
> {'Id1', 'a', 'b', 'foo', 'p'}
>
>
> Is this expected ?
>
>
>
>

-- 
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: A case of immaculate conception...

[Nils Bruin]

On Tuesday, March 19, 2019 at 4:52:19 AM UTC-7, Emmanuel Charpentier wrote:
>
> Defining a symbolic function seems to declare its arguments. Is this 
> expected ?
>
It's certainly explicit programmed:

sage: preparse("f(x)=1")
'__tmp__=var("x"); f = symbolic_expression(Integer(1)).function(x)

On the plus side, we have very concise syntax for defining symbolic 
variables without having to write quotes:

sage: _(x,y,z)=1
sage: x^2+y^2+z^2
x^2 + y^2 + z^2

which is shorter than var("x,y,z") AND it doesn't cause a tuple to be 
printed.

-- 
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: A case of immaculate conception...

[Simon King]

Hi Emmanuel,

On 2019-03-19, Jeroen Demeyer  wrote:
> On 2019-03-19 12:52, Emmanuel Charpentier wrote:
>> Defining a symbolic function seems to declare its arguments.
>
> I tend to think that everything on the left of the '=' sign in an 
> assignment is stuff that is assigned to. So
>
>(a, b, c) = range(3)
>
> assigns to a, b and c.
>
>R. = ZZ[]
>
> assigns to R and x.
>
>func(x) = x
>
> assigns to func and x.
>
> So in this sense, it's expected.

Some addition: While the first example
   (a,b,c) = range(3)
is standard Python behaviour, the other examples work because Sage uses
a preparser to make it possible to use nicer syntax in maths:
   f(x) = x^2
is a lot more concise and easier to understand for non-programmers than
   __tmp__=var("x"); f = symbolic_expression(x**Integer(2)).function(x)
(which is what the preparser makes of it).

Best regards,
Simon

-- 
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] A case of immaculate conception...

[Jeroen Demeyer]

On 2019-03-19 12:52, Emmanuel Charpentier wrote:

Defining a symbolic function seems to declare its arguments.


I tend to think that everything on the left of the '=' sign in an 
assignment is stuff that is assigned to. So


  (a, b, c) = range(3)

assigns to a, b and c.

  R. = ZZ[]

assigns to R and x.

  func(x) = x

assigns to func and x.

So in this sense, it's expected.

--
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] A case of immaculate conception...

[Emmanuel Charpentier]

Defining a symbolic function seems to declare its arguments. Case 
illustrated in this sagecell example 

 :

reset()
Id1=set(show_identifiers())
foo(p,a,b)=p^(a-1)*(1-p)^(b-1)
Id2=set(show_identifiers())
Id2 - Id1

which happily prints :

{'Id1', 'a', 'b', 'foo', 'p'}


Is this expected ?



-- 
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.