You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the dynamic world of quantitative trading, **factors** are the secret weapons that traders use to harness market inefficiencies.
14
14
15
15
These powerful tools—ranging from straightforward metrics like price-to-earnings ratios to intricate discounted cash flow models—unlock the potential to predict stock prices with remarkable precision.
@@ -18,8 +18,13 @@ By tapping into this rich vein of data, quantitative traders craft sophisticated
18
18
Embrace the power of factors, and you're not just trading; you're strategically outsmarting the market.
19
19
20
20
21
-
Introduction
22
-
~~~~~~~~~~~~
21
+
🎥 Demo
22
+
~~~~~~~~~~
23
+
TODO: Here should put a video of the demo.
24
+
25
+
26
+
🌟 Introduction
27
+
~~~~~~~~~~~~~~~~
23
28
In this scenario, our agent illustrates the iterative process of hypothesis generation, knowledge construction, and decision-making.
24
29
25
30
It highlights how financial factors evolve through continuous feedback and refinement.
@@ -43,7 +48,7 @@ Here's an enhanced outline of the steps:
43
48
**Step 4 : Backtesting with Qlib 📉**
44
49
45
50
- Integrate the full dataset into the factor implementation code and prepare the factor library.
46
-
- Perform backtesting using the Alpha158+ model in Qlib to assess the factor's effectiveness and performance.
51
+
- Conduct backtesting using the Alpha158 plus newly developed factors and LGBModel in Qlib to evaluate the new factors' effectiveness and performance.
@@ -59,27 +64,101 @@ Here's an enhanced outline of the steps:
59
64
60
65
61
66
**Step 5 : Feedback Analysis 🔍**
62
-
- Analyze backtest results.
63
-
- Incorporate feedback to refine hypotheses.
67
+
68
+
- Analyze backtest results to assess performance.
69
+
- Incorporate feedback to refine hypotheses and improve the model.
64
70
65
71
**Step 6 :Hypothesis Refinement ♻️**
66
-
- Refine hypotheses based on feedback and repeat the process.
67
72
68
-
Demo
69
-
~~~~~~~~~~
70
-
.. TODO
73
+
- Refine hypotheses based on feedback from backtesting.
74
+
- Repeat the process to continuously improve the model.
71
75
72
-
Quick Start
76
+
⚡ Quick Start
73
77
~~~~~~~~~~~~~~~~~
74
78
75
-
To quickly start the Automated Quantitative Trading & Iterative Factors Evolution process, run the following command in your terminal within the `rdagent` virtual environment:
79
+
You can try our demo by running the following command:
76
80
77
-
.. code-block:: sh
81
+
- 🐍 Create a Conda Environment
82
+
- Create a new conda environment with Python (3.10 and 3.11 are well tested in our CI):
83
+
84
+
.. code-block:: sh
85
+
86
+
conda create -n rdagent python=3.10
78
87
79
-
python rdagent/app/qlib_rd_loop/factor_w_sc.py
88
+
- Activate the environment:
80
89
90
+
.. code-block:: sh
81
91
82
-
Usage of modules
83
-
~~~~~~~~~~~~~~~~~
84
-
TODO: Show some examples:
92
+
conda activate rdagent
93
+
94
+
- 🛠️ Run Make Files
95
+
- Navigate to the directory containing the MakeFile and set up the development environment:
- Place the `.env` file in the same directory as the `.env.example` file.
111
+
- The `.env.example` file contains the environment variables required for users using the OpenAI API (Please note that `.env.example` is an example file. `.env` is the one that will be finally used.)
112
+
113
+
- Export each variable in the .env file:
114
+
115
+
.. code-block:: sh
116
+
117
+
export$(grep -v '^#' .env | xargs)
118
+
119
+
- If you want to change the default environment variables, you can refer to `Env Config`_ below
120
+
121
+
- 🚀 Run the Application
122
+
.. code-block:: sh
123
+
124
+
python rdagent/app/qlib_rd_loop/factor_w_sc.py
125
+
126
+
127
+
🛠️ Usage of modules
128
+
~~~~~~~~~~~~~~~~~~~~~
129
+
130
+
.. _Env Config:
131
+
132
+
- **Env Config**
133
+
134
+
The following environment variables can be set in the `.env` file to customize the application's behavior:
135
+
- **Path to the folder containing private data (default fundamental data in Qlib):**
**Research reports** are treasure troves of insights, often unveiling potential **factors** that can drive successful quantitative trading strategies.
14
14
Yet, with the sheer volume of reports available, extracting the most valuable insights efficiently becomes a daunting task.
15
15
16
16
Furthermore, rather than hastily replicating factors from a report, it's essential to delve into the underlying logic of their construction.
17
17
Does the factor capture the essential market dynamics? How unique is it compared to the factors already in your library?
18
18
19
19
Therefore, there is an urgent need for a systematic approach to design a framework that can effectively manage this process.
20
-
This is where our R&D Agent comes into play.
20
+
This is where our RDAgent comes into play.
21
+
21
22
23
+
🎥 Demo
24
+
~~~~~~~~~~
25
+
TODO: Here should put a video of the demo.
22
26
23
27
24
-
Introduction
25
-
~~~~~~~~~~~~
26
-
In this scenario, our agent demonstrates the process of extracting factors from financial research reports, implementing these factors, and analyzing their performance through Qlib backtesting.
28
+
🌟 Introduction
29
+
~~~~~~~~~~~~~~~~
30
+
In this scenario, RDAgent demonstrates the process of extracting factors from financial research reports, implementing these factors, and analyzing their performance through Qlib backtesting.
27
31
This process continually expands and refines the factor library.
28
32
29
33
Here's an enhanced outline of the steps:
@@ -45,7 +49,7 @@ Here's an enhanced outline of the steps:
45
49
**Step 4 : Backtesting with Qlib 📉**
46
50
47
51
- Integrate the full dataset into the factor implementation code and prepare the factor library.
48
-
- Perform backtesting using the Alpha158+ model in Qlib to assess the factor's effectiveness and performance.
52
+
- Conduct backtesting using the Alpha158 plus newly developed factors and LGBModel in Qlib to evaluate the new factors' effectiveness and performance.
- Place the `.env` file in the same directory as the `.env.example` file.
111
+
- The `.env.example` file contains the environment variables required for users using the OpenAI API (Please note that `.env.example` is an example file. `.env` is the one that will be finally used.)
112
+
113
+
- Export each variable in the .env file:
114
+
115
+
.. code-block:: sh
116
+
117
+
export$(grep -v '^#' .env | xargs)
118
+
119
+
- If you want to change the default environment variables, you can refer to `Env Config`_ below
0 commit comments