Rob,
I'm not sure if this is relevant but you might like to check out the
work going on in sympy (physics/quantum/...) I have been keeping an
eye on this (it is now in the main branch but not opened up yet). My
motivation like the authors of the above is in quantum (computation)
but there is an Hi
Way to go... this would be excellent - instant scalable sage
computing:
check out the kind of thing BIx folks are doing for the community:
http://bcbio.wordpress.com/2010/05/08/automated-build-environment-for-bioinformatics-cloud-images/
You have to get sage into this party - actually I think a
Can anyone cast any light on this for me?
This is OOB sage python
00:41 chi:lib.macosx-10.3-i386-2.5 504\> sage --version
Sage Version 3.2.3, Release Date: 2009-01-05
00:41 chi:lib.macosx-10.3-i386-2.5 505\> sage -python
Python 2.5.2 (r252:60911, Jan 6 2009, 19:03:06)
[GCC
x_double_dense.pyx, which seems odd.
>
> Getting back to your question,
> matrix_double_dense.pyxhttp://www.sagemath.org/hg/sage-main/file/8b1d19463fc4/sage/matrix/ma...
> does have an is_symmetric method, which maybe could be modified for
> the purpose you state?
>
> ++
What is the recommended way to extend sage classes? - I want to add
some functionality to the complex matrix class - specifically tests
for: is_symmetric, is_hermitian, is_unitary etc... you get the idea.
I have experienced and read that this is not so straightforward.
I guess I could do it by
I am happy to report that boost_1_35_0, pycuda 0.9 (plus my hacks) are
all now working and tested against this build. Thanks to David for his
help and patches. Game on.
On Sep 12, 1:28 am, Simon Beaumont <[EMAIL PROTECTED]> wrote:
> Ok - got there in the end...
>
> I did a fr
Ok - got there in the end...
I did a fresh build (OS X 10.5.4 intel) with 3.1.1 sources.
Applied David's patches and fixed up the externs in cvxopt sources as
he indicated. All built just fine.
All test pass apart from trace - which is no doubt due to sage command
line not being able to load rea
yet how to to this in an automated
> fashion than to
> just parse the output string from "gcc -v")
>
> If you could supply your Xcode version information, I'd add this info
> to that ticket.
>
> The "uname -a" command gives on my PPC exactly the same i
Kernel Version 8.11.0: Wed Oct 10
18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Power Macintosh
powerpc
that's: OS X 10.4.11
On Sep 8, 7:16 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 8, 10:52 am, Simon Beaumont <[EMAIL PROTECTED]> wrote:
>
> > One more thi
One more thing is that atlas doesn't seem to build on this platform. I
can hand crank an atlat configuration but it barfs beacuse I cant turn
off cpu throttling on the PowerBook G4 - how is this "tuned" for a
binary build?
On Sep 8, 4:52 pm, Simon Beaumont <[EMAIL PROTECT
Just completed this lengthy process on my power book.
A couple of trivial problems arose:
1. had to set MACOSX_DEPLOYMENT_TARGET=10.3 (why not 10.4?) as this
was missing from ntl build and defaults to 10.0 which won't work with -
undefined dynamic_lookup. Workaround was to set this globally, may
On a more upbeat note: the only motivation for all this grief was to
build pycuda - against boost - against a framework based python. I
have not been so impressed with CUDA for basic matrix operations
relative to a fast muti-core CPU on relatively small matrices (though
I really like the pycuda a
On Sep 5, 6:27 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 5, 10:21 am, Simon Beaumont <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> > I tried building sage 3.0.1
>
> *3.0.1*?
>
3.1.1 of course - it's been a long day...
> > with David Philp
I lied about attaching the log (I have a bzipped log if that's of any
interest to anyone)
On Sep 5, 6:21 pm, Simon Beaumont <[EMAIL PROTECTED]> wrote:
> I tried building sage 3.0.1 with David Philps patches - make failed
> first with the r build looking for sage (which is i
I tried building sage 3.0.1 with David Philps patches - make failed
first with the r build looking for sage (which is in there somewhere
but without packages in place) so I did a make -k and have attached
the install.log - I've got a nice framework python and a half baked
sage and cvxopt build sti
On Aug 29, 1:34 am, Carl Witty <[EMAIL PROTECTED]> wrote:
> On Aug 28, 4:34 pm, Simon Beaumont <[EMAIL PROTECTED]> wrote:
>
> > Well any python code fails to work as expected:
>
> > try: sage-python -c "import sys"
> > File "", line 1
&g
I have pycuda working on OSX 10.5.2 with the standard framework based
python and nv CUDA 2.0... now for the hacks!
Not at all sure about the right direction for this CUDA stuff yet.
Simon
On Aug 29, 12:29 am, Simon Beaumont <[EMAIL PROTECTED]> wrote:
> On Aug 28, 11:22 pm, David Phil
ein
configure has:
$PYTHON -c "import sys; print (\"%d.%d\" % (sys.version_info[0],
sys.version_info[1]))"`
On Aug 28, 10:32 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 28, 2008 at 1:19 PM, Simon Beaumont <[EMAIL PROTECTED]> wrote
On Aug 28, 11:22 pm, David Philp <[EMAIL PROTECTED]> wrote:
> On 29/08/2008, at 7:56 AM, mabshoff wrote:
>
> > David Philip has been playing with building PyCuDA against Sage's
> > Python on OSX.
>
> No!!! I'd love to do it but I haven't got time for CUDA. I've been
> using boost.python, for
got a rather weird one - os x 10.5.2 sage 3.1.1 (binary build) I am
trying to build boost (python) for this version on os x - so I can get
pycuda going against the OS X 2.0 cuda.
well the python (python-sage) seems not to handle the -c "command"
like regular python that is "import" fails with a s
Can someone please outline for me the process/thread structure of the
sage workbook server - given multiple connections (user sessions) and
multiple concurrent notebooks and the degree of scope sharing - I did
think that each notebook had its own python process but this is
mistaken - how is contex
On Jul 22, 11:18 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> On Jul 22, 2:55 pm, Simon Beaumont <[EMAIL PROTECTED]> wrote:
>
> Hi Simon,
>
> > I decided to have a play with the pycuda-0.90.2 kit for which I needed
> > boost_1_35_0
>
> Mhh, is 1.35.0 ma
I decided to have a play with the pycuda-0.90.2 kit for which I needed
boost_1_35_0 - the main caveat is to make sure boost is using the sage
python include, lib and executable rather than any system installed
python. Similarly configure pycuda. My sage server runs as user sage -
so I had to run t
I am just about to embark on integrating come CUDA libraries into
sage. I was not sure of the best route to go - I am considering the
pycuda libraries as a starting point - this a pure kernel approach - I
but would also like to get the CUDA blas and fft libraries integrated.
(I think cuda-python)
Thanks Michael - that's a very good heads up - I'll take some time to
digest the issues and get working on an approach that makes sense for
the widest community - we want a well supported capability with a
future.
It is my opinion (in spite of current 32bit floats - though I think
the Tesla h/
25 matches
Mail list logo
