Commit 24827f2c authored by stephen.wang's avatar stephen.wang

更新config -> 換數位部的API(基金數據源)/新增emmarket_prr5

parent 7f64610b
......@@ -42,7 +42,7 @@ py-jftech:
hold-report: portfolios.holder.DivHoldReportor
mpt: portfolios.builder.PoemARCPortfoliosBuilder # RiskParityARCPortfoliosBuilder/PoemARCPortfoliosBuilder
dividend-holder: portfolios.holder.InvTrustPortfoliosHolder
navs-sync: basic.sync.FundNavSync
navs-sync: basic.sync.TWFundNavSync
email:
server: smtphz.qiye.163.com
user: jft-ra@thizgroup.com
......@@ -253,7 +253,7 @@ robo-executor: # 执行器相关
sync-data: ${SYNC_DATA:on} # 是否开启同步资料数据
backtest: # 回测执行器相关
start-date: 2013-01-02 # 回测起始日期
end-date: 2025-08-01 # 回测截止日期
end-date: 2025-11-26 # 回测截止日期
sealing-period: 10 #调仓封闭期
start-step: ${BACKTEST_START_STEP:1} # 回测从哪一步开始执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
end-step: ${BACKTEST_END_STEP:3} # 回测从哪一步执行完成后结束执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
......
This diff is collapsed.
......@@ -42,7 +42,7 @@ py-jftech:
hold-report: portfolios.holder.DivHoldReportor
mpt: portfolios.builder.PoemARCPortfoliosBuilder # PoemARCPortfoliosBuilder, RiskParityARCPortfoliosBuilder
dividend-holder: portfolios.holder.InvTrustPortfoliosHolder
navs-sync: basic.sync.FundNavSync
navs-sync: basic.sync.TWFundNavSync
email:
server: smtphz.qiye.163.com
user: jft-ra@thizgroup.com
......@@ -245,7 +245,7 @@ robo-executor: # 执行器相关
sync-data: ${SYNC_DATA:on} # 是否开启同步资料数据
backtest: # 回测执行器相关
start-date: 2013-01-02 # 回测起始日期
end-date: 2025-08-01 # 回测截止日期
end-date: 2025-11-26 # 回测截止日期
sealing-period: 10 #调仓封闭期
start-step: ${BACKTEST_START_STEP:1} # 回测从哪一步开始执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
end-step: ${BACKTEST_END_STEP:3} # 回测从哪一步执行完成后结束执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
......
......@@ -42,7 +42,7 @@ py-jftech:
hold-report: portfolios.holder.DivHoldReportor
mpt: portfolios.builder.RiskParityARCPortfoliosBuilder # PoemARCPortfoliosBuilder,RiskParityARCPortfoliosBuilder
dividend-holder: portfolios.holder.InvTrustPortfoliosHolder
navs-sync: basic.sync.FundNavSync
navs-sync: basic.sync.TWFundNavSync
email:
server: smtphz.qiye.163.com
user: jft-ra@thizgroup.com
......@@ -259,7 +259,7 @@ robo-executor: # 执行器相关
sync-data: ${SYNC_DATA:on} # 是否开启同步资料数据
backtest: # 回测执行器相关
start-date: 2013-01-02 # 回测起始日期
end-date: 2025-08-01 # 回测截止日期
end-date: 2025-11-26 # 回测截止日期
sealing-period: 10 #调仓封闭期
start-step: ${BACKTEST_START_STEP:1} # 回测从哪一步开始执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
end-step: ${BACKTEST_END_STEP:3} # 回测从哪一步执行完成后结束执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
......
......@@ -42,7 +42,7 @@ py-jftech:
hold-report: portfolios.holder.DivHoldReportor
mpt: portfolios.builder.PoemARCPortfoliosBuilder # RiskParityARCPortfoliosBuilder/PoemARCPortfoliosBuilder
dividend-holder: portfolios.holder.InvTrustPortfoliosHolder
navs-sync: basic.sync.FundNavSync
navs-sync: basic.sync.TWFundNavSync
email:
server: smtphz.qiye.163.com
user: jft-ra@thizgroup.com
......@@ -251,7 +251,7 @@ robo-executor: # 执行器相关
sync-data: ${SYNC_DATA:on} # 是否开启同步资料数据
backtest: # 回测执行器相关
start-date: 2013-01-02 # 回测起始日期
end-date: 2025-08-01 # 回测截止日期
end-date: 2025-11-26 # 回测截止日期
sealing-period: 10 #调仓封闭期
start-step: ${BACKTEST_START_STEP:1} # 回测从哪一步开始执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
end-step: ${BACKTEST_END_STEP:3} # 回测从哪一步执行完成后结束执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
......
......@@ -42,7 +42,7 @@ py-jftech:
hold-report: portfolios.holder.DivHoldReportor
mpt: portfolios.builder.PoemARCPortfoliosBuilder
dividend-holder: portfolios.holder.InvTrustPortfoliosHolder
navs-sync: basic.sync.FundNavSync
navs-sync: basic.sync.TWFundNavSync
email:
server: smtphz.qiye.163.com
user: jft-ra@thizgroup.com
......@@ -250,7 +250,7 @@ robo-executor: # 执行器相关
sync-data: ${SYNC_DATA:on} # 是否开启同步资料数据
backtest: # 回测执行器相关
start-date: 2013-01-02 # 回测起始日期
end-date: 2025-08-01 # 回测截止日期
end-date: 2025-11-26 # 回测截止日期
sealing-period: 10 #调仓封闭期
start-step: ${BACKTEST_START_STEP:1} # 回测从哪一步开始执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
end-step: ${BACKTEST_END_STEP:3} # 回测从哪一步执行完成后结束执行 1:计算资产池;2:计算最优投组:3:计算再平衡信号以及持仓投组
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment