-
Notifications
You must be signed in to change notification settings - Fork 145
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
bug: plot_rmse_xxx_evolution.m and plot_evolution not working with 1D location #230
Comments
This is trying to reshape a 3x3 into 400x 1
|
lorenz_63 workshop_setup.sh (input.workshop.nml) is out-of-date (v10 vs v11 qceff) |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This could be fixed by changing the many plotting programs to be smarter in detecting the lack of a 'level' for fields generated by models that use the oned location module. It can also be fixed as Tim suggested by modifying the oned/obs_diag_mod.f90 so that it outputs fields with an additional dimension 'level' that only has a single legal value. Note that these matlab scripts are generating an annoying error message when they create postscript output files which are apparently going to be no longer supported sometime after the matlab 2024a release. |
Implemented a fix to oned/obs_diag.f90 as discussed above. Results in output nc files where the fields have an extra singleton dimension with the only legal value -1 for level. This has been tested with Lorenz_96, Lorenz_63, Lorenz_84 and Lorenz_96_tracer_advection with matlab programs plot_rank_histogram.m, plot_evolution.m, and plot_rmse_xxxx_evolution.m. These had never been tested with Lorenz_96_tracer_advection which has multiple observation types, but all the features worked nicely. |
Describe the bug
plot_rmse_xxx_evolution.m and plot_evolution.m (and maybe more) no longer work with obs_diag_output.nc files from the models that use the oned_location_mod.f90
Run the lorenz_63 workshop_setup.csh and then run the obs_diag program with the default values. It generates an obs_diag_output.nc file with 200 timesteps and 3 observations (one for each state variable).
Error Message
Which model(s) are you working with?
Anything that uses the oned_location_mod.f90
Version of DART
v9.10.4
Have you modified the DART code?
No
Build information
Not a compiler problem, but Matlab is
R2019a Update 7 (9.6.0.1307630) 64-bit (maci64)
Any Idea on the solution?
The 1D obs_diag_output.nc files do not have a 'level' dimension, so it is (now) not interpreting the
time,copy,region
correctly.The 3D obs_diag_output.nc files have variables dimensioned
time,copy,level,region
. I think the solution is to detect that one has read 1D output files and reshape the variable to have a singleton dimension for level. Right about line 265 in the case ofplot_rmse_xxx_evolution.m
... I have not tested this solution, BTW.The text was updated successfully, but these errors were encountered: