File and Data Management

Transcription

1

2 IC-CAP January 2013 File and Data Management Agilent Technologies, Inc Stevens Creek Blvd, Santa Clara, CA USA No part of this documentation may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Agilent Technologies, Inc as governed by United States and international copyright laws Acknowledgments UNIX is a registered trademark of the Open Group MS-DOS, Windows, and MS Windows are US registered trademarks of Microsoft Corporation Pentium is a US registered trademark of Intel Corporation PostScript is a trademark of Adobe Systems Incorporated Java is a US trademark of Sun Microsystems, Inc Mentor Graphics is a trademark of Mentor Graphics Corporation in the US and other countries Qt Version 474 Qt Notice The Qt code was modified Used by permission Qt Copyright Qt Version 474, Copyright (c) 2010 by Nokia Corporation All Rights Reserved Qt License Your use or distribution of Qt or any modified version of Qt implies that you agree to this License This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 21 of the License, or (at your option) any later version This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE See the GNU Lesser General Public License for more details You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc, 51 Franklin St, Fifth Floor, 1

3 Boston, MA USA Permission is hereby granted to use or copy this program under the terms of the GNU LGPL, provided that the Copyright, this License, and the Availability of the original version is retained on all copies User documentation of any code that uses this code or any modified version of this code must cite the Copyright, this License, the Availability note, and "Used by permission" Permission to modify the code and to distribute modified code is granted, provided the Copyright, this License, and the Availability note are retained, and a notice that the code was modified is included Qt Availability Patches Applied to Qt can be found in the installation at: $HPEESOF_DIR/prod/licenses/thirdparty/qt/patches You may also contact Brian Buchanan at Agilent Inc at brian_buchanan@agilentcom for more information For details see: Python A HISTORY OF THE SOFTWARE ========================== Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see ) in the Netherlands as a successor of a language called ABC Guido remains Python's principal author, although it includes many contributions from others In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see ) in Reston, Virginia where he released several versions of the software In May 2000, Guido and the Python core development team moved to BeOpencom to form the BeOpen PythonLabs team In October of the same year, the PythonLabs team moved to Digital Creations (now Zope Corporation, see ) In 2001, the Python Software Foundation (PSF, see ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property Zope Corporation is a sponsoring member of the PSF All Python releases are Open Source (see for the Open Source Definition) Historically, most, but not all, Python releases have also been GPLcompatible; the table below summarizes the various releases Footnotes: (1) GPL-compatible doesn't mean that we're distributing Python under the GPL All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don't (2) According to Richard Stallman, 161 is not GPL-compatible, because its license has a choice of law clause According to CNRI, however, Stallman's lawyer has told CNRI's 2

4 lawyer that 161 is "not incompatible" with the GPL File and Data Management Thanks to the many outside volunteers who have worked under Guido's direction to make these releases possible B TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON =============================================================== PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 1 This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation 2 Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, ie, "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee 3 In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 4 PSF is making Python available to Licensee on an "AS IS" basis PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS 5 PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF 6 This License Agreement will automatically terminate upon a material breach of its terms and conditions 7 Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party 8 By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement BEOPENCOM LICENSE AGREEMENT FOR PYTHON BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1 This LICENSE AGREEMENT is between BeOpencom ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software") 2 Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee 3 BeOpen is making the Software available to Licensee on an "AS IS" basis BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS 4 BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE 3

5 SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF 5 This License Agreement will automatically terminate upon a material breach of its terms and conditions 6 This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party As an exception, the "BeOpen Python" logos available at may be used according to the permissions granted on that web page 7 By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement CNRI LICENSE AGREEMENT FOR PYTHON This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 161 software in source or binary form and its associated documentation 2 Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 161 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, ie, "Copyright (c) Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 161 alone or in any derivative version prepared by Licensee Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 161 is made available subject to the terms and conditions in CNRI's License Agreement This Agreement together with Python 161 may be located on the Internet using the following unique, persistent identifier (known as a handle): /1013 This Agreement may also be obtained from a proxy server on the Internet using the following URL: " 3 In the event Licensee prepares a derivative work that is based on or incorporates Python 161 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python CNRI is making Python 161 available to Licensee on an "AS IS" basis CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 161 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS 5 CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 161 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 161, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF 6 This License Agreement will automatically terminate upon a material breach of its terms and conditions 7 This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such US federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions Notwithstanding the foregoing, with regard to derivative works based on Python 161 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party 4

6 8 By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 161, Licensee agrees to be bound by the terms and conditions of this License Agreement ACCEPT CWI LICENSE AGREEMENT FOR PYTHON 090 THROUGH Copyright (c) , Stichting Mathematisch Centrum Amsterdam, The Netherlands All rights reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE bzip2 This copy of Python includes a copy of bzip2, which is licensed under the following terms: This program, "bzip2", the associated library "libbzip2", and all documentation, are copyright (C) Julian R Seward All rights reserved Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1 Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer 2 The origin of this software must not be misrepresented; you must not claim that you wrote the original software If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required 3 Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software 4 The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE Julian Seward, jseward@bziporg bzip2/libbzip2 version 105 of 10 December 2007 OpenSSL This copy of Python includes a copy of openssl, which is licensed under the following terms: LICENSE ISSUES ============== The OpenSSL toolkit stays under a dual license, ie both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit 5

7 See below for the actual license texts Actually both licenses are BSD-style Open Source licenses In case of any license issues related to OpenSSL please contact OpenSSL License Copyright (c) The OpenSSL Project All rights reserved Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1 Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution 3 All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( )" 4 The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission For written permission, please contact openssl-core@opensslorg 5 Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project 6 Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( )" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE ==================================================================== This product includes cryptographic software written by Eric Young (eay@cryptsoftcom) This product includes software written by Tim Hudson (tjh@cryptsoftcom) Original SSLeay License Copyright (C) Eric Young (eay@cryptsoftcom) All rights reserved This package is an SSL implementation written by Eric Young (eay@cryptsoftcom) The implementation was written so as to conform with Netscapes SSL This library is free for commercial and non-commercial use as long as the following conditions are adhered to The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc, code; not just the SSL code The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoftcom) Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1 Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice, this list of 6

8 conditions and the following disclaimer in the documentation and/or other materials provided with the distribution 3 All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoftcom)" The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related 4 If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoftcom)" THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE The licence and distribution terms for any publically available version or derivative of this code cannot be changed ie this code cannot simply be copied and put under another distribution licence including the GNU Public Licence Tcl This copy of Python includes a copy of Tcl, which is licensed under the following terms: This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc, Scriptics Corporation, ActiveState Corporation and other parties The following terms apply to all files associated with the software unless explicitly disclaimed in individual files The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any distributions No written agreement, license, or royalty fee is required for any of the authorized uses Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS GOVERNMENT USE: If you are acquiring this software on behalf of the US government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause (c) (2) If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause (c) (1) of DFARs Notwithstanding the foregoing, the authors grant the US Government and others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license Tk This copy of Python includes a copy of Tk, which is licensed under the following terms: This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc, and other parties The following terms apply to all files associated with the software unless explicitly disclaimed in individual files The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices 7

9 are retained in all copies and that this notice is included verbatim in any distributions No written agreement, license, or royalty fee is required for any of the authorized uses Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS GOVERNMENT USE: If you are acquiring this software on behalf of the US government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause (c) (2) If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause (c) (1) of DFARs Notwithstanding the foregoing, the authors grant the US Government and others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license Mersenne Twister The _random module includes code based on a download from matumoto/mt2002/emt19937arhtml The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26 Coded by Takuji Nishimura and Makoto Matsumoto Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length) Copyright (C) , Makoto Matsumoto and Takuji Nishimura, All rights reserved Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1 Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution 3 The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE Any feedback is very welcomehttp://wwwmathkeioacjp/matumoto/emthtml matumoto@mathkeioacjp Sockets The socket module uses the functions, getaddrinfo(), and getnameinfo(), which are coded in separate source files from the WIDE Project, Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project All rights reserved 8

10 Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1 Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution 3 Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND GAI_ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR GAI_ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON GAI_ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN GAI_ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE Floating point exception control The source for the fpectl module includes the following notice: / Copyright (c) 1996 \ The Regents of the University of California All rights reserved Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software This work was produced at the University of California, Lawrence Livermore National Laboratory under contract no W-7405-ENG-48 between the US Department of Energy and The Regents of the University of California for the operation of UC LLNL DISCLAIMER This software was prepared as an account of work sponsored by an agency of the United States Government Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately-owned rights Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or the University of California The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product \ endorsement purposes / MD5 message digest algorithm The source code for the md5 module contains the following notice: Copyright (C) 1999, 2002 Aladdin Enterprises All rights reserved This software is provided 'as-is', without any express or implied warranty In no event will the authors be held liable for any damages arising from the use of this software Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 9

11 1 The origin of this software must not be misrepresented; you must not claim that you wrote the original software If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required 2 Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software 3 This notice may not be removed or altered from any source distribution L Peter Deutsch ghost@aladdincom Independent implementation of MD5 (RFC 1321) This code implements the MD5 Algorithm defined in RFC 1321, whose text is available at The code is derived from the text of the RFC, including the test suite (section A5) but excluding the rest of Appendix A It does not include any code or documentation that is identified in the RFC as being copyrighted The original and principal author of md5h is L Peter Deutsch <ghost@aladdincom> Other authors are noted in the change history that follows (in reverse chronological order): lpd Removed support for non-ansi compilers; removed references to Ghostscript; clarified derivation from RFC 1321; now handles byte order either statically or dynamically lpd Edited comments slightly for automatic TOC extraction lpd Fixed typo in header comment (ansi2knr rather than md5); added conditionalization for C++ compilation from Martin Purschke <purschke@bnlgov> lpd Original version Asynchronous socket services The asynchat and asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE Cookie management The Cookie module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alummitedu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, 10

12 WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE Profiling The profile and pstats modules contain the following notice: Copyright 1994, by InfoSeek Corporation, all rights reserved Written by James Roskind Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose (subject to the restriction in the following sentence) without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of InfoSeek not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission This permission is explicitly restricted to the copying and modification of the software to remain in Python, compiled Python, or other languages (such as C) wherein the modified or derived code is exclusively imported into a Python module INFOSEEK CORPORATION DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS IN NO EVENT SHALL INFOSEEK CORPORATION BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE Execution tracing The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc, all rights err reserved and offered to the public under the terms of the Python 22 license Author: Zooko O'Whielacronxhttp://zookocom/ zooko@zookocom Copyright 2000, Mojam Media, Inc, all rights reserved Author: Skip Montanaro Copyright 1999, Bioreason, Inc, all rights reserved Author: Andrew Dalke Copyright , Automatrix, Inc, all rights reserved Author: Skip Montanaro Copyright , Stichting Mathematisch Centrum, all rights reserved Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission UUencode and UUdecode functions The uu module contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 11

13 PERFORMANCE OF THIS SOFTWARE File and Data Management Modified by Jack Jansen, CWI, July 1995: Use binascii module to do the actual line-by-line conversion between ascii and binary This results in a 1000-fold speedup The C version is still 5 times faster, though Arguments more compliant with Python standard XML Remote Procedure Calls The xmlrpclib module contains the following notice: The XML-RPC client interface is Copyright (c) by Secret Labs AB Copyright (c) by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT-ABILITY AND FITNESS IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE test_epoll The test_epoll contains the following notice: Copyright (c) Twisted Matrix Laboratories Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE Select kqueue The select and contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1 Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY 12

14 EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE strtod and dtoa The file Python/dtoac, which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M Gay, currently available from The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** The author of this software is David M Gay Copyright (c) 1991, 2000, 2001 by Lucent Technologies Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE ***************************************************************/ expat The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat: Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE libffi The _ctypes extension is built using an included copy of the libffi sources unless the build is configured --with-system-libffi: Copyright (c) Red Hat, Inc and others Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ``Software''), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 13

15 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE zlib The zlib extension is built using an included copy of the zlib sources unless the zlib version found on the system is too old to be used for the build: Copyright (C) Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty In no event will the authors be held liable for any damages arising from the use of this software Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1 The origin of this software must not be misrepresented; you must not claim that you wrote the original software If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required 2 Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software 3 This notice may not be removed or altered from any source distribution Jean-loup Gailly Mark Adler jloup@gziporg madler@alumnicaltechedu pywin Unless stated in the specfic source file, this work is Copyright (c) , Mark Hammond All rights reserved Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution Neither name of Mark Hammond nor the name of contributors may be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE win32com Unless stated in the specfic source file, this work is Copyright (c) , Greg Stein and Mark Hammond All rights reserved 14

16 Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution Neither names of Greg Stein, Mark Hammond nor the name of contributors may be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE adodbapi adodbapi - A python DB API 20 (PEP 249) interface to Microsoft ADO Copyright (C) 2002 Henrik Ekelund, version 21 by Vernon Cole This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 21 of the License, or (at your option) any later version This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE See the GNU Lesser General Public License for more details You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc, 59 Temple Place, Suite 330, Boston, MA USA django adaptations and refactoring by Adam Vandenberg isapi Copyright by Blackdog Software Pty Ltd All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Blackdog Software not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission BLACKDOG SOFTWARE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL BLACKDOG SOFTWARE BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE Scintilla and SciTE

17 Copyright by Neil Hodgson All Rights Reserved File and Data Management Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation NEIL HODGSON DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL NEIL HODGSON BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE Numpy Numpy license Copyright? , NumPy Developers All rights reserved Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution Neither the name of the NumPy Developers nor the names of any contributors may be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE Errata The IC-CAP product may contain references to "HP" or "HPEESOF" such as in file names and directory names The business entity formerly known as "HP EEsof" is now part of Agilent Technologies and is known as "Agilent EEsof" To avoid broken functionality and to maintain backward compatibility for our customers, we did not change all the names and labels that contain "HP" or "HPEESOF" references Warranty The material contained in this documentation is provided "as is", and is subject to being changed, without notice, in future editions Further, to the maximum extent permitted by applicable law, Agilent disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose Agilent shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein Should Agilent and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control Technology Licenses The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license Restricted Rights Legend US Government Restricted Rights Software and technical data rights granted to the federal government include only those rights customarily provided to end user customers Agilent provides this customary commercial license in Software and technical data pursuant to FAR (Technical Data) and (Computer Software) and, for the Department of Defense, DFARS (Technical Data - Commercial Items) and DFARS (Rights in Commercial Computer Software or Computer Software Documentation) 16

18 17

19 18 Open and Save Files 17 Importing Data 21 IC-CAP File Structure and Format 22 IC-CAP Data Manager 24 Setting Data Management System Variables 25 Importing Data through MDM 27 Exporting Data through MDM 29 MDM File Structure 33 Data Management Examples 38 Database Connection Manager 40 Configuring Database with Database Connection Manager 41 Working with Database Connection Manager 46 Database Query Syntax 50 Using Database Connection Manager APIs 56

20 Open and Save Files To open a file: File and Data Management 1 Choose File > Open from the Main IC-CAP window By default, the path is set to the directory from which you started the program and the filter is set to *ext where ext is an extension specific to the task you are performing (For example, *mdl for model files, *hdw for hardware configuration files, etc) All the files in the current directory with that extension are displayed 2 3 Adjust the path as required Note The path for IC-CAP model files cannot contain any folder names that use a space If a model file is saved in a folder name with spaces, you will not be able to open the model file You will have to move the model file to a folder name that does not use a space To choose a file, double-click it or click once and choose OK Note If loading a model file, once it is loaded, a symbol with the model name is displayed in the work area Double-click the symbol to open the Model window Opening Parts of a Model File The File > Open command in the Model window enables you to open a file (previously saved using File > Save As in the Model window) that contains some portion of a model To open a file containing a portion of a model: 1 If you want to replace some portion of the current model file with a portion of another file, select the item you want to replace 2 Choose File > Open in the Model window 3 Select the appropriate file type and click Browse to view the files of that type in the directory you specify Note The path for IC-CAP model files cannot contain any folder names that use a space If a model file is saved in a folder name with spaces, you will not be able to load the model file You will have to move the model file to a folder name that does not use a space 4 Select a file and click OK 5 For Model Parameters and DUT Parameters, select Replace Parameter Set or Read Values Only and click OK Replace Parameter Set replaces all Value, Min, and Max values with the ones in the selected file If the selected file does not include Min and Max ranges (for example, when reading pre-ic-cap 2004 parameter set files), the existing Min and Max ranges are deleted Read Values Only replaces parameter Values while maintaining existing Min and Max ranges if possible If the new Value is outside the existing range, Min or Max is extended to include the new Value and a warning is displayed in the Status window 6 For all other Model folders, select the Replace option to use the specified file as a replacement and click OK To add the specified file, make sure the option is turned off and click OK Saving Files To specify a directory and a filename: 1 Choose File > Save As and a dialog box appears 2 Double-click in the Directories list box to locate the desired directory 3 To save to an existing file, select that filename from the Files list box and click OK To save to another name, type that name in the Selection field and click OK 4 Where applicable, click OK to dismiss the previous dialog box Saving a Model File From the Save As dialog box in the Main window: 1 Select all models you want to save to one model file 19

21 2 Accept the default status of saving the file with the measured and simulated data, or enable the option to save without it 3 Adjust the path and filename as needed, and click Apply Hint: To avoid typing a lengthy path change, use the Browser 4 5 Note The path for IC-CAP model files cannot contain any folder names that use a space If you include a space in a folder name, you will not be able to load the model file You will have to move the model file to a folder name that does not use a space Continue saving as needed, clicking Apply to effect each change Click OK to dismiss the dialog box Note You can also save a model file from the Model Window if you want to save all components to one file Saving Parts of a Model File When you choose File > Save As in a Model window, you can choose which part of the model to save to file: DUT, setup, input, output, transform, plot, macro, variable table, parameter set, circuit description, or instrument options 1 Select the option representing the portion of the file you want to save (Where applicable, select the option from the drop-down list) 2 Accept the default status of saving the file with the measured and simulated data, or enable the option to save without it 3 Adjust the path and filename as needed Tip Hint: To avoid typing a lengthy path change, use the Browser 4 Note The path for IC-CAP model files cannot contain any folder names that use a space If you include a space in a folder name, you will not be able to load the model file You will have to move the model file to a folder name that does not use a space Click OK to effect the save and dismiss the dialog box Change Default Directory By default, model files and data will be saved to the directory from which you started the program To change the directory: 1 Choose File > Change Directory By default, the path is set to the directory from which you started the program 2 Adjust the path as needed 3 Select the required directory, click OK 20

22 Importing Data File and Data Management Importing Data into a Single Setup 1 Select the DUT and setup 2 Select File > Import Data and choose Active Setup Alternatively, you can select Measure/Simulate and click Import Data 3 Enter the name of the file directly into the field corresponding to the setup, by typing in or by using the File Browser 4 Select a fill data type Measured if available, otherwise Simulated: Outputs of type M or B receive mdm data in their measured array Outputs of type S receive mdm data in their simulated array Measured only: Outputs of type M or B receive data in their measured array Outputs of type S do not receive any data Simulated if available, otherwise Measured: Outputs of type S or B receive mdm data in their simulated array Outputs of type M receive mdm data in their measured array Simulated only: Outputs of type S or B receive mdm data in their simulated array Outputs of type M do not receive any data 5 Click OK The data is now imported into the outputs of the setup Importing Data into All Setups 1 Select the DUT 2 Select File > Import Data and choose one of the following: Active Setup All Setups in Active DUT All DUTs in Model The dialog box that appears has three columns (DUT, Setup, Data Filename) and a Fill Data Type selection area 3 Specify a filename for each setup You can type the path and filename directly in the Filename field, or use the Browser to select it 4 Click Apply each time you specify a filename for a setup 5 Select a fill data type Measured if available, otherwise Simulated: Outputs of type M or B receive mdm data in their measured array Outputs of type S receive mdm data in their simulated array Measured only: Outputs of type M or B receive data in their measured array Outputs of type S do not receive any data Simulated if available, otherwise Measured: Outputs of type S or B receive mdm data in their simulated array Outputs of type M receive mdm data in their measured array Simulated only: Outputs of type S or B receive mdm data in their simulated array Outputs of type M do not receive any data 6 Click OK See Also IC-CAP Data Manager (datamanagement) Database Connection Manager (datamanagement) 21

23 IC-CAP File Structure and Format This section describes the format of the IC-CAP mdl file and associated files that can be written to and read from the system When read into the system, these files restore IC- CAP to a previously saved state Knowledge of the design of these files allows advanced users to perform many creative modifications to an IC-CAP configuration See An Example Model File (managemodels) File Structure All files used by IC-CAP are stored in an ASCII format that can be accessed by standard HP-UX tools and editors IC-CAP Model files have a user-defined name; the extension is assigned by the system The following table lists the file types and extensions IC-CAP File Types and Extensions File Type Extension File Type Extension Dataset ds Data management mdm Hardware hdw Setup set Model mdl Input inp Circuit cir Output out Model Parameters mps Transform xfm Macro mac Plot plt DUT dut Instrument Options iot DUT Parameters dps Variables Table vat Test Circuit tci Input inp Statistical data sdf The mdl file is a combination of the file types listed below it If all Models currently loaded are saved together, they are put in a single mdl file The complete Model file contains a circuit description, a model parameter set, Macros, and DUT descriptions The DUT description in turn contains a DUT parameter set, a Test Circuit, and Setups The Setups contain Inputs, Outputs, Transforms, and Plots The hardware description is global to IC-CAP and is not a part of a Model file It can be saved in a hdw file It is also found in the icconfig file in the user's home directory In addition to the hardware description, this file contains values of system variables, and status information for windows that are directly available from the Main Menu The individual major sections of the complete Model file begin with the word LINK followed by the type (for example, Model or DUT) and a name The supporting information under this defines the appropriate configuration for IC-CAP The hierarchy of related items in each file is defined by sets of braces { } A major section title is followed by an open brace { and continues until the complementary closing brace } Within a section there are several key words that indicate the function of the associated information When a single key word is on a line, the associated information is on the lines below For some key words, their associated information is in fields to the right only, while for others, associated information is in fields to the right and lines below These key words are summarized in the following table When editing an IC-CAP Model file, key words and braces must be in the correct locations for the file to be correctly read into IC-CAP Editing the file with a text editor can be quite productive in some areas When developing large Program Transforms or Macros, you may find it more convenient to create these with an editor outside of IC-CAP and read them in When doing this, begin each line of text in your Program Transform or Macro with the pound sign (#) Key words in the IC-CAP File Structures 22

24 Key Word Definition LINK major IC-CAP building block applic application window that can be opened by IC-CAP subapp title within an application TABLE collection of user-modifiable elements element user-programmable field (input box) HYPTABLE table that is dynamically configured by IC-CAP BLKEDIT block editor text follows (note: leading space in text) CNTABLE connection table-not currently used in IC-CAP PSTABLE parameter set table param model parameter name and value data configuration data follows belonging to the LINK item dataset collection of numerical data datasize dimensional information for a dataset type MEASured, SIMUlated, or COMMON data points to follow point individual data value-index, row, column, real value, imaginary value list this item is dependent on the owning LINK item member the owning LINK item is dependent on this item File and Data Management 23

25 IC-CAP Data Manager File and Data Management The Data Manager (MDM) de-couples the measured or simulated data from a Model file With this capability, you can save all the data for a collection of device geometries, temperatures, etc into a single data management file (one file per setup) Subsets of this file (as required by specific extractions) can be imported into a given setup With the Data Manager, you can import data measured from a non-ic-cap environment into IC-CAP You can use this data in a database (commercially available or internal), where you can use an external database program to manage huge amounts of data and then translate the data in the database into the MDM format for subsequent input into IC-CAP Similarly, you can use the external database to control the exported MDM file Using the Data Manager, you can: Export measured or simulated data along with non-simulatable attributes (such as, length, width, temperature, etc) Export transforms Import data from the MDM file as a whole Import data from parts of the MDM file Import data with sweep-orders that are different from what was measured, exported or stored in the data file Managing your measured data consists of following two major steps: 1 2 Exporting the measured or simulated data in a setup to an MDM file Importing the data back into a pre-defined setup This section describes the IC-CAP Data Manager (MDM), its system variables, and the file structure It also provides the procedure to: Import and Export data to an MDM file Export data to an MDIF (Model Data Interchange Format) file Export data to a dataset file (ds) This section covers the following topics: Setting Data Management System Variables (datamanagement) Exporting Data through MDM (datamanagement) Importing Data through MDM (datamanagement) Data Management Examples (datamanagement) MDM File Structure (datamanagement) 24

26 Setting Data Management System Variables You can set system variables to control the data management Figure: Set Default Variables for Data Management The following table lists the system variables for data management Variable Name Description Examples MDM_FILE_PATH Specifies the Data Manager file name path MDM_FILE_NAME Specifies the Data Manager file name _ MDM_EXPORT_COMMENT Specifies the text to be added as a comment at the top of an MDM file, when you export the data The text can include embedded IC-CAP variables such as val$(var-name), and predefined program variables such as DATE, NEWLINE, TAB, MODEL, DUT, and SETUP MDM_EXPORT_COMMENT_FILE Specifies the Data Manager comment file to be used when exporting data to an MDM file The contents of the specified file are prepended to the MDM file MDM_EXPORT_XFORM_DATA When set to TRUE, exports all transform(s) data in a setup Default is FALSE Note MDM_ERROR is replaced by MDM_REL_ERROR _ MDM_STD_COM - Today's date : $DATE MDM_EXPORT_COMMENT - val$(mdm_std_com) MDM_EXPORT_COMMENT - MDM file exported on $DATE MDM_EXPORT_COMMENT - Date: $DATE $SETUP L=val$(L) W=val$(W) where W and L are Model, DUT or Setup parameters/variables MDM_REL_ERROR When IC-CAP reads a value from an MDM file, it tries to match the requested input values with the data in the MDM If the data does not exist in the MDM file, importing the data is not advised However, due to roundoff errors, a tolerance must be assumed _ MDM_VALUES_LIST MDM_XFORM_LIST IC-CAP uses the formula MDM_REL_ERROR > (req - mdm)/req as its acceptance test The Default value is 1E-10 This value should rarely need to be adjusted, and can be adjusted for an individual Input By assigning a value to MDM_REL_ERROR_<name> (where < name> is the name of the Input to which the tolerance is to be applied), specific control is possible (See MDM_ZERO_TOL) Specifies a space or comma separated _ list of Parameter or Variable names The values of these Parameters/Variables are written to the MDM file When an MDM file with values stored in it is imported or used to auto-create a setup, these Parameters/Variables are automatically reset to the values stored in the MDM However, if a Parameter or Variable no longer exists in the scope of the setup being imported to, a variable will be created for that value in the Setup Variables Table Specifies a comma separated list of 25

27 transform names that will be exported when this setup is exported By using this variable, you may specify a subset of all the transforms for export In addition, you may specify the mode, nodes, and other data Each transform entry in the comma separated list appears in the MDM file as an output The actual values of each output type are shown below: File and Data Management MDM_XFORM_LIST = calc_ic I C E, calc_ib I B E SMU2 MDM_XFORM_LIST = Hcalc H, beta Mode Values V,N,U <Name> <Mode> <+ Node> <- Node> <Unit> <Type> I <Name> <Mode> <To Node> <From Node> <Unit> <Type> C,G <Name> <Mode> <High Node> <Low Node> <Unit> <Type> T <Name> <Mode> <Node> <Pulse Param> <Unit> <Type> S,H,Z,K,A,Y <Name> <Mode> <Port 1> <Port 2> <AC Ground> <Unit> <Type> MDM_ZERO_TOL Note, only the transform name is required You may include as many extra entries per transform as required This variable is only referenced if MDM_EXPORT_XFORM_DATA is set to TRUE When IC-CAP reads values from an MDM file, it tries to match requested Input values with data in the MDM If the data does not exist in the MDM file, importing the data is not advised However, due to roundoff errors, a tolerance must be assumed _ MDM_HEADER_VERBOSE IC-CAP uses the formula MDM_ZERO_TOL > (req - mdm) req == 0 or mdm == 0 as its acceptance test Default value is 1E-30 This value should rarely need to be adjusted, and can be adjusted for an individual Inputs By assigning a value to MDM_ZERO_TOL_<name> (where < name> is the name of the Input to which the tolerance is to be applied), specific control is possible See MDM_REL_ERROR Specifies if the header of the MDM file includes comments describing each field The default value is FALSE _ 26

28 Importing Data through MDM File and Data Management You can import data (mdm files) into an active setup, to all the setups in an active DUT, or to all the DUTs in a model Note You cannot import dataset files (ds) into a model file However, you can export the dataset files from a Model window and then view it in the ADS Data Display window This sections covers the following topics: Importing Data into an Active Setup Importing Data into All Setups Importing Data into an Active Setup To import data into an active setup: Select the setup in the DUT/Setup pane Select File > Import Data > Active Setup Alternatively, you can click Import Data in the Measure/Simulate pane Enter the name of the file corresponding to the selected setup or click Browse to select an existing file 4 Select a fill data type Measured if available, otherwise Simulated: Outputs of type M or B receive mdm data in their measured array Outputs of type S receive mdm data in their simulated array Measured only: Outputs of type M or B receive data in their measured array Outputs of type S do not receive any data Simulated if available, otherwise Measured: Outputs of type S or B receive mdm data in their simulated array Outputs of type M receive mdm data in their measured array Simulated only: Outputs of type S or B receive mdm data in their simulated array Outputs of type M do not receive any data 5 Click OK The data is now imported into the outputs of the setup Importing Data into All Setups To import data into all setups in an active DUT or all DUTs in the model: 1 2 Select the DUT Select File > Import Data and choose one of the following: 1 All Setups in Active DUT 2 All DUTs in Model Note All Setups in Active DUT imports an ASCII-based MDM data file of a pre-determined format, to the selected DUT; All DUTs in Model imports an ASCII-based MDM data file of a predetermined format, to all setups in all DUTs of the current model 3 Note ICCAP_FUNC can be used to import data from MDM files into all setups in a DUT, and into all DUTs in a model as shown in these examples: iccap_func(<model/dut>,"import Data") All Setups in Active DUT iccap_func(<model>,"import Data") All DUTs in Model The dialog box that appears has three columns and a Fill Data Type selection area The first column shows the DUT name, the 2nd column the setup names and the 3rd column the MDM file to be imported By default, the file represented by the variables MDM_FILE_PATH and MDM_FILE_NAME are shown in the 3rd column Enter the name of the file directly into the field corresponding to the setup, by typing in or by using the File Browser 27

29 4 Select a fill data type Measured if available, otherwise Simulated: Outputs of type M or B receive mdm data in their measured array Outputs of type S receive mdm data in their simulated array Measured only: Outputs of type M or B receive data in their measured array Outputs of type S do not receive any data Simulated if available, otherwise Measured: Outputs of type S or B receive mdm data in their simulated array Outputs of type M receive mdm data in their measured array Simulated only: Outputs of type S or B receive mdm data in their simulated array Outputs of type M do not receive any data Viewing an MDM File Header: To view the header of an MDM data file, select the Setup cell in the dialog box, enter the corresponding MDM filename, then click View Automatically creating the inputs- and outputs-based on an MDM file: You can create the input sweeps and outputs in a newlycreated setup from the header of an MDM file To create the inputs and outputs, first create a new setup, select the setup name in the dialog box, enter the corresponding MDM filename, and then click Create Clicking Create does not import data-it simply creates the inputs/outputs based on the MDM file To create the inputs/outputs and import data in one step, select Measure/Simulate and click Import Create Note You can delete the inputs and outputs from a setup by using ICCAP_FUNC with Import Delete as the second argument, as in this example ICCAP_FUNC(<setup>, "Import Delete") 5 Click Apply or OK Clicking Apply imports data into all setups with filenames Clicking OK does the same but also closes the dialog box Clicking Cancel closes the dialog box without importing any data, but does not cancel any setups created using the Create button See Also Exporting Data through MDM (datamanagement) Data Management Examples (datamanagement) MDM File Structure (datamanagement) 28

30 Exporting Data through MDM File and Data Management You can export various types of IC-CAP data for various uses You can export your current model parameters to an MDIF (Model Data Interchange Format) file for use in the Advanced Design System (ADS) schematics You can merge your current model parameters with your circuit definition and export to a file for use in an external simulator You can export all the numeric data in your model file to a dataset file for use in ADS You can export your measurement, simulation, and transformation data to an IC-CAP MDM file This data (or subsets of this data) can then be read back into IC-CAP This section covers the following topics: Exporting Data to MDIF Files Exporting Data to Extracted Deck Files Exporting Data to Dataset Files Exporting Data to MDM Files Exporting Data to MDIF Files To export your current model parameters to an MDIF (Model Data Interchange Format) file for use in the ADS schematics: In the Model window, choose File > Export Data > Write Model MDIF The File Save As dialog box appears In the File Name field, enter a unique filename or select an existing filename Click OK to export the data to an MDIF file Exporting Data to Extracted Deck Files To merge your current model parameters with your circuit definition and export to a file for use in an external simulator: Select the DUT and setup Select File > Export Data > Extracted Deck The File Save As dialog box appears In the File Name field, type in a unique filename or select an existing filename Click OK to export the data to an extracted deck file Exporting Data to Dataset Files Dataset (ds) files can be read by various tools in ADS IC-CAP exports all data in the Parameter tables, Variable tables, Inputs, Outputs, and Transforms You can export this data for an entire model, a single DUT, or a single Setup To export an entire model to a dataset file: 1 Choose File > Export Data > All DUTs in Model The Data Manager - Export Dataset file dialog box appears 2 In the File Name field, enter a unique filename or select an existing filename The ds file extension is automatically appended to the filename 3 Note If you select an existing filename, it is overwritten without any error message Click OK to export the data to a dataset file To export a single DUT to a dataset file: 1 Select a DUT in the DUTs-Setups tab 29

31 2 Choose File > Export Data > All Setups in Active DUT The Data Manager - Export Dataset file dialog box appears 3 In the File Name field, enter a unique filename or select an existing filename The ds file extension is automatically appended to the filename 4 Note If you select an existing filename, it is overwritten without any error message Click OK to export the data to a dataset file To export a single setup to a dataset file: 1 Select a setup in the DUTs-Setups tab 2 Choose File > Export Data > Active Setup or click Export Data on the Measure/Simulate tab The Data Management - Export Data dialog box appears 3 Select Dataset Format (ds) from the Data File Type drop-down list 4 In the File Name field, enter a unique filename or click Browse to select an existing filename The ds file extension is automatically appended to the filename 5 Note If you select an existing filename, it is overwritten without any error message Click OK to export the data to a dataset file Exporting Data to MDM Files The method you use to export data depends on the type of data you want to export The type of data you can export can be attribute-independent measurements (such as the measured or simulated data in a setup) or geometry, temperature or other attributedependent data To export geometry, temperature or other attribute-dependent data, you must use a PEL macro Some of the functions used for this purpose are discussed in PEL Functions An example for exporting data in this manner is provided in Exporting the Data Using a PEL (datamanagement) Attribute-Independent Measurements To export attribute-independent measurements to an MDM file: 1 2 Select the DUT and setup Choose File > Export Data > Active Setup or click Export Data in the Measure/Simulate tab The Data Management - Export Data dialog box appears 3 Select MDM Format (mdm) from the Data File Type drop-down list 4 In the File Name field, type in a unique filename or click Browse to select an existing filename The mdm file extension is automatically appended to the filename 30

32 5 6 Note The file path and file name are specified by the IC-CAP system variables MDM_FILE_PATH and MDM_FILE_NAME When exporting, the program automatically sets these variables in the Setup Variables Table Similarly, exporting transforms is controlled by MDM_EXPORT_XFORM_DATA Select the Data Type (Measured or Simulated) If appropriate, select Export Transform Enter a comment file name, if needed Note Use separate files when exporting Measured or Simulated data to an MDM file, eg, idvg_data_measmdm and idvg_data_simmdmyou can specify the name of a comment file by setting the system variable MDM_EXPORT_COMMENT_FILE When set, the program automatically prepends the comment file to the exported data file Click OK to export the data to an MDM file Attribute-Dependent Measurements You can only export non-measurable/simulatable parameters (such as, length, width, or temperature) by using a PEL macro Before exporting any data, you must register these parameters to the MDM file using one of the three PEL functions: icdb_register_con_sweep icdb_register_lin_sweep icdb_register_list_sweep icbd_register_lsync_sweep Some important points to be noted while exporting or importing data: The setup used for importing must have all the input sweeps defined in the MDM file You can import one or more output data You can import all the data in an MDM file, or part of the data, by defining the input sweeps in the setup accordingly You can import the data in any order, independent of the order in which the data is in the MDM file However, if LSYNC data is in the MDM file, you must either access all sweeps with the same LSYNC master sweep or all with a CON sweep You cannot request a LIN sweep (of more than 1 point) for the master and then CON sweeps for others You can, however, access this data by specifying a LIN sweep for the master and LSYNC sweeps for the others You must enter the same constant value for each entry in the LSYNC when making this request You can export the data in all the transforms in the setup, by setting the IC-CAP variable MDM_EXPORT_XFORM_DATA to TRUE Exported transforms are treated as outputs and can only be imported into an output Both measured and simulated data cannot be exported into the same MDM file Data can be exported into an MDM file only from one setup That is, an MDM file cannot have data exported from multiple setups unless all setups have the identical sweep structure and PEL is used to build the MDM file by varying external parameter sweeps Similarly, data from multiple MDM files cannot be imported into the same setup Attribute-dependent measurements or parameters like geometry, temperature can be imported using a parameter mode type P PEL Functions The PEL functions used for exporting the data include: icdb_open/icdbf_open Opens a file for exporting measured data in IC-CAP's data management file format (mdm) For more details, refer to icdb_open (extractionandprog) and icdbf_open (extractionandprog) icdb_close/icdbf_close Closes a file that has been opened with icdb_open/icdbf_open For more details, refer to icdb_close (extractionandprog) and icdbf_close (extractionandprog) icdb_add_comment/icdbf_add_comment Writes an arbitrary comment string to the opened file For more details, refer to icdb_add_comment (extractionandprog) and icdbf_add_comment (extractionandprog) icdb_export_data/icdbf_export_data Exports the measured or simulated data from the specified setup to the opened file Header information containing current information about the values of the registered sweep parameters is automatically appended to the file For more details, refer to icdb_export_data (extractionandprog) and icdbf_export_data (extractionandprog) 31

33 icdb_get_sweep_value/icdbf_get_sweep_value Returns the current value of the specified user sweep at any point in the export loop For more details, refer to icdb_get_sweep_value (extractionandprog) and icdbf_get_sweep_value (extractionandprog) icdb_register_con_sweep/icdbf_register_con_sweep Creates a CON type sweep of an arbitrary parameter in the exported file Intended primarily to create sweeps of parameters that cannot be swept during a measurement Returns the total number of points in all the registered sweeps For more details, refer to icdb_register_con_sweep (extractionandprog) and icdbf_register_con_sweep (extractionandprog) icdb_register_lin_sweep/icdbf_register_lin_sweep Creates a LIN type sweep of an arbitrary parameter in the exported file Intended primarily to create sweeps of parameters that cannot be swept during a measurement Returns the total number of points in all the registered sweeps For more details, refer to icdb_register_lin_sweep (extractionandprog) and icdbf_register_lin_sweep (extractionandprog) icdb_register_list_sweep/icdbf_register_list_sweep Creates a LIST type sweep of an arbitrary parameter in the exported file Intended primarily to create sweeps of parameters that cannot be swept during a measurement Returns the total number of points in all the registered sweeps For more details, refer to icdb_register_list_sweep (extractionandprog) and icdbf_register_list_sweep (extractionandprog) icdb_register_lsync_sweep/icdbf_register_lsync_sweep Creates a LSYNC type sweep of an arbitrary parameter in the exported file Intended primarily to create sweeps of parameters that cannot be swept during a measurement Returns the total number of points in all the registered sweeps For more details, refer to icdb_register_lsync_sweep (extractionandprog) and icdbf_register_lsync_sweep (extractionandprog) See Also Importing Data through MDM (datamanagement) Data Management Examples (datamanagement) MDM File Structure (datamanagement) 32

34 MDM File Structure File and Data Management The MDM file format provides the following advantages: ASCII based Table-based, row-column format with column header lines that make reading easyincludes a list of the inner-most independent variables All data tables have identical shape A header at the top of the file provides an outline of all the data in the file After the header has been parsed, the location of any data group can be computed quickly, permitting rapid location of arbitrary data groups scattered throughout the file Comment lines are denoted by the exclamation character (!) The file extension for the data files is mdm (measured data management) File Header Format The file header contains all the relevant information about the inputs sweeps as well as a listing of all the outputs The header information begins with the BEGIN_HEADER keyword and ends with the END_HEADER keyword The header information is contained in one of four separate sections: ICCAP_INPUTS, ICCAP_OUTPUTS, USER_INPUTS, and ICCAP_VALUES The ICCAP_INPUTS and ICCAP_OUTPUTS sections contain information that would be contained in an IC-CAP setup These portions of the header are mandatory The optional USER_INPUTS section contains sweep information on variables that can't be swept in a traditional IC-CAP setup (such as, Length, Width and Temperature) The optional ICCAP_VALUES section contains parameter and variable data When IC-CAP reads the MDM file, the parameter or variable values are reset to the value in the file If the parameter or variable does not exist, IC-CAP creates a variable by that name in the setup where the file is being read The header structure is as follows: BEGIN_HEADER USER_INPUTS <user_input_name_1> <sweep_type> [<sweep_type_options_list>] <user_input_name_n> <sweep_type> [<sweep_type_options_list>] ICCAP_INPUTS <input_name_1> <mode> [<mode_options_list>] <sweep_type> [<sweep_type_options_list>] <input_name_m> <mode> [<mode_options_list>] <sweep_type> [<sweep_type_options_list>] ICCAP_OUTPUTS <output_name_1> <mode> [<mode_options_list>] <unit> <compliance> <type> <output_name_p> <mode> [<mode_options_list>] <unit> <compliance> <type> ICCAP_VALUES <value_name_1> <value_1> <value_name_q> <value_q> END_HEADER where, <input_name> is a unique but arbitrary name for a user sweep or an IC-CAP sweep <mode> is set to one of the following values: V, I, F, T, P, U, W (inputs) or V, I, C, G, T, S, H, Z, Y, K, A (outputs) <mode_options_list> is a list of fields that depend on the <mode> The following shows the fields for each <mode>: <mode_options_list> 33

35 <mode> Inputs Fields V, U <+ Node><- Node> <Unit> <Compliance> I P W <To Node><From Node> <Unit> <Compliance> <Param Name><Unit> F, T (no options) Outputs File and Data Management <+ Node><- Node> <dbm(d)/watts(w)> <Resistance> <Fund> <Unit> <Compliance> V, N, U <+ Node><- Node> I <To Node><From Node> C, G <High Node><Low Node> T S, H, Z, K, A, Y <Node><Pulse Param> <Port 1><Port 2><AC Ground> <sweep_type> is set to one of the following IC-CAP sweeps: LIN, LOG, SYNC, LIST, CON, AC, HB, EXP, PULSE, PWL, SFFM, SIN, TDR, SEG <sweep_options_list> is a list of fields that depend on the <sweep_type> The following shows the fields for each <sweep_type>: <sweep_options_list> <sweep_type> Fields LIN LOG SYNC LIST CON AC HB EXP PULSE PWL SFFM SIN TDR <sweep order> <start> <stop> <number of points> <step size> <sweep order> <start> <stop> <number of points> <sweep scale (D or O)> <total number of points> <ratio> <offset> <master sweep> <sweep order> <n = number of values> <value1> <value2> <valuen> <value> <magnitude> <phase> <sweep order> <value> <order> <number of points> <initial value> <pulsed value> <rise delay> <rise const> <fall delay> <fall const> <initial value> <pulsed value> <delay time> <rise time> <fall time> <pulse width> <period> <number of pairs> <time 1> <value 1> <time 7> <value 7> <start time> <repeat times> <offset> <amplitude> <carrier frequency> <modul index> <signal frequency> <offset v> <amplitude> <frequency> <delay time> <damp factor> <phase> <initial value> <pulsed value> <delay time> <rise time> <fall time> <pulse width> <period> <resistance> SEG <sweep order> <number of segments> <number of points> <value 1> <value 10> <unit> is set to the IC-CAP instrument unit associated with the output (use DEFAULT for unspecified) <compliance> is the compliance limit for the output (use DEFAULT for unspecified) <type> is a single character-m, S, or B M indicates that the output, if created from an MDM file, is for measured data only S indicates simulated data only and B indicates either The data in the ICCAP_OUTPUTS block is restricted to data that can exist in a single IC- CAP setup For example, since forward and reverse gummel DC measurements on a bipolar device are measured with different sweeps, the file headers for each of these would be incompatible In order to make all the data within a file importable into a standard IC-CAP setup, two separate files (one for each setup) would be required to store this data File Data Format The data within a file is organized into multiple groups of tabular data Each group of tabular data is arranged in columns representing the innermost sweep data and its associated dependent data The innermost sweep is always the first column Any inputs with SYNC sweep type and with the innermost sweep as its master are listed next Dependent data may be either real or complex, depending on the following rules: C, G, and T output modes are always real-therefore require only 1 column TwoPort (S, H, Z, Y, K, or A) output modes are always 2-port complex-therefore require 8 columns V and I output modes depend on the sweep types of the inputs specified in the setup If any of the inputs in a setup have sweep type AC or HB, V and I output modes require 2 columns-one for real and one for imaginary data For all other setups, V and I output modes require a single real column Any output mode not covered in the preceding rules have 2 columns for complex 34

36 data File and Data Management For real data, the tabular data is structured as follows: <input_name> <output_name 1> <output_name 2> <output_name n> input1 (output 1) 1 (output 2) 1 (output n) 1 inputm (output 1) m (output 2) m (output n) m For matrix data (such as, multiport data), the data format for a single output is structured as follows: <in_name> R:<out_name>(1,1) I:<out_name>(1,1) R:<out_name>(n,m) I:<out_name>(n,m) input1 real(output 1,1)1 imag(output 1,1) 1 real(output n,m) 1 imag(output n,m) 1 inputk real(output 1,1) k imag(output 1,1) k real(output n,m) k imag(output n,m) k Each group of tabular data is preceded by a list of each remaining input name (ie, all inputs except the innermost sweep) and its current value for the data group in question Each group begins with the keyword BEGIN_DB and ends with the END_DB keyword Note that the IC-CAP inputs always vary faster than the user inputs The file structure of each group is as follows: BEGIN_DB <user_input_1> <user_value_1> <user_input_n> <user_value_n> <iccap_input_2> <iccap_value_2> <iccap_input_m> <iccap_value_m> [tabular data goes here] END_DB Since the import function in IC-CAP determines the size of the dataset from the header information alone, the data following the header must be consistent with the description in the header After parsing the header, IC-CAP knows exactly how many data blocks should be contained in the file, as well as the number of lines occupied by a single data block If any data blocks are missing, or if the number of lines within a data block are inconsistent with the header, the data import fails File Examples This section contains three example mdm files that were generated with IC-CAP's export functions Example 1: Forward Gummel Data The Forward Gummel Data example (code listing below) shows how some forward Gummel data can be stored in an mdm file In this example, the variables vb and Temp are being swept The variable vb is the inner most (fastest varying) sweep Since vc is synchronized to vb, the values of vc must appear in each data block The actual ordering of the sweeps within the USER_INPUTS, ICCAP_INPUTS or ICCAP_OUTPUTS block, as well as the ordering of the variables in the secondary header (USER_VAR, ICCAP_VAR), is immaterial Example: Forward Gummel Data! VERSION = 600 BEGIN_HEADER ICCAP_INPUTS vb V B GROUND SMU1 001 LIN ve V E GROUND GND 01 CON 0 vc V C GROUND SMU2 02 SYNC 1 0 vb ICCAP_OUTPUTS ib I B GROUND SMU1 B ic I C GROUND SMU2 B END_HEADER BEGIN_DB ICCAP_VAR ve 0 #vb vc ib ic e e e e

37 e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e e END_DB Example 2: Saving Transformed Data File and Data Management The Saving Transformed Data example (code listing below) shows how some forward Gummel data can be stored along with additional data beta, which has been computed from the measured data Since the beta data has been computed rather than measured, information such as node connections is not relevant The IC-CAP import functions accept outputs in the ICCAP_OUTPUTS block in the abbreviated form shown in the example for beta, as well as in the standard form for measured quantities, such as ib and ic In order to differentiate between real data (such as, current, voltage, and capacitance) and 2-port data (such as, s-parameters) non-measured quantities must have one of two mode types listed after the variable name: Real quantities should use V as the generic real data mode type Two-port quantities should use S as the generic 2-port mode type Example: Saving Transformed Data! VERSION = 600 BEGIN_HEADER ICCAP_INPUTS vb V B GROUND SMU1 001 LIN ve V E GROUND GND 01 CON 0 vc V C GROUND SMU2 02 SYNC 1 0 vb ICCAP_OUTPUTS ib I B GROUND SMU1 B ic I C GROUND SMU2 B beta U END_HEADER BEGIN_DB ICCAP_VAR ve 0 vb vc ib ic R:beta(1,1) I:beta(1,1) e e e e

38 e e e e e e e e e e e e e e END_DB Example 3: 2-Port Data The 2-Port Data (code listing below) example shows how some 2-port data is stored in an mdm file This a simple example with only one data block Multiple blocks of 2-port data are easily handled using the same approach as illustrated in the Forward Gummel data example Example: 2-Port Data BEGIN_HEADER ICCAP_INPUTS freq F LIN 1 1e+09 2e vd V D 0 CON 2 vg V G 0 CON 0 vs V S 0 CON 0 ICCAP_OUTPUTS s S G D 0 END_HEADER BEGIN_DB ICCAP_VAR vd 2 ICCAP_VAR vg 0 ICCAP_VAR vs 0 freq R:s(1,1) I:s(1,1) R:s(1,2) I:s(1,2) R:s(2,1) I:s(2,1) R:s(2,2) I:s(2,2) 1e e e e e e e e e e e e e e e e e e e e END_DB Tips To view the header of an MDM data file, select the Setup cell in the dialog box, enter the corresponding MDM filename, then click View To create the inputs and outputs for a new setup from the header of an MDM file, first create a new setup, select the setup name in the dialog box, enter the corresponding MDM filename, and click Create 37

39 Data Management Examples File and Data Management The data management example is located in the product directory: ${ICCAP_ROOT}/examples/demo_features/3_MEAS_ORGANIZE_n_VERIFY_DATA/2_mdm_basics/2_xforms_2_dbmdl The example model has two setups in the DUT dc_at_temps: fgummel_exp and fgummel_imp_all Exporting the Data Using a PEL In the example, a PEL transform is used to export non-measurable/simulatable attributedependent data The exporting data example uses the setup fgummel_exp The PEL transform, mdm_export, is available in the setup and in this example, exports temperature In the macro (code listing below) line 32 registers a non-measurable/simulatable attribute called Temp The sweep type is LIN with a start, stop and total number of points of TSTART = -50, TSTOP = 50 and TNUM = 11 The sweep order is 1 This function also returns the number of points In lines 50 through 69, the setup (defined by the variable path ) is simulated and exported (line 67) The MDM file exported in the example has 11 data-blocks corresponding to 11 different simulations/measurements that were made at the different temperatures Example: Exporting Data Using a PEL! Here is a simple data export example which illustrates the use of the icdb_xxx! commands Although simulated data is exported in this example, it is easy! to see how a simple replacement of the "Simulate" command inside the main! export loop with a "Measure" would yield a data file with temperature dep-! endent Gummel-Poon measurement data MDM_EXPORT_XFORM_DATA=1! flag to also export transform data path = "/xforms_2_db/dc_at_temps/fgummel_exp"!path to the export setup LINPUT "enter filename for database file",val$(filename),filename file_exists=system("ls "&VAL$(filename)) IF file_exists==0 THEN LINPUT "--WARNING-- overwriting existing file '"&VAL$(filename)&"'","ok",dummy! This command opens the file that the data will be stored in! The function icdb_open returns nothing dummy=icdb_open(val$(filename))! This command adds a comment line to the data file dummy = icdb_add_comment(" Data management file for forward gummel data") dummy = icdb_add_comment("")! The next data base function tells IC-CAP to define a linear sweep over! temperature The function arguments are: sweep order, sweep start,! sweep stop, number of points and sweep name The function returns the! cumulative number of points in all the registered user sweeps The value! "num_pts" is useful for setting up the export loop!note: In this example the icdb_register_lin_sweep and icdb_register_list_sweep! commands will generate the same file One of the command must remain! commented out num_pts=icdb_register_lin_sweep(1, TSTART, TSTOP, TNUM, "Temp")! The next data base function tells IC-CAP to define a list sweep over! temperature The function arguments are: sweep order, sweep name,! and IC-CAP variable array name The function returns the cumulative! number of points in all the registered user sweeps The value "num_pts"! is useful for setting up the export loop!num_pts=icdb_register_list_sweep(1, "Temp", "TEMP_LIST") ICCAP_FUNC(path&"/ibicvsvb", "Display Plot") ICCAP_FUNC(path&"/ibicvsvb", "Autoscale OnOff")! Here is the "export" loop The number of loop iterations should be consistent! with the dimension of the user sweep space For example, if a LIST sweep with! 10 points is defined and a LIN sweep with 5 points is defined, then 5*10 = 50! iterations of the export loop must be completed The export functions will! error out if too many iterations are attempted However, if too few iter-! ations are performed, the problem will go undetected until an import is tried! Use the return value of the icdb_register_xxx_sweep to set the maximum number! of iterations This should minimize the possibility of any errors count=0 while count < num_pts 38

40 ! Once a sweep has been registered, IC-CAP automatically internally updates! the values of all the user sweep values after each call to icdb_export_data! The function icdb_get_sweep_value provides useful means of getting the! current value of any sweep variable The function arguments are the index! of the desired sweep value and the sweep name TEMP = icdb_get_sweep_value(count, "Temp")! Now that we've updated the temperature for the simulator, we can! re-simulate to compute a new set of data ICCAP_FUNC(path, "Simulate")! This call exports the simulated data ("S") in the current setup out! to the file Measured data can be exported by specifying "M" for the! second argument The first call to icdb_export_data writes the header! information as well as the setup data The function icdb_export_data! returns nothing To reference a setup other than the one under which! a transform is executing, the full path should be passed in as the! first arguement of icdb_export_data dummy = icdb_export_data("", "S") count=count+1 end while! This function closes the file opened with icdb_open Note, that only one! file can be opened at a time The first opened file must be closed before! a second one is opened The function icdb_close returns nothing dummy=icdb_close() ICCAP_FUNC(path&"/ibicvsvb", "Autoscale OnOff") LINPUT "Run Import Data in Setup fgummel_imp_all and load the beta curves from the data base file too",dummy! The following code guarantees that the output of this transform will not be! exported to the mdm file if MDM_EXPORT_XFORM_DATA is set to TRUE COMPLEX tmp[1] RETURN tmp Importing the Data The importing data example uses the setup fgummel_imp_all The setup has the nonsimulatable attribute Temp defined as a Parameter mode You can import the data using the Import Data button in the setup If you wish, you can import a slice of the data For example you can import data at temperatures 50, 100, 150 for vb between 300 mv and 700 mv 39

41 Database Connection Manager The new Database Connection Manager in IC-CAP provides a mechanism for rapid data storage, data retrieval, and powerful generic querying, thus, making it an ideal solution for scaling larger amounts of data Currently, the Database Connection Manager supports the ability to create and store data in SQLite and MySQL databases The Database Connection Manager also provides various APIs (designed to work within the IC-CAP Parameter Extraction language (PEL)) using which you can query and retrieve the stored data The Database Connection Manager provides the following key features and benefits: Faster data search and identification Supports SQlite and MySQL databases Utilizes its own schema for storing the IC-CAP data Customizable indexing mechanism that allows you to search the data according to a schema as per the industry standard Quick access to MDM data based on the values within the MDM Quick access to WaferPro data Ability to store several runs of WaferPro data within the database This section provides information on how you can configure and get started with the Database Connection Manager: Configuring Database with Database Connection Manager (datamanagement) Working with Database Connection Manager (datamanagement) Database Query Syntax (datamanagement) Using Database Connection Manager APIs (datamanagement) 40

42 Configuring Database with Database Connection Manager Before beginning with Database Connection Manager, you must configure and create a link to MySQL databases The Database Connection Manager works with SQLite as out of the box solution and do not require any additional configuration This section provides information on how you can configure MySQL on Windows, Linux, and Solaris operating systems following the links below: Configuring MySQL on Windows (datamanagement) Configuring MySQL on Linux (datamanagement) Configuring MySQL on Solaris (datamanagement) Configuring MySQL on Windows The following sections provide information on how you can create and configure the plugin to link MySQL on Windows Download and install MySQL on Windows Download and install the MySQL installer for 32-bit Windows available at If MySQL is already installed on your system, or if you are installing the 64-bit version of MySQL, you need to install the Client C API Library only The 32-bit version of these libraries are required to create the plugin For the 32-bit version of MySQL also, ensure that you include the Client C API Library in your installation, as shown in the following screenshot To install only the development library, ensure to deselect the Launch MySQL Configuration option in the last screen of the installer Configuring Qt and Building the Plugin After the MySQL installation is complete, perform the following steps to configure Qt: 1 Download the qt-win-opensource-463-vs2008exe file for Visual Studio 2008 from QT FTP Archive 2 Install the downloaded qt-win-opensource-463-vs2008exe file By default, the Qt 463 is installed at C:\Qt\463 filepath 3 Navigate to Start > Programs > Qt by Nokia v463 > QT 463 Command Prompt to open the Qt 463 command prompt 4 In the Qt 463 Command Prompt, change the directory to %QTDIR%\src\plugins\sqldrivers\mysql 41

43 5 File and Data Management Set the QTDIR variable to the QT installation directory, for example, c:\qt\463 6 Execute the following command: %QTDIR%\bin\qmake -o Makefile "INCLUDEPATH+=\"C:\Program Files\MySQL\MySQL Server 56\include\"" "LIBS+=\"C:\Program Files\MySQL\MySQL Server 56\lib\libmysqllib"" mysqlpro The following screenshot displays the above command in the Qt 463 Command Prompt window Then, execute the nmake command to build the qsqlmysql4dll plugin in the %QTDIR%\plugins\sqldrivers directory Copy the qsqlmysql4dll file and paste it in the %ICCAP_ROOT%\bin\plugins\qt\sqldrivers directory Copy the libmysqllib file which is in the lib directory of the MySQL installed path and paste it in the %ICCAP_ROOT%\bin directory Now, launch Database Connection Manager from Tools menu in IC-CAP Main window You can access the MySQL option from the Select Database Connection Type dropdown list See Also Configuring MySQL on Linux (datamanagement) Configuring MySQL on Solaris (datamanagement) Configuring MySQL on Linux To build the plugin for linking MySQL on Linux, you require development libraries package instead of full MySQL installation There are various packages available for Linux, however, in this example, we have used the Redhat 4 package for supported IC-CAP Linux platforms Note You may require a different package depending on your platform and versions of MySQL Download and Install MySQL Development Libraries Download and install the appropriate Development Libraries from In this example, we have downloaded and installed Development libraries under the Oracle Linux 4 & 5 section, specifically, the MySQL-devel rhel4i386rpm distribution You must install this using rpm If it conflicts with an existing MySQL installation, you may find the equivalent development package for your installation (if it is not already installed), or uninstall the conflicting version (and any applications depending on it) The development package will create a /usr/include/mysql directory and a /usr/lib/mysql directory with required libraries to link against Other distributions may install these to different locations Note An alternative is to download the source to MYSQL and compile it completely to avoid having an install conflicting version Configuring QT 42

44 Note If you already have a 463 distribution of Qt on your Linux box, or you find a downloadable rpm for Qt 463, you can skip this section and build the plugin directly as shown in Building the plugin section To configure Qt 463, perform the following steps: 1 Navigate to and click on Visit our FTP archive section at the bottom of the page 2 Under the FTP Index, go to qt/source directory 3 Download any qt-everywhere 463 package (either in zip or tar), for example, qteverywhere-opensource-src-463targz or qt-everywhere-opensource-src- 463zip 4 Create a clean working directory and unpackage the source code Notes This distribution does not include any binaries so you may have to build it It is recommended to use the same gcc compiler as required for IC-CAP userc compilation These instructions compile the minimal distribution that can build the required MySQL plugin It is applicable on a 64-bit machine as long as 32-bit versions of the X libraries exist and 32- bit versions of other required libraries exist However, if possible, perform the compilation on a 32-bit machine IC-CAP requires a 32-bit version of the MySQL plugin 5 Change the working directory to the unpackaged qt-everywhere-opensource-src- 463 directory 6 Execute the following command: /configure -release -prefix-install -prefix /qt_target -platform linux-g opensource -no-largefile -no-accessibility -no-qt3support -no-xmlpatterns -no-multimedia -no-audiobackend -no-phonon -no-phonon-backend -no-svg -no-webkit -no-javascript-jit -no-script -noscripttools -no-declarative -no-gif -no-libtiff -no-libpng -no-libmng -no-libjpeg -noopenssl -no-rpath -no-nis -no-cups -no-iconv -no-pch -no-dbus -no-separate-debug-info -nogtkstyle -no-nas-sound -no-opengl -no-openvg -no-sm -no-xshape -no-xsync -no-xinerama -noxcursor -no-xfixes -no-xrandr -no-xrender -no-mitshm -no-fontconfig -no-xinput -no-xkb -noglib Accept the displayed lgpl license agreement Now, to make Qt, execute the gmake command Note It is not mandatory to make the install target Building the Plugin After the Qt configuration is complete, you can build the libqsqlmysqlso plugin to link MySQl with Database Connection Manager To build the plugin, perform the following steps: 1 Set the QTDIR variable to the location you unpackaged the qt-everywhereopensource-src-463 package as shown in the following example 2 export QTDIR=/tmp/ qt-everywhere-opensource-src-463 Execute the following command: $QTDIR/bin/qmake -o Makefile "INCLUDEPATH+=\include" "LIBS+=-L -lmysqlclient_r" mysqlpro If you have installed the MySQL development package, as described previously, then execute the following command: 3 4 $QTDIR/bin/qmake "INCLUDEPATH+=/usr/include/mysql" "LIBS+=-L/usr/lib/mysql -lmysqlclient_r" mysqlpro Execute the gmake command This step builds the libqsqlmysqlso plugin in the $QTDIR\plugins\sqldrivers directory Now, copy the libqsqlmysqlso plugin to your %ICCP_ROOT%\bin\plugins\qt\sqldrivers directory to be able to use MySQL with Database Connection Manager on Linux Now, launch Database Connection Manager from Tools menu in IC-CAP Main window You can access the MySQL option from the Select Database Connection Type dropdown list See Also Configuring MySQL on Windows (datamanagement) Configuring MySQL on Solaris (datamanagement) 43

45 Configuring MySQL on Solaris File and Data Management To build the plugin for linking MySQL on Solaris, you may not require full MySQL installation If you have the tar distribution, you can then open it and point at the required libraries/include files to build the plugin Download and Install MySQL Solaris Package To download and configure MySQL for Sun Solaris, perform the following steps: Navigate to and go to the Downloads section Click Downloads and choose Sun Solaris IC-CAP requires a 32-bit library to link against, but mysql no longer provides a Solaris bit distribution Click on the link that displays Looking for previous GA versions In this location, you will find a mysql-5160-solairs10-sparctargz package If a newer version is required, you must download the source to MySQL and compile it on Solaris using 32-bit mode Download the mysql-5160-solairs10-sparctargz package Open the tar file and make a note of the directory Configuring QT Note If you already have a 32-bit 463 distribution of Qt on your Solaris box, or you find a downloadable package for Qt 463, you can skip this section and build the plugin directly as shown in Building the plugin section To configure Qt 463, perform the following steps: 1 Navigate to and click on Visit our FTP archive section at the bottom of the page 2 Under the FTP Index, go to qt/source directory 3 Download any qt-everywhere 463 package (either in zip or tar), for example, qteverywhere-opensource-src-463targz or qt-everywhere-opensource-src- 463zip 4 Create a clean working directory and unpackage the source code Notes This distribution does not include any binaries so you may have to build it It is recommended to use the same gcc compiler as required for IC-CAP userc compilation These instructions compile the minimal distribution that can build the required MySQL plugin It is applicable on a 64-bit machine as long as 32-bit versions of the X libraries exist and 32- bit versions of other required libraries exist However, if possible, perform the compilation on a 32-bit machine IC-CAP requires a 32-bit version of the MySQL plugin 5 Change the working directory to the unpackaged qt-everywhere-opensource-src- 463 directory 6 Execute the following command: /configure -release -prefix-install -prefix /qt_target -platform solaris-cc -opensource - no-largefile -no-accessibility -no-qt3support -no-xmlpatterns -no-multimedia -no-audiobackend -no-phonon -no-phonon-backend -no-svg -no-webkit -no-javascript-jit -no-script -noscripttools -no-declarative -no-gif -no-libtiff -no-libpng -no-libmng -no-libjpeg -noopenssl -no-rpath -no-nis -no-cups -no-iconv -no-pch -no-dbus -no-separate-debug-info -nogtkstyle -no-nas-sound -no-opengl -no-openvg -no-sm -no-xshape -no-xsync -no-xinerama -noxcursor -no-xfixes -no-xrandr -no-xrender -no-mitshm -no-fontconfig -no-xinput -no-xkb -noglib Accept the displayed lgpl license agreement Now, to make Qt, execute the gmake command Note It is not mandatory to make the install target Building the Plugin After the Qt configuration is complete, you can build the libqsqlmysqlso plugin to link MySQl with Database Connection Manager To build the plugin, perform the following steps: 1 Set the QTDIR variable to the location you unpackaged the qt-everywhereopensource-src-463 package as shown in the following example 2 export QTDIR=/tmp/ qt-everywhere-opensource-src-463 Execute the following command: 44

46 $QTDIR/bin/qmake -o Makefile "INCLUDEPATH+=/include" "LIBS+=-L/lib -lmysqlclient_r" mysqlpro For example, if you opened the MYSQL package as shown previously in /tmp, then execute the following command: 3 4 $QTDIR/bin/qmake "INCLUDEPATH+=/tmp/mysql-5160-solaris10-sparc/include" "LIBS+=- L/tmp/mysql-5160-solaris10-sparc/lib -lmysqlclient_r" mysqlpro Execute the gmake command This step builds the libqsqlmysqlso plugin in the $QTDIR\plugins\sqldrivers directory Now, copy the libqsqlmysqlso plugin to your %ICCP_ROOT%\bin\plugins\qt\sqldrivers directory to be able to use MySQL with Database Connection Manager on Linux Now, launch Database Connection Manager from Tools menu in IC-CAP Main window You can access the MySQL option from the Select Database Connection Type dropdown list See Also Configuring MySQL on Windows (datamanagement) Configuring MySQL on Linux (datamanagement) 45

47 Working with Database Connection Manager The Database Connection Manager allows you to store the simulated and measured data into SQLite or MySQL database The stored data can be retrieved or scaled using the Database Connection Manager APIs or Data Processing and Selection Tool (DataPro) Accessing Database Connection Manager The Database Connection Manager can be opened from IC-CAP Main window It can also be invoked from the IC-CAP Wafer Professional (WaferPro) (waferpro) and Data Processing and Selection Tool (DataPro) (extractionandprog) applications To open the Database Connection Manager from IC-CAP Main window, choose Database Connection Manager from Tools menu When you invoke the Database Connection Manager, the Manage Database Connection window is displayed, as shown in the following figure The Manage Database Connection window allows you perform the following tasks: Add a Database Connection Edit a Database Connection Remove a Database Connection Check a Database Connection Add a Database Connection You can create a new database connection or use an existing connection to connect to a database To add a database connection: 1 Click Add New in the Manage Database Connections window The Add Database Connection window is displayed You can create a database connection for SQLite or MYSQL database By default, the database connection type is set to SQLite 46

48 1 2 Enter the name of the new connection in the Connection Name field The Connection Name is a string which represents the name of the connection using which you can connect to the database By default, the connection name is Connection_0, for the first connection name It gets incremented by 1 for subsequent connections You can specify a connection name as per your requirement To add a database connection for SQLite Select the database as SQLITE from the Select Database Connection Type dropdown list Specify the Database File Path, where you want to store the database Click OK To add a database connection for MYSQL Before adding a database connection for MYSQL, ensure that MYSQL is configure and linked with Database Connection Manager, as described in Configuring Database with Database Connection Manager (datamanagement) section 1 Select the database as MYSQL from the Select Database Connection Type dropdown list 2 Enter the Hostname which is the machine on which the database is installed 3 Specify the Port on the machine through which you can connect to the database 4 Enter the Database Name which is the name of the database you wish to create or 47

49 an existing database you want connect to 5 Specify Database Username and Database Password to connect to the selected database 6 Click OK The added database connection is displayed in the Manage Database Connection window, as shown in the following figure Editing a Database Connection You can edit a previously created database connection To edit a database connection: 1 Select a database connection in the Manage Database Connections window 48

50 1 2 3 Click Edit The Edit Database Connection window is displayed Modify the fields and click OK Removing a Database Connection To remove a database: 1 2 Select a database connection in the Manage Database Connections window Click Remove The Remove Database Connection prompt displays that the selected database is removed Check a Database Connection You can check for the validity of a database connection from the Manage Database Connections window To check a database: 1 2 Select a database connection Click Check Connection The Check Database Connection prompt displays the selected database connection is successful or failed See Also Using Database Connection Manager APIs (datamanagement) 49