Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

References in documentation/logs #90

Open
frostedoyster opened this issue Feb 20, 2024 · 1 comment
Open

References in documentation/logs #90

frostedoyster opened this issue Feb 20, 2024 · 1 comment
Labels
Documentation Improvements or additions to documentation Infrastructure: Logging Related to logging Priority: Low Non-urgent issues to handle last.

Comments

@frostedoyster
Copy link
Collaborator

The current documentation does not make it easy for users to cite the relevant papers. In my opinion, bibtex should be readily available. Another good idea, as suggested by @PicoCentauri, would be to print the papers to cite in the logs of the training runs (at the beginning? at the end? ...)

@PicoCentauri
Copy link
Contributor

Thanks for bringing up this discussion.

Currently, I would split the way references are provided: 1. within the documentation and 2. within the code.

  1. As introduces in Document hyperparameters for SOAP-BPNN #72 I am suggesting to use the sphinxcontrib-bibtex library. We have to keep a bibtex file, which many scientists in our field are familiar with. Then you can easily cite references in the docs and they get rendered in a consistent way.

  2. For the code my idea is to introduce an ArchitectureInfo class, where each Architecture has to define some meta data. This meta data includes a property references which for simplicity should be list of strings. This list will get formatted and displayed during training.

I know this may somehow a bit of a duplication for references but I think putting a bibtex parser to the code is an overkill and on top printing five lines (as usually for a real paper like reference) per references is too much for a logfile.

On the other hand having nice formatted references in the actual docs is nice and there, at least for me sphinxcontrib-bibtex seems like a good solution.

Let me know what you think

@Luthaf Luthaf added infrastructure Documentation Improvements or additions to documentation labels Feb 26, 2024
@PicoCentauri PicoCentauri added the Priority: Low Non-urgent issues to handle last. label Jun 3, 2024
@PicoCentauri PicoCentauri added Infrastructure: Logging Related to logging and removed infrastructure labels Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Improvements or additions to documentation Infrastructure: Logging Related to logging Priority: Low Non-urgent issues to handle last.
Projects
None yet
Development

No branches or pull requests

3 participants