10-11-2023, 02:50 PM
I have stopped counting the runs...
most of them have not been very good... The major issue is that trade signals are followed even when volume is clearly too low to confirm the signal...
The system description only says that when volume is above average, this is your confirmation. That might be enough in fx trading or stock market or any other traditional market...
but in crypto, beside maybe on the top 3 exchanges... Above average is not enough because in most markets, the volume is very low... I have kept raising the bar on which my system only consider signals above it...
maybe I am too conservative or too prudent in raising the bar as I have kept being bitten by the invalid signals due to unrecognized low volume...
but now, since the last time that I have rise the volume bar, the signals have become a desert... Beside last week-end because of extreme geopolitical events, the trading volume has been very low...
but the work around this last system did made me make some fundamental realizations... Those realizations are really going to pay off down the road...
Beside that, the refactoring driven by the need of the latest trading system did made me uncover 2 very small bugs. They were small but very serious in terms of their impact on the overall accuracy of the system.
One is very recent. It got introduced in the last week when I wrote the last system code... The other one has been lurking for much more time... I estimate it to have been around for at least 4 months...
Seeing it and fixing it has been a great catch... I have deployed the fix this morning... Alas, due to low volume, I have not yet noticed any improvements... but I am sure it will... It was in part responsible for the bad performance of my last system...
I really wonder if those 2 small bugs are just some random honest mistakes or if they are part of some unconscious sabotage... I guess that I will never know... and my project keeps moving forward...
most of them have not been very good... The major issue is that trade signals are followed even when volume is clearly too low to confirm the signal...
The system description only says that when volume is above average, this is your confirmation. That might be enough in fx trading or stock market or any other traditional market...
but in crypto, beside maybe on the top 3 exchanges... Above average is not enough because in most markets, the volume is very low... I have kept raising the bar on which my system only consider signals above it...
maybe I am too conservative or too prudent in raising the bar as I have kept being bitten by the invalid signals due to unrecognized low volume...
but now, since the last time that I have rise the volume bar, the signals have become a desert... Beside last week-end because of extreme geopolitical events, the trading volume has been very low...
but the work around this last system did made me make some fundamental realizations... Those realizations are really going to pay off down the road...
Beside that, the refactoring driven by the need of the latest trading system did made me uncover 2 very small bugs. They were small but very serious in terms of their impact on the overall accuracy of the system.
One is very recent. It got introduced in the last week when I wrote the last system code... The other one has been lurking for much more time... I estimate it to have been around for at least 4 months...
Seeing it and fixing it has been a great catch... I have deployed the fix this morning... Alas, due to low volume, I have not yet noticed any improvements... but I am sure it will... It was in part responsible for the bad performance of my last system...
I really wonder if those 2 small bugs are just some random honest mistakes or if they are part of some unconscious sabotage... I guess that I will never know... and my project keeps moving forward...
