verifImportMapping
verifImportMapping(
g_sessionId
t_fileName
S_type
)
=> t / nil
Description
Import mapping from an Excel or CSV file.The first row of the file will be ignored as it should be a header row. The rest of the rows should have at least two columns: RequirementId and MappingName. Any other columns will be ignored. Each row is a single requirement-to- implementation mapping, so if a requirement is mapped to multiple implementations, then there will be multiple rows with the same requirement ID in the first column.
Requirement,Mapping
ID6,opamp090/full_diff_opamp_AC/maestro/Active/opamp090:full_diff_opamp_TRAN:1/SlewRate
ID6,opamp090/full_diff_opamp_AC_bad/maestro/Active/opamp090:full_diff_opamp_TRAN:1/SlewRate
ID5,opamp090/full_diff_opamp_AC/maestro/Active/opamp090:full_diff_opamp_TRAN:1/SettlingTime
Shell-style wildcard character "*" can be used in the names, but it is recommended to avoid numerous matches when importing the file. For example:
ID*,op*/full_diff_opamp_AC/maestro*/Active
This mapping is valid, but would map every requirement beginning with ID to all implementations that match. Any existing mapping on the requirement is retained, so any new mapping is added on top of that.
Arguments
|
Integer, string number, or window specifying the Verifier session ID. For example, |
|
|
String or symbol to specify the type of file. It can be either |
Value Returned
Examples
Opens a Verifier cellview and imports the mapping information from the specified file.
sess = verifOpenCellView("test" "sample" "verifier")
=> 0
verifExportMapping(sess "map.csv")
=> t
sess2 = verifOpenCellView("test" "sample2" "verifier")
=> 1
verifImportMapping(sess2 "map.csv")
=> t
Related Topics
Requirement-to-Implementation Mapping Functions
Return to top