LukeB

Well, sure, I'd like whatever benefits are available....   who knows, maybe I'll become active again.  I recall enjoying this forum when I was participating.

There are still many better systems here !

I'm always interested in what people think is the 'best' system. I think psaini1973 posted enough trades to show that with a little skill, this signal can be traded profitably.

What system do you think works the best?

here is a new link to Signal Amalgamate: http://www.4shared.com/file/3fWlSVxP/Signal_Amalgamate.html?

I wish someone would look through the code and tell me if the box drawing has a bug, or if I've found a MT4 display bug that messes up the boxes regularly.

Haven't bought it, but these would be a fun read:

1. The ETF Set to Skyrocket in Price as the Devaluation of the U.S. Dollar Continues

2. Single Best Leveraged Play for the Gold Bull Market

3. Making Money from the Sovereign Debt Crisis: How to Achieve Massive Profit from the Collapse of the Euro

4. Inflation Hedge: Serious Profits from the New Multi-Year Trend of Higher Interest Rates

5. Lombardi’s Secret Stock That Goes up When the Stock Market Goes Down

hxxp://ttt.pr0fitc0nfidential.c0m/video/ca/index.php?sb=YAHOO1&sdate=02132012

hxxps://ttt.l0mbardipublishing.c0m/SecurePubs/NewF0rmular/newformular_pc2.asp?pub=CA&sb=PC-CA-YAHOO1V-02132012

HOLLOW arrows - An alarm requested by Lololo - basically, there is an array that contains a master level for each timeframe that if exceeded for each will draw the arrow, and the last column contains a value that if the current TF master level drops below, it will reset. You can put whatever value you want in the array, it doesn't affect anything else (TFAlarmLevels[9][10], 9 = one row for each timeframe, 10 = 1 column for each timeframe + the reset value). You will also see that result in the Alarm row of the grid.

Sorry for an update on the download link. I realized the daily pivots were not changing at 8:00 AM - I went in and changed MinsToCity to (MinsToCity*60) in several spots to fix it. Converts minutes to seconds for addition to the time. I was so happy to see the pivots working I didn't notice that detail.

Complicated - much more complicated than I thought I would make when I started. You better have a decent PC or it will make your CPU grunt.

kokopelli - change the time offset MinsToCity. You can change the City as well. I haven't found any way to tell the servers time offset being sent to MetaTrader, so the only way I know to get a time is to put the offset in manually. Daily pivots will work off of 8:00 AM on the City Time (and they treat Fri, Sat, Sun and Mon until 8:00 AM as all one day).

There are a bunch of extern's you can set.

// Pivot Controls

(www.earnforex.com/pivot-points-calculator)";

extern int PivotCalcMethod = FLOOR; // "0-off; 1-FLOOR; 2-WOODIE; 3-CAMARILLA; 4-DEMARK

extern int PivotCycleType = NATURAL; // "1 = NATURAL, 2 = DAILY";

extern bool SaveScreenPivotChange = true; // this overrides the above, as it will read in the values saved from the screen.

extern bool BoxClean = true; // wipes out the old up and down boxes when the pivots change (pivot change deletes old pivot lines, and I included ability to delete old boxes as well with this).

// User Alerts

extern bool ArrowDrawOn = true; // Display up and down Arrows

extern bool BoxDrawOn = true; // Display up and down boxes

extern bool AlertWindowOn = false; // Pop Up the Alert when an arrow is drawn

extern bool AlertSoundOn = true; // Play a tone whe the arrow is drawn.

extern bool AlertSMSOn = false; // Send an SMS message when an Arrow is created.

// Time Display Info

extern int MinsToCity = -360; // Minutes between the server's time and NYC time.

extern string CityName = "NYC"; // change this to reference the City you are setting the time for.

// Other Lines to Display

extern bool ChartSmoothedProbability = false; // Display a MA of Master probability.

extern bool ShowSuperTrend= false; // Display Super Trend Indicator.

extern bool StrenthLineOn = false; // Display the TOR indicator

// - Stuff

extern bool UseTFLimits = false; // Limit All Timeframe Probability Calcluation to Master Probability timeframes.

extern bool DispSignalGrid = true; // Display the Signal Grid.

extern bool DispTFLimits = false; // Display the Signal Grid with TF limits versus all time frames.

I completed the Pivot Displays (you can change the pivots by moving the stars and placing them in the boxes) and added a graphical display of the MTF probabilities (per Fortuna).

http://www.4shared.com/file/GvZdwU8u/Signal_Amalgamate.html

Link did not work.....Could you upload it again? Thanks

Seems like everything muti or mega upload related has been killed. 4shared seems to still be alive, try this for signal amalgamate: http://www.4shared.com/file/GvZdwU8u/Signal_Amalgamate.html

and from post #1239, this for pip accumulator: 4shared.com/rar/1qKwgstr/Pip_Accumulator.html

Put in some updates, http://www.multiupload.com/20X3611MU0. Haven't had much chance to test, so keep your old one if you are using it.

The indicator will draw up and down arrows with different colors, based on if the signal crossing qualifies with the long term MA.

- extern color UpQualColor = Green;

- extern color DnQualColor = Red;

- extern color UpUnQualColor = MediumSeaGreen;

- extern color DnUnQualColor = Coral;

I also built in the TOR trend indicator I found at http://codebase.mql4.com/7703. The long term MA is color coded for the current chart time frame trend as follows:

- Green // Starting Trend

- Blue // Trend Continuing

- Turquoise // Trend Fading

- Salmon // No Trend - Ranging

" in what post # is your last version of Signal Amalgamator" - http://www.multiupload.com/IFL8HUQB8E.

I updated all of my posts with the muti-upload reference to point to the latest version of Signal Amalgamate....

"you guys update newer versions with instructions on the first post" - Sorry, the first post is not editable by 'me' guys, as it was not made by me.

The rules for trading would be identical with the two indicators - Psaini1973's posts detail them. Some of the features of Signal Amalgmate suggest additional things that may be looked at by the trader, including the PA moving away from the Pivot Line in the direction indicated by the signal, consideration of Pivot support and resistance, and the crossing of the Master Probability lines and the All Time Frame lines (or the smoothed line) after a period of divergence.

The 'version' is Signal Amalgamator - and it's a very different set of code, built to show and signal with the Master Probability calculation. Then, some comments were made and I added some features - and still intend to add the Daily Pivot feature as soon as I find some free time.

II Pip Accumulator's boxes and arrows are a MACD signal - the historical signals are 100% MACD. There is no historical look at anything related to Master Probability. Also, the code was rapidly made, the original contributor left (it was not being updated), and it has several inefficiencies (it does the same piece of work multiple times).

I wanted to see the historical Master Probability Signal. As it is a multi-timeframe calculation, it is impossible to get the exact value in history, but if you look at the real time calculation over a couple weeks, you will conclude that its historical version is pretty close. There is no MACD Signal in Signal Amalgamate (except as MACD is one of the signals 'amalgamated' into the Master Probability calculation). The indicator code is broke up into discrete functions, so it is more readable code, and the indicator itself has some code errors fixed as compared to II Pips Accumulator. Bottom line -the Master Probability calculation is very nearly the same, but Signal Amalgamate is not the same indicator as II_PipsAcumulator.

Based on the confusion putting Signal Amalgamate here seems to have created, I'm thinking I should quit providing updates to it here.

This indicator is worthless

You have one to share that isn't?

http://www.multiupload.com/71LJHFA51N

updated

Plots the Long EMA and with

extern bool RulesOnlyDraw = true;

only puts arrows on qualifying signal crossings.

http://www.multiupload.com/71LJHFA51N

SignalMethod - set to 0 to calculate on the current bar (bar zero). I think the signal could flicker, but haven't seen it - seems pretty stable.

Arrow Colors and Arrow size are both external, set them as you like.

yes,please add arrow alerts.thanks in advance...

http://www.multiupload.com/71LJHFA51N

looks like too many loosing signals in with the winning. Have to be more rules than just the line crossings.

Crossing moving averages as a tradeing strategy are way old and unsuccessful, and that's all there is here.

Fortuna, Do you see that text, (when true)? I only see it as mouse-over information (not visible if I don't select the box or line and hold my mouse over it). I'm sure I wouldn't want that cluttering up my screen if it was there all the time.

Now that you've looked at the Pivots - I know Psaini asked about a good pivot indicator at one point - What do you think of the 'natural Master Probability cycle' for pivots versus having a daily pivot? With the code all there, it would be pretty easy to change it to work either way. Just have to trigger the cycle on the day/time change instead of the box change, and make an initialization routine for loading data to start it up if the Chart Time Frame is greater than 30 minutes, so you wouldn't have to wait a day to get a good daily pivot.

Not sure how many people like to have support and resistance lines. I think they help keep me from chasing trades that are about over, so want to have them. Not sure how good the 'Master Probability Cycle' idea is for making them.

Signal Amalgamate updated, v1.08.

http://www.multiupload.com/IFL8HUQB8E

I've done what I set out to do with Signal Amalgamate - It now has pivots. The pivots are natural to this indicator - we have a 360 degree rotation of the signal every two boxes, and the pivots are calculated for that cycle.

This is my source for Pivot formulas - and the 4 pivot styles are each implemented:

www.earnforex.com/pivot-points-calculator

extern int PivotCalcMethod // "0-off; 1-FLOOR; 2-WOODIE; 3-CAMARILLA; 4-DEMARK

There are about 100 people downloading these updates - so I know at least that many look at this forum. Please participate, give back if you benefit from this community or the code. I know just from searching for Pivot code, and ending up just writing it - there are a some code samples here that could be beneficially picked up by people doing other work. If you use what I've contributed - please post a msg to me.

Fortuna, I found why the indicators changed:

When making grid rows match original, I swapped RSI and and SAR without swapping their percents.

This:

double SignalPercents[] = {25, 25, 10, 10, 10, 10, 10};

Change to:

double SignalPercents[] = {25, 10, 25, 10, 10, 10, 10};

and you get the same signal.

I can look, maybe in the array references that were supposed to make the grid display easy - I made one significant change to the Master Probability calculation that I am aware of, but this appears to be in the code you posted - a condition that cannot be right from the original II_PIP Accumulator was copied into mine. This problem made the indicator values visibly wrong at certain times in the chart history.

Here are the original lines (they reference the zero candle of the chart timeframe for all timeframes and candles):

if (SAR[j] < Open[0]) Signal_SAR[j] = 1;

if (SAR[j] > Open[0]) Signal_SAR[j] = -1;

.

if (Low[sMA1_shift] > SMA1[j]) Signal_SMA1[j] = 1;

if (High[sMA1_shift] < SMA1[j]) Signal_SMA1[j] = -1;

They are replaced with:

double candleOpen = iOpen(CHARTSYMBOL,IDXperiod,candleToProcess);

double candleLow = iLow(CHARTSYMBOL,IDXperiod,candleToProcess);

double candleHigh = iHigh(CHARTSYMBOL,IDXperiod,candleToProcess);

if (SAR[j] < candleOpen) SignalGrid[j][sIGSAR] = 1;

if (SAR[j] > candleOpen) SignalGrid[j][sIGSAR] = -1;

.

if (candleLow > SMA1[j]) SignalGrid[j][sIGSMA1] = 1;

if (candleHigh < SMA1[j]) SignalGrid[j][sIGSMA1] = -1;

I also made the All Time Frame calculation configurable to use only the TimeFrames valid for the chart Master Probability or all time frames (UseTFLimits = false). Other than that, the code for the probabilities should have remained the same.

As it will probably be a week before I get to work on this again - here are my latest changes:

http://www.multiupload.com/IFL8HUQB8E

Includes:

- will draw a Moving Average of the Master probability - Set ChartSmoothedProbability true.

- Displays the signal grid - DispSignalGrid true

- Display the signal grid with only the time frames valid for the charts Master Probability: DisTFLimits true

- Displays a One Bar Direction change to the current probability values in the signal grid.

- Includes lololo's alarm: MitiTFAlarmOn true.

lololos alarm uses this array for the values to trigger on - put in the trigger values and it should alarm when all are exceed (a positive value should work for both positive and negative)

// M1, M5, M15, M30, H1, H4, D1, W1, MN1

double TFAlarmLevels[] = {0, 10, 20, 0, 0, 10, 0, 0, 0 };

- so, put your values in there and see if it works. Post back what needs to change there, and what values make sense.

Still haven't thought enough about TrueTrader's ideas to decide if that is quick, takes awhile, or is hard. Just the basic Master Prob values exceeded or do not exceed a value is available by looking at the displayed numbers, and the current direction is in the 1BarDir signals.

lololo and TrueTrader - are you asking for the same thing? The download from TrueTrader looks like a one bar direction indicator (trivial to implement as part of the signal grid), but doesn't seem to match the text.

lololo - does this represent what you want (absolute values, both positive and negative):

if ( (H4Prob > H4triggerLevel) && (M15prob>M15trigerLevel) && (M5prob>M5triggerLevel) )

{

draw an arrow on the bar

}

Also, would you want it intra-bar on Bar 0, or the final result (when Bar 0 becomes Bar 1)? And, would you want to keep signalling, or signal once and wait for a resetting event before signalling again (and what would that event be)?

One thing you will see with the arrows and box drawing as triggered in Signal Amalgamate, the direction switches real time / intra-bar, so as it runs, you will see times when the signal reverses as a result of intra-bar quotes, but by the end of the bar, the graph doesn't show the trigger levels being met but an arrow is displayed and a new box of the new direction is being drawn. Changing it to only trigger when a new bar occurs would mean the signal is slower, but historically and visually, it would be more consistent. So far, I prefer a faster signal.

I saw in fx4_ever's response that he also likes the signal grid - I just added it to my work env., and will post in a few days. While doing so, I found a code discrepancy in the original indicator (copied into my version):

int M1TFWeights[8] = {55, 25, 13, 7, 0, 0, 0, 0, 0}; //M1

And the rest of the weights should be [9], or with no number in the bracket at all, just "[]". The compiler must 'fix' the discrepancy or it seems like someone would have seen something wrong by now. Just to be safe, I'd change it.

lololo and TrueTrader - as this is all free and spare time work (and even though I view the signal grid as decorative), I'd like to concentrate on code with demonstrable value, and it can take some time to find free hrs to contribute. If you produce working code and submit it, code review and clean up can be faster than invention. Anyway, I'd like to see a description of the trading rules these features would facilitate and get some sense as to if those rules really create additional profit before working on the features. I'd thought a built in Pivot indicator that would use a flexible work day definition associated with the time display on the indicator would be a valuable feature, but am already frustrated with the time that is taking to get working correctly.

Signal Amalgamate does not use MACD to create any alerts or draw any boxes - except as MACD is part of the Master probability calculation. The results of the Master probability calculation and crossing of the 20 levels draw the boxes, arrows, and trigger the alerts.

Code review for box and signal drawing on II_PipAcumulator:

The main start function has ReadIndicators() and CalcMasterProbability() - These are only executed for the zero candle, and they calculate the Master Probability. The Master Probability value is never placed into an indicator buffer in II_PipAccumulator.

The Start function then has the for loop that is executed with every tick LookBackPeriod times - "extern int LookBackPeriod = 1000;" until it reaches the value of CandleNo - CandleNo is never explicitly initialized, but is always zero - so 1000 executions of CalculateSignals with every tick to redraw the indicator for the last 1000 candles.

CalculateSignals uses three iMACD values (BoxMACD_Main, BoxMACD_Prev, and BoxMACDSignal) to perform all drawing until it reaches candle 1. Most of us are using the defaults, so only "extern bool ArrowMACDx=true;" and "extern bool AlertMACDx = true;" and the box drawing and alerts are controlled by these two if statements for 999 candles of history:

if (ArrowMACDx && BoxMACD_Main > BoxMACD_Signal) and

if (ArrowMACDx && BoxMACD_Main < BoxMACD_Signal)

Until Candle 1 is reached.

Once candle 1 is reached, the conditions are satisfied to start using the two if statements for using MasterProbability with the 20 level crossings to draw and create alerts:

1) if (MasterProb > ProbLevelLong && i == 1) // The MasterProb is calculated for the current Tic (in candle 0) and is triggered for candle 1.

2) if (MasterProb < ProbLevelShort && i == 1)

But, those arrow and box flag values will be lost once that candle becomes candle 2 and the next tick re-does all the box calculations again as MACD signals - I think that may have triggered the 'redraw' comments found in the thread.

Hope that clarifies.

This is the same indi that started this thread, just re-written, cleaned up, and made to work as described above. Follow the rules as described in the thread. Psaini1973 is the grand master, posting all the big bucks. Fortuna says hes not a programmer, but has been in the code a little.

I have a long list of posts with rules for trading, but without looking them up, I have marked as the main posts #577, 874, 929, 935. The indicator as posted by me is simplified to only what I see Psaini using (other than some alerts). I see the Indicator Signal Grid displayed on some posts, which could be added, but I don't think it adds to the 'rules' and would just be additional stuff on the main chart. Most recent indicators from SoundFX are Post 701 I believe.

The first version was created by SoundFX. It's somewhat of a hack, or rip, of something else that I'm not familiar with, but it works and people on this thread have been using it. SoundFX carried the technical side of this for awhile, but seems to have left for lack of technical participation by others. Anyway, it would be nice if others did some analysis of the code and how this works and posted back ideas and improvements.

An improvement idea - if you shut down your trading terminal and restart it, the indicator box redraw on Window Zero can be horrible until you switch back and forth between two timeframes. I don't know how to stop this, you can see two commented out experiments to correct this left in the code. I think it's a bug in the MT4 platform this has exposed - anyone who knows, please join in.

Happy New Year - and have an updated II_PipAccumulator Indicator

http://www.multiupload.com/IFL8HUQB8E

1) It displays Master Probability and All Time Frame Probability in a Separate Window, with historical calculations.

Original only calculates Master Probability during the time it is running on bar 0 - no historical calculations.

2) It displays boxes and arrows on the main chart window (window 0), all calculated with the Master probability calculation. It will also put up an alert window, make a sound, and send an SMS. All under user control.

Original creates historical boxes and arrows using MACD signals. It has no historical Master Probability calculation. I left the 'no time actually passed' space between box ends and starts empty as I liked the effect. As noted elsewhere - Historical cannot be exactly like runtime as you cannot get the signal values for the larger time frames at the time a shorter timeframe bar ended.

3) It displays the timeframe probabilities, per fortuna, and the iATR.

4) It displays the NYC time if you set "extern int ServerToNYC = -300;" correctly. The server I'm using runs GMT, so -300 is 5 hrs. I chose minutes in case some of you need finer adjustment than hr.

- change the NYC string to one of your liking and go here to get your time straight - http://www.timeanddate.com/worldclock/

5) The code does a fair job of following a readable code standard, so you can read through it and know what's going on. Also, this leads to people being able to make and post improvements. I believe the code is considerably faster than the original indicator.