#17902: Basic combinatorial game theory
-------------------------------------------------+-------------------------
Reporter: kcrisman | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.6
Component: game theory | Resolution:
Keywords: Combinatorial Game Theory, | Merged in:
partially ordered set, Nim, Impartial games, | Reviewers:
Partizan Games, Sprague–Grundy theorem | Work issues:
Authors: | Commit:
Report Upstream: N/A | Stopgaps:
Branch: |
Dependencies: |
-------------------------------------------------+-------------------------
Comment (by kcrisman):
What I suggest is the following.
* Create basic classes that have the same API as CGSuite, though
"Sageified" or "Pythonized" (I don't know anything about CGSuite).
* Create some basic implementation that doesn't require CGSuite, but
which could use it behind the scenes.
* Eventually connect it via perhaps the scripting language for CGS. But
yes, you are right that it would need something that at the very least
could be connected with using a library or pexpect.
However, given that there doesn't seem to be such an api, and yet one
wouldn't want to reimplement a huge thing like this, maybe the first best
step is the following:
* Contact the CGSuite maintainer
* Ask whether they would be interested in a Sage interface
* And whether they would be interested in providing at least some minimal
CLI for the program.
* For instance, one could install CGSuite as an optional package than
then there is something called `sage-native-execute` or other ways to run
such programs from Java "inside Sage", so to speak, though we don't do it
with Java too much, maybe for polymake when it worked?
* Then in the meantime work on the Sage version of the structures and
classes, leaving room (as with the history of the normal form games) for
later incorporation of that.
* Alternately, maybe the maintainer even wants to help directly with Sage
integration if the project has been idle for a while...
One big reason is that it's not just not wasting time, but that it's so
super-easy for little bugs to creep in when rewriting something in a
different language.
But anyway it sounds like you have a good handle on this already, and a
plan, which is great.
--
Ticket URL: <http://trac.sagemath.org/ticket/17902#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
