The Anamolies of Captain EA

This is through observation which may be true or otherwise.

The other day I was trying to find out if by making a mirror mt4 platform in another computer, can CEA close the trades made by the mirrored account after it was closed. What I did was to set up the account running on the netbook and after a few trades had open "close" the trading. Open the mirror trading platform with the same account and install CapEA to work on. What happened, soon as CapEA was activated it closed all the opened trades made by the mirrored trading platform. Not only that I even saw consecutive trades been open and closed fast. Its like CEA was deranged or something.

Then in the night saw that like CapEA  was dead. No trades were open for a while. But this morning saw that it had ben opening and closing trades rapidly.

On checking the CapEA version they were both the same as ver 1.0. The same one that i got from the seller. So I look deeper into the problem.

Could it be that when a trading platform is not running on the computer but having robots still attaching to the chart even thou EA disabled (at least the case with CapEA) they are still active ?

So what i did next was to go back to the mirrored trading platform and remove CapEA entirely and now waiting to see what is happening after that. 

Good thing I am seeing, the CapEA is not erratic anymore and acting sensibly like old times. Maybe that was the problem and the solution was right on target.

Now this raise the question:-
maybe it is OK to operate the same account in another computer to "take over" the other one. This may come in handy say when one of the computer is down or having heaty problem and other problems. It could work if I remove CapEA from the chart, disable EA and shut off the trading platform. Maybe this can actually work.

So will try that again in the future. 

The bitterness of the day after tommorow

 So the problem was over since last night when at about 9.30pm the UJ had lowered down far enough to give only about RPL -600 that was much better than -3k a few hours earlier. But with the consistent closings of trades from Monday morning, the total amount that was closed was about -12k for 2 days ! That was about this month's achievement.

So this is trading. Like it was a lesson or principle to behold is never to let emotion overcontrolled you. Add another one, trust your robots if you have already began to know and trust em. Like it is for me with Capt Ea and possibly Bender too. 

So at this very moment the price of UJ had gone to the low level when we started to panic and started to intervene  its authority and questions its decision. If no trades were closed then we could have a sizeable profit for the month instead of losing the month's profit !

But as it is with the human mind when it comes to indecision, the price may have gone up and up and the losing amount maybe as huge as it could be. but did not happened and the decision we intervene was a big mistake. But that is trading.

CALL TO ACTION
Since we are running CapReal with the other CEas and Benders in the local desktop, the only thing to make sure is that it should be running all the time. Internet down which is very rare (hope so) cant be controlled. Electricity down happens when it rains but can be rectified easily or avoided with the Power back up. The only thing is to have consistent checking like email every 4 hrs that the robot is running fine.

Losing grips and trust with CapEA

Trouble began when the 2nd day it recorded a lost of about -600. Before that it was merely -15, but still a loss.

What made me to believe was that the other demo accounts which are running local are making profits like usual. There are trades opening and closing unlike CapEA on VPS which were not closing orders or opening new ones.

Then the feeling that something is not right with the VPN which coincidently could not be log in as I did not do that for quite something. Why not as it was churning daily profits after daily profits.

Then the best crisis management decision is to contact the seller from Shopee. It was made worse as the seller said that it could not log in too. So the worst fear that the VPS was confirmed down.

Now the best decision to make at that time was to open the account locally with the other demos and mirrored on the CapEA VPN only on USDJPY which was going up and up and not tobe going down.

Then it was realised that the VPN was not able to log in because I had changed the password before and when logged in I saw that CapEA was inplaced and the next thing that came to mind that the robot itself maybe at fault. So decided to let it run USDJPY by itself while try to tackle the problem locally. The other pairs since no trades were opened were put on hold.

So the agenda was to control the trades manually, meaning that make it break even and not to loose too much. Also thinking that the price will go up and up. So if that behaviour was seen, the lowest trade will be closed. I was also thinking that the local CapEA can only control its opened trades not the one in VPN. Which in the end still not sure.

Now problem starts as CapEA was not actually dead  and starts opening trades along with the local ones. Where 2 trades were seen.

CONCLUSION
CapEA was working fine. It has the capability to make the best rapid judgement. But in this case its capability was doubtful and human intervention made it worst. If it was allowed to act on its own most probably it would minimise the loss as best as it could. 
Maybe the VPN was in fact have some technical issues making CapEA to open so many trades and not closing much.
The best now is to run it locally. If it behaved like the other local CapEAs they faced no issues at this time.
 

 

Captain EA in crisis

It is confirmed that the VPS  is not working. CEA remains dead with 0 running trades open or close today. The VPS seller has not gotten back to me. So we would take the worst case scenario here.

1. A local mt4 platform was opened on the local desktop.
2. Captain EA was attached to the 2 [airs which are now dangling around -$7k running PL. Even when the parameter for the number of new trades set to 0, we saw 1 trade opened for EU on the opposite side, The display did show all the trades running. So it is hoped that CapEA subs has got the power to close the running PL at the appropiate time.
3. The other 2 pairs would remain idle and no action taken unless the running 2 ones have recovered.

This is the test of time and hopefully we will get through this. It is not the robots fault rather than technical problem with the VPS. Thus proving that having a VPS is not a sure way of giving the best to robot trading.

 

Capt EA Binifit in problem technically

 Lately we have seen some irregularities in the account where last week it made the first declared loss for a day at 15.00. This is miniscule of course and thought that it is just those times where even CapEA has to submit. But then yesterday it made a bigger declared loss of the day at around 623. Now we are worried what the problem is.

Now on trying to check on the VPS located in Singapore, the remote desktop command could not access it and it informed on an internal error. I have communicated with the seller from shopee but it has yet to respond.

So I opened the local Mt4 trader of the account and can see that there are a number of trades running only on 2 pairs and the number of trades did not change meaning that the VPS may be probably dead ? Where we now have ronins trades which cant close let alone open new trades. 

I could close all the trades from here but then if i am willing to sacrifice the current Runing Loss of over 4,900. This decision cant be made unless it is confirmed that the Vps server is dead and the CapEA has loss control of the trades. So i am waiting for the respond from the seller which i rent the VPS from the 30jun20 for 1 year cost of RM60. Now the problem is the seller has change its shop ID and the package which is currently out of stock is now RM90/year not RM60.

Lets say the seller is notw hostile and unresponsive. I could change the password from the brokers board. And then install Cap EA on the local end. i dont know if it can take control of the trades as it may not identify them as they are with different IDs. Of course it will create new ones and control the new ones.

But what can be done with the current running ones is closing those in profits and leave the losing ones from the new robot to take control (if it could) if not then close them manually as there not many. Do not disturb the new ones thou. We can do this by sorting them by dates opened.

In the meantime, run the trades on our good old desktop along with the others. In the new future the machine would be upgraded to a bigger RAM and faster speed one. Its ok to control locally as it seem even with the current CPU it would be able to control thou there are a number of CapEA demos and Bender EA running. The problem of frequent current supply tripping is mostly solved and the availability of the back up battery also helps. As for internet down which can happen but seldom, we'll think about that later.

Making Cap EA more productive but increasing the risk

 No doubt the CapEA which is running freely in the Singapore VPS ( now facing problem, a bit on that later) is doing fine churning little profits on a daily basis. However its achievement is nothing to shout about rather than being an under achiever. if its getting a 0.07% profit on a daily basis yet its highest running profit is about 9,000k out of 178,000k funding or 5% and it happen once in a blue moon, thats not much a risk taker at all. So we are back to our demo lab figuring whats the optimum risk that CaptEA should take.

BTW, fantastic result is seeing at the All CPs at 300k demo Capt EA runs, doubling its 300k to 600k in a matter of about 2 weeks trading ! But this is with some manual intervention where once in a while we look at the trades being opened at any particular time. If there are too many trades running (parameter would be set) but RPL is in profit (to set parameter on how much) then we invoke the close all trades with the Close All Scripts. Trades will be closed fast the running winners and the losers too. But in the end the sizeable profit is ascertained and all tradings back to Square 1. This has worked a number of times. Of course Capt EA would eventually decide on the best course of action trying to break even, but our action maybe the better one.

This course of action is not necessary if we are very confident or familiar with CapEA money management. We dont dare to play with the lots parameter as it creates a lot of variables. So we decide on what is the right size of funding with the intention that CapEA RPL would not hit Margin Call as the funding amount is sufficient.

This should not be taken lightly. as we have faced MC even with a real account and demo accounts a few times just as our funding is not large enough. At that time it was something like 20k, 4cps and 0.01 start lot.

Now back to the experimentation on Profit and Risk. So lets decide on what is the ideal fund for the trade. We anticipated the RPL to be as high as 12k.

Quite simple calculation where we multiply 12k to the reasonable amount.
There are 3 module running where fund is 3x,4x and 5x of anticipated RPL.
So the experiment has begun with demo accounts of 36k, 48k and 60k. If everything is right then there should be any problem. But lets just see how this things go before making any conclusion. 

The experimentation began yesterday.