On Feb 23, 12:47 pm, Niles wrote:
> A couple of other threads have mentioned ways to possibly shorten the
> startup time for Sage. This made me wonder: What is a good way to
> tell *what* is making Sage take so long to start up? Are certain
> sections of the library taking the majority of the
Hi Sage-Devel, etc.
I'm going to run a small (6 students) number-theory oriented
undergraduate "REU-style" program at University of Washington this
summer (June 20 - August 12, 2011). Sage will play a big role in the
program.
Here's the website: http://wiki.sagemath.org/reu/2011
If you know of
On Wed, Feb 23, 2011 at 8:05 PM, John Cremona wrote:
> The source for eclib is now at eclib.googlecode.com.
Awesome. I'm now even more likely to just browse the code whenever.
-- William
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this gro
The source for eclib is now at eclib.googlecode.com.
Sage's version is older, and should be updated; something for me to do.
John
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For
On Wed, Feb 23, 2011 at 5:29 PM, rjf wrote:
>
>
> On Feb 23, 1:45 pm, Ivan Andrus wrote:
>
>
>>
>> > (RJF) I know of no other programming language that requires this.
>>
>> C++0x will require something similar for templates, so that
>>
>> std::vector> x;
>>
>> will parse instead of requiring
>>
>
On Feb 23, 1:45 pm, Ivan Andrus wrote:
>
> > (RJF) I know of no other programming language that requires this.
>
> C++0x will require something similar for templates, so that
>
> std::vector> x;
>
> will parse instead of requiring
>
> std::vector > x;
>
> That said, I don't think many people c
On 2/23/11 3:56 PM, Robert Bradshaw wrote:
On Wed, Feb 23, 2011 at 1:47 PM, Jason Grout
wrote:
On 2/23/11 3:06 PM, Robert Bradshaw wrote:
On Wed, Feb 23, 2011 at 11:34 AM, William Steinwrote:
On Wed, Feb 23, 2011 at 10:57 AM, Jason Grout
wrote:
On 2/23/11 12:28 PM, William Stein
On Wed, Feb 23, 2011 at 1:47 PM, Jason Grout
wrote:
> On 2/23/11 3:06 PM, Robert Bradshaw wrote:
>>
>> On Wed, Feb 23, 2011 at 11:34 AM, William Stein wrote:
>>>
>>> On Wed, Feb 23, 2011 at 10:57 AM, Jason Grout
>>> wrote:
On 2/23/11 12:28 PM, William Stein wrote:
>
> At lunch
On Wed, Feb 23, 2011 at 1:33 PM, kcrisman wrote:
>
>> > Note that the OP's issue will go away once that deprecation
>> > warning becomes an actual error. (Well, it'll be an error rather than
>> > a bad answer.)
>>
>> Indeed. That will be a large improvement.
>
> Disagree. Does Nils' suggestion wi
On 2/23/11 3:06 PM, Robert Bradshaw wrote:
On Wed, Feb 23, 2011 at 11:34 AM, William Stein wrote:
On Wed, Feb 23, 2011 at 10:57 AM, Jason Grout
wrote:
On 2/23/11 12:28 PM, William Stein wrote:
At lunch yesterday Robert Bradshaw made the interesting suggestion to
read the docs for importlib
On Feb 23, 2011, at 6:37 PM, rjf wrote:
> On Feb 23, 9:17 am, "Dr. David Kirkby"
> wrote:
>> On 02/22/11 10:57 PM, Dr. David Kirkby wrote:
>>> On 02/22/11 03:49 PM, rjf wrote:
A parser for the maxima language is not only easier to write,
it is available in source form. It is also based o
On Wed, Feb 23, 2011 at 1:19 PM, Nils Bruin wrote:
> On Feb 23, 12:50 pm, Robert Bradshaw
> wrote:
>
>> Escaping is nice when one wants to take a derivative, etc. I don't
>> think most calculus students think about "scope" being local or not,
>> and relying on the symbol not being re-defined seem
> > Note that the OP's issue will go away once that deprecation
> > warning becomes an actual error. (Well, it'll be an error rather than
> > a bad answer.)
>
> Indeed. That will be a large improvement.
Disagree. Does Nils' suggestion with the lambda not work? (I don't
know, just asking - maybe
On Feb 23, 12:50 pm, Robert Bradshaw
wrote:
> Escaping is nice when one wants to take a derivative, etc. I don't
> think most calculus students think about "scope" being local or not,
> and relying on the symbol not being re-defined seems like it would
> make for fragile and harder to follow code
On Wed, Feb 23, 2011 at 11:34 AM, William Stein wrote:
> On Wed, Feb 23, 2011 at 10:57 AM, Jason Grout
> wrote:
>> On 2/23/11 12:28 PM, William Stein wrote:
>>>
>>> At lunch yesterday Robert Bradshaw made the interesting suggestion to
>>> read the docs for importlib
>>> (http://docs.python.org/de
On Wed, Feb 23, 2011 at 10:13 AM, slabbe wrote:
> Hi,
>
>> I'm going to still wait a few days before starting, so feel free to
>> pile on if you would like to add to the discussion.
>
> At Sage Days 28, I gave a talk about how to contribute to Sage. The
> philosophy I choose to present was to crea
On Wed, Feb 23, 2011 at 11:45 AM, Nils Bruin wrote:
>> > Do you have the same objections to:
>> > R.=QQ[]?
>
> No, but that is because I am used to magma. Perhaps also because the
> notation contrasts with R = QQ["x","y"]. The fact that the variable
> names only occur on the left side (and in fact
Hi, Nicolas!
On 23 fév, 02:44, "Nicolas M. Thiery"
wrote:
> Hi Alexandre!
>
>
> I assume Eviatar's message was really about using Sage's symbolic
> capabilities for manipulating systems of equations. Not Sage's
> symbolic solver. So one could imagine doing something like:
>
> sage: sy
On 2011-Feb-22 18:30:28 -0600, Jason Grout wrote:
> # We must start a new shell with no .profile or .bashrc files
> # processed, so that we know our path is correct
> PS1="SAGE_ROOT=${SAGE_ROOT}\n(sage subshell) \h:\W \u\$ "
> export PS1
> case $SHELL_NAME in
...
> sh)
On 2011-Feb-22 23:01:14 +, "Dr. David Kirkby"
wrote:
>That could be due to someone setting a path with something like
>
>export PATH=/a/b/c:/d/e/f etc
>
>when it is more portable to use
>
>PATH=/a/b/c:/d/e/f etc
>export PATH
Agreed but I don't think it's worth changing this.
>I've seen a nu
Hm, thinking about how to parse the SR.var("x") properly, it seems a
rather odd symbolic object gets created by
sage: v=SR.var('x,')[1]
sage: x+v
+ x
sage integral(x+v,x)
*BOOM*
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
> > Do you have the same objections to:
> > R.=QQ[]?
No, but that is because I am used to magma. Perhaps also because the
notation contrasts with R = QQ["x","y"]. The fact that the variable
names only occur on the left side (and in fact in a place where they
should not in mathematics!) suggests th
On Wed, Feb 23, 2011 at 10:57 AM, Jason Grout
wrote:
> On 2/23/11 12:28 PM, William Stein wrote:
>>
>> At lunch yesterday Robert Bradshaw made the interesting suggestion to
>> read the docs for importlib
>> (http://docs.python.org/dev/library/importlib.html) and write a
>> customized import hook,
> The side effect of "phi(x)=" is very unexpected and almost certainly
> not intended. In fact, even in the symbolic world I think this can
> lead to nasty surprises. Suppose someone wants to look at the
> derivative of sin(x^2) via the chain rule.
>
> sage: y(x)=x^2
> sage: f(y)=sin(y)
> sa
On 2/23/11 12:28 PM, William Stein wrote:
At lunch yesterday Robert Bradshaw made the interesting suggestion to
read the docs for importlib
(http://docs.python.org/dev/library/importlib.html) and write a
customized import hook, so that every time during Sage startup that a
module is imported, the
On 2/23/11 12:28 PM, William Stein wrote:
At lunch yesterday Robert Bradshaw made the interesting suggestion to
read the docs for importlib
(http://docs.python.org/dev/library/importlib.html) and write a
customized import hook, so that every time during Sage startup that a
module is imported, the
On Wed, Feb 23, 2011 at 10:48 AM, Jason Grout
wrote:
> On 2/23/11 11:35 AM, Nils Bruin wrote:
>>
>> When I saw the following, initially I thought the preparser was
>> providing a very convenient feature:
>>
>> sage: f(t)=sin(t)
>> sage: f
>> t |--> sin(t)
>> sage: parent(t)
>> Symbolic
On 2/23/11 11:35 AM, Nils Bruin wrote:
When I saw the following, initially I thought the preparser was
providing a very convenient feature:
sage: f(t)=sin(t)
sage: f
t |--> sin(t)
sage: parent(t)
Symbolic Ring
but recently I noticed on a trac ticket:
sage: R.=QQ[]
sage: p
On Wed, Feb 23, 2011 at 7:09 AM, Volker Braun wrote:
> Its true that there are lots of failed attempts to get files, which is
> normal for any system where you have a multiple directories which can
> contain any given file:
>
> [vbraun@volker-desktop ~]$ echo quit | strace -f sage |& grep ENOENT |
Hi,
> I'm going to still wait a few days before starting, so feel free to
> pile on if you would like to add to the discussion.
At Sage Days 28, I gave a talk about how to contribute to Sage. The
philosophy I choose to present was to create one personnal branch
using queues for managing many tick
On Feb 23, 9:17 am, "Dr. David Kirkby"
wrote:
> On 02/22/11 10:57 PM, Dr. David Kirkby wrote:
>
>
>
> > On 02/22/11 03:49 PM, rjf wrote:
> >> A parser for the maxima language is not only easier to write,
> >> it is available in source form. It is also based on a well known
> >> technique which i
When I saw the following, initially I thought the preparser was
providing a very convenient feature:
sage: f(t)=sin(t)
sage: f
t |--> sin(t)
sage: parent(t)
Symbolic Ring
but recently I noticed on a trac ticket:
sage: R.=QQ[]
sage: phi(x)=x^2+c
Which causes:
sage: parent(x)
S
On 02/22/11 10:57 PM, Dr. David Kirkby wrote:
On 02/22/11 03:49 PM, rjf wrote:
A parser for the maxima language is not only easier to write,
it is available in source form. It is also based on a well known
technique which is also used by Reduce. The real difficulty is
to implement a Mathematica
On Wed, Feb 23, 2011 at 4:43 AM, Volker Braun wrote:
> I take it that the slow thing is reading ~2000 sage library files from a
> harddisk into the filesystem cache. I'm using SSDs and Sage starts
> consistently within about 1 second. There is "sage -startuptime" to profile.
> The way I see it, th
This would be better asked on sage-support or asksage.
John
On Wed, Feb 23, 2011 at 6:00 AM, Dox wrote:
> Hi group!
> I'm trying to change the metric from Euclidean to Spherical. I know there
> are several ways of doing so, but I'd like to do something like this:
>
> Define the new coordinates v
Its true that there are lots of failed attempts to get files, which is
normal for any system where you have a multiple directories which can
contain any given file:
[vbraun@volker-desktop ~]$ echo quit | strace -f sage |& grep ENOENT | wc
24322 298143 3532797
But, really, that just means tha
Hi group!
I'm trying to change the metric from Euclidean to Spherical. I know there
are several ways of doing so, but I'd like to do something like this:
1. Define the new coordinates var('phi')
2. Give the relation between old and new coordinates x = cos(phi) and y =
sin(phi)
3. Fi
On 2/23/11 6:43 AM, Volker Braun wrote:
I take it that the slow thing is reading ~2000 sage library files from a
harddisk into the filesystem cache. I'm using SSDs and Sage starts
consistently within about 1 second. There is "sage -startuptime" to profile.
The way I see it, the only way to make
I take it that the slow thing is reading ~2000 sage library files from a
harddisk into the filesystem cache. I'm using SSDs and Sage starts
consistently within about 1 second. There is "sage -startuptime" to profile.
The way I see it, the only way to make a significant dent into the startup
tim
A couple of other threads have mentioned ways to possibly shorten the
startup time for Sage. This made me wonder: What is a good way to
tell *what* is making Sage take so long to start up? Are certain
sections of the library taking the majority of the time? Are there
some profiling tools which c
Hi Alexandre!
On Wed, Feb 16, 2011 at 01:13:57PM -0800, Alexandre Blondin Massé wrote:
> On 16 fév, 15:52, Eviatar wrote:
> > Another option would be to use Sage's existing symbolic capabilities.
> > For example:
> >
> > sage: solve(u*v==log(u*v), u)
> > [u == log(u*v)/v]
>
> The equatio
41 matches
Mail list logo
