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

Pipeline phase name #192

Open
Mortal opened this issue Dec 11, 2015 · 0 comments
Open

Pipeline phase name #192

Mortal opened this issue Dec 11, 2015 · 0 comments
Labels

Comments

@Mortal
Copy link
Collaborator

Mortal commented Dec 11, 2015

Jakob and I think it would be better to have phase names (with priorities) and node names (without priorities) than the current setup where we only have node names with priorities, and the phase name is the node name with highest priority.

  1. Introduce phase names and change phase name selection procedure
  2. Switch our code to not pass priorities to node names
  3. Remove the possibility of passing priorities to node names

We should only be able to set phase names on a pipe_base object.

antialize added a commit that referenced this issue Dec 11, 2015
Currently nodes do export a set_phase_name, even though we would like them not to
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant