On May 6, 11:45 am, Francois Bissey
wrote:
> > On May 5, 5:44 pm, Francois Bissey
>
> > wrote:
> > > > On May 5, 6:35 am, Francois Bissey
>
> > > > wrote:
> > > > > > On May 4, 8:43 pm, Francois Bissey
> > > > > >
>
> > > > > > wrote:
> > > > > > > > same problem if I try building a standalon
> On May 5, 5:44 pm, Francois Bissey
>
> wrote:
> > > On May 5, 6:35 am, Francois Bissey
> > >
> > > wrote:
> > > > > On May 4, 8:43 pm, Francois Bissey
> > > > >
> > > > >
> > > > > wrote:
> > > > > > > same problem if I try building a standalone ecl, and if I use
> > > > > > > gcc 4.0.1, t
On May 5, 5:44 pm, Francois Bissey
wrote:
> > On May 5, 6:35 am, Francois Bissey
>
> > wrote:
> > > > On May 4, 8:43 pm, Francois Bissey
>
> > > > wrote:
> > > > > > same problem if I try building a standalone ecl, and if I use gcc
> > > > > > 4.0.1, too.
> > > > > > So this looks like the co
Looking at the source for attached_files(), I don't see how removing
elements from the list it returns could detach the files. It looks
like you can detach files manually by deleting from the
sage.misc.preparser.attached dictionary, but there is a function
`detach` that does the job (as foreshadow
On 5/5/11 4:42 PM, Dr. David Kirkby wrote:
On 05/ 5/11 03:06 PM, Jeroen Demeyer wrote:
Hi all,
I recently adapted the merge scripts to deal with spkg's in a new way.
Further ideas, suggestions, complaints are welcome.
Jeroen.
I've often wondered if it would be possible to safely remove th
On 5/5/11 5:02 PM, Francois Bissey wrote:
I would add on top of that for consideration that SPKG.txt often contains
more info than what you would find in a normal changelog. It often has
special instructions about the package, it is much more info than just a
changelog.
Yes, and +1 for keeping
Hi,
I often use matplotlib directly (for various reasons) in sage.
Unfortunately, a common error that crops up is matplotlib's pdf backend has
difficulty with Sage's wrapped integer and float representations.
i.e.
sage: import pylab as pl
pl.plot([1,2,3]sage: pl.plot([1,2,3], linewidth=3.5)
[]
On 5 May 2011 23:02, Francois Bissey wrote:
>> I suppose for my spkg workflow (mostly Cython) the new spkg doesn't
>> usually involve anything more than swapping out the sources and
>> perhaps adding/removing a patch. Adding an SPKG.txt entry is entirely
>> redundant with the hg commit (if one is
On Thu, May 5, 2011 at 3:02 PM, Francois Bissey
wrote:
>> On Thu, May 5, 2011 at 1:34 PM, Jason Grout
> wrote:
>> > On 5/5/11 3:29 PM, Jeroen Demeyer wrote:
>> >> On 2011-05-05 20:20, Dr. David Kirkby wrote:
>> >>> I like SPKG.txt. Personally I would have called the file "ChangeLog"
>> >>> in
>>
> On Thu, May 5, 2011 at 1:34 PM, Jason Grout
wrote:
> > On 5/5/11 3:29 PM, Jeroen Demeyer wrote:
> >> On 2011-05-05 20:20, Dr. David Kirkby wrote:
> >>> I like SPKG.txt. Personally I would have called the file "ChangeLog" in
> >>> common with just about every other software project, but SPKG.txt
On 05/ 5/11 03:06 PM, Jeroen Demeyer wrote:
Hi all,
I recently adapted the merge scripts to deal with spkg's in a new way.
Further ideas, suggestions, complaints are welcome.
Jeroen.
I've often wondered if it would be possible to safely remove the write
permissions from the "src" director
On May 5, 2:04 pm, Nils Bruin wrote:
> I would guess they should be methods on
>
> sage.modules.fg_pid.fgp_module.FGP_Module_class
I think so.
Without time to experiment and refresh my memory from many months ago
- can you not just use the intersection method that already exists,
but with a pair
Oh shoot that's a really silly implementation of intersection. One
should of course just do
def intersect_submodules(M,S1,S2):
F1=span([b.lift() for b in S1.gens()])
F2=span([b.lift() for b in S2.gens()])
M.submodule([M(b) for b in F1.intersection(F2).gens()])
--
To post to this grou
On May 5, 10:21 am, Volker Braun wrote:
> Thats a bug. Its tricky because it involves homs from a FreeModule to a
> FGP_Module. If you stay within FGP_Modules then it works:
Great! That has almost everything on it that I need. Intersection and
sum of submodules don't seem to exist yet, though. Sh
On Thu, May 5, 2011 at 1:34 PM, Jason Grout wrote:
> On 5/5/11 3:29 PM, Jeroen Demeyer wrote:
>>
>> On 2011-05-05 20:20, Dr. David Kirkby wrote:
>>>
>>> I like SPKG.txt. Personally I would have called the file "ChangeLog" in
>>> common with just about every other software project, but SPKG.txt doe
On 5/5/11 3:29 PM, Jeroen Demeyer wrote:
On 2011-05-05 20:20, Dr. David Kirkby wrote:
I like SPKG.txt. Personally I would have called the file "ChangeLog" in
common with just about every other software project, but SPKG.txt does.
I think that summerises the changes much better than what "hg log"
On 2011-05-05 20:20, Dr. David Kirkby wrote:
> I like SPKG.txt. Personally I would have called the file "ChangeLog" in
> common with just about every other software project, but SPKG.txt does.
> I think that summerises the changes much better than what "hg log" does,
> where often there are numerou
On 5/5/11 3:21 PM, Jeroen Demeyer wrote:
On 2011-05-05 22:17, Jason Grout wrote:
Does anyone have a copy of the sage-forker code that Jeroen wrote a
while ago:
http://boxen.math.washington.edu/home/jdemeyer/src/forker/
Perfect; thanks!
Jason
--
To post to this group, send an email to sag
On 2011-05-05 22:17, Jason Grout wrote:
> Does anyone have a copy of the sage-forker code that Jeroen wrote a
> while ago:
http://boxen.math.washington.edu/home/jdemeyer/src/forker/
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an ema
On May 5, 7:23 am, Rob Beezer wrote:
> On the ticket, I've posted instructions for installing all the Python
> bits necessary for a plain Ubuntu distribution to have RunSnakeRun
> installed system-wide.
Never mind, there are slightly better instructions in the docstring.
--
To post to this gr
Does anyone have a copy of the sage-forker code that Jeroen wrote a
while ago:
http://groups.google.com/group/sage-devel/browse_thread/thread/eb8748e2fff0b73d?fwc=1
I can't seem to find it anywhere anymore.
Thanks,
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
On Thu, May 5, 2011 at 1:07 PM, Jason Grout wrote:
> On 5/5/11 2:54 PM, Robert Bradshaw wrote:
>>
>> manually keeping track of known failures is cumbersome and more likely
>> to let in new failures in the files "known to fail."
>
> One possibility is to use nose for tests like these, and put these
On 5/5/11 2:54 PM, Robert Bradshaw wrote:
manually keeping track of known failures is cumbersome and more likely
to let in new failures in the files "known to fail."
One possibility is to use nose for tests like these, and put these
"known to fail" tests in a separate file. Numpy/scipy base t
On Tue, May 3, 2011 at 12:09 AM, Dr. David Kirkby
wrote:
> A discussion started on sage-release, which I think is best on sage-devel.
>
> I believe this ticket
>
> http://trac.sagemath.org/sage_trac/ticket/11277
>
> is a very bad idea, as it disables a doctest which is known to fail on one
> platf
On 05/ 5/11 04:47 PM, kcrisman wrote:
Further ideas, suggestions, complaints are welcome.
I agree with the sentiment expressed elsewhere in previous threads that
the changelog should be in the hg log, and not necessarily in the
SPKG.txt file. In other words, I feel like the changes you made
On May 5, 9:52 am, Nils Bruin wrote:
> Thanks! I don't mind the language particularly, I'm just looking for a
> convenient wrapper of the functionality.
Then you'll want to stick with FGP_Module because I'm not adding
anything, just specializing with students of introductory group theory
in mind
Thats a bug. Its tricky because it involves homs from a FreeModule to a
FGP_Module. If you stay within FGP_Modules then it works:
sage: FGP_Z3 = Z3 / Z3.span([])
Finitely generated module V/W over Integer Ring with invariants (0, 0, 0)
sage: FGP_Z3.hom([M(b) for b in Z3.gens()])
Morphism from mod
On May 5, 3:23 am, Volker Braun wrote:
> I found the FGP_Module to be the most useful implementation of finitely
> generated Z-modules:
Thank you! That does indeed look promising. For free modules it seems
it does everything I need:
Z3=ZZ^3
K=Z3.span([Z3.0+Z3.1,Z3.0-Z3.1])
KtoZ3=K.hom([Z3(b) for
Hi Rob,
Thanks! I don't mind the language particularly, I'm just looking for a
convenient wrapper of the functionality. So calling the things abelian
groups or Z-modules is fine with me either way. Your patches don't
seem to mention "hom" at all, so am I right in assuming they are not
fixing any s
I'll see what I can do. :)
I'm using Maple's implementation of Puiseux series to debug my code. A while
ago my advisor wrote this implementation and has retained the rights to
distributing his code. However, Maple is a rather cryptic language to me so
at the moment I'm only checking output. :)
On Thu, May 5, 2011 at 8:47 AM, kcrisman wrote:
>
>> > Further ideas, suggestions, complaints are welcome.
>>
>> I agree with the sentiment expressed elsewhere in previous threads that
>> the changelog should be in the hg log, and not necessarily in the
>> SPKG.txt file. In other words, I feel li
> > Further ideas, suggestions, complaints are welcome.
>
> I agree with the sentiment expressed elsewhere in previous threads that
> the changelog should be in the hg log, and not necessarily in the
> SPKG.txt file. In other words, I feel like the changes you made should
> be reversed---the hg l
On #5, I stated both in the ticket description and in a comment
and in the form field "Dependencies" that it depends on #9976 and
#11298. Similarly, I indicated on #11298 that it depends on #9976. But
the patchbot keeps ignoring #9976 when it applies the patches.
Could it be that the patchbot
On May 4, 7:04 am, "Nicolas M. Thiery"
wrote:
> - An interface to the graphical profiler runsnake:
Thanks, Nicolas, this is very nice.
On the ticket, I've posted instructions for installing all the Python
bits necessary for a plain Ubuntu distribution to have RunSnakeRun
installed system-wide.
On May 5, 5:59 am, Burcin Erocal wrote:
> Some business cards with the web site and the address of a responsive
> notebook server would also be good.
Marshall Hampton was in charge of business cards.
> I will be at Sage Days 31
> right before the industrial applications event. There is no need t
On 5/5/11 9:06 AM, Jeroen Demeyer wrote:
Hi all,
I recently adapted the merge scripts to deal with spkg's in a new way.
Most importantly, changes inside a spkg are automatically *committed*
before merging the spkg into Sage (the spkg is extracted, hg commit is
done using a commit message coming
Hi There,
Ticket #3089 says:
removing an attached file doesn't work
The help page given by attach? claims:
Type attached_files() for a list of all currently attached files.
You can remove files from this list to stop them from being watched.
In fact, this has no effect w
Hi all,
I recently adapted the merge scripts to deal with spkg's in a new way.
Most importantly, changes inside a spkg are automatically *committed*
before merging the spkg into Sage (the spkg is extracted, hg commit is
done using a commit message coming from SPKG.txt, an hg tag is added and
the
Hi!
Working on #11298, the patchbot claims that my patch fails to apply.
But it seems to me that the patchbot is in fact considering a patch
from a different ticket, accidentally from me as well.
Details:
#9976 (which is merged in some alpha version) is a dependency for
#11298. In my patch queue,
Hi Rob,
On Thu, 5 May 2011 05:49:20 -0700 (PDT)
Rob Beezer wrote:
> On May 5, 1:46 am, Burcin Erocal wrote:
> > Any volunteers to help out at the booth and prepare publicity
> > materials?
>
> I could likely easily do another run of Sage stickers, have them
> shipped to you, and handle all the
On May 5, 1:46 am, Burcin Erocal wrote:
> Any volunteers to help out at the booth and prepare publicity materials?
I could likely easily do another run of Sage stickers, have them
shipped to you, and handle all the finances here on the Pacific Coast.
Contact me off-list if the Sage Foundation co
Hi Nils,
There is a working patch for finitely generated abelian groups, which
builds on the ZZ-modules routines and some similar code for finite
groups.
http://trac.sagemath.org/sage_trac/ticket/9773
Patch needs docs, and a couple of fixups, but there are some working
examples (like multiplicat
There has been some discussion in the past on this. And offcourse
ideally everything would build with SAGE_CHECK=yes but a lot of the
failures are not even due to sage so we are less strict on these then
the sage doctests. I also remember that some people (including me)
wished that a failure SAGE_C
I found the FGP_Module to be the most useful implementation of finitely
generated Z-modules:
sage: M = ZZ^2
sage: Q = M / M.span([ 2*M.gen(0) ]); Q
Finitely generated module V/W over Integer Ring with invariants (2, 0)
sage: type(Q)
sage: [ q.additive_order() for q in Q.gens() ]
[2, +Infinity]
On 5 mai, 12:01, Jeroen Demeyer wrote:
> This is #11278 (needs_review).
Thanks for pointing that out, I'll have a look at it.
--
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
On May 5, 7:04 am, Thierry Dumont wrote:
> If it is possible, I propose (me) to make a package of ODE/DAE
> intergrators: ther is a lot of methods which would be nice in Sage like
> Implicit R-K methods, Symplectic methods and so on...
I naively volunteer to help on setting a package with updat
On 2011-05-05 11:37, Francois Bissey wrote:
>> ld: for architecture ppc
>> ld: ../kernel/libkernel.a(matpol.o) has external relocation entries in
>> non-writable section (__TEXT,__text) for symbols:
>> restFP
>> saveFP
>> libtool: internal link edit command failed
>> make[3]: *** [libsingular] Erro
On May 4, 6:48 am, Joris Vankerschaver
wrote:
> I wrote a C++ wrapper around DASSL some time ago,
I've being tracking/learning more about available codes.
I was amazed to learn that there is a huge zoo of many different
solvers.
I gathered some links and I am trying to tabulate this informatio
On May 4, 1:48 am, David Joyner wrote:
> It seems there is a python interface to
> daetoolshttp://daetools.sourceforge.net/w/index.php/PyDAE_user_guide
PyDAE seems *very* interesting.
It also quite a large beast. It sweeps from Blas, SUNDIALS IDAS (!),
Umfpack, MUMPS, Trilinos...
Maybe it makes
I do not have the admin password on that computer currently, so I
fear I won't be able to install a newer version of XCode.
IIRC I built Sage 4.6.something on the same computer without (oo
much ?) trouble when I ran some tests for pynac.
You can find the full log at
http://perso.telecom-paristech
> On May 5, 6:35 am, Francois Bissey
>
> wrote:
> > > On May 4, 8:43 pm, Francois Bissey
> > >
> > > wrote:
> > > > > same problem if I try building a standalone ecl, and if I use gcc
> > > > > 4.0.1, too.
> > > > > So this looks like the combination of OSX 10.5 and PPC that is not
> > > > > w
> I get the followig failure while building Sage:
> g++ -O2 -g -fPIC -pipe -fno-implicit-templates -I. -I../kernel -I/
> Users/Shared/sage/sage-4.7.rc1/local/include -I/Users/Shared/sage/
> sage-4.7.rc1/local/include -I/Users/Shared/sage/sage-4.7.rc1/local/
> include -DNDEBUG -DOM_NDEBUG -DppcMac_
On May 5, 6:13 am, Nils Bruin wrote:
> Does anybody know the current state-of-the-art in sage to compute with
> finitely generated Z-modules (i.e., finitely generated abelian
> groups)? The operations I would be looking for are
> - sums, intersections and quotients of/by submodules
> - homomorph
Ooh didn't know bitbucket can do that :-)
https://bitbucket.org/vbraun/compilerwrapper/get/compilerwrapper-1.1.tar.bz2
--
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 option
Hi,
there will be an industrial applications of computer algebra meeting in
Kaiserslautern on June 21-22:
http://www.computeralgebra.de/IndustrialApplications2011/index.html
This is the event that we were notified about in Sep 2009:
http://groups.google.com/group/sage-devel/t/a8bfb79c1a30e621
I get the followig failure while building Sage:
g++ -O2 -g -fPIC -pipe -fno-implicit-templates -I. -I../kernel -I/
Users/Shared/sage/sage-4.7.rc1/local/include -I/Users/Shared/sage/
sage-4.7.rc1/local/include -I/Users/Shared/sage/sage-4.7.rc1/local/
include -DNDEBUG -DOM_NDEBUG -DppcMac_darwin -DH
On Thu, May 5, 2011 at 12:49 AM, dagss wrote:
>
> On Thursday, May 5, 2011 3:42:59 AM UTC+2, Ondrej Certik wrote:
>>
>> On Wed, May 4, 2011 at 12:51 AM, dagss wrote:
>> > I don't really have a say in this, but I've given this a lot of thought
>> > since I decided to drop Sage as my scientific Pyt
Hi Volker,
On Wed, 4 May 2011 14:38:44 -0700 (PDT)
Volker Braun wrote:
> I finished compilerwrapper-1.1 which now allows you to transform the
> wrapper as well as the wrapped gcc binary names by means of configure
> options. For example,
>
> ./configure --with-gcc-transform-name='s/^/x86_64-/'
On Thursday, May 5, 2011 3:42:59 AM UTC+2, Ondrej Certik wrote:
>
> On Wed, May 4, 2011 at 12:51 AM, dagss wrote:
> > I don't really have a say in this, but I've given this a lot of thought
> > since I decided to drop Sage as my scientific Python distribution a year
> ago
> > and have been searc
59 matches
Mail list logo
