On Thu, Mar 01, 2007 at 11:14:14PM -0800, William Stein wrote:
>
> On Thursday 01 March 2007 11:01 pm, Nick Alexander wrote:
> > On Mar 1, 3:25 pm, Martin Albrecht <[EMAIL PROTECTED]>
> >
> > wrote:
> > > > > I'm also wondering what are the most common usage methods of SAGE:
> > > > > 1) noteboo
Keep up the great work you're doing. If I get enough time, I may email you again
over spring break to ask you some questions about how to improve the tutorial
based on your new stuff.
On 3/2/07, Bobby Moretti <[EMAIL PROTECTED]> wrote:
> Hey Joel,
>
>
> >
> > I'm wondering if we could have an upd
> I'm also wondering what are the most common usage methods of SAGE:
> 1) notebook
> 2) command line sage prompt
> 3) file.sage or file.py scripts
> Other methods???
Anyone using the Live CD ?
--~--~-~--~~~---~--~~
To post to this group, send email to sage-deve
Hey Joel,
> I'm wondering if we could have an update on the basic calculus rewrite
> which
> was discussed a while ago on the mailing list?
I gave a very brief talk about this at SAGE Days 3. You can see my slides at
http://sage.math.washington.edu/home/moretti/days3/talks/calculus.pdf
if yo
> > I actually use the notebook quite often now, especially when
> > debugging/timing code. The reason is that my inputs are still there (even
> > without going up and down the history) if SAGE crashes etc. I also love
> > the %sagex feature.
>
> Hmm... perhaps we should be thinking about moving t
On Thursday 01 March 2007 11:01 pm, Nick Alexander wrote:
> On Mar 1, 3:25 pm, Martin Albrecht <[EMAIL PROTECTED]>
>
> wrote:
> > > > I'm also wondering what are the most common usage methods of SAGE:
> > > > 1) notebook
> > > > 2) command line sage prompt
> > > > 3) file.sage or file.py script
On Mar 1, 3:25 pm, Martin Albrecht <[EMAIL PROTECTED]>
wrote:
> > > I'm also wondering what are the most common usage methods of SAGE:
> > > 1) notebook
> > > 2) command line sage prompt
> > > 3) file.sage or file.py scripts
>
> I actually use the notebook quite often now, especially when deb
I probably do about 80% notebook and 20% command line.
For real quick things the command line is more convenient, but
if I ever do anything I want to mess with again later,
the notebook is the best place to do it.
Alex
--~--~-~--~~~---~--~~
To post to this group, s
On Thursday 01 March 2007 6:21 pm, Nathan Ryan wrote:
> I mostly use the notebook, too which is what I think we can expect the
> average calculus student to use. This student would want instant
> graphics (not available in either 2) or 3)), copying and pasting via
> ctrl-c and ctrl-v, interactive
I mostly use the notebook, too which is what I think we can expect the
average calculus student to use. This student would want instant
graphics (not available in either 2) or 3)), copying and pasting via
ctrl-c and ctrl-v, interactive tab completion and documentation.
N
[EMAIL PROTECTED]
I use the notebook about 99% of the time. Quite frequently, I'll use the
public notebook while I'm at school, so I can download the worksheet later on.
Very handy for experimenting / jotting ideas down.
On Thu, 1 Mar 2007, Joel B. Mohler wrote:
>
> I'm wondering if we could have an update o
> > I'm also wondering what are the most common usage methods of SAGE:
> > 1) notebook
> > 2) command line sage prompt
> > 3) file.sage or file.py scripts
I actually use the notebook quite often now, especially when debugging/timing
code. The reason is that my inputs are still there (even wit
On 3/1/07, Joel B. Mohler <[EMAIL PROTECTED]> wrote:
>
> I'm wondering if we could have an update on the basic calculus rewrite which
> was discussed a while ago on the mailing list?
>
> I'm giving a talk on SAGE in a week and I might want to have a basic calculus
> demo if it's ready to show.
>
>
On Mar 1, 11:28 pm, "Joel B. Mohler" <[EMAIL PROTECTED]> wrote:
> I'm wondering if we could have an update on the basic calculus rewrite which
> was discussed a while ago on the mailing list?
>
> I'm giving a talk on SAGE in a week and I might want to have a basic calculus
> demo if it's ready t
Interesting discussion on calculus in Sage. I definitely like the use
of "natural syntax" for defining functions. In fact if an
easy_calculus_mode preprocessor is part of the deal, and if we really
want calculus to be "insanely easy" (as David puts it) I would advocate
for going even further.
I d
On Dec 7, 2006, at 5:18 AM, William Stein wrote:
>
> On Thu, 07 Dec 2006 00:08:23 -0800, Robert Bradshaw
> <[EMAIL PROTECTED]> wrote:
>
>>> If we wanted, we could always add that later on top of what I
>>> proposed.
>>> It would just be:
>>>
>>>f = (sin(x)*cos(x+y+3)).function(x,y)
>>>
>>> o
On Thu, 07 Dec 2006 00:08:23 -0800, Robert Bradshaw
<[EMAIL PROTECTED]> wrote:
>> If we wanted, we could always add that later on top of what I
>> proposed.
>> It would just be:
>>
>>f = (sin(x)*cos(x+y+3)).function(x,y)
>>
>> or
>>
>>dummy = sin(x*) * cos(x+y+3)
>>f = dummy.functio
On Thursday 07 December 2006 02:34, William Stein wrote:
> Also, with my proposal one could also already type
>
> f = function( (x,y), sin(x)*cos(x+y+3) )
>
> which is nice since in Mathematica one types "f = Function[ {x,y},
> Sin[x]*Cos[x+y+3] ]".
> Here this would be implemented via:
Thi
On Dec 6, 2006, at 11:34 PM, William Stein wrote:
>
> On Wed, 06 Dec 2006 23:20:56 -0800, Robert Bradshaw
> <[EMAIL PROTECTED]> wrote:
>> First, let me say that I like this proposal.
>> On Dec 6, 2006, at 5:03 PM, William Stein wrote:
>>> Sage calculus
>>> f = alg expr
>>>
>>> f.subs(var, val, .
On 12/6/06, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
>
> First, let me say that I like this proposal.
>
> On Dec 6, 2006, at 5:03 PM, William Stein wrote:
>
> > Sage calculus
> > f = alg expr
> >
> > f.subs(var, val, ...)
> > f.subs(dict)
> > f.subs(list of pairs)
> > implement recursively, with
On Wed, 06 Dec 2006 23:20:56 -0800, Robert Bradshaw
<[EMAIL PROTECTED]> wrote:
> First, let me say that I like this proposal.
> On Dec 6, 2006, at 5:03 PM, William Stein wrote:
>> Sage calculus
>> f = alg expr
>>
>> f.subs(var, val, ...)
>> f.subs(dict)
>> f.subs(list of pairs)
>> implement recu
First, let me say that I like this proposal.
On Dec 6, 2006, at 5:03 PM, William Stein wrote:
> Sage calculus
> f = alg expr
>
> f.subs(var, val, ...)
> f.subs(dict)
> f.subs(list of pairs)
> implement recursively, with base case functions of 1 var and vars and
> constants being clear.
I would
On Wed, 06 Dec 2006 17:18:10 -0800, David Harvey
<[EMAIL PROTECTED]> wrote:
>
>
> On Dec 6, 2006, at 8:14 PM, David Joyner wrote:
>
>>
>> This is brilliant, IMHO.
>>
>>
>> On 12/6/06, William Stein <[EMAIL PROTECTED]> wrote:
>>>
>>> Sage calculus
>>> f = alg expr
>
> But what does "f = alg expr
On Dec 6, 2006, at 8:14 PM, David Joyner wrote:
>
> This is brilliant, IMHO.
>
>
> On 12/6/06, William Stein <[EMAIL PROTECTED]> wrote:
>>
>> Sage calculus
>> f = alg expr
But what does "f = alg expr" mean? Do you mean using predefined
single-character variables?
David
--~--~-~--~-
This is brilliant, IMHO.
On 12/6/06, William Stein <[EMAIL PROTECTED]> wrote:
>
> Sage calculus
> f = alg expr
>
> f.subs(var, val, ...)
> f.subs(dict)
> f.subs(list of pairs)
> implement recursively, with base case functions of 1 var and vars and
> constants being clear.
>
> f.function(*args) -
25 matches
Mail list logo
