Open tomjrtsmith opened 12 months ago
ExaByt3s
commented
10 months ago Hello @nateemma , good job, I see that you have made big changes throughout the code, it seems good, on this occasion I would like to know what version of tensorflow you are using.
tomjrtsmith
commented
10 months ago This is TS_Wavelet (old version) running long short.
It seems to be willfully ignoring market direction and fwr entry points, I've got long entry at -0.8 and short at 1.0 and it still wants to enter shorts any old place.
On Mon, Dec 11, 2023 at 2:13 PM Exabyte @.***> wrote:
Hello @nateemma https://github.com/nateemma , good job, I see that you have made big changes throughout the code, it seems good, on this occasion I would like to know what version of tensorflow you are using.
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1849172496, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXUNNMNBNO5NP2ES6GE5B3YIZM4FAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBZGE3TENBZGY . You are receiving this because you authored the thread.Message ID: @.***>
nateemma
commented
10 months ago tensorflow 2.15 currently
On Sun, Dec 10, 2023 at 5:13 PM Exabyte @.***> wrote:
Hello @nateemma https://github.com/nateemma , good job, I see that you have made big changes throughout the code, it seems good, on this occasion I would like to know what version of tensorflow you are using.
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1849172496, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABD4X5ZYSHP3XKYIWOQSCFDYIZM4FAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBZGE3TENBZGY . You are receiving this because you were mentioned.Message ID: @.***>
nateemma
commented
10 months ago is there anywhere I can view the code? Also, what kind of entry/exit_pricing settings are you using in your config file?
Cheers,
Phil
On Mon, Dec 11, 2023 at 5:50 PM tom s @.***> wrote:
This is TS_Wavelet (old version) running long short.
It seems to be willfully ignoring market direction and fwr entry points, I've got long entry at -0.8 and short at 1.0 and it still wants to enter shorts any old place.
On Mon, Dec 11, 2023 at 2:13 PM Exabyte @.***> wrote:
Hello @nateemma https://github.com/nateemma , good job, I see that you have made big changes throughout the code, it seems good, on this occasion I would like to know what version of tensorflow you are using.
— Reply to this email directly, view it on GitHub < https://github.com/nateemma/strategies/issues/38#issuecomment-1849172496>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AXXUNNMNBNO5NP2ES6GE5B3YIZM4FAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBZGE3TENBZGY>
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1851176348, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABD4X5ZDFJGNYGBD36LI4FLYI6Z63AVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJRGE3TMMZUHA . You are receiving this because you were mentioned.Message ID: @.***>
tomjrtsmith
commented
10 months ago I sent you a access to my repo, production file is TS_Wavelet_5.py
Repo is a bit of a mess sorry lots of half finished files.
Price side same and I'm still using limit orders, I can change it to other/market.
It seems to be profitable I'm just intrigued by the sheer volume of short entries and the fact they seem impervious to any fwr settings but I may have done something wrong.
On Tue, Dec 12, 2023 at 6:26 PM Nateemma @.***> wrote:
is there anywhere I can view the code? Also, what kind of entry/exit_pricing settings are you using in your config file?
Cheers,
Phil
On Mon, Dec 11, 2023 at 5:50 PM tom s @.***> wrote:
This is TS_Wavelet (old version) running long short.
It seems to be willfully ignoring market direction and fwr entry points, I've got long entry at -0.8 and short at 1.0 and it still wants to enter shorts any old place.
On Mon, Dec 11, 2023 at 2:13 PM Exabyte @.***> wrote:
Hello @nateemma https://github.com/nateemma , good job, I see that you have made big changes throughout the code, it seems good, on this occasion I would like to know what version of tensorflow you are using.
— Reply to this email directly, view it on GitHub < https://github.com/nateemma/strategies/issues/38#issuecomment-1849172496>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/nateemma/strategies/issues/38#issuecomment-1851176348>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABD4X5ZDFJGNYGBD36LI4FLYI6Z63AVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJRGE3TMMZUHA>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1851324257, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXUNNIE4LJ7HZZD7DGOY6LYI7TG7AVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJRGMZDIMRVG4 . You are receiving this because you authored the thread.Message ID: @.***>
nateemma
commented
10 months ago Not sure if this makes a difference, but in your declarations of short_entry_fwr and long_entry_fwr, you need to reverse the min/max values:
long_entry_fwr = DecimalParameter(-1.0, 0.0, default=-0.0, decimals=1,space='buy', load=True, optimize=True) short_entry_fwr = DecimalParameter(0.0, 1.0, default=0.0, decimals=1, space='buy', load=True, optimize=True)
long_exit_fwr = DecimalParameter(0.0, 1.0, default=0.0, decimals=1,space='sell', load=True, optimize=True) short_exit_fwr = DecimalParameter(-1.0, 0.0, default=0.0, decimals=1, space='sell', load=True, optimize=True)
With fisher_wr, positive values indicate overbought conditions, and negative values indicate oversold conditions.
Also, in TS_Wavelet5.json you have the following values set:
"long_entry_fwr": -0.8,
"short_exit_fwr": -0.3
"short_entry_fwr": 1.0,
"long_exit_fwr": 0.3Those values take precedence over what you set in the python declaration. I think you probably want the short values inverted (+0.3 and -0.3). If you want to set the values in the .py file then just delete the .json file (it is generated by hyperopt)
Hope that helps,
Cheers,
Phil
On Mon, Dec 11, 2023 at 10:19 PM tom s @.***> wrote:
I sent you a access to my repo, production file is TS_Wavelet_5.py
Repo is a bit of a mess sorry lots of half finished files.
Price side same and I'm still using limit orders, I can change it to other/market.
It seems to be profitable I'm just intrigued by the sheer volume of short entries and the fact they seem impervious to any fwr settings but I may have done something wrong.
On Tue, Dec 12, 2023 at 6:26 PM Nateemma @.***> wrote:
is there anywhere I can view the code? Also, what kind of entry/exit_pricing settings are you using in your config file?
Cheers,
Phil
On Mon, Dec 11, 2023 at 5:50 PM tom s @.***> wrote:
This is TS_Wavelet (old version) running long short.
It seems to be willfully ignoring market direction and fwr entry points, I've got long entry at -0.8 and short at 1.0 and it still wants to enter shorts any old place.
Message ID: @.***>
tomjrtsmith
commented
10 months ago Thanks Phil that seemed to help.
The short signals still seem to conflict with the fwr settings.
Here it's gone short at fwr 0.9 with no signal, and the preceding two short signals are 0.4 and 0.5, short_entry_fwr is set to 0.9 in the json file.
On Wed, Dec 13, 2023 at 4:54 AM Nateemma @.***> wrote:
Not sure if this makes a difference, but in your declarations of short_entry_fwr and long_entry_fwr, you need to reverse the min/max values:
long_entry_fwr = DecimalParameter(-1.0, 0.0, default=-0.0, decimals=1, space='buy', load=True, optimize=True) short_entry_fwr = DecimalParameter(0.0, 1.0, default=0.0, decimals=1, space='buy', load=True, optimize=True)
long_exit_fwr = DecimalParameter(0.0, 1.0, default=0.0, decimals=1, space='sell', load=True, optimize=True) short_exit_fwr = DecimalParameter(-1.0, 0.0, default=0.0, decimals=1, space='sell', load=True, optimize=True)
With fisher_wr, positive values indicate overbought conditions, and negative values indicate oversold conditions.
Also, in TS_Wavelet5.json you have the following values set:
"long_entry_fwr": -0.8, "short_exit_fwr": -0.3
"short_entry_fwr": 1.0, "long_exit_fwr": 0.3
Those values take precedence over what you set in the python declaration. I think you probably want the short values inverted (+0.3 and -0.3). If you want to set the values in the .py file then just delete the .json file (it is generated by hyperopt)
Hope that helps,
Cheers,
Phil
On Mon, Dec 11, 2023 at 10:19 PM tom s @.***> wrote:
I sent you a access to my repo, production file is TS_Wavelet_5.py
Repo is a bit of a mess sorry lots of half finished files.
Price side same and I'm still using limit orders, I can change it to other/market.
It seems to be profitable I'm just intrigued by the sheer volume of short entries and the fact they seem impervious to any fwr settings but I may have done something wrong.
On Tue, Dec 12, 2023 at 6:26 PM Nateemma @.***> wrote:
is there anywhere I can view the code? Also, what kind of entry/exit_pricing settings are you using in your config file?
Cheers,
Phil
On Mon, Dec 11, 2023 at 5:50 PM tom s @.***> wrote:
This is TS_Wavelet (old version) running long short.
It seems to be willfully ignoring market direction and fwr entry points, I've got long entry at -0.8 and short at 1.0 and it still wants to enter shorts any old place.
Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1852317349, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXUNNJDNYGF5M6IR4FMJRTYJB43PAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSGMYTOMZUHE . You are receiving this because you authored the thread.Message ID: @.***>
nateemma
commented
10 months ago OK, I'm trying to get it running on my system, but in the meantime:
in populate_entry_trend and populate_exit_trend do not reuse the same variables for both long and short conditions. For example, for the short conditions change conditions to short_conditions and model_cond to short_model_cond
See if that helps
Cheers,
Phil
On Wed, Dec 13, 2023 at 4:11 PM tom s @.***> wrote:
Thanks Phil that seemed to help.
The short signals still seem to conflict with the fwr settings.
Here it's gone short at fwr 0.9 with no signal, and the preceding two short signals are 0.4 and 0.5, short_entry_fwr is set to 0.9 in the json file.
Message ID: @.***>
nateemma
commented
10 months ago Also, remove line 913:
dataframe.loc[:, 'enter_tag'] = ''
this is clearing the previous tags
I appears that I cannot run short strategies using BinanceUS...
Cheers,
Phil
On Thu, Dec 14, 2023 at 9:05 AM Phil Price @.***> wrote:
OK, I'm trying to get it running on my system, but in the meantime:
in populate_entry_trend and populate_exit_trend do not reuse the same variables for both long and short conditions. For example, for the short conditions change conditions to short_conditions and model_cond to short_model_cond
See if that helps
Cheers,
Phil
On Wed, Dec 13, 2023 at 4:11 PM tom s @.***> wrote:
Thanks Phil that seemed to help.
The short signals still seem to conflict with the fwr settings.
Here it's gone short at fwr 0.9 with no signal, and the preceding two short signals are 0.4 and 0.5, short_entry_fwr is set to 0.9 in the json file.
Message ID: @.***>
nateemma
commented
10 months ago ...and, thinking about it, custom_exit() will not work with short trades. If you set use_custom_stoploss to False it will also disable custom_exit, so you should probably do that for now
I'll look into at least checking whether an active trade is long or short
Cheers,
Phil
On Thu, Dec 14, 2023 at 9:45 AM Phil Price @.***> wrote:
Also, remove line 913:
dataframe.loc[:, 'enter_tag'] = ''
this is clearing the previous tags
I appears that I cannot run short strategies using BinanceUS...
Cheers,
Phil
On Thu, Dec 14, 2023 at 9:05 AM Phil Price @.***> wrote:
OK, I'm trying to get it running on my system, but in the meantime:
in populate_entry_trend and populate_exit_trend do not reuse the same variables for both long and short conditions. For example, for the short conditions change conditions to short_conditions and model_cond to short_model_cond
See if that helps
Cheers,
Phil
On Wed, Dec 13, 2023 at 4:11 PM tom s @.***> wrote:
Thanks Phil that seemed to help.
The short signals still seem to conflict with the fwr settings.
Here it's gone short at fwr 0.9 with no signal, and the preceding two short signals are 0.4 and 0.5, short_entry_fwr is set to 0.9 in the json file.
Message ID: @.***>
tomjrtsmith
commented
10 months ago I rewrote predict_drop using trade.is_short so now there's predict_drop and predict_gain and I flipped a few of the other conditions so custom exit works.
All the exit signals work long and short now and it's obeying the fwr settings for longs but it still won't seem to stick to them for shorts.
On Fri, Dec 15, 2023 at 7:19 AM Nateemma @.***> wrote:
...and, thinking about it, custom_exit() will not work with short trades. If you set use_custom_stoploss to False it will also disable custom_exit, so you should probably do that for now
I'll look into at least checking whether an active trade is long or short
Cheers,
Phil
On Thu, Dec 14, 2023 at 9:45 AM Phil Price @.***> wrote:
Also, remove line 913:
dataframe.loc[:, 'enter_tag'] = ''
this is clearing the previous tags
I appears that I cannot run short strategies using BinanceUS...
Cheers,
Phil
On Thu, Dec 14, 2023 at 9:05 AM Phil Price @.***> wrote:
OK, I'm trying to get it running on my system, but in the meantime:
in populate_entry_trend and populate_exit_trend do not reuse the same variables for both long and short conditions. For example, for the short conditions change conditions to short_conditions and model_cond to short_model_cond
See if that helps
Cheers,
Phil
On Wed, Dec 13, 2023 at 4:11 PM tom s @.***> wrote:
Thanks Phil that seemed to help.
The short signals still seem to conflict with the fwr settings.
Here it's gone short at fwr 0.9 with no signal, and the preceding two short signals are 0.4 and 0.5, short_entry_fwr is set to 0.9 in the json file.
Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1856360387, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXUNNITWDFQV2KWJMNIXG3YJM7MBAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWGM3DAMZYG4 . You are receiving this because you authored the thread.Message ID: @.***>
tomjrtsmith
commented
10 months ago from freqtrade import leverage
tomjrtsmith
commented
10 months ago Oops ... this implementation of leverage doesn't seem to work ...
On Sun, Dec 17, 2023 at 3:17 PM Tom Smith @.***> wrote:
from freqtrade import leverage
nateemma
commented
10 months ago haven't had time to look closely, but it looks like some of your thresholds are reversed.
For example:
cexit_long_fwr_overbought = DecimalParameter(0.90, 1.00, default=0.98,decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_oversold = DecimalParameter(0.90, 1.00, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_long_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True)
should be:
cexit_long_fwr_overbought = DecimalParameter(0.90, 1.00, default=0.98,decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_oversold = DecimalParameter(-1.00,-0.90, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_long_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_take_profit = DecimalParameter(-1.00, -0.90, default=0.90, decimals=2, space='sell', load=True, optimize=True)
they seem correct in the .json file though
also, remove line 909:
dataframe.loc[:, 'enter_tag'] = ''and line 1007:
dataframe.loc[:, 'exit_tag'] = ''these don't affect functionality but it does reset the long-tracing tags
Cheers,
Phil
On Sat, Dec 16, 2023 at 6:18 PM tom s @.***> wrote:
Oops ... this implementation of leverage doesn't seem to work ...
On Sun, Dec 17, 2023 at 3:17 PM Tom Smith @.***> wrote:
from freqtrade import leverage
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1859016428, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABD4X54KKY4WQAACBPRUTFLYJZI6VAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGAYTMNBSHA . You are receiving this because you were mentioned.Message ID: @.***>
tomjrtsmith
commented
10 months ago Thanks Phil,
also, remove line 909:
dataframe.loc[:, 'enter_tag'] = ''
and line 1007:
dataframe.loc[:, 'exit_tag'] = ''
I took these out and now it doesn't look like it's entering long trades, only shorts.
On Mon, Dec 18, 2023 at 3:03 PM Nateemma @.***> wrote:
haven't had time to look closely, but it looks like some of your thresholds are reversed.
For example:
cexit_long_fwr_overbought = DecimalParameter(0.90, 1.00, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_oversold = DecimalParameter(0.90, 1.00, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_long_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True)
should be:
cexit_long_fwr_overbought = DecimalParameter(0.90, 1.00, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_oversold = DecimalParameter(-1.00,-0.90, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_long_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_take_profit = DecimalParameter(-1.00, -0.90, default=0.90, decimals=2, space='sell', load=True, optimize=True)
they seem correct in the .json file though
also, remove line 909:
dataframe.loc[:, 'enter_tag'] = ''
and line 1007:
dataframe.loc[:, 'exit_tag'] = ''
these don't affect functionality but it does reset the long-tracing tags
Cheers,
Phil
On Sat, Dec 16, 2023 at 6:18 PM tom s @.***> wrote:
Oops ... this implementation of leverage doesn't seem to work ...
On Sun, Dec 17, 2023 at 3:17 PM Tom Smith @.***> wrote:
from freqtrade import leverage
— Reply to this email directly, view it on GitHub < https://github.com/nateemma/strategies/issues/38#issuecomment-1859016428>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABD4X54KKY4WQAACBPRUTFLYJZI6VAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGAYTMNBSHA>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1859425982, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXUNNPINMXH77FC3FZD3BTYJ6P7FAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGQZDKOJYGI . You are receiving this because you authored the thread.Message ID: @.***>
tomjrtsmith
commented
10 months ago I think RMI is a better indicator than WR. It seems to work better with the prediction algo. I had it working using the BB-RPB rmi_17 implementation but I. can't seem to get it working without a key error.
On Tue, Dec 19, 2023 at 12:55 PM Tom Smith @.***> wrote:
Thanks Phil,
also, remove line 909:
dataframe.loc[:, 'enter_tag'] = ''
and line 1007:
dataframe.loc[:, 'exit_tag'] = ''
I took these out and now it doesn't look like it's entering long trades, only shorts.
On Mon, Dec 18, 2023 at 3:03 PM Nateemma @.***> wrote:
haven't had time to look closely, but it looks like some of your thresholds are reversed.
For example:
cexit_long_fwr_overbought = DecimalParameter(0.90, 1.00, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_oversold = DecimalParameter(0.90, 1.00, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_long_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True)
should be:
cexit_long_fwr_overbought = DecimalParameter(0.90, 1.00, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_oversold = DecimalParameter(-1.00,-0.90, default=0.98, decimals=2, space='sell', load=True, optimize=True) cexit_long_fwr_take_profit = DecimalParameter(0.90, 1.00, default=0.90, decimals=2, space='sell', load=True, optimize=True) cexit_short_fwr_take_profit = DecimalParameter(-1.00, -0.90, default=0.90, decimals=2, space='sell', load=True, optimize=True)
they seem correct in the .json file though
also, remove line 909:
dataframe.loc[:, 'enter_tag'] = ''
and line 1007:
dataframe.loc[:, 'exit_tag'] = ''
these don't affect functionality but it does reset the long-tracing tags
Cheers,
Phil
On Sat, Dec 16, 2023 at 6:18 PM tom s @.***> wrote:
Oops ... this implementation of leverage doesn't seem to work ...
On Sun, Dec 17, 2023 at 3:17 PM Tom Smith @.***> wrote:
from freqtrade import leverage
— Reply to this email directly, view it on GitHub < https://github.com/nateemma/strategies/issues/38#issuecomment-1859016428>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABD4X54KKY4WQAACBPRUTFLYJZI6VAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGAYTMNBSHA>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/nateemma/strategies/issues/38#issuecomment-1859425982, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXUNNPINMXH77FC3FZD3BTYJ6P7FAVCNFSM6AAAAAA6JYNPWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGQZDKOJYGI . You are receiving this because you authored the thread.Message ID: @.***>
Hey Phil,
TS_Simple is throwing out this error, seems to be a dataframe index length error. I've added one or two additional indicators but that is all. Wondered if any code fixes sprang to mind, seems to run ok on a couple of machines but not others.
Oct 21 00:31:08 instance-20220819-1716 freqtrade_ft3b[590203]: 2023-10-21 00:31:08,362 - freqtrade.strategy.strategy_wrapper - WARNING - Strategy caused the following exception: Length of values (974) does not match length of index (1033)<bound method IStrategy._analyze_ticker_internal of <TS_Simple.TS_Simple object at 0xffff6e8c9a50>> Oct 21 00:31:08 instance-20220819-1716 freqtrade_ft3b[590203]: 2023-10-21 00:31:08,362 - freqtrade.strategy.interface - WARNING - Unable to analyze candle (OHLCV) data for pair XRP/USDT:USDT: Length of values (974) does not match length of index (1033) Oct 21 00:31:08 instance-20220819-1716 freqtrade.strategy.strategy_wrapper - WARNING - Strategy caused the following exception: Length of values (974) does not match length of index (1033)<bound method IStrategy._analyze_ticker_internal of <TS_Simple.TS_Simple object at 0xffff6e8c9a50>>