+func FillStateCell(data planet_data, dims []int, table []State, addr []int) {
+}
+
+func FillStateTable2(data planet_data, dims []int, table []State,
+fuel_remaining, edens_remaining int, planet string, barrier chan<- bool) {
+ /* The dimension nesting order up to this point is important.
+ * Beyond this point, it's not important.
+ *
+ * It is very important when iterating through the Hold dimension
+ * to visit the null commodity (empty hold) first. Visiting the
+ * null commodity represents selling. Visiting it first gets the
+ * action order correct: arrive, sell, buy, leave. Visiting the
+ * null commodity after another commodity would evaluate the action
+ * sequence: arrive, buy, sell, leave. This is a useless action
+ * sequence. Because we visit the null commodity first, we do not
+ * consider these action sequences.
+ */
+ eden_capacity := data.Commodities["Eden Warp Units"].Limit
+ addr := make([]int, len(dims))
+ addr[Edens] = edens_remaining
+ addr[Fuel] = fuel_remaining
+ addr[Location] = data.p2i[planet]
+ for addr[Hold] = 0; addr[Hold] < dims[Hold]; addr[Hold]++ {
+ for addr[Cloaks] = 0; addr[Cloaks] < dims[Cloaks]; addr[Cloaks]++ {
+ for addr[UnusedCargo] = 0;
+ addr[UnusedCargo] < dims[UnusedCargo];
+ addr[UnusedCargo]++ {
+ if addr[Edens] + addr[Cloaks] + addr[UnusedCargo] <=
+ eden_capacity + 1 {
+ for addr[NeedFighters] = 0;
+ addr[NeedFighters] < dims[NeedFighters];
+ addr[NeedFighters]++ {
+ for addr[NeedShields] = 0;
+ addr[NeedShields] < dims[NeedShields];
+ addr[NeedShields]++ {
+ for addr[Visit] = 0;
+ addr[Visit] < dims[Visit];
+ addr[Visit]++ {
+ FillStateCell(data, dims, table, addr)
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ barrier <- true
+}
+
+/* Filling the state table is a set of nested for loops NumDimensions deep.
+ * We split this into two procedures: 1 and 2. #1 is the outer, slowest-
+ * changing indexes. #1 fires off many calls to #2 that run in parallel.
+ * The order of the nesting of the dimensions, the order of iteration within
+ * each dimension, and where the 1 / 2 split is placed are carefully chosen
+ * to make this arrangement safe.
+ *
+ * Outermost two layers: Go from high-energy states (lots of fuel, edens) to
+ * low-energy state. These must be processed sequentially and in this order
+ * because you travel through high-energy states to get to the low-energy
+ * states.
+ *
+ * Third layer: Planet. This is a good layer to parallelize on. There's
+ * high enough cardinality that we don't have to mess with parallelizing
+ * multiple layers for good utilization (on 2011 machines). Each thread
+ * works on one planet's states and need not synchronize with peer threads.
+ */
+func FillStateTable1(data planet_data, dims []int) []State {
+ table := make([]State, StateTableSize(dims))
+ barrier := make(chan bool, len(data.Planets))
+ eden_capacity := data.Commodities["Eden Warp Units"].Limit
+ work_units := (float64(*fuel) + 1) * (float64(eden_capacity) + 1)
+ work_done := 0.0
+ for fuel_remaining := *fuel; fuel_remaining >= 0; fuel_remaining-- {
+ for edens_remaining := eden_capacity;
+ edens_remaining >= 0;
+ edens_remaining-- {
+ for planet := range data.Planets {
+ go FillStateTable2(data, dims, table, fuel_remaining,
+ edens_remaining, planet, barrier)
+ }
+ for _ = range data.Planets {
+ <-barrier
+ }
+ work_done++
+ fmt.Printf("\r%3.0f%%", 100 * work_done / work_units)
+ }
+ }
+ return table
+}
+