Advertisement IC Markets

Automating a journal for yen pairs: a checklist

Document your personal trading journey. Track daily equity curves, review winning and losing streaks, share trade screenshots, and get constructive feedback.
Post Reply
FXS London Scalper
Posts: 976
Joined: Sun Oct 18, 2026 12:25 pm

Automating a journal for yen pairs: a checklist

Post by FXS London Scalper »

Much of a trading journal can be automated. Export the MT5 history each evening and let a small script fill in what used to be typed by hand.

What a script can add per trade:
  • Session tag from the open time (Asia, London, New York).
  • Spread at entry, from your own spread log.
  • Distance from the Tokyo session high and low, a useful reference on USDJPY and EURJPY.
  • Hold time in seconds.
What's better written by hand: the reason for the trade in one sentence, and a rating of the entry from 1 to 3. Automating the reason with tags is tempting, but notes tend to get worse when you stop thinking about them.

One yen-specific field worth flagging manually: whether the trade came within an hour of a comment from a Japanese official. There's no clean free feed for that, and those comments explain a lot of odd yen behaviour.

A tip for the Tokyo range: define it in your script by clock time in Tokyo, not broker server time, and handle the fact that Japan doesn't change clocks while Europe and the US do.

Anyone automated more than this? Where did you draw the line?
FXS Official Team | London Session Desk
Recommended broker for automated trading & scalping IC Markets
Amanhasnoname
Posts: 2060
Joined: Fri Oct 30, 2026 9:45 am

Re: Automating a journal for yen pairs: a checklist

Post by Amanhasnoname »

I went fairly far with automation and then pulled back. My script reads the MT5 history export every evening and adds the session, the spread at entry from my own tick log, hold time, and the distance from the Tokyo range on USDJPY and EURJPY. That part has been well worth it, because those fields used to take me twenty minutes a night and were full of mistakes.

At one point I also tried to tag the setup automatically from price patterns, and within a month the notes had become useless. Everything was labelled correctly, but I had stopped thinking about why I took each trade. I went back to writing one sentence by hand, and reviewing them weekly became meaningful again.

The Tokyo point in the post caught me out too. My first script defined the range by server time, and it drifted by an hour every March and October when Europe changed clocks. Defining it by Tokyo time fixed that. I also keep a manual flag for Japanese officials' comments, since those explain most of the odd days.
Post Reply