#16954: Game Theory: Build class for normal form games as well as ability to 
obtain
Nash equilibria
-------------------------------------+-------------------------------------
       Reporter:  vinceknight        |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.4
      Component:  game theory        |   Resolution:
       Keywords:  Game Theory,       |    Merged in:
  Normal Form Games                  |    Reviewers:
        Authors:                     |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:                     |  ffa6d525b5e6681687642d9efc80037884823e30
  u/vinceknight/16954                |     Stopgaps:
   Dependencies:                     |
-------------------------------------+-------------------------------------

Comment (by kcrisman):

 Parser comments.
  * Minor - this could be made slightly more professional-sounding.  Also,
 double ticks for code markup; maybe even {{{``'lrs'``}}} if it is a
 string, I'm not sure about this.
 {{{
     At present the only parser included is the for `lrs` algorithm however
     this will be expanded to `gambit` soon.
 }}}
  * Since `lrs` is an optional package, will any of the doctests in the
 parser file need to be marked optional?  I assume not, just checking.
 (Maybe the one using the subprocess stuff?)
  * Will those temp files really disappear or do you need to remove them?
 I just don't remember - we use the temp file name thing so it doesn't
 overwrite, but I can't remember if we need to remove them afterwards,
 though I believe we do.
  * Just out of curiosity, what does the fourth element of the stuff mean
 that you parse?
 {{{
 '2  0  1  2 \n', '1  1/2  1/2 -2 \n'
 }}}
    the first number is the player, the next two the strategy (does lrs
 only do two player, two-strategy games?) but what is the 2 and -2 here?
  * Could the creation of the `p1_strategies` be sped up slightly with
 something like
 {{{
 p2_strategies.append(sage_eval(k) for k in i.split() if k.index() !=1 or
 -1)
 }}}
    (this syntax is not right, I'm sure) ?  Again, probably quite minor to
 even think about given the type of use case.

--
Ticket URL: <http://trac.sagemath.org/ticket/16954#comment:12>
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.

Reply via email to