The Data module in Cosmic Frog is where all model inputs and outputs live. Here you can enter, import, export, review, filter, aggregate, edit, and delete data.
The data contained in the Data module is essential to a Cosmic Frog model as the input data is used when the model is run and therefore determines the outcomes. Additionally, all other modules build upon it:
A Cosmic Frog model is a Postgres database under the hood. Model databases use a specific schema called “Anura” that Cosmic Frog understands and can use with its multiple engines. You can learn more about Anura and the modeling schema in these articles on Anura Inputs and Anura Outputs.
After the Quick Start section, this documentation starts with an overview of the components of the Data module and then gets into the details of the technology filter, tables list, and table grid. Multiple options for data transfer, how to filter a table, and additional menus and context menus are covered next. The document wraps up with an overview of available data validation tools, tips on configuring the data module based on your role, and best practices.
Follow these steps to get your first data into a model:
To open the Data module within Cosmic Frog, click on the Module menu’s hamburger icon, and select Data from the list:

The layout of the Data module is as follows:

The Technology Filter, in the top toolbar, controls which tables and columns are shown based on the technologies you are using. Each technology is run by its own engine and has its own icon in the filter:

Example in the next 2 screenshots: with all engines enabled, the Facilities table shows both Initial State (used only by Neo) and Fixed Operating Cost (used by Neo and Triad). Disable everything except Throg and Dendro, and both columns disappear — neither engine uses them.


As shown in the overview above, the list with tables that are present in the model is located on the left-hand side:

Note that right-clicking on a table brings up a context menu with many options from the File, Grid, and Filter menus. This context menu is covered in the Table Context Menu subsection.
The following configuration options are available at the top of the tables list:

The Visibility Options when opened for input tables are shown here:

In addition to the visibility options listed under bullets 2 and 3 above, there is an additional output table-specific one:
This table shows which of the visibility options are available for which table type(s):

Next, we have a look at the scenario indicators mentioned under bullet 2b above:

The Technology Filter and Visibility Options both control which tables and columns are shown, and they combine — only tables/columns that satisfy every active filter appear.
For example, with only Neo enabled and Show Required Columns Only, Show Populated Tables Only, and Show Populated Columns Only all ON: the tables list shows only tables that are both required for Neo and populated, and each grid shows only columns that are both required for Neo and populated. Because these filters combine, a table or column that is genuinely required for Neo could still be hidden if it is not populated yet — worth remembering when something seems to be missing.
For the recommended filter settings at each stage of building a model, see Build in Stages under Best Practices.
If you cannot find a table or column you expect to see, clear everything that could be hiding it:
When tables are opened, they are shown in the grid in the center part of the Cosmic Frog UI. This screenshot gives an overview of the grid; we will cover more details of each part in later sections with more screenshots:

As seen in the previous screenshot, the tabs of the tables that are open can be seen at the top of the grid:

To close tables:

We can learn a lot about a column by hovering over its name to bring up a tooltip:

From top to bottom the tooltip, shown for Unit Price on the Products table, contains:
When looking at the column headers, we see:

Resizing columns: when hovering over the vertical bar, the cursor changes to 2 arrows pointing away from each other. Now you can drag the column separator to resize the columns; drop it when the desired width is reached:

Re-ordering columns: you can drag and drop columns to change their order in the grid. The move symbol will be showing when you are moving the column around:

Freezing panes: you can pin 1 or multiple columns to the left or right of the grid, so they stay visible when scrolling. Drag and drop the column all the way left or right, until the pin icon appears next to the column name, then drop the column:

To unfreeze/unpin: drag and drop the column until the pin icon disappears.
Sorting by individual columns: clicking on a column once will sort it in ascending order and an arrow pointing upwards will appear next to the column name. Clicking on it again will sort it in descending order, and the arrow will now point downwards. Clicking a third time will remove the sort and the arrow.
Sorting by multiple columns: click once or twice on the first column to sort by, then holding Ctrl+Shift down, click once or twice on the second column to sort by, etc. The sorted columns will again show arrows pointing up or down indicating the sort order, and now they will also have a number which indicates the order in which the columns were sorted:

Options from the context menu:

From top to bottom:
When selecting Choose Columns from the context menu, the following form comes up:

When selecting Bulk Update this Column from a column’s context menu, the following pane opens on the right-hand side:

For more than a few records, use one of these bulk options instead of manual entry (covered below):
Bulk Import/Export from/to Excel and CSV Files
This can be done via Cosmic Frog’s File menu. See the details on how to use these options in this Cosmic Frog – Importing and Exporting Data Help Center article.

Ada
Ada is Optilogic’s agentic AI. Use it on the next generation Optilogic platform or through AI agents such as Claude, ChatGPT, Copilot, Mistral, or Grok via the Optilogic MCP Connector. For example, you can attach raw data and ask Ada to populate a model’s input tables.
DataStar
DataStar is Optilogic’s AI-powered data product in which you can build repeatable workflows which take care of importing, cleansing, and transforming data into the Anura format for use in Cosmic Frog models. Automated output analysis workflows can be set up too. Learn more about DataStar in the Navigating DataStar section on the Help Center.
Using Postgres Queries
A Cosmic Frog model is a Postgres database under the hood, which uses the Anura schema. You can use SQL queries to transform their raw data into the Anura schema and populate a model’s input tables in this way. One option is to use the SQL Editor application available on the Optilogic platform.
Similarly, queries can be used to examine, summarize, and aggregate results of scenario runs which are present in a model’s output tables.
This section covers data entry, editing, and removal done purely by hand; the Grid Menu section further down contains several options to speed some of these actions up.
Note that following sections only apply to input and custom tables, since output tables are read-only. The only exception is the Copying Data section, which also applies to output tables.
Entering Data Manually
In an open input table, the top record which has a darker color can be used to enter records manually:

For columns where the value needs to be one of a specific list of values, a drop-down list will automatically appear when you move the cursor to the cell. You can use the up/down arrows to choose the desired value and use Tab to select it and move to the next cell or Enter to select it and commit the record.

The committed record appears in the grid below the data entry row, which clears for the next record:

When starting to type in a column that needs to have a value that exists in another table, the options containing the typed text will automatically be populated in a dynamic drop-down list – it is updated as you type more characters. This will contain entity names (e.g. Facility Name or Customer Name), group names (see explanation in the Grid Menu section), and table filter names (see the Named Filters in Cosmic Frog article) based on the allowed entity/entities for the column.

Pasting Data
Single cell or single row:
Data for multiple columns and/or rows can also be pasted from for example an Excel file if it is in the right format, including the order of the columns:
Note that pasting multiple records as new records (i.e. to append) in an already populated table does not work. In general, using the Import/Export options under the File menu is recommended over manually pasting in more than one record as it is less error-prone.
Editing Data
To edit data, you can go into the cell to be edited and manually change the value or use the steps from the previous section to update the data by pasting the new values in from another source.
If you are changing the values of fields that can be used by other input tables, you will be prompted if you want to update this value in any dependent tables too. Choose Continue with Cascade if so; otherwise choose Change Master Only.

Copying Data
Copying data is simply done by selecting the cells to be copied and using Ctrl+C. Options to include headers when copying are available from the Grid menu and the right-click context menu, see the Grid Menu section which follows this one.

Deleting Data
Options for deleting cell contents and entire rows include:

Filter a table on one or more columns to show a subset of its records. Filters can be saved as Named Filters for reuse in the same table, as dynamic groups, and as conditions in scenario items and maps (see Named Filters in Cosmic Frog). This section covers building and applying filters.
When you click on the filter icon to the right of the column name, the following filter configuration form comes up:

The next 2 screenshots show the filtering condition options for text-based columns (top) and numeric columns (bottom):


Once a filter condition has been entered, Begins with “Mich” in the screenshot below, the form automatically adds fields to allow you to add another filtering condition. You can choose if these conditions should be treated as AND or OR. Once one is chosen, it will be applied for all following conditions too.
In the screenshot below, the filter is on the Region column in the Customers table. The filter reads “Region Begins with Mich OR Region Begins with Oh”. Since the values of the Region column are the names of US States, the filter should result in showing records where the region is either Michigan or Ohio.

After applying the filter, the Customers table looks as follows:

Filters can be applied to multiple columns in a table; these work as an AND statement: only records that match all filters will be shown. In the next 2 screenshots the filtered table from the previous screenshot is used, and an additional filter is added to the Customer Name column: Customer Name Contains “CZ2” or Customer Name Contains “CZ3”:

After applying the filter, we see the same indicators that filters have been applied, plus the resulting records:

What we have discussed above uses what is called the Default filter. Besides this filter, we can instead also use a Set filter, where values can be enabled and disabled by checkboxes – especially useful for cases where there are several distinct values present. The last option in a column’s context menu allows you to switch to the Set filter:

Now, when clicking on the filter icon next to the column’s name (Product Name on the Customer Demand table here), the following filter form comes up:

A convenient way to quickly set up filters on multiple columns in a table is to use the Filters fold-out pane on the right-hand side of a table:

Clicking on the Filters pane again folds it back in. After applying the filters shown in the previous screenshot, the Customer Demand table looks as follows. The same indicators that filters are present can be seen and we do indeed only see records for Rockets with quantities of at least 1,000:

Finally, we have a look at the Filter menu and its options:

Next, we will cover the options available under the Grid menu. Please note that:
When clicking on the Grid menu, the following options are shown:

When selecting Table from the Grid menu, a sub-menu with 5 options folds out:

From top to bottom:
Choosing the Add Custom Column option brings up the following pane to the right of the grid:

When selecting Rows from the Grid menu, a sub-menu with 4 options folds out:

From top to bottom:
When selecting Groups from the Grid menu, a sub-menu with 2 options folds out:

From top to bottom:
This screenshot shows Create Group pane that opens when choosing the Create Group option:

When selecting Aggregation from the Grid menu, a sub-menu with 4 options folds out:

Aggregation shows the minimum (Min), average (Avg), summed (Sum), or maximum (Max) values of each numeric column in the (filtered) records at the bottom of the grid
This screenshot shows an example of a filtered grid that has the “sum columns” aggregation option turned on:

Right-clicking the grid brings up a context menu with most of the options from the Grid menu (covered in the previous section). The differences are highlighted in the next screenshot:

The next 3 screenshots show how Duplicate Selected Rows works. It is selected via the grid’s right-click context menu here but works the same when chosen from the Grid menu. Our aim is to duplicate 5 records on the Customer Demand table.

This brings up the Duplicate pane to the right of the grid:

The resulting duplicated rows are shown in this screenshot:

The Geocode button is only available on the Customers, Facilities, and Suppliers input tables. Based on location information, such as Address, City, Region, and Country entered into these tables, the geocoding provider looks up a location’s latitude and longitude and saves those in the table. These can be used to draw locations in the correct location on a map and for distance calculations.
Consider the following Customers table:

By default, the MapBox geoprovider will be used to look up coordinates. You are prompted to indicate if you only want to get results where MapBox finds a 100% match. When this option is left unchecked, the best match (closest to 100%) will be used in case a 100% match is not found:

Once the geocoding is finished, the latitude and longitude columns of these records are populated:

Note that Geoproviders other than MapBox can be configured to be used for geocoding and distance lookups, see the Using Alternate Geocoding Providers Help Center article.
Right-clicking on a table in the Tables list brings up a context menu which contains the options we have already seen and covered above from the File, Grid, and Filter menus that are applicable to the table. Again, multiple options that do not apply to output tables are automatically greyed out in this context menu.

From top to bottom:
There are several tools within Cosmic Frog which can help find problems with the model’s data and overall construction. The table below gives an overview of how these tools compare to each other to help you choose the most suitable one for your situation:
These Help Center articles contain more details on some of these tools:
The Data module has many configuration options as covered above. Following suggested setups are starting points by role.
Model Builder (constructing a new model)
Data Analyst / Data Engineer (loading and cleaning external data)
Scenario Modeler (testing what-if changes)
Reviewer / Business Stakeholder (checking outputs, not building)
A few habits make working in the Data module faster and your models easier for others (or future you) to pick up.
Build in stages, not all at once
This avoids the common trap of populating dozens of tables before confirming the model even runs.
Use Status and Notes fields deliberately
Most input tables include Status and Notes columns. Rather than deleting records you might need later, set Status = Exclude and tag them with a Notes value (e.g., a scenario name or a data source). This keeps your baseline data intact while letting you filter, bulk-update, or scenario-toggle those records later. See the Scenarios article for how this pattern powers scenario items.
Save filters as Named Filters, do not recreate them
If you find yourself typing the same filter condition more than once — on a table, a scenario item, or a map layer — save it as a Named Filter instead. It is pre-validated, reusable across the model, and shows a record-count preview so you can confirm it is selecting what you expect. See Named Filters in Cosmic Frog.
Validate early, not just before a run
Do not wait until a model fails to run to check your data. Run the Integrity Checker (Grid menu) after any significant data load or edit, not only at the end. Catching an issue right after an import is far faster to fix than tracing it back after a failed solve. See Cosmic Frog's Integrity Checker and the Data Validation Tools section above for guidance on choosing the right tool.
Prefer bulk tools over manual entry for anything beyond a few rows
Pasting or typing in more than a handful of records is error-prone and does not scale. Use File > Import for structured Excel/CSV files, Ada or DataStar for messier source data and repeatable workflows, or a Postgres query via the SQL Editor when you need to transform data into the Anura schema.
Use custom columns to stage data, not to feed the model
Custom columns are a convenient place to keep source values, growth factors, or notes external to the model — but remember they are not read by any engine and cannot be used in scenario items. If a value needs to affect a model run, it needs to live in a real Anura column, even if a custom column feeds into it via a scenario item's Actions field.
Happy modeling! As always, please contact our Support team at support@optilogic.com for any questions or feedback.
The Data module in Cosmic Frog is where all model inputs and outputs live. Here you can enter, import, export, review, filter, aggregate, edit, and delete data.
The data contained in the Data module is essential to a Cosmic Frog model as the input data is used when the model is run and therefore determines the outcomes. Additionally, all other modules build upon it:
A Cosmic Frog model is a Postgres database under the hood. Model databases use a specific schema called “Anura” that Cosmic Frog understands and can use with its multiple engines. You can learn more about Anura and the modeling schema in these articles on Anura Inputs and Anura Outputs.
After the Quick Start section, this documentation starts with an overview of the components of the Data module and then gets into the details of the technology filter, tables list, and table grid. Multiple options for data transfer, how to filter a table, and additional menus and context menus are covered next. The document wraps up with an overview of available data validation tools, tips on configuring the data module based on your role, and best practices.
Follow these steps to get your first data into a model:
To open the Data module within Cosmic Frog, click on the Module menu’s hamburger icon, and select Data from the list:

The layout of the Data module is as follows:

The Technology Filter, in the top toolbar, controls which tables and columns are shown based on the technologies you are using. Each technology is run by its own engine and has its own icon in the filter:

Example in the next 2 screenshots: with all engines enabled, the Facilities table shows both Initial State (used only by Neo) and Fixed Operating Cost (used by Neo and Triad). Disable everything except Throg and Dendro, and both columns disappear — neither engine uses them.


As shown in the overview above, the list with tables that are present in the model is located on the left-hand side:

Note that right-clicking on a table brings up a context menu with many options from the File, Grid, and Filter menus. This context menu is covered in the Table Context Menu subsection.
The following configuration options are available at the top of the tables list:

The Visibility Options when opened for input tables are shown here:

In addition to the visibility options listed under bullets 2 and 3 above, there is an additional output table-specific one:
This table shows which of the visibility options are available for which table type(s):

Next, we have a look at the scenario indicators mentioned under bullet 2b above:

The Technology Filter and Visibility Options both control which tables and columns are shown, and they combine — only tables/columns that satisfy every active filter appear.
For example, with only Neo enabled and Show Required Columns Only, Show Populated Tables Only, and Show Populated Columns Only all ON: the tables list shows only tables that are both required for Neo and populated, and each grid shows only columns that are both required for Neo and populated. Because these filters combine, a table or column that is genuinely required for Neo could still be hidden if it is not populated yet — worth remembering when something seems to be missing.
For the recommended filter settings at each stage of building a model, see Build in Stages under Best Practices.
If you cannot find a table or column you expect to see, clear everything that could be hiding it:
When tables are opened, they are shown in the grid in the center part of the Cosmic Frog UI. This screenshot gives an overview of the grid; we will cover more details of each part in later sections with more screenshots:

As seen in the previous screenshot, the tabs of the tables that are open can be seen at the top of the grid:

To close tables:

We can learn a lot about a column by hovering over its name to bring up a tooltip:

From top to bottom the tooltip, shown for Unit Price on the Products table, contains:
When looking at the column headers, we see:

Resizing columns: when hovering over the vertical bar, the cursor changes to 2 arrows pointing away from each other. Now you can drag the column separator to resize the columns; drop it when the desired width is reached:

Re-ordering columns: you can drag and drop columns to change their order in the grid. The move symbol will be showing when you are moving the column around:

Freezing panes: you can pin 1 or multiple columns to the left or right of the grid, so they stay visible when scrolling. Drag and drop the column all the way left or right, until the pin icon appears next to the column name, then drop the column:

To unfreeze/unpin: drag and drop the column until the pin icon disappears.
Sorting by individual columns: clicking on a column once will sort it in ascending order and an arrow pointing upwards will appear next to the column name. Clicking on it again will sort it in descending order, and the arrow will now point downwards. Clicking a third time will remove the sort and the arrow.
Sorting by multiple columns: click once or twice on the first column to sort by, then holding Ctrl+Shift down, click once or twice on the second column to sort by, etc. The sorted columns will again show arrows pointing up or down indicating the sort order, and now they will also have a number which indicates the order in which the columns were sorted:

Options from the context menu:

From top to bottom:
When selecting Choose Columns from the context menu, the following form comes up:

When selecting Bulk Update this Column from a column’s context menu, the following pane opens on the right-hand side:

For more than a few records, use one of these bulk options instead of manual entry (covered below):
Bulk Import/Export from/to Excel and CSV Files
This can be done via Cosmic Frog’s File menu. See the details on how to use these options in this Cosmic Frog – Importing and Exporting Data Help Center article.

Ada
Ada is Optilogic’s agentic AI. Use it on the next generation Optilogic platform or through AI agents such as Claude, ChatGPT, Copilot, Mistral, or Grok via the Optilogic MCP Connector. For example, you can attach raw data and ask Ada to populate a model’s input tables.
DataStar
DataStar is Optilogic’s AI-powered data product in which you can build repeatable workflows which take care of importing, cleansing, and transforming data into the Anura format for use in Cosmic Frog models. Automated output analysis workflows can be set up too. Learn more about DataStar in the Navigating DataStar section on the Help Center.
Using Postgres Queries
A Cosmic Frog model is a Postgres database under the hood, which uses the Anura schema. You can use SQL queries to transform their raw data into the Anura schema and populate a model’s input tables in this way. One option is to use the SQL Editor application available on the Optilogic platform.
Similarly, queries can be used to examine, summarize, and aggregate results of scenario runs which are present in a model’s output tables.
This section covers data entry, editing, and removal done purely by hand; the Grid Menu section further down contains several options to speed some of these actions up.
Note that following sections only apply to input and custom tables, since output tables are read-only. The only exception is the Copying Data section, which also applies to output tables.
Entering Data Manually
In an open input table, the top record which has a darker color can be used to enter records manually:

For columns where the value needs to be one of a specific list of values, a drop-down list will automatically appear when you move the cursor to the cell. You can use the up/down arrows to choose the desired value and use Tab to select it and move to the next cell or Enter to select it and commit the record.

The committed record appears in the grid below the data entry row, which clears for the next record:

When starting to type in a column that needs to have a value that exists in another table, the options containing the typed text will automatically be populated in a dynamic drop-down list – it is updated as you type more characters. This will contain entity names (e.g. Facility Name or Customer Name), group names (see explanation in the Grid Menu section), and table filter names (see the Named Filters in Cosmic Frog article) based on the allowed entity/entities for the column.

Pasting Data
Single cell or single row:
Data for multiple columns and/or rows can also be pasted from for example an Excel file if it is in the right format, including the order of the columns:
Note that pasting multiple records as new records (i.e. to append) in an already populated table does not work. In general, using the Import/Export options under the File menu is recommended over manually pasting in more than one record as it is less error-prone.
Editing Data
To edit data, you can go into the cell to be edited and manually change the value or use the steps from the previous section to update the data by pasting the new values in from another source.
If you are changing the values of fields that can be used by other input tables, you will be prompted if you want to update this value in any dependent tables too. Choose Continue with Cascade if so; otherwise choose Change Master Only.

Copying Data
Copying data is simply done by selecting the cells to be copied and using Ctrl+C. Options to include headers when copying are available from the Grid menu and the right-click context menu, see the Grid Menu section which follows this one.

Deleting Data
Options for deleting cell contents and entire rows include:

Filter a table on one or more columns to show a subset of its records. Filters can be saved as Named Filters for reuse in the same table, as dynamic groups, and as conditions in scenario items and maps (see Named Filters in Cosmic Frog). This section covers building and applying filters.
When you click on the filter icon to the right of the column name, the following filter configuration form comes up:

The next 2 screenshots show the filtering condition options for text-based columns (top) and numeric columns (bottom):


Once a filter condition has been entered, Begins with “Mich” in the screenshot below, the form automatically adds fields to allow you to add another filtering condition. You can choose if these conditions should be treated as AND or OR. Once one is chosen, it will be applied for all following conditions too.
In the screenshot below, the filter is on the Region column in the Customers table. The filter reads “Region Begins with Mich OR Region Begins with Oh”. Since the values of the Region column are the names of US States, the filter should result in showing records where the region is either Michigan or Ohio.

After applying the filter, the Customers table looks as follows:

Filters can be applied to multiple columns in a table; these work as an AND statement: only records that match all filters will be shown. In the next 2 screenshots the filtered table from the previous screenshot is used, and an additional filter is added to the Customer Name column: Customer Name Contains “CZ2” or Customer Name Contains “CZ3”:

After applying the filter, we see the same indicators that filters have been applied, plus the resulting records:

What we have discussed above uses what is called the Default filter. Besides this filter, we can instead also use a Set filter, where values can be enabled and disabled by checkboxes – especially useful for cases where there are several distinct values present. The last option in a column’s context menu allows you to switch to the Set filter:

Now, when clicking on the filter icon next to the column’s name (Product Name on the Customer Demand table here), the following filter form comes up:

A convenient way to quickly set up filters on multiple columns in a table is to use the Filters fold-out pane on the right-hand side of a table:

Clicking on the Filters pane again folds it back in. After applying the filters shown in the previous screenshot, the Customer Demand table looks as follows. The same indicators that filters are present can be seen and we do indeed only see records for Rockets with quantities of at least 1,000:

Finally, we have a look at the Filter menu and its options:

Next, we will cover the options available under the Grid menu. Please note that:
When clicking on the Grid menu, the following options are shown:

When selecting Table from the Grid menu, a sub-menu with 5 options folds out:

From top to bottom:
Choosing the Add Custom Column option brings up the following pane to the right of the grid:

When selecting Rows from the Grid menu, a sub-menu with 4 options folds out:

From top to bottom:
When selecting Groups from the Grid menu, a sub-menu with 2 options folds out:

From top to bottom:
This screenshot shows Create Group pane that opens when choosing the Create Group option:

When selecting Aggregation from the Grid menu, a sub-menu with 4 options folds out:

Aggregation shows the minimum (Min), average (Avg), summed (Sum), or maximum (Max) values of each numeric column in the (filtered) records at the bottom of the grid
This screenshot shows an example of a filtered grid that has the “sum columns” aggregation option turned on:

Right-clicking the grid brings up a context menu with most of the options from the Grid menu (covered in the previous section). The differences are highlighted in the next screenshot:

The next 3 screenshots show how Duplicate Selected Rows works. It is selected via the grid’s right-click context menu here but works the same when chosen from the Grid menu. Our aim is to duplicate 5 records on the Customer Demand table.

This brings up the Duplicate pane to the right of the grid:

The resulting duplicated rows are shown in this screenshot:

The Geocode button is only available on the Customers, Facilities, and Suppliers input tables. Based on location information, such as Address, City, Region, and Country entered into these tables, the geocoding provider looks up a location’s latitude and longitude and saves those in the table. These can be used to draw locations in the correct location on a map and for distance calculations.
Consider the following Customers table:

By default, the MapBox geoprovider will be used to look up coordinates. You are prompted to indicate if you only want to get results where MapBox finds a 100% match. When this option is left unchecked, the best match (closest to 100%) will be used in case a 100% match is not found:

Once the geocoding is finished, the latitude and longitude columns of these records are populated:

Note that Geoproviders other than MapBox can be configured to be used for geocoding and distance lookups, see the Using Alternate Geocoding Providers Help Center article.
Right-clicking on a table in the Tables list brings up a context menu which contains the options we have already seen and covered above from the File, Grid, and Filter menus that are applicable to the table. Again, multiple options that do not apply to output tables are automatically greyed out in this context menu.

From top to bottom:
There are several tools within Cosmic Frog which can help find problems with the model’s data and overall construction. The table below gives an overview of how these tools compare to each other to help you choose the most suitable one for your situation:
These Help Center articles contain more details on some of these tools:
The Data module has many configuration options as covered above. Following suggested setups are starting points by role.
Model Builder (constructing a new model)
Data Analyst / Data Engineer (loading and cleaning external data)
Scenario Modeler (testing what-if changes)
Reviewer / Business Stakeholder (checking outputs, not building)
A few habits make working in the Data module faster and your models easier for others (or future you) to pick up.
Build in stages, not all at once
This avoids the common trap of populating dozens of tables before confirming the model even runs.
Use Status and Notes fields deliberately
Most input tables include Status and Notes columns. Rather than deleting records you might need later, set Status = Exclude and tag them with a Notes value (e.g., a scenario name or a data source). This keeps your baseline data intact while letting you filter, bulk-update, or scenario-toggle those records later. See the Scenarios article for how this pattern powers scenario items.
Save filters as Named Filters, do not recreate them
If you find yourself typing the same filter condition more than once — on a table, a scenario item, or a map layer — save it as a Named Filter instead. It is pre-validated, reusable across the model, and shows a record-count preview so you can confirm it is selecting what you expect. See Named Filters in Cosmic Frog.
Validate early, not just before a run
Do not wait until a model fails to run to check your data. Run the Integrity Checker (Grid menu) after any significant data load or edit, not only at the end. Catching an issue right after an import is far faster to fix than tracing it back after a failed solve. See Cosmic Frog's Integrity Checker and the Data Validation Tools section above for guidance on choosing the right tool.
Prefer bulk tools over manual entry for anything beyond a few rows
Pasting or typing in more than a handful of records is error-prone and does not scale. Use File > Import for structured Excel/CSV files, Ada or DataStar for messier source data and repeatable workflows, or a Postgres query via the SQL Editor when you need to transform data into the Anura schema.
Use custom columns to stage data, not to feed the model
Custom columns are a convenient place to keep source values, growth factors, or notes external to the model — but remember they are not read by any engine and cannot be used in scenario items. If a value needs to affect a model run, it needs to live in a real Anura column, even if a custom column feeds into it via a scenario item's Actions field.
Happy modeling! As always, please contact our Support team at support@optilogic.com for any questions or feedback.