Search results

So I went back to the original code which din't have the unnecessary settings I asked the dev to add later. And settled on this change to handle open orders/positions that may be left after target is hit: I still need to figure out how to handle situation if an order is placed out of sequence...

Sounds like a sales pitch already. You just forgot the 2nd part "If it is good enough, join us as we open the doors of financial freedom to you and your family! For only $4999, you can have access to this amazing strategy that will make money in up or down markets! WHat are you waiting for call...

Another legit b/e

Yes, I think this is what I want as a fail safe. Release! :D

This edit works, and it ended flat..

SHit, nevermind

per chatgpt The provided code is written in C# and appears to be part of a trading or financial application. Let's break down what each part of the code does: void OnFlatten() This is a method that appears to be called when you want to "flatten" your trading positions, which means closing...

Ok. So here's the current code: When target is completed and position is flat, message is sent out to indicate the pnl. So at that point, I want to add a check: I want to add this section into the code. Basically the intent is once target is met, I want to retrieve any orders that may be...

RIght, nobody remembers WW2 anymore. Do you even remember your mother's birthday?

Yea the dev is probably not very detailed in his approach. You would probably laugh if i told you waht I paid to ge the algo done. BUt I did get about 20x out of the initial code investment.

You like the wretched, ghetto hood rat types huh?

Yes, numbers don't lie. But then people get delusional over few months of gains. Recency bias to cover up years of losses lol.

I reviewed yesterday's event log and found the issue. Yesterday, the OCO process didn't work, I had a sell order that didnt' cancel when a buy order is triggered. SO the reverse+the sell stop got executed. The limit target on the buy stop was also not cancelled so that was weird too. How the...

Removing another outlier. WOul'dve been a flat day yesterday.

No I can't replicate live execution back in market replay. Market replay is basically demo environment and do not reflect real market execution/latency.

That's what I'm tryin to figure out. Last change I did is to make sure everything's flat when i get the TP target hit. BUt today, target never was hit, so that code never got executed. I had a reverse order that was supposed to be cancelled (OCO) but did not cancel. Also I'm realizing that...

I dont' need a perfect algo, I just need a safety switch to trigger when the algo does mess up. That switch is to go flat! I have play around with conditional check a bit more.

Don't jinx me man. Right now I have a strategy with a broken algo. Imagine having a decent strategy but too clueless to make it work automatically :banghead::banghead::banghead:

I feel like the stop and reverse process is overcompicating things. If I had just treat each order with its own s/l, then place a new stop order for re-entry (reverse). This would treat each order as individuals rather than this mesh of stop and reverses and partials that can can confusing..

I have to undo the recent changes I added, cause this definitely is not what it's supposed to do! You can invest for growth or you can invest for yield. I'm a yield's guy...it's in my nature.