> Many thanks. Is there a documented version available? Martin, when I looked at that code, I was asking myself the same question. I guess Mike might answer: the documentation is at http://www.risc.uni-linz.ac.at/people/hemmecke/aldor/combinat/index.html I find that very unsatisfying. I've put *a lot* of energy in the documentation which probably caused that Mike was able to implement that stuff so quickly. Now, if in the future we would like to transfer some ideas from sage-combinat to aldor-combinat. We are in a very bad situation. That's somehow unfair and I hope that people working on sage-combinat will do a bit more than writing doc-strings. Mike, just imagine I had not documented the way I deal with 'approximateOrder'. I guess you would have had very hard times to understand my code.
Where is all your background information and your design decisions. You probably could not follow the Aldor approach exactly. Where do I find a documentation of the different design? [snip] >> I was wondering if you'd be willing to release Aldor-Combinat to me under GPL >> v2 or later since that is the license I'd like to release my code under to be >> compatible with the rest of Sage. > I cannot answer that one, but I guess it shouldn't be a problem. It's not a > problem for me, at least. So, before I say yes, what does that actually mean? And why do you need it? You are not using Aldor-code anyway. My position is actually as follows. AC is under GPL2, because GPL3 was not available when we started. Now I am not really against adding "and later versions" to our GPL license. But first explain, why you need that. >> I'll probably be working on the multisort case later on. Due to lack of >> funds, I can't make it out to RISC this summer, but I'd be more than happy to >> join in your discussions about multisort species. > > I did most of the maths involved (i.e., how to generate isotypes of a > composition of multisort species), it's mainly a problem of representation. > The trouble is, so far I did not find a reasonable way to do composition such > that the output are *representatives* of isomorphismtypes -- the approach > taken > in the trunk version of Ralf's code and mine. But if your code above solves > this problem, then there is little left to do! Mike, actually, I'd like to follow your code using mercurial, but I've no experience with it. If you could give some hint on what to do exactly to be always up-to-date with your latest sage-combinat and what to do to actually run it. BTW, I haven't looked into Multisort species for some time. Theoretically that is not too difficult. Why I don't go on with it is, because Aldor doesn't let me do the definition as nicely as I want it. Basically, I'd like to write F(G,H,K) similar to what is done in the univariate case (see http://www.risc.uni-linz.ac.at/people/hemmecke/AldorCombinat/combinatsu26.html#x40-580008.13 Actually that is not a problem for bi- tri-, ... n-variate species. But that would mean n implementations of basically equivalent code. As you might guess, I don't want to double code and rather write generic code for that situation. Aldor doesn't let me specify this at compile time. Since Python is interpreted, you might be more lucky. Best regards Ralf ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Aldor-combinat-devel mailing list Aldor-combinat-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aldor-combinat-devel
