VmaPredict2.js (new)

[PGTART]

new strategy based upon volume prediction and moving averages.
still tweaking it around, can do quite good to average ,but also loose a bit, overall its not a bad looser, reasonable above average

it can be found here https://github.com/PGTBoos/GekkoStrategies

Let me now your tweaking results or code alterations

Also I like to point out it has nice console log, and its realy handy to use as a template.
Its a code template i will stick too

a default TOML is included as well.

What are the parameters that you are testing with regarding candle size and warmup?

I Used 1 hour setting 10 hour warmup (one can use longer warmup equal to largest medium length since long periods where not used)
With some tweaking other periods and settings can make profit as well, i personally found it difficult with 5 minute ranges.
tweaking for 30 wouldnt take long just test it.

In general this could do slightly better then the market, i think.
It tries to find lower then averages to buy and higher then to sell, most of the times it works, but misstakes happen and can reduce profit.
At somepoint I made the BullsEye rule (take 1000 profit if it estimates it might becomme), it doesnt hurt it also allows for more trades.

For tweaking watch the console output none of the rules should dominate the output, some will be rarely though but it should be mixed.
Each rule has a certain chance to ocure and to make profit or take a loss. MaxPeekPred often makes a loss (but not always), but it allows for trading as well.  (its not a hodl stoploss)

First, thanks for you prompt answer

I can confirm your observations, I've tested with candles below 1 hour and the results are always loss. With 1 day candles it tends to get better, but i see that in a Bear market it will loose a lot, draining the profits made in the Bull market.

I'm using a time-frame for the past August (FROM: 2019-07-30 18:00 TO: 2019-08-31 23:59) with 1 day candles and 30 for warmup, which is the longest medium value ([VolumePeriodAverage]   Medium = 30  ).

using the default toml configuration:

[Swings]
Magica = 250
MediumOut = 250
ShortSight = 350
MaxPeekPred = 550

[ForcastTrend]
Short =  6 
Medium = 17
Long = 100   #nan

[PeriodAverage]
Short = 6 
Medium = 25   
Long = 100    #nan

[VolumePeriodAverage]   
Short  = 6    #nan
Medium = 30  
Long   = 100  #nan

Should I use a longer time frame? 2, 3 months?


I'm getting the following results in the attached image.

Also I have a question about this values:
Magica = 150
MediumOut = 150
ShortSight = 250
MaxPeekPred = 350

What do they stand for?

While writing an answer i noted a imperfection at the code idea, so at my github there is new code (also a new toml )
code is here : https://github.com/PGTBoos/GekkoStrategies

I recomend you to install visual studio Code (available on linux and windows), its a good code editor. (and not as heavy a visual studio)
I have added more comments in the code, and altered the rules slightly.

The first Magica is used in finding buy moments (its a alternative to the default)
The others are used in the going short math, to decide when to sell.
They are tweakable, and you can check them out.

One is easy to explain, is MaxPeekPred  it goes short when it predicts the price will drop "this amount" since the last high.
New is BullsEye kind of the oposite it goes short after a (huge) gain since coins where bought, i recomend to set it high like 1000 or so
The others are a bit bit more complex to explain, but becomme more clear when you read to code. (which is now better commented)

I tested with 2 and 7 month and 1 hour periods on Biance with a gekko simulation
Especially the SwingsVar might require tweening when the time scales are altered.
I wish to make it less dependant on time scales, but thats another open question here at the forum.

shown below it got 141% out of a 93% market, it might not be always like this but just showing it can be possitive