David Slater

`TF2` can be mapped to `PYTORCH`. Actually, I would probably just map them all to `armory` or some generic container name. the deep speech container will require some additional work:...

Let's have `pytorch-deepspeech` be a different PR, but let's put `tf2` in this one, mapping it to PyTorch like you have done here with `carla-mot`. The current `tf2` and `pytorch`...

What I am trying to prevent is the `+attack.foo=targeted +defense.foo=targeted` sort of thing. I would rather be able to do `armory run experiments/carla_mot.yaml +targeted=false` This comes up, for instance, in...

For the version `0.17.0` release, we should have deprecation errors that tell users to use version `0.16.0` for those containers.

@lcadalzo can you resolve the merge conflict?

The error may be due to changes in develop that happened after we branched to tfdsv4

No, on second look, those occurred before develop was merged into tfdsv4, so I don't know.

I like adding it to the config part of instrumentation.

See my two recent comments. Beyond that, I think what needs to be done is: A) remove the changes to `armory/instrument/config.py`, and `armory/utils/config_schema.json`. B) move the new functions from `statistical`...

Hi Guillaume, sorry for dropping this one. I don't have any experience with Singularity, so I don't think we'll be able to directly support that, at least right now. We...