Document in High-level (#93)

* Add init information

* Adjust order and move content

* GPU support

* edit docs

* README structure

* Update Dockerfile

* Update rdagent/utils/env.py

* Update read the docs

* Update framework
This commit is contained in:
you-n-g
2024-07-22 12:49:03 +08:00
committed by GitHub
parent 444a773259
commit 15dbdb68d5
12 changed files with 199 additions and 177 deletions
BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 115 KiB

+10 -13
View File
@@ -1,18 +1,15 @@
=========================
API reference
=========================
=============
API Reference
=============
title1
=========================
Here you can find all ``RDAgent``'s interfaces.
content1
title2
=========================
RD Loop
=======
content2
Research
--------
title3
=========================
content3
.. automodule:: rdagent.core.proposal
:members:
+3 -1
View File
@@ -15,7 +15,9 @@ author = "Microsoft"
# -- General configuration ---------------------------------------------------
# https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration
extensions = []
extensions = [
'sphinx.ext.autodoc',
]
autodoc_member_order = "bysource"
+9 -9
View File
@@ -2,17 +2,17 @@
Demo and Introduction
=========================
title1
=========================
Introduction
============
content1
TODO: copy the content in the README.md
title2
=========================
A Quick Demo
============
content2
TODO:
- copy the demo content in the README.md
- Quick start for the demo.
title3
=========================
content3
TODO: link to more demos
+59 -7
View File
@@ -2,17 +2,69 @@
For Development
=========================
title1
🔧Prepare for development
=========================
content1
- Set up the development environment.
title2
```bash
make dev
```
- Run linting and formatting.
```bash
make lint
```
Code Structure
=========================
content2
.. code-block:: text
title3
=========================
📂 src
➥ 📂 <project name>: avoid namespace conflict
➥ 📁 core
➥ 📁 components/A
➥ 📁 components/B
➥ 📁 components/C
➥ 📁 scenarios/X
➥ 📁 scenarios/Y
➥ 📂 app
➥ 📁 scripts
content3
.. list-table::
:header-rows: 1
* - Folder Name
- Description
* - 📁 core
- The core framework of the system. All classes should be abstract and usually can't be used directly.
* - 📁 component/A
- Useful components that can be used by others (e.g., scenarios). Many subclasses of core classes are located here.
* - 📁 scenarios/X
- Concrete features for specific scenarios (usually built based on components or core). These modules are often unreusable across scenarios.
* - 📁 app
- Applications for specific scenarios (usually built based on components or scenarios). Removing any of them does not affect the system's completeness or other scenarios.
* - 📁 scripts
- Quick and dirty things. These are candidates for core, components, scenarios, and apps.
Conventions
===========
File Naming Convention
----------------------
.. list-table::
:header-rows: 1
* - Name
- Description
* - `conf.py`
- The configuration for the module, app, and project.
<!-- TODO: renaming files -->
+7 -5
View File
@@ -7,16 +7,18 @@ Welcome to RDAgent's documentation!
===================================
.. toctree::
:maxdepth: 2
:maxdepth: 3
:caption: Doctree:
demo_and_introduction
installation
scenarios_and_quickstart
project_framework_introduction
development
api_reference
demo_and_introduction
project_framework_introduction
scenarios_and_quickstart
test_dropdown/test1
policy
.. test_dropdown/test1
Indices and tables
+8 -11
View File
@@ -2,17 +2,14 @@
Installation
=========================
title1
=========================
Installation
============
content1
For different scenarios
- for purely users:
- for dev users: link to development
title2
=========================
Configuration
=============
content2
title3
=========================
content3
Quick configuration
+17 -8
View File
@@ -1,18 +1,27 @@
===============================
Project framework introduction
Framework Design & Components
===============================
title1
Framework & Components
=========================
content1
- TODO: Components & Feature Level
title2
- Class Level Figure
Detailed Design
=========================
content2
title3
=========================
Configuration
-------------
You can manually source the `.env` file in your shell before running the Python script:
Most of the workflow are controlled by the environment variables.
```sh
# Export each variable in the .env file; Please note that it is different from `source .env` without export
export $(grep -v '^#' .env | xargs)
# Run the Python script
python your_script.py
```
content3
+22 -7
View File
@@ -2,17 +2,32 @@
Scenarios and Quick Start
=========================
title1
Scenario lists
=========================
content1
TODO: Copy the content in the README.md
title2
Scnarios' demo & quick start
=========================
content2
Scen1
-----
title3
=========================
Scen1 Intro
~~~~~~~~~~~
Scen1 Demo
~~~~~~~~~~
Scen1 Quick Start
~~~~~~~~~~~~~~~~~
Usage of modules
================
TODO: Show some examples:
content3
+1 -1
View File
@@ -25,4 +25,4 @@ content3
:caption: Doctree:
:hidden:
test2
test2