David Sutherland

> Even though both clock triggers are sequential by default, I get all of the tasks spawning out to the runahead limit ~1s after each other I guess the expected...

> > Even though both clock triggers are sequential by default, I get all of the tasks spawning out to the runahead limit ~1s after each other > > I...

Ok fixed it now: ``` [scheduler] allow implicit tasks = True [scheduling] initial cycle point = 2018 [[xtriggers]] clock_1 = wall_clock() clock_2 = wall_clock(P10Y) [[graph]] P1D = @clock_1 & @clock_2...

> I've sorted out the conflict and added a few tests in [dwsutherland#19](https://github.com/dwsutherland/cylc-flow/pull/19) Saw there were a lot of conflicts with that PR, I assume you had rebased on master,...

> Ah I see you've force pushed again - the merge error is here: https://github.com/cylc/cylc-flow/compare/598e0afe6c2e89cbcc6353f48e2363fe2dde34f2..8e7e3f17fc8832aa6ebb9a9dec800ec85d624762#diff-616dbf97f9b89762d7da3666f7ab3abf0cc3f2e6443b5367af9d25439a4321d5R334-R354 Haha.. Apologies, yes, I rebased and did some tests.. will squash as fix to your...

> @dwsutherland this is now my main focus for review - are you working on conflict resolution, post `cylc set` merge? Ping me if you need any help understanding the...

`to_snake_case` gets called on every field, it essentially translates between python variable names and JS names (i.e. `taskProxy` -> `task_proxy`).. only way to get rid of it would be to...

My only concern with `|` is how it plays out in the shell world WRT CLI.. i.e. ``` (flow) sutherlander@cortex-vbox:~$ echo hello|goodbye goodbye: command not found ``` so we'd always...

> (Unfortunately, the pipe | character cannot be used here either because it is already the OR operator.) @matthewrmshin - We/I weren't advocating for `|` as a task name character...

Hmm... Maybe migrating to a two character delimiter for CLI/IDs (internally and externally) is something to look into, then we can probably jump through all shell, datetime, suite/task name hoops....