TDesk Whispers

[rapple]

You are using two RSIs on D1 with different settings?

Correct. This was a setup that someone else posted (Sorry I cannot remember who)

Anyway it has a short and long term RSI signal based on D1

Cheers Richard

[tomele]

Sorry, no.

This would mean to tweak and dilute the clear TDesk structure which is based on unique descriptors of indi/timeframe. I won't do so for an unproven strategy anyone has posted whose name you can't even remember.

Feel free to change the RSI indi code to generate two different RSI signals if you think this gets you anywhere.

A strategy involving a short term and a long term RSI signal, both based on D1, however is confusing. Base them on different timeframes and things will probably make sense. And will meet the TDesk and FXTestify requirements.

That is all I can tell you at the moment.

Cheers
Thomas

[rapple]

Sorry, no.

This would mean to tweak and dilute the clear TDesk structure which is based on unique descriptors of indi/timeframe. I won't do so for an unproven strategy anyone has posted whose name you can't even remember.

Feel free to change the RSI indi code to generate two different RSI signals if you think this gets you anywhere.

A strategy involving a short term and a long term RSI signal, both based on D1, however is confusing. Base them on different timeframes and things will probably make sense. And will meet the TDesk and FXTestify requirements.

That is all I can tell you at the moment.

Cheers
Thomas

No problem Thomas

I am work with the current setup.....

Thanks again for all your excellent work

[Dragonian]

Hello Thomas,

Here's an interesting one.

As I have limited computing resources I run more than one set-up per platform/account which means that TDesk can see, and show, open trades that were not necessarily opened by Desky.

My FXT-SPB-3 test is showing 7 short GBPCAD trades, TDesk generates buy signals for GBPCAD and Desky opens long trades.

With veto exit signals enabled in TDesk exit signals are generated because TDesk sees the 7 short trades as being contra to the long signals just generated so sends an exit signal to Desky which promptly closes the open, in profit, long trades

Is there a way around this that I have missed? Or must I limit myself to using TDesk on it's own with no other set-ups running?

TDesk 1.png

[Dragonian]

Having said all that there is a new GBPCAD long position which has not yet been closed so it may be that my exit criteria were met briefly and I did not notice

I'll keep an eye on it and report back.

[tomele]

Hi Bill.

Some remarks:

Setting MagicNumber of TDesk and Desky to the same number different from your other tests should work. Or giving your other tests different magic numbers. Please test it

I will have to normalize the lot output to 2 digits. Didn't spot that yet.

I will have to FORCE the users in using the real indi names for EAX-PINs, not PIN1, PIN2 ... Otherwise nobody can tell from FXTestify data which indis were used.

Good work.
Thomas

[Dragonian]

Hi Bill.

Some remarks:

Setting MagicNumber of TDesk and Desky to the same number different from your other tests should work. Or giving your other tests different magic numbers. Please test it

I will have to normalize the lot output to 2 digits. Didn't spot that yet.

I will have to FORCE the users in using the real indi names for EAX-PINs, not PIN1, PIN2 ... Otherwise nobody can tell from FXTestify data which indis were used.

Good work.
Thomas

Hello Thomas,

Changing TDesk MagicNumber from -1 to 40(Desky's MN) removes all the signals received by TDesk; it only shows the trades opened by Desky with that MN but no signals, even with all charts still open.

Some of the PIN names are very long which is why I chose to just name them PIN 1 etc. You'll have to tell us how you want us to abbreviate whichever PIN we are using so that we are all on the same page.

Talking of PINs, Jagz's very useful JagzFX-EAX-MUX-v1-03 uses PIN inputs from 10 to 19. If you try to use it with TDesk 6.02 you get a continual error message from TDesk saying that only PINs 1-8 are allowed which means that, as it stands, we can't use MUX with 6.02.

Talking of messages, and this is more for Steve, when activating some of the new alerts in Desky 3e they appear to sound an alarm continuously while the relevant parameter is met rather than a one off alarm each time a parameter is met.

[tomele]

Hi @all.

TDesk 1.03 is in post 1. The changes are marked blue in post 2. I am running out of colors.

* MagicNumber is replaced by TradesMagicNumber and SignalsMagicNumber
* PINs outside 1..8 get ignored without warning.
* Naming EAX-PINs "PIN" results in a warning.
* Some explanations regarding PIN names got added.


Have fun. I do.

Cheers
Thomas

[Dragonian]

Thank you Thomas, that's much more user friendly, good stuff :hi:

[tomele]

One more thing.

Do you guys think an option to close all trades before (selectable impact) news would make sense?

Cheers
Thomas