4 ms·
> Data, Materials, and Code Availability > [...] However, sharing the AlphaZero algorithm code, network weights, or generated representation data would be tech
by bnprks 4y ago
> Data, Materials, and Code Availability
> [...] However, sharing the AlphaZero algorithm code, network weights, or generated representation data would be technically infeasible at present.
Very interesting paper overall. However, the excuse that code sharing is "technically infeasible" is wearing thin nearly 5 years after the initial AlphaZero paper was released.
- mgraczyk 4y agoMy assumption is that the code is not separate from other deepmind code. It would be very difficult for them to share the AlphaZero code without also sharing everything else deepmind is working on. The representations are probably not manifest in a way that would be intelligible if shared. I don't have an explanation for why they wouldn't share the weights.
- espadrine 4y agoIn some frames of the Deepmind documentary film on AlphaGo, we can see code for loading SSTs (a common key-value data format at Google) from GFS (the Google file system). It is possible that the entire codebase depends on Google-only infrastructure.
- mgraczyk 4y agoThat part is true, but things like that are usually not too bad by themselves. For example, you can use open source tensorflow to access files on Google's internal filesystem with tf.io.gfile. It's possible other infra is somewhat hairy to decouple, for example the code they use to allocate and use GPU resources is internal. (I work on ML at Google and we use some of Deepmind's stuff)
- heavenlyblue 4y agoSurely all of that could easily be replaced with a "virtual" version of these interfaces