>
>
> >> integrate it with our other forms of user support? I would suggest
> echoing
> >> each bug report to sage-support, and CCing the thread to any email
> address
> >> provided on the form. What do you think?
>
> echoing every bug report is not a good idea, as quite a bit of it
> contai
On 1/25/13 9:38 PM, kcrisman wrote:
indeed. Also note that lots of it is sagenb-specific. I cc this to
Or even sagenb.org-specific. I lost count of how many people asked about
the disabled public worksheets... not that I counted very long.
Pull requests are *definitely* welcome for tha
On 2013-01-26, Dima Pasechnik wrote:
> On 2011-10-18, Keshav Kini wrote:
>> Is anyone reading
>> https://spreadsheets.google.com/pub?key=pCwvGVwSMxTzT6E2xNdo5fA ? If you
>> don't know what it is (as I didn't until a few minutes ago), it's where
>> users' bug reports are sent from the form they
>
>
> indeed. Also note that lots of it is sagenb-specific. I cc this to
>
>
>
Or even sagenb.org-specific. I lost count of how many people asked about
the disabled public worksheets... not that I counted very long.
--
You received this message because you are subscribed to the Google Grou
On 2011-10-18, Keshav Kini wrote:
> Is anyone reading
> https://spreadsheets.google.com/pub?key=pCwvGVwSMxTzT6E2xNdo5fA ? If you
> don't know what it is (as I didn't until a few minutes ago), it's where
> users' bug reports are sent from the form they see when they click "Report a
> Problem" i
On Friday, January 25, 2013 9:06:48 PM UTC-5, kcrisman wrote:
>
>
>
> On Friday, January 25, 2013 9:05:22 PM UTC-5, kcrisman wrote:
>>
>>
>>
>> On Tuesday, October 18, 2011 8:07:01 AM UTC-4, kcrisman wrote:
>>>
>>>
>>>
>>> On Oct 18, 4:28 am, Jason Grout wrote:
>>> > On 10/18/11 12:30 AM, Kesha
Well my personal take on it is that the ATLAS build had a small issue. In the
context of
sage-on-gentoo i have seen particular version of Atlas or other cblas break
only one doctest
as an indication that there was a fault or a difference with the atlas sage
usually ship.
Early version of atlas 3
On Friday, January 25, 2013 9:05:22 PM UTC-5, kcrisman wrote:
>
>
>
> On Tuesday, October 18, 2011 8:07:01 AM UTC-4, kcrisman wrote:
>>
>>
>>
>> On Oct 18, 4:28 am, Jason Grout wrote:
>> > On 10/18/11 12:30 AM, Keshav Kini wrote:
>> >
>> > > I would suggest echoing each bug report to sage-sup
On Tuesday, October 18, 2011 8:07:01 AM UTC-4, kcrisman wrote:
>
>
>
> On Oct 18, 4:28 am, Jason Grout wrote:
> > On 10/18/11 12:30 AM, Keshav Kini wrote:
> >
> > > I would suggest echoing each bug report to sage-support, and CCing the
> > > thread to any email address provided on the form.
On 2013-01-25 20:17, leif wrote:
> Jeroen Demeyer wrote:
>> I tested sage-5.7.beta0 with the latest GCC-4.8 (under development) with
>> SAGE_CHECK=yes, builds fine and all doctests pass.
>
> Does this include building R with '-O3'? ;-)
Yes, even with SAGE_CHECK=yes.
--
You received this message
On 2013-01-25, Hari Krishna wrote:
> --Apple-Mail-8154B97B-50BA-401C-AF26-245F7648E3AF Content-Type:
> text/plain; charset=ISO-8859-1
>
> Greetings folks,
>
> I'm new to research in math, having taken up the path of research in
> august 2012. I began working on quantifier elimination and came up
>
I do not have any easy way to run that build. It certainly doesn't run on
my machine (12.10 x86). Is there a straightforward way to run it that I'm
unaware of?
Also, can you clarify for me: does this build-related error appear on lots
of machines (i.e. have other people encountered it), or onl
On 1/25/13 3:15 PM, Jason Grout wrote:
Can you please comment on it and offer advice?
Of course, I assume you've also asked Chris Brown, maintainer of qepcad b?
Thanks,
Jason
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe fro
On 1/25/13 2:16 PM, Hari Krishna wrote:
Greetings folks,
I'm new to research in math, having taken up the path of research in
august 2012. I began working on quantifier elimination and came up with
the following idea. Can you please comment on it and offer advice?
I'm looking to implement it fo
Greetings folks,
I'm new to research in math, having taken up the path of research in august
2012. I began working on quantifier elimination and came up with the following
idea. Can you please comment on it and offer advice?
I'm looking to implement it for SAGE in the long run, if it proves suc
kcrisman wrote:
On Friday, January 25, 2013 10:49:21 AM UTC-5, Jeroen Demeyer wrote:
On 2013-01-25 16:38, kcrisman wrote:
> Yes with SAGE_CHECK=yes
I actually don't think the value of SAGE_CHECK matters, as the failure
is in a quick test which is done anyway (even with SAGE_CH
Jeroen Demeyer wrote:
I tested sage-5.7.beta0 with the latest GCC-4.8 (under development) with
SAGE_CHECK=yes, builds fine and all doctests pass.
Does this include building R with '-O3'? ;-)
[For me, R keeps segfaulting while byte-compiling when built with FSF
GCC 4.6.y (IIRC, not that sure
On Friday, January 25, 2013 10:49:21 AM UTC-5, Jeroen Demeyer wrote:
>
> On 2013-01-25 16:38, kcrisman wrote:
> > Yes with SAGE_CHECK=yes
> I actually don't think the value of SAGE_CHECK matters, as the failure
> is in a quick test which is done anyway (even with SAGE_CHECK off).
>
That was
On 1/24/13 4:37 PM, Florent Hivert wrote:
Hi,
Is it possible to have nested roles? I'm thinking about something
like :article:arxiv:`...`, :article:doi:`...`, etc
That would make it easier to add new types of references, should the
need arise.
I'm pretty sure it's not.
Rest is kind
On Fri, Jan 25, 2013 at 05:57:24PM +0100, Florent Hivert wrote:
> On Fri, Jan 25, 2013 at 01:43:27AM -0800, Christian Stump wrote:
> > > +1
>
> This is #14011
>
> I'll upload a patch soon,
Done ! Please review.
Florent
--
You received this message because you are subscribed to the Google Gro
On Fri, Jan 25, 2013 at 01:43:27AM -0800, Christian Stump wrote:
> > +1
This is #14011
I'll upload a patch soon,
Cheers,
Florent
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
On 2013-01-25 16:38, kcrisman wrote:
> Yes with SAGE_CHECK=yes
I actually don't think the value of SAGE_CHECK matters, as the failure
is in a quick test which is done anyway (even with SAGE_CHECK off).
--
You received this message because you are subscribed to the Google Groups
"sage-devel" grou
On 2013-01-24, Jeroen Demeyer wrote:
> While testing for speed regressions due to #12313, I actually
> encountered a serious slowdown from sage-5.5 to sage-5.6:
>
> def test():
> for count in range(12):
> for n in [2..20]:
> for g in Gamma0(n).gamma_h_subgroups():
>
On Friday, January 25, 2013 6:32:35 AM UTC-5, David Joyner wrote:
>
> On Fri, Jan 25, 2013 at 6:23 AM, Jeroen Demeyer
> >
> wrote:
> > On 2013-01-25 12:21, David Joyner wrote:
> >> On Fri, Jan 25, 2013 at 6:10 AM, Jeroen Demeyer
> >> >
> wrote:
> >>> On 2013-01-25 12:02, David Joyner wrote
On 2013-01-25, Dima Pasechnik wrote:
> On 2013-01-25, Volker Braun wrote:
>> --=_Part_681_2503209.1359120527992
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> On Friday, January 25, 2013 1:11:15 PM UTC, Dima Pasechnik wrote:
>>
>>> If I read what Volker noticed right, in this code the
On 2013-01-25, Volker Braun wrote:
> --=_Part_681_2503209.1359120527992
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Friday, January 25, 2013 1:11:15 PM UTC, Dima Pasechnik wrote:
>
>> If I read what Volker noticed right, in this code the bulk of time is
>> spent computing the order
On Friday, January 25, 2013 1:11:15 PM UTC, Dima Pasechnik wrote:
> If I read what Volker noticed right, in this code the bulk of time is
> spent computing the order of a group of 2x2 matrices by converting it
> into a permutation group, via GAP. And the order of the group is never
> more than
On 2013-01-24, Jeroen Demeyer wrote:
> While testing for speed regressions due to #12313, I actually
> encountered a serious slowdown from sage-5.5 to sage-5.6:
>
> def test():
> for count in range(12):
> for n in [2..20]:
> for g in Gamma0(n).gamma_h_subgroups():
>
Hi,
I did take a look at the ticket.
I think it perfectly makes sense but I have a little problem with a part of the
implementation. Please see my review on trac.
Maybe someone could comment on this (or better even provide a patch?).
Stephan
On Thursday, 24 January 2013 18:53:34 UTC, Christia
I've reported this upstream at http://tracker.gap-system.org/issues/221
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+uns
Its just computing the order of a matrix group over integers mod 20 got
slower, I think:
┌───┐ GAP, Version 4.5.7 of 14-Dec-2012 (free software, GPL)
│ GAP │ http://www.gap-system.org
└───┘ Architecture: x86_64-unknown-linux-gnu-gcc-default64
Libs used: gmp
Loading the libra
On Friday, 25 January 2013 19:43:39 UTC+8, Volker Braun wrote:
>
> sage: %prun test()
>
> 6569139 function calls (6564056 primitive calls) in 36.792 seconds
>
>Ordered by: internal time
>
>ncalls tottime percall cumtime percall filename:lineno(function)
>116767 27.134
sage: %prun test()
6569139 function calls (6564056 primitive calls) in 36.792 seconds
Ordered by: internal time
ncalls tottime percall cumtime percall filename:lineno(function)
116767 27.1340.000 27.1340.000 {select.select}
964462.4390.000 32.468
On 2013-01-25 12:31, Dima Pasechnik wrote:
>
>
> On Friday, 25 January 2013 18:44:56 UTC+8, Jeroen Demeyer wrote:
>
> I have determined that this is due to the GAP upgrade (#13211).
>
> do you know where the regression is more precisely?
Unfortunately not, and I wouldn't know how to find ou
On Fri, Jan 25, 2013 at 6:23 AM, Jeroen Demeyer wrote:
> On 2013-01-25 12:21, David Joyner wrote:
>> On Fri, Jan 25, 2013 at 6:10 AM, Jeroen Demeyer
>> wrote:
>>> On 2013-01-25 12:02, David Joyner wrote:
Does that mean something is still wrong?
>>> Yes, this bug hasn't been fixed. The bug
On Friday, 25 January 2013 18:44:56 UTC+8, Jeroen Demeyer wrote:
>
> I have determined that this is due to the GAP upgrade (#13211).
>
> do you know where the regression is more precisely?
> On 2013-01-24 15:36, Jeroen Demeyer wrote:
> > While testing for speed regressions due to #12313, I a
On 2013-01-25 12:21, David Joyner wrote:
> On Fri, Jan 25, 2013 at 6:10 AM, Jeroen Demeyer
> wrote:
>> On 2013-01-25 12:02, David Joyner wrote:
>>> Does that mean something is still wrong?
>> Yes, this bug hasn't been fixed. The bug is non-deterministic, try
>> building again. But it seems that
I tested sage-5.7.beta0 with the latest GCC-4.8 (under development) with
SAGE_CHECK=yes, builds fine and all doctests pass.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubs
On Fri, Jan 25, 2013 at 6:10 AM, Jeroen Demeyer wrote:
> On 2013-01-25 12:02, David Joyner wrote:
>> Does that mean something is still wrong?
> Yes, this bug hasn't been fixed. The bug is non-deterministic, try
> building again. But it seems that the new MPIR somehow made this bug
> more likely
On 2013-01-25 12:02, David Joyner wrote:
> Does that mean something is still wrong?
Yes, this bug hasn't been fixed. The bug is non-deterministic, try
building again. But it seems that the new MPIR somehow made this bug
more likely to appear.
--
You received this message because you are subscri
On Thu, Jan 10, 2013 at 4:46 AM, Jean-Pierre Flori wrote:
> Dear all,
>
> Could someone try to build the new MPIR from
> http://trac.sagemath.org/sage_trac/ticket/13137 and build zn_poly on top of
> it (especially the make check target).
It is included in 5.7.b0 and I can't get sage to built on l
I have determined that this is due to the GAP upgrade (#13211).
On 2013-01-24 15:36, Jeroen Demeyer wrote:
> While testing for speed regressions due to #12313, I actually
> encountered a serious slowdown from sage-5.5 to sage-5.6:
>
> def test():
> for count in range(12):
> for n in [
Right, right. We could have something like g.show(highlight =
whateveryouwant(edgesorvertices)). Would make sense :-)
Nathann
On Thursday, January 24, 2013 6:36:40 PM UTC+1, jason wrote:
>
> On 1/24/13 6:25 AM, Nathann Cohen wrote:
> > But there mustbe other functions somewhere : I haven't seen
Hi,
> Is it possible to have nested roles? I'm thinking about something
> like :article:arxiv:`...`, :article:doi:`...`, etc
>
> That would make it easier to add new types of references, should the
> need arise.
I'm pretty sure it's not.
Florent
--
You received this message because you
Sage 5.6 was released on 21 January 2013. It is available in
source and binary form from:
* http://www.sagemath.org/download.html
Sage (http://www.sagemath.org/) is developed by volunteers and combines
over 90 open source packages. For instructions about installing Sage, see
* http://www.sag
> +1
as well a big +1!
Cheers, Christian
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
V
46 matches
Mail list logo
