Stella Export

[Ceumar Pee]

StellaConnect offers a Data Return API to allow you to retrieve Connect responses programmatically into your own systems. We offer details on the technical requirements, how to request data, and what to expect from the data that is returned in our API Data Return Articles. You can find them below:

An enhanced version of our data return feature enables you to flow data from Stella Connect directly into Google sheets via a Google Sheets add-on. Once enabled, this will make it easier to quickly retrieve data in Google Sheets, without going through the export responses screen in Connect. You can retrieve data from any time period for which you have been using Stella Connect, by specifying optional start dates and end dates, 10,000 responses per request.

To better serve the exporting community, BIS has launched an on-line version of its System for Tracking Export License Applications (STELA). You may now check the status of your export/reexport license applications, classification requests, and AGR notifications at Applicants must input their BIS assigned application control number(s) (ACN).

STELA allows users to track export license applications, commodity classification requests, reexport license applications, and license exception agricultural commodity (AGR) notifications online that have been submitted through SNAP-R. For more information, please visit the Bureau of Industry and Security's website.

Each link is shown in a separate row. Use the button to add a new link. Then, use the controls described below to set it up. To remove a link, click on the link you want to remove, and then click on the button.

This column indicates whether the destination you've specified exists and can be read. It will say No until you select a destination, and will also say No if you have an existing link, but the file is missing or unreadable.

Check this option to have the specified used, or uncheck it to effectively turn the link off. When unchecked the link will be ignored when the model is run and when you click on the Export All button described below. You can still perform an export for the link with the Export button appearing at the right.

This specifies the file to which the software will write the data. Click on this field to open a File Selection dialog and choose a file. If the file can't be used, most commonly because all its worksheets are already specified for importing or exporting data, an error message will appear.

This option is only applicable to Excel files, and the control will not be visible if you choose a csv file. After you've selected the file, the first worksheet it contains and that is not in use will be shown. Click on dropdown list then, click on the name of the worksheet to select the worksheet you want.

Click on the button to export to the designated link. The export will be attempted regardless of the Enabled and Dynamic settings. A message will be shown about the success of, or problems with, the export.

Click this button to export to all of the links that are marked enabled. Links marked both dynamic and on demand will be exported. A message will be displayed showing the results of all the exports. If you have many links, this is a convenient way to check that they're all working as expected.

Click OK to save the changes you've made to links. Click Cancel to discard them. Note that any changes you have made in the editing portion of the dialog will be incorporated into the row you are editing. If you did export any results the files created by that will still exist whether you choose OK or Cancel.

In order to import data from an Excel (.XLS or .XLSX) or .CSV file into a model, you need to set up the Excel or .CSV file so that the data is properly formatted. To export data from a model to an Excel or .CSV file, you can use a blank file. The export process will automatically overwrite any information in the file and set it up in the correct format.

The variable names in the file must exactly match the variable names used in the model. You do not need to include all model variables in your file; include only the variables whose values you want to import to the model. Model variables that do not appear in the file are not affected during the import.

You can enter the variable names as column headings or row headings (you will indicate the format you choose when you Setting up import linksto your model). For example, the following Excel worksheet defines the initial values for population (a stock), birth rate (a converter), and death rate (a graphical function), with the variable names in the column headings:

The name of each variable appears as a column heading and the values to import for each variable appear immediately beneath it. All values for the graphical function (death rate), ordered from minimum x to maximum x, appear under the variable heading. If the number of values in the import file is different from the number of points in the graphical function, the graphical function will be adjusted to match the number of values in the import file.

The following example shows the same data with the variables as row headings:

Note that the data in the spreadsheet do not have to start at row 1, column A. The import process searches for names that match variables in the model and then for values below (vertical) or to the right (horizontal) of those names (again ignoring empty cells).

Arrays are imported by specifying 1 dimensional array slices followed by a column (vertical) or row (horizontal) of values for that dimension. For one dimensional arrays you can leave off the [*] and just specify the name.

One-dimensional arrays. To import values in a file into a one-dimensional array in a model, the file must contain one column (or row) of data for the array. The column (or row) heading specifies the array name. All subsequent columns (or rows) contain the data.

N-dimensional arrays. To import values from a file into a higher-dimensional array in a model, the file must contain one column (or row) of data for one or more one-dimensional slices of the array. Instead of just a variable name, a variable with subscripts filled in must be used.

You can use the dimension name or a * to denote the dimension over which the slice is being made. Similarly, if you use array labels you can use the label or the number to specify which slice is being used.

To import values from a file into a conveyor or queue, enter all values for the conveyor or queue as a comma-separated list in a single cell of the import file. For conveyors, you specify one value per unit time in the conveyor. For queues, you specify one value per element in the queue.

Earlier version of iThink and Stella used a different convention when importing data. File formatted in this manner as still supported in Version 10.1, but will not be in future versions. These formats are not recommended because they are both inflexible and confusing.The below documentation is intended to aid conversion of legacy formats to the array slice identification described above.

The entity names in the file must exactly match the entity names used in the model. You do not need to include all model entities in your file; include only the entities whose values you want to import to the model. Model entities that do not appear in the file are not affected during the import.

You can enter the entity names as column headings or row headings (you will indicate the format you choose when you set up the link to your model). For example, the following Excel worksheet defines the initial values for population (a stock), birth rate (a converter), and death rate (a graphical function), with the entity names in the column headings:

The name of each entity appears as a column heading and the values to import for each entity appear immediately beneath it. All values for the graphical function (death rate), ordered from minimum x to maximum x, appear under the entity heading. If the number of values in the import file is different from the number of points in the graphical function, the graphical function will be adjusted to match the number of values in the import file.

The following example shows the same data with the entities as row headings:

Note that the data in the spreadsheet do not have to start at row 1, column A. The import process searches the first 20 rows and 10 columns (200 cells) for a entity name, so you can begin entering data anywhere within that area. This allows you to enter header data or other documentation in the file that will not affect the import process. You can also enter descriptive information between columns (if you are using a column format) or between rows (if you are using a row format).

Between each entity, you can have up to five columns (or rows, if you are using row format) that have a blank header line. Data can appear in any other row (or column, in row format) than the header row and these columns (or rows) will be ignored during the import.

Two-dimensional arrays. To import values from a file into a two-dimensional array in a model, the file must contain more than one column (or row) of data for the array. The first column (or row) specifies the array name. All subsequent columns or rows for the array contain an ellipsis ("...").

N-dimensional arrays. To import values from a file into an n-dimensional array in a model, the file must contain data for each two-dimensional slice of the array. The first column (or row) specifies the array name. All subsequent columns or rows for the two-dimensional slice contain an ellipsis ("..."). To indicate the start of a new two-dimensional slice use "***" in the first column (or row). Optional labels or text appended to the asterisks can be used to help identify the array slice.

3a8082e126