Currently, to update the starting lineup, you need to use the command line interface. In Flask, there needs to be a display of available players and the ability to select them. Should we do this with a database? Relational or doc store?

I wrote the baseball sim at the same time as when I was working on a rocket sim so I used some of the same libraries in both projects but much of what was put in for the rocket sim isn't needed here.

For example, in lib 'generalEquations' the library is currently billed as general math equations for rocket simulations. Very little of the library is used. I need to figure out what's used and get rid of the rest.

Need to validate form so one team can't be selected twice for team1 and team2

We will use React.js to display simulation results and other pages in the baseball app. We can add the React.js frontend with create-react-app.

I propose that we have a development ("develop" or "dev") branch and master branch (the currently deployed version).

We can have other short-lived branches that follow this style:

{reason}-{1 to 3 word description}-{id-type}-{id}

Reasons would be limited to "bug", "feature", "refactor", "hotfix" or "spike" (spike for experiments).

So for example, to work on issue #23, I could name it "feature-add-lineup-selector-issue-23". Maybe that's a bit long. Should we try to limit the description to a word? Or always use issues (rather than stories, or other ids). So it could be "feature-lineup-23"

I'm going to set up CICD (Travis CI probably) on the project so I don't know if that matters for branch names other than for separating develop and master.

We should be able to view details of each game produced by a simulation.

The data is available for all players but currently, only two teams are supported. This issue is blocked by the previous issue #23. Once starting lineups can be entered on the fly, all teams can be supported.

The advance_runners function advances runners based on the base the hitter gets to (on a double, everyone moves forward two bases). But, for singles especially, decent runners can go from 1st to 3rd on a single. Perhaps there should be a "time to advance bases" concept where runners have a certain amount of time to advance based on the hit type? This is related to issue #11 as it lowers the overall score.

Current goals are to

• create a better display of the current functionality in a Flask App.
• add documentation
• add license
• add contribution guidelines
• improve code quality

need a basic page for displaying simulation results

• Add install instructions
• Add the project's current functionality
• Add the project's direction and goals (which needs to be discussed)

The way the sample space is coded awkwardly encodes object like data as a string.

Here's what it looks like:

        self.sample_space = {
            'Walk: Base on balls': base_on_balls / outcomes,
            'Walk: Hit by pitch': stats['hbp'] / outcomes,
            'Walk: Intentional Walk': stats["ibb"] / outcomes,
            'Out: SO': stats["so"] / outcomes,

This needs to be coverted to named tuples. Something like ("Result Type", "Result Details", "Probability") and the code that uses it needs to be adjusted.

The average runs per game tend to be around 2.7 for both teams.

• Investigate what the avg should be
• Are starting pitchers rotated
• Do pitchers fatigue

Rather than a running total of how many runs were scored, the scoreboard should show how many runs have scored that inning followed by total runs and the total hits and possibly total errors. See https://www.quora.com/How-can-I-read-a-baseball-scoreboard

The code needs to be modified to be compliant with PEP8. The library Flake8 should be used to check and fix issues.

Local libraries are referenced. Either make them public packages on PyPI or bring them into this repo.

Please let me know what areas of the code are difficult to follow and I'll refactor them.

Reformat requirement.txt

I'd love to share what we already have so I'd like to get a domain and deploy the site.

• Create a team on Digital Ocean
• Create a droplet
• Create a Flask deployment following this tutorial
• Install Node on the droplet
• Adapt the tutorial to our site
• Decide on a domain name
• Register and point the domain at the droplet
• Add TravisCI

Regarding the domain name, I've been trying to think of a better name for the project. I'm thinking "Pop-up Sim." Something like "Home Run Sim" would oversell the modest ambitions of the project and both pop-up-sim.com and popupsim.com are available. Do you have a preference between the two or other name suggestions?

I'm receiving a 500 error when the number of games isn't set