Ecosyste.ms: Timeline

Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.

metatensor/metatrain

frostedoyster pushed 1 commit to auto-continue metatensor/metatrain

View on GitHub

frostedoyster created a review comment on a pull request on metatensor/metatrain
Ok! It's now there

View on GitHub

frostedoyster created a review on a pull request on metatensor/metatrain

View on GitHub

SanggyuChong created a review on a pull request on metatensor/metatrain
To me it looks good, didn't understand the shift from computing something on the energies and forces to working directly on the loss functions, but now i understand and see it now. Thanks for t...

View on GitHub

PicoCentauri pushed 1 commit to download-model metatensor/metatrain
  • allow exporting models on remote locations e8e3248

View on GitHub

PicoCentauri pushed 1 commit to download-model metatensor/metatrain
  • allow exporting models on remote locations 60abba5

View on GitHub

HannaTuerk created a branch on metatensor/metatrain

pet_history - Training and evaluating machine learning models for atomistic systems.

Luthaf added HannaTuerk to metatensor/metatrain
github-actions[bot] pushed 1 commit to gh-pages metatensor/metatrain
  • deploy: 6af1bed826252f35e3be4c7242f6ffba9d2b89d4 b7c9c56

View on GitHub

abmazitov closed an issue on metatensor/metatrain
Energies per atom are written to the `output.xyz` instead of full energies
While running the `mtt eval`, I noticed that instead of writing total energies to the `xyz` file with the predictions, we write the energies per atom. This happens because of the following lines: ...
abmazitov deleted a branch metatensor/metatrain

full_output_energies_on_eval

abmazitov pushed 1 commit to main metatensor/metatrain
  • Adding total energies to the output during mtt eval (#367) * Adding total energies to the output during mtt eval ... 6af1bed

View on GitHub

abmazitov pushed 1 commit to full_output_energies_on_eval metatensor/metatrain

View on GitHub

abmazitov pushed 1 commit to full_output_energies_on_eval metatensor/metatrain

View on GitHub

PicoCentauri created a review comment on a pull request on metatensor/metatrain
We should inform the user that the training is continued if the `outputs` directory is found or maybe error or warn if continue="auto" and now directory is found.

View on GitHub

PicoCentauri created a review on a pull request on metatensor/metatrain
Might be a good idea. If this moves further remember to explain this well in the docs. We aren't writing the checkpoints of the current training run in the directory where the training is starte...

View on GitHub

PicoCentauri created a review on a pull request on metatensor/metatrain
Might be a good idea. If this moves further remember to explain this well in the docs. We aren't writing the checkpoints of the current training run in the directory where the training is starte...

View on GitHub

frostedoyster pushed 1 commit to nanopet metatensor/metatrain

View on GitHub

frostedoyster pushed 2 commits to nanopet metatensor/metatrain
  • MLP for geometric embedding a951638
  • Merge branch 'nanopet' of https://github.com/lab-cosmo/metatrain into nanopet 92d2c80

View on GitHub

frostedoyster pushed 1 commit to nanopet metatensor/metatrain

View on GitHub

abmazitov opened a pull request on metatensor/metatrain
Adding total energies to the output during mtt eval
<!-- What does this implement/fix? Explain your changes here. --> # Contributor (creator of pull-request) checklist - [ ] Tests updated (for new features and bugfixes)? - [ ] Documenta...
abmazitov created a branch on metatensor/metatrain

full_output_energies_on_eval - Training and evaluating machine learning models for atomistic systems.

abmazitov opened an issue on metatensor/metatrain
Energies per atom are written to the `output.xyz` instead of full energies
While running the `mtt eval`, I noticed that instead of writing total energies to the `xyz` file with the predictions, we write the energies per atom. This happens because of the following lines: ...
frostedoyster pushed 1 commit to nanopet metatensor/metatrain

View on GitHub

frostedoyster pushed 1 commit to nanopet metatensor/metatrain
  • Get rid of nanopet-neighbors a675bfe

View on GitHub

frostedoyster pushed 1 commit to nanopet metatensor/metatrain
  • Get rid of nanopet-neighbors 6b9e45e

View on GitHub

github-actions[bot] pushed 1 commit to gh-pages metatensor/metatrain
  • deploy: 6b5fb29f258c70f7dc322b6b667204e7461746fe 0306fe3

View on GitHub

github-actions[bot] pushed 1 commit to gh-pages metatensor/metatrain
  • deploy: fc17b495e9648b681f80aa2aeeac1c8738cfc567 fc68b13

View on GitHub

frostedoyster pushed 3 commits to nanopet metatensor/metatrain
  • Add MAE logging (#361) fc17b49
  • Print learning rate decreases (#365) 6b5fb29
  • Merge branch 'main' into nanopet d88cfcf

View on GitHub

frostedoyster deleted a branch metatensor/metatrain

print-lr

Load more