[sage-devel] Python and R (and maybe Julia) in data science
This may be of interest a few folks - nothing really new but just pointing it out. http://www.packtpub.com/books/content/war-data-science-python-versus-r -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] On scientific computing, Python and Julia
On Wed, Aug 6, 2014 at 7:00 PM, rjf wrote:
>> >> > coercing the integer 10 into something like 10 mod 13 or
>> >> > perhaps
>> >> > -3
>> >> > mod 13 is
>> >> > a choice, probably the wrong one.
>> >>
>> >> It is a completely canonical choice, and the only possible sensible one
>> >> to
>> >> make in this situation.
>> >
>> > Which one, -3 or 10?
>> > They can't both be canonical.
>>
>> Yes, they can "both" be canonical: they are equal (as elements of
>> Z/13Z). There is the choice of internal representation, and what
>> string to use when displaying them to the user, but that doesn't
>> affect its canonicity as a mathematical object.
>>
> I don't understand this.
> I use the word canonical to mean unique distinguished exemplar.
> So there can't be two. If there are two distinguishable items, then one or
> the other or neither might be canonical. Not both.
The are two representations of the same canonical object.
>> >> > presumably one could promote your variable a to have a value in Z and
>> >> > do
>> >> > the addition again. Whether comfortably or not.
>> >>
>> >> sage: a = Mod(5,13); a
>> >> 5
>> >> sage: a + 10
>> >> 2
>> >> sage: b = a.lift(); parent(b)
>> >> Integer Ring
>> >> sage: b + 10
>> >> 15
>> >
>> >
>> > Thanks. Can the lifting be done to another computational structure, say
>> > modulo 13^(2^n)?
>>
>> Sure.
>>
>> sage: b = Integers(13^1024)(a); b
>> 5
>> sage: b^(4*13^1023)
>> 1
>>
> And what structure is that? Does Sage know about Z_{nonprime} ?
Of course, as illustrated.
sage: Integers(13^1024)
Ring of integers modulo 4764...1
>> >> > What is the precision of the parent ring of a float?? Rings with
>> >> > precision???
>> >>
>> >> sage: R = parent(1.399390283048203480923490234092043820348); R
>> >> Real Field with 133 bits of precision
>> >> sage: R.precision()
>> >> 133
>> >>
>> > I'm confused here. Are you now saying R is a Field? Is a Real Field a
>> > kind
>> > of
>> > Field? Is there a multiplicative inverse in R for the object 3.0 ? Or
>> > is a
>> > Real Field
>> > like a "Dutch Oven" which is actually not an oven, but a pot?
>>
>> R is a (very well studied) approximation to a field.
>
>
> I'm still confused. Is the term "Real Field" in Sage the (or some) real
> field?
>
> If it is an approximation to a field, but not a field, why are you calling
> it a field?
Because it's shorter to type and easier to find/discover than
ApproximateRealField or something like that.
> If that doesn't get you in trouble, why doesn't it? Does Real Field inherit
> from
> Field? Does every non-zero element have an inverse?
Of course it suffers from the same issues that (standard) floating
point numbers do in any language, user be aware (and we at least
document that).
> Does Sage have other um, approximations, in its nomenclature?
Sure. RealField(123)[x]. Power series rings. P-adics.
>> >> >> sage: 1.3 + 2/3
>> >> >> 1.97
>> >> >
>> >> >
>> >> > arguably, this is wrong.
>> >> >
>> >> > 1.3, if we presume this is a machine double-float in IEEE form, is
>> >> > about
>> >> > 1.300044408920985006261616945266723633
>> >> > or EXACTLY
>> >> > 5854679515581645 / 4503599627370496
>> >> >
>> >> > note that the denominator is 2^52.
>> >> >
>> >> > adding 2/3 to that gives
>> >> >
>> >> > 26571237801485927 / 13510798882111488
>> >> >
>> >> > EXACTLY.
>> >> >
>> >> >
>> >> > which can be written
>> >> > 1.9667110755876516729282836119333903...
>> >> >
>> >> > So you can either do "mathematical addition" by default or do
>> >> > "addition yada yada".
>> >> >
>> >>
>> >> In Sage both operands are first converted to a common structure in
>> >> which
>> >> the operation can be performed, and then the operation is performed.
>> >
>> >
>> > Well, there are a large number of common structures.
>> > One that gets the exact answer is to convert to arbitrary-precision
>> > rationals.
>> > One that does not always get the exact answer is some kind of
>> > floating-point
>> > representation.
>>
>> It is more conservative to convert operands to the domain with less
>> precision.
>
> Why do you say that? You can always exactly convert a float number in
> radix b to
> an equal number of higher precision in radix b by appending zeros.
> So it is more conserving (of values) to do so, rather than clipping off
> bits from the other.
Clipping bits (or digits) is exactly how one is taught to deal with
significant figures in grade school, and follows the principle of
least surprise (though floating point numbers like to play surprises
on you no matter what). It's also what floating point arithmetic does
when the exponent is different.
>> We consider the rationals to have infinite precision, our
>> real "fields" a specified have finite precision. This lower precision
>> is represented in the output, similar to how significant figures are
>> used in any other scientific endeavor.
>
> Thanks for distinguishing between "field" and field. You don't seem
> to u
Re: [sage-devel] On scientific computing, Python and Julia
On Tuesday, August 5, 2014 7:59:00 PM UTC-7, Robert Bradshaw wrote:
>
> On Tue, Aug 5, 2014 at 6:36 PM, rjf >
> wrote:
> >
> >
> > On Sunday, August 3, 2014 10:11:57 PM UTC-7, William wrote:
> >>
> >>
> >>
> >> On Sat, Aug 2, 2014 at 11:16 PM, rjf wrote:
> >> > On Wednesday, July 30, 2014 10:23:03 PM UTC-7, William wrote:
> >> >> [1] http://maxima.sourceforge.net/docs/manual/en/maxima_29.html
> >> >>
> >> >> > Perhaps Axiom and Fricas have such odd Taylor series objects;
> they
> >> >> > don't
> >> >> > seem to be
> >> >> > something that comes up much, and I would expect they have some
> >> >> > uncomfortable
> >> >> > properties.
> >> >>
> >> >> They do come up frequently in algebraic geometry, number theory,
> >> >> representation theory, combinatorics, coding theory and many other
> >> >> areas of pure and applied mathematics.
> >> >
> >> >
> >> >You can say
> >> > whatever you want about some made-up computational problems
> >> > in "pure mathematics" but I think you are just bluffing regarding
> >> > applications.
> >>
> >> Let me get this straight -- you honestly thinking I'm bluffing
> regarding
> >> applications of:
> >>
> >> "power series in one variable over a finite field"
> >
> > Yes.
> >
> > I read your statement above to say, among other things, that
> >
> > {such odd power series objects} come up frequently in ... many area of
> ...
> > applied mathematics.
> >
> >
> >
> >>
> >>
> >>
> >> Are you seriously claiming that "power series over a finite field" have
> no
> >> applications?
> >
> >
> > I can imagine you could invent an "application", so I would not say
> these
> > objects
> > have "no applications".I can even invent one application for you.
> The
> > application is
> > "show a structure that can be created by a computer program that
> consists of
> > a power
> > series etc etc." This sort of smacks of the self referentiality that
> comes
> > from answering
> > the command:
> >
> > Use X in a sentence.
> >
> > by the response
> > "Use X in a sentence.
> >>
> >>
> >>
> >>
> >> >> > Note that even adding 5 mod 13 and the integer 10 is
> potentially
> >> >> > uncomfortable,
> >> >>
> >> >> sage: a = Mod(5,13); a
> >> >> 5
> >> >> sage: parent(a)
> >> >> Ring of integers modulo 13
> >> >> sage: type(a)
> >> >>
> >> >> sage: a + 10
> >> >> 2
> >> >> sage: parent(a+10)
> >> >> Ring of integers modulo 13
> >> >>
> >> >> That was really comfortable.
> >> >
> >> >
> >> > Unfortunately, it (a) looks uncomfortable, and (b) got the answer
> >> > wrong.
> >> >
> >> > The sum of 5 mod13 and 10 is 15, not 2.
> >> >
> >> > The calculation (( 5 mod 13)+10) mod 13 is 2.
> >> >
> >> > Note that the use of mod in the line above, twice, means different
> >> > things.
> >> > One is a tag on the number 5 and the second is an operation akin to
> >> > remainder.
> >>
> >> The answer from Sage is correct, and your remarks to the contrary are
> just
> >> typical of rather shallow understanding of mathematics.
> >
> >
> > Are you familiar with TeX's \bmod ?
> >
> > It is possible to define anything that comes from Sage as correct.
> > Mathematica does that kind of thing often, declaring its reported bugs
> to be
> > features. Sometimes
> > I agree, sometimes not.
> >
> >>
> >>
> >> >> It's basically the same in Magma and
> >> >> GAP. In PARI it's equally comfortable.
> >> >>
> >> >> ? Mod(5,13)+10
> >> >> %2 = Mod(2, 13)
> >> >>
> >> >>
> >> >> > and the rather common operation of Hensel lifting requires doing
> >> >> > arithmetic
> >> >> > in a combination
> >> >> > of fields (or rings) of different related sizes.
> >> >
> >> >
> >> > If you knew about Hensel lifting, I would think that you would
> comment
> >> > here,
> >> > and that
> >> > you also would know why 15 rather than 2 might be the useful answer.
> >>
> >> The answer output by Pari is neither 15 nor 2. It is "Mod(2, 13)".
> >
> >
> > Well, if you simply insist that arithmetic requires the conversion of 10
> to
> > a number in Z_13,
> > then that answer is OK.
> >
> >>
> >>
> >>
> >> > coercing the integer 10 into something like 10 mod 13 or
> perhaps
> >> > -3
> >> > mod 13 is
> >> > a choice, probably the wrong one.
> >>
> >> It is a completely canonical choice, and the only possible sensible one
> to
> >> make in this situation.
> >
> > Which one, -3 or 10?
> > They can't both be canonical.
>
> Yes, they can "both" be canonical: they are equal (as elements of
> Z/13Z). There is the choice of internal representation, and what
> string to use when displaying them to the user, but that doesn't
> affect its canonicity as a mathematical object.
>
> I don't understand this.
I use the word canonical to mean unique distinguished exemplar.
So there can't be two. If there are two distinguishable items, then one or
the other or neither might be
[sage-devel] Re: Authenticity warning message when SSH-ing into g...@trac.sagemath.org
You should be getting: The authenticity of host 'trac.sagemath.org (128.208.178.249)' can't be established. ECDSA key fingerprint is 21:ba:10:2a:59:cd:7d:36:f7:4c:52:bf:fc:5e:0e:07. Are you sure you want to continue connecting (yes/no)? Type "yes" when you see it the first time. The trac server's public key is then saved and used in future connections to avoid man-in-the-middle attacks. The "content of the public key file" is the whole content. The "foo@bar.local" is just an arbitrary comment for you to remember what that key is, anything else must match exactly. On Tuesday, August 5, 2014 6:38:53 PM UTC+1, Paul Graham wrote: > > When i type in > ssh g...@trac.sagemath.org info > > It says: > > The authenticity of host 'trac.sagemath.org (some IP address)' can't be > established. > ECDSA key fingerprint is (some hex string). > Are you sure you want to continue connecting (yes/no)? > > I am new to this process and wasn't sure whether or not its safe to write > down the IP address and hext string in the above message. But i dont know > what to do with thiat message, as id like to get up and running. > > And relating to this, step 5. in the Manually Linking your Public Key to > your Trac Account section of the dev guide: > > 5. Paste the content of your public key file (e.g. ~/.ssh/id_rsa.pub) > > I wasn't sure whether to copy and paste just the random string by itself, > or the whole thing including the "ssh-rsa" and "foo@bar.local" parts, as > like i said before, this is new to me :) > > Example key (not mine) taken from: > http://git-scm.com/book/en/Git-on-the-Server-Generating-Your-SSH-Public-Key > > ssh-rsa B3NzaC1yc2EBIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/ > BWDSUGPl+nafzlHDTYW7hdI4yZ5ew18JH4JW9jbhUFrviQzM7xlELEVf4h9lFX5QVkbPppSwg0cda3 > > Pbv7kOdJ/MTyBlWXFCR+HAo3FXRitBqxiX1nKhXpHAZsMciLq8V6RjsNAQwdsdMFvSlVK/7XA > t3FaoJoAsncM1Q9x5+3V0Ww68/eIFmb1zuUFljQJKprrX88XypNDvjYNby6vw/Pb0rwert/En > mZ+AW4OZPnTPI89ZPmVMLuayrD2cE86Z/il8b+gw3r3+1nKatmIkjn2so1d01QraTlMqVSsbx > NrRFi9wrf+M7Q== foo@bar.local > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Reocvering from system crash during compile?
Don't compile as root. Chown everything to your normal user, and then do a make distclean && make On Thursday, August 7, 2014 12:59:12 AM UTC+1, Alasdair wrote: > > I think the trouble may be one which has been reported before: the > permissions in $SAGE_ROOT/local/lib/python/distutils being not group > writable: I'm compiling as root. I went back to $SAGE_ROOT and entered > "chown -R root:root .", and then tried make again - same errors. The > compile gets stuck on pynac. This is the first time (in many many sage > compilations) where I've had an error compiling as root, which leads me to > wonder if either there's some sort of error in the source code, or if > something has been changed so that compiling as root (which I've always > done previously) can't be done. > > Advice is welcome! > > Thanks, > Alasdair > > On Wednesday, 6 August 2014 15:47:39 UTC+10, P Purkayastha wrote: >> >> Try to rebuild the whole thing again, just so as to ensure that >> everything is properly built. >> >> make distclean >> make >> >> On Wednesday, August 6, 2014 12:46:47 PM UTC+8, Alasdair wrote: >>> >>> I'm running Ubuntu 14.04 as a guest VM inside VirtualBox 4.3.12, with >>> Windows 7.1 Enterprise as the host OS. (This gives me access to my >>> university's network, networked printers and drives etc, which are >>> unreachable from linux). And in the middle of compling Sage 6.2 from >>> source, while I was fiddling about with a webcam, the system crashed with >>> the delightful, friendly BSOD. Back in linux, the error messages I >>> received were >>> >>> checking for the distutils Python package... no configure: error: cannot import Python module "distutils". Please check your Python installation. The error was: sys:1: RuntimeWarning: not adding directory '' to sys.path since it's writable by an untrusted group. Untrusted users could put files in this directory which might then be imported by your Python code. As a general precaution from similar exploits, you should not execute Python code from this directory make[3]: Entering directory `/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2/src' make[3]: *** No targets specified and no makefile found. Stop. make[3]: Leaving directory `/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2/src' Error building pynac. real0m1.585s user0m0.254s sys 0m0.159s Error installing package pynac-0.3.2 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /opt/sage-6.2/logs/pkgs/pynac-0.3.2.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2 and type 'make' or whatever is appropriate. Instead, the following commands setup all environment variables correctly and load a subshell for you to debug the error: (cd '/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2' && '/opt/sage-6.2/sage' --sh) When you are done debugging, you can type "exit" to leave the subshell. make[2]: *** [/opt/sage-6.2/local/var/lib/sage/installed/pynac-0.3.2] Error 1 make[2]: Leaving directory `/opt/sage-6.2/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/opt/sage-6.2/build' real0m2.256s >>> user0m0.457s sys 0m0.224s *** Error building Sage. The following package(s) may have failed to build: package: pynac-0.3.2 log file: /opt/sage-6.2/logs/pkgs/pynac-0.3.2.log build directory: /opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2 >>> >>> >>> I'm not sure if the errors were caused by the system crash, or are the >>> fault of the system itself. But now that I've rebooted - how do I >>> recover? Should I just throw everything away, and start from scratch? >>> >>> Thanks, >>> Alasdair >>> >>> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Reocvering from system crash during compile?
I think the trouble may be one which has been reported before: the permissions in $SAGE_ROOT/local/lib/python/distutils being not group writable: I'm compiling as root. I went back to $SAGE_ROOT and entered "chown -R root:root .", and then tried make again - same errors. The compile gets stuck on pynac. This is the first time (in many many sage compilations) where I've had an error compiling as root, which leads me to wonder if either there's some sort of error in the source code, or if something has been changed so that compiling as root (which I've always done previously) can't be done. Advice is welcome! Thanks, Alasdair On Wednesday, 6 August 2014 15:47:39 UTC+10, P Purkayastha wrote: > > Try to rebuild the whole thing again, just so as to ensure that everything > is properly built. > > make distclean > make > > On Wednesday, August 6, 2014 12:46:47 PM UTC+8, Alasdair wrote: >> >> I'm running Ubuntu 14.04 as a guest VM inside VirtualBox 4.3.12, with >> Windows 7.1 Enterprise as the host OS. (This gives me access to my >> university's network, networked printers and drives etc, which are >> unreachable from linux). And in the middle of compling Sage 6.2 from >> source, while I was fiddling about with a webcam, the system crashed with >> the delightful, friendly BSOD. Back in linux, the error messages I >> received were >> >> checking for the distutils Python package... no >>> configure: error: cannot import Python module "distutils". >>> Please check your Python installation. The error was: >>> sys:1: RuntimeWarning: not adding directory '' to sys.path since it's >>> writable by an untrusted group. >>> Untrusted users could put files in this directory which might then be >>> imported by your Python code. As a general precaution from similar >>> exploits, you should not execute Python code from this directory >>> make[3]: Entering directory >>> `/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2/src' >>> make[3]: *** No targets specified and no makefile found. Stop. >>> make[3]: Leaving directory >>> `/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2/src' >>> Error building pynac. >>> >>> real0m1.585s >>> user0m0.254s >>> sys 0m0.159s >>> >>> Error installing package pynac-0.3.2 >>> >>> Please email sage-devel (http://groups.google.com/group/sage-devel) >>> explaining the problem and including the relevant part of the log file >>> /opt/sage-6.2/logs/pkgs/pynac-0.3.2.log >>> Describe your computer, operating system, etc. >>> If you want to try to fix the problem yourself, *don't* just cd to >>> /opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2 and type 'make' or >>> whatever is appropriate. >>> Instead, the following commands setup all environment variables >>> correctly and load a subshell for you to debug the error: >>> (cd '/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2' && >>> '/opt/sage-6.2/sage' --sh) >>> When you are done debugging, you can type "exit" to leave the subshell. >>> >>> make[2]: *** [/opt/sage-6.2/local/var/lib/sage/installed/pynac-0.3.2] >>> Error 1 >>> make[2]: Leaving directory `/opt/sage-6.2/build' >>> make[1]: *** [all] Error 2 >>> make[1]: Leaving directory `/opt/sage-6.2/build' >>> >>> real0m2.256s >>> >> user0m0.457s >>> sys 0m0.224s >>> *** >>> Error building Sage. >>> >>> The following package(s) may have failed to build: >>> >>> package: pynac-0.3.2 >>> log file: /opt/sage-6.2/logs/pkgs/pynac-0.3.2.log >>> build directory: /opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2 >>> >> >> >> I'm not sure if the errors were caused by the system crash, or are the >> fault of the system itself. But now that I've rebooted - how do I >> recover? Should I just throw everything away, and start from scratch? >> >> Thanks, >> Alasdair >> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Deleting SSH key from trac account?
Are you able to delete an SSH key that is associated with your trac account? Ive tried erasing it and pressing 'save changes' but it stays there? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Authenticity warning message when SSH-ing into g...@trac.sagemath.org
Im new to Sage development and am going through the various items from the dev guide, right now im trying to test that im being authenticated correctly as suggested by example in http://www.sagemath.org/doc/developer/trac.html#manually-linking-your-public-key-to-your-trac-account after adding my ssh key to my trac account (i have one). When i type in ssh g...@trac.sagemath.org info It says: The authenticity of host 'trac.sagemath.org (some IP address)' can't be established. ECDSA key fingerprint is (some hex string). Are you sure you want to continue connecting (yes/no)? I am new to this process and wasn't sure whether or not its safe to write down the IP address and hext string in the above message. But i dont know what to do with thiat message, as id like to get up and running. And relating to this, step 5. in the Manually Linking your Public Key to your Trac Account section of the dev guide: 5. Paste the content of your public key file (e.g. ~/.ssh/id_rsa.pub) I wasn't sure whether to copy and paste just the random string by itself, or the whole thing including the "ssh-rsa" and "foo@bar.local" parts, as like i said before, this is new to me :) Example key (not mine) taken from: http://git-scm.com/book/en/Git-on-the-Server-Generating-Your-SSH-Public-Key ssh-rsa B3NzaC1yc2EBIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/BWDSUGPl +nafzlHDTYW7hdI4yZ5ew18JH4JW9jbhUFrviQzM7xlELEVf4h9lFX5QVkbPppSwg0cda3 Pbv7kOdJ/MTyBlWXFCR+HAo3FXRitBqxiX1nKhXpHAZsMciLq8V6RjsNAQwdsdMFvSlVK/7XA t3FaoJoAsncM1Q9x5+3V0Ww68/eIFmb1zuUFljQJKprrX88XypNDvjYNby6vw/Pb0rwert/En mZ +AW4OZPnTPI89ZPmVMLuayrD2cE86Z/il8b+gw3r3+1nKatmIkjn2so1d01QraTlMqVSsbx NrRFi9wrf+M7Q== foo@bar.local -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] List of standard packages
On Wednesday, August 6, 2014 12:49:55 PM UTC-7, Jeroen Demeyer wrote: > > sage --standard is still using the old pre-git package system, it > doesn't list any new git packages. So yes, this is a major bug. > > I suppose you could get the list of standard packages by parsing the appropriate part of SAGE_ROOT/build/install, or (if you want version numbers) SAGE_ROOT/build/Makefile after you've at least started the "make" process from SAGE_ROOT. -- John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] List of standard packages
sage --standard is still using the old pre-git package system, it doesn't list any new git packages. So yes, this is a major bug. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] List of standard packages
Hello, How standard packages are determined after switching to git? I want to be able to pre-download all standard packages (*not* including optional databases). My attempt to rely on "sage -standard" was mostly successful, but apparently some packages are not in the list, at least pkgconf is not, and config... (needed if automake is not installed) is not either. Does the "sage -standard" list need manual updating or it is generated automatically somehow? Thank you! Andrey -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Remove webassets from sagenb?
On Aug 5, 2014, at 9:46 PM, François Bissey wrote: > On Tue, 05 Aug 2014 07:06:36 kcrisman wrote: >> That took more time to track down than I would have liked. So I guess we >> can indeed scrap it, though if we can keep samuela's branch compatibility >> (this is called the "newui" branch on github) that would be good for >> honoring that contribution, as someone may have time to do this in the long >> run (sagenb may not be cutting-edge but it is still the best choice for a >> lot of local work; I assume it is lighter-weight than whatever local SMC >> comes up but assumptions are dangerous). Anyway, hope this detective work >> was useful. > Actually if you are using KDE there is an interesting alternative to sagenb: > "cantor" http://www.kde.org/applications/education/cantor > Pity it doesn't work on OS X. Has anyone tried? You can install KDE libraries with homebrew (or fink, or mac ports). It's not inconceivable that cantor could work. -Ivan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: creating a new monoid together with a new group (categories)
Hi Travis, Am 2014-08-01 um 20:14 schrieb Travis Scrimshaw: > The creation of the monoid (Parent and Element) is described very well > in [1] (and got to understand the category framework a bit more). From > an object-orientated point of view, I now would inherit a class for the > invertible elements from both, the created monoid element and from > GroupElement. This class will have methods only invertible elements > have. > My question now is, how the interplay between all theses elements (and > also parents) is. In particular, when I create an invertible element > through my monoid parent, does this already give a group element or > do I > explicitly have to construct the element via the group parent? How is > this handled usually? Is there some (well written ;)) code (some > monoid/groups) in Sage, where I can see a similar thing going on? > > > How I did it for free monoids/groups whose generators are indexed by > arbitrary sets (indexed_free_*.py) and how I would suggest would be to > have a class for the monoid element, and then have the group element > inherit from the monoid element (plus whatever else seems appropriate) > and implement the inverse there. Ok, this was/is the plan. > In implementing the multiplication, you > should be ending with something like > > | > returnself.__class__(self.parent(),data) > | Yes. > Now I would also implement _coerce_map_from_(self, P) for the group (the > parent) which returns True when P is an instance of the monoid (the > parent) > (which I did not implement for the free group...probably should > do that). Then I would have the group's _element_constructor_ handle > elements from the monoid and spits out an element of the group. Then the > coercion framework will take care of the rest. This sounds like a coercion from the monoid to the group, but IMHO should be the other way round. Each group element is also an monoid element (therefore the coercion always works). > I don't know of a specific place where this is currently for > monoids/groups. There's code scattered throughout sage for the > _coerce_map_from_ (ex. shuffle_algebra.py, symmetric_group_algebra.py in > the latest beta). Ok. I hope that helps, and feel free to cc me on the > ticket (tscrim) or ask if you have any other questions. I will (but will take some time, since there are also other things to do...) BTW: is there a reason why sage.groups.group.Group is derived from Parent and not from Monoid (Monoid_class)? > There is also a second question I have (but much more non-specific): My > elements can be seen also as functions acting on some set and the > monoid > operation corresponds to function composition. Is there a way to bring > this aspect in? (As this question is very vague, I'm happy with every > input you can provide.) > > You can implement a __call__() method to have the elements act as > functions (although you'll have the implement the function composition > and possible coercions manually). Ok. > Alternatively it might be possible for > the element to inherit from Map or Morphism, and in that case, the > coercion would be done automatically and you'll want to implement > _call_() (with only one underscore). I'd suggest trying the latter first. Yes, definitvely. :) Many thanks for your input. Daniel -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: review requests
Hi Jakob, thanks! Here is some documentation on how to review a patch in Sage: http://sagemath.org/doc/developer/trac.html#section-review-patches but it essentially boils down to reading the code and checking if it is sound + checking that it indeed solves the problem + was a testcase added? Note that the green circle in the top right of the ticket at http://trac.sagemath.org/ticket/15672 tells you that normal doctests pass and that the patch applies. This does not test optional doctests, though, i.e. those involving Magma. Let me know if you need any help. Cheers, Martin On Wednesday 06 Aug 2014 01:12:55 Jakob Kroeker wrote: > Hi Martin, > > > I would review (the simple) 15672. > Since it is my first review in Sagemath, I have to find out how to review > first > and how to check, that your patch is indeed correct. > > > Jakob > > Am Montag, 4. August 2014 19:26:44 UTC+2 schrieb Martin Albrecht: > > Hi all, > > > > anyone up for reviewing: > > > > 1) > > > > http://trac.sagemath.org/ticket/15672 > > > > which fixes a simple bug in the Magma interface when computing Gröbner > > bases. > > > > 2) > > > > http://trac.sagemath.org/ticket/16585 > > > > which improves Polynomial Sequences and fixes many small annoyances there. > > > > Cheers, > > Martin signature.asc Description: This is a digitally signed message part.
Re: [sage-devel] On scientific computing, Python and Julia
>> >> Are you seriously claiming that "power series over a finite field" have no >> applications? > > > I can imagine you could invent an "application", so I would not say these > objects > have "no applications".I can even invent one application for you. The > application is > "show a structure that can be created by a computer program that consists of > a power > series etc etc." This sort of smacks of the self referentiality that comes > from answering > the command: > > Use X in a sentence. > > by the response > "Use X in a sentence. >> Power series over finite fields play a very important part in the algorithms used in elliptic curve cryptography. That is a real world application, and not one which has been invented for the sake of it. John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: review requests
Hi Martin, I would review (the simple) 15672. Since it is my first review in Sagemath, I have to find out how to review first and how to check, that your patch is indeed correct. Jakob Am Montag, 4. August 2014 19:26:44 UTC+2 schrieb Martin Albrecht: > > Hi all, > > anyone up for reviewing: > > 1) > > http://trac.sagemath.org/ticket/15672 > > which fixes a simple bug in the Magma interface when computing Gröbner > bases. > > 2) > > http://trac.sagemath.org/ticket/16585 > > which improves Polynomial Sequences and fixes many small annoyances there. > > Cheers, > Martin -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
