On 2012-06-14 09:02, Simon King wrote:
> Probably *yes* - as you say, a dependency of ATLAS has probably been
> upgraded.
I wanted to say that an upgrade of a dependency in many cases does not
require rebuilding the package. Especially if the upgrade is within the
same upstream version (foo-X.Y.X.p
1. the concept that Maxima fails to "preserve precision" that seems to be
bandied about here
doesn't seem to me to make much sense. You have 2 numbers of different
precisions and you
operate on them. What is supposed to be preserved?
2. If the MPFR fraction has N bits, then ?fpprec:N will b
On Jun 13, 7:32 pm, rjf wrote:
> If you want a Sage number X of n (binary) bits precision to be converted to
> a Maxima bigfloat of n bits,
> then you can do this.
> First in Sage compute Xrat which is an exact rational that is equal to X.
> It could be computed
> by something like (some integer
http://www.gap-system.org/Download/index.html
now points to GAP 4.5.4, so we should start
upgrading some time soon.
I won't be able to look into it before July, though.
Best,
Dima
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an emai
I just turned off experimental. There aren't that many things being tested
there at the moment, so no one should need to use it. One of plugins being
tested (the git plugin) may also be causing all of these zombie git
processes.
On Thu, Jun 14, 2012 at 2:14 PM, Jonathan Bober wrote:
> I think th
Jonathan Bober writes:
> I think that the experimental trac server is getting hit by Baidu in
> bad places, and it isn't behaving well. There should be a robots.txt
> for trac, which should probably completely disallow the experimental
> installation, and something probably needs to be fixed with
I think that the experimental trac server is getting hit by Baidu in
bad places, and it isn't behaving well. There should be a robots.txt
for trac, which should probably completely disallow the experimental
installation, and something probably needs to be fixed with the
experimental installation.
+1
-- sent from a telephone.
On Jun 14, 2012 9:32 PM, "Volker Braun" wrote:
> Since we are using references to trac in the manuals, how about we allow
> trac urls for tickets of the form
>
> http://trac.sagemath.org/
>
> instead of the current
>
> http://trac.sagemath.org/sage_trac/ticke
Since we are using references to trac in the manuals, how about we allow
trac urls for tickets of the form
http://trac.sagemath.org/
instead of the current
http://trac.sagemath.org/sage_trac/ticket/
Its an easy search/replace with mod_rewrite, and the manuals wouldn't be
filled with n
I assume this has been noticed by others, but Trac has been a nightmare
today. Just pointing it out, I understand if there isn't anything that can
be done...
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsu
On Thursday, June 14, 2012 12:34:11 PM UTC-5, kcrisman wrote:
>
> surface. Turn on the black mess and start it spinning. Then toggle the
>> "high quality" on and off.
>>
>>
>
> Wow, it's sort of mesmerizing.
>
> I'm a little torn. The speckles are definitely distracting, if of
> potential va
On Tuesday, June 12, 2012 4:52:37 PM UTC-4, Jonathan wrote:
>
> I have set up my test server to default to high quality (antialiasing).
> Test it out.
>
> The answer to Jason's question is "yes". The antialiasing causes white
> speckles in regions of high contrast change. That was another
If you did this you'd need to tell maxima to assume various things about
the variables (real, in between floatvalue - epsilon and floatvalue +
epsilon...). I don't know maxima well enough to determine how feasible
this idea is if you made such assumptions, but it's worth investigating.
David
On T
If the optional one is functional, then I agree that the experimental one
should be removed. Go for it!
David
On Wed, Jun 13, 2012 at 11:44 PM, Rajeev Singh wrote:
> Hi,
>
> I was going through the list of optional and experimental packages for
> Sage and discovered that sip appears twice (diff
On Thu, Jun 14, 2012 at 9:47 AM, William Stein wrote:
> On Thu, Jun 14, 2012 at 9:35 AM, Jason Grout
> wrote:
>> This may be what some people have been complaining about. For me (on UW
>> campus), http://sage.math.washington.edu/home/jason/sagecell/ gives
>>
>> Error 502 - Bad Request
>> The ser
On Thu, Jun 14, 2012 at 9:35 AM, Jason Grout
wrote:
> This may be what some people have been complaining about. For me (on UW
> campus), http://sage.math.washington.edu/home/jason/sagecell/ gives
>
> Error 502 - Bad Request
> The server could not resolve your request for uri:
> http://sage.math.w
Done. Patch is ready for review at
http://trac.sagemath.org/sage_trac/ticket/12806
Cheers,
J
--
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 htt
This may be what some people have been complaining about. For me (on UW
campus), http://sage.math.washington.edu/home/jason/sagecell/ gives
Error 502 - Bad Request
The server could not resolve your request for uri:
http://sage.math.washington.edu/home/jason/sagecell/
but http://boxen.math.wa
On 6/14/12 7:40 AM, Javier López Peña wrote:
On Thursday, June 14, 2012 3:39:23 PM UTC+1, Javier López Peña wrote:
Yes, that is the case. The (weighted) clustering coefficient
algorithm (with weighted *edges*)
computes some auxiliary *vertex* weights. The old method used to
retur
On Thursday, June 14, 2012 3:39:23 PM UTC+1, Javier López Peña wrote:
>
> Yes, that is the case. The (weighted) clustering coefficient algorithm
> (with weighted *edges*)
> computes some auxiliary *vertex* weights. The old method used to return
> all of it, the new one
> just returns the cluste
On Thursday, June 14, 2012 3:27:41 PM UTC+1, jason wrote:
>
> So, to be clear, the new networkx function does not give you as much
> information as the old one?
Yes, that is the case. The (weighted) clustering coefficient algorithm
(with weighted *edges*)
computes some auxiliary *vertex* wei
On 6/14/12 7:20 AM, Javier López Peña wrote:
I don't think this should be a problem, but current policy is to
first deprecate it for a while (usually I've heard one year, see
also #13109 for something that will hopefully work in the
future). Presumably you can chan
>
> I don't think this should be a problem, but current policy is to first
>> deprecate it for a while (usually I've heard one year, see also #13109 for
>> something that will hopefully work in the future). Presumably you can
>> change the backend but still return the weights for now, and make
On Thursday, June 14, 2012 7:19:01 AM UTC-4, Javier López Peña wrote:
>
> Hi all,
>
> I am working on the failing doctest to upgrade our almost 2 year old
> NetworkX 1.2 to NetworkX 1.6 (see #12806, [1]) I have sorted out the
> doctest failures in graph.py and digraph.py; in order to solve the
Hi all,
I am working on the failing doctest to upgrade our almost 2 year old
NetworkX 1.2 to NetworkX 1.6 (see #12806, [1]) I have sorted out the
doctest failures in graph.py and digraph.py; in order to solve the ones in
generic_graph.py there is some design decision that needs to be made.
The
No takers? :)
On 11 June 2012 14:47, Martin Albrecht wrote:
> Update, we are down to these doctest failures:
>
> 1) File
> "/opt/sage-5.0-linbox/devel/sage/sage/tests/french_book/numbertheory.py",
> line 43:
> sage: [r for r in R]
> Expected:
> [0, 2*x, x + 1, x + 2, 2, x, 2*x + 2, 2*x + 1
While its certainly impressive that there are apache processes with >30GB
resident ram usage(!), that alone shouldn't be enough to drag boxen down.
There are also about 5000 git processes in the zombie state, owned by
www-data. Whoever is serving /home/git/repositories/sage.git over http is
doi
On Wed, Jun 13, 2012 at 10:38 PM, Minh Nguyen wrote:
> Hi Jeroen,
>
> On Thu, Jun 14, 2012 at 3:24 PM, Jeroen Demeyer
> wrote:
>>> Thank you very much for the report. The problem has been fixed now.
>> Do you know what happened before, what went wrong?
>
> It has to do with the memory consumpti
On 2012-06-14, Jeroen Demeyer wrote:
> On 2012-06-14 07:12, Rajeev Singh wrote:
>> Why does atlas recompile if I upgrade sage using -
>>
>> $ sage -upgrade
>>
>> even though atlas has not been updated?
> Because some *dependency* of ATLAS has been updated. Could be MPIR for
> example.
>
>> Is i
29 matches
Mail list logo
