I am strongly against conversion from floating-point to interval
field. Floatting point arithmetic is approximate whereas interval
arithmetic is guaranteed. Moreover, the conversion between non exact
rings in Sage are always from "more precision" to "less precision".
For these reasons the conversio
2013/8/26 Marc Mezzarobba
> Hi,
>
> Sage happily coerces floating-point numbers (e.g., elements of RR) into
> intervals (e.g., elements of RIF), subject to some conditions on the
> precision of the source and destination rings.
>
> The relevant portion of the coercion graph looks like this:
>
>
I apologize for not providing some of the details earlier.
I discovered an environmental variable ARCHFLAGS that I'd set a long time
ago and totally forgotten. That environmental variable was responsible for
adding the '-arch x86_64' to the compilation process. I'm going to try
unsetting this a
Vincent Delecroix a écrit :
> This is clearly what we want. If you have an operation involving
> several real numbers with different precisions then you want that the
> result has the least precision.
And in analogous situations where each precision corresponds to a well-
defined ring, the idea t
2013/8/26 Jeroen Demeyer
> It's hard to define what "coercion" would even mean in this case. The
> manual mentions that it must be a ring homomorphism, but in this case (RLF,
> RR, RIF) the mathematical ring is all the same, namely "the real numbers".
> It is only the implementation of the ring w
It's hard to define what "coercion" would even mean in this case. The
manual mentions that it must be a ring homomorphism, but in this case
(RLF, RR, RIF) the mathematical ring is all the same, namely "the real
numbers". It is only the implementation of the ring which is different.
I don't und
On 8/23/13 1:53 AM, William Stein wrote:
One could of course create something that provides computation of a
"single cell" that has proper authentication. I can't see any reason
not to encourage that too, but it's up to Jason.
It could follow in the same spirit as our new terms of service
ag
Hi,
Sage happily coerces floating-point numbers (e.g., elements of RR) into
intervals (e.g., elements of RIF), subject to some conditions on the
precision of the source and destination rings.
The relevant portion of the coercion graph looks like this:
( +---> RDF )
On 2013-08-26 04:32, P Purkayastha wrote:
Did you try the compilation with the environment variable
|
SAGE_INSTALL_GCC="no"
|
You can try, but I would be very surprised if that worked (but if it
does work, I certainly want to know!)
--
You received this message because you are subscribed to t
On 2013-08-24 11:46, ASageWoodpecker wrote:
When trying to build sage
Which version of Sage?
I came across a weird situation with
matplotlib on OS X.
Which version of OS X?
The setup deemed my default version of gcc (LLVM) to be too old
(equivalent to 4.2) and downloaded GNU GCC 4.6.
Good!
10 matches
Mail list logo
