Re: [sage-combinat-devel] Re: trac_12453-refactor_integer_vectors-ts.patch does not apply
Hi Travis, Well, it still does not work: applying trac_8386_big_clean_fc.patch applying trac_8386_assert_removal.patch applying trac_14864-descents_composition_of_empty_permutation-cs.patch patching file sage/combinat/permutation.py Hunk #1 FAILED at 2215 1 out of 1 hunks FAILED -- saving rejects to file sage/combinat/permutation.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_14864-descents_composition_of_empty_permutation-cs.patch Abort Best, Anne On 7/8/13 6:56 AM, Travis Scrimshaw wrote: Hey Anne, I caught this (I forgot to qrefresh) and pushed. Best, Travis On Sunday, July 7, 2013 10:19:53 PM UTC-7, Anne Schilling wrote: Travis, Sorry to say, but the queue does not apply! Anne patching file sage/combinat/all.py Hunk #1 succeeded at 64 with fuzz 2 (offset 0 lines). applying trac_12453-refactor_integer_vectors-ts.patch patching file sage/combinat/tableau.py Hunk #4 FAILED at 581 Hunk #5 FAILED at 1555 Hunk #6 FAILED at 1876 3 out of 6 hunks FAILED -- saving rejects to file sage/combinat/tableau.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_12453-refactor_integer_vectors-ts.patch Abort -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] trouble installing graphviz on combinat
I just did apt-get install graphviz graphviz-doc, so graphviz is now installed system-wide. This may make it so you don't have to build it from source. Fantastic! Thank you very much! Anne -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: SageManifolds: differential geometry and tensor calculus in Sage
Le dimanche 7 juillet 2013 10:39:30 UTC+2, vdelecroix a écrit : Cool! It looks nice. How do you intend to define a manifold: numerically (via fine triangulations) or via symbolic expressions? Both? At the moment, a manifold is mostly defined as a set of charts with the associated transition maps, the latter being given by symbolic expressions. But why not adding the possibility to define a manifold numerically as you mention ? Are you aware of #9439 (hyperbolic geometry) and #10132 (surfaces embedded in R^3) which are somewhat related? Thanks for pointing these two packages; they are definitevely relevant to our project. I did not know #9439 and will give a look. Regarding #10132, it differs from SageManifolds in various points: - the chart on the surface is fixed, as well as the chart in the embedding space (R^3), while in SageManifolds various charts can be used on the same manifold; also various vector frames can be used to expand tensors, not only coordinate bases. - it implements extrinsic geometry, which SageManifolds does not do yet (but should do soon) (cf. Joris Vankerschaver's message). Eric. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: UTF-8 and old terminals (new startup banner)
On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote: Frédéric Chapoton has written a patch at http://trac.sagemath.org/14733that will beautify the Sage startup banner using some UTF-8 characters to draw the box. This will display incorrectly in terminals that do not support UTF-8. In that case, Sage still works but the box around the banner is garbled (most likely rendered by placeholder signs for non-ASCII characters). -1 to a UTF-8 banner. There's hardly anything in the sage command line that requires a UTF-8 capable terminal (all the colour stuff should shut off automatically for a dumb terminal). Why require it for *just* the banner? More personally, I dislike the UTF-8 banner because it looks too nice. To me it doesn't fit with the simple prompt-and-return-value interface (see banners of magma, maple, R, matlab, pari/GP, python, IPython, GAP, Singular). The graphics looking lines are more suggestive of a menu-driven interface to me, like the text-based dialog interfaces. So to me, the +-|-built borders raise expectations more appropriate for what sage command line offers. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
Le 08/07/2013 10:51, Nils Bruin a écrit : On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote: Frédéric Chapoton has written a patch at http://trac.sagemath.org/14733 http://trac.sagemath.org/14733 that will beautify the Sage startup banner using some UTF-8 characters to draw the box. This will display incorrectly in terminals that do not support UTF-8. In that case, Sage still works but the box around the banner is garbled (most likely rendered by placeholder signs for non-ASCII characters). -1 to a UTF-8 banner. There's hardly anything in the sage command line that requires a UTF-8 capable terminal (all the colour stuff should shut off automatically for a dumb terminal). Why require it for *just* the banner? More personally, I dislike the UTF-8 banner because it looks too nice. To me it doesn't fit with the simple prompt-and-return-value interface (see banners of magma, maple, R, matlab, pari/GP, python, IPython, GAP, Singular). The graphics looking lines are more suggestive of a menu-driven interface to me, like the text-based dialog interfaces. So to me, the +-|-built borders raise expectations more appropriate for what sage command line offers. -1 too for the same reasons. Keep the banner short and simple ; people don't come to sage to enjoy that sight! Snark on #sagemath -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: Error installing package matplotlib-1.2.1
Le dimanche 7 juillet 2013 22:06:12 UTC+1, Paul Mercat a écrit : As it's recommanded, I give here the error I get when I try to compile sage 5.10 on my MacBook pro : ld: library not found for -lpng The problem comes from the fact that there should be a library libpng somewhere but the compiler was not able to find it. It looks like the problem in http://stackoverflow.com/questions/12630593/g-linking-with-libpng. I let the mac expert answer to this. I would like very much to fix this problem, because I would like to participate to the developpement of sage (for example to add finite state automatons). Cool! Regarding finite state automatons, there is yet a patch which handles this at http://trac.sagemath.org/sage_trac/ticket/12996 which is almost finished (and as you are hyperbolic you may like http://trac.sagemath.org/sage_trac/ticket/9439). Best Vincent -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
Le 08/07/2013 10:51, Nils Bruin a écrit : On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote: Frédéric Chapoton has written a patch at http://trac.sagemath.org/14733 http://trac.sagemath.org/14733 that will beautify the Sage startup banner using some UTF-8 characters to draw the box. This will display incorrectly in terminals that do not support UTF-8. In that case, Sage still works but the box around the banner is garbled (most likely rendered by placeholder signs for non-ASCII characters). -1 to a UTF-8 banner. There's hardly anything in the sage command line that requires a UTF-8 capable terminal (all the colour stuff should shut off automatically for a dumb terminal). Why require it for *just* the banner? More personally, I dislike the UTF-8 banner because it looks too nice. To me it doesn't fit with the simple prompt-and-return-value interface (see banners of magma, maple, R, matlab, pari/GP, python, IPython, GAP, Singular). The graphics looking lines are more suggestive of a menu-driven interface to me, like the text-based dialog interfaces. So to me, the +-|-built borders raise expectations more appropriate for what sage command line offers. Is the banner of R so simple? Probably it does not use UTF8, but it speakes your mother's language (French in my case)... -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. attachment: tdumont.vcf
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
IIRC the new GAP banner uses UTF-8. On Monday, July 8, 2013 11:28:23 AM UTC+2, tdumont wrote: Le 08/07/2013 10:51, Nils Bruin a �crit : On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote: Fr�d�ric Chapoton has written a patch at http://trac.sagemath.org/14733 http://trac.sagemath.org/14733 that will beautify the Sage startup banner using some UTF-8 characters to draw the box. This will display incorrectly in terminals that do not support UTF-8. In that case, Sage still works but the box around the banner is garbled (most likely rendered by placeholder signs for non-ASCII characters). -1 to a UTF-8 banner. There's hardly anything in the sage command line that requires a UTF-8 capable terminal (all the colour stuff should shut off automatically for a dumb terminal). Why require it for *just* the banner? More personally, I dislike the UTF-8 banner because it looks too nice. To me it doesn't fit with the simple prompt-and-return-value interface (see banners of magma, maple, R, matlab, pari/GP, python, IPython, GAP, Singular). The graphics looking lines are more suggestive of a menu-driven interface to me, like the text-based dialog interfaces. So to me, the +-|-built borders raise expectations more appropriate for what sage command line offers. Is the banner of R so simple? Probably it does not use UTF8, but it speakes your mother's language (French in my case)... -- 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+...@googlegroups.com javascript:. To post to this group, send email to sage-...@googlegroups.comjavascript:. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences
Hi, I do like the project find_stat but do not like the way it intends to do it. In that sense, I mostly agree with Nathann objections. Following Thierry, why combinatorial maps are not implemented as morphisms between two proper parents ? We could add some semantic to morphisms (injectivity/surjectivity/bijectivity, ...) which is definitely useful. Note that some semantic is already there as a morphism might be a map between sets or a map between between graded objects. It is possible to implement a decorator that actually creates a morphism from a method (@morphism_from_method) and cache it somewhere. I think that it should not transform a method to a combinatorial map (which was one of the main Nathann's objection) but it might be useful that such decorator exists. Then, the problem is what method is not an actual morphism between two parents (do we want decorators everywhere) ? Where do we register the morphisms (in the parent, in a database) ? Another problem is that given a parent, it is not possible to determine all the morphisms from or to that parent (possible here means that such function will never exists, because most of the objects and morphisms are dynamically created with the coercion framework and that set of morphisms is potentially infinite). Nevertheless, coercion framework takes care about somewhat natural morphisms and combinatorial maps are somewhat opposite (ie non trivial transformations). But still, some semantic might be applied to coercion morphisms. There are several obstruction to such project: - an object (let say the partition [3,2,1]) may have several parent (Partitions of 6, Partitions graded by the length, ...) but the combinatorial map exists somewhat independently of the parent - we need to convince Nathann that it would be good to have the parent Graphs ;-) Best Vincent -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
On Monday, July 8, 2013 11:33:18 AM UTC+2, Jean-Pierre Flori wrote: IIRC the new GAP banner uses UTF-8. You're right. With (to me) the same jarring effect, so I don't like it. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
If we allow an UTF-8 banner then we may also allow UTF-8 string representations for Sage objects (why not?). But I think we do not want to force the user to have UTF-8 output because it is always harder to parse an UTF-8 string than an ASCII string (this argument is also valid for the Sage banner). It might be useful to have two console modes, ASCII and unicode, and I have no objection of having unicode as default. Finally, I strongly believe that we do not want to change the sage-banner at each release. Vincent -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: SageManifolds: differential geometry and tensor calculus in Sage
Impressive work! I started improving my programming skills to try implementing the Hodge star on DifferentialForms, I see you went much further! I'll immediately install the package, working on several examples, and asap start contributing with it! Congratulations! -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
On Monday, July 8, 2013 12:46:42 PM UTC+2, Nils Bruin wrote: On Monday, July 8, 2013 11:33:18 AM UTC+2, Jean-Pierre Flori wrote: IIRC the new GAP banner uses UTF-8. You're right. With (to me) the same jarring effect, so I don't like it. That was also a problem to me when I updated some Sage's doc and latex or maybe Sphinx did not like the strange UTF-8 chars used. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] tutorial()
Hi notebook() launches in firefox (my preferred browser on ubuntu 12.04). tutorial() launches in chromium, why is that? Trying to do a from-source install so that I can look at the code. Regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: tutorial()
Le lundi 8 juillet 2013 13:32:11 UTC+1, Jan Groenewald a écrit : notebook() launches in firefox (my preferred browser on ubuntu 12.04). tutorial() launches in chromium, why is that? Trying to do a from-source install so that I can look at the code. You do not need to install from source to have the code on your computer. Everything is in $SAGE_ROOT/devel/sage-main/sage/ and you can even access the code within the console with sage: my_function?? Vincent -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: UTF-8 and old terminals (new startup banner)
On Monday, July 8, 2013 4:51:28 AM UTC-4, Nils Bruin wrote: all the colour stuff should shut off automatically for a dumb terminal). The colors are ansi escape sequences, they have nothing to do with unicode for the record Why require it for *just* the banner? As I said already, we *already* require it for display of non-ascii characters in docstrings. More personally, I dislike the UTF-8 banner because it looks too nice. These kids nowadays, they have it to easy. When I was young, we had to walk an hour through the snow to school. And uphill. In both directions ;-) -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: tutorial()
sage: tutorial?? Type: instancemethod String Form:bound method _sage_doc.tutorial of sage.misc.sagedoc._sage_doc instance at 0x1418758 File: /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/misc/sagedoc.py Definition: tutorial(self) Source: def tutorial(self): The Sage tutorial. To get started with Sage, start here. EXAMPLES:: sage: tutorial() # indirect doctest, not tested self._open(tutorial) sage: PS. It looks like tutorial honours SAGE_BROWSER which can be used as a workaround, but I do not have that set and tutorial is not using the default browser... tutorial is actually opened with xdg... with SAGE_BROWSER set to 'firefox': sage: from sage.misc.viewer import browser sage: browser() 'sage-native-execute firefox' sage: Exiting Sage (CPU time 0m0.31s, Wall time 0m19.01s). 0 jan@muizenberg:~$unset SAGE_BROWSER 0 jan@muizenberg:~$sage ++ | Sage Version 5.10, Release Date: 2013-06-17| | Type notebook() for the browser-based notebook interface.| | Type help() for help.| ++ sage: from sage.misc.viewer import browser sage: browser() 'sage-native-execute xdg-open' sage: From a bash terminal, I can type xdg-open index.html and that uses chrome, but xdg-settings get default-web-browser says 'firefox.desktop' Regards, Jan Regards, Jan On 8 July 2013 14:49, vdelecroix 20100.delecr...@gmail.com wrote: Le lundi 8 juillet 2013 13:32:11 UTC+1, Jan Groenewald a écrit : notebook() launches in firefox (my preferred browser on ubuntu 12.04). tutorial() launches in chromium, why is that? Trying to do a from-source install so that I can look at the code. You do not need to install from source to have the code on your computer. Everything is in $SAGE_ROOT/devel/sage-main/sage/ and you can even access the code within the console with sage: my_function?? Vincent -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: SageManifolds: differential geometry and tensor calculus in Sage
https://lh4.googleusercontent.com/-0IDPoNIN3ko/Udq6gYqcLMI/PEo/Smdr5rsJse8/s1600/SM_doc.png I just installed SageManifolds package, and tried sage: Chart? to review the documentation, and the format is not OK, Is it just me or a documentation `bug`? -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
On Monday, July 8, 2013 6:46:40 AM UTC-4, vdelecroix wrote: If we allow an UTF-8 banner then we may also allow UTF-8 string representations for Sage objects (why not?). Kind of off topic, but I think there is no doubt that we will be using UTF-8 for string representations at some point in the future. It would be stupid for a mathematics project to not take advantage of all the mathematical symbol codepoints in unicode. Having said that, it is also true that there are still non-UTF8 capable terminals in the wild. So until we have an idea of how many people are using them, we shouldn't require them to actually use Sage. But the banner and the docstrings aren't really crucial to using Sage. But I think we do not want to force the user to have UTF-8 output because it is always harder to parse an UTF-8 string than an ASCII string (this argument is also valid for the Sage banner). I disagree, the difficulty right now is that you often get a mix of byte strings with various encodings so its not obvious what to do. But Python 3 has only unicode strings, so basically there will be no such thing as an ASCII string. String operations are then naturally unicode and just as easy or difficult as if everything were ASCII. -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] New basis for an algebra
Thank you for your answer which was very useful. I have now another problem. In order to define the product of two primitive elements (P_l for l a Lyndon word), I think I need the structure equivalent to that of the CombinatorialFreeModule but in the case of monoids, something that others have already dreamt of: https://groups.google.com/forum/#!topic/sage-combinat-devel/E5aETiD7GNU. To be clear, I would like to have a monoid whose generators are indexed by Lyndon words. Does it exist? Matthieu Le mercredi 3 juillet 2013 14:54:16 UTC+2, Nicolas M. Thiéry a écrit : On Sun, Jun 30, 2013 at 04:52:18PM -0700, Matthieu Deneufch�tel wrote: I try to implement the Poincare-Birkhoff-Witt basis of the free algebra. I defined the elements of this basis and a function which gives the expansion of an element of the free algebra on this basis; actually, it returns a dictionary whose keys are monomials and whose values are the corresponding coefficients. I would like to define a new basis of the free algebra, but I don't know which structure I should use. Is there a canonical way? Should I use a CombinatorialFreeModule? There might be some documentation I should have read before asking any question. Please tell me where I should have a look. Sounds like a good candidate for having a: class PoincareBirkhoffWittBasisOfFreeAlgebra(CombinatorialFreeModule): ... and making your change of basis function into a morphism. And possibly a shortcut: sage: F = FreeAlgebra(...) sage: PBW = F.poincare_birkhof_witt_basis() In the long run, if more bases come in, you might consider having a FreeAlgebraWithRealizations similar to Sym with its several bases. A natural starting point in the documentation is: http://combinat.sagemath.org/doc/thematic_tutorials/tutorial-implementing-algebraic-structures.html with its prerequisite: http://combinat.sagemath.org/doc/reference/modules/sage/modules/tutorial_free_modules.html Good luck! Nicolas -- Nicolas M. Thi�ry Isil nth...@users.sf.net javascript: http://Nicolas.Thiery.name/ -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: SageManifolds: differential geometry and tensor calculus in Sage
I'm trying to reproduce the examples in the page, starting with Schwarzschild spacetime So far I'm getting the following: * When defining a `Chart`, say `X`, t from manifolds.all import * M = Manifold(4, 'M', r'M'); M X = Chart(M, r't, r:positive, th:positive:\theta, ph:\phi', 'BL') X does not return the latex output, but this chart 'BL' (t, r, th, ph) this is not a problem because after trying X.show() the expected output pops up! When using the `show()`method on the metric the output is not shown in the way I expected (with the tensor product of the basis, g[0,0], g[1,1], g[2,2], g[3,3] = -(1 - 2*m/r), 1/(1 - 2*m/r), r^2, (r*sin(th ))^2; show(g) g = (2*m/r - 1) dt*dt - 1/(2*m/r - 1) dr*dr + r^2 dth*dth + r^2*sin(th)^2 dph*dph I try a couple of things and non of them yields the result shown in the documentation. Similar behaviour goes on and on through the WS. * I'd add the following line to the WS nab[:] because people can see the components of the connection. * Additionally, I shall propose to define a method to show only the non-trivial components of the tensors... including the `name` of the component (in indices). The code below will do the work, but of course it can be improved. for i in M.irange(): for j in M.irange(): for k in xrange(j,M.dimension()): if (nab[:][i][j][k] != 0): print Gam_{%d %d %d}: %(i, j, k) print \t, nab[:][i][j][k], \n\n This method should be implemented for tensors. I'm still learning the stuff, and should be posting more suggestions later! Thank you for the wonderful work done with this package!!! Cheers -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: SageManifolds: differential geometry and tensor calculus in Sage
On Monday, July 8, 2013 4:31:43 PM UTC+2, Dox wrote: I'm trying to reproduce the examples in the page, starting with Schwarzschild spacetime So far I'm getting the following: * When defining a `Chart`, say `X`, t from manifolds.all import * M = Manifold(4, 'M', r'M'); M X = Chart(M, r't, r:positive, th:positive:\theta, ph:\phi', 'BL') X does not return the latex output, but this chart 'BL' (t, r, th, ph) this is not a problem because after trying X.show() the expected output pops up! It may be that the option typeset is not set in your notebook. Cheers, Michał -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: SageManifolds: differential geometry and tensor calculus in Sage
Thx Michael, I didn't know that feature of sage notebook! -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: Error installing package matplotlib-1.2.1
On Monday, July 8, 2013 11:08:57 AM UTC+2, vdelecroix wrote: Le dimanche 7 juillet 2013 22:06:12 UTC+1, Paul Mercat a écrit : As it's recommanded, I give here the error I get when I try to compile sage 5.10 on my MacBook pro : ld: library not found for -lpng The problem comes from the fact that there should be a library libpng somewhere but the compiler was not able to find it. It looks like the problem in http://stackoverflow.com/questions/12630593/g-linking-with-libpng. I let the mac expert answer to this. I've installed the library libpng-1.6.2 (the lastest), and now the compilation is successfull. BUT the tests don't pass : the checks fails each time there is a plot or some graphical result. Here is the error I get each time : libpng warning: Application built with libpng-1.2.35 but running with 1.6.2 Unhandled SIGSEGV: A segmentation fault occurred in Sage. This probably occurred because a *compiled* component of Sage has a bug in it and is not properly wrapped with sig_on(), sig_off(). You might want to run Sage under gdb with 'sage -gdb' to debug this. Sage will now terminate. ** So I've try to install a other version of libpng libpng-1.2.50 (more near to libpng-1.2.35), and recompile all sage. (I've not found the version libpng-1.2.35 on the libpng website) Now I've a new error when I compiling sage : File /Applications/sage-5.10/local/lib/python2.7/site-packages/sage/structure/sequence.py, line 289, in Sequence from sage.rings.polynomial.pbori import BooleanMonomialMonoid ImportError: dlopen(/Applications/sage-5.10/local/lib/python2.7/site-packages/sage/rings/polynomial/pbori.so, 2): Library not loaded: /usr/local/lib/libpng12.0.dylib Referenced from: /Applications/sage-5.10/local/lib/libpolybori_groebner-0.8.dylib.3.0.0 Reason: Incompatible library version: libpolybori_groebner-0.8.dylib.3.0.0 requires version 51.0.0 or later, but libpng12.0.dylib provides version 36.0.0 real 0m7.212s user 0m0.957s sys 0m0.446s Error installing package conway_polynomials-0.4.p0 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /Applications/sage-5.10/logs/pkgs/conway_polynomials-0.4.p0.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /Applications/sage-5.10/spkg/build/conway_polynomials-0.4.p0 and type 'make' or whatever is appropriate. Instead, the following commands setup all environment variables correctly and load a subshell for you to debug the error: (cd '/Applications/sage-5.10/spkg/build/conway_polynomials-0.4.p0' '/Applications/sage-5.10/sage' --sh) When you are done debugging, you can type exit to leave the subshell. make[2]: *** [/Applications/sage-5.10/spkg/installed/conway_polynomials-0.4.p0] Error 1 make[1]: *** [all] Error 2 real 202m38.206s user 164m49.863s sys 17m57.458s *** Error building Sage. What is the right version of libpng that I have to install ? And why this library is not installed automatically as every other ones needed by sage ? This library seems to be the only problem I have. I would like very much to fix this problem, because I would like to participate to the developpement of sage (for example to add finite state automatons). Cool! Regarding finite state automatons, there is yet a patch which handles this at http://trac.sagemath.org/sage_trac/ticket/12996 which is almost finished (and as you are hyperbolic you may like http://trac.sagemath.org/sage_trac/ticket/9439). Thank you for the links, I will see that more in details when I will succed to compile sage correctly. Paul -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
On Mon, Jul 8, 2013 at 1:55 AM, Julien Puydt julien.pu...@laposte.netwrote: Le 08/07/2013 10:51, Nils Bruin a écrit : On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote: Frédéric Chapoton has written a patch at http://trac.sagemath.org/14733 http://trac.sagemath.org/**14733http://trac.sagemath.org/14733 that will beautify the Sage startup banner using some UTF-8 characters to draw the box. This will display incorrectly in terminals that do not support UTF-8. In that case, Sage still works but the box around the banner is garbled (most likely rendered by placeholder signs for non-ASCII characters). -1 to a UTF-8 banner. There's hardly anything in the sage command line that requires a UTF-8 capable terminal (all the colour stuff should shut off automatically for a dumb terminal). Why require it for *just* the banner? More personally, I dislike the UTF-8 banner because it looks too nice. To me it doesn't fit with the simple prompt-and-return-value interface (see banners of magma, maple, R, matlab, pari/GP, python, IPython, GAP, Singular). The graphics looking lines are more suggestive of a menu-driven interface to me, like the text-based dialog interfaces. So to me, the +-|-built borders raise expectations more appropriate for what sage command line offers. -1 too for the same reasons. Keep the banner short and simple ; people don't come to sage to enjoy that sight! I agree, no need to have fancy unicode here. If you're doing something that requires nice output you should probably be using a notebook interface anyways; the CLI interface just isn't going to go there and going part way is worse than just keeping things simple. - Robert -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: RFC: a good name the category of algebras that are not necessarily associative nor unital
Dear all, While working on an implementation of finite algebras over fields (#12141) I was slightly annoyed by the fact that Algebras are currently assumed to be unital. I agree with Simon King's opinion: I don't really like magma algebra or magmatic algebra, but that's mainly because I never heard anyone using this notion before. I'd rather describe an algebra as a module over an appropriate operade than call it magma algebra. What I'd prefer is very simple: Just say algebra to an algebra. If any additional axiom holds, then the algebra should be called commutative, associative, unital, noetherian, lie, finite-dimensional, or whatever you like. But don't mention the *absence* of axioms! Best regards, Peter Bruin -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: Error installing package matplotlib-1.2.1
Actually, the version of libpng the compiler should use is not the one which you just installed but the one which is shipped with sage (ie $SAGE_ROOT/local/lib/libpng*)... It looks like a problem of compiler options but I have no clue of how to solve this and it is quite strange that it fails only for libpng... -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.