Maybe I'm missing something here, but aren't these test also badly stated?
This would be a good example why some tolerance should be included
if one test something with floating points: Every small change in some flop
somewhere in the
code will lead to a fail.
I personally wouldn't call something
tions (specifically, matrix-vector).
>
>
>
>
> On Sunday, February 15, 2015 at 3:37:25 PM UTC+1, maldun wrote:
>>
>> Hi!
>>
>> Maybe this may be interesting for future consideration with respect which
>> blas implementation to choose:
>>
>>
Sorry I mean MKL, somehow the I lost the L ...
--
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
Hi!
Maybe this may be interesting for future consideration with respect which
blas implementation to choose:
https://github.com/xianyi/OpenBLAS/issues/322
It appears that OpenBLAS seems to match more and more MKL performance.
--
You received this message because you are subscribed to the Goog
Hi!
On Thursday, December 11, 2014 10:47:20 PM UTC+1, William wrote:
>
> On Thu, Dec 11, 2014 at 1:28 PM, maldun >
> wrote:
> > That's great to hear!
> >
> > Although I don't know If GPL3 is the best choice ...
>
> I actually didn't have an
That's great to hear!
Although I don't know If GPL3 is the best choice ...
Are there already alternative plans to make funding from SMC, since closed
Source is not an option anymore?
(I think this topic is important, since resources are a major issue)
On Thursday, December 11, 2014 6:47:05 PM U
lliam wrote:
>
> On Tue, Dec 9, 2014 at 12:14 PM, maldun >
> wrote:
> > Hi!
> >
> > Concerning the support problematic for ARM, Windows etc:
> >
> > We should ask ourselfs if we need a more minimal Sage distribution,
> which is
> > easily po
Hi!
Concerning the support problematic for ARM, Windows etc:
We should ask ourselfs if we need a more minimal Sage distribution, which
is easily portable to
ALL Platforms. The main problem with Sage on many platforms is, that some
packages often fail to build.
Especially C based packages as tr
ch we should not underestimate.
On Friday, December 5, 2014 9:39:55 PM UTC+1, William wrote:
>
> On Fri, Dec 5, 2014 at 12:19 PM, maldun >
> wrote:
> > What we still don't have is a working windows version. This is still a
> big
> > blocker for being succes
What we still don't have is a working windows version. This is still a big
blocker for being succesfull.
On Friday, December 5, 2014 8:17:44 AM UTC+1, Nathann Cohen wrote:
>
> Helloo everybody !
>
> I am preparing some Sage talk, and I wanted to say at some point:
> "Honestly we are not that
Hi!
Since William's statement, that Sage failed as a real alternative to the 4
MMs there are currently some threads
with thoughts on improving Sage.
But till now I see only discussions among the devlopers. But I think we
should also ask the users.
The most of us here are scientists. But to make
Nice arcticle!
I totally agree with his comments about Matlab. It was written as
fast Fortran interface and still has this feeling. Object oriented
programming is a joke in Matlab. I used Matlab 2009 and measured
1ms(!) time for access to one simple class member. (Comparison:
Pyton needs some µs
TC+1, Dr. David Kirkby (Kirkby
Microwave Ltd) wrote:
>
> On 27 Nov 2014 20:51, "maldun" > wrote:
>
> > I personally a comparison of sage with the other Systems is quite hard,
> since all of the other 4Ms concentrate more or less
> > on particular fields of mathe
+1
As already said in an other thread: I don't understand this high waves of
emotion, and I don't think it is healthy
for the community
--
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
On Friday, November 28, 2014 11:37:20 PM UTC+1, Simon King wrote:
>
> Hi Maldun,
>
> On 2014-11-28, maldun > wrote:
> > So far as I understand, this code/guidline/whatever does not serve as a
> > law, or is written in stone,
> > nor does it say: "If
On Friday, November 28, 2014 11:04:08 PM UTC+1, vdelecroix wrote:
>
> Hi,
>
> 2014-11-28 15:48 UTC−06:00, maldun >:
> > Hi all!
> >
> > I quite watched this discussion for this so called code of conduct.
> There
> > are a lot of
> > oppo
Hi all!
I quite watched this discussion for this so called code of conduct. There
are a lot of
opponents of this idea and I wonder why.
So far as I understand, this code/guidline/whatever does not serve as a
law, or is written in stone,
nor does it say: "If you don't behave as stated in the cod
One of the most important differences between Sage and Mathematica, is that
no one of the developers has such a big ego than Stephen Wolfram. It even
got it's own music theme: https://mollyrocket.com/11235
And we all know that Python will never decipher the universe like the
Wolfram language wi
The only clean solution for this behaviour would be a warning e.g:
"Warning: This Identity holds only almost everywhere!"
But I don't know if it's worth the effort ...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
>
>
> This is in some sense good, since we don't have to care about the
> derivative at zero,
> but in an other sense it is not so good, since the subdifferential ∂abs(0)
> = [0,1] is a bounded and with this definition one could come to the false
> conclusion that abs(x)
> has a pole, althoug
Traceback (most recent call last)
in ()
> 1 f(x=Integer(0))
/home/maldun/sage/sage-6.3/local/lib/python2.7/site-packages/sage/symbolic/expression.so
in sage.symbolic.expression.Expression.__call__
(build/cythonized/sage/symbolic/expression.cpp:21933)()
/home/maldun/sage/sage-6.3/local/
Hi!
On trac http://trac.sagemath.org/ticket/16813 Ralf Stephan and I come to
the question which representation of legendre_Q and gen_legendre_Q is
better suited,
since it is not unique due to the complex logarithm.
We have several choices to represent the logorithm appering in the formula
of le
>
> Well, I think you didn't understand me or I don't understand you.
> There is already numpy, scipy and matplotlib in Sage and there is no
> obstruction whatsoever to use it. One has to turn off the preparser,
> otherwise you might see really odd errors.
>
>
> Oversaw that comment ...
No it
I know that, but it frightens me. I have no idea how to enter those
characters ...
Without knowing anything, I bluntly assume that Sage will have a
Python-2-only policy for variable names.
-- H
Nothing simpler than that:
https://code.google.com/p/ibus/wiki/LaTeX
based on Ibus: https://cod
On Wednesday, August 27, 2014 7:00:51 PM UTC+2, Harald Schilly wrote:
>
>
>
> On Wednesday, August 27, 2014 4:16:46 PM UTC+2, bluescarni wrote:
>>
>> My impression is that the Scipy-Numpy-Sympy ecosystem is a better fit
>> than Sage, at least for numerical purposes.
>>
>
> Mine too, and despite S
There a reports on Trac that sage 5.9 worked fine on windows 7 64-Bit.
http://trac.sagemath.org/wiki/CygwinPort
So it is no science-fiction to say that sage on Cygwin is possible.
Indeed it will not come without some trouble and hard work.
On Monday, August 25, 2014 1:48:41 PM UTC+2, Dr. David Ki
And I forgot: It is defenitely better than the 5th M, namely MatCAD!
--
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 p
Sage has definietly not failed! I use it as alternative to Matlab and
Mathematica for years now, and what the true strength of Sage is not, that
it is better than one of the 4M's, but is doing a equivalently good job in
all those areas, which each of this programs is speciallized in!
The one th
I don't think it's a bad idea to make something partly commercial.
>From the moral point of view I may cite Richard Stallmann (
http://www.gnu.org/philosophy/selling.html ):
> Many people believe that the spirit of the GNU Project is that you should
> not charge money for distributing copies o
Hi!
Python XY ( https://code.google.com/p/pythonxy/ )and WinPython
(http://winpython.sourceforge.net/) do this for years now and are working
properly. Maybe one can use this as a start since many of the needed
prequisites are there.
but why not concentrate on a working cygwin port, and bundle
+1
One could also go further and raise a PlusInfinitiyException or a
MinusInfinityException and handle them correctly.
On Monday, January 6, 2014 5:39:56 PM UTC+1, Gregory Bard wrote:
>
> Perhaps we could get the best of both worlds?
>
> We could throw a "divergent integral/sum exception" (that
y, December 20, 2013 2:58:51 AM UTC-10, maldun wrote:
>>
>> Another more careful approach would be to start at the field of rational
>> functions and extend it step by step with algebraic and transcendental
>> functions, till we reach a field which is maximal under the
Another more careful approach would be to start at the field of rational
functions and extend it step by step with algebraic and transcendental
functions, till we reach a field which is maximal under the available
symbolic expressions.
On Friday, December 20, 2013 9:26:22 AM UTC+1, maldun
On Thursday, December 19, 2013 7:47:19 PM UTC+1, Nils Bruin wrote:
> On Wednesday, December 18, 2013 11:04:22 PM UTC-10, maldun wrote:
>>
>> What I mean is that we should only allow expressions of meromorphic
>> functions in the symbolic field, i.e. we would
r 2013 09:04, maldun > wrote:
> > The fact, that SR is not a field is interesting, the Kronecker delta
> example
> > on the ticket shows it quite well. But the problem originates from the
> fact,
> > that the Kronecker delta is not a continuous function. The r
, John Cremona wrote:
>
> On 19 December 2013 09:04, maldun > wrote:
> > The fact, that SR is not a field is interesting, the Kronecker delta
> example
> > on the ticket shows it quite well. But the problem originates from the
> fact,
> > that the Kronecker delta is
The fact, that SR is not a field is interesting, the Kronecker delta
example on the ticket shows it quite well. But the problem originates from
the fact,
that the Kronecker delta is not a continuous function. The ring of analytic
functions is an Integral domain.
Question: Should we define a subs
>
> Moreover, I feel very uncomfortable having an extra layer with
> symbolic polynomial. Most of the time, the symbolic ring should just
> be avoided. And I guess a long term goal of Sage would be to make it
> disappear.
>
> Vincent
>
> 2013/12/18, maldun >:
> &
mial. Most of the time, the symbolic ring should just
> be avoided. And I guess a long term goal of Sage would be to make it
> disappear.
>
> Vincent
>
> 2013/12/18, maldun >:
> > Why reinvent the wheel? A symbolic polynomal class should be capable of
> a
&g
The fact, that SR is not a field is interesting, the Kronecker delta
example on the ticket shows it quite well. But the problem originates from
the fact,
that the Kronecker delta is not a continuous function. The ring of
continuous functions is an Integral domain.
Question: Should we define a su
The fact, that SR is not a field is interesting, the Kronecker delta
example on the ticket shows it quite well. But the problem originates from
the fact,
that the Kronecker delta is not a continuous function. The ring of
continuous functions is an Integral domain.
Question: Should we define a su
Good Job!
But I have to agree with Volker, using strings is not a good idea.
Why not using functions as input instead?
e.g. in your example from the tutorial:
X. = M.chart('x y z', 'xyz')
I would use something like
var('x y z')
charti = x*y*z
X = M.chart(vars = [x,y,z], map = charti)
On Sund
rings.
The other benefit is the possibility to extend the class for symbolic usage.
On Wednesday, December 18, 2013 12:04:28 PM UTC+1, Simon King wrote:
>
> Hi again,
>
> On 2013-12-18, maldun > wrote:
> > 1) I think that applying Polynomial division by commands like
> >
And another thing: A more unified interface for polynomials.
Currently we have, as you mentioned, three ways to define polynomials. It
would enable us to design a class which provides a good default behavior
for the average user.
--
You received this message because you are subscribed to the G
On Tuesday, December 17, 2013 3:01:47 PM UTC+1, Volker Braun wrote:
>
> On Tuesday, December 17, 2013 12:34:31 PM UTC, maldun wrote:
>>
>> And I have another question: why github?
>>
>
> We only use github to mirror our own repo to save bandwidth. All
> dev
King wrote:
>
> Hi,
>
> On 2013-12-17, maldun > wrote:
> > On ticket http://trac.sagemath.org/ticket/9706 for the orthogonal
> > Polynomials Jeroen Demeyer came up with the the idea of a
> > SymbolicPolynomial class. I think that's a great idea, because, if wel
or better for the client: hg-git (http://hg-git.github.io/)
On Tuesday, December 17, 2013 1:26:23 PM UTC+1, maldun wrote:
>
> Why not use git-hg? https://github.com/cosmin/git-hg
>
> On Monday, December 16, 2013 11:51:27 AM UTC+1, Volker Braun wrote:
>>
>> I would recom
And I have another question: why github? afaik bitbucket would allow to use
both git and mercurial. So it is possible for users to submit a mercurial
patch on a git repo and vice versa. I think this would avoid a lot of
compability issues.
I peronally prefer git, but I guess there are a lot of p
Why not use git-hg? https://github.com/cosmin/git-hg
On Monday, December 16, 2013 11:51:27 AM UTC+1, Volker Braun wrote:
>
> I would recommend people change their mercurial patches to git branches,
> even only if to get their feet wet with git and the "sage -dev" scripts.
> But I will merge merc
Hi all!
On ticket http://trac.sagemath.org/ticket/9706 for the orthogonal
Polynomials Jeroen Demeyer came up with the the idea of a
SymbolicPolynomial class. I think that's a great idea, because, if well
designed, such a class has much potential to give very much comfort to the
handling of sag
code, and its tiring to test and look through about
2000 lines of code.
Hope this approach is ok for you, but I think it is better the get new
polys every few version, instead of getting no new classes.
cheers maldun
--
You received this message because you are subscribed to the Google G
It is not only more pythonic if you cut the series at N-1 it is also
natural
if you are used to work with spectral methods and ffts, because a
trig. poly. with deg
N-1 has N coefficients, since the constant term has degree 0.
greez
Maldun
On Jun 18, 2:25 am, Andrey Novoseltsev wrote:
> He
If you want I could make the numpy update again. Since most necessary
patches of the Bugs we found in #9808 should be merged in 1.5.1 this
should be rather easy.
regards,
Stefan
On Jan 27, 2:45 pm, kcrisman wrote:
> On Jan 27, 5:30 am, François Bissey
> wrote:
>
> > Hi all,
>
> > so it's that t
Would be good to know!
I updated the corresponding documentation in numerical sage:
http://trac.sagemath.org/sage_trac/ticket/10689
these examples should work now. You could simply test waeve with the
repaired examples ^^
(sorry for possible double posting ^^")
greez,
maldun
On Jan 25,
Update: I allowed myself to update the docu:
http://trac.sagemath.org/sage_trac/ticket/10689
would need review.
greez maldun
On Jan 25, 3:16 pm, maldun wrote:
> As mentioned in the other post, it's included in scipy and can be
> imported via
>
> from scipy import weave
&g
As mentioned in the other post, it's included in scipy and can be
imported via
from scipy import weave
so I think this package is simply outdated.
greez,
maldun
On Jan 22, 3:48 pm, Jeroen Demeyer wrote:
> There is some documentation about using Weave, but it doesn't work.
&g
5, 2:46 pm, maldun wrote:
> Question: Isn't a version of weave included in scipy, or would
> deleting the weave in Sage,
> also cripple the weave in Scipy? (I personally don't think so)
>
> I only import weave from scipy via from scipy import weave
> so if removing weave doe
Question: Isn't a version of weave included in scipy, or would
deleting the weave in Sage,
also cripple the weave in Scipy? (I personally don't think so)
I only import weave from scipy via from scipy import weave
so if removing weave doesn't do any harm to the weave in scipy, I have
no problems wi
Also +1 for keeping.
Many people which are more familiar with Matlab expect this behavior
in Sage too.
(I recently introduced Sage to some people)
Of course it's safer to specify the variable, but if I need to I can
do it. I think
this should always be a users choice and never the choice of the
de
oned above: to understand BuiltinFunction, you should
understand how the base class is working (at least the basics).
regards,
maldun
On 18 Jan., 22:24, Chris Swierczewski wrote:
> > Coercion is currently still a little problem, and I think you would
> > earn some credits here if a
n the code I
posted on trac if it helps you:
http://trac.sagemath.org/sage_trac/ticket/9706
If you need a quick solution, simply writing a small python class
would do the trick. (similar as in the current ortho_polys version)
regards,
maldun
On 18 Jan., 17:13, Chris Swierczewski wrote:
> &
gards,
maldun
On Jan 18, 1:14 pm, maldun wrote:
> Of course theta can't handle lists.
> Try map instead: map(theta,[x,x^2,x^3]), because map applies the
> function
> to every list element.
>
> Hope this helps =)
> maldun
>
> On Jan 14, 12:22 pm, Chris Swierczewski
Of course theta can't handle lists.
Try map instead: map(theta,[x,x^2,x^3]), because map applies the
function
to every list element.
Hope this helps =)
maldun
On Jan 14, 12:22 pm, Chris Swierczewski wrote:
> Does anyone know of an example where a class __call__ method takes lists as
I had the same errors, simply update the source
The version is 2.8.7 current is 2.8.11
You find a new spkg on
http://computational-sage.googlecode.com/files/wxPython-2.8.11.0.spkg
On 17 Jan., 20:11, Sancho wrote:
> I'll try to apply this fix:http://trac.wxwidgets.org/ticket/10883
>
> On Jan
-
install, but I'm quite sure
there is a better way. has somenone an Idea?
greez maldun
--
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 more options, visit this group at
quite sure
there is a better way. has somenone an Idea?
greez maldun
--
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 more options, visit this group at http://groups.google.com/group
for beginners too, who
search a good alternative to the notebook. (or generally for students
who begin programming, but find the emacs confusing)
greez maldun
--
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
Hi, Burcin!
I think this is a great Idea!
I'm short on time in the next months, but
If I'm free again, could help with this.
greez,
Stefan
On 16 Okt., 14:21, Burcin Erocal wrote:
> Hi,
>
> Motivated by the call for the bug days, here is an idea to manage the
> rapidly increasing number of "new"
Hi!
Burcin asked me to make a new version of ortho polys some time ago,
and since Ticket #9808 for upgrading numpy and scipy finally got a
positive review, I can now finish this task.
Please feel free to look at the new version. The new version is a lot
faster as the old implementation with maxim
Ok I found a workarround:
I enlarged the ranges in the for loop for the search of the functions.
The change apparently made the search range for the function foo
wider.
All doctests pass now
Open question why does this work if I type it in by hand...
On 14 Okt., 21:57, maldun wrote:
> Hi
quot;devel/sage/sage/symbolic/pynac.pyx"
I worked the first one out. This is clear, that when you add new
symbolic objects the random expressions change.
But the second is giving me headaches for some time now... I give an
example because I think the others have the same problem:
File "/hom
her things, like a new version of
orthogonal polynomials before.
Another goal would be doing something similar to Mathematica's
NIntegrate, but his would take some years and should only considered
as long time goal for sage.
-maldun
On Oct 14, 6:01 am, Oscar Gerardo Lazo Arjona
wrote:
> Hell
Thanks for the hints but actually I'm doing this anyway since my sage
holds a lot of experimental stuff which I use for my work. So I have
always an clean intallation of Sage ready if something goes wrong =)
But using git is a nice Idea to manage this, I had thought about that
earlier.
-m
on is Sage
is based on Python, and has therefore the benefit, that it is based on
a real programming language, which knows more than one data type.
Just my 2 cents.
-maldun
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
mputations with Cython:
http://conference.scipy.org/proceedings/SciPy2009/paper_2/full_text.pdf
Hope that helps a little bit.
-maldun
On Oct 14, 10:17 am, Alexander Dreyer
wrote:
> Hi,
> are there Sage Worksheets around for explaining the advantages of
> Sage to people, which usually u
Thanks for the quick response! I will update my sage on this computer
then =)
On Oct 12, 5:20 pm, Burcin Erocal wrote:
> On Tue, 12 Oct 2010 08:05:40 -0700 (PDT)
>
> maldun wrote:
> > Hi all!
>
> > I had the following problem with the latex() function in sage:
>
&
\sqrt{x} instead
before the \frac{...} where it belongs.
Perhaps the parser has the wrong priorities
--maldun
--
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 more options, visit this
You're right... I really should go to bed now =)
Well then it works also for ubuntu ^^
-maldun
On 10 Okt., 23:07, Mike Hansen wrote:
> On Sun, Oct 10, 2010 at 2:05 PM, maldun wrote:
> > Thanks to your patch the segfault is now gone, but apperently a new
> > problem arises:
On 10 Okt., 20:47, Mike Hansen wrote:
> On Sun, Oct 10, 2010 at 11:15 AM, maldun wrote:
> > sage: sage: a = var('a')
> > sage: sage: R. = a.parent()[]
> > sage: sage: (x - a).change_ring(RR) # boom!
>
> I've posted a patch athttp://trac.sagemath.org
invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run Sage under gdb with 'sage -gdb' to debug this.
Sage will now terminate (sorry).
More interesting is this from sage -gdb
/home/maldun/
invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run Sage under gdb with 'sage -gdb' to debug this.
Sage will now terminate (sorry).
More interesting is this from sage -gdb
/home/maldun/
invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run Sage under gdb with 'sage -gdb' to debug this.
Sage will now terminate (sorry).
More interesting is this from sage -gdb
/home/maldun/
Ok then they didn't upgrade the valgrind package in the meantime.
I'm using Ubuntu myself and had the same problem, but I build my own
package with the latest source from svn. It worked for me
I can send it to you if you want, and you test it out.
maldun
On 7 Okt., 20:07, Johannes w
I would suggest to run sage with valgrind to get more information out
of your error messages.
On 7 Okt., 17:31, Johannes wrote:
> Hi list,
> i got my sage crashed once again:
>
> sage: a,b,c= var('a,b,c')
> sage: mprime = matrix([[01,b+1,2],[a+1,2,1],[2,1,c+1]])
> sage: cp = mprime.charpoly()
> s
When I find some time this weekend, I can do some proofreading.
Hope you get along with austrian german as well ;-)
greez,
maldun
On Oct 5, 12:10 am, Philipp Schneider
wrote:
> Dear Sage community,
>
> Michael Mardaus and I are happy to announce that we have finished
> tra
When I find some time this weekend I will make a little bit
proofreading.
greez,
maldun
On Oct 5, 12:10 am, Philipp Schneider
wrote:
> Dear Sage community,
>
> Michael Mardaus and I are happy to announce that we have finished
> translating the complete Sage tutorial to German.
>
On 30 Sep., 14:58, Jason Grout wrote:
> On 9/30/10 6:25 AM, maldun wrote:
>
> > There is another thing that I want to mention another thing:
>
> > Leif mentioned that it would be important that after installing of
> > numpy rebuilding of sage should happen with -b,
There is another thing that I want to mention another thing:
Leif mentioned that it would be important that after installing of
numpy rebuilding of sage should happen with -b, and not with -ba
like I suggested. I can understand his thoughts because actually it is
a good thing when sage builds the
Could you alse give the 1.4.1.p0 a spin? it contains the patch for
linux ppc. (download link a few posts above) Perhaps the whole thing
will get obsolete
with 1.5.0 but I'm curious if that would work also, because I'm not
sure if I get 1.5.0 ready in time.
greez
maldun
On Sep 30
>
> Maldun, do you think that would be possible? I'd be willing to retest
> it on the OS X PPC box to make sure that didn't break anything - no,
> Dima, I still don't have the Linux up on that yet :(
>
> - kcrisman
I packed it:
http://code.google.com/p/spkg-u
Yeah that's true, and I wouldn't make the final decision on that, but
it would be great if it could be tested
anyway, I think this may make porting to 1.5.1 easier when it finally
will be released,
On 29 Sep., 18:49, kcrisman wrote:
> On Sep 29, 11:46 am, maldun wrote:
>
>
>
> Maldun, do you think that would be possible? I'd be willing to retest
> it on the OS X PPC box to make sure that didn't break anything - no,
> Dima, I still don't have the Linux up on that yet :(
>
> - kcrisman
Sure why not! I give it a shot and post a p
On Sep 29, 3:55 pm, Volker Braun wrote:
> I thought this is fixed due to Debian people pestering numpy dev's :-)
> But I'm not sure if the patch is already included in the newest
> release.
>
> http://mail.scipy.org/pipermail/numpy-svn/2010-July/004318.html
>
> Volker
As far as I know this will
This is the reason why I think Sage and Python in general are so
useful.
I'm doing a lot of experimental code recently, and it is very easy to
get them
up and running in Python/Sage programs.
And since the whole system is so flexible in communicating with other
languages,
sorting out the critical
This is the reason why I think Sage and Python in general are so
useful.
I'm doing a lot of experimental code recently, and it is very easy to
get them
up and running in Python/Sage programs.
And since the whole system is so flexible in communicating with other
languages,
sorting out the critical
Ok latest update: numpy-1.4.1 and scipy-0.8 should now be ready! (see
ticket #9808; http://trac.sagemath.org/sage_trac/ticket/9808 )
Many many thanks to fbissey for the help with the spkg-install script,
and kcrisman for additional testing!
I have now a question: Should we merge it into sage-4.6.
This is just my opinion, but isn't the name SPKG (SAGE package)
already quite specialised?
On Sep 27, 11:13 pm, Ondrej Certik wrote:
> Hi,
>
> in Femhub (http://femhub.org) I wrote a new buildsystem from scratch
> using Python, so far it's a simple Python script:
>
> http://github.com/hpfem/femhu
Ok first I would thank everyone for their thoughts. I think the best
is to do a design document, or at least start a ticket where we come
to a common agreement how to handle the input because there are
several possiblities to do that. And it is important that we are more
or less happy about the sol
PyOpenCL would also be available:
http://trac.sagemath.org/sage_trac/ticket/10009
Everything works for me, I hope it's useful for others too!
greez,
maldun
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+uns
Since nobody answered I figured it out myself how it works.
Opened a ticket on this. see http://trac.sagemath.org/sage_trac/ticket/10009
. This would need testing, it is only tested on ubuntu 10.04
with latest NVIDIA developer drivers, and CUDA toolkit.
I use a geforce 9500 GT.
greez,
maldun
1 - 100 of 121 matches
Mail list logo
