On 12 ago, 11:38, Jason Grout wrote:
>
> Well, there is a general trend towards using functions instead of
> attributes in Sage. I think the main reason is for documentation (I
> wish python had attribute docstrings that we could query!).
>
They wouldn't be attributes (that would involve having
I suspect that many of these issues would be resolved by using Maxima
directly, using
one of the graphical interfaces (e.g. wxmaxima).
--
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
On Aug 2, 10:47 pm, William Stein wrote:
> On Mon, Aug 2, 2010 at 1:38 PM, cousteau
> wrote:
> > I'm studying engineering, and I'm used to some programs such as
> > Matlab, Maple, etc. When I knew about SAGE I found it very powerful,
> > simple and well structured, but I quickly found out that
On 8/7/10 3:14 AM, dagss wrote:
On Aug 3, 5:52 am, Jason Grout wrote:
6. TRANSPOSE/CONJUGATE
It seems that implementing this would just involve modifying the
__pos__(self) method for complexes, matrices and complex matrices, and
I think that both conjugating and transposing are common enough
op
Maurizio's function is pretty nice! It's exactly what I was looking
for. I think it should be included in future releases. But it's a bit
slow (at least for the 1..1e9 range), maybe it should be rewritten or
compiled.
The only thing I didn't like is that it saves the image to the current
directory,
On Sat, Aug 7, 2010 at 10:31 AM, William Stein wrote:
> On Sat, Aug 7, 2010 at 5:23 AM, Robert Miller wrote:
>> On Fri, Aug 6, 2010 at 4:52 PM, cousteau
>> wrote:
>>> The aim of my syntax suggestion wasn't to clone Matlab's syntax, but
>>> to provide an easy way to input matrices.
>>
>> Speakin
On Sat, Aug 7, 2010 at 5:23 AM, Robert Miller wrote:
> On Fri, Aug 6, 2010 at 4:52 PM, cousteau
> wrote:
>> The aim of my syntax suggestion wasn't to clone Matlab's syntax, but
>> to provide an easy way to input matrices.
>
> Speaking of syntax and matrices, let's not forget the seemingly
> biza
On Fri, Aug 6, 2010 at 4:52 PM, cousteau wrote:
> The aim of my syntax suggestion wasn't to clone Matlab's syntax, but
> to provide an easy way to input matrices.
Speaking of syntax and matrices, let's not forget the seemingly
bizarre behavior one gets when one does
sage: trace(M)
for a matrix
On Aug 3, 5:52 am, Jason Grout wrote:
> >> 6. TRANSPOSE/CONJUGATE
> >> It seems that implementing this would just involve modifying the
> >> __pos__(self) method for complexes, matrices and complex matrices, and
> >> I think that both conjugating and transposing are common enough
> >> operations t
> * a function that plots the Bode diagram. Once it's possible to (1)
> draw logarithmic axes, (2) align plots on a graphic array so that both
> horizontal axes scales match perfectly, and maybe (3) select the
> divisions on the axes (it would be nicer to have divisions each 15 or
> 45 degrees than
On 5 ago, 04:31, William Stein wrote:
> On Wed, Aug 4, 2010 at 4:42 PM, Alex Ghitza wrote:
> > On Wed, 4 Aug 2010 13:21:11 -0700 (PDT), cousteau
> > wrote:
> >> I agree with Simon in that developers may be reluctant to modify the
> >> preparser unless it's strictly necessary.
> >> An argument i
On Wed, Aug 4, 2010 at 4:42 PM, Alex Ghitza wrote:
> On Wed, 4 Aug 2010 13:21:11 -0700 (PDT), cousteau
> wrote:
>> I agree with Simon in that developers may be reluctant to modify the
>> preparser unless it's strictly necessary.
>> An argument in favor of changing it would be Sage's mission:
>>
On Wed, 4 Aug 2010 13:21:11 -0700 (PDT), cousteau
wrote:
> I agree with Simon in that developers may be reluctant to modify the
> preparser unless it's strictly necessary.
> An argument in favor of changing it would be Sage's mission:
> "Creating a viable free open source alternative to Magma, Ma
On 3 ago, 13:01, Simon King wrote:
>
> 1) It must be easily recognisable for the preparser. I think this is
> the case here.
> 2) There is no way to interpret it in Python syntax (i.e., there can
> be no doubt for the preparser which syntax is being used). I think
> this is the case here, since ha
Hi Johan!
On Aug 3, 9:57 am, "Johan S. R. Nielsen"
wrote:
> > 4. MATRIX INPUT
> > ...
> > (Another alternate syntax would be using a semicolon inside a list:
> > "[1,2;3,4]", or "[1,2,3;]" for row matrices; it's more Matlab-like but
> > it still has the same problem...
At least, it seems technic
> 4. MATRIX INPUT
> If the "[...]m" syntax is messing too much with Python's syntax, don't
> implement it then, but I keep thinking there should be an easier way
> than the one right now to input matrices. It's just not comfortable
> for people who does an intensive usage of matrices.
> (Another al
On 8/2/10 4:59 PM, cousteau wrote:
3. BODE DIAGRAMS
Well, ok, maybe when I tried to plot a bode diagram I didn't research
much on the graphics array point, but there's still missing a way to
graphics array doesn't line up the scales with each other (if that's
needed). However, that is very e
On 8/2/10 6:40 PM, kcrisman wrote:
On Aug 2, 7:59 pm, cousteau wrote:
3. BODE DIAGRAMS
Well, ok, maybe when I tried to plot a bode diagram I didn't research
much on the graphics array point, but there's still missing a way to
make the X axis have a logarithmic scale (without replacing x wit
On Mon, Aug 2, 2010 at 6:40 PM, kcrisman wrote:
> Finally, having multiple interfaces to Sage would be a great thing!
> The notebook is great for many educational and research purposes, the
> command line for others, and why not one for engineering/programming?
> Are there any IDE candidates which
On Mon, Aug 2, 2010 at 4:59 PM, cousteau wrote:
> 1. ENGINEERING MODE
> Ok, I didn't think about the problems that using real numbers where
> indexes are required would cause. Doesn't look easy to workaround, so
> better forget about this one.
>
> 2. UNITS
> Good to know that Sage already supports
On Aug 2, 7:59 pm, cousteau wrote:
> 1. ENGINEERING MODE
> Ok, I didn't think about the problems that using real numbers where
> indexes are required would cause. Doesn't look easy to workaround, so
> better forget about this one.
>
I also encourage the appending of a . syntax. But we've defin
1. ENGINEERING MODE
Ok, I didn't think about the problems that using real numbers where
indexes are required would cause. Doesn't look easy to workaround, so
better forget about this one.
2. UNITS
Good to know that Sage already supports units, when were they
implemented? Apparently not in 4.1.2 at
>> sage: matrix(2, [1,2, 3,4])
>> [1 2]
>> [3 4]
>>
>> I don't like your suggestion to introduce something that isn't valid
>> Python to enter matrices.
>
> Could you please clarify the policy to introduce unacceptable Python
> syntax in the preparser?
There is no policy. My personal policy is t
Sorry, I mistyped the last part, which I replicate here.
I would add to this list a different notebook interface, something
like a single file editor, plus an online console... something like
Matlab's IDE :) I'm actually investigating how difficult it would be
using codemirror plugin (already in S
I'd like to jump in, since I often struggles with those issues. I
still suggest to estimate the engineering audience in this list to
coordinate a little and maybe just start with a little wiki to
cooperate.
>From my little experience, I can tell you that SAGE is a wonderful
investment for its inter
25 matches
Mail list logo
