Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

special notation for initial and final cycle points #1038

Closed
hjoliver opened this issue Jul 30, 2014 · 2 comments
Closed

special notation for initial and final cycle points #1038

hjoliver opened this issue Jul 30, 2014 · 2 comments
Assignees
Milestone

Comments

@hjoliver
Copy link
Member

(to consider after #996 is merged)

We can currently start (and end) recurrences at the initial (and final) cycle point using our simplified "in suite context" notation, which omits the end points entirely from the appropriate recurrence form. This works and is well defined but is not exactly easy to read at a glance particularly for the "fourth recurrence form" and final cycle point.

Should we consider either requiring or allowing explicit ^ and $ characters to represent suite initial and final points in recurrences, instead of omission - that would be easy to read and consistent with our in-graph notation (at least for initial point ... as I recall we didn't see a use case for in-graph final point notation yet).

@benfitzpatrick - thoughts?

@hjoliver hjoliver added this to the later milestone Jul 30, 2014
@benfitzpatrick
Copy link
Contributor

Yes, I think so - allowing it would be good for consistency. If a user writes:

foo[^+PT6H] => bar

they might expect to be able to write:

         [[[R1/^+PT6H]]]
             graph = "foo"

I think requiring it would lead to 'full rabbit' suites... too much caret.

@arjclark
Copy link
Contributor

There are a few cases where a notation for final cycle point would be useful - for example in trials where you want to run final cycle housekeeping/verification/archiving tasks.

@benfitzpatrick benfitzpatrick modified the milestones: soon, later May 25, 2016
@matthewrmshin matthewrmshin modified the milestones: next release, soon May 25, 2016
@matthewrmshin matthewrmshin modified the milestones: next release, soon Jun 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants