{"id":29317,"date":"2004-01-01T00:12:01","date_gmt":"2004-01-01T00:12:01","guid":{"rendered":"https:\/\/silvaco.com\/uncategorized\/new-smartlib-library-of-models\/"},"modified":"2021-07-08T18:31:22","modified_gmt":"2021-07-09T01:31:22","slug":"new-smartlib-library-of-models","status":"publish","type":"post","link":"https:\/\/silvaco.com\/ja\/simulation-standard\/new-smartlib-library-of-models\/","title":{"rendered":"New SmartLIb Library of Models"},"content":{"rendered":"
\n

New SmartLIb Library of Models<\/h1>\n

Overview<\/strong><\/p>\n

In all previous versions of\u00a0SmartSpice<\/em><\/strong>\u00a0the model code (BSIM, diode etc.) was included in the one executable (SmartSpice<\/em><\/strong>\u00a0). This means any updates to the model code would take a while to reach the customer because of the full SPICE functionality checks required before releasing a new\u00a0SmartSpice<\/em><\/strong>\u00a0version. We have therefore separated the\u00a0SmartSpice<\/em><\/strong>\u00a0core from the modeling code to eliminate this delay and dependency. Now the new model release time has been reduced by having a separate library that the customer can download from the web and include into the\u00a0SmartSpice<\/em><\/strong>\u00a0program through the use of these described new functions. All previous\u00a0SmartSpice<\/em><\/strong>\u00a0functionality is maintained as before. This new configuration is only of interest to customer who wish to explore model changes in more depth.<\/p>\n

The -slinstall Option<\/strong><\/p>\n

The \u201c-slinstall\u201d option moves libraries from a download directory to the installation directory.<\/p>\n

Example 1<\/strong><\/p>\n

\n

smartspice -slinstall mydir 0.2.0.R<\/span><\/p>\n<\/blockquote>\n

where mydir is the directory of the libraries that have to be installed, and 0.2.0.R is the version number of the\u00a0SmartLib<\/em><\/strong>\u00a0library it belongs to.<\/p>\n

This command will inspect the files that lay in the mydir directory.\u00a0SmartSpice<\/em><\/strong>\u00a0moves each file to the installation directory if it can be used as a library, and there is no file with the same name. This insures that the file installed will work correctly, and that an installed file cannot be lost while adding a new one.<\/p>\n

To use this option, you must have the rights to modify the installation. Ask to your system Administrator if you are allowed such rights.<\/p>\n

How to Use the -slinstall Option<\/strong><\/p>\n

Example 1<\/strong><\/p>\n

The situation: I\u2019ve downloaded the Solaris library\u00a0libSGP_1_0_5_R.so.tar\u00a0<\/span>which is in a PUB directory from my home.
\nAt this point, you need to untar the file. Move it to the PUB directory:<\/p>\n

\n

cd ~\/PUB<\/span><\/p>\n

tar -xvf libSGP_1_0_5_R.so.tar<\/span><\/p>\n<\/blockquote>\n

Now you must have the libSGP_1_0_5_R.so in the directory:<\/p>\n

\n

smartspice -slinstall . 1.0.0.R<\/span><\/p>\n<\/blockquote>\n

SmartSpice<\/em><\/strong>\u00a0indicates that\u00a0libSGP_1_0_5_R.so.tar<\/span>\u00a0cannot be loaded so it won\u2019t be installed. It also indicates that\u00a0libSGP_1_0_5_R<\/span>.so has been copied, and that the installation has been successful.<\/p>\n<\/div><\/section><\/div>

<\/div>