brokerclock 0.1.0__tar.gz

brokerclock-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,19 @@
+---
+name: Bug report
+about: A conversion or detection result that looks wrong
+labels: bug
+---
+
+**Broker server name** (optional):
+
+**Offset you saw** (and the UTC date and time you saw it):
+
+**Code** (a minimal example; include the bar or tick times if you can):
+
+```python
+
+```
+
+**Expected:**
+
+**Versions:** brokerclock, Python, pandas (if used), operating system

brokerclock-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,31 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    name: ${{ matrix.os }}, Python ${{ matrix.python-version }}
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install
+        run: python -m pip install ".[dev]"
+      - name: Lint
+        run: |
+          python -m ruff check .
+          python -m ruff format --check .
+      - name: Test
+        run: python -m pytest -q

brokerclock-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,65 @@
+# This workflow will upload a Python Package to PyPI when a release is created
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
+
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: Release
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  release-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Build release distributions
+        run: |
+          python -m pip install build twine
+          python -m build
+          python -m twine check --strict dist/*
+
+      - name: Upload distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+  pypi-publish:
+    runs-on: ubuntu-latest
+    needs:
+      - release-build
+    permissions:
+      # IMPORTANT: this permission is mandatory for trusted publishing
+      id-token: write
+
+    # Dedicated environments with protections for publishing are strongly recommended.
+    # For more information, see: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-protection-rules
+    environment:
+      name: pypi
+      url: https://pypi.org/p/brokerclock
+
+    steps:
+      - name: Retrieve release distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+      - name: Publish release distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/

brokerclock-0.1.0/.gitignore

@@ -0,0 +1,32 @@
+# Byte-compiled files
+__pycache__/
+*.py[cod]
+
+# Packaging
+build/
+dist/
+*.egg-info/
+.eggs/
+wheels/
+
+# Virtual environments
+.venv/
+venv/
+env/
+
+# Test and tool caches
+.pytest_cache/
+.hypothesis/
+.ruff_cache/
+.mypy_cache/
+.coverage
+.coverage.*
+htmlcov/
+.tox/
+.nox/
+
+# Editors and operating systems
+.idea/
+.vscode/
+.DS_Store
+Thumbs.db

brokerclock-0.1.0/CHANGELOG.md

@@ -0,0 +1,22 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - Unreleased
+
+### Added
+
+- `ServerZone`: a broker server clock as an IANA time zone plus a shift in 15-minute steps, with the constructors
+  `us()`, `eu()`, `au()` and `fixed()`, and the conversions `offset_at()`, `to_utc()`, `to_server()` and
+  `server_timestamp()`. The repeated hour is resolved by an explicit `ambiguous` policy; the skipped hour raises.
+- `detect()`: finds the server clock from M1 to H1 bar history alone, using the Friday 17:00 New York weekly
+  close, and reports the evidence: matched weeks, outliers, unexplained closes and tied candidates.
+- `measure_offset()` and `check()`: measure the current offset from a fresh tick, or confirm a zone against live
+  ticks, refusing stale ticks instead of guessing.
+- `brokerclock.pandas`: `to_utc()`, `frame_to_utc()` and `to_server_timestamps()` for whole columns and for the
+  arrays MetaTrader's `copy_rates_*` and `copy_ticks_*` return.
+- Errors with the common base `BrokerClockError`.
+
+[0.1.0]: https://github.com/raiez-alshamaly/brokerclock/releases/tag/v0.1.0

brokerclock-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        https://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       https://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

brokerclock-0.1.0/PKG-INFO

@@ -0,0 +1,204 @@
+Metadata-Version: 2.5
+Name: brokerclock
+Version: 0.1.0
+Summary: MetaTrader broker server time to UTC and back, with daylight saving done right.
+Project-URL: Homepage, https://github.com/raiez-alshamaly/brokerclock
+Project-URL: Source, https://github.com/raiez-alshamaly/brokerclock
+Project-URL: Issues, https://github.com/raiez-alshamaly/brokerclock/issues
+Author-email: Raeez alshamaly <github@raeez-alshamaly.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: algorithmic trading,backtesting,broker,daylight saving,dst,forex,fx,gmt offset,metatrader,metatrader5,mt4,mt5,pandas,server time,time zone,timezone,trading,utc
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Office/Business :: Financial :: Investment
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: tzdata; sys_platform == 'win32'
+Provides-Extra: dev
+Requires-Dist: hypothesis>=6; extra == 'dev'
+Requires-Dist: pandas>=2.0; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff==0.17.0; extra == 'dev'
+Provides-Extra: pandas
+Requires-Dist: pandas>=2.0; extra == 'pandas'
+Description-Content-Type: text/markdown
+
+# brokerclock — MetaTrader broker server time to UTC (and back), with daylight saving done right
+
+MetaTrader 5 does not give you UTC. The `time` and `time_msc` values that `copy_rates_*`, `copy_ticks_*`,
+`history_deals_get` and `history_orders_get` return are the broker's **server clock written as epoch seconds**,
+even though they look like Unix timestamps. If you searched for "MT5 server time UTC", "broker GMT offset" or
+"copy_rates time zone", this is why your bars are two or three hours off.
+
+- Most brokers run **GMT+2 in winter and GMT+3 in summer, switching with US daylight saving**: New York time plus
+  7 hours, so the forex day starts at server midnight, 17:00 in New York.
+- A fixed offset breaks for weeks every year. `+3` is wrong all winter, and even a European daylight-saving rule is
+  wrong for about three weeks in March and one week around the start of November, when the US and Europe switch
+  on different dates.
+- The server clock works in the other direction too: the date arguments of `copy_rates_range` and friends, and an
+  order's `expiration`, are read as server time.
+
+brokerclock models the server clock as an IANA time zone plus a shift, so every conversion uses the rule in force at
+that moment. It finds the rule from price history alone, confirms it against live ticks, and converts single values
+or whole pandas columns. It needs only the standard library (plus `tzdata` on Windows) and never imports
+`MetaTrader5`, so it runs and tests on any operating system.
+
+## Install (after the first release)
+
+```bash
+pip install brokerclock
+pip install "brokerclock[pandas]"   # with the pandas helpers
+```
+
+Python 3.10 or newer.
+
+## Quick start
+
+### 1. Find the broker's clock from H1 EURUSD bars
+
+```python
+import MetaTrader5 as mt5
+
+import brokerclock
+
+mt5.initialize()
+
+# About a year of H1 bars of a forex major.
+rates = mt5.copy_rates_from_pos("EURUSD", mt5.TIMEFRAME_H1, 0, 6500)
+result = brokerclock.detect(rates["time"], timeframe=3600)
+print(result.zone)  # GMT+2/+3 (US daylight saving)
+print(f"{result.matched} of {result.total} weeks agree")
+zone = result.zone
+```
+
+If `result.ambiguous` is true, the bars cannot separate the clocks in `result.candidates` (summer-only data, for
+example): fetch a longer span. Running the same check on a second major is good practice. Once known, the clock is a
+constant you can keep in your configuration, such as `brokerclock.ServerZone.us()`.
+
+### 2. Convert bars to UTC
+
+```python
+import brokerclock.pandas as bcpd
+
+bars = bcpd.frame_to_utc(rates, zone)  # a DataFrame whose "time" column is aware UTC
+print(bars[["time", "close"]].tail(3))
+
+first_bar = zone.to_utc(rates["time"][0])  # one value, without pandas: an aware UTC datetime
+```
+
+### 3. Query by UTC and set an order expiration
+
+```python
+from datetime import datetime, timedelta, timezone
+
+# Bars of March 2025 in UTC terms. Pass server-clock ints: a naive datetime would go through the PC's time zone.
+start = datetime(2025, 3, 1, tzinfo=timezone.utc)
+end = datetime(2025, 4, 1, tzinfo=timezone.utc)
+march = mt5.copy_rates_range("EURUSD", mt5.TIMEFRAME_H1, zone.server_timestamp(start), zone.server_timestamp(end))
+
+# A pending order that expires four hours from now.
+expiry = datetime.now(timezone.utc) + timedelta(hours=4)
+request = {
+    "action": mt5.TRADE_ACTION_PENDING,
+    "symbol": "EURUSD",
+    "volume": 0.1,
+    "type": mt5.ORDER_TYPE_BUY_LIMIT,
+    "price": 1.05,
+    "type_time": mt5.ORDER_TIME_SPECIFIED,
+    "expiration": zone.server_timestamp(expiry),
+}
+mt5.order_send(request)
+```
+
+### 4. Check the clock against live ticks
+
+```python
+tick = mt5.symbol_info_tick("EURUSD")
+if brokerclock.check(zone, [tick.time_msc / 1000]):
+    print("live ticks agree with", zone)
+else:
+    print("no fresh tick to confirm it: the market is closed, or the zone is ahead of the server")
+
+# Without a known zone: the current offset, while the market trades.
+print(brokerclock.measure_offset([tick.time_msc / 1000]))  # 3:00:00 in summer, 2:00:00 in winter
+```
+
+`check` raises `ZoneMismatchError` when the tick would be from the future under that zone (the zone is behind the
+server, or the PC clock is behind). `measure_offset` raises `StaleTickError` or `OffsetOutOfRange` instead of
+guessing when the tick is not fresh.
+
+## Broker clock conventions
+
+| Server clock | Winter | Summer | Switch dates | `ServerZone` |
+|---|---|---|---|---|
+| New York close, the most common | GMT+2 | GMT+3 | US: second Sunday of March, first Sunday of November | `ServerZone.us()` |
+| EU rule | GMT+2 | GMT+3 | EU: last Sundays of March and October | `ServerZone.eu()` |
+| EU rule, central European | GMT+1 | GMT+2 | EU | `ServerZone.eu(1)` |
+| Australian rule | GMT+2 (April to October) | GMT+3 (October to April) | AU: first Sundays of October and April | `ServerZone.au()` |
+| Fixed GMT | GMT+0 | GMT+0 | none | `ServerZone.fixed(0)` |
+| Fixed GMT+2 | GMT+2 | GMT+2 | none | `ServerZone.fixed(2)` |
+| Any other clock | | | | `ServerZone.us(3)`, `ServerZone.fixed(5.75)`, `ServerZone("Asia/Tokyo")`, `ServerZone("Europe/Berlin", timedelta(hours=1))` |
+
+A `ServerZone` is the wall clock of an IANA zone plus a shift in 15-minute steps; `str(zone)` describes it, for
+example `GMT+2/+3 (US daylight saving)`.
+
+## How detection works
+
+1. A gap of 40 hours or more after a bar is a weekend; that bar's end is the weekly close on the server clock.
+2. The forex week ends on Friday at 17:00 New York, so each close gives the server's offset that week. Brokers close
+   at or before 17:00, never after, so the offset is rounded up to the next 15 minutes.
+3. Every candidate clock (fixed, or US, EU or Australian daylight saving, at any base offset) predicts each week.
+4. The clock that predicts the most weeks wins; the weeks it misses are `outliers` (early holiday closes), and closes
+   that fit no Friday are `unexplained`.
+5. A tie means the data cannot tell the clocks apart, and `zone` is `None`: use a longer span.
+
+Detection needs a forex major and bars from M1 to H1 (`timeframe` 60 to 3600 seconds; longer bars are rejected
+because they end on the server's own 4-hour or day boundaries and hide the switch weeks). Use M15 or shorter for
+clocks with 30- or 45-minute offsets. The data should cover at least six months, or a span that includes March or
+late October to early November.
+
+## API
+
+| Name | Purpose |
+|---|---|
+| `ServerZone(zone, shift)`, `.us()`, `.eu()`, `.au()`, `.fixed()` | the server clock |
+| `zone.to_utc(server_time, ambiguous="raise")` | server epoch seconds or naive server datetime to aware UTC |
+| `zone.server_timestamp(instant)`, `zone.to_server(instant)` | aware instant to server epoch int, or naive server datetime |
+| `zone.offset_at(instant)` | the server's UTC offset at an aware instant |
+| `detect(bar_times, timeframe=3600)` | the clock from M1 to H1 bar history, as a `Detection` |
+| `measure_offset(server_times, now=None, tolerance=60)` | the current offset from a fresh tick and the PC clock |
+| `check(zone, server_times, now=None, tolerance=60, max_age=300)` | whether live ticks agree with a zone |
+| `brokerclock.pandas`: `to_utc`, `frame_to_utc`, `to_server_timestamps` | the same conversions for whole columns |
+
+The library's own errors share the base class `BrokerClockError`, a `ValueError`: `AmbiguousTimeError`,
+`NonexistentTimeError`, `NotEnoughData`, `StaleTickError`, `OffsetOutOfRange` and `ZoneMismatchError`. Invalid
+arguments raise a plain `ValueError` or `TypeError`.
+
+## Limitations
+
+- When a broker switches the clock of 24/7 symbols (crypto CFDs) is broker-specific, so bars of those symbols right
+  at a switch can be an hour off.
+- Metals and indices follow their own exchange hours; detect the clock from a forex major.
+- Live measurement depends on the PC clock; keep automatic time sync on.
+- A broker's demo and live servers can run different clocks; detect each one.
+- A broker that changes its clock may rewrite its history in the new clock; detect again after a change.
+- Weekly closes less than 14 minutes before 17:00 New York are handled (16:50 in M5 bars, 16:47 or later in M1
+  bars). If the last bar of a week ends 14 minutes or more early (16:40, say), that week reads 15 minutes off. A
+  few such weeks become `outliers`; if every week ends that way, the whole result is 15 minutes off, for example
+  GMT+1:45/+2:45 instead of GMT+2/+3. H1 bars avoid this, because the last H1 bar still ends at 17:00.
+
+## Notes
+
+Not affiliated with MetaQuotes. MetaTrader is a trademark of MetaQuotes Ltd.
+
+Copyright 2026 Raeez alshamaly. Licensed under the Apache License, Version 2.0; see [LICENSE](LICENSE).