Looking for 9x9 model files in .minigo file format about minigo HOT 7 CLOSED

It doesn't seem that we have converted the old 9x9 models.

@tommadams or I will try to do.

@tommadams is this the general jist

for MODEL_PATH in `gsutil ls ...` do
  python freeze_graph.py  --model_path=$MODEL_PATH
  python3 oneoffs/wrap_model.py \
    --src_path $MODEL_PATH.tflite \
    --dst_path $MODEL_PATH.minigo \
  --metadata engine=lite,input_features=agz,input_layout=nhwc,input_type=float,board_size=9
done

note there's a small typo in cc/README.md see s/minifo/minigo/

from minigo.

I'll do this now

from minigo.

Oh, it looks like we don't have frozen .pbs for those 9x9 models.

We'll need to freeze them. Does anyone know what the architecture flags used were?

from minigo.

That's a question for @amj or @brilee

from minigo.

from minigo.

I'm digging through the github history to see if I can pull out the appropriate architecture flags.

The v0.6 MLPerf was 9x9 but the benchmark was set up to train a model that plays something "reasonable" in as short a time as possible. The trained models are pretty weak.

from minigo.

Ok, I've uploaded .minigo versions of all the v3-9x9 models to the GCS bucket.

When you're building the C++ binaries, remember to pass --define=board_size=9 because the board size is a compile-time constant. For example:

gsutil cp gs://minigo-pub/v3-9x9/models/000496-polite-ray.minigo .
bazel build  -c opt  --define=board_size=9  cc:simple_example
./bazel-bin/cc/simple_example  --model=000496-polite-ray.minigo

from minigo.