-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add optional argument to make sure xbout reads David Bold's MMS outpu…
…t file as a dump file rather than a grid file.
- Loading branch information
Showing
1 changed file
with
7 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0ff4e76
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mrhardman the reason that xBOUT is thinking that you don't have a dump file is because it doesn't have a time output.
This is how xBOUT decides the file type:
xBOUT/xbout/load.py
Lines 593 to 595 in d113e0e
t is missing in the MMS test output. I would recommend to undo the changes from this commit and add time as an output variable to the MMS test.
0ff4e76
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discussed this on slack, and @dschwoerer was not in favour of this solution. Did you test that manually adding a t dimension solved all subsequent issues? If not, we will need to check if the dataset can have a dimension which none of the arrays use.
0ff4e76
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I just reviewed the chat. In that case why don't we rename this flag to "is_dump" or something like that? It sounds like it could be useful for whoever writes a BOUT++ application that doesn't need a time array.
0ff4e76
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might it not be better to always add some metadata to the BOUT++ output files?
Having xBOUT guess the type is probably not that great in general, that is why I was against this option, as it might be for other tools also helpful to have the info what kind of data this is.
Then we do not need an option for xBOUT, as the dump files will always have the needed info.
0ff4e76
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dschwoerer I totally agree that this would be the right solution. But in the meantime, maybe we can still put this flag in?