Re: [sage-devel] Possible bug report: Incorrect SymbolicSeries expansion (spurious 1/x term)

Thank you all for the speedy turnaround on this! In particular: Vincent and Dima: Thank you for the informative 'code archaeology' and helpful pointers Dave: Thank you for filing (and fixing!) #31645 Best, Thomas On Sun, Apr 11, 2021 at 12:53 AM dmo...@de

Re: [sage-devel] Re: should "foo?" print TESTS: blocks or omit them?

A corollary to this is that relevant documentation should not exist in the TESTS block. And those edge cases should be documented. If the user wants to know more, foo?? will give them the Only True Documentation, which happens to include the TESTS block. [x] 'foo?' should NOT display TESTS bloc

[sage-devel] Re: Figuring out imports required when moving from a .sage to a .py file?

Thankyou for all that information. I'm sure I will have some more questions once I have had a chance to chew through all of that. On Tuesday, 6 October 2015 22:17:25 UTC+8, Travis Scrimshaw wrote: > > Something else to consider is that Sage has a preparser and that can come > into play. To see w

[sage-devel] Figuring out imports required when moving from a .sage to a .py file?

x27;t direct me to pynac.py where it is defined. Now I have a slightly more tricky error which will take a bit of reading on my part to debug (. Traceback (most recent call last): File "test.sage.py", line 17, in print(f.fourier(x,k)) File "sage/symbolic/expression.pyx&quo

[sage-devel] Re: Error installing package ncurses-5.9.20131221

> Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > > On Saturday, October 3, 2015 at 10:35:58 AM UTC+2, Tom Kitchen wrote: >> >> I get the following error when trying to compile sage with gcc 5.2. I >

[sage-devel] Error installing package ncurses-5.9.20131221

/tom/sage/logs/pkgs/ncurses-5.9.20131221.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /home/tom/sage/local/var/tmp/sage/build/ncurses-5.9.20131221 and type 'make' or whatever is appropriate. Instead, the fol

Re: [sage-devel] Re: Checker function for integer parameters

Hold on, why do you want to rule out zero? It seems like a dumb thing to do a search at depth zero, but raising an error rather than returning a trivial result is infuriating to a user. On Sat, Sep 26, 2015 at 11:06 AM, John H Palmieri wrote: > > > On Saturday, September 26, 2015 at 10:55:57 AM

Re: [sage-devel] About license of nauty and poset generator

On Tue, Jun 30, 2015 at 11:14 PM, Jori Mäntysalo wrote: > > Maybe. But it would be quite nasty to interpret it that way, if we know that > propably it is not what was meant. You say nasty, I say that's the legal ramification of distributing his code under GPLv3+. We agree on this point, which is

Re: [sage-devel] About license of nauty and poset generator

der the GPL). Best to make sure he knows what he's getting into. On Tue, Jun 30, 2015 at 12:15 PM, William Stein wrote: > On Tue, Jun 30, 2015 at 11:28 AM, Tom Boothby wrote: >> On Tue, Jun 30, 2015 at 11:12 AM, Jori Mäntysalo >> wrote: >> >>> Duh. Then what he m

Re: [sage-devel] About license of nauty and poset generator

On Tue, Jun 30, 2015 at 11:12 AM, Jori Mäntysalo wrote: > Duh. Then what he means when saying that we can ignore it for incorporation > into Sage? Only he can clarify that. If he releases the source under a GPL-compatible license, then we have evidence that he means what he says. His verbal p

Re: [sage-devel] About license of nauty and poset generator

I spoke with Brendan McKay personally less than a month ago. He is fully aware about the restrictions, and utterly unmoved by the difficulty his license creates. On Mon, Jun 29, 2015 at 4:30 AM, Jori Mäntysalo wrote: > More about licenses, see http://trac.sagemath.org/ticket/14110 . This is a >

Re: [sage-devel] Completely remove in-place operations?

If a @cached_method accepts mutable objects, that's a bug. On Tue, Jun 23, 2015 at 12:48 AM, Volker Braun wrote: > On Tuesday, June 23, 2015 at 3:40:24 AM UTC+2, William wrote: >> >> What about something explicit, e.g., >>A.add_inplace(B) >> which would mutate A and be very clear and explicit

Re: (off topic) Re: [sage-devel] The future of polybori

Wow, is that some top-shelf navel lint. Perhaps we should call the language WolframWolframWolfram, or WWW for short. Then, Stephen and Al Gore can fight over who invented what. On Thu, Jun 11, 2015 at 1:28 PM, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: > > On 11 Jun 2015 20:10, "William Ste

Re: [sage-devel] A database of "interesting" graphs

House of Graphs has a similar goal; perhaps it would be better to implement an interface to HoG like we have for OEIS, rather than reinvent the wheel. http://hog.grinvin.org/ -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from thi

Re: [sage-devel] cartesian_product

d'oh, I misread that, and mentally converted cartesian_product to its camelcase variant. On Fri, Mar 6, 2015 at 11:32 AM, William Stein wrote: > On Fri, Mar 6, 2015 at 11:29 AM, Tom Boothby wrote: >> That's never worked. You probably want >> >> sage: ca

Re: [sage-devel] cartesian_product

That's never worked. You probably want sage: cartesian_product([1,2,3], [1,2,3]) On Fri, Mar 6, 2015 at 10:59 AM, William Stein wrote: > Hi, > > I'm unhappy that this doesn't work: > > sage: cartesian_product([[1,2,3], [1,2,3]]) > BOOM! > > It seems clear from the docstring that thi

Re: [sage-devel] Re: The "code of conduct" is getting out of hand - please stop for 2 weeks.

The irony of this is staggering, if not surprising. +1 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this gr

Re: [sage-devel] Re: When/by who/how was the "code of conduct" initiated ?

v 26, 2014 at 8:44 AM, Nathann Cohen wrote: > Volker, Tom: > > Please consider the tone of my first email, and the tone of your answers. > Please consider the "code of conduct" that was just voted. Can you see why I > may feel that you broke it clearly and cleanly at my ex

Re: [sage-devel] When/by who/how was the "code of conduct" initiated ?

Ya know... Nathann. Buddy. Calling out people who may have had complaints that could trigger a discussion about a code of conduct is a bully move. Please avoid doing this in the future. If you want to vent your spleen, you're welcome to do it on sage-flame. On Tue, Nov 25, 2014 at 6:37 PM, Nat

Re: [sage-devel] Re: Code of Conduct

In my mind, "moving a conversation to sage-flame" is a constructive, if imperfect way to handle conversations that are going off the deep end. It's a way that we can flag a conversation as being inappropriate for the tone of sage-devel without pointing fingers. If somebody doesn't want to continu

Re: [sage-devel] Re: Code of Conduct

On Tue, Nov 18, 2014 at 10:36 AM, William Stein wrote: > Given the potentially political nature of such a choice, one > possibility is to do something apolitical, and select based on > ownership. In particular, based on lines of code contributed to Sage, > which is an (imperfect!) but non-politic

Re: [sage-devel] Digest for sage-devel@googlegroups.com - 2 updates in 1 topic

) Target: x86_64-apple-darwin13.1.0 Thread model: posix Best, Tom On 5 April 2014 04:40, sage-devel@googlegroups.com < sage-devel@googlegroups.com> wrote: >Today's topic summary > > Group: http://groups.google.com/group/sage-devel/topics

Re: [sage-devel] Dropping Windows support (phew!!)

had me right until the point I saw "as of today (1/4)."... On Mon, Mar 31, 2014 at 4:56 PM, François Bissey wrote: > On Mon, 31 Mar 2014 19:55:47 Stephen Kauffman wrote: >> On 3/31/2014 7:53 PM, François Bissey wrote: >> > On Mon, 31 Mar 2014 19:50:30 Stephen Kauffman wrote: >> >> On 3/31/2014 7:

Re: [sage-devel] Re: charpoly of sparse matrix

IIRC, the bottleneck to computing the spectra of large graphs is in the construction of the adjacency matrix. I don't know why. On Wed, Mar 26, 2014 at 3:28 PM, Paul Mercat wrote: > Le mercredi 26 mars 2014 22:56:46 UTC+1, Dima Pasechnik a écrit : >> >> On 2014-03-26, Paul Mercat wrote: >> > >>

Re: [sage-devel] Re: M4RI GPL → LGPL (?)

lol... IIRC, William has gotten a few libraries to change their licenses. It is a genuine request, and there is no blackmail here. On Sun, Mar 16, 2014 at 11:23 AM, Volker Braun wrote: > As far as Sage is concerned, anything that is GPLv3 compatible is fine (this > includes LGPL). > > I don't un

Re: [sage-devel] coding style: should foo.is_blah(...) be allowed to return nonboolean?

By default, I agree with you -- foo.is_blah() should be boolean. However, I agree with Nathann. When there are extra parameters, we should be able to return other stuff. On Thu, Feb 27, 2014 at 6:51 AM, Dima Pasechnik wrote: > I am reviewing http://trac.sagemath.org/ticket/15864 > and it occurs

Re: [sage-devel] wolfram language

On Thu, Feb 27, 2014 at 8:31 AM, Dr. David Kirkby wrote: > > I like the fact the picture on his desktop is of him. > > Dave Isn't yours? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fr

Re: Re: [sage-devel] Sherlock

On Sun, Jan 5, 2014 at 2:47 PM, Martin Albrecht wrote: >> I remember that dinner... where I had license discussions with an >> intoxicated Germans... > > Makes sense: as far as I know the Sage rule is you're *only* allowed to > discuss licenses if you are intoxicated. I'm going to have to disag

Re: [sage-devel] Removing the Graph "boundary" parameter

The boundary code does get used... though it's fairly specialized -- it's for the UW Math REU. On Sun, Dec 8, 2013 at 2:58 AM, Nathann Cohen wrote: > Hell everybody !! > > While working on #15278, Simon rediscovered the "boundary" graph parameter. > Turns out that there is a line is G

Re: [sage-devel] Re: Gray code

Well too darned bad, 'cause I'm gonna share the magic formula I just found anyway: [((i&-i)-1).popcount() for i in srange(1,2^n)] from http://aggregate.org/MAGIC/ On Fri, Dec 6, 2013 at 6:42 AM, Nathann Cohen wrote: > Yo !! > >> Yes indeed -- with a formula like that, there's little re

Re: [sage-devel] Re: Gray code

On Thu, Dec 5, 2013 at 9:50 PM, Nils Bruin wrote: > It will be very hard to beat the simple closed formula > > ( (i>>1) ^^ i for i in xrange(2^n) ) > Yes indeed -- with a formula like that, there's little reason not to implement it ad-hoc every time. Unless a user wants it, and doesn't know thi

Re: [sage-devel] making tuples in cython

On Mon, Oct 21, 2013 at 11:03 AM, Robert Bradshaw wrote: > You can iterate over a vector using "for x in ..." rather than indexing > though. > Nice. I do love cython. Every time I use it for something new, I learn that features "just work" that I never thought to try. Thanks for your help! -

Re: [sage-devel] making tuples in cython

or[int]] M): return M def identity(tuple t): return tupletuple(t) On Mon, Oct 21, 2013 at 10:28 AM, Tom Boothby wrote: > lol, really? Can I then toss that back to python? > > On Mon, Oct 21, 2013 at 10:19 AM, Robert Bradshaw > wrote: >> How about >> >>

Re: [sage-devel] making tuples in cython

lol, really? Can I then toss that back to python? On Mon, Oct 21, 2013 at 10:19 AM, Robert Bradshaw wrote: > How about > > cdef tupletuple(vector[vector[int]] M): > return M > > On Mon, Oct 21, 2013 at 8:48 AM, Tom Boothby wrote: >> I'm working on overh

[sage-devel] making tuples in cython

I'm working on overhauling a class (see [1]) that wraps some c++, and I've got just about everything working how I want... but I have a nagging doubt about performance. Is the following fast? Can it be made fast without a bunch of ugly python c-api stuff? cdef tupletuple(vector[vector[int]] M):

Re: [sage-devel] Re: We need a new color?

raise RuntimeError,"Could not obtain comic data from %s . Maybe you should enable time travel!"%url You gave up on this too early, IMO. I'd "from __future__ import *" and then try the url again. For the more pragmatic, you can fairly accurately predict when that url will come live, and just slee

Re: [sage-devel] Inverse of discrete functions

Thu, Sep 26, 2013 at 12:03 PM, Nils Bruin wrote: > On Wednesday, September 25, 2013 9:59:46 AM UTC-7, Tom wrote: >> >> For iso/automorphisms of graphs, I often wish that dictionaries were >> both callable and invertible. In general, yes, I think >> DiscreteFunction and

Re: [sage-devel] Inverse of discrete functions

If the dictionary is a bijection, I use: {v:k for k,v in d.iteritems()} Otherwise, I use defaultdict: d_inv=defaultdict(list) map(lambda(k,v):d_inv[v].append(k), d.items()) For iso/automorphisms of graphs, I often wish that dictionaries were both callable and invertible. In general, yes, I think

Re: [sage-devel] Re: Is the glass half-full or half-empty ? Pick a standard.

I will argue against False. We've had the convention that Graph().is_connected() is True for the last n years. This was an arbitrary (if heedless) choice at the boundary of several definitions. It doesn't seem to be an undue source of bugs, so the only impact of changing this arbitrary choice to

Re: [sage-devel] Sage logic code

I have a script I use to convert a boolean function into an equivalent CNF boolean function so I can use a SAT solver on arbitrary boolean functions. I hoped to use SymbolicLogic, but it was so lacking, I rolled my own. Off with its head! On Thu, Jul 11, 2013 at 3:07 PM, William Stein wrote: >

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

Indeed, the whole reason many of us do any work on Sage is to help our research projects. The principle of helping Sage to help our individual mathematical pursuits is actually what makes it consistently stronger as a system. Find Stat is a great tool for the community, and I think there are o

[sage-devel] Re: Paper publication of the book "Calcul Mathematique avec Sage"

Congratulations! This reminds me that I need to work on my paper interface to the Sage Cell Server. :) On Wednesday, June 12, 2013 12:18:21 AM UTC+3, Dox wrote: > > Great work! Congratulations! > -- You received this message because you are subscribed to the Google Groups "sage-devel" group.

[sage-devel] Re: Consistent failure of zn_poly in latest Sage

week, another OS X 10.6.8 system with somewhat newer specs. I attributed it to the presence of Nicolas Thiery & Anne Schilling in the room during most of the compile, but perhaps there are some other places where I should be looking for differences in my systems to explain this? Tom

[sage-devel] Error installing package zn_poly-0.9.p10 on Mac OS 10.6.8

relevant. Thanks for any light anyone can shed on this! Tom Found package zn_poly-0.9.p10 in spkg/standard/zn_poly-0.9.p10.spkg zn_poly-0.9.p10 Extracting package /Applications/sage-5.8/spkg/standard/zn_poly-0.9.p10.spkg -rw-r--r--@ 1 tr

Re: [sage-devel] Re: cpdef (a little) harmful

On Tue, Apr 9, 2013 at 1:44 PM, Nils Bruin wrote: > Since it is entirely unclear from that tutorial what the factor 20 (or > the factor 10) refers to, I would not have understood that code to > mean "even the fastest path of a cpdef function is slower than a > cdef". There is a lot of documentati

Re: [sage-devel] cpdef (a little) harmful

This shouldn't really come as a surprise. From the Cython documentation, "This is about 20 times slower, but still about 10 times faster than the original Python-only integration code. This shows how large the speed-ups can easily be when whole loops are moved from Python code into a Cython modul

Re: [sage-devel] Signal handling

xecute arbitrary machine code from > within Sage, so you need to have a plan for how to isolate it from the web > frontend. Importing it all into one process is a bad idea. > > On Friday, March 29, 2013 7:23:10 AM UTC, tom d wrote: >> >> I'm trying to import t

Re: [sage-devel] Signal handling

Hm, the issue is that there's really big startup costs for Sage; it looks based on my cursory understanding of subprocess that there's a couple seconds of hang-time for each calculation one wants to execute. This doesn't really scale. I know there's something involving spawning a pile of kern

Re: [sage-devel] Signal handling

h 29, 2013 10:23:10 AM UTC+3, tom d wrote: > > Cool, I'll give the patch a shot. It looks like some other projects have > a variable or option for disabling interrupts for exactly this reason; if a > patch works, it might make sense to do signals optionally in Sage. > &

Re: [sage-devel] Signal handling

wrote: > > On 03/28/2013 11:44 PM, tom d wrote: > > The problem seems to be at: > > from sage.ext.c_lib import _init_csage, sig_on_count > > _init_csage() > > which is explicitly using the signal library and doing signal handling > > stuff for Sage. Any

[sage-devel] Signal handling

Hello! I'm trying to run Django inside of the Sage python and import the sage libraries. (Idea: "Hey, look, a web server that can find derivatives!") The Django install into my Sage install went fine, but I'm getting an error when trying to import the Sage libraries: http://dpaste.com/1038581

[sage-devel] Re: a problem in the new permutation groups code (and a solution ?)

'Allo! On Tuesday, March 26, 2013 1:34:32 PM UTC+3, Volker Braun wrote: > > The group action framework is just the implementation, you still haven't > answered the question that this thread was about: Should permutation > actions on nested containers automatically discover one possible action or

[sage-devel] Re: a problem in the new permutation groups code (and a solution ?)

oops, here's the code! I keep getting server erros when trying to attach as a file, so I'm just including the text of the code file below: class GroupAction(Parent): def __init__(self, G, S, phi): #phi a group action G\times S \rightarrow S self.phi=phi self.G=G

[sage-devel] Re: a problem in the new permutation groups code (and a solution ?)

t; exactly the same question that Dima asked: What are you going to do if > there is more than one possible action. You'll have to either use some > heuristics (take the simpler / less nested action) or raise some exception > telling the user to explicitly disambiguate between them.

[sage-devel] Re: a problem in the new permutation groups code (and a solution ?)

Hm, wouldn't this just be a direct product of the individual group actions? It seems to me that we're expecting the permutations to act according to an 'obvious' group action. Should we also expect 'obvious' actions of things like a dihedral group when given a 2-dimensional vector? Probably

[sage-devel] Re: strange behavior of sage

Yes, I would support such a warning; I've even led tutorials with new sage users where defining things called 'max' or 'min' has seemed an obvious thing to do and then minutes later been a problem as the default function was unavailable. On Tuesday, March 5, 2013 12:36:33 AM UTC+3, luisfe wrote

[sage-devel] Re: Longest element in a Coxeter Group - name decision

I think longest_element is fine; long_word indicates that there will be a word returned instead of an element, which is maybe not what we're after here. Wiser minds than mine will have more knowledge of how to handle deprecation, but here's an example from skew_partition.py: sage: x.r_quotient

Re: [sage-devel] Falso

No worries. I just proved that Sage does not infringe Estatis Inc.'s intellectual property. We're cool. On Mon, Feb 18, 2013 at 5:23 PM, kcrisman wrote: > > How did we ever get along trying to prove theorems with more than one axiom? > > http://www.eleves.ens.fr/home/amarilli/falso/ > > Sage r

[sage-devel] Re: Sage-5.2 on raspberry pi

ing a line to the Raspian folks and asking them to make such a link in the Raspbian image. Best, -tom On Monday, January 28, 2013 5:54:42 PM UTC+3, Dima Pasechnik wrote: > > On 2013-01-28, Dan > wrote: > > --=_Part_291_16107307.1359380648388 > > Content-Type: text/p

[sage-devel] Re: Sage 5.6 on ARM

I can confirm that this same numerical noise (binomial, gamma functions) happens on the ARM6 on the Raspberry Pi, running the 'raspian' distro. (Which isn't Ubuntu, though it is a Debian derivative.) On Monday, January 28, 2013 1:55:30 PM UTC+3, Dima Pasechnik wrote: > > On 2013-01-28, Julien P

Re: [sage-devel] Graph theory roadmap

Jernej, While somebody is at this, Maple has graphs, too. On Wed, Jan 23, 2013 at 11:52 AM, Jernej Azarija wrote: > Hello! > > This question is related to the following page > http://trac.sagemath.org/sage_trac/wiki/GraphTheoryRoadmap > > As one can see the last time it was modified was 3 years

Re: [sage-devel] Should sage -b run sage -sync-build to get rid of outdated .py and .pyc files?

Another possible solution would be to change the error message one gets on a failed import statement. (I also lost hair on this issue a couple days ago.) Right now it says 'have you tried %upgrade?' or something similar; it could include the recommendation to -sync-build. On Sunday, January 2

[sage-devel] Sage-5.2 on raspberry pi

After many trials and tribulations, I've finished a build of Sage-5.5 for the Raspberry Pi. I'm still running the doctests; I've only seen timeouts so far, which is quite positive. I'm unsure how long the full (long) testsuite will take to run, but will post an update when it finishes. If an

Re: [sage-devel] raspberry pi build fails - ARM

ilable will help with the compilation time. Best, -tom On Wednesday, January 2, 2013 10:27:21 AM UTC+3, Don Harter wrote: > > I ran the compile again after shutting down several services. I also > shut down a swap file so that it would only have swap disk partitions to > use. > I

Re: Re: [sage-devel] Re: Sage 5.4 on ARM

And I'm on a truly measly 256mb of RAM, but with 2gb swap. Thanks for taking some time to consider this! On Monday, December 24, 2012 2:53:56 PM UTC+3, Martin Albrecht wrote: > > On Monday 24 Dec 2012, tom d wrote: > > Man, still no success in getting through the libm4rie b

Re: [sage-devel] Re: Sage 5.4 on ARM

it becomes available to every 10-20 year old nerd with $35+ to burn on a new machine.. I'm personally looking at deploying in rural schools in Western Kenya. Best, -tom On Thursday, December 20, 2012 12:47:53 AM UTC+3, Snark wrote: > > Le 19/12/2012 21:52, tom d a �crit : &

[sage-devel] Re: Sage 5.4 on ARM

yone have a good idea of where to look? cheers! -tom On Thursday, December 13, 2012 2:35:52 PM UTC+3, mmarco wrote: > > jaebond, did you try the image i linked? did it work for you? > > On 9 dic, 10:56, mmarco wrote: > > I have made a zip archive with both the image and the s

Re: [sage-devel] A product() analogue to sum()

prod() does just what you want. On Tue, Dec 4, 2012 at 5:53 PM, Michael Orlitzky wrote: > I've been carrying this around in my init.sage. Is there really nothing > like it in the library? If not, any reason not to add it? > > ## > > from functools import reduce > > def product(factors): > """

Re: [sage-devel] Extra loop created in a graph

Hey Rob, I ran into something similar a little while back in sage-5.0 sage: G = Graph([(0,1,0),(0,1,0)]) sage: G.num_edges() 4 but IIRC, it was fixed in 5.3. On Wed, Nov 28, 2012 at 8:02 PM, Rob Beezer wrote: > Anybody recognise this bug? I don't see anything in Trac. > > T=[(0, 2, '0'), (3,

[sage-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries

the first week I'll be in Ethiopia.) Basically, drop me a line and we can talk about scope and further details that should be nailed down. Best, -tom On Sunday, November 11, 2012 12:00:34 PM UTC+3, Nicolas M. Thiery wrote: > > Dear Sage devs, > > The fall school on D

[sage-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries

and a couple good text editors, making a good case for general linux use. As a last note, there's an algebraic geometry workshop happening in Mombasa, Kenya, sometime between May and June next year; I'm trying to figure out what the dates are now! We could potentially try some thing

[sage-devel] Re: Sage-Combinat days in Paris, June 2013

It's looking like there's a good chance that I'll be able to come through! On Friday, September 28, 2012 11:12:05 AM UTC+3, Nicolas M. Thiéry wrote: > > Dear Sage / Sage-Combinat fans, > > FPSAC (Formal Power Series and Algebraic Combinatorics) is the main > yearly international conferen

Re: [sage-devel] Re: Testing if a graph is edge-transitive

Nah, I'll pick up some review credit. On Sun, Nov 18, 2012 at 10:16 PM, Jernej Azarija wrote: > Tom, > > I have created a patch implementing the edge/arc transitive tests. I > mentioned on the wiki page that the main idea of the test was suggested by > you, but in case y

Re: [sage-devel] Re: Testing if a graph is edge-transitive

Thank you, Jernej, for bringing up this issue. Turns out I've been lazy, and hadn't carefully thought about degenerate cases. The line graph is a bad test because the claw and triangle have the same line graph... the disconnected pair (claw + C_3) has a vertex-transitive line graph! The followin

Re: [sage-devel] Re: Testing if a graph is edge-transitive

12-10-30, Jernej Azarija wrote: >> --=_Part_1698_7171753.1351582604933 >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Monday, 29 October 2012 22:49:03 UTC+1, Tom wrote: >>> >>> Here's a list of 21 edge-transitive graphs on 6 vertices. >&g

Re: [sage-devel] Testing if a graph is edge-transitive

rection to OEIS. On Tue, Oct 30, 2012 at 12:36 AM, Jernej Azarija wrote: > > > On Monday, 29 October 2012 22:49:03 UTC+1, Tom wrote: >> >> Here's a list of 21 edge-transitive graphs on 6 vertices. >> >> "E???" # 6 K_1 >> "E_??" # K_2

Re: [sage-devel] Testing if a graph is edge-transitive

29, 2012 at 12:37 PM, Jernej Azarija wrote: > This works yes. However it still leaves open what is going on with > disconnected graphs and what is the problem with the proposed > is_edge_transitive method! > > Do you (or anyone) happens to see a bug or a bizarre mistake in the > implem

Re: [sage-devel] Testing if a graph is edge-transitive

Sorry, I meant n=8. sage: print [ec(n) for n in range(9)] [1, 1, 1, 2, 3, 4, 6, 5, 8] On Mon, Oct 29, 2012 at 11:41 AM, Tom Boothby wrote: > Wanna run that on connected graphs? I get the correct sequence out to n=9 for > > def ec(n) > c = 0 > for g in graphs(n

Re: [sage-devel] Testing if a graph is edge-transitive

gt; sage: ec(8) > 39 > > But there are 26 and 40 edge-transitive graphs on 7 and 8 nodes > respectively. It appears as if something is wrong with the computation of > the automorphism group of a graph. > > Can someone comment on that? > > > > > &g

Re: [sage-devel] Testing if a graph is edge-transitive

I use G.line_graph().is_vertex_transitive() On Mon, Oct 29, 2012 at 7:12 AM, Jernej Azarija wrote: > Hello! > > I am slowly implementing a patch that will provide some features for > symmetry testing of graphs. > > However I am already puzzled by the following attempt at testing for > edge-transi

Re: [sage-devel] Please review: new ANF2CNF converter (#13558)

Philipp, The ticket already has some comments from Martin -- it needs doctests, etc. When I looked at the code, I found the documentation about the various substitution strategies. The docstrings should list the strategies and give an explanation for how they work. Regards, Tom On Thu, Oct

Re: [sage-devel] Sage (tm)

So, the deadline came and went -- what happened? On Sat, Jun 2, 2012 at 12:26 PM, Fernando Perez wrote: > On Sat, Jun 2, 2012 at 9:43 AM, Robert Bradshaw > wrote: >> It's also much >> better to make it official now, when ownership is not being >> questioned, than at some later date when it is n

Re: [sage-devel] Sage (tm)

Found a nice feature of Python's approach. License for this Policy Interested parties may adapt this policy document freely under the Creative Commons CC0 license: On Thu, May 31, 2012 at 11:50 PM, Tom Boothby wrote: > Thanks, Martin, I hadn't thought about that -- Debian/Ic

Re: [sage-devel] Sage (tm)

Thanks, Martin, I hadn't thought about that -- Debian/IceWeasel is an excellent example of things that can go wrong. Trademarks are useless if impinged and not challenged. If people start making SageThis and SageThat, we may lose control. Per the norm, when sticky legal questions arise, I think

Re: [sage-devel] Re: Sage (tm)

I think this makes a lot of sense from a legal perspective (IANAL). My only concern is: how legally binding is asking this question on sage-devel with a 5-day turnaround? On Thu, May 31, 2012 at 4:08 PM, William Stein wrote: > On Thu, May 31, 2012 at 12:20 PM, Jason Grout > wrote: >> On 5/31/12

Re: [sage-devel] Re: SAT and MAXSAT in Sage

At one point, Victor Miller, William Stein and I looked at interfacing directly to minisat, but IMO, we stopped due to a lack of a nice interface. I've tried to rewrite my SAT approach every time I solve a new problem with SAT solvers -- forcing me to rethink it every time. In general, I've gotte

Re: [sage-devel] April Fool's Day

Oh man, that's a shame. I really thought we were gonna get a real productivity boost out of spooning. And, of course, knifing. On Mon, Apr 2, 2012 at 6:38 AM, Jason Grout wrote: > Just so we are clear, some (but not all) of the posts yesterday were jokes > posted as part of the "April Fool's Da

Re: [sage-devel] Wolfram on Reddit

On Tue, Mar 13, 2012 at 8:30 AM, David Kirkby wrote: > On 13 March 2012 13:42, Tom Boothby wrote: >> On Tue, Mar 13, 2012 at 6:29 AM, David Kirkby >> wrote: > >>>> Two years ago, few would believe that a computer could win Jeopardy, >>>> much less

Re: [sage-devel] Wolfram on Reddit

On Tue, Mar 13, 2012 at 6:29 AM, David Kirkby wrote: > On 12 March 2012 01:57, Tom Boothby wrote: >> On Sun, Mar 11, 2012 at 12:01 PM, Dr. David Kirkby > >>> I take exception to what he said: >>> >>> "It'll probably be related to my goal

Re: [sage-devel] Wolfram on Reddit

On Sun, Mar 11, 2012 at 12:01 PM, Dr. David Kirkby wrote: > On 03/11/12 05:00 PM, Volker Braun wrote: >> >> On Saturday, March 10, 2012 3:59:24 PM UTC-5, Dr. David Kirkby wrote: >>> >>> >>> HARD >>> C++, Mathematica >>> >> The Mathematica language is just difficult because its ugly and uses weird

Re: [sage-devel] Re: Literal matrix syntax

On Thu, Jan 26, 2012 at 5:15 PM, David Roe wrote: >>> Another issue: do we allow [1..10; 10..20]? >> >> We probably shouldn't go to extra effort to support it. >> >>> I can't seem to construct >>> matrices with matrix entries (this is not absurd) -- but should the >>> preparser grok it? [[1..10; 1

Re: [sage-devel] Re: Literal matrix syntax

On Thu, Jan 26, 2012 at 3:21 PM, Robert Bradshaw wrote: > On Thu, Jan 26, 2012 at 3:08 PM, Tom Boothby wrote: >> On Thu, Jan 26, 2012 at 2:36 PM, Robert Bradshaw >> wrote: >>> On Thu, Jan 26, 2012 at 1:51 PM, Michael Orlitzky >>> wrote: >>&g

Re: [sage-devel] Re: Literal matrix syntax

t the bar for inclusion >> should be pretty high. > > I totally agree with you here, the bar for adding to the preparser > should be high. I think it's a good candidate here because (1) It's > easy to understand what it means (2) it's illegal Python syntax, and >

Re: [sage-devel] Re: Literal matrix syntax

On Thu, Jan 26, 2012 at 12:09 PM, Jason Grout wrote: > Another option would be: > > [QQ: 1,2,3; 4,5,6] QQ:1 is a slice... > or, as Robert suggests: > > [1,2,3; 4,5,6, base_ring=QQ] -- but then it looks like base_ring=QQ is > another element. assignments aren't literals... but I don't like this

Re: [sage-devel] Re: Literal matrix syntax

On Thu, Jan 26, 2012 at 10:13 AM, Robert Bradshaw wrote: > To get a quick sense of what people think about this, I've decided to > rephrase this as a survey.  To be clear, though this coincides with > Matlab syntax, the intent is not to try to make Sage a Matlab clone, > rather it is to add a miss

Re: [sage-devel] graph isomorphism checking with labeled (or colored) vertices

Jason, I've been working with nonisomorphic colorings recently. I use the following: def canonical_coloring_label(G,c): """ Given a coloring dictionary, {color1 : [u1, u2, ...], color2 : [v1, v2, ... ], ... } return a string which uniquely identifies the isomorph

Re: [sage-devel] Executive decision needed

By this logic, no bugs should be fixed, because they aren't covered in the warranty... this isn't a healthy attitude. On Tue, Jan 3, 2012 at 2:39 PM, Michael Orlitzky wrote: > This is an old ticket to catch misspellings of 'sage:' in doctests: > >  http://trac.sagemath.org/sage_trac/ticket/6439 >

Re: [sage-devel] Re: Proposal for faster linear algebra over GF(q), q<255 odd and non-prime

On Wed, Nov 30, 2011 at 6:52 AM, Simon King wrote: > Hi Dima, > > On 30 Nov., 15:29, Dima Pasechnik wrote: >> I might get blamed for making discouraging remarks, but let me play the >> devil's advocate: >> >> I wonder if these kinds of speed-ups are to be beaten, soon, by >> sufficiently fast har

Re: [sage-devel] Re: Fwd: C compiler in Mathematica

On Thu, Nov 24, 2011 at 9:25 PM, rjf wrote: > > William seems to prefer to tout the Sage-Cython link. That's because we use Cython, and it's easy to use in Sage, and provides a fully-functional language-native interface between Cython and Sage. Not a single part of that is true about the Maxima

Re: [sage-devel] 90% doctest coverage thrust

I'll doctest polynomial_compiled this week, since it's 100% my fault. On Sun, Nov 13, 2011 at 12:41 PM, William Stein wrote: > Hi Sage Developers, > After deleting the server directory we need to add doctests to > about588 more functions to get coverage to 90%, which is a major goal > forsage-5.0

  1   2   3   4   >