{"action":"opened","issue":{"url":"https://api.github.com/repos/idaholab/moose/issues/4877","labels_url":"https://api.github.com/repos/idaholab/moose/issues/4877/labels{/name}","comments_url":"https://api.github.com/repos/idaholab/moose/issues/4877/comments","events_url":"https://api.github.com/repos/idaholab/moose/issues/4877/events","html_url":"https://github.com/idaholab/moose/issues/4877","id":65973054,"number":4877,"title":"Multiapp Initialization and header sanity","user":{"login":"permcody","id":3036960,"avatar_url":"https://avatars.githubusercontent.com/u/3036960?v=3","gravatar_id":"","url":"https://api.github.com/users/permcody","html_url":"https://github.com/permcody","followers_url":"https://api.github.com/users/permcody/followers","following_url":"https://api.github.com/users/permcody/following{/other_user}","gists_url":"https://api.github.com/users/permcody/gists{/gist_id}","starred_url":"https://api.github.com/users/permcody/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/permcody/subscriptions","organizations_url":"https://api.github.com/users/permcody/orgs","repos_url":"https://api.github.com/users/permcody/repos","events_url":"https://api.github.com/users/permcody/events{/privacy}","received_events_url":"https://api.github.com/users/permcody/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/idaholab/moose/labels/C:%20MOOSE","name":"C: MOOSE","color":"0052cc"},{"url":"https://api.github.com/repos/idaholab/moose/labels/P:%20normal","name":"P: normal","color":"ededed"},{"url":"https://api.github.com/repos/idaholab/moose/labels/T:%20task","name":"T: task","color":"cccccc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-02T17:29:25Z","updated_at":"2015-04-02T17:29:25Z","closed_at":null,"body":"I believe that we should settle on a way to display information to the users when running a Multiapp simulation:\r\n\r\n- Currently Headers are output in post-order depth first search\r\n- Execution Order however is post-order breadth first search\r\n\r\nWe should output the headers in execution order or *pre-order* breadth first search (my pick). While execution order has the obvious advantage of indicating the execution order it still creates an odd order to display information to the user. It reports information about *this* simulation very last and shows the user information about the lowest leaves very first. If additional levels are tacked onto the bottom they also start coming out first which just doesn't feel intuitive. I feel that the best order to display header information in a top down fashion. See samples below:\r\n\r\n```\r\npost-order depth first search (current implementation)\r\nsub0_sub0\r\nsub0_sub1\r\nsub0\r\nsub1_sub0\r\nsub1_sub1\r\nsub1\r\nmaster\r\n```\r\n\r\n```\r\npre-order breadth first search (my favorite)\r\nmaster\r\nsub0\r\nsub1\r\nsub0_sub0\r\nsub0_sub1\r\nsub1_sub0\r\nsub1_sub1\r\n```\r\n\r\n```\r\npost-order breadth first search (execution order - another alternative)\r\nsub0_sub0\r\nsub0_sub1\r\nsub1_sub0\r\nsub1_sub1\r\nsub0\r\nsub1\r\nmaster\r\n```\r\n\r\n@idaholab/moose-developers please comment\r\n"}}