How can item properties be assigned based on part number in Lambda Predict?
Lambda Predict allows you to match the part number of an item in a project to an item in the current project, system or library and then automatically set the properties for the matching item. To do this, select the block or component in the System panel that you want to match to an item in the current project or system. Click the magnifying glass icon that appears next to the Part Number field in the Data panel (Dialog view). A menu will appear, as shown next.
Select Search System, Search Project and/or Search Library to search the current system, project and/or library for existing part numbers. The Part Number drop-down menu will be populated with all part numbers that are within the selected search scope. When you select an existing part number from the drop-down menu, the application will automatically set the properties for the current item to match the existing item with the selected part number. In the example shown next, a capacitor is being added to System B. The drop-down menu of part numbers has been populated by a project-level search; the part numbers are those of components that already exist within the systems in the project. Choosing one will assign all component properties associated with that part number to the new component.
In addition, when importing items into a project, you can match the part numbers of the parts that are being imported against the part numbers in the current project or active library and automatically set the properties for the matching items. You can do this by selecting either Project or Library from the Look up Part ID in field in Step 4 of the Import Wizard, as shown next.
How can simulation results be repeated in RENO?
On the General (first) page of the Simulation Console, you can select to use a seed. This causes the simulations to use a specified starting point for random number generation. The same sequence of random numbers will be used each time you simulate the Flowchart when the same seed value is used and, therefore, the same simulation results will be generated.
It is important to note that when you use a seed, the same stream of random numbers is utilized, but the order of the utilizations of the stream may differ depending on the way the model was constructed. Two people constructing the same model in separate projects may add Constructs or create Definitions in a different sequence. In other words, two people may have the same Random Variables, A and B, defined in a project. If A was created before B in one project, A will take the first random value from the stream and B will take the second. If the other person (in the other project) defined the same model but created B before A, B will take the first random value from the stream and A will take the second, thus yielding slightly different answers, even though both people may have used the same seed in simulation.
Copyright 2006 ReliaSoft Corporation, ALL RIGHTS RESERVED