This folder contains code documentation for the BlueSky Prototype, which is documented using Sphinx. Sphinx allows us to automatically generate documentation from the codebase and provides outputs in various formats, including HTML and Markdown.
The energy model consists of several packages and subpackages that are organized into functional sections. The primary goal of the documentation is to help users understand how the different components fit together and how they can be used.
The documentation is generated using Sphinx, and the output is available in both HTML and Markdown formats. The documentation automatically captures docstrings from the code, organizes modules and packages, and provides references to each class, function, and method.
In general, the HTML code documentation provided in the docs
folder is the BEST method for exploring BlueSky code documentation. Below are instructions for viewing the html and markdown code documentation outputs.
-
Clone the BlueSky repository. Instructions can be found here
-
From the cloned bluesky_prototype directory, open the
docs
folder and click on the following file:html_documentation.bat
-
This should open the code documentation locally using your web browser.
-
From the cloned bluesky_prototype directory, Navigate to the following:
docs\build\html
-
Click on file called
index
. This should open a webpage and allow you to navigate and click on links to the code documentation.
Markdown Table of Contents
-
From the cloned bluesky_prototype directory in VS-Code, Navigate to the following:
docs\build\markdown
-
Click on file called
index
. Using the markdown preview functionality of VS-Code, you should be able to follow the markdown Table of contents list.
Use the PDF link on the Wiki homepage to access the latest version of code documentation. PDF documentation
Please note that this documentation is a work in progress. As the model evolves, additional details and sections will be added. The documents generated (html, markdown, pdf) are not meant for external publication at this time.
We welcome any feedback, suggestions, or contributions that could help improve the clarity and usefulness of the documentation. If you encounter any gaps or areas that need further explanation, feel free to open an issue or submit a pull request to enhance the documentation.