add / revise definitions of terms used in the CIM
This page provides documentation for ticket:280.
The table below will be used to record agreed definitions of terms used within the CIM and Controlled Vocabularies (CVs) used by the CIM and the questionnaire being developed for CMIP5. There is not a one-to-one mapping between the terms used by the CIM, CVs, or questionnaire. The reason is as follows:
The CIM is intended to capture the structure of concepts in climate modeling and how they relate to each other. For example, the CIM clearly documents that there are things called components and they can have child components and, furthermore, each component has a type which can take one of several enumerated values. The CIM is implemented in UML. This UML is then translated to a set of XSD files.
CVs are intended to capture the permissible content of those enumerated values and to further constrain how the CIM - now with its specific content taken from a CV - can be organised. For example, the CV we are building for CMIP5 clearly documents that the set of component types that can be used in the CIM includes things like "atmosphere," "ocean," "sea-ice," "radiation," etc. Furthermore it constrains where those values can be used; an atmosphere component can have a child radiation component, but not a child ocean component. The CVs are currently implented as mindmaps. But this is just for convenience (mindmaps were easy to work with, useful for showing scientists, and able to be used as input to the questionnaire code). In the future, the CVs will be implemented differently. More on that later.
The questionnaire is a means of creating CIM records (XML documents that conform to the CIM XSD) which adhere to a particular (set of) CV(s). So the questionnaire might ask if your atmosphere component has any radiation components as children, but it would never ask if you have any ocean components as children of atmosphere. The output of the questionnaire is translated to an XML file that conforms to the CIM. Of course, since it's really just a data-collection tool the terms used in the questionnaire can obviously differ from those used in the CIM (this would all be sorted out during translation).
Now, here's where it gets tricky(er): It is true that eventually the CV will be stored in some format other than a mindmap. We think that it will be stored externally in a "CV Server" where it can be downloaded and paired with the CIM. In the meantime, though, we have to have working code. So many of the terms/concepts in the CV are explicitly stored in the CIM. For example, the <<codelist>> ComponentType in the CIM has a set of enumerated values defined in the UML such as "ocean," "atmosphere," "radiation," etc. This is obviously an incomplete list, and one of the goals of this wiki page is to extend/refine such lists in the CIM to make them more usable and to ensure they don't contradict or leave out anything defined in the CV (mindmaps). The relationships among CV terms that is implicit in the hierarchical structure of the mindmaps is missing in the CIM. For now we are relying on the fact that the questionnaire will constrain all input so that invalid relationships (like an atmosphere with a child ocean) are never generated.
This should explain why things are a bit messy right now and there is not a one-to-one mapping between terms used in the CIM, CVs, or questionnaire.
METAFOR CIM value is the name of the item as it is displayed in the CIM.
METAFOR package is the package the item appears in within the CIM. If it only appears in the Models.py file or the mindmaps, so indicate.
ESG display is the name of the item as it is displayed in the ESG portal. "Needed:" preceding the entry indicates that this still needs to be added to the display.
ESG search will capture which pieces of metadata we will want to search on. An X in the box indicates a searchable term
ESG source indicates why this is targeted for ESG - it is desired for CMIP5, it is being used to describe previous CMIP3 simulations, it came from the dynamical core workshop, or from an early Curator prototype.
ESG input describes how the metadata is expected to be entered into ESG, and may be the models.py file of the questionnaire (Q), the gridspec tool, output data files (NC), or other.
ESG tab is the tab the term appears on in the ESG user interface.
Notes should include relevant comments or questions about the definition as well as the name of the controlled vocabulary that the term belongs to.'
Status can be either submitted (added to the wiki, not yet discussed via email), in-progress (being discussed), agreed (having been discussed, the term is resolved), rejected (the term has been replaced or is not needed) or done (having been resolved, the definition has been embedded within the CIM). Uploaded indicates the definition has been added to the ESG ontology. Non-contentious terms don't really have to be discussed.
| METAFOR CIM value | METAFOR package | ESG display | ESG search | ESG source | ESG input | ESG tab | Definition | Notes | Status | in CIM? | ||
| BASIC COMPONENT PROPERTIES | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | |||
| Abbreviation for Component | N/A for components | CMIP5 | Q for Component NC for Experiment | Displayed above tabs & Experiment | N/A for component | SJM: For components, this is the rdfs:label The word label does not appear in the display only its value:<h1>get.value(rdfs:label)</h1> | N/A for component | |||||
| ExperimentID for Experiment | experimentID for activity::Experiment | Experiment for Experiments | CMIP5 | NC for Experiment | Displayed above tabs & Experiment | A controlled test or investigation with predefined parameters. This is a citation or pointer where further information may be found. | SJM: For experiments, this is "Experiment". It is the short identifier. For CMIP3 this is a number e.g. 3.4 | submitted | activity::Experiment has attribute "experimentID" of type shared::Identifier | |||
| Title for Component Experiment for Experiment | Full Name | X for Experiment | CMIP5 | Q for Component NC for Experiment | Displayed above tabs & Experiment | N/A for component The name of a model, model component, simulation, experiment, or dataset with all acronyms spelled out. | SJM: For Components: This will be displayed above the tabs right under the Label/Abbreviation. While the text "Full Name" will appear, like "Description", we will not associate a definition with it. SJM: For Experiments: This will appear as "Full Name" under the experiment tab. We would prefer not to display a definition for "Full Name". The ability to turn off select definition has not yet been implemented. SJM: This is the string that describes each experiment numeric identifier. Gary Strand has the complete table. | N/A for component submitted & uploaded for experiment | ||||
| Description | Description | CMIP5 | Q | Displayed above tabs | N/A | SJM: While description shows up on the UI, it is right below the title and outside of the the tabs. I don't think we want a definition for it. | N/A | "description" attributes appear throughout the CIM; they are CharaterStrings. | ||||
| ContactName | NA | Contact Name | CMIP3 & CMIP5 | Q for Component Needed: for Experiment | Basic Properties & Experiment | The person designated to provide information about a model component, dataset, or experiment. | SJM: A unique contact name for the experiment will show up under the experiment tab. | submitted & uploaded | responsibleParty is an attribute of data::DataDistribution, activity::Activity, and software::SoftwareComponent - these are all instances of gmd:CI_ResponsibleParty | |||
| ContactEmail | NA | Contact Email | CMIP5 | Q for Component Needed: for Experiment | Basic Properties & Experiment | The email address of the person designated to provide information about a model component, dataset, or experiment. | SJM: Gary Strand recommends that there be only one email address per simulation. They plan to create an alias so that questions go to a group vice a person. SJM: The contact email for the Experiment will be different. | submitted & uploaded | email is described as part of gmd:CI_ResponsibleParty (above) | |||
| PI | activity | Principal Investigator | CMIP3 & CMIP5 | Needed:Q | Basic Properties | The scientist in charge of an experiment or research project. | SJM: Gary Strand says this is important but no email address, just a name. | submitted & uploaded | principleInvestigator is an optional attribute of activity::Activity | |||
| Needed: DataHolder | Data Holder | CMIP3 & CMIP 5 | Needed:Q | Basic Properties | The person responsible for a dataset. | SJM: Gary Strand says this is important but no email address, just a name. | submitted & uploaded | |||||
| Reference | Shared | Reference | CMIP5 | Q | Reference | A citation or pointer (e.g.URL) to a location where further information may be found. | submitted & uploaded | |||||
| Note | Note | Curator | Q NC Local Runs | Basic Properties | A brief comment. | SJM: The questionnaire contains many comment blocks. In the XML instance, will these be listed as <comment> or <note>. Either way we can handle it. | submitted & uploaded | |||||
| ScienceType | Software (Model Component Type) | Discipline | X | CMIP5 | Q | Basic Properties | A primary field or area of study that applies to a component or dataset. | CD: mainly for use as a search term (e.g., climate, weather, hydrology) SJM: These attributes may be used to describe datasets as well. | submitted & uploaded | |||
| Realm | Physical Domain | X | Curator | NC | Basic Properties | A description of the geographic range being simulated in a particular activity. | SJM: According to Bryan there are at most 7, possible 8 realms SJM: It will not be in the questionnaire per 8/4/09 email from Bryan. Only Science Type will be collected. | submitted & uploaded | ||||
| Needed: FundingSource | Funding Source | CMIP3 | Needed:Q | Basic Properties & Experiment | The entity that funded a model component, simulation, or dataset. | SJM: This will be two different values for Experiment and the Model/Simulation. | submitted & uploaded | |||||
| Centre | Institution | CMIP5 | Q | Basic Properties | An organization associated with a model component, simulation, or dataset. | SJM: We will convert on upload | submitted & uploaded | |||||
| Components | Child Components | CMIP5 | Q | Components | N/A | SJM: Opened ticket 312 to find out if this value will list the child components of the questionnaire instance | N/A | |||||
| CONFORMANCE | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | |||
| Experimental Conformance Type | CMIP5 | Q | Conformance | The method(s) by which a simulation conforms to an experiment requirement | ||||||||
| Experimental Conformance Input Binding Component | CMIP5 | Q | Conformance | The model component(s) that require inputs to allow a simulation to conform to an experiment requirement | ||||||||
| Experimental Conformance Input Binding Variable | CMIP5 | Q | Conformance | The input variable(s) that are required to allow a simulation to conform to an experiment requirement | ||||||||
| Experimental Conformance Note | CMIP5 | Q | Conformance | Extra information which conveys the scientific intent | ||||||||
| Model Modification Component | CMIP5 | Q | Conformance | The model component(s) that are modified to allow a simulation to conform to an experiment requirement | ||||||||
| Model Modification Type | CMIP5 | Q | Conformance | The form that the modification takes: can be either a parameter change or a code change | Parameter change eg. change the value of the concentration of CO2. Code change eg. apply an algorithm which changes the concentration of CO2. | |||||||
| Model Modification Description | CMIP5 | Q | Conformance | Extra information which conveys the scientific intent | ||||||||
| Conformance | CMIP5 | Q | Conformance | The association of input bindings and/or model modifications with an experiment requirement | ||||||||
| Experiment Requirement | CMIP5 | Q | Conformance | An instruction which governs the experiment setup | ||||||||
| ACTIVITY | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ||||
| Project | Project | X | Q for Component Needed: for Experiment | Basic Properties & Experiment | A campaign, such as a model intercomparison project, that may involve multiple groups and experiments. | SJM: To facilitate the search, a particular simulation will list more than one project (e.g. CCSM, IPCC-AR5). SJM: For an Experiment, the project will just be who is running the broader Experiment (e.g. CMIP5) | submitted & uploaded | |||||
| Rationale | Activity | Rationale | CMIP5 | Q | Experiment | The reason for performing an experiment. | submitted & uploaded | |||||
| EnsembleMembers | Ensemble Members | CMIP3 & CMIP5 | Q | Experiment | A list of other simulations that comprise an ensemble. | submitted & uploaded | ||||||
| Needed: NumberOfEnsembles | Number Of Ensemble Members | CMIP5 | Q | Basic Properties | The number of simulations in an ensemble. | SJM: Gary Strand said to keep this. | submitted & uploaded | |||||
| Needed: EnsembleID | Ensemble | CMIP3 & CMIP5 | NC | Basic Properties | The reference name or number of the ensemble to which a simulation belongs. | SJM: This will be a string identifying the simulation within an ensemble sequence. SJM: The older CMIP3 runs had a long string for this ID. Gary indicated this could be carried over as is but for CMIP CCSM it will most likely be an integer. | submitted & uploaded | |||||
| Needed: SimulatonStartDate | Simulation Start Date | CMIP3 & CMIP5 | Q | Basic Properties | The date in simulated time of the start of a model simulation. | submitted & uploaded | ||||||
| Needed: SimulationEndDate | Simulation End Date | CMIP3 & CMIP5 | Q | Basic Properties | The date in simulated time of the end of a model simulation. | submitted & uploaded | ||||||
| Simulation Status | CMIP3 | Local Runs | Experiment | Indicates whether a simulation is completed, pending, proposed, or running. | submitted & uploaded | |||||||
| ExperimentStartDate | Start Date | CMIP5 | Q | Experiment | The date in simulated time of the start of a model experiment. | submitted & uploaded | ||||||
| ExperimentEndDate | End Date | CMIP5 | Q | Experiment | The date in simulated time of the end of a model experiment. | submitted & uploaded | ||||||
| Needed: PreviousSimulation | Previous Simulation | CMIP3 & CMIP5 | Needed: Q | Basic Properties | A previous simulation is a prequel in model time to the current simulation. The current simulation may be a direct decedent (e.g. same forcing) or may use the previous simulation as initial conditions with a change in present forcing. | SJM: Ticket 313 has been opened to clarify this item. Is it the same as genealogy from the models.py file. | submitted & uploaded | |||||
| SOFTWARE | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | |||
| Needed:License | License | CMIP5 | Q | Technical Properties | Description of the license or conditions under which software is distributed. | SJM: On the 8/13/09 Metafor call, the group agreed to provide license for the upper most components. It currently does not exist under software in the CIM so I have left as needed for now. | submitted & uploaded | |||||
| Needed: Rights | Rights | CMIP3 | local runs | Technical Properties | Description of the distribution and/or access restrictions for a particular piece of software or dataset. | SJM: For older CMIP3 runs, we will have rights (which exists in the database), for CMIP5 runs we will have License. SJM: Gary Strand ok'ed this strategy. | submitted & uploaded | |||||
| Version | Version | CMIP5 | NC | Technical Properties | A specific form or variation of an artifact (i.e. a unit of software or metadata). | version is used throughout the CIM/CV; therefore the definition should encompass more than just software (for example, all CIM documents have a version) | submitted & version | |||||
| PreviousVersionName | Previous Version Name | CMIP5 | Q | Technical Properties | Name of the previous version of a model or model component. | submitted & uploaded | ||||||
| YearReleased | Year Released | CMIP5 | Q | Technical Properties | The year a model or model component was released. | submitted | ||||||
| Needed: CodingLanguage | Coding Language | Curator | Needed:Q | Technical Properties | The computer language in which a unit of software is written. | SJM: ACTION: Add a request for this attribute to ticket 299 | submitted & uploaded | |||||
| ParallelizationType | Software | Parallelization Type | Curator | Needed:Q | Technical Properties | The software package or interface used to distribute data across processors on a parallel computing system. | submitted & uploaded | |||||
| To Suppress(mpm+sv)?: ConnectionType | Software | Connection Type | Curator | Q | Technical Properties | The software package or mechanism used to transfer and transform data between model components. | submitted & uploaded | |||||
| To Suppress(mpm+sv)?: CouplingFlux | Needed: Coupling Flux | CMIP5 | Q | Outputs | The name of the variable transferred between components in a coupled system. | SJM: Flux, Frequency, Regridder, and Target are per flux. We'll need a way to display that. SJM: What we tend to do is list all variables in an export state vice list the variables individually. We'll want to examine this paradigm. | submitted | |||||
| To Suppress(mpm+sv)?: CouplingFluxFrequency | Needed: Coupling Frequency | CMIP5 | Q | Outputs | The interval at which a particular variable is transferred between components in a coupled modeling system. | submitted | ||||||
| To Suppress(mpm+sv)?: CouplingFluxRegridder | Needed: Regridder | CMIP5 | Q | Outputs | ||||||||
| To Suppress(mpm+sv)?: CouplingFluxTarget | Needed: Coupling Target | CMIP5 | Q | Outputs | The component for which a particular coupling flux variable is required. | submitted | ||||||
| Needed: ExportState | Export State | CMIP5 | Outputs | The variables transmitted from a component in a coupled modeling system. | submitted & uploaded | |||||||
| Needed: ImportState | Import State | CMIP5 | Inputs | The variables received from another component in a coupled modeling system. | submitted & uploaded | |||||||
| INPUT CONDITIONS | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | |||
| Needed: Input Name | Input Name | CMIP5 | Q | Inputs | SJM: This is the variable name. There is currently no way to attach a definition to it. | |||||||
| Input Type | CMIP5 | Q | Inputs | SJM: This is not display for each condition, but is used to place each condition under the appropriate accordion (e.g. Initial condition and Boundary conditions) | ||||||||
| Connection::type | Software | Input Technique | CMIP5 | Q | Inputs | The software package or mechanism used to transfer and transform data between model components. | ||||||
| Connection::spatialRegridding:: spatialRegriddingDimension | Input Spatial Regridding Dimension | CMIP5 | Q | Inputs | Dimension of the coupling field (2D/3D) | |||||||
| Connection::spatialRegridding:: spatialRegriddingOrder | Input Spatial Regridding Order | CMIP5 | Q | Inputs | Accuracy of the regridding (1st/2nd) | |||||||
| Connection::spatialRegridding:: conservativeSpatialRegridding | Input Spatial Regridding Conservative | The area integral of the coupling field is conserved between the source and the target grid. | ||||||||||
| Connection::timeTransformation:: timeAverage | Input Time Transformation Average | CMIP5 | Q | Inputs | The field is averaged over a certain period before or after spatial regridding | |||||||
| Connection::timeTransformation:: timeAccumulation | Input Time Transformation Accumulation | The field is summed over a certain period before or after spatial regridding | ||||||||||
| Connection::connectionSource | Input Dataset OR Input Source Component | The source (file or model component) of the coupling field | ||||||||||
| Connection::connectionTarget | N/A | The target (file or model component) of the coupling field | ||||||||||
| To suppress(mpm+sv)?: InputDataset | Input Dataset | CMIP5 | Q | Inputs | ||||||||
| To suppress(mpm+sv)?: InputSourceComponent | Input Source Component | CMIP5 | Q | Inputs | ||||||||
| HARDWARE | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | |||
| ProcessorType | Processor | Curator | Q | Technical Properties | The type of computer chip used in a particular computer platform. | submitted & uploaded | ||||||
| Vendor | Software | Platform | Curator | Q | Technical Properties | The brand name of a computer system. | submitted & uploaded | |||||
| OperatingSystem | Software | Operating System | Curator | Q | Technical Properties | The software that is responsible for the management and coordination of activities and the sharing of resources of a computer. | submitted & uploaded | |||||
| Compiler | Software | Compiler | Curator | Q | Technical Properties | The brand of the software that takes source code and turns it into an executable. | submitted & uploaded | |||||
| CompilerVersion | Software | Compiler Version | Curator | Q | Technical Properties | The specific configuration value of the software used to take source code and turn it into executable code. | submitted & uploaded | |||||
| (Machine)Name | Software | Machine Name | CMIP3 & CIM | Q | Technical Properties | The name given to a computer by its system administrators. This is not the brand name of the system. | submitted & uploaded | |||||
| MaxProcessors | Max Processors | CMIP5 | Q | Technical Properties | The highest number of computer chips on a computer system. | submitted & uploaded | ||||||
| CoresPerProcessor | Cores per Processor | CMIP5 | Q | Technical Properties | The number of sub-divided elements or mini-chips on a computer chip. | submitted & uploaded | ||||||
| HardwareType | Hardware Type | CMIP5 | Q | Technical Properties | The type of computer system. (e.g. vector, parallel, cluster, etc.) | submitted & uploaded | ||||||
| InterconnectType | Interconnect Type | CMIP5 | Q | Technical Properties | The technology used to associate each node in a supercomputer with every other node. | submitted & uploaded | ||||||
| Configuration Files | Curator | local runs | Inputs | The collection of files used to create a model simulation. May include scripts, name lists etc. | submitted & uploaded | |||||||
| Input Datasets | Curator | local runs | Inputs | External data files used by a model simulation. May include initial conditions, boundary conditions, or restart files. | submitted & uploaded | |||||||
| GRID PROPERTIES | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ||||
| Grid | GridSpec | CMIP5 | gridspec tool | Grids | The specification of a grid used in a geoscience model. | Phil has reviewed the grid definitions. Those he and SJM agree on are listed as approved | approved & uploaded | |||||
| Mosaic | Grid | Mosaic | CMIP5 | gridspec tool | Grids | A collection of grid tiles. | approved & uploaded | |||||
| Tile | Grid | Tile | CMIP5 | gridspec tool | Grids | A portion of a grid that is separately discretized. | approved & uploaded | |||||
| GridType | Grid | Grid Type | X | CMIP5 | gridspec tool | Grids | A text description of the grid that uses common terminology. | submitted & uploaded | ||||
| IsCongruent | Grid | Congruent Tiles | CMIP5 | gridspec tool | Grids | Indicates whether or not all the tiles contained within a grid mosaic are of the same size and shape. | approved & uploaded | |||||
| Number of Grid Tiles | CMIP5 | gridspec tool | Grids | The number of separately discretized regions within the grid. | approved | |||||||
| IsRegular | Grid | Regular | CMIP5 | gridspec tool | Grids | Indicates whether or not the horizontal coordinates of the grid can be defined using 1D arrays (vectors). This means that grid node locations are defined by the cartesian product of the X/Lon and Y/Lat coordinate vectors. It also means that grid cells are logically rectangular (they may also be physically rectangular in the case of projected coordinates). | approved & uploaded | |||||
| IsUniform | Grid | Uniform | CMIP5 | gridspec tool | Grids | Indicates whether or not the horizontal coordinates of a grid have fixed offsets in the X and Y directions. If the offset is the same in both directions then the grid is logically square, otherwise it is logically rectangular. | approved & uploaded | |||||
| IsConformal | Grid | Conformal | CMIP5 | gridspec tool | Grids | Indicates if the grid tile is angle-preserving. If so, angles measured on the grid are equal to the equivalent angles on the Earth. | approved & uploaded | |||||
| DimOrder | Grid | Dimension Order | gridspec tool | Grids | The order in which latitude and longitude appear within the two dimensional grid array. | approved & uploaded | ||||||
| NY | Grid | NY | CMIP5 | gridspec tool | Grids | Specifies the length of the Y, or latitude, dimension of the grid tile. | approved & uploaded | |||||
| NX | Grid | NX | CMIP5 | gridspec tool | Grids | Specifies the length of the X, or longitude, dimension of the grid tile. | approved & uploaded | |||||
| GeometryType | Grid | Geometry Type | CMIP5 | gridspec tool | Grids | Indicates the geometric figure used to approximate the shape of the Earth, e.g. "sphere". | approved & uploaded | |||||
| DiscretizationType | Grid | Discretization Type | CMIP5 | gridspec tool | Grids | Specifies the method by which a two-dimensional coordinate system is sampled to form a computational grid. | in-progress & uploaded | |||||
| NorthPoleLocation | Grid | North Pole Location | CMIP5 | gridspec tool | Grids | Defines the lat-long position of the 'north pole' used by the grid tile in the case of rotated/displaced pole grids. | approved & uploaded | |||||
| CoordinatePoles | Grid | Coordinate Poles | CMIP5 | gridspec tool | Grids | Specifies the lat-long position of any coordinate poles (in the mathematical sense) that form part of the definition of a grid tile. | approved & uploaded | |||||
| SCIENTIFIC PROPERTIES | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ||||
| Forcing Type | X | CMIP3 | Scientific Properties | The category of forcing used to drive a model component (e.g. wind, wave, volcanism). | submitted & uploaded | |||||||
| Forcing Value | CMIP3 & CMIP5 | Scientific Properties | The specific value or constant set for a particular forcing type. Forcing types may also be defined by entire fields. That information is captured in a component's list of input datasets. | SJM: Gary Strand indicated that this will exist for CMIP5 as well. SJM: He indicated that it may be a string that defines a constant, describes an equation, points to a file etc, so it needs to be a string. | submitted & uploaded | |||||||
| Needed: InitializationMethod | Initialization Method | CMIP5 | NC | Scientific Properties | The means by which a geoscience simulation is started. | submitted & uploaded | ||||||
| Needed: PhysicsVersion | Needed: Physics Version | CMIP5 | NC | Scientific Properties | ||||||||
| CalendarType | Activity | Calendar Type | Curator | Needed:Q | Scientific Properties | The type of calendar used in a simulation. | submitted & uploaded | |||||
| DYNAMICAL CORE PROPERTIES | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ***** | ||||
| Equations of Motion | dycore workshop | Scientific Properties | The time dependent ordinary and partial differential equations that describe behavior of a geophysical system. They form the basis for the numerical discretization of a geoscience model. | in-progress & uploaded | ||||||||
| Advection Scheme | dycore workshop | Scientific Properties | The algorithm used to solve the equations that represent the transport mechanism of a substance or a conserved property within a moving fluid. | in-progress & uploaded | ||||||||
| Conservation Type | dycore workshop | Scientific Properties | The physical characteristics of the equations of motion that are conserved by the numerical discretization. | submitted & uploaded | ||||||||
| Conservation Fixer | dycore workshop | Scientific Properties | Any physical quantities that are formally conserved by the continuous equations of motion and restored to their initial value at periodic intervals. | submitted & uploaded | ||||||||
| Time Stepping | dycore workshop | Scientific Properties | Part of the solver that moves the solution of the continuous equations of motion forward in time. A solver is an algorithm that computes a numerical solution to a time-dependent ordinary or partial differential equation required by computer simulations of physical processes. | submitted & uploaded | ||||||||
| Numerical Method | dycore workshop | Scientific Properties | The means by which continuous operators are represented on a finite set of points. In a scientific model, numerical methods are used to discretize the continuous equations of motion. | in-progress & uploaded | ||||||||
| Spatial Approximation | dycore workshop | Scientific Properties | The estimate of the spatial portion of the continuous equations of motion. It is used simplify the overall solutions to those equations. | in-progress & uploaded | ||||||||
| Temporal Approximation | dycore workshop | Scientific Properties | A description of how time is descretized within an algorithm that computes a numerical solution to a time-dependent ordinary or partial differential equation required by computer simulations of physical processes. | in-progress & uploaded | ||||||||
| Inherent Spatial Diffusion | dycore workshop | Scientific Properties | Diffusion terms that are added to the equations of motion. | in-progress & uploaded | ||||||||
| Implicit Diffusion | dycore workshop | Scientific Properties | Diffusion that typically dampens grid scale oscillations through the numerical method rather than through terms added to equations of motion (explicit diffusion). | in-progress & uploaded | ||||||||
| Explicit Spatial Filter | dycore workshop | Scientific Properties | A posteriori dampening of waves on an entire gridded field at specified intervals. This is dampening not implemented in either Implicit or Explicit Diffusion. | in-progress & uploaded | ||||||||
| Diagnostic Variable | dycore workshop | Scientific Properties | Variables that are derived from other variables. | in-progress & uploaded | ||||||||
| Prognostic Variable | dycore workshop | Scientific Properties | Variables that are directly calculated by the equations of motion. | in-progress & uploaded | ||||||||
| Projection | dycore workshop | Scientific Properties | Any projection used for the discretization of the equations of motion. For example, cubed-sphere grids can use gnomonic (equiangular) or gnomonic (equal-distance along cube edges). Also, planar projections used in some icosahedral grid models etc. | in-progress & uploaded | ||||||||
| Horizontal Resolution | dycore workshop | Scientific Properties | The number of points within the horizontal domain of a model or grid. | in-progress & uploaded | ||||||||
| Horizontal Staggering | dycore workshop | Scientific Properties | Placement of model field data relative to the center point of a grid cell in the horizontal dimension. | submitted & uploaded | ||||||||
| Time Step Size (Example) | dycore workshop | Scientific Properties | Time-step size in seconds used moving the solver forward. This will vary by horizontal resolution. | in-progress & uploaded | ||||||||
| Vertical Coordinate | dycore workshop | Scientific Properties | The system that describes the vertical discretization of a geophysical model in terms of given point’s radial distance from the surface of the earth. | in-progress & uploaded | ||||||||
| Vertical Resolution | dycore workshop | Scientific Properties | The number of points within the vertical domain of a model or grid. | submitted & uploaded | ||||||||
| Vertical Staggering | dycore workshop | Scientific Properties | Placement of model field data relative to the center point of a grid cell in the vertical dimension. | submitted & uploaded | ||||||||
| Location at Vertical Top | dycore workshop | Scientific Properties | The value the vertical coordinate at the top of a geophysical model. | in-progress & uploaded | ||||||||
| Tracer Transport | dycore workshop | Scientific Properties | The algorithm used to solve the equations that represent the transport mechanism of tracers within a moving fluid. | in-progress & uploaded | ||||||||
| Tracer Temporal Approximation | dycore workshop | Scientific Properties | A description of how time is descretized within the algorithm that computes the tracer transport solver. | in-progress & uploaded | ||||||||
| Tracer Conservation Type | dycore workshop | Scientific Properties | Physical quantities that are inherently conserved by the numerical tracer transport scheme. | in-progress & uploaded | ||||||||
| Tracer Fixer | dycore workshop | Scientific Properties | Any physical quantities that are formally conserved by the continuous tracer transport equation and restored to their initial values. | in-progress & uploaded | ||||||||
| Tracer Spatial Approximation | dycore workshop | Scientific Properties | The estimate of the spatial portion of the tracer transport equation. | in-progress & uploaded | ||||||||
| Tracer Spatial Filter | dycore workshop | Scientific Properties | Any explicit or implicit diffusion or spatial filtering applied in the tracer transport solver. | in-progress & uploaded | ||||||||
| Tracer Temporal Filter | dycore workshop | Scientific Properties | Any filters applied to the time-stepping method to remove spurious waves in the time-stepping method for tracers. | in-progress & uploaded | ||||||||
| Tracer Time Stepping | dycore workshop | Scientific Properties | Part of the solver that moves the tracer transport equation forward in time. A solver is an algorithm that computes a numerical solution to a time-dependent ordinary or partial differential equation required by computer simulations of physical processes. | submitted & uploaded | ||||||||
| Tracer Time Step | dycore workshop | Scientific Properties | Time-step size in seconds used moving the tracer transport solver forward. This will vary by horizontal resolution. | submitted & uploaded | ||||||||
| Tracer Advection Scheme | dycore workshop | Scientific Properties | The algorithm used to solve the equations that represent the tracer transport mechanism of a substance or a conserved property within a moving fluid. | submitted & uploaded |
- note to self: incorporate the terms found on this page http://metaforclimate.eu/trac/wiki/WP2/ControlledVocabulariesList then modify that page to point here.
