SuperNova Release Notes (in Reverse order)

Beta 14 was released a few posts ago and we should run with that this week. I am
currently working on:

1. Scale out in loss
2. The fnal position of the scale out in proft will be allowed to continue with a
trailing stop of it's own
. !andle 1"1# pip brokers

$ather than add functionality% I think we should focus on:
1. $obustness & are we getting any order errors' I want to eliminate all errors.
2. (orrectness. )re our **"$* methods working correctly' I am especially
interested in the +S)$ based methods. ,et's keep an eye on those.
. +roftability. )s we get more data points% let's start to analy-e which methods are
working best for us.
.. Time e/ects. Is market open on Sunday o0erly 0olatile' Should we ha0e a setting
to allow us to delay taking on new positions until *onday' Should we ha0e the
option to close all open positions 1if in proft% perhaps2 on 3riday'

!ere is beta 12. I tried to get the trial out loss done% but ran out of time. This
0ersion adds +yramiding to the ** choices. I tested e4tensi0ely with 56+7+8 !. and
91 since it is the most 0olatile pair and pyramiding and scaleout made 0ery
noticeble di/erences.

+yramiding adds to a winning position at certain proft points. These points are
defned by either the )T$ based TS or the +S)$ TS% so like scale out you must use
one of those TS's to use pyramiding. The inputs are:

e4tern bool :se+yramiding ; false<
e4tern double +yramid$isk+ercent ; 1.#<

If :se+yramiding is true +yramid$isk+ercent lots will be added to winning positions.

I am sending 2 sets of set fles to =rion. =ne set implements the ** features using
fairly conser0ati0e settings and the other set is more aggressi0e.

I ha0e noticed that it takes >>? a few seconds after the platform starts to update. I
would always turn o/ the big ?) switch before closing the platfor down% then turn it
on after the platform stabili-es to a0oid false entries.
@ell% here is Beta 10. It only has a portion of the ** I promised. I will fnish the rest
this week. I am almost done% but don't want to rush it out before it is tested.

I ha0e added scaling out of trades to this 0ersion. The inputs are:
e4tern bool :seScale=ut+roft ; false<
If true% the ?) will scale out of proftable trades by the Scale=ut+roft+ercent 0alue.
3or this 0ersion% you must ha0e either :se)tr6asedTrailingStop or Trail6y+S)$ set to
true. This is because I ha0e hooked the Scale=ut to those TrailingStop functions.
!owe0er% I may decide in the fnal release to decouple the Scaling from the Trailing
Stops as I can see where some traders might want that feature. Aeed to think on
that a bit.

e4tern bool :se+rogressi0eScale=ut+roft ; false<
If this is true the percentage is as based on the current open position. So% the frst
scale of a 1 lot initial position at B#C would be .B lots. The ne4t would be .2B and so
on. If the Dag is false then the scale is done on the original lots of the original
position. So the frst scale in the pre0ious e4ample would be .B lots and ne4t scale
would be .B lots and we would be out of the trade.

e4tern double Scale=ut+roft+ercent ; B#.#<
This is the percentage of the position to scale out of.

I did Euite a bit of testing using the )T$ Trailing stop set as .2B on 56+7+8 91 and it
pro0ed a useful test. I place no faith in backtesting% though% so we will determine in
the open market what is best.

,astly% I ha0e added:
e4tern bool :se,egacy*odeTs+S)$ ; false
for *att and the others that wanted the Trailing +S)$ to beha0e as it used to. If
false% the ?) does not apply the trailing stop until the trade is in proft. If false% it
works as it used to and trails solely on the +S)$.

)s always% please let me know if there are problems or suggestions. I am surprised
that no&one has asked for a confgurable )T$ T3 as I thought that would be a
popular reEuest from 6eta F

I am currently implementing scaleout in proft% scaleout in loss% and pyramiding.

Scaleout in proft will be done today% but the other 2 won't and I apologi-e for that.
7ust not enough time. I completely re&wrote the scaleout in proft from yesterday
and am much happier with the result. I ha0e implemented it in a way that will be
0ery robust e0en if the platform is re&started. It scales out by percentage either from
the original lots of the starting position or by progessi0ely applying the scale to the
current lots of the open position. It uses the =rder!istory to reco0er from platform
outages and other catastrophes. Gery safe.




Beta9

@ell% as I suspected I couln't Euite get pyramiding and scal in"out completed before
heading o/ to 9isney for a few days during school 0acation.

+lease refer back to post HB#BB for particulars% but the additional inputs are:

e4tern bool :se)T$6asedStop ; true<
e4tern double Stop,oss*ultiplier ; 2.#<
e4tern bool :se)T$6asedTake+roft ; false<
e4tern double Take+roft*ultiplier ; 2.#<
e4tern bool :se)tr6asedTrailingStop ; false<
e4tern double TrailingStop*ultiplier; 2.#<

The risk% T+% and TS all ha0e )T$ options% which allows us to defne settings that
should be more generic to all pairs since we will be using percentages of daily
0olatility o0er the last 1. days to dynamically tune our settings. 8ou might make a
good case that I should add the ability to use the chart T3 as an o0erride to the 91
)T$ and I would do that if the group wants.

The mutiplier is simply used to determine how much )T$ to base the settings on.
3or e4ample% a .2B TrailingStop*ultiplier uses 2BC of the 91 1. period )T$ to
determine trailing stop le0els.

This 0ersion all si-es lots based on risk and the Stop,oss*ultiplier. It is fully
normali-ed for all pairs by riskCand 0olatility. If your trade hits the stoploss% you will
lose no maore than the specifed risk C.

The default settings are not meaningful in any way. ?4periment with what seems
reasonable to your trading style.


6eta F. This Iust a summary. I will pro0ide more details on confguration when I
realease on Saturday. !ere is what I ha0e implemented:

)T$ 6ased $isk & $isk is now normali-ed by pair )T$. If you only want to risk 2C per
trade% the ?) will now set a stop and calculate lots based on a multiplier of the daily
)T$. This means that your trade allocates only the number of lots that if stopped
out eEuals 2C. Since it is )T$ based% it is self adIusting by pair and e0en by market
conditions. 6ig )T$ pairs like 56+7+8 open smaller positions than slow mo0ers like
?:$7+8 since the stops are narrower for less 0olatile pairs. So the risk and the proft
potential are both normali-ed.

)T$ 6ased Take+roft & (arol 1?ureka2 this is for you This is a self adIusting
Take+roft target based on )T$. It adIusts by pair and by market conditions. 56+7+8
will set larger targets% while ?:$56+ will set smaller targets. The )T$ multiplier
allows you to gi0e it a C of )T$ to target per trade.

)T$ based TrailingStop & This is the heart of the ** system. It is the basis for
pyramiding and scale in"out. It also uses )T$ to defne trailing stop. It works a bit
di/erently than the standard SA TS. The current TS and +S)$ TS 1both still work2
increment the stoploss after the TS is hit e0ery tick. This one mo0es the stop only
when the TS or a multiple of the TS is hit. 3or e4ample% if the user specifes an )T$
TS of B#C and the )T$ is 1## pips. The Stoploss will be set when the price is B# pips
abo0e the entry price J spread. 6ut the ne4t time it is hit is another B#C later at
1## pips abo0e the entry. These also make the scale in"out and pyramiding targets.

I am hoping to get the pyramiding and scale in"out in for Sunday% but it is a bit of
work yet. ,ost time to being sick. !ere is what I suggest:

I ha0e added Euite a bit of new fuctionality in betas K and F and I think it might be a
good idea to ha0e an informal play week to debug and get used to these features.
8ou may also want changes. )lso% I am away from home Sunday through Tuesday
during school 0action week. This would allow us to test and get used to the new
stu/ while I fnish the **. Then we go full blast in two Sundays.





!ere is beta K. (ould you please replace your beta L's with beta K and restart the
accounts. This has the +S)$ f4% but also the new magic number code that you will
need to make sure the ?) uniEuely identifes the symbol" T3 pair as the default
autogeneration of magic numbers does not support this.

*y fault for not letting =rion know about this release in time. I'll blame it on the Du

The frst day is really about debugging and getting to know reacti0ity which is a 2
edged sword. $eacti0ity gets us into and out of trades much more Euickly% but at
the e4pense of potential false signals caused by momentary crosses that penetrate
the signal lines% but don't fully commit. That is why I ha0e put in se0eral fltering
mechanisms. I ha0e one more mechanism 1 a channel deadband2% but if these
simpler methods pro0e suMcient% we will be fne. )lso% after we fnish with
debugging% we will add a few tests to compare the reacti0e with non&reacti0e. That
should be really insightful.

If I can get a good head of steam% we can start the **"$* ne4t week.

!ere is 6eta L. It doesn't ha0e all the features I had hoped and I apologi-e for that.
6eya K will ha0e the *oney and $isk *anagement. +romise

This 0ersion contains the reacti0e code and some mechanisms for fltering trades
that get bad flls caused by price spikes 1news2 and fast mo0ing markets that cause
price to stray wildly from the mo0ing a0erage causing a 0alid% but usually poor%
entry.

!ere are the new inputs:

e4tern bool :se$eacti0e?ntry>>? ; false<
@hen true% >>? will use the current bar for entry decisions.

e4tern bool :se$eacti0e?4it>>? ; false<
@hen true% >>? will use the current bar for e4it decisions.

e4tern bool :se$eacti0e?ntry ; false<

@hen true% all non&>>? indis will use the current bar for entry decisions.

e4tern bool :se$eacti0e?4it ; false<

@hen true% all non&>>? indiswill use the current bar for e4it decisions.

e4tern bool :se$eacti0e+ips3ilter ; false<
e4tern int $eacti0e+ips3ilter ; B<
These 2 are used together. @hen the boolean is true% the entry and e4it conditions
will ha0e to be true for $eacti0e+ips3ilter pips before the trade will occur. This is
meant to flter brief crosses of >>? and the other indis which could cause false
entries and e4its. This will need optimi-ation.

e4tern bool :seSlope3ilter ; false<
@hen this is true% the entry condition must agree with the slope of the internal ?*).
So if a long is triggered% it will only be placed if the ema slope is upward. @orks with
reacti0e and standard settings.

e4tern bool :se+rice3ilter ; false<
@hen this is true% the current price must be below the internal ema when entry
condition is met for a trade to occur. So if the ask is below the ema price for a long%
the trade is 0alid. This helps protect against taking trades after price spikes that
cause 0alid crosses and helps to eliminate bad flls. @orks with reacti0e and
standard settings.

e4tern bool Same6ar$e0erseTrade ; false<
This allows a trade in the opposite direction to occur on the same bar as a Iust
closed trade. So id a long closes and the conditions are 0alid for a short% the short
will be placed on the same bar. @orks with reacti0e and standard settings.

If all of the inputs are false% 6eta L works Iust like beta N.




The (heck(onfrmingTrend uses Iust >>? on the specifed T3 to determine trend. I
like to trade !. and 91 and use 91 to confrm for !..



These frst few hours are going really well. *any of the indicators did a good Iob of
fltering out a troublesome 56+:S9. *arket open is always risky as there is not
much 0olatility% so indicators do not beha0e as well as they do when 0olatility
increases. The same is true of the dead -one. I usually wait until the ,ondon open to
begin trading on *onday and our data may lead me to add a market open input so
that traders can specify a time to accept new trades after market open.

It is interesting to see that Gol took the opposite trade after the down spike. )lso
notice that >>? alone is not a great e4it indi 1so far2. It defnitely likes help . *y own
obser0ations are that >>? alternate T3 1*att's idea2 using the trade with long term
trend input impro0es >>? substantially. )lso% >>? is much better by itself for the !.
and 9aily T3's 1which I often trade2 while other indi's get better for shorter T3's.

)lso% note how ((I got us out of trouble really e/ecti0ely.

I am releasing beta 6 with the following changes:

1. ) Dag called !ideStop)ndTake+roft has been added with a default of false. If you
put a 0alue other than # into the Stoploss and"or Takeproft felds% it will include
these 0alues in the order. This means that in the case of a loss of connection% power
outage%etc your stops will be e4ecuted by your broker. If the Dag is true% then the ?)
manages the stops to hide them from your broker.

2. ) :ser(omment3ield has been added to the inputs. )nything you type in there
will be placed in the (omments feld of the order and will also display on the chart
that the ?) is attached to.

. +Sar has been added as both an entry and e4it criteria. ?ach has Step% *a4imum%
+recision% and 6ar 0alues. The bar 0alue is defaulted to 1 which means that the
e0aluation is done 1 bar back from the current bar. If this is set to #% the current bar
is used and entries are much Euicker.

The way the trailing psar works is that it does it's e0aluation of whether or not to
mo0e the stop based on the (andleTrailStop+S)$ input. If you specify 2% then on
e0ery new candle it will look at the +Sar high and low candles 2 candles back from
the current candle to determine if the stop should change. If the conditions do not
warrant a change% it will wait until the ne4t candle and look 2 candles back. Since
you may be long on a trade and the candle 2 back closed lower 1the psar high O
psar low2% it would not make sense to mo0e the stop. I hope this makes sense.


I am releasing 6eta . of the SuperAo0a ?) with the following additions:

1. ) new ,aguerre(ross condition has been added for entries and e4its per 5lenn's
reEuest. It does not replace the current ,a5uerre condition. 6oth are now a0ailable.
6oth share the same 5amma settings% though if users want separate setting% that is
possible. *y reasoning was that the settings appear to always be the same in
Imran's use of ,a5uerre and also that most users would choose to use these
conditions mutually e4clusi0ely. The idea is the when the entry ,aguerre crosses
o0er the e4it ,a5uerre% go long and 0ice 0ersa for short. In addition% I confrm a
signal if both 0alues are pegged at 1.# for long and #.# for short. There is another
way we could do this% but we will need to do some testing to determine the best
method. The other method would be to confrm on one ,a5uerre simply being
abo0e the other 1depending on intended trade direction2. This is less strict than the
actual cross% so is worth considering.

2. I ha0e added a (heck(onfrmingT3 boolean 0alue that when true uses the
(onfrmingTimeframe 0alue to determine if a signaled trade is in the direction of the
confrming trend. 3or e4ample% the user could reEuire that all .!$ trades be in the
direction of the 91 trend.

. Start and Stop time functionality has been modifed so that when the time falls
between the 2 0alues all ?) functionality is acti0e. @hen time falls outside the
0alues% all ?) functionality is acti0e e4cept for new orders. So all e4its and money
management continue to work% but no new trades will open. These times are broker
based% not local.

*att% I am still testing your non&standard time periods% but could not fnish it for this
release. Sorry about that.

+lease let me know if I ha0e broken anything or if any of the new code is not
working as you e4pect. )fter this 1and possibly *att's time periods2% I would like to
free-e the code for new features. ,et's refne what we ha0e and determine it's
strengths and weaknesses. )fter this analysis% we will turn toward impro0ing *oney
*anagement to impro0e proftability and reduce drawdown.