Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
1edv authored Mar 22, 2022
1 parent eadc387 commit da4829d
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions manuscript_code/model/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,9 +27,9 @@ This directory contains all the code and data for reproducing our results in a s
<ul>
<li> <h4>benchmarking_models</h4>
<li> <h4>biochemical_model</h4>
<li> <h4>gpu_only_model</h4>: The convolutional model is referred to as the "gpu_only_model" in this repo. We recommended that future readers use the [transformer model](https://github.com/1edv/evolution/tree/master/manuscript_code/model/tpu_model) instead, for their applications going forward. The convolutional model will be deprecated and is unlikely to be supported by future versions of TensorFlow.
<li> <h4>gpu_only_model</h4>The convolutional model is referred to as the "gpu_only_model" in this repo. We recommended that future readers use the transformer model instead, for their applications going forward. The convolutional model will be deprecated and is unlikely to be supported by future versions of TensorFlow.
<li> <h4>reproduce_test_data_performance</h4>
<li> <h4>tpu_model</h4>: The transformer model is referred to as the "tpu_model" in this repo. This is our recommended model for future users.
<li> <h4>tpu_model</h4>The transformer model is referred to as the "tpu_model" in this repo. This is our recommended model for future users.
</ul>
</ul>
There is another subdirectory called CodeOcean_run here, it is simply there because of CodeOcean's directory structure requirements and CodeOcean_run's contents can be better accessed in the results_summary directory mentioned above. Pressing the 'Reproducible Run' button on CodeOcean runs the code here and reproduces Fig. R1 and Fig. R2 in the Reviewer response.
Expand Down

0 comments on commit da4829d

Please sign in to comment.