-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update docs to AiiDA v2.x and Jupyter Book #116
Labels
Comments
Irratzo
changed the title
Update docs to AiiDA v2.x and switch src from RST to MyST or notebooks
Update docs to AiiDA v2.x and switch src from RST to MyST or Jupyter Book
Dec 6, 2022
Irratzo
changed the title
Update docs to AiiDA v2.x and switch src from RST to MyST or Jupyter Book
Update docs to AiiDA v2.x and switch src from RST to MyST or Jupyter notebooks
Dec 6, 2022
Created branch support/aiida-2.x-docs from branch Commit commit 01 of improvement 'migrate docs to MyST'. Ran RST-to-MyST converter on all docs at once, as described in its docs. $ cd /opt/aiida-kkr/docs/source
$ rst2myst convert docs/**/*.rst Result:
Output:
TODO:
|
Irratzo
changed the title
Update docs to AiiDA v2.x and switch src from RST to MyST or Jupyter notebooks
Update docs to AiiDA v2.x and Jupyter Book
Dec 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an AiiDA-KKR improvements issue.
All references to repositories in this post are permalinks to latest commits at time of writing, for archival purposes.
The current documentation is out of date.
(One example: User's guide example uses length unit Angstroem, but kkrparams switched to length unit Bohr.)
((In more detail: JuKKR internally uses Bohr length units. AiiDA-KKR uses Angstrom units and
converts as needed. For instance, the
impurity_info
Dict
node assumes its propertiesRcut
to be given in Angstrom units, butRimp_rel
andimp_cls
to be given in ALAT units. This info should be added to theimpurity_info
docs section. That is why, for instance,plot_kkr_imp_sub_wc
converts back and forth with ALAT units.))In addition, the plugin migration to AiiDA v2.x is finished.
In addition, the current docs source format is reStructuredText (RST). RST is good for technical documentation, but complex to use. The Executable Books Project has made writing such text simpler by creating both the MyST format (a Markdown flavor for technical writing, inspired by RST but simpler to use), and the possibility to write docs as Jupyter notebooks (
.ipynb
) (Jupyter Book). For example, the JuDFTteam masci-tools docs have switched to MyST, and chrisjsewell (AiiDA and Executable Books Project contributor) has created aiida-qe-demo, a tutorial based solely on Jupyter notebook source format. The latter has the additional feature supported by Jupyter Book projects that a docs page has a 'launch' button, allowing the reader to execute the respective page as a notebook directly from their browser in a computational environment without installation, like Binder or Google Colab.So, this improvements issue has two aims.
For subtask two, this means that the current docs will be the last version aimed at AiiDA-KKR used with AiiDA v1.x. We skip the subtask of first updating to docs to the current state of AiiDA-KKR used with AiiDA v1.x. (such as the initial example).
For subtask one, it is worthwhile to note that MyST / Jupyter Book -- based docs accept as source format either RST (
.rst
), MyST Markdown (.md
), or Jupyter notebooks (.ipynb
). Assisted conversion from RST to MyST is possible via the tool RST-to-MyST, and conversion (or, alternatively, local syncing between) MyST and Jupyter notebook is possible via the tool Jupytext. Both are mentioned in the Jupyter Book docs and MyST docs. At this point we have only decided to switch from RST to MyST or notebooks as source format, but not on the latter.We will use the masci-tools and aiida-qe-demo docs as guiding examples.
An additional subtask is that aiida-kkr has an examples folder
/examples
, outside of the/docs
, with Jupyter notebooks in various stages of outdatedness. These also should be integrated into the "new" docs.Additional resources for using Jupyter Book for documentation:
The text was updated successfully, but these errors were encountered: