-
Notifications
You must be signed in to change notification settings - Fork 52
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
Save MOC due to GM bolus velocity (postprocessing script) #673
Comments
@milenaveneziani, could you clarify if the request is to plot just the MOC component due to the bolus velocity or if it is to write out this data in a NetCDF file (or both)? |
The easiest thing could be to start saving it to file. And then leave the plotting to the more advanced user. |
@milenaveneziani, is this something you want to try to do before the next MPAS-Analysis release in a month or so? |
probably not, @xylar. I'd also need to check with @vanroekel about whether this is done already with in-house scripts. |
That's fine. Just checking. |
@milenaveneziani this is now written by the online MPAS-O analysis member by all runs for quite a while. I don't recall exactly when, but now for all meshes that have the MOC turned on in MPAS-O you get the total (resolved + GM) and a separate GM only streamfunction. |
OK, so I did remember correctly. Thanks @vanroekel. It would just be a matter of adding panels with the GM bolus streamfunction component in MPAS-Analysis. |
Mat noted that we should save the MOC component due to the bolus velocity. This is especially important when we use horizontally and vertically varying GM, to make sure that things look OK.
The text was updated successfully, but these errors were encountered: