ckt file, use the Browse button to nominate the required file from an available library. Model File – for a model that has been defined using a.This is the name that must be entered into the Model Name field. Several default example schemes are available, utilizing the short-form code for either the folder type ( SML – Simulation Model Libraries) or the content type ( SIM – Simulation Model): This defines the format of the unique ID for each Item created in that particular folder. Specifying the folder type – its intended use – gives a visual indication of the content of that folder when browsing the Workspace.Īnother important aspect of the parent folder is the Item Naming Scheme employed for it. To nominate a folder's use as a container for simulation models, set its Folder Type as Simulation Models, when defining the folder properties in the Edit Folder dialog. It simply provides a visual 'clue' as to what is stored in a folder and can be beneficial when browsing a Workspace for particular content. This has no bearing on the content of the folder – saving a simulation model definition will always result in a corresponding Simulation Model Item. When creating the folder in which to store simulation models, you can specify the folder's type. The interface to this process – the Library Importer – presents an intuitive flow that takes initial selected libraries, and imports them to your Workspace. Models can also be created in the Workspace as part of migration of existing existing, older generation (SchLib, PcbLib, IntLib, DbLib, SVNDbLib) libraries of components. Once a simulation model has been created (and data saved into a revision of it), it can be reused in the creation of one or more components. Such simulation models are created directly within the Workspace. These links are specified when defining the component.Īltium NEXUS, in conjunction with your connected Workspace, caters for the ability to create and manage simulation models (Simulation Model Items) in that Workspace. In terms of its representation in the various domains, a component doesn't contain the domain models themselves, but rather links to these models. It could therefore be thought of as a container in this respect – a 'bucket' into which all domain models and parametric information is stored. From a designer's perspective, a Workspace component gathers together all information needed to represent that component across all design domains, within a single entity.
0 kommentar(er)
