# Wall clock synchronization (real time scheduling)

**URL:** <https://cylc.discourse.group/t/wall-clock-synchronization-real-time-scheduling/58>\
**Category:** Cylc Support\
**Created:** [June 5, 2019, 12:08pm UTC](https://cylc.discourse.group/t/wall-clock-synchronization-real-time-scheduling/58 "2019-06-05T12:08:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![matthewrmshin](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/matthewrmshin/32/23_2.png) [@matthewrmshin](https://cylc.discourse.group/u/matthewrmshin)\
**Post date:** [June 5, 2019, 1:22pm UTC](https://cylc.discourse.group/t/wall-clock-synchronization-real-time-scheduling/58/2 "2019-06-05T13:22:26Z")

</div>

Hi Clinton,

After a lot of discussion between the development team, it looks like the best answer looks like this:

```auto
[scheduling]
    initial cycle point = next(T-00; T-05; T-10; T-15; T-20; T-25; T-30; T-35; T-40; T-45; T-50; T-55)
    [[dependencies]]
        [[[PT5M]]]
             graph = task1

```

Note:

1. The `-` in `T-00`, etc is a placeholder for the hour, not a minus sign.
2. This should work the way you expect. If current time is 16:23, the initial cycle point will become 16:25. The `next(...)` syntax is explained in the user guide: [https://cylc.github.io/doc/built-sphinx-single/index.html#scheduling-initial-cycle-point-initial-cycle-point-relative-to-current-time](https://cylc.github.io/doc/built-sphinx-single/index.html#scheduling-initial-cycle-point-initial-cycle-point-relative-to-current-time)
3. This is most efficient for Cylc, because your graph will have a single recurrence, instead of 12 recurrences.

Matt

---

_[View the full topic](https://cylc.discourse.group/t/wall-clock-synchronization-real-time-scheduling/58)._