Selecting Files in Databases as Output Targets
Output data generated by a model can be stored as data files in a Model Manager database in the same way you can store such output as files on the file system. From the Select File window for an output setting, you can either specify a new file or select an existing file in one of your configured databases to use as output target for the model opened in the COMSOL Desktop. Choose the database that you want to select files from in the list of options on the left. Choose Add Database () if you want to add a new database.
The Select File window is, for example, opened when you click the expand button next to Browse () and select Browse From () for a model output setting in the Settings window in the Model Builder workspace.
Click the Select New radio button in the Select File window for a database to specify a new file target. Write a title for the output data in the Title field. The Filename field will be automatically populated with a suggested filename for the main output file based on the title and the output’s file extension.
Change the target branch for the output by clicking the Location link button and selecting another branch in The Select Location Dialog Box. The Location link button is hidden if the database only contains a single branch, which is the default for a new database, or when All Versions in Database () is selected.
Click the Select Existing radio button to find and select an existing data file as output target. The window offers the same search and filter functionality as when selecting a data file from a database as input source — see Selecting Files in Databases as Input Sources.
Click Select () once you have specified a file to use as target for the output.
Selecting a data file from a Model Manager database via the Select File window and clicking Select () only specifies a target for the output. The actual writing and saving of the output data to the database happens later — either directly by clicking, for example, an Export button or as a two-step procedure in which the output is first written to a temporary folder on the local file system and then manually saved to the database. See Loading and Saving Auxiliary Data Files Stored in Databases for more details.
Switching to the All Versions in Database () search mode and selecting an existing version as output target that is not the latest version on a branch will inevitably lead to a version conflict once you try to save any written output to the database. You can choose to manually ignore this conflict from the Export window — see Loading and Saving Auxiliary Data Files Stored in Databases.