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

Output VectorPostprocessor data in order that they are declared #8974

Closed
aeslaughter opened this issue Apr 20, 2017 · 2 comments
Closed

Output VectorPostprocessor data in order that they are declared #8974

aeslaughter opened this issue Apr 20, 2017 · 2 comments
Assignees

Comments

@aeslaughter
Copy link
Contributor

Description of the enhancement or error report

In Mastodon we are creating time histories using VectorPostprocessors, which include the time as well as other parameters. When output it would be nice if the column named "time" was the first column.

Rationale for the enhancement or information for reproducing the error

Currently, they are in alphabetical order because they are stored in a map. I propose adding a vector of the ordered names when the VPP is declaring vectors, which can then be iterated on during output.

Identified impact

(i.e. Internal object changes, limited interface changes, public API change, or a list of specific applications impacted)
The order of CSV output would change.

@idaholab/moose-team Any objects before I whip this little guy out?

@aeslaughter aeslaughter self-assigned this Apr 20, 2017
@permcody
Copy link
Member

No need to store yet another piece of data that you have to manage and keep in sync. Just change the inner map to a vector of pairs instead. There are no speed issues here because we only declare a few vectors per vector postprocessor and those references are stored so we don't have to find them over and over again.

@friedmud
Copy link
Contributor

friedmud commented Apr 21, 2017 via email

aeslaughter added a commit to aeslaughter/moose that referenced this issue Apr 24, 2017
Chuban pushed a commit to Chuban/moose that referenced this issue May 2, 2017
Chuban pushed a commit to Chuban/moose that referenced this issue May 2, 2017
Chuban pushed a commit to Chuban/moose that referenced this issue May 2, 2017
Chuban pushed a commit to Chuban/moose that referenced this issue May 2, 2017
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

3 participants