-
Notifications
You must be signed in to change notification settings - Fork 1
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
Map out structure of domzgr.F90 #2
Comments
HI guys, I generated the NEMO4.0.4-DOMAINcfg tool call tree documentation using doxygen ( https://www.doxygen.nl/index.html ) with graphviz ( http://www.graphviz.org ). As far I understood (from @malmans2 ’s notes), our documentation will be automatically generated and managed by Sphynx. |
As @malmans2 noted, we're not going to upload NEMO code on GitHub - so doc for FORTRAN DOMAINcfg needs to be generated only once. He suggests to put it into pyDOMCFG/docs/_static (maskes sense to me as well) and then just add a reference to it (I am not sure I understand this correctly - you mean in the index?). @malmans2 also asked about graphviz, since there is an extension for sphinx: https://www.sphinx-doc.org/en/master/usage/extensions/graphviz.html: Would a single .dot file work or we need an html tree? The .dot file can be embedded using: I checked and when running doxygen with graphviz no *.dot files are produced - so I think we might discard this option .... |
Actually, let me check if there's some kind of extension, because if you just link to the FORTRAN index.html then I doubt all links will work... |
Nevermind, maybe it just works.
then you can show the reference with:
I guess you could either place the link in our |
Add NEMO4 DOMAINcfg tool callgraph #2
Naive question: why the doc (https://pydomcfg.readthedocs.io/en/latest/) is not updated with my last merged modfications? |
I can see the call graph. Did you try to force refresh? |
Produce skeleton of domzgr.F90 routines to hang the python package on.
The text was updated successfully, but these errors were encountered: