Re: [sage-support] Re: Serious bug in Graph.modular_decomposition (which propagates to Graph.is_prime)

Hello ! > Thank you very much. With your help I was able to compile the library from > the "new" sources and it is working properly now, although just for me of > course. "Good" :-P > I understand your disappointment because of not being able to solve > the issue for everybody. > > I am willing

[sage-support] Sage find_root error

Don't know why but find_root(x*tan(x), -1, 5) gives me 1.570796 which is incorrect, since it is pi/2, the value at which tangent doesn't exist. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving em

Re: [sage-support] Re: Serious bug in Graph.modular_decomposition (which propagates to Graph.is_prime)

Hi Nathann, Thank you very much. With your help I was able to compile the library from the "new" sources and it is working properly now, although just for me of course. I understand your disappointment because of not being able to solve the issue for everybody. I am willing to write to the aut

Re: [sage-support] Re: Serious bug in Graph.modular_decomposition (which propagates to Graph.is_prime)

Hello ! > I would like to know if there is any workaround for solving this issue for > version 6.6. Unfortunately, there is no dm.c and no random.c in the sage 6.6 > directory structure so as to replace them and so I do not know how to > proceed. Sigh... Modular decomposition. A story of many dis

Re: [sage-support] Re: Serious bug in Graph.modular_decomposition (which propagates to Graph.is_prime)

Dear Nathann, I have just installed sage 6.6 and found out that the bug is still there and that I am not able to apply the same workaround as before. I used to replace dm.c and random.c, apply touch to modular_decomposition.pyx and do sage -b. That used to be enough. But I do not know how to re

[sage-support] Re: A typo in command line options for Sage

this is now https://github.com/sagemath/sage/pull/40 On Saturday, 2 May 2015 08:27:37 UTC+1, Han Xiao wrote: > > I think in line 46 and line 139 of the command line options for Sage > sage/src/bin/sage > > it should be 'current' instead

Re: [sage-support] bug in Graph is_subgraph method

If you consider the documentation of the function you will see def is_subgraph(self, other, induced=True): """ Tests whether ``self`` is a subgraph of ``other``. .. WARNING:: Please note that this method does not check whether ``self`` contains a subgraph *isomorphic

[sage-support] A typo in command line options for Sage

I think in line 46 and line 139 of the command line options for Sage sage/src/bin/sage it should be 'current' instead of 'currend', even though I'm not a native English speaker. -- You received this message because you are subscribed

[sage-support] bug in Graph is_subgraph method

Graph("E`oo") is the disjoint union of 2 triangles. Graph("ExSW") is two triangles with 2 more edges connecting them. So the first graph is a subgraph (a non-induced subgraph) of the second graph. But Sage reports that it is not. Both graphs have order 6. sage: h=Graph("E`oo") sage: g=Graph("Ex