If this is agreeable to the findstat project, how would this fare if tomorrow me or my students: - start adding semantic decorators to existing classes (for instance, for groups, adding information in the groupprops database, or from categories adding information from the database of categories at the nLab) - start adding essentially empty classes and functions in sage that are there only so I can add the empty decorators (for instance, LMFDB)
I understand I could do this as a separate git branch, but the point is that this is meant to build on other people adding decorators, because it is easy and convenient to them and they want to help my research project, while at the same time "hey-you-never-know-how-those-semantic-annotations-might-prove-useful=so=why-not-have-it-in-sage-even-if-it-supports-just-one-guy" I am looking for a consistent workflow to support my work and that of my students. Paul Paul-Olivier Dehaye SNF Professor of Mathematics University of Zurich skype: lokami_lokami (preferred) phone: +41 76 407 57 96 chat: pauloliv...@gmail.com twitter: podehaye freenode irc: pdehaye On Wed, May 28, 2014 at 1:28 AM, Nathann Cohen <nathann.co...@gmail.com>wrote: > > Let's not mix everything here. In FindStat, we do use a database for > > statistics (not maps) but that's not what we're talking about here. We're > > just talking about flagging some object methods as maps with some > semantic > > information. > > Indeed. You agreed to only talk about the aspects of this decorator which > are of interest to Sage. > > > > my only question is what "storing the info" means. I understand Nathan is > > suggestiong I just put it in some database object somewhere, and then my > > permutation object would just ask this object whenever it needs to give > the > > list of maps. Am I right here? > > Let us say that when the combinatorial_map decorator is called on a > function f with some parameters, it does the following > > from sage.combinat.combinatorial_map import my_dictionary_database > my_dictionary_database[f] = list_of_parameters_or_anything_you_like > return f > > With a design like that, any semantic information is still available if > you ever need it, and the function is left unchanged. > > Nathann > > -- > 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-de...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-combinat-devel. > For more options, visit https://groups.google.com/d/optout. > -- 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/d/optout.
