Simulation
Reading the variables of each file type
Please wait!
The simulations you have added to the bank. In Analyze and Compare simulations, the arrow in the Name box lists them. Add simulation info to see how many files and variables a simulation has, the years they cover and how big it is. Removing one only forgets its name, directory and info: no files are touched.
| Name | Directory | Number of files | Number of variables | Years | Size of simulation |
|---|
Nothing is in the bank yet. Use Add to the bank below, or Add to bank when you set up Analyze or Compare simulations.
These go on in the background, one at a time: you can leave this page, or ask for more.
Reading the data store...
Built-in datasets that have not been downloaded into the data store. The years are those the dataset covers.
The work you chose to add to your OceanVal history. Choose the kind of work to see it.
| Name | Saved |
|---|
Removing work here only takes it out of OceanVal's history. No files are deleted.
Reading the variables of each file type
Please wait!
One check for each file pattern, made on its first file for the first variable matched up from it. No matchups can be run unless every check passes.
A recipe describes a set of observations once, so that you can use it again in any matchup by name, like recipe={"chlorophyll": "occci"}, which is one of OceanVal's own. Your recipes are kept in .oceanvalrc files: in the directory you run OceanVal from, for that directory only, or in your home directory, for everywhere. Which kind of data is the recipe for?
OceanVal has just identified whether the units are the same or whether the observational data needs to be adjusted to be in the model units. Please check the unit conversions below before proceeding.
Each observation becomes observation × Multiply by + Add before it is compared with the model. Multiply by rescales the units: roughly 1.025 turns µmol/kg into mmol/m3. Add shifts the zero point: 273.15 turns °C into K. Leave both boxes empty when no conversion is needed, and fill in any row OceanVal could not work out. Its suggestions are in bold. The units must be confirmed, with the tick box beside Continue, before the matchup starts.
Reading the units from the simulation…
OceanVal's gridded recipes, and your own gridded data (netCDF).
| Matchup | Simulation variable | Simulation units | Observation variable | Observation units | Multiply by | Add |
|---|
No gridded datasets are being matched up.
OceanVal's ICES recipes, and your own point data. Your own point data is csv files, which have no units, so it is up to you to make sure they match the simulation's.
| Matchup | Simulation variable | Simulation units | Observation variable | Observation units | Multiply by | Add |
|---|
No point datasets are being matched up.
OceanVal matches each observation in these point datasets to the simulation output on the same day, as their point_time_res includes day. But the simulation output for their variables is coarser than daily: monthly, or once every few days. So most of their observations may find no simulation output on the same day, and be left out of the matchups.
Matching them by year and month instead compares each observation with the simulation output for its month. OceanVal suggests that, in bold, but you can choose for all of them at once, for each one, or keep them as they are.
| Variable | Dataset | Time resolution | Matched by now | Match observations by |
|---|
Click the × on a box to leave that figure or analysis out of the report. A box left out is greyed out: click Add back to keep it after all.
OceanVal is finding the simulation's output files, and the variables in them.
The simulation has changed, so OceanVal filled in the variables it recognised again. The rows you gave yourself are kept.
Choose the variables to analyze
| Environmental variable Enter your own or select from available presets | Variable name in the simulation Enter variable names or search terms that will look up the variable and name and descriptions in files |
|---|
These simulation variables are time means, and their times look like the end of the period each mean covers: a day's mean dated 00:00 the next day, or a month's dated 00:00 on the 1st of the next month. If so, a January mean would count as February's, and the year's last mean would fall in the next year.
Their files have no time bounds to say for certain, so OceanVal does not shift anything unless you choose it. It suggests shifting every simulation time back one day, in bold, so that each mean falls in the period it covers. The dates of the files are read once you have chosen.
| Variable | Files | Times now | Shifted | Why they look like ends |
|---|
OceanVal is checking whether the times of the files are the start or the end of the period each mean covers.
| Variable | Model variable | Files | Time resolution | Dates |
|---|
Everything you choose is worked out for every simulation, over the same years, which must be years all of them have, and the cell thickness (a variable in each simulation's output, or a file) is the same in all of them.
Select one or more of the analyses
Choose where to save the analysis
OceanVal is finding the simulations' output files, and the variables in them.
What variables do you want to compare?
Each value becomes value × Multiply by + Add as it is read, so every analysis (and a water column's integral) is of the converted values. Multiply by rescales the units: 1000 turns mol/m3 into mmol/m3. Add shifts the zero point: -273.15 turns K into °C. Leave both boxes empty when the units are the same, only written another way. OceanVal's suggestions are in bold. The units must be confirmed, with the tick box beside Continue.
These simulation variables are time means, and their times look like the end of the period each mean covers: a day's mean dated 00:00 the next day, or a month's dated 00:00 on the 1st of the next month. If so, a January mean would count as February's, and the year's last mean would fall in the next year.
Their files have no time bounds to say for certain, so OceanVal does not shift anything unless you choose it. It suggests shifting the times of the simulations below back one day, in bold, so that each mean falls in the period it covers. The other simulations are not shifted. The dates of the files are read once you have chosen.
| Simulation and variable | Files | Times now | Shifted | Why they look like ends |
|---|
OceanVal is checking whether the times of the files are the start or the end of the period each mean covers.
The simulation output with the highest temporal resolution has been identified and is listed below. These files will be used for analysis. The simulations are compared over the years they all have.
The simulations can be on different model grids. To compare them cell by cell, and to take means over exactly the same area, they need to be put on one grid.
FVCOM output is a mesh of triangles. It is regridded to the grid chosen (nearest neighbour, as the matchups regrid it) when the comparison runs, so only the cells inside the mesh have values; the unified grid below shows this. The regridding method chosen is for the simulations that are not FVCOM. Variables below the surface are interpolated from the sigma layers to the depths of the levels of the first simulation that is not FVCOM, or, if all of them are, 0 to 150 m every 5 m.
Cells with no value in any one simulation are made missing in all of them. Once the simulations are on one grid, a cell that is missing in one simulation (land, say, or a place it has no water) is set to missing in every simulation, so that all of them are compared over exactly the same cells. This is judged from the first time step of each simulation's output, for each variable and each layer.
Every simulation is put on a regular lon-lat grid of this box and resolution, with nctoolkit's to_latlon, by the method chosen below.
The baseline's grid is the one the comparisons are made on. Each of the other simulations is regridded to it, with nctoolkit's regrid, by the method chosen below. The baseline itself is not regridded.
These simulation variables are time means, and their times look like the end of the period each mean covers: a day's mean dated 00:00 the next day, or a month's dated 00:00 on the 1st of the next month. If so, matched up as they are, a January mean is compared with February's observations, and the year's last mean falls in the next year and is left out.
Their files have no time bounds to say for certain, so OceanVal does not shift anything unless you choose it. It suggests shifting every simulation time back one day, in bold, so that each mean falls in the period it covers.
| Variable | Files | Times now | Shifted | Why they look like ends |
|---|
| Variable | Years | Simulation variable | Observation source | File pattern to be used | Time resolution | Dates |
|---|
Change which file names are used. OceanVal will read the simulation again with them and return to the recipes, to check the simulation variables, keeping your choices where they still apply.
A question for you
Earlier output is not shown.
Nothing has been matched up and no report has been built. To do both later, open a terminal, activate the environment OceanVal is installed in, and run:
Script file:
Datasets Required
Years Required
lon-lat extent Required
The area is rounded out to whole degrees, and one that is nearly the whole globe is kept as the whole globe. What the store already has of a dataset is kept too: the new area is added to it.
Do you want the water column? Required
Asked for the datasets that can be kept at the surface alone (World Ocean Atlas 2023). Yes replaces a surface-only copy in the store.
Downloads can be slow, and the servers send whole global fields whatever the area: the area only shrinks what is kept. They go on in the background, one at a time, so you can ask for more.
Where it looks. OceanVal searches the directory you give, and the number of directories below it that you say, for netCDF files. Once you have told it the names of your simulation variables, it works out which files contain each one.
Which files it uses. Where a variable is held at more than one time resolution, for example in both daily and monthly files, OceanVal uses the files with the highest temporal resolution, so your matchups are as detailed as your output allows.
When to help it. A simulation directory often holds files that are not the output you want to validate: restart files, test runs, 5-day means, or files for a spatial subregion beside files for the whole domain. If these are picked up, the matchups can be wrong. Don’t worry, OceanVal will tell you exactly what files it’s going to use for matchups later on. Type words from the names of the files to leave out into Skip file names containing and press Enter (for example restart or 5d), or words that the files you want share into Only include file names containing (for example grid_T). Each word appears in a list below its box; the × at its top right removes it. Every Skip list starts with restart and spinup, the files that are not the output; the × beside a word removes it.
To choose words, look at the names of the files in your simulation with “View the files in a random subdirectory”.
| Required | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Variable | Start Required | End Required | Surface | Bottom | Vertical mean | Vertical integration | Use a rolling mean (years) | Show as | Total over the domain |
For FVCOM output the cell thickness is worked out from its sigma levels (siglev), bathymetry (h) and surface elevation (zeta), at each time.
The time series are always worked out for the model's domain as a whole. Choose regional subdomains, as in the validation, to work them out for each region too, and cut a box out of the domain if you want only part of it. The long-term time series and the seasonal cycles share these, and the stations are not cut by the box.
Add places to work the series out at too: the name of each and its longitude and latitude. The nearest cell of the model with values is used. The stations are the same for the long-term and the seasonal time series.
| Name | Longitude | Latitude |
|---|
Click the variables of the simulation's output files to add. Those already in the list are marked and cannot be picked again.
The day of the year of the seasonal peak at the surface is calculated from the daily climatology for the year range given, and mapped. It needs daily output.
| Model variable | Start Required | End Required |
|---|
The average of each period is calculated and mapped, with its change from the historical period. A second future period is optional: give both of its years, or neither.
| Required | Required | Required | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Variable | Historical | Future 1 | Future 2 Optional | Surface | Bottom | Vertical mean | Vertical integration | |||
| First | Last | First | Last | First | Last | |||||
For FVCOM output the cell thickness is worked out from its sigma levels (siglev), bathymetry (h) and surface elevation (zeta), at each time.
The model's values along straight lines are calculated for the year ranges given, and plotted. Each variable can have as many transects as you like.
Each transect must run north–south, with the same longitude at both ends, or east–west, with the same latitude at both ends. The Surface and the Vertical (a section through the water column) each have a Climatology, the mean of each month of the year along the line (at the surface) or the annual mean (in the section), and Changes, how it changed over the years as a map of position along the line by year, of the annual means or of their change from the first year (or the first rolling mean), with an optional rolling mean.
A vertical section needs to know where each cell is. With z_level the model's levels are the depths. With a thickness, each cell is placed at its depth, from the top of the water column, and the section is put on evenly spaced depths.
For FVCOM output each sigma layer of a vertical section is placed at its depth from its share of the sigma levels (siglev) of the mean depth of the water (h + zeta), so no thickness is needed.