-
Notifications
You must be signed in to change notification settings - Fork 31
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
[FEATURE REQUEST] Update User's Guide for HEMCO 3.0.0 release #36
Comments
This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the Stale bot from closing this issue. |
The HEMCO user's guide has been moved to https://hemco.readthedocs.io/en/latest/. Right now, the basics for getting started are included there. I still plan to add more detailed information there prior to the final 3.0.0 release. |
Hi Melissa, Thanks so much for working on the documentation. I was looking at the HEMCO documentation at Readthedocs earlier and noticed that it doesn't have a stylesheet like the GCHP documentation. I was wondering if maybe the theme isn't being included? I've tried several browsers and they all display like this: Best, |
We had the same issue on the HEMCO ReadTheDocs page as on the GEOS-Chem ReadTheDocs. RTD now uses Sphinx v4.0.0 which seems to be problematic. The fix is to restrict the version numbers of Sphinx and other Python modules as in commit: 927f625 |
We can close out this issue because we now have good stable documentation at https://hemco.readthedocs.io. |
The HEMCO User's Guide currently at http:https://wiki.seas.harvard.edu/geos-chem/index.php/The_HEMCO_User's_Guide contains a lot of information on a single page and is outdated in many places. The documentation needs to be updated to reflect the updates in this repository. This should be complete by the HEMCO 3.0.0 release, which will be concurrent with the GEOS-Chem 13.0.0 release.
The text was updated successfully, but these errors were encountered: