On Apr 14, 10:08 am, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
Hello sage-devel,
I wrote a program called ptyrun, which runs an arbitrary program in a
pseudo-tty. I personally found it useful, so maybe somebody else will
find it useful also.
I personally found this useful in the
On Apr 7, 5:04 am, Rob Beezer goo...@beezer.cotse.net wrote:
... is the determinant? Does this make sense to anyone? Am I missing
something? I can't think of a reason why, and the documentation
(sage.matrix.matrix2.Matrix._abs_) does not shed any extra light on
the reason.
This came up on
On Apr 7, 4:15 am, kcrisman kcris...@gmail.com wrote:
For many people, this would make Sage no longer free - it would
effectively cost $5 and none of that money goes to Sage.
Well, you could still download a binary. They aren't requiring that
people give them money from things compiled
No I still have to get administrative rights so didn't even had the
canche on working on this.
On Apr 3, 2:26 am, Keshav Kini keshav.k...@gmail.com wrote:
Yup, this is a great idea. You were working on this during sage days
29, right? Any progress?
-Keshav
On Mar 24, 3:14 am, koffie
Since we have a highly configurable bug tracking system, why not add
some custom fields?
http://trac.edgewall.org/wiki/TracTicketsCustomFields
On Mar 22, 2:51 pm, Jason Grout jason-s...@creativetrax.com wrote:
On 3/22/11 4:28 PM, Jeroen Demeyer wrote:
I would obviously prefer that the
On Mar 17, 4:34 am, Simon King simon.k...@uni-jena.de wrote:
Hi!
On 17 Mrz., 12:16, koffie m.derickx.stud...@gmail.com wrote:
If people think it's a good idea we can add another status to the sage
trac (it's a really small change in the configuration file). It's also
possible
On Mar 18, 10:20 am, Simon King simon.k...@uni-jena.de wrote:
On 18 Mrz., 15:32, koffie m.derickx.stud...@gmail.com wrote:
The only discussion I know of
ishttp://groups.google.com/group/sage-devel/browse_thread/thread/351e2a...
where I suggested the same thing. It got a +1
If people think it's a good idea we can add another status to the sage
trac (it's a really small change in the configuration file). It's also
possible to restrict the ability to close tickets to certain groups in
trac so that regular people cannot close tickets.
Let me know what you think of
And of course you should not close it but you should let the release
manager do it.
On Mar 3, 1:57 am, John Cremona john.crem...@gmail.com wrote:
Yes, close the old one but cross-reference each ticket to the other.
John
On Wed, Mar 2, 2011 at 4:45 PM, Dr. David Kirkby
I don't have any problems with people getting paid for sage related
stuff (selling service contract, implementing features, fixing bugs)
as long as the output of it is getting back to the community. I mean,
someone working fulltime on sage related stuf, and improving sage
along the way, also
That sounds very interesting, to bad I'm not a US Citizen.
--
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
On Feb 23, 12:47 pm, Niles nil...@gmail.com wrote:
A couple of other threads have mentioned ways to possibly shorten the
startup time for Sage. This made me wonder: What is a good way to
tell *what* is making Sage take so long to start up? Are certain
sections of the library taking the
First of all, sorry Simon to have misread you :(.
To awnser your question. I guess your algorithm makes sense when you
do it with fractions in the reduced form. I will do it only for prime
powers since the general case will follow from this.
Suppose we have two prime powers p^a and p^b with a,b
By the way, notice that in http://trac.sagemath.org/sage_trac/ticket/3214
they also added a function content which does the old gcd behaviour
(i.e. similar to what simon describes).
sage: (1/4).content(1/6)
1/12
On Feb 11, 12:15 pm, koffie m.derickx.stud...@gmail.com wrote:
First of all, sorry
So bruno and simon agree that lcm(1/4,1/6) = 1/2 (lcm(numerators)/
gcd(denominators)) is the most logical. It also seems to satisfy dough
wanted relation up to units. I like it because it makes sense if you
think in terms of fractional ideals. And I suggest we switch to that
convention.
When
Hej Doug,
Nice list of bugs. I was wondering, might you be interested in
becoming a sage developer to? It's really not that hard, and it sounds
to me that if you knew how to edit the source code of sage you would
be able to fix some of these bugs yourself, and become one of the
volunteers who
On Feb 6, 6:49 am, Rob Beezer goo...@beezer.cotse.net wrote:
William, Volker,
Thanks for the replies. Kernels for the rationals go to IML and for
number fields they go to PARI. Does either of those rely on linbox?
Here's the requested output - three different number fields are
evident.
My recent work has been in to speed up a lot of modular symbols
related code, especially the linear algebra it depends on. Not
everything is up to standars to get it into sage but should be in the
near future.
I'm also interested in the integrality question, and my own code is
pretty good at
A real programmer could also help with spreading his knowledge of good
coding practices and software design patterns in the sage community.
By reading this mailing list I sometimes get the feeling we have
enough smart mathematicians, but not enough battle field tested
diehard programmers.
On Jan
On Jan 15, 8:34 pm, Rob Beezer goo...@beezer.cotse.net wrote:
On Jan 15, 9:23 am, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
Whether every range() should be changed to xrange(): I can't comment on
that.
In Python 3, range() will return an iterator, which is the current
behavior of
Dear All,
When optimizing some sage code. I found in multiple places the same
reason for some stupid slowdown. Namely using: for i in
range(huge_number): in several places. Instead of manually changing
each of these occurances I thought it was easier to just write a bash
oneliner which does this
Maybe slightly related is that sage is already leaking memory at
startup time. See http://trac.sagemath.org/sage_trac/ticket/10570 for
more info.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Sage uses symbolic ring fot this. I guess you should just look how the
following is implemented and copy that disign:
sage: var('x')
x
sage: f=sin(x^2)
sage: f(x=2)
sin(4)
sage: f
sin(x^2)
sage: f.derivative()(x=2)
4*cos(4)
sage: f.derivative(7)
-128*x^7*cos(x^2) - 1344*x^5*sin(x^2) +
By the way your nummerical approximation will finally get called when
you do something like:
sage: f(4).numerical_approx()
-0.287903316665065
or use it's shorter alias:
sage: f(4).n()
-0.287903316665065
By the way, the sinus was a bad example since that uses ginac as a
backend. You should look
read this william, this also undo's the major slowdown of
the modular symbols initialization code we discussed about earlier.
On Jan 7, 6:31 pm, koffie m.derickx.stud...@gmail.com wrote:
I tried to speed up scalar multiplication of sparse matrices. I did
this using _lmul_ as explained
inhttp
1. What release should be the target against which a patch should be
checked before it is uploaded to the Trac for review? Is it the latest
publicly released version OR one of the release candidates?
Most of the time the code doesn't change to much between two releases,
you just got
I tried to speed up scalar multiplication of sparse matrices. I did
this using _lmul_ as explained in
http://www.sagemath.org/doc/reference/coercion.html
I alredy made a patch giving sparse matrix objects a function _lmul_
but somehow it doesn't seem to get called.
See
Hej All,
I just looked at the patch bot reports And a lot of patches seem to
give the same error log when applied.
For example: compare the bottom of
http://sage.math.washington.edu:21100/log/10515/linux/ubuntu/hardy/sage.math.washington.edu/2010-12-22%2006:40:04%20-0800?short
and
I agree with Robert.
And from an enduser point of view I think that being one large bundle
is actually on of the key strength's of sage. I have had some open
source programs which I didn't start using because after having to
hand compiling the third dependancy I thought it wasn't worth the
Maybe someone who cares enough should write a SEP=Sage Enhancement
Proposal about how to make a more modular sage without having
sacrificing on the user experience and stability of sage. And see how
many people are willing to put the time and effort needed into it.
On Dec 23, 11:50 am, koffie
I seem not to be able to edit the wiki so on wiki it still sais in
multiple places: Fully supported - Sage is ALWAYS check on ALL these
platforms BEFORE a release is made
Ofcourse it should be checked instead of check to make it proper
English.
On Nov 10, 6:29 am, Dr. David Kirkby
locate it in the pynac spkg but
it's not there either (I wasn't sure if search_def also looked in the
spkg files), and it's also not to be found in the GiNaC reference.
Maarten Derickx
On Nov 2, 8:26 pm, Mike Hansen mhan...@gmail.com wrote:
On Tue, Nov 2, 2010 at 12:15 PM, koffie m.derickx.stud
By the way, http://pynac.sagemath.org/ seems outdated since
pynac-0.2.1.spkg already ships with sage while the version for
download there is pynac-0.1.11.spkg.
On Nov 3, 12:34 pm, koffie m.derickx.stud...@gmail.com wrote:
Thanks, that sort of makes things a bit clearer. So most of the magic
sage depends?
Kind regards,
Maarten Derickx
On Nov 3, 7:08 pm, Mike Hansen mhan...@gmail.com wrote:
On Wed, Nov 3, 2010 at 4:34 AM, koffie m.derickx.stud...@gmail.com wrote:
search_def(g_hold2_wrapper) doesn't return anything so it's not in
sage self. I also used grep to maybe locate
Hej All,
I was trying to do some work on:
http://trac.sagemath.org/sage_trac/ticket/9129
The problem seems to be in the .sqrt functiontion for symbolic ring
elements. The source code is:
return new_Expression_from_GEx(self._parent,
g_hold2_wrapper(g_power_construct, self._gobj, g_ex1_2,
Are you testing all doctest (ie also the long ones) since it could be
that some long doctests have been tagged as such in an update.
Then there is ofcourse still the possibility that there was a merge
off a ticket which improves general sage performance.
The recently proposed regresion testing
This would be a good addition to the sage developement process
indeed.
Before going trough all the work of implementing this stuff, it might
be wise to first look what's already out there. It might prevent you
from doing double work, or give inspiration on how to do it. There
seems to be a
And don't forget the sage-flame list ;)
http://groups.google.com/group/sage-flame
On Oct 6, 5:00 am, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi Mitesh,
On Wed, Oct 6, 2010 at 10:29 AM, Mitesh Patel qed...@gmail.com wrote:
Have I missed any?
The group debian-sage [1] seems to be reviving
, koffie m.derickx.stud...@gmail.com wrote:
David: you are 100% right about the garbage collector.
The following example sort of shows what is going on:
from time import time
import gc
K = Qp(13, 10)
M = [K.random_element() for j in range(200)]
save(M,thing.sobj)
L
David: you are 100% right about the garbage collector.
The following example sort of shows what is going on:
from time import time
import gc
K = Qp(13, 10)
M = [K.random_element() for j in range(200)]
save(M,thing.sobj)
L = []
for i in range(4000):
L.append(load(thing.sobj))
for i in
Thanks for the quick response. I'd say it's ready to go with the
additional changes.
Kind regards,
Maarten Derickx
On Sep 13, 11:25 am, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi koffie,
On Mon, Sep 13, 2010 at 3:45 PM, koffie m.derickx.stud...@gmail.com wrote:
I definitely like the new
I definitely like the new compatible lay-out.
When I looked at
http://trac.sagemath.org/sage_trac/attachment/ticket/9850/walkthrough.png
my eye spotted some details which leave room for some more
improvement.
1. The grey background of the search button (with the tekst GO on
it) should be a
I really like the idea of switching to multiple actively managed
maintained sage versions which is suggested somewhere in this thread.
I just happened to have suggested it also in a response to Williams
blog http://389a.blogspot.com/2010/08/computational-projects-part-1.html.
Where he discusses
, when new attributes are added to
RingElement or FieldElement, it is via inheritance added to
LazyFieldElement, except if it is one of those implemented over the
reals.
Cheers,
Johan
On Aug 10, 12:40 pm, koffie m.derickx.stud...@gmail.com wrote:
Hej Robert,
Your other implementation
Hej Robert,
Your other implementation sounds interesting to. I would really love
to see a lazy way which does work well together with class
inheretance. I don't really know enough of the detailed working of
python/cython to implement what you suggest. Are you willing to write
a patch for this?
If
Hej All,
I started developing for sage not so long ago and I wonder if there
are some good coding practices / conventions for dealing with global
functions and attributes which have the same name and also do the same
thing. An example of such a global function / atribute combination:
sage:
Hej All,
I was doing some work on http://trac.sagemath.org/sage_trac/ticket/9094.
In trying to do it the nice way (i.e. avoiding unnessery double code
by putting the code in a common base class) I ran into trouble. The
core of all problems seems to be with real_lazy. What goes wrong is
that they
Hej David,
If you think that RAM exaustion is going to cause problems, why don't
you also add the recording of the memory useage in the doctesting (I
wouldn't now how to exactly do this but I guess you could use the
output of command line utilities such as top, vmstat/vm_stat or free).
If this
Thanks, that seemed to do the trick. Since the goal was to get some
working code into sage and not to make it blazingly fast I'll just use
this solution.
Kind regards,
Maarten Derickx
On Jul 17, 7:01 am, Carl Witty carl.wi...@gmail.com wrote:
On Fri, Jul 16, 2010 at 8:21 PM, koffie
Hi All,
I'm just starting with sage developement and after my first patch I
think it's time to use something more sophisticated then a plain tekst
editor to do the coding for sage. I started this thread so people can
share which IDE's they are using and what they like about it. The
following is a
Dear All,
I was writing some code for sage and ran into trouble. The code was
working just fine when it was a standalone function. Then I tried to
add it to a pyx file (sage/rings/fraction_field_element.pyx to be
precise) and ran into trouble. Somewhere in the code I would like to
use the command
+1 on craig, especially the 3th point.
ow I forgot to mention before, I also think that a massive
reorganization would be a bad thing to do since this would be big load
of work, and there are much better things that could get done in that
time. But motivating people to have the newly added stuff
Are there some general guidelines on how to use the namespaces in
sage. Like: which function's should be accesible from which namespace
(global v.s. local and maybe some hierachical structure in the local
namespace).
I think some guidelines on this would improve the userfriendliness of
sage a big
Srry, I think I got a bit lost from the core of the problem with some
people talking about Integer(float(1.5)) an Integer(RR('1.0')).
Making things like Integer(1.0) work for is ok to me.
My previous reaction was probably a bit to worried reaction. I was
woried about implicit functions call's
I have to agree with William that something like Integer(float(1))
really should not work, this is because floats are really ugly and
unpredictable things which are prone to a lot of errors, and even
implementing Integer(float(X)) to work only if X is just happens to be
an integer wil not help to
As we are now bussy discussing copyright and licence issues. (How) is
the google CLA licenced?
I.e. is it legal to make an almost litteral copy of it and use it for
sage purposes ;)
Maarten
--~--~-~--~~~---~--~~
To post to this group, send email to
William asked me to post the following on the sage-devel list. Could
someone here help me get started?
Kind Regards
Some help in where to start would also be apreciated (this is
the first
open
source developement project that I'm interested in joining so
I read
some
I guess the current implementation was deemed as temporary and to be
refactored; so not that useful to document right away at the user
level. Of course, the final implementation will need extensive
documentation. I actually expect the documentation to take out most of
the code and
I uploaded it. You can find it now at
http://www.math.leidenuniv.nl/~mderickx/Install_Sage.zip.
Kind Regards
On Nov 10, 1:27 am, koffie [EMAIL PROTECTED] wrote:
So, after getting us all exited could you describe what you did?
To describe it a bit more precise, it is just a small work flow
sage: C = VectorSpaces(GF(5))
sage: C
Category of vector spaces over Finite Field of size 5
sage: W = (ZZ^3).span([[1,2,3],[4,5,3]])
sage: W
Free module of degree 3 and rank 2 over Integer Ring
Echelon basis matrix:
[1 2 3]
[0 3 9]
sage: C(W)
Vector space of degree 3 and dimension 2
So, after getting us all exited could you describe what you did?
To describe it a bit more precise, it is just a small work flow, that
on execution first askes you if you want to copy the sage folder to
you application folder. When you say yes it does so by running cp -R /
Volumes/sage-*/sage
61 matches
Mail list logo
