On 11/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> The expected output is incorrect; the actual output is correct.
From irc:
20:24 < mabshoff> Sucks, but also re #750:
20:24 < mabshoff> File "permgroup_element.py", line 323:
20:24 < mabshoff> sage: g([0,1,2,3,4])
20:24 < mabshoff> Expected:
20:24 < mabshoff> [1, 2, 3, 0, 5, 4]
20:24 < mabshoff> Got:
20:24 < mabshoff> [1, 2, 0, 4, 3]
20:25 < wstein> oh, since I forgot to actually change the patched file.
20:25 < mabshoff> for the gmp?
20:25 < wstein> yes.
20:26 < wstein> What is g?
20:27 < mabshoff> No clue, but I am surprised that the Expected result
has a "5" in it.
20:28 < wstein> I strongly suspect the claimed output is wrong but the
actual output is right.
20:28 < wstein> But what is g?
20:28 < mabshoff> Permutation Group with generators [(1,2,3)(4,5)]
20:28 < wstein> It should be listed in permgroup_element.py.
20:28 < wstein> What is g itself?
20:29 < wstein> It should be an element of that perm group.
20:29 < mabshoff> g = G.gen(0)
20:29 < wstein> ok.
20:29 < wstein> It doesn't make sense to apply g to [0,1,2,3,4], does it?
20:29 < wstein> that seems really suspect.
20:29 < wstein> If it did make sense, it would have to fix 0
20:29 < mabshoff> Yep, something seems fishy.
In particular, how does applying (1,2,3)(4,5) to [0,1,2,3,4]
result in what you claim, i.e., in [1, 2, 0, 4, 3]?
It should either be an error, or maybe:
[2,0,1,3,4]
if say (1,2,3)(4,5) sends the "first entry", i.e., 0th position
to the 1st, the 1st to 2nd, etc,
Or it should be an error.
Or it should be
[0,2,3,1,5]
since the permutation fixes 0, say, and sends 1|-->2, 2|-->3
and 3|--1, and sends 4 to 5.
>
> On Thu, 1 Nov 2007, mabshoff wrote:
>
> >
> > I have released 2.8.11.rc1 (sorry, I skipped rc0, by the time I
> > realized the problem I had already called it rc1 in trac) at
> >
> > http://sage.math.washington.edu/home/mabshoff/sage-2.8.11.rc1.tar
> >
> > It passes testall on sage.math, but I would like to get some build
> > feedback on OSX 10.4, both PPC and Intel flavors, as well as 32 bit
> > Linux. I plan to release 2.8.11 final by late Friday night (PST).
> > Overall it is a rather conservative release because that build will be
> > the basis for Sage Bug Day 5. William and I are working on full 32 bit
> > OSX 10.5 support which will be rc2 hopefully. This release will still
> > fail to build on OpenSuSE 10.2 with their gcc.
> >
> > We have one doctest failure due to #750, so somebody with expertise
> > please tell us what to do:
> >
> > ./sage -t devel/sage-main/sage/groups/perm_gps/permgroup_element.py
> > sage -t devel/sage-main/sage/groups/perm_gps/permgroup_element.py
> > **********************************************************************
> > File "permgroup_element.py", line 323:
> > sage: g([0,1,2,3,4])
> > Expected:
> > [1, 2, 3, 0, 5, 4]
> > Got:
> > [1, 2, 0, 4, 3]
> > **********************************************************************
> > 1 items had failures:
> > 1 of 7 in __main__.example_7
> > ***Test Failed*** 1 failures.
> > For whitespace errors, see the file .doctest_permgroup_element.py
> > [3.0 s]
> > exit code: 256
> >
> > ----------------------------------------------------------------------
> > The following tests failed:
> >
> >
> > sage -t devel/sage-main/sage/groups/perm_gps/
> > permgroup_element.py
> > Total time for all tests: 3.0 seconds
> >
> > The following tickets have been closed (alpha0 and rc1 combined):
> >
> > #217: optimize matrix permanents (Jaap Spies)
> > #431: dsage jobs get lost by server (Yi Qiang, fixed by an earlier
> > patch)
> > #750: permutation group element (dict method, acting on lists) (Tom
> > Boothby)
> > #762: Elliptic curve L-series bug (William Stein)
> > #830: SAGE does not install 'gphelp' for extended PARI/GP help (Carl
> > Witty)
> > #845: can't pass boolean as parameter to Magma (Martin Albrecht)
> > #948: very slow factorization over a numberfield in a 2-variable ring
> > (Martin Albrecht, Hannes Schönemann)
> > #959: errors building sage because singular gets confused by system-
> > wide boost (Martin Albrecht)
> > #969: cvxopt miscompiled on OSX ppc (Josh Kantor, fixes by Michael
> > Abshoff)
> > #971: update Sympy.spkg to 0.5.6, add some minimal doctests (Carl
> > Witty, Ondrej Certik)
> > #973: Unhandled SIGSEGV: A segmentation fault occured running
> > dance(10) (Michael Abshoff, Carl Witty)
> > #993: Pari's gp interpreter has built-in library search path (Carl
> > Witty)
> > #1011: MagmaElement.__nonzero__ (Martin Albrecht)
> > #1026: memleak in linbox's gmp++_int_io.C (Michael Abshoff)
> > #1030: MPolynomial_libsingular mutates with call to factor (Joel
> > Mohler)
> > #1033: updated optional spkg: biopython 1.44 (Mike Hansen, fixes by
> > William Stein, Michael Abshoff)
> > #1034: clean up 'revlex' term ordering mess (Martin Albrecht)
> > #1037: arithmetic with Schubert polynomials (Mike Hansen)
> > #1039: Dokchitser L-series of number field (Jennifer S. Balakrishnan,
> > referred by William Stein)
> > #1044: segfault apply morphism to field element (Carl Witty)
> > #1045: add eulerian testing and circuit-finding (Jason Grout, referred
> > by Robert Miller)
> > #1049: graphs: transitive reduction function (Jason Grout, referred by
> > Robert Miller)
> > #1053: updated Cython to the 0.9.6.8b release (Robert Bradshaw)
> > #1056: Fix Givaro 3.2.6 build problem on MacOS X 10.5 (Ralf-Philipp
> > Weinmann, integrated by Michael Abshoff)
> > #1059: fix lcalc installation on OSX 10.5 (William Stein, integrated
> > by Michael Abshoff)
> > #1051: pari/gp extended help stops working when sage tree is moved
> > (Carl Witty)
> > #1060: fix flintqs compile on OSX 10.5 (William Stein, integrated by
> > Michael Abshoff)
> > #1061: updated python spkg on 10.5 (William Stein)
> > #1063: "sage -sh" should run $SHELL with Sage environment variables
> > set (Carl Witty)
> >
> >
> > Needs more feedback/discussion:
> >
> > #705: William wrote an EMail to Josh with suggestions after we had a
> > look at it. Since this is an optional spkg its upload is not tied to
> > the release of 2.8.11
> > #787: This ought be be resolved soon, but might be Bug Day 5 material
> > #980: needs more discussion, unlikely to get merged in 2.8.11
> > #1032: Latex'ing variable names is more robust and consistent (Joel
> > Mohler) - this one was actually backed out again - see the ticket for
> > comment
> >
> > If you have any more patches please make sure they apply cleanly
> > against this rc release. As far as I know I have looked at all patches
> > available in trac, if I overlooked one please let me know.
> >
> > Cheers,
> >
> > Michael
> >
> >
> > >
> >
>
>
>
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
