cPlans versus DivePlans
When working on a project, it is a best practice to build a consistent environment for data displays and analysis. Version 7.x gives you access to both cPlans and DivePlans, so it is important to know what each of these file types are and what is the best use for each.
cPlans and DivePlans defined
- A cPlan is a Spectre file type that defines input sources and data calculations for cBase data. cPlans describe merges, calcs, time series, and lookups to be done when opening Spectre cBase data.
- A DivePlan is a Diver Platform file type that determines the presentation of DI model and cBase data to Diver Platform clients. DivePlans describe merges, calcs, time series, named groups, and lookups to be done when opening classic Model data.
- In ProDiver, you can use DivePlans to control what is in the console as well as the dive window. For example, you can use DivePlans to reorder dimensions and group them into categories in the console, to define named groups, and to select columns for display in the dive window. This functionality extends to cPlans, so ProDiver users can see cBase data in the manner that they expect. In other words, DivePlans for 7.x can include Models, cBases, and cPlans.
cPlans and DivePlans best usage
cPlans are designed to be a developer tool. Developers can use the Workbench editor to name cBases or cPlans to merge, script expressions to add calculations, specify time series, and code lookups to pull in additional data.
While developers can create and edit DivePlans by using the DiveMaster tool in Workbench, end-users working in ProDiver can also alter DivePlans. You can build in separation between developers and end-users:
- Use cPlans for work that you want to centralize and control
- Use Project access to control the cPlans and ensure data integrity
- Allow power users to control the DivePlans
- Allow power users to use ProDiver to refine the DivePlans to present the data as needed
See also: