In three different Mac browsers (Safari, Camino, Firefox) the two-
column display of an index page such as
http://www.sagemath.org/doc/reference/genindex-A.html
has a white background when first displayed, but scroll to the right
and the new area has a dark blue background. This makes reading
I tried something with try/except as suggested by pang but fork makes
me getting out without evaluating the except statement
Have you an idea why it does not work?
On 16 juil, 20:40, pang pablo.ang...@uam.es wrote:
A related question: is it possible to catch an exception if there is a
On Jul 19, 3:48 pm, Kent Morrison kentemorri...@gmail.com wrote:
In three different Mac browsers (Safari, Camino, Firefox) the two-
column display of an index page such as
http://www.sagemath.org/doc/reference/genindex-A.html
has a white background when first displayed, but scroll to the
A related question: is it possible to catch an exception if there is a
time out?
I think there should be. The timeout process should raise an exception
which can be catch. Right now, one can catch that it sends back a
string 'NO DATA (timed out)' rather than a result. So the following
Hi,
I use ZZ(ss).factor(proof=False,limit=10^5).
By changing 'limit' you limit the search.
2^26 * 3^30 * 5^15 * 7^5 * 13^5 * 23^2 * 29 * 37 * 967 *
100231435706561580153005984524922236635721822683010490144527758096287118\
468921220756478157058125901560872523532972896397
This can be combined
Hi,
On this topic, Sebastian Pancratz and I wrote an optimized
implementation of trial division to find the smallest factor of an
integer:
http://trac.sagemath.org/sage_trac/ticket/9537
This may be in sage-4.5.2.
-- William
On Mon, Jul 19, 2010 at 9:16 PM, Rolandb rola...@planet.nl
I'm curious about the intent behind the Milestone field in
Trac tickets. It appears (at least for tickets I've been
interested in) that this field is always set to whatever the
next coming release is. Then, after that release is done, the
milestone is (automatically?) bumped up to the next
thank you chris,
I thought about something like that but I could not catch this 'NO
DATA etc'.
On 19 juil, 17:51, chris wuthrich christian.wuthr...@gmail.com
wrote:
A related question: is it possible to catch an exception if there is a
time out?
I think there should be. The timeout
Hi all
I have been using the inner tensor product in the Schur basis. My
question is :
a) Is it just my computer or is this way slower than Stembridge's SF
package ?
For example, SF computes
s[14,14].itensor(s[14,13,1])
in no time . But it seems to take quite a lot of time on Sage. I
have 4
On Mon, Jul 19, 2010 at 11:46 PM, vasu tewari.v...@gmail.com wrote:
Hi all
I have been using the inner tensor product in the Schur basis. My
question is :
a) Is it just my computer or is this way slower than Stembridge's SF
package ?
For example, SF computes
s[14,14].itensor(s[14,13,1])
Hi
Thanks for the info.
I'll post over there.
Regards
On Jul 19, 2:47 pm, William Stein wst...@gmail.com wrote:
On Mon, Jul 19, 2010 at 11:46 PM, vasu tewari.v...@gmail.com wrote:
Hi all
I have been using the inner tensor product in the Schur basis. My
question is :
a) Is it just my
Using Polyhedron as you are doing is the correct way to compute convex
hulls in Sage. If your vertices are integral, then you could also try
using the LatticePolytope class. LatticePolytope uses PALP instead of
cddlib, and so might be faster for some inputs.
I have meant for a long time to make
Sadly this is not possible now but its something we should have. I
would like to someday add (or have someone else add) a beneath-and-
beyond convex hull method to Sage; once we have that it would be
pretty easy to add a method to the Polyhedron class that could take a
vertex as an input and add
13 matches
Mail list logo
