Analyse statistics from all csv files in the directory or a given data pack.
builddatapack.sh runs an arbitrary number of simulations and defaults to 40 runs. Each simulation saves its data into a csv file that looks like this. Each simulation runs some statistics function stats() in dicemechanicsim.py. It would be cool to run statistics comparing several simulations. This would allow easier comparisons between settings used to generate datapacks.
Example data packs can be found in dice-mechnanic-datapacks. data20180219-2137.zip is the latest one uploaded to dice-mechanic-datapacks (dmd).
The best place for this type of script might be a new file called data/datapackstats.py that could be called at the end of builddatapack.sh with a line like python3 ./data/datapackstats.py.
Ideas for statistics:
- What is the average of all event 6 scores within the datapack?
- What is the average high score within each csv?
- What is the average low score within each csv?
- What is the average score after each event?
- Inspect the
stats() function in dicemechanicsim.py
Analyse statistics from all csv files in the directory or a given data pack.
builddatapack.shruns an arbitrary number of simulations and defaults to 40 runs. Each simulation saves its data into a csv file that looks like this. Each simulation runs some statistics functionstats()indicemechanicsim.py. It would be cool to run statistics comparing several simulations. This would allow easier comparisons between settings used to generate datapacks.Example data packs can be found in dice-mechnanic-datapacks.
data20180219-2137.zipis the latest one uploaded to dice-mechanic-datapacks (dmd).The best place for this type of script might be a new file called
data/datapackstats.pythat could be called at the end ofbuilddatapack.shwith a line likepython3 ./data/datapackstats.py.Ideas for statistics:
stats()function indicemechanicsim.py