[sage-devel] Re: Sage 3.1.3.alpha3 released

[Georg S. Weber]

On Intel Mac OS X 10.4, 3.1.3.alpha3 built fine, "make test" had three
doctest failures:
- ell_point.py: issue calculating elliptic log, as
reported (with fix reported) above
- abvar/homspace.py: failure due to timeout  (known, that one occured
before)
- plot.py:   failure due to timeout (I don't think I
saw this one timeout before)

"make testlong" is still running, I'll give feedback this evening.

Cheers,
gsw
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Sage, Scicos, and MapleSim

[Hazem]

Hello Sage develpers,

Sage is a great project, and I'd like to thank everyone involved.
I'm not much of a developer, but I wanted to throw out an idea:

I work with physics/engineering/numerical applications mostly.I know
it is probably premature and difficult to implement or include
something like Simulink or Labview in Sage, but it occured to me that
given that SAGE's main strength is as a Symbolic computational engine,
that perhaps a block-diagram multidomain dynamical system modeler/
simulator/optimizer could eventually be implemented that takes
advantage of the symbolic capabilities of SAGE. In this regard, check
out MapleSim (http://www.maplesoft.com/products/maplesim/) which I
think makes very clever use of the Maple engine.

There is code available under a GPL-like license that could possibly
be used to start this, and that is the code from Scicos (a part of
Scilab). See Scicos.org.

I think that if this were implemented, it would be a great boost to
Sage since it would find a big audience in the applied sciences and
engineering fields.

Another idea is to create a LabVIEW-SAGE gateway so that LabVIEW could
use some SAGE capabilities.

If this is all nonsense then please excuse my ignorance.

Regards,

Hazem


--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3.alpha3 released

[David Joyner]

OS: amd64 hardy heron. Build went fine.
Only one doctest failure:


--
The following tests failed:


sage -t  devel/sage/sage/schemes/elliptic_curves/ell_point.py
Total time for all tests: 5373.5 seconds
Please see /home/wdj/sagefiles/sage-3.1.3.alpha3/tmp/test.log for the
complete log from this test.
[EMAIL PROTECTED]:~/sagefiles/sage-3.1.3.alpha3$ ./sage -t
devel/sage/sage/schemes/elliptic_curves/ell_point.py
sage -t  
devel/sage/sage/schemes/elliptic_curves/ell_point.py**
File "/home/wdj/sagefiles/sage-3.1.3.alpha3/tmp/ell_point.py", line 1103:
sage: P.elliptic_logarithm(precision=55)
Expected:
0.2735052644156991
Got:
0.2735052671206336
**
File "/home/wdj/sagefiles/sage-3.1.3.alpha3/tmp/ell_point.py", line 1105:
sage: P.elliptic_logarithm()  # 100 bits
Expected:
0.27656204014107100870071052662
Got:
0.27656204014107100870070982517
**
1 items had failures:
   2 of  20 in __main__.example_33
***Test Failed*** 2 failures.
For whitespace errors, see the file
/home/wdj/sagefiles/sage-3.1.3.alpha3/tmp/.doctest_ell_point.py
 [12.9 s]
exit code: 1024

--
The following tests failed:


sage -t  devel/sage/sage/schemes/elliptic_curves/ell_point.py
Total time for all tests: 12.9 seconds

+

On Wed, Oct 8, 2008 at 7:49 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> this took much longer than I had planned, but I got sick and was also
> pretty burned out, so finally here we go. There are still a bunch of
> known problems with 3.1.3.a3:
>
>  * parallel make is broken for eclib (#4228)
>  * build of R hangs with the latest 10.5 Java update by Apple (#4219).
> This update also seems to have broken 3D plotting
>  * a doctest failure in sage/schemes/elliptic_curves/ell_point.py
> caused by #4225 (no ticket yet)
>
> Most of the above should be pretty easy to fix, but I ran out of time
> before leaving for SD10 in Nancy in a couple hours. The good news is
> that he following major issues got merged:
>
>  * The ReST toolchain with its depenencies
>  * the initial version of the species code
>
> Hopefully we can get 3.1.3 out before the start of the coding spring
> of SD10. As mentioned above most problems have known fixes and just
> need to be reviewed and merged. But it will be 24 hours until I am
> back online again, so expect some activity then.
>
> Sources and a sage.math only binary can be found in the usual place at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.3/
>
> Please build, test and repot issues.
>
> Cheers,
>
> Michael
>
> #3385: Jason Grout: plot_vector_field does not deal with aspect ratios
> correctly [Reviewed by Mike Hansen]
> #3665: Mike Hansen: add initial species code [Reviewed by Robert
> Miller]
> #3980: Jason Merrill: Find_root bug [Reviewed by Marshall Hampton]
> #4106: Alex Ghitza: error coercing symbolic variable into polynomial
> ring modulo 4 (but not mod 3) [Reviewed by William Stein]
> #4220: Mike Hansen: include Sphinx, Docutils, Jinja, and Pygments in
> Sage [Reviewed by Michael Abshoff]
> #4224: Carl Witty: small error in new question-mark interval printing
> [Reviewed by Michael Abshoff]
> #4225: Robert Bradsahw: faster sqrt for complex numbers [Reviewed by
> Alex Ghitza]
> #4226: Robert Bradshaw: Real Lazy Field [Reviewed by Mike Hansen]
> #4227: Michael Abshoff: Sage 3.1.3.alpha2: many Magma doctests that
> should are not optional [Reviewed by Alex Ghitza]
> #4232: Robert Bradshaw: #249 causes bug in importing large lists
> [Reviewed by Jason Grout]
> #4233: John Palmieri: fix doctest failure due to deprecation warning
> in calculus/all.py [Reviewed by Mike Hansen]
> #4234: Minh Nguyen: typos in programming guide [Reviewed by Michael
> Abshoff]
> #4235: Minh Nguyen: typos in and enhancement to installation guide
> [Reviewed by Michael Abshoff]
> #4238: David Fu, Robert Bradshaw: option to create local .so file
> for .spyx modules [Reviewed by Georg Weber]
> #4239: Francis Clarke: fix for problems with zero kernel and images
> [Reviewed by Georg Weber]
> #4247: William Stein: plotting -- bug in text and pdf export [Reviewed
> by Mike Hansen]
>
> >
>

--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3.alpha3 released

[mhampton]

My only failure on an intel mac (10.5) is the ell_point.py test.

M. Hampton

On Oct 8, 6:49 am, mabshoff <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> this took much longer than I had planned, but I got sick and was also
> pretty burned out, so finally here we go. There are still a bunch of
> known problems with 3.1.3.a3:
>
>  * parallel make is broken for eclib (#4228)
>  * build of R hangs with the latest 10.5 Java update by Apple (#4219).
> This update also seems to have broken 3D plotting
>  * a doctest failure in sage/schemes/elliptic_curves/ell_point.py
> caused by #4225 (no ticket yet)
>
> Most of the above should be pretty easy to fix, but I ran out of time
> before leaving for SD10 in Nancy in a couple hours. The good news is
> that he following major issues got merged:
>
>  * The ReST toolchain with its depenencies
>  * the initial version of the species code
>
> Hopefully we can get 3.1.3 out before the start of the coding spring
> of SD10. As mentioned above most problems have known fixes and just
> need to be reviewed and merged. But it will be 24 hours until I am
> back online again, so expect some activity then.
>
> Sources and a sage.math only binary can be found in the usual place at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.3/
>
> Please build, test and repot issues.
>
> Cheers,
>
> Michael
>
> #3385: Jason Grout: plot_vector_field does not deal with aspect ratios
> correctly [Reviewed by Mike Hansen]
> #3665: Mike Hansen: add initial species code [Reviewed by Robert
> Miller]
> #3980: Jason Merrill: Find_root bug [Reviewed by Marshall Hampton]
> #4106: Alex Ghitza: error coercing symbolic variable into polynomial
> ring modulo 4 (but not mod 3) [Reviewed by William Stein]
> #4220: Mike Hansen: include Sphinx, Docutils, Jinja, and Pygments in
> Sage [Reviewed by Michael Abshoff]
> #4224: Carl Witty: small error in new question-mark interval printing
> [Reviewed by Michael Abshoff]
> #4225: Robert Bradsahw: faster sqrt for complex numbers [Reviewed by
> Alex Ghitza]
> #4226: Robert Bradshaw: Real Lazy Field [Reviewed by Mike Hansen]
> #4227: Michael Abshoff: Sage 3.1.3.alpha2: many Magma doctests that
> should are not optional [Reviewed by Alex Ghitza]
> #4232: Robert Bradshaw: #249 causes bug in importing large lists
> [Reviewed by Jason Grout]
> #4233: John Palmieri: fix doctest failure due to deprecation warning
> in calculus/all.py [Reviewed by Mike Hansen]
> #4234: Minh Nguyen: typos in programming guide [Reviewed by Michael
> Abshoff]
> #4235: Minh Nguyen: typos in and enhancement to installation guide
> [Reviewed by Michael Abshoff]
> #4238: David Fu, Robert Bradshaw: option to create local .so file
> for .spyx modules [Reviewed by Georg Weber]
> #4239: Francis Clarke: fix for problems with zero kernel and images
> [Reviewed by Georg Weber]
> #4247: William Stein: plotting -- bug in text and pdf export [Reviewed
> by Mike Hansen]
--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3.alpha3 released

[Alex Ghitza]

There's a patch waiting for review at trac #4214 fixing that doctest failure
(once and for all :).  I've moved #4214 to 3.1.3 instead of 3.2 so that it
has better visibility.

Best,
Alex

On Thu, Oct 9, 2008 at 1:25 AM, Martin Albrecht <
[EMAIL PROTECTED]> wrote:

>
> On Wednesday 08 October 2008, mabshoff wrote:
> > Please build, test and repot issues.
>
> I *upgraded* from alpha2 and only see the known doctest failure in
>
>  sage -t  devel/sage/sage/schemes/elliptic_curves/ell_point.py
>
> on 64-bit Debian/GNU Linux, Core2Duo
>
> Cheers,
> Martin
>
> --
> name: Martin Albrecht
> _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
> _www: 
> http://www.informatik.uni-bremen.de/~malb
> _jab: [EMAIL PROTECTED]
>
>
> >
>


-- 
Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne --
Australia -- http://www.ms.unimelb.edu.au/~aghitza/

--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] in-place WYSIWYG text-cell editing

[Jason Grout]

I just posted a patch and two spkgs that enable in-place WYSIWYG editing 
of text cells in the notebook.  Basically, apply the patch and install 
the two spkgs here:

http://sage.math.washington.edu/home/jason/jeditable-1.6.1.spkg

http://sage.math.washington.edu/home/jason/tinyMCE-3.2.0.2.spkg

Create a worksheet and make a text cell by editing it in the "Edit" mode 
and putting text between the cells. Switch back to the worksheet view 
and doubleclick on that text. A TinyMCE editor should pop up, letting 
you edit the text. As usual, $x^2$ and $$x^2$$ give you jsmath latex 
output.  Save your changes and the worksheet is updated.

I've run out of time to make creating text cells easier; but that's also 
a point on which to solicit feedback anyway.  Currently text cells are 
just the stuff between the real cells (the "compute" cells).  Are there 
thoughts about how to support text cells better (i.e., allow creation 
from the notebook?).  What about a UI for creation?  Currently clicking 
on the horizontal blue line makes a compute cell; how should we make 
text (i.e., straight html) cells?

Thanks,

Jason


--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3.alpha3 released

[Justin C. Walker]

On Oct 8, 2008, at 4:49 AM, mabshoff wrote:

>
> Hello folks,
>
> this took much longer than I had planned, but I got sick and was also
> pretty burned out, so finally here we go. There are still a bunch of
> known problems with 3.1.3.a3:
>
>  * parallel make is broken for eclib (#4228)
>  * build of R hangs with the latest 10.5 Java update by Apple (#4219).
> This update also seems to have broken 3D plotting

A quick check: this *will* hang on 10.5 systems that have done the  
recent "Java 2" update, correct?  Is the workaround to 'touch' the  
appropriate 'r' file in $SAGE_ROOT/spkg/installed and restart the build?

Thanks.

Justin

--
Justin C. Walker, Curmudgeon-At-Large, Director
Institute for the Enhancement of the Director's Income

The path of least resistance:
it's not just for electricity any more.





--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] weird bug in alpha2, went away in alpha3

[John Cremona]

In sage-3.1.3.alpha2, this works fine from the command line:

sage: E=EllipticCurve('5077a1')
sage: E.integral_points()

but in the notebook it gives this error:

Traceback (click to the left for traceback)
...
TypeError: Argument 'left_precomposition' has incorrect type (expected
sage.categories.morphism.Morphism, got
sage.structure.coerce_maps.DefaultConvertMap_unique)

However in 3.1.3.alpha3 (which just finished building as was typing
that) it works fine.  I guess I had better be careful which version I
use in my talk at SD10!

John

--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3.alpha3 released

[Martin Albrecht]

On Wednesday 08 October 2008, David Kohel wrote:
> Hi,
>
> I'm just trying to update my sage for SAGE Days 10, but find that the
> compilation hangs here:
>
> checking for paperconf... false
> checking for java... /usr/bin/java
> checking for javac... /usr/bin/javac
> checking for javah... /usr/bin/javah
> checking for jar... /usr/bin/jar
> checking whether Java compiler works...
>
> This is on Mac OSX Leopard, after moving /opt/local/ to /opt/
> local.back
> by hand.
>
> I actually have had a javac process running for 3 hours...
>
> Any suggestions?

I think this is this bug:

>  * build of R hangs with the latest 10.5 Java update by Apple (#4219).
> This update also seems to have broken 3D plotting

Cheers,
Martin

-- 
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_www: http://www.informatik.uni-bremen.de/~malb
_jab: [EMAIL PROTECTED]


--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3.alpha3 released

[David Kohel]

P.S. I get the same behavior for 3.1.2.

--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3.alpha3 released

[David Kohel]

Hi,

I'm just trying to update my sage for SAGE Days 10, but find that the
compilation hangs here:

checking for paperconf... false
checking for java... /usr/bin/java
checking for javac... /usr/bin/javac
checking for javah... /usr/bin/javah
checking for jar... /usr/bin/jar
checking whether Java compiler works...

This is on Mac OSX Leopard, after moving /opt/local/ to /opt/
local.back
by hand.

I actually have had a javac process running for 3 hours...

Any suggestions?

--David

--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3.alpha3 released

[Martin Albrecht]

On Wednesday 08 October 2008, mabshoff wrote:
> Please build, test and repot issues.

I *upgraded* from alpha2 and only see the known doctest failure in 

  sage -t  devel/sage/sage/schemes/elliptic_curves/ell_point.py

on 64-bit Debian/GNU Linux, Core2Duo

Cheers,
Martin

-- 
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_www: http://www.informatik.uni-bremen.de/~malb
_jab: [EMAIL PROTECTED]


--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: review request for trac #4164 (polyhedra.py)

[mhampton]

There are some problems with the patch above:

1) the line lift_i *= 1.1 isn't good because usually we want rational
or integer values for vertex coordinates.  If numerical input is given
(for the other vertices), these will just be cast to floats, but with
exact input cddlib will try to do exact computations.
2) after changing this to lift_i = lift_i * 11/10, I could still find
examples where it fails.

There is no doubt in my mind that lrs would be faster than anything
you or I could produce in python.  It is also code that has been
tested by polytope experts (which I am not) for almost 10 years.

If you want to keep trying, here's a particularly nasty 4D example
whose vertices are:

[[-97, -99, -61, 0], [-100, 93, -78, 0], [88, -100, 2, 0], [-34, 100,
-65, 0], [96, 88, -10, 0], [64, -71, 99, 0], [-64, -100, -37, 0], [80,
86, -98, 0], [96, 91, -66, 0], [15, 99, -98, 0], [81, -95, -96, 0],
[97, -50, 89, 0], [-92, 85, -97, 0], [56, 19, 100, 0], [98, 78, -63,
0], [-99, -100, 30, 0], [-13, -98, 97, 0], [-34, 34, 100, 0], [-15,
-30, 100, 0], [95, -97, -75, 0], [94, -64, -92, 0], [94, -92, 46, 0],
[98, 70, 63, 0], [-95, -52, 78, 0], [-94, -25, 95, 0], [83, 4, -97,
0], [-6, -100, -32, 0], [-6, 100, -45, 0], [-95, 81, 98, 0], [-79, 95,
97, 0], [100, -63, 56, 0], [90, -86, 94, 0], [35, -100, 94, 0], [-18,
99, 76, 0], [-48, -92, -91, 0], [-49, 94, -94, 0], [-99, 69, 69, 0],
[-77, 100, 16, 0], [98, -76, -27, 0], [75, 98, 24, 0], [97, 71, -79,
0], [99, 24, -14, 0], [90, -97, 34, 0], [-88, 90, -91, 0], [-79, -14,
-99, 0], [100, -72, 53, 0], [94, 97, -80, 0], [67, 99, 39, 0], [-95,
-95, 54, 0], [66, 82, -99, 0], [-99, -73, -82, 0], [-58, -71, 97, 0],
[-88, -36, -97, 0], [79, -41, 100, 0], [-82, -75, -99, 0], [-96, 90,
55, 0], [-99, 100, -71, 0], [-30, 100, 20, 0], [37, -9, -99, 0], [91,
84, -96, 0], [-66, 68, -98, 0], [92, 90, 98, 0], [43, -100, -19, 0],
[-93, -91, -82, 0], [92, 1, 99, 0], [-87, -55, 96, 0], [34, 99, 77,
0], [-51, -27, 99, 0], [81, -95, 83, 0], [99, 69, 37, 0], [59, 100, 2,
0], [97, -62, -53, 0], [-20, 94, 99, 0], [39, 98, 86, 0], [96, -27,
-87, 0], [100, -75, 24, 0], [0, 0, 0, 1]]

lrs is almost instantaneous on that example, whereas both my code and
yours fails.   In the short term the current trac patch is still a big
improvement over what was there before, so I think it should go in.

Cheers,
Marshall

On Oct 7, 10:51 pm, "Arnaud Bergeron" <[EMAIL PROTECTED]> wrote:
> 2008/10/7 mhampton <[EMAIL PROTECTED]>:
>
>
>
> > Linearly increasing the lift values does not work.  I can find a
> > relatively small example (81 vertices in 4 dimensions) where your
> > patch fails.
>
> > For higher dimensions I think using lrs is really the way to go, since
> > adding it has other advantages as well.  When I have a little time I
> > will try to write an interface to use it for triangulation.
>
> If it is faster, then go for it.  But in the meantime I would like to
> have something that works in all cases.
>
> If as I kind of guessed, but hoped to be false, linear increments are
> not good because the may create planar situations in the extra
> dimension, then an exponential growth should work.  I have yet another
> revised patch that does just that.
>
> After this one I promise to stop bothering you.
>
> Arnaud
>
> > I am putting the other improvements from your patch into another
> > merged patch.  Can you review it?
>
> > Cheers,
> > Marshall
>
> >> On Oct 4, 7:59 pm, "Arnaud Bergeron" <[EMAIL PROTECTED]> wrote:
>
> >> > 2008/9/29 mhampton <[EMAIL PROTECTED]>:
>
> >> > > I thought I would explicitly point this one out because I had been
> >> > > reviewing #4164 (work by Arnaud Bergeron), but now I am also
> >> > > contributing code and I think the best scenario is to have someone
> >> > > else take a look.  Mike Hansen has looked at polyhedra.py before, so
> >> > > he is a candidate if willing, but it would be great if someone else
> >> > > takes a look.  Polyhedra.py (in sage/geometry) is still in its early
> >> > > stages; eventually I hope for it and other things in the geometry
> >> > > group to provide most of the functionality of polymake and other
> >> > > packages if they can't be made part of standard sage.  Because the
> >> > > optimal design is far from clear to me, I want to encourage more
> >> > > eyeballs on it (I am an enthusiastic amateur when it comes to
> >> > > polytopes, not an expert).
>
> >> > > Marshall Hampton
>
> >> > About this patch I have an idea for an improvement that would make it
> >> > work 100% in all cases.  I can't believe I didn't think of this
> >> > sooner.
>
> >> > The idea is that instead of adding a random value in the extra
> >> > dimension for the lifting we can only add an monotonically increasing
> >> > value.  I tried this on the simple 4D example that was in doctest
> >> > before as well as the monster that crashed my code (and my hopes)
> >> > before and they both worked repeatedly (with a newly created
> >> > polyhedron, otherwise it just hits the cache).
>
> >

[sage-devel] coercion of variables

[Alex Ghitza]

Hi folks,

In the process of dealing with
http://trac.sagemath.org/sage_trac/ticket/4246 , I ran into some issues
involving coercion of variables.  I quickly realized that I don't really
know what the desired behavior should be, hence this post.

On one hand, William gave a very compelling example of something going quite
wrong:

sage: var('x y')
sage: S = QQ['x']
sage: S(x+y)
2*x

What happens is that the symbolic variables x and y both coerce to x, hence
we get 2*x.  It's hard to imagine any situation in which you would want this
to be the right answer, and in fact it is hard to see what a "right answer"
would be -- hence the idea of throwing a TypeError here.

However, this clashes with some current behavior that might be viewed as
correct/useful:

sage: var('x')
sage: S = QQ['t']
sage: S(x)
t

It's a bit harder to discard this as wrong.  Also, it's not just an issue
with symbolic variables:

sage: R = QQ['x']
sage: S = QQ['t']
sage: S(x)
t

I don't know what to do.  If we want to keep the last two behaviors, it
seems that we're stuck with the first one as well.

Best,
Alex

-- 
Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne --
Australia -- http://www.ms.unimelb.edu.au/~aghitza/

--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Sage 3.1.3.alpha3 released

[mabshoff]

Hello folks,

this took much longer than I had planned, but I got sick and was also
pretty burned out, so finally here we go. There are still a bunch of
known problems with 3.1.3.a3:

 * parallel make is broken for eclib (#4228)
 * build of R hangs with the latest 10.5 Java update by Apple (#4219).
This update also seems to have broken 3D plotting
 * a doctest failure in sage/schemes/elliptic_curves/ell_point.py
caused by #4225 (no ticket yet)

Most of the above should be pretty easy to fix, but I ran out of time
before leaving for SD10 in Nancy in a couple hours. The good news is
that he following major issues got merged:

 * The ReST toolchain with its depenencies
 * the initial version of the species code

Hopefully we can get 3.1.3 out before the start of the coding spring
of SD10. As mentioned above most problems have known fixes and just
need to be reviewed and merged. But it will be 24 hours until I am
back online again, so expect some activity then.

Sources and a sage.math only binary can be found in the usual place at

http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.3/

Please build, test and repot issues.

Cheers,

Michael

#3385: Jason Grout: plot_vector_field does not deal with aspect ratios
correctly [Reviewed by Mike Hansen]
#3665: Mike Hansen: add initial species code [Reviewed by Robert
Miller]
#3980: Jason Merrill: Find_root bug [Reviewed by Marshall Hampton]
#4106: Alex Ghitza: error coercing symbolic variable into polynomial
ring modulo 4 (but not mod 3) [Reviewed by William Stein]
#4220: Mike Hansen: include Sphinx, Docutils, Jinja, and Pygments in
Sage [Reviewed by Michael Abshoff]
#4224: Carl Witty: small error in new question-mark interval printing
[Reviewed by Michael Abshoff]
#4225: Robert Bradsahw: faster sqrt for complex numbers [Reviewed by
Alex Ghitza]
#4226: Robert Bradshaw: Real Lazy Field [Reviewed by Mike Hansen]
#4227: Michael Abshoff: Sage 3.1.3.alpha2: many Magma doctests that
should are not optional [Reviewed by Alex Ghitza]
#4232: Robert Bradshaw: #249 causes bug in importing large lists
[Reviewed by Jason Grout]
#4233: John Palmieri: fix doctest failure due to deprecation warning
in calculus/all.py [Reviewed by Mike Hansen]
#4234: Minh Nguyen: typos in programming guide [Reviewed by Michael
Abshoff]
#4235: Minh Nguyen: typos in and enhancement to installation guide
[Reviewed by Michael Abshoff]
#4238: David Fu, Robert Bradshaw: option to create local .so file
for .spyx modules [Reviewed by Georg Weber]
#4239: Francis Clarke: fix for problems with zero kernel and images
[Reviewed by Georg Weber]
#4247: William Stein: plotting -- bug in text and pdf export [Reviewed
by Mike Hansen]

--~--~-~--~~~---~--~~
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://www.sagemath.org
-~--~~~~--~~--~--~---