In the Adjustment field in the block that you have the STD and the RSI, I noticed you typed "*rel"
Does that standardize the two indicators to one another and mean "relative"?
Like, if I were to stack a MA on the ATR, for example, under the MA in the adjustment box, would typing "*rel" make the MA relative to the ATR?
Neat idea. Thanks for sharing it, bud.
I'm looking through the shared project again, Roar, and I am curious:
Could you possibly explain the logic behind the streak being set to -1, why if condition five is false streak gets adjusted in block 6 by +1, and the V6+2 in the same block? I'm trying to understand the thought process behind this. I'm sure you have very good reasons for doing it this way, but I don't immediately understand why. Hahah.
Thanks again, bud. Sorry to load you down.
I'm also starting to look more into the array stuff, as you'd suggested.
I'm assuming, to work with arrays, it's going to all be custom code stuff? I've not seen any blocks titled with the word "array" in it.
It's not a problem or whatever. Hahaha. Was planning on learning the basics of coding EAs by hand at some point anyways, but like many of us, I kinda got FxDreema to NOT have to do a lot of coding.
@osmanxx said in Rsi crossover take many trades:
ake with macd and rsi. Example I use macd value and rsi v
Hey, Osmanxx. It sounds like you're new to FxDreema like many of us.
I'd recommend starting here and seeing if you can maybe get the workings going yourself.
If you get something built and it still doesn't work, then share the project here and maybe one of us will help.
Unfortunately we're all just like you. We're not being paid to build stuff for others or anything like that and we're simply just helping out of the goodness of our hearts. Hahaha.
Good luck on your journey.
ere i can decide at what price it
It sounds like you're really new and you're getting ahead of yourself a little bit. I'd really recommend thumbing through the FAQ example builds that FxDreema provides as a basic launching point (even if it means just building things you don't even intend to use, just for practice).
You need to create inputs for your Entry, SL, TP, and maybe a bool (T/F) for if you're placing longs or shorts.
You'd probably want to work with pending orders and not "buy now" since you're working with a specific price.
You can go to your "on init" tab an simply set up a "once per bar", into a "No trade/Pending order", into a condition block that checks if you have true or false selected (for placing buy/sell), then out one side, place a pending sell at specified price with specified TP/SL, and the pending buy on the other side.
Since you also have this added criteria that if the last trade was a loss, then to open a new trade, you can Once per bar (or leave it on tick if you must depending on your strategy, just going to be more resource demanding) into a "no trade/pending order", into a check profit of last closed trade, see if it was a loser. If it was, then it checks your true/false condition for buy sell, into a new pending buy/sell order, just like the last step, if that makes sense. If it was profitable on the last trade, if you don't connect anything there, then it will break the loop.
Is this because you're working on someone else's project and not your own? That's the only time I've seen that part disappear.
@boll3k They have some built in Martingale features in the "buy/sell now" blocks. I've not messed with them, but that might be enough for you, but as far as the formula, I was thinking something like this
So, on the left, you have whatever conditions you have to enter a long
Then it stores your "lots" input into a variable.
Then it places a buy now with the "lot" variable for the trade size.
Afterwards, however you choose to do it, you've got the for each trade
pips away from open price (put a negative here if you want to count pips against you)
then a formula where you multiply the previous lot size by a scaling factor you've predetermined. It stores this in a "New Lot" variable.
Then it has a new buy now with the "new lot" for the lot size.
If it successfully buys, then it stores the "new lot" value into the "lot" variable.
That way, the next time it loops, the lot value has increased.
I'm sure there's more effective and efficient ways to do it, but as a noob, this is how I'd approach it. I hope this is descriptive enough to give you a framework to start with, at least. There's usually more than one way to accomplish a task in this arena, I'm starting to learn.
@xyon126 said in Condition with weekly filter:
the time filter, in my case only weekly s
The idea still applies. You can filter for time before, if you prefer, but it's going to be checking for the time constantly, just like it's checking for the conditions constantly now, so I'm not sure if it matters all that much which one you put first or second.
You can use the "check age" if you like in place of the time time and day filters, if you prefer. You can use the check profit to check and see how much a trade is winning or losing.
I guess what I'm trying to understand is, what part in specific is giving you trouble? This appears to just be a series of really simple tasks, and at first, I thought your problem was that you were unsure how to connect them together. If there's a particular part that is giving you trouble, most of us are happy to help, but we're just like you--trying to build our own EAs and be successful traders. Hahaha. We're not paid by the company and we're not here to build EAs for people.
If you specify exactly which part is causing you problems, or you share a project file with the part that's giving you trouble, I'm sure we'd be happy to look at it.
But,
c) if it's being allowed to continue, you don't need to specify anything. It's already going to continue anyways, so you can ignore this part when you're building (I understand this information is probably just so we can help you)
a) and b) these are just two conditions (ignore the close trade part). You can check profit on a trade and see if it's losing money, that would confirm condition A as true. You can also check the profit of the same trade and see if it's above a certain amount (idk what this "max amount" is. Again, it's kind of vague).
Connect the false from A to the input for B then run the "true" from those to a time filter, check age filter, whatever method you wish to identify when the trade will be closed. Then tell it to close trades.
Maybe something like this.
First off, pips or points? 400 pips is a toonnnnnn of movement on a 30 minute chart with Forex.
There might be an easier way, but I'd use the formula block, subtract the pips off of it, store it in a variable, then add a condition block immediately after it that does "Candle Close <= Variable"
Then add a "Draw" command after it and specify what you want it to draw and where you want it to be drawn.
@roar said in Condition Sunflower indicator.:
s before the sunflower, you need to
@Ontrade that post Roar linked to was one where I'd posed a question and it was very very productive to my understanding in the area of loops and stuff. If it's something that's new to you, I second Roar's recommendation and suggest you go check out our conversation.
I'm not sure what conditions or anything you're checking for, but you'd have one condition it checks for (whatever that is) and if it's true, then you pass it through your time filter stuff and close trades or modify things or whatever you're going to do after that.
If condition 1 is false, then it checks if condition 2 is true. That way, if either of them are true, it moves on. If neither of them are true, nothing happens (or you can put something connected to the false of the second condition and that would only be true if both conditions are false.
Unfortunately I can't make anything of much use because it's still very vague and not clear what you're asking, but logically, you need something to this effect.
@cdwilder1
Oops. Forgot to tag you. Hahaha. @roar
Thanks again, man. You're an absolute legend!
It's all made very good sense and everything and I'm still getting a lot from this (especially seeing how you've modified it). I feel confident that I can handle the task myself now. It's been extremely helpful getting a glimpse into the thought process of someone with much more experience in this area and it's helped frame things out for me in a way that I can better use them.
Arrays...I haven't seen/heard of them in context of MT4, but from just now glancing at it, it seems like you might be right. And I know my question is kind of vague. My apologies. Not trying to be cryptic or anything like that. I have some ideas of how I want to use it, but I don't have just one specific way in mind, though I was mainly thinking of using an EA on range bars, isolating streaks could point towards a supply/demand zone, so being able to extract a price from that could be useful. (Especially with the idea of extracting the low or high from the candle BEFORE the streak started, if it's lower/higher, like you intuitively did yourself). I was also interested in storing multiple outputs because of the idea that price could bull streak, for example, multiple times in a row and each one could provide a potentially useful supply level if they've not been broken yet. This means it could/would be useful to store the outputs of, say, the last 10, for example. (or until they're broken by some other criteria in the EA).
I'm sure the loops will be a really helpful part of this, but it's sounding like arrays are also a new framework, as you described it, that I'm going to need to tackle now. Hahahahaha. The joys of learning!
@l-andorrà said in EA automatically drawing trendlines or channels:
d drawer and then importint
If you have an idea of how you want these trendlines drawn, there are tools out there (similar to FxDreema) that allow you to make custom indicators. I hope FxDreema adds that functionality one day. I don't have experience on this or anything, but I merely wanted you to know it's an option, if you weren't aware and couldn't find an indicator that does exactly what you want, but you feel confident in your ability to make one yourself.
But like L'andorra said, you can find/create an indicator that does the job, store it as a custom indicator in FxDreema, then use its values to power your EA.
@darryl-0 Roar is def the one to help, but I'm also completely new to loops, also, but Roar and I had a good little discussion about it on one of my questions already. You might try checking out our discussion and see if it clears things up for you. If it doesn't, maybe you could tag Roar and see if he can help you further.
https://fxdreema.com/forum/topic/10894/scan-historical-data-for-conditions-values
Hey, @XYON126
You need some "or" logic since you have two variables and if either is true, then it moves on. Your question is on the vague side, but the logic might be something like,
"Condition (whatever you're talking about) <= 0" (checks if whatever you're talking about is negative) True
Checks what day of the week it is with "weekday filter".
If you need a specific time also, then use a time filter afterwards.
Back up to your original condition. If it's true, it doesn't matter if the other one is true or false since this is "or" logic. But, if the first one is false, and the second one is true, then it's the same outcome.
So, if your first condition is false (output on the false side), then add a new condition that checks if whatever variable is below whatever value you have predefined (again, vague question, so I don't know what these are). If that's true, then connect it to your weekday filter and stuff, as described above. If it's false, then both of them must be false, so you don't need to do anything (unless you want it to do something special when both are false, also).
Hey, @yerlin
I had my first loop question just a couple days ago, also, and I've gotten some really good replies so far. I'm probably not the best to answer, but maybe my post will help you find some answers in the mean time?
https://fxdreema.com/forum/topic/10894/scan-historical-data-for-conditions-values/12
