| # Emergent Language Library | |
| ## Running code | |
| For each emergent language entry, we provide wrapper code to create | |
| a reproducible environment and run the emergent language-generating code. | |
| Environments are specified precisely in the `environment.yml` file; if you wish | |
| to edit the dependencies manually, it may be easier to start with | |
| `environment.editable.yml` instead, if it exists. | |
| ### Git submodules | |
| This project uses git submodules to manage external dependencies. Submodules | |
| do not always operate in an intuitive way, so we provide a brief explanation of | |
| how to use them here. By default, submodules are not "init-ed" which means | |
| that they will be empty after you clone the project. If you would like to | |
| populate a submodule (i.e., the directory pointing to another repo) to see or | |
| use its code, run `git submodule init path/to/submodule` to mark it as init-ed. | |
| Second, run `git submodule update` to populated init-ed submodules. Run `git | |
| submodule deinit -f path/to/submodule` to make the submodule empty again. | |