Economic calendar via MQL5 functions - may I save a private local copy for personal research?

New comment


Hello,

I read the MQL5 economic calendar in MT5 with the calendar functions (CalendarValueHistory and related) for my own personal research. Before saving anything further I would like to check what the terms allow.

1. May I save a private, local copy of the values I read (event time, importance, actual, forecast, previous) for personal research only, without sharing, publishing or reselling it? I have read sections 3.7, 3.9, 3.13 and 3.18 of the MQL5 terms and I am not sure whether a personal copy falls under them.
2. Are there limits on history depth, number of requests or frequency?
3. Is Actual the first published figure, or is it updated when the source revises it?

I have run one small test only and will not save more until I understand the rules. If the answer needs to come from MetaQuotes staff, could someone point me to the right place?

Thank you.
MrSmithEFC:

I read the MQL5 economic calendar in MT5 with the calendar functions (CalendarValueHistory and related) for my own personal research. Before saving anything further I would like to check what the terms allow.

1. May I save a private, local copy of the values I read (event time, importance, actual, forecast, previous) for personal research only, without sharing, publishing or reselling it? I have read sections 3.7, 3.9, 3.13 and 3.18 of the MQL5 terms and I am not sure whether a personal copy falls under them.
2. Are there limits on history depth, number of requests or frequency?
3. Is Actual the first published figure, or is it updated when the source revises it?

1.Yes, you can save a local copy and use it for further analysis. For example, the calendar is not available in the tester, so you'll be able to load it there and backtest EAs based on events.

2. There are no limits, because your requests are cached in the internal calendar base in the terminal. When you request the calendar first time after the session start, it will usually take a considerable time (at least several seconds) to update, then you'll work with this copy and small online updates.

3. The actual value is just a field which can be changed (reviewed), the calendar does not provide a log of changes, so if you want it, you can monitor all values and save changes (if they happen) manually in a dedicated place (file, database, etc).

Stanislav Korotky #:

1.Yes, you can save a local copy and use it for further analysis. For example, the calendar is not available in the tester, so you'll be able to load it there and backtest EAs based on events.

2. There are no limits, because your requests are cached in the internal calendar base in the terminal. When you request the calendar first time after the session start, it will usually take a considerable time (at least several seconds) to update, then you'll work with this copy and small online updates.

3. The actual value is just a field which can be changed (reviewed), the calendar does not provide a log of changes, so if you want it, you can monitor all values and save changes (if they happen) manually in a dedicated place (file, database, etc).

Thank you for the clarification. Appreciated

New comment