Philip Turner

The reason I initially decided to compile S4TF with the old TF 2.4 binary was to narrow down the source of https://github.com/s4tf/s4tf/issues/14, not to make it accessible on Colab. You...

Also, I'm planning to un-comment out `x10_training_loop` from the package manifest on both the head branch and this TF 2.4 branch. It was deactivated in January 2021 because of some...

SwiftPlot has started failing to import on the first try if you use `-c release -Xswiftc -Onone`. You have to restart the runtime and rerun the `%include` command. This strange...

Even wierder - you now have to restart 2 times to use S4TF on [s4tf/s4tf:main](https://github.com/s4tf/s4tf)! You only need to restart once when using `fan/resurrection`. Both branches were tried on the...

[v2.2](https://github.com/philipturner/swift-colab/releases/tag/v2.2) was released, and the README has instructions for compiling Swift for TensorFlow. I noted the issue with `-c release -Xswiftc -Onone`, keeping the SwiftPM flags directive commented out. Let...

> It should allow me to run some old S4TF models using X10 on TPU if I want. I haven't tried this yet but it would be handy. However elaborate...

For starters, I'm going to lay out the challenges we will face. Swift-Colab is extremely fine-tuned for the Colab environment. I hard-coded concise URLs such as `/opt/swift/toolchain` and assumed there...

I was drafting the above message while you were typing yours, so it wasn't a proper response to your questions.

> package the install process as a set of binaries which can be directly downloaded in colab instead of compiling it from scratch I think I skimmed over some of...

> PS: the swift-colab name might not be as appropriate when we get there, but that is for later … :) The naming seems to be a done deal. I...