Nexus 5000.4.9 Release Notes

Nexus® and VIP® Software Version 5000.4.9 Release Notes

Contents

What’s In This Release ...... 2

Introduction ...... 4

System Requirements ...... 5

Third Party Applications ...... 10

International Trade Compliance...... 37

Installation ...... 39

Licensing ...... 54

Running the Software ...... 56

Configuring Linux Systems to Run Parallel Jobs ...... 57

Enhancements and New Functionality ...... 66

Fixed Issues ...... 69

Known Issues...... 77

Contacting Landmark Customer Support ...... 81

5000.4.9 Page 1 of 84 July 2014 Nexus® and VIP® Software Release Notes

What’s In This Release

The 5000.4.9 release of Nexus® and VIP® software provides new functionality and bug fixes to prior releases of the software.

To go directly to the enhancements, bug fixes, and known issues for the Nexus® and VIP® software applications, click on the blue links below:

New Functionality

Nexus Simulator SimDataStudio™ SurfNet™ Nexus Desktop™

Fixed Problems

Nexus Simulator SimDataStudio™ SurfNet™ Nexus Desktop, Job Submittal, and Installation Nexus View Documentation

Known Issues

General Nexus Simulator VIP Nexus Desktop/Job Submission SimDataStudio™ Nexus View SimConvert SurfNet™ Documentation SimResults™

5000.4.9 Page 2 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

An Introduction to the Nexus® and VIP® software release, as well as System Requirements, Installation Instructions, and Licensing Information are also provided in this document.

After their initial release, updates to these release notes may be provided on the Landmark Software Manager (LSM) site. The latest version of the Nexus® 5000.4.9 Release Notes can be downloaded from the LSM site at the following link: https://esd.halliburton.com/download/download.jsp#Home

5000.4.9 Page 3 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Introduction

The Nexus® and VIP® R5000.4.9 software release is a point product release which includes improved versions of SurfNet™, Nexus® View, SimConvert™, SimDataStudio™, and the Nexus® and VIP® simulators. The primary platforms for this software are Windows 7 64-bit, and Red Hat EL 5.3 64-bit. Secondary platforms are Red Hat EL 4U6 64-bit and Windows Server 2008 64-bit.

Remote display options were not tested in this release.

5000.4.9 Page 4 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” System Requirements

Windows Platform

Hardware Requirements

The following table lists hardware requirements for Windows workstations running Nexus® and VIP® 5000.4.9 software. The software runs on the recommended requirements listed. Extremely large datasets generally require computers with more physical memory than the minimum recommendation.

Hardware Recommended Configuration

CPU Intel Xeon E5-2600, or Xeon E5-2600 v2 series processor

Memory (RAM) 12 GB or greater

Hard Disk 500 GB or more free space.

Display Dual monitor in TwinView: 1920 x 1200 per monitor Color Depth: True Color (32-bit)

Graphics Card See the Graphics Cards section below.

Installation Device Not required for LSM (electronic software delivery) Drive CD/DVD (in case you order the software)

Graphics Cards

The following graphics cards were tested by the Nexus® Quality Management Team on Windows 7 64-bit workstations and can be expected to perform adequately.

• Nexus® software on laptops - HP Elitebook 8540w, with NVIDIA Quadro FX 880M, 1.00 GB. This card was tested with version 8.17.11.9805 of the NVIDIA driver for Windows 7 64-bit systems.

• Windows 7 Workstation - Quadro FX 5800 card. This card was tested with the following NVIDIA Quadro FX 5800 64-bit driver version: 8.15.11.9045

• Windows 7 Workstation - Quadro FX 4800 card. This card was tested with the following NVIDIA Quadro FX 4800 64-bit driver version: 8.17.12.5957

5000.4.9 Page 5 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” It is recommended that the Nexus® software that requires high-end graphics cards, such as the Nexus® View software, run only on the tested graphic cards listed above. Nexus® software does not currently support ATI cards on desktops or laptops.

Software Requirements

The table below lists the software requirements necessary to run Nexus® and VIP® 5000.4.9 on Windows workstations.

Software Version (for PC Client) Required By Included in Nexus and VIP 5000.4.9 CD

Operating Windows 7 64-bit All products. No. Systems Windows Server 2008 64- bit** **For simulator-only installations.

Connectivity Hummingbird Exceed and GridGenr, Array No. Software Exceed3D 14 or higher. The Calculator, Grid Nexus-VIP applications Calculator, Region should work with earlier Calculator, Desktop versions of Exceed. PVT, PlotView, 3DView

License LAM 5000.0.3.0 All Landmark products. No. Management The installation program and the documentation for LAM 5000.0.3.0 can be downloaded from the Landmark Software Manager (LSM).

Document Adobe Reader 7.x or later All Products No. Viewer

5000.4.9 Page 6 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

MKS MKS Toolkit for Enterprise Nexus and VIP Yes. Platform Developers, version 9.x ..\Nexus- Components VIP5000.4.9\MKS94 (formerly (Prior versions of Nutcracker Nutcracker) or MKS Toolkit should be uninstalled before installing Nexus.)

Message Intel MPI Library Runtime Nexus and VIP for Yes. Passing Environment 4.0 Update 3 parallel processing job ..\Nexus-VIP 5000.4.9\Intel- Environment for Windows OS submission. MPI (MPI) (Installed automatically.)

Linux Platform

Hardware Requirements

The following table lists the hardware requirements for Linux workstations running 5000.4.9 Nexus® and VIP® software. The software runs on the recommended requirements listed below.

Hardware Recommended Configuration

CPU Intel Xeon E5-2600 or Xeon E5-2600 v2 series processor

Memory (RAM) 12 GB or greater

Hard Disk 500 GB or more free space.

Display Dual monitor in TwinView: 1920 x 1200 per monitor Color Depth: True Color (32-bit)

Graphics Card See the Graphics Cards section below.

Installation Device Not required for LSM (electronic software delivery) Drive CD/DVD (in case you order the software)

5000.4.9 Page 7 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Graphics Cards

The following graphics cards were tested by the Nexus®-VIP® Quality Management team for the Linux workstation. These cards can be expected to perform adequately.

• NVIDIA Quadro FX 4600 • NVIDIA Quadro FX 4500 • NVIDIA Quadro FX 3450/4000 SDI • NVIDIA Quadro FX 3500

These cards were tested with version 185.18.36 of the NVIDIA driver for Linux. NVIDIA Quadro FX 4500 was also tested with version 270.41.06 of the NVIDIA driver for Linux. It is recommended that Nexus®-VIP® applications that require high-end cards, such as the Nexus® View software run only on the tested graphic cards listed above. Nexus®-VIP® software does not currently support ATI cards.

Software Requirements

The table below lists software requirements for Nexus®-VIP® 5000.4.9 on Linux. Some of these software requirements pertain to server installations only.

Software Version Required By Included in Nexus-VIP 5000.4.9 CD

Operating System Red Hat Enterprise Linux All products. No. Workstation 5 64-bit. Update 3 or later.

Desktop Gnome or KDE All products. No. Environment

License LAM 5000.0.3.0 All Landmark No. Management products. The installation program and the documentation for LAM 5000.0.3.0 can be downloaded from the Landmark Software Manager (LSM).

5000.4.9 Page 8 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Document Viewer All Products No.

Message Passing Intel MPI Library Runtime Nexus and VIP Yes. Environment (MPI) Environment 4.0 Update for parallel job ../Nexus-VIP 5000.4.9/ 3 for Linux OS submission. Nexussimulators/LinuxEM64/ Intel-MPI

(Installed automatically.)

5000.4.9 Page 9 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Third Party Applications

Halliburton uses various third-party applications in the development of its software.

Halliburton acknowledges that certain third party code has been bundled with, or embedded in, its software. The licensors of this third party code, and the terms and conditions of their respective licenses, are found below. The following information is provided in accordance with the software manufacturer’s terms of usage.

Important Disclaimer: Halliburton programs and documentation may provide links to External Web sites and access to content, products, and services from third parties. Halliburton is not responsible for the availability of, or any content provided on, third- party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Halliburton is not responsible for: (a) the quality of third- party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Halliburton is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

5000.4.9 Page 10 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Permission is hereby granted to use, copy, modify, and distribute this software (or portions thereof) for any purpose, without fee, subject to these conditions: (1) If any part of the source code for this software is distributed, then this README file must be included, with this copyright and no-warranty notice unaltered; and any additions, deletions, or changes to the original files must be clearly indicated in accompanying documentation. (2) If only executable code is distributed, then the accompanying documentation must state that "this software is based in part on the work of the Independent JPEG Group". (3) Permission for use of this software is granted only if the user accepts full responsibility for any undesirable consequences; the authors accept NO LIABILITY for damages of any kind.

Sun Microsystems: Copyright © 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All Java Runtime Environ- rights reserved. U.S. ment (JRE) Sun Microsystems, Inc. Binary Code License agreement Java Architecture For XML Binding (JAXB) This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/ Java 3D

JavaBeans Activation Framework (JAF)

Java Media Framework (JMF)

5000.4.9 Page 11 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Oracle Corporation: Portions of this software contain Oracle JDBC drivers open source software Copyright © 2002, Oracle Corporation. All rights reserved. Oracle JDBC Thin Driver Please note that for the purposes of this open source software: Classes 1. You shall have no right to distribute the open source, and Oracle is a third party beneficiary of this agreement as it relates to Oracle JDBC drivers.

2. Oracle's technical support organization will not provide technical support, phone support, or updates to you for Oracle JDBC drivers licensed under this agreement.

3. “Open Source” software - software available without charge for use, modification and distribution - is often licensed under terms that require the user to make the user's modifications to the Open Source software or any software that the user 'combines' with the Open Source software freely available in source code form. If you use Open Source software in conjunction with the programs, you must ensure that your use does not: (i) create, or purport to create, obligations of us with respect to the Oracle programs; or (ii) grant, or purport to grant, to any third party any rights to or immunities under our intellectual property or proprietary rights in the Oracle programs. For example, you may not develop a software program using an Oracle program and an Open Source program where such use results in a program file(s) that contains code from both the Oracle program and the Open Source program (including without limitation libraries) if the Open Source program is licensed under a license that requires any “modifications” be made freely available. You also may not combine the Oracle program with programs licensed under the GNU General Public License (“GPL”) in any manner that could cause, or could be interpreted or asserted to cause, the Oracle program or any modifications thereto to become subject to the terms of the GPL.

5000.4.9 Page 12 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

2. Oracle's technical support organization will not provide technical support, phone support, or updates to you for Oracle JDBC drivers licensed under this agreement.

3. "Open Source" software - software available without charge for use, modification and distribution - is often licensed under terms that require the user to make the user's modifications to the Open Source software or any software that the user 'combines' with the Open Source software freely available in source code form. If you use Open Source software in conjunction with the programs, you must ensure that your use does not: (i) create, or purport to create, obligations of us with respect to the Oracle programs; or (ii) grant, or purport to grant, to any third party any rights to or immunities under our intellectual property or proprietary rights in the Oracle programs. For example, you may not develop a software program using an Oracle program and an Open Source program where such use results in a program file(s) that contains code from both the Oracle program and the Open Source program (including without limitation libraries) if the Open Source program is licensed under a license that requires any "modifications" be made freely available. You also may not combine the Oracle program with programs licensed under the GNU General Public License ("GPL") in any manner that could cause, or could be interpreted or asserted to cause, the Oracle program or any modifications thereto to become subject to the terms of the GPL.

5000.4.9 Page 13 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Sun Microsystems: Copyright © 2002 Sun Microsystems, Inc. All Rights Reserved. 4150 Network Circle, Santa Clara, California 95054 U.S.A. Java Architecture For XML Binding (JAXB) Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Java 3D • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. • Redistribution 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 Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote products derived from this software without specific prior written permission.

This software is provided “AS IS,” without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICU- LAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. (“SUN”) AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODI- FYING OR DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

You acknowledge that this software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility.

5000.4.9 Page 14 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Sun Microsystems: Copyright © 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, Califor- nia 94303, U.S.A. All rights reserved. Java Runtime Environ- ment (JRE) Sun Microsystems, Inc. has intellectual property rights relating to technology embod- ied in this product. In particular, and without limitation, these intellectual property Java Architecture For XML rights may include one or more of the U.S. patents listed at http://www.sun.com/pat- Binding (JAXB) ents and one or more additional patents or pending patent applications in the U.S. and other countries. Java 3D This product is distributed under licenses restricting its use, copying distribution, and Java Media Framework decompilation. No part of this product may be reproduced in any form by any means (JMF) without prior written authorization of Sun and its licensors, if any.

Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, Java, Netra, Sun Ray, the 100% Pure Java logo and the Java Coffee Cup logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Parts of the product may be derived from FIST and FTSG, licensed from the Research Foundation of State University of New York.

The OPEN LOOK and Sun (TM) Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs and otherwise comply with Sun's written license agree- ments.

Federal Acquisitions: Commercial Software - Government Users Subject to Standard License Terms and Conditions.

5000.4.9 Page 15 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Sun Microsystems: A) The following software may be included in this product: ANT, 1.5.4; RegExp; Xerces 2.x; Xindice v1.1; Tomcat v5; Xalan v2.x; Struts v1.1; BCEL; Apache XML Java Architecture For XML Dsig; Apache xmlenc, XML Security 1_0_6. Use of any of this software is governed by Binding (JAXB) the terms of the license below:

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistribution of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistribution 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. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

The names "Apache JServ", "Apache JServ Servlet Engine" and "Java Apache Proj- ect" must not be used to endorse or promote products derived from this software without prior written permission. Products derived from this software may not be called "Apache JServ" nor may "Apache" nor "Apache JServ" appear in their names without prior written permission of the Java Apache Project. Redistribution of any form whatsoever must retain the following acknowledgement: This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

Continued next page.

5000.4.9 Page 16 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Sun Microsystems: Continued from previous page.

Java Architecture For XML THIS SOFTWARE IS PROVIDED BY THE JAVA APACHE PROJECT "AS IS" AND Binding (JAXB) 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 JAVA APACHE PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDI- RECT, 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 INTERRUP- TION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTH- ERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

B) The following software may be included in this product: DOM (Document Object Model). Use of any of this software is governed by the terms of the license below:

W3C SOFTWARE NOTICE AND LICENSE

Copyright © 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/

This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) 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 documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make:

1.The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.

Continued on next page.

5000.4.9 Page 17 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Sun Microsystems: Continued from previous page.

Java Architecture For XML 2.Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If Binding (JAXB) none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright © [$date-of-software] World Wide Web Consortium, (Massachusetts Institute of Tech- nology, Institut National de Recherche en Informatique et en Automatique, Keio Uni- versity). All Rights Reserved. http://www.w3.org/Consortium/Legal/"

3.Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPY- RIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANT- ABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPY- RIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFT- WARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.

C) The following software may be included in this product: iso-relax.jar v2002/07/07; This software may be obtained under the terms of the license below:

The MIT License

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 per- sons to whom the Software is furnished to do so, subject to the following conditions:

Continued next page.

5000.4.9 Page 18 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Sun Microsystems: Continued from previous page.

Java Architecture For XML The above copyright notice and this permission notice shall be included in all copies Binding (JAXB) 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 NONIN- FRINGEMENT. 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

D) The following software may be included in this product: relaxngDatatype.jar v1.0; This software may be obtained under the terms of the license below:

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 names of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission

Continued next page.

5000.4.9 Page 19 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Sun Microsystems: Continued from previous page.

Java Architecture For XML THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIB- Binding (JAXB) UTORS "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, INDI- RECT, 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 INTERRUP- TION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTH- ERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

E) The following software may be included in this product: JLEX; This software may be obtained under the terms of the license below:

JLEX COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.

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 the copyright notice and this permission notice and warranty disclaimer appear in supporting documentation, and that the name of the authors or their employers not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers 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.

Java is a trademark of Sun Microsystems, Inc. References to the Java programming language in relation to JLex are not meant to imply that Sun endorses this product.

Continued next page.

5000.4.9 Page 20 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Sun Microsystems: Continued from previous page.

Java Architecture For XML F) The following software may be included in this product: CUP Parser Generator; Binding (JAXB) This software may be obtained under the terms of the license below:

CUP Parser Generator Copyright Notice, License, and Disclaimer

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 the copyright notice and this permission notice and warranty disclaimer appear in supporting documentation, and that the names of the authors or their employers not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

G) The following software may be included in this product: CUP Parser Generator; This software may be obtained under the terms of the license below:

5000.4.9 Page 21 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Apache Software Founda- Copyright © 2000-2002 The Apache Software Foundation. All rights reserved. tion 1. Redistributions of source code must retain the above copyright notice, this list of Jakarta-ORO 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 end-user documentation included with the redistribution, if any, must include the following acknowledgement: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgement may appear in the software itself, if and wherever such third-party acknowl- edgements normally appear.

4. The names "Apache" and "Apache Software Foundation", "Jakarta-Oro" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "Apache" or "Jakarta-Oro", nor may "Apache" or "Jakarta-Oro" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``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 DIS- CLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPE- CIAL, 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) ARIS- ING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

5000.4.9 Page 22 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Apache Software Founda- Copyright (c) 1999 The Apache Software Foundation. All rights reserved. tion 1. Redistributions of source code must retain the above copyright notice, this list of Xerces conditions and the following disclaimer.

4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foun- dation.

5000.4.9 Page 23 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

This product includes software developed by The Apache Software Foundation (http:/ /www.apache.org/).

This product contains W3C XML Schema documents. Copyright ©2001-2003 World Wide Web Consortium (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University).

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. CERN makes no representations about the suitability of this software for any purpose. It is provided “as is” without expressed or implied warranty.

The Software and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (C)(1) and (2) of the Commercial Com- puter Software - Restricted Rights at 48 CFR 52.227-19, as applicable. Contractor / manufacturer is Northwoods Software Corporation, 142 Main St., Nashua, NH 03060.

5000.4.9 Page 24 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

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 Jython Developers 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 COPYRIGHT HOLDERS AND CONTRIB- UTORS ``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, INDI- RECT, 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 INTERRUP- TION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTH- ERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

JPython (Version 1.1.x) is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement may be located on the Internet using the following unique, persistent identifier (known as a handle): 1895.22/1006. The License may also be obtained from a proxy server on the Web using the following URL: http:// hdl.handle.net/1895.22/1006.

5000.4.9 Page 25 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

This product includes software developed by the JDOM Project (http://www.jdom.org/ ).

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 disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management ([email protected]).

THIS SOFTWARE IS PROVIDED ``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 DIS- CLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CON- TRIBUTORS 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.

Stingray Objective Toolkit This product includes the Stingray Objective Toolkit Standard software product Standard developed by Rogue Wave Software, a QUOVADX™ division. Stingray Objective Toolkit Standard is a library of controls and utilities for enhancing the GUI of custom applications. Per Agreement:

(c) You may distribute User Software Products including those portions of the Licensed Software used solely for purposes of supporting execution of said User Soft- ware Product where steps have been taken to ensure that no parts of the Software Application Programming Interface or any internally used Value-Added Interfaces (if any) have been exposed directly or indirectly, and where the license for said User Software Products explicitly prohibits the use of the User Software Product for software development use.

5000.4.9 Page 26 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Stingray Objective Grid This product includes the Stingray Objective Grid Standard software product Standard developed by Rogue Wave Software, a QUOVADX™ division. Stingray Objective Grid Standard is an advanced grid component that mimics Microsoft Excel features and provides database connectivity. See agreement above.

MKS Toolkit for Enterprise This product redistributes MKS Toolkit for Enterprise Developers, version 9.x, a UNIX Developers runtime environment for running UNIX applications on Windows systems. NuTCracker is redistributed in conformance with a corporate agreement with MKS.

INT This product redistributes INT graphics widgets, a set of Motif widgets that provides 2D and 3D charting, 3D rendering, hardcopy output, and other geoscience displays.

HOOPS This product redistributes the HOOPS 3D Application Framework (HOOPS/3dAF), a toolkit for designing and developing 2D and 3D engineering software applications. HOOPS is redistributed in compliance with a corporate license agreement with TechSoft 3D.

5000.4.9 Page 27 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Intel MPI Intel MPI libraries.

The Intel(R) MPI Library for Linux* OS is a multi-fabric message passing library based on ANL* MPICH2* and OSU* MVAPICH2*.

The Intel(R) MPI Library for Linux* OS implements the Message Passing Interface, version 2.1 (MPI-2.1) specification.

See the information below for additional licenses of the following third party tools used within the Intel(R) MPI Library: Eclipse*, Silicon Graphics Inc.* STL, libc, gdf, BOOST*, my_getopt, Python*, and AVL Trees*.

Eclipse* ------http://www.eclipse.org/legal/epl-v10.html

Silicon Graphics, Inc.* Standard Template Library ------* Copyright (c) 1996,1997 * Silicon Graphics Computer Systems, Inc. * * Permission to use, copy, modify, distribute and sell this software * and its documentation for any purpose is hereby granted without fee, * provided that the above copyright notice appear in all copies and * that both that copyright notice and this permission notice appear * in supporting documentation. Silicon Graphics makes no * representations about the suitability of this software for any * purpose. It is provided "as is" without express or implied warranty. * */

libc ----- /* * Copyright (c) 1988 Regents of the University of California. * 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. Neither the name of the University nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * Continued on next page.

5000.4.9 Page 28 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Intel MPI (Continued) Continued from previous page

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIM- ITED 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, INCI- DENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SER- VICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CON- TRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHER- WISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. gdf This is copy of the code which implements the GFD(32) hashing of datatypes * described in this paper: Julien Langou, George Bosilca, Graham Fagg and Jack Dongarra (2005). Hash functions for MPI datatypes. In the Proceedings of the 12th European PVM/MPI Users' Group Meeting, Sorrento, Italy, September 2005. Springer's Lecture Notes in Com- puter Science, LCNS-3666:76-83, 2005. related software. * http://www.cs.utk.edu/~library/TechReports/2005/ut-cs-05-552.pdf * http://www.cs.utk.edu/~langou/articles/LBFD:05/2005-LBFD.html

The code is used with permission of the author and was released under the "Modified BSD" license (no need to mention in advertising material). Here's a copy of the complete COPYING file that came with the source: Copyright (c) 1992-2006 The University of Tennessee. All rights reserved. Additional copyrights may follow 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 listed in this license in the documentation and/ or other materials provided with the distribution. - Neither the name of the copyright holders 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 COPYRIGHT HOLDERS AND CONTRIB- UTORS "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 SUBSTI- TUTE 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 NEGLI- GENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Continued on next page.

5000.4.9 Page 29 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Intel MPI (Continued) Continued from previous page.

BOOST Boost Software License - Version 1.0 - August 17th, 2003 Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following: The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor. 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, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

my_getopt my_getopt - a command-line argument parser Copyright 1997-2001, Benjamin Sittler 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 per- sons 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 NONIN- FRINGEMENT. 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.

Continued on next page.

5000.4.9 Page 30 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Intel MPI (Continued) Continued from previous page.

Python* PSF LICENSE AGREEMENT FOR PYTHON 2.3 ------1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 2.3 software 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 2.3 alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, for example, "Copyright (c) 2001, 2002, 2003, 2004 Python Software Foundation; All Rights Reserved" are retained in Python 2.3 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 2.3 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 2.3. 4. PSF is making Python 2.3 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 REPRE- SENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 2.3 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 2.3 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 2.3, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSI- BILITY 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 Agree- ment 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 2.3, Licensee agrees to be bound by the terms and conditions of this License Agreement.

Continued on next page.

5000.4.9 Page 31 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Intel MPI (Continued) Continued from previous page.

AVL Trees* ------Copyright (c) 1989-1997 by Brad Appleton, All rights reserved. This software is not subject to any license of the American Telephone and Telegraph Company or of the Regents of the University of California.

Permission is granted to anyone to use this software for any purpose on any computer system, and to alter it and redistribute it freely, subject to the following restrictions:

1. Neither the authors of the software nor their employers (including any of the employers' subsidiaries and subdivisions) are responsible for maintaining & supporting this software or for any consequences resulting from the use of this software, no matter how awful, even if they arise from flaws in the software.

2. The origin of this software must not be misrepresented, either by explicit claim or by omission. Since few users ever read sources, credits must appear in the documentation.

3. Altered versions must be plainly marked as such, and must not be misrepresented as being the original software. Since few users ever read sources, credits must appear in the documentation.

4. This notice may not be removed or altered.

The Intel MPI library includes altered AVL Trees* source codes.

Windows Installer XML* (WiX) http://www.opensource.org/licenses/cpl1.0.php

BeanShell This product includes Beanshell. BeanShell is a small, free, embeddable Java source interpreter with object scripting language features, written in Java. BeanShell dynamically executes standard Java syntax and extends it with common scripting conveniences such as loose types, commands, and method closures like those in Perl and JavaScript. For more information about Beanshell, please refer to the URL below: http://www.beanshell.org

Beanshell is redistributed under the following license: GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

LSGRG2 This product redistributes LSGRG2 by agreement with Optimal Methods, Inc. LSGRG2 is a sparsity-exploiting tool for solving non-linear problems.

5000.4.9 Page 32 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Silicon Graphics, SGI, Silicon Graphics, SGI, XFS, and Altix are registered trademarks and NUMAlink, XFS and Altix NUMAflex, CXFS and ProPack are trademarks of Silicon Graphics, Inc., in the U.S. and/or other countries worldwide.

3DSL 3DSL is a registered trademark of StreamSim Technologies, Inc. SimDataStudio™ generates files which compatible with 3DSL.

Novell Novell, the Novell logo, the N logo and SUSE are registered trademarks of Novell, Inc. in the United States and other countries.

Microsoft Visual Studio This product incorporates the following Microsoft Visual Studio v. 6.0 libraries -- V6.0 MSVCP60.dll and mfc42.dll. This incorporation is in compliance with the End-User License Agreement for Microsoft Visual Studio V6.0, dated 5/31/1998. COPYRIGHT. All title and intellectual property rights in and to the SOFTWARE PRODUCT (including but not limited to any images, photographs, animations, video, audio, music, text, and "applets" incorporated into the SOFTWARE PRODUCT), the accompanying printed materials, and any copies of the SOFTWARE PRODUCT are owned by Microsoft . All title and intellectual property rights in and to the content which may be accessed through use of the SOFTWARE PRODUCT are the property of the respective content owner and may be protected by applicable copyright or other intellectual property laws and treaties. All rights not expressly granted are reserved by Microsoft.

Ascender “Ascender” is a trademark of Ascender Corporation registered in the U.S. Patent and Trademark Office and elsewhere. All other trademarks are the property of their respective owners. Revised 25 February, 2005 Copyright © 1999–2006 MyFonts.com, Inc.

POSC: RESCUE Public Information RESCUE is a Joint Industry Project managed by the Petrotechnical Open Software RESCUE API Library Corporation (POSC). The acronym “RESCUE” stands for REServoir Characterization Using Epicentre. (http://www.posc.org/rescue/)

3.1 RESCUE 2 Standards shall be free of any and all restriction as to use or distribution.

3.2 All intellectual property rights, including copyright, to the RESCUE 2 Products shall be vested in each of the Participants, their Affiliates, and the Project Manage- ment Company as tenants-in-common, except that the Project Management Steering Committee shall have the sole right to determine whether or not to seek formal protection for the intellectual property rights in the RESCUE 2 Products, the sole right to seek such protection, and the sole right to enforce such protection.

3.3 As owners of the intellectual property rights in RESCUE 2 Products, all Partici- pants, their Affiliates, and the Project Management Company shall have a perpetual, irrevocable and nonexclusive right to use the RESCUE 2 Products without payment of any kind (except as provided in Article 6.7) solely for inclusion in proprietary products intended for their own use or for license to other parties.

5000.4.9 Page 33 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Project Info: http://www.jfree.org/jfreechart/index.html

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 Founda- tion; either version 2.1 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 WAR- RANTY; 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 Street, Fifth Floor, Boston, MA 02110-1301, USA.

[Java is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.]

5000.4.9 Page 34 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

MUMPS This version of MUMPS is provided to you free of charge. It is public domain, based on public domain software developed during the Esprit IV European project PARASOL (1996-1999) by CERFACS, ENSEEIHT-IRIT and RAL. Since this first public domain version in 1999, the developments are supported by the following institutions: CERFACS, CNRS, INPT(ENSEEIHT)-IRIT, and INRIA.

Current development team includes Patrick Amestoy, Alfredo Buttari, Abdou Guermouche, Jean-Yves L'Excellent, Bora Ucar.

Up-to-date copies of the MUMPS package can be obtained from the Web pages: http://mumps.enseeiht.fr/ or http://graal.ens-lyon.fr/MUMPS

THIS MATERIAL IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY EXPRESSED OR IMPLIED. ANY USE IS AT YOUR OWN RISK.

User documentation of any code that uses this software can include this complete notice. You can acknowledge (using references [1] and [2]) the contribution of this package in any scientific publication dependent upon the use of the package. You shall use reasonable endeavours to notify the authors of the package of this publication.

[1] P. R. Amestoy, I. S. Duff, J. Koster and J.-Y. L'Excellent, A fully asynchronous multifrontal solver using distributed dynamic scheduling, SIAM Journal of Matrix Analysis and Applications, Vol 23, No 1, pp 15-41 (2001).

[2] P. R. Amestoy and A. Guermouche and J.-Y. L'Excellent and S. Pralet, Hybrid scheduling for the parallel solution of linear systems. Parallel Computing Vol 32 (2), pp 136-156 (2006).

5000.4.9 Page 35 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Zoltan /* * @HEADER * * *********************************************************************** * * Zoltan Toolkit for Load-balancing, Partitioning, Ordering and Coloring * Copyright 2012 Sandia Corporation * * Under the terms of Contract DE-AC04-94AL85000 with Sandia Corporation, * the U.S. Government retains certain rights in this software. * * 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 Corporation nor the names of the * contributors may be used to endorse or promote products derived from * this software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY SANDIA CORPORATION "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 SANDIA CORPORATION OR THE * 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. * * Questions? Contact Karen [email protected] * * Erik [email protected] * ************************************************************************ *@HEADER

5000.4.9 Page 36 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” International Trade Compliance

This application is manufactured or designed using U.S. origin technology and is therefore subject to the export control laws of the United States. Any use or further disposition of such items is subject to U.S. law. Exports from the United States and any re-export thereafter may require a formal export license authorization from the government. If there are doubts about the requirements of the applicable law, it is recommended that the buyer obtain qualified legal advice. These items cannot be used in the design, production, use, or storage of chemical, biological, or nuclear weapons, or missiles of any kind.

The ECCN’s provided in Release Notes represent Halliburton’s opinion of the correct classification for the product today (based on the original software and/or original hardware). Classifications are subject to change. If you have any questions or need assistance please contact us at:

[email protected]

Under the U.S. Export Administration Regulations (EAR), the U.S. Government assigns your organization or client, as exporter/importer of record, responsibility for determining the correct authorization for the item at the time of export/import. Restrictions may apply to shipments based on the products, the customer, or the country of destination, and an export license may be required by the Department of Commerce prior to shipment. The U.S. Bureau of Industry and Security provides a website to assist you with determining the need for a license and with information regarding where to obtain help.

The URL is:

http://www.bis.doc.gov

Definitions

CCATS (Commodity Classification Automated Tracking System) - the tracking number assigned by the U.S. Bureau of Industry and Security (BIS) to products formally reviewed and classified by the government. The CCATS provides information concerning export/re- export authorizations, available exceptions, and conditions.

ECCN (Export Control Classification Number) -The ECCN is an alpha-numeric code, e.g., 3A001, that describes a particular item or type of item, and shows the controls placed on that item. The CCL (Commerce Control List) is divided into ten broad categories, and each category is further subdivided into five product groups. The CCL is available on the EAR

5000.4.9 Page 37 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Website (http://www.access.gpo.gov/bis/ear/ear_data.html#ccl).

The ECCN Number, License Type, and the CCATS Numbers for this product are included in the table below.

ECCN CCATS Product/Component/R5000 License Number Number

DeskTop VIP 5D002 ENC G048061

DecisionSpace Infrastructure (DSI) 5D002 ENC G054690

Landmark Software Manager (LSM) 5D002 ENC G058319

Nexus 5D002 ENC G047832

PowerGrid™ 5D002 ENC G051477

5000.4.9 Page 38 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Installation

On a Windows Workstation

Note: The Windows release of the Nexus® and VIP® R5000.4.9 is supported on all configurations listed on Software Requirements.

The following section provides procedures for installing Nexus® R5000.4.9 on a Windows workstation. These procedures provide some information that is unique to the Nexus® installation requirements.

Checklist

The complete installation requires that you perform the following procedures before installing Nexus®-VIP® 5000.4.9 on Windows.

Important: You must be logged in using an account that has administrative privileges on the workstation to which you are installing.

1. Check the operating system. It should be one of the following:

• Windows 7 64-bit • Windows Server 2008 (for simulators-only installations)

2. Install LAM 5000.0.3.1 if a network license will be served from this computer.

3. Install Adobe Reader.

4. Install Hummingbird Exceed 14 and Exceed 3D (or later).

5. Check whether your system already has MKS Platform Components or Nutcracker installed.

If your system currently has a version of Nutcracker or a version of MKS Platform Components prior to version 9.4 installed, uninstall it and reboot the system.

Important: The Nexus® R5000.4.9 applications are supported on MKS Platform Components 9.x, version 9.4 or later. They are not supported on prior versions of Nutcracker or MKS Platform Components 9.x. Compatibility with older applications that use Nutcracker should be checked prior to uninstalling an old Nutcracker version and

5000.4.9 Page 39 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” installing a new one. To assess whether compatibility issues may occur, please check with your system administrator. If a later version of MKS Platform Components is found, the installer will complain, but continuing the installation works as desired.

6. Install Nexus®-VIP® 5000.4.9.

Installing the Nexus-VIP Applications on Windows

The following steps explain how to do a typical install on a Windows 7 64-bit system. The standard Nexus® installation includes: The Nexus® simulator, the VIP® simulator, and all the Nexus® Desktop applications, including SurfNet™, and PowerGrid™ software.

1. Log into the client machine with a user account that belongs to the Administrators group on the machine to which you are installing the software.

Caution: Performing the install as the system Administrator can be risky, particularly if you delete existing folders, since all child folders will be deleted. (See Step 14.)

2. Download the Nexus-VIP5000.4.9 install image from the Landmark Software Manager (LSM) website.

3. Navigate to the directory where the install image resides. The name of the image is NexusVIP5000_4_9_0ReleaseWin7_64setup.zip. Unzip this file, which will provide an installer named NexusVIP5000_4_9_0ReleaseWin_7_64setup.exe.

4. Double click on “NexusVIP5000_4_9_0ReleaseWin_7_64setup.exe..”

The Nexus-VIP Release5000.4.9 installer displays.

5. Click Next in the Introduction panel of the InstallAnywhere wizard.

6. If you want to view the release notes, toggle the Launch Release Notes option ON.

7. Click Next.

8. If you agree to comply with the Landmark software agreement, toggle the “I accept .” radio button ON.

By toggling the button ON, you agree to comply with the license agreement. If you do not toggle this button ON, you cannot continue with the install.

9. Click Next.

5000.4.9 Page 40 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” 10.Specify where you want the Nexus-VIP installation to reside on your machine.

The location that you specify must not have spaces or special characters.

11.Click Next.

12.Specify which “install set” you want to install. An install set is one or more applications. The Windows installer provides two Nexus®-specific install sets:

Complete: Installs both the Simulator and Desktop Applications sets which are described below. This is the default.

Simulators Only: Installs only the Simulators application set described below.

There is a Custom install set, which is activated whenever you check or uncheck one of the check boxes which describe the application sets. The application sets are:

Simulators: Installs only the Nexus® and VIP® simulators. These can be run independently of the Nexus® and VIP® applications that have user interfaces.

Desktop Applications: Installs the Nexus® Desktop applications and utilities, SurfNet™, and the PowerGrid™ software.

Important: If you are installing on a Windows server, sect the Simulators Only install set. Only the Nexus® and VIP® simulators are supported on Windows server operating systems.

13.Click Next.

14.If you are installing on a system where Nexus®-VIP® R5000.4.9 has already been installed, and if there are still modules from the previous installation in the selected folder, the following dialog will be displayed.

5000.4.9 Page 41 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Select whether you want to install to a new location, overwrite the existing installation, or abort the job. If you wish to uninstall the previous installation, choose “Abort”. After the installer exits, uninstall Nexus® from the Windows Control Panel.

15.If you have selected the Desktop Applications option, specify what Nexus®-VIP® shortcuts you want to be created.

The options are:

• A standard shortcut on the Start Menu in All Programs

This shortcut will appear in the Landmark program group (i.e., Start -> Programs -> Landmark ->.).

• A standard shortcut on the computer desktop.

16.Click Next.

17.Review your selections and check that you have sufficient disk space on your machine.

Note that MKS Platform Components and Intel MPI will be listed as products to be installed if they have not already been installed on your system.

5000.4.9 Page 42 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” 18.Click Install to perform the installation.

The installer will immediately install the Nexus® and VIP® products that you selected.

InstallAnywhere will display the progress of the installation. When all of the files have been installed, a message will announce that the installation has completed.

If your system requires the installation of additional third party applications (such as the MKS Platform Components 9.x or Intel MPI), you will be prompted to review the copyright information of the applications before proceeding.

19.Click Next.

Setup dialogs for third party applications display as they are installed, configured, and registered.

When the installation is complete, an Install Complete panel displays.

20.Click Done.

Uninstalling Nexus-VIP 5000.4.9

Caution: The uninstaller deletes ALL files in the Nexus-VIP 5000.4.9 folders, including files that have been placed there by the user. Before uninstalling, move any files that you want to preserve to a directory outside of the Nexus-VIP 5000.4.9 directory structure.

Use the Windows Add and Remove Programs utility (Start -> Settings -> Control Panel - > Add or Remove Programs) to uninstall Nexus-VIP 5000.4.9.

Setting Environment Variables

To Submit Jobs from the Command Line:

To configure a Windows 7 or Windows Server 2009 system so that the user can submit jobs from the command line, set the following environment variables.

5000.4.9 Page 43 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Environment Description Example Variable

STAND_EXE Must be set to the appropri- C:\Landmark\Nexus-VIP 5000.4.9\ ate Standalone executable. Nexussimulators\Windows64\ Setting must include the standaloneEM64_5000_4_9.exe complete path.

DBMAP_EXE Must be set to the appropri- C:\Landmark\Nexus-VIP 5000.4.9\ ate DBMAP executable. Set- Nexusexec\dbmap.exe ting must include the complete path.

NEXUS_EXE Must be set to the appropri- C:\Landmark\Nexus-VIP 5000.4.9\ ate Nexus executable. Set- Nexussimulators\Windows64\ ting must include the NexusEM64_5000_4_9.exe complete path.

I_MPI_ROOT Must be set to the root direc- C:\Program Files (x86)\Intel\MPI-RT\4.0.3.009 tory of the MPI installation. Typically this variable is set automatically when you install Nexus.

PATH Must include settings for MPI C:\%I_MPI_ROOT%\intel64\bin for Windows 7 bin directory. Typically this variable is set automatically (Note: The above string should be added to the when you install Nexus. existing PATH definition. The string should be placed at the beginning of the existing PATH entries.)

To Customize Nexus View Software

To customize the Nexus® View software for the display of very large models, set the following environment variables.

5000.4.9 Page 44 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Environment Variable Description Default Setting

LGCRSV_KEEP_LAYER_CACHE Setting to 'false' will not set aside true permanent memory for the geometry layer cache (50 Mb max) if the geometry is being served by layers. Setting this value to 'false' will result in the smallest possible 'memory footprint' for geometry operations.

LGCRSV_CACHE_THRESHOLD Defines the number of cells in a 5 million cells grid above which all geometry operations will be done on a layer- by-layer basis. Only a limited number of layers will be in memory at any given time for grids with cell counts above the threshold. All layers will be loaded simultane- ously for grids with cell counts below the threshold.

LGCRSV_FORCE_CORRECT_HANDED- If set to 'true' will override any false NESS data-provided ijk handedness flags and compute the correct ijk handedness based on the geometry and topology of a visible cell in the grid.

LGCRSV_INITIAL_STREAMLINES If set, will limit the number of 10,000 streamlines initially loaded by the viewer (only if the total counter is larger).

LGCRSV_SMALLEST_LOG_VALUE If set defines the smallest real 0.010 value on the logarithmic colormap.

5000.4.9 Page 45 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

LGCRSV_USE_FULL_TERNARY_ If set to 'true' will use a data range false SATURATION_RANGE of min=0.0 and max=1.0 for all sat- urations (Oil, Water, Gas) when rendering in ternary mode. By default this value is 'false', i.e., use the range of the data when rendering in ternary mode. If not rendering ternary saturation data, this environment variable will have no effect.

LGCRSV_FAULT_FACE_MASK Controls which faces of a fault 191 object, by default, are rendered. The default value renders all faces belonging to active cells (which is a value of 128+63=191). If you wanted to see all faces of a fault belonging to all cells (active or not), you would set LGCRSV_- FAULT_FACE_MASK to 63. Or, to see all 'non-k' faces belonging to active cells of faults, set the value to 128+27=155.

5000.4.9 Page 46 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Configuring the License Manager

The Nexus® or VIP® workstation must be able to connect to a license.dat file that has license keys for the various Nexus® and VIP® features that you want to run. The license.dat file must be hosted by a FLEXlm license server. Typically, the license server is installed on a server, although other configurations are possible.

While it is possible to use the standard LM_LICENSE_FILE variable to configure license access, this can cause problems on systems with multiple applications and multiple license servers. Environment variables specific to Landmark software have been created to address these problems; for the Nexus® application, the relevant environment variable is LICSRV_LICENSE_FILE. To configure the Nexus®-VIP® 5000.4.9 workstation to connect to a valid license.dat file, set up a LICSRV_LICENSE_FILE variable on the local workstation as follows:

1. Select Start > Control Panel > System. The System Properties dialog box displays.

2. In the Advanced tab, click the Environment Variables button to display the Environment Variables dialog box.

3. Check whether an LICSRV_LICENSE_FILE variable exists.

If one does, select it and click Edit to display the Edit System Variable dialog box.

If one does not, click the New button in the System Variables group box to display the New System Variable dialog box and type LICSRV_LICENSE_FILE in the Variable name text box.

4. In the Variable value text box, enter a string that points to the license.dat file that you want to use.

For example, your environment variable can be as follows:

LICSRV_LICENSE_FILE = \\Server\lam\license.dat or

LICSRV_LICENSE_FILE = @ where Server is the system name or IP address of the license server.

For information on installing and configuring a license server, see the LAM Installation Procedures manual for Release 5000.0.3.0. You can download this manual from the Landmark Software Manager.

5000.4.9 Page 47 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Installing on a Linux System

Note: The Linux release of Nexus® and VIP® 5000.4.9 is supported on all systems listed on Software Requirements.

Note:

The following section provides procedures for performing a standard Nexus® R5000.4.9 installation on a Linux workstation. A standard installation installs the Nexus® and VIP® simulators, as well as the Nexus® Desktop applications and utilities, and the PowerGrid™ software. E2V, SimResults™, and SimDataStudio™ are not available on the Linux platform.

You can also install the Nexus® and VIP® simulators in the server mode. Use this type of installation if you want to submit jobs to the simulators from a remote Windows system that has the standard installation, or to run jobs from the command line only.

Checklist

The standard installation requires that you perform the following procedures before installing Nexus® on Linux.

1. Install the Red Hat Enterprise Linux Workstation operating system.

2. Install LAM 5000 or configure the system to use a remote LAM server.

3. Ensure a PDF reader is installed on the Linux workstation.

Install Nexus-VIP 5000.4.9

The following steps describe a typical installation of Nexus® on a Linux system.

1. Log into the client machine with a Linux user account that has write permissions for the area where you want to install Nexus®-VIP® 5000.4.9.

Caution: Performing the install while using the root login can be risky, particularly if you delete existing folders, since all child folders will be deleted. (See Step 15.)

2. Download the Nexus-VIP 5000.4.9 install image from the Landmark Software Manager (LSM) site. It is provided in a tar file named: NexusVIP 5000_4_9_0ReleaseLx64setup.tar

5000.4.9 Page 48 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” 3. Navigate to the Nexus-VIP 5000.4.9 directory where the install image resides. Untar the file to obtain the installer executable, which has the same base name but the extension “.bin” rather than “.tar”.

4. Execute the Nexus-VIP 5000.4.9 installer command.

sh ./NexusVIP5000_4_9_0ReleaseLx64setup.bin & The Nexus-VIP 5000.4.9 Install window appears.

5. Click Next.

6. If you want to view the release notes, toggle the Launch Release Notes option ON.

7. Click Next.

8. If you agree to comply with the Landmark software agreement, toggle the “I accept .” radio button ON.

By toggling the button ON, you agree to comply with the license agreement. If you do not toggle this button ON, you cannot continue with the install.

9. Click Next.

10.Specify where you want the Nexus®-VIP® installation to reside on your machine.

The location that you specify cannot have spaces or special characters. You must have write permissions for the location.

11.Click Next.

12.Specify which “install set” you want to install. An install set is one or more applications. The Linux installer provides two Nexus®-specific install sets:

Simulators: Installs only the Nexus® and VIP® simulators. These can be run in the batch mode independently of the Nexus® and VIP® applications that have user interfaces.

Desktop Applications: Installs the Nexus® and VIP® simulators, as wells as the Nexus® Desktop applications and utilities. The SimDataStudio™, E2V, and SimResults™ applications are not included in the Linux installation as these are Windows-only packages.

13.Click Next.

5000.4.9 Page 49 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” 14.Click Next again.

15.If you are installing into a folder where Nexus®-VIP® R5000.4.9 has already been installed, and if there are still modules from the previous installation in the selected folder, the following dialog will display.

Select whether you want to remove the existing installation, specify a new location, continue and overwrite the existing installed folders, or abort the job. If uninstall information is found, an option to launch the uninstaller is also available.

16.If you have selected the Desktop Applications option, specify what Nexus®-VIP® shortcuts you want to be created.

The only option is:

• A standard shortcut on the computer desktop.

17.Click Next.

InstallAnywhere will display a summary of the selections you have made.

Review your selections. Confirm that the folder that you have selected for the installation provides sufficient free space.

18.Click Install to accept the summarized settings and to start copying files.

5000.4.9 Page 50 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

InstallAnywhere will display the progress of the installation. When all of the files have been installed, a message will announce that the installation has completed.

19.Click Done to complete the installation.

It is not necessary to reboot after the installation.

Upgrading Nexus-VIP 5000.4.9

To upgrade an existing Nexus®-VIP® installation in the same location, you must first uninstall the previous installation, and then install the current version as described on page 48.

Uninstalling Nexus-VIP 5000.4.9

The Nexus®-VIP® 5000.4.9 installer should detect if you are installing on top of a location where Nexus®-VIP® 5000.4.9 is already installed. If it detects an existing installation, it allows you to uninstall (if it finds the uninstaller), delete the existing installation, specify a new location, overwrite existing files, or abort.

You can uninstall manually by navigating to the “Uninstall_Nexus-VIP _5000.4.9” directory, which is typically located in the directory where you installed Nexus-VIP 5000.4.9 (such as /opt/Landmark). From this directory, run the following command:

sh ./Uninstall_Nexus-VIP5000.4.9

The InstallAnywhere Wizard will launch and prompt you to select the applications to be uninstalled. You can uninstall all of the currently installed Nexus®-VIP® 5000.4.9 applications, or you can uninstall individual applications.

5000.4.9 Page 51 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Set the Nexus Environment Variables

You must set the following Nexus® environment variables on all the Linux systems which will run jobs submitted by the Nexus® Job Submitter:

• NEXUS_SIM - Identifies the location of the simulator folder/directory on the workstation.

Typical value: /opt/Landmark/Nexus-VIP5000.4.9/Nexussimulators

• NEXUS_SCRIPT - Identifies the location of the job submission scripts on the workstation.

Typical value: /opt/Landmark/Nexus-VIP5000.4.9/Nexusscript

• LICSRV_LICENSE_FILE - Identifies the location of the license.dat that contains the required license keys. This value is customer dependent. Landmark recommends using this environment variable rather than the generic LM_LICENSE_FILE.

You should set these environment variables in your shell initialization script on the Linux system. The usual names for shell initialization scripts are ~/.cshrc for C shell and compatible shells, and ~/.profile for Bourne shell and compatible shells.

If users will be submitting jobs from the command line, the following environment variables can be set for the sake of convenience. These variables are used in the command-line workflows given in the Nexus® User Guide.

The values of the variables given below assume that Nexus® was installed in a typical location for a Linux system (/opt/Landmark/Nexus-VIP5000.4.9). If a different installation directory was used, its full path should be substituted below wherever /opt/Landmark/ Nexus-VIP5000.4.9 is found.

Environment Variable Example

NEXUS_EXE /opt/Landmark/Nexus-VIP5000.4.9/Nexussimulators/ LinuxEM64/NexusEM64_5000_4_9.exe (Identifies the location of the Nexus simulator executable.)

5000.4.9 Page 52 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

STAND_EXE /opt/Landmark/Nexus-VIP5000.4.9/Nexussimulators/ LinuxEM64/standaloneEM64_5000_4_9.exe (Identifies the location of the Standalone executable.)

DBMAP_EXE /opt/Landmark/Nexus-VIP5000.4.9/Nexusexec/dbmap.exe (Identifies the location of the DBMAP executable.)

I_MPI_ROOT /opt/Landmark/Nexus-VIP5000.4.9/Nexussimulators/ LinuxEM64/Intel-MPI (Identifies location of the Intel MPI installation.)

LD_LIBRARY_PATH /opt/Landmark/Nexus-VIP5000.4.9/Nexussimulators/ LinuxEM64/Intel-MPI/intel64/lib (Identifies the location of the Intel MPI run-time libraries.)

PATH Identifies a search path for executables. /opt/Landmark/Nexus-VIP5000.4.9/Nexussimulators/ LinuxEM64/Intel-MPI/intel64/bin:$PATH.

5000.4.9 Page 53 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Licensing

Nexus® and VIP® features are enabled by specific license keys that must reside in a license.dat file that is accessible from the Nexus®-VIP® installation.

License Key Product Description

NEXUSBM Nexus simulator Enables black oil simulation.

NEXUSCM Nexus simulator Enables compositional simulation.

NEXUSMR Nexus simulator Enables multi-reservoir simulation.

NEXUSMS Nexus simulator Enables multi-scenario simulation when coupled with DMS™.

NEXUSPM Nexus simulator Enables parallel simulation.

BLACKOIL, PBLACKOIL VIP Enables VIP serial and parallel black oil simulations, respectively.

COMP, PCOMP VIP Enables VIP serial and parallel compositional simulations, respectively.

DUAL VIP Enables VIP serial dual porosity, dual permeability.

LGR VIP Enables local grid refinement option.

PNPROC VIP Enables a maximum number of multiple proces- sors per parallel run.

POLY VIP Enables serial polymer simulation.

PVIP VIP Enables a maximum number of parallel VIP jobs.

SURFACE VIP Enables serial surface simulation.

THERM VIP Enables serial thermal simulation.

TRACER VIP Enables the particle tracking capability within VIP (the tracer option).

VIP VIP Enables maximum number of serial VIP runs.

DSPOWERGRID Nexus/VIP utilities Enables the advanced upscaling features of PowerGrid™.

DSSLAM StreamCalc Enables the StreamCalc streamline generator.

DSUPSCALER Nexus/VIP utilities Enables the basic upscaling features of PowerGrid™.

DT3DV Nexus/VIP utilities Enables use of the viewer 3DView.

DTGRIDGENR Nexus/VIP utilities Enables use of the GridGenr gridding tool.

5000.4.9 Page 54 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

DTGUI Nexus/VIP utilities Enables use of the 2D graphing and calculator utilities from the Nexus Desktop.

DTPVT Nexus/VIP utilities Enables use of the Desktop PVT compositional property tool.

DTSIMRESPLUS Nexus/VIP utilities Enables use of the “plus” extra features in SimResults™.

DTSIMPRESPLUS3D Nexus/VIP utilities Enables use of the 3D features in SimResults™.

NEXUSEM Nexus/VIP utilities Enables use of SimDataStudio™ to create Nexus input files.

NEXUSRV Nexus/VIP utilities Enables use of the Nexus View reservoir viewer.

SIMRESULTSHPG Nexus/VIP utilities Enables use of the high-performance graphics features in SimResults™.

SURFNETPOST Nexus/VIP utilities Enables use of SurfNet™.

See your Landmark sales representative to request licensing for particular Nexus®-VIP® features.

5000.4.9 Page 55 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Running the Software

Information related to running the Nexus® software, including the use of the Nexus® Desktop, can be found in the online help system, or in the Nexus® User Guide (..\help\com\lgc\Nexus\Nexus_User_Ref.pdf).

5000.4.9 Page 56 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Configuring Linux Systems to Run Parallel Jobs

You can run Nexus® in parallel either on a single Linux workstation or on multiple nodes of a Linux cluster. You can run from the command line, or, in some circumstances, from the Nexus® Job Submitter. If Nexus® is installed to a shared (NFS-mounted) disk, a single installation will suffice for all Linux systems that can access that disk. In this case, you do not need to install Nexus® on each individual node of a cluster. This greatly simplifies the system administrator's tasks.

The Nexus® Job Submitter in Nexus®-VIP® 5000.4.9 allows users to submit Nexus® or VIP® simulation jobs from a Windows or Linux computer which can be configured.

• to run locally on that computer

• to run on a user-specified Linux computer

• to run on a Linux cluster which is running certain commercial or open-source batch management (queuing) software packages, under the management of the queuing software.

Jobs cannot be submitted to remote Windows computers from the Nexus® Job Submitter.

1. IInstall Red Hat Enterprise Linux 5.3. Review Red Hat’s documentation for assistance, if needed.

2. Install the Nexus® and VIP® simulators, either onto a shared filesystem or onto each of the nodes to be used. (See Install the Nexus and VIP Simulators.)

3. Configure the Nexus® environment (See Configure the Nexus Environment.)

Install the Nexus and VIP Simulators

Follow the installation instructions in the Installing on a Linux System section above to install Nexus® and VIP® on each of the Linux workstations that will run local jobs or that will be used to submit jobs to remote Linux workstations. As noted above, installation to a shared disk is preferred, as the installation does not require special setup on each workstation of cluster compute node.

5000.4.9 Page 57 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Configure the Nexus Environment

This section includes information on the following:

• requirements for remote job submission • testing network connectivity between Windows and Linux systems • establishing Windows-to-Linux connectivity (if necessary) • installing Intel MPI on all remote Linux workstations in a cluster, or onto a shared filesystem (automatically done by the Nexus®-VIP® installer) • setting the Nexus® environment variables for parallel computing • establishing Linux-to-Linux connectivity (if necessary)

Requirements for Submitting Remote Simulation Jobs via Secure Shell (SSH)

For remote submittal to work properly, Windows and Linux machines must be able to communicate across the network with each other using ping, scp and ssh commands.

• The use of ping, scp, and ssh commands must be allowed by any firewall or security software on both the local and remote systems. Failure to allow these will generally result in the Nexus® Desktop indicating that the NEXUS_SCRIPT environment variable is not set correctly.

• Machines are assigned an IP address, either static or dynamically via DHCP. In either case, the DNS (Domain Names Service) server on the network should have a proper record of the fully qualified and unqualified hostname for all machines.

• If there is no DNS or it is not properly configured, each local and remote machine must have a record of every other machine’s qualified and unqualified hostname in the respective machine’s HOSTS file. On Linux machines this file can be found in the /etc directory. On Windows machines this file can be found in the C:\windows\system32\drivers\etc directory.

Test Network Connectivity between Windows and Linux Systems

Network connectivity can be tested by using the “ping” command. Ping is found in the following locations:

• Linux - /bin/ping • Windows- C:\Windows\system32\ping.exe

Ping can be executed as follows:

5000.4.9 Page 58 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

ping machinename

If the network has not been set up properly, errors such as “Time Out” or “Connection Refused” will be given. If this occurs, check the DNS server in a resolution network or add the proper IP address and both qualified and unqualified hostname information in the respective hosts files of each machine.

Establish Windows-to-Linux SSH Connectivity

Nexus® utilizes SSH (secure shell) to submit jobs from the Windows client machine to remote Linux hosts. The necessary SSH software is installed and configured by the Windows installation and special setup is not required by the user.

The following instructions assume that SSH has been installed and enabled on the remote Linux host(s).

Before attempting to submit a simulation job from a Windows client to a Linux host, the user must insure that connectivity is functioning properly. The user must successfully make a test connection using a utility called ‘plink.exe’ that is installed by Nexus®. This initial connection is required in order to cache SSH authentication keys on the Linux host so that the Windows client is automatically recognized without challenge.

On the Windows desktop run the following command at a command prompt:

C:\Landmark\Nexus-VIP5000.4.9\Nexusexec\plink –pw @

Where the arguments are defined as follows:

= user’s Linux password = user’s Linux username = Linux hostname = simple remote command to be issued to the Linux host

The first time the “plink” command is run from a Windows client to a Linux host, the user will be prompted whether or not to add an authentication “key” to the host’s SSH cache.

The user must answer “y” to add the key to the cache. A response of “n” or pressing Return will not permanently cache the key and Remote Submission will not function.

5000.4.9 Page 59 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Future connections via “plink” command will not be challenged.

This step must be performed from each Windows client to all Linux hosts to which the client will connect. In cases where a Linux cluster has been configured such that Windows clients can only connect directly to a “master” node, this step must be performed from the Windows client to the master node.

During the initial setup, perform the “plink” command twice in succession to insure that SSH communication has been established correctly.

Example of the plink command issued for the first time from a Windows command prompt:

C:\Landmark\Nexus-VIP5000.4.9\Nexusexec>plink -pw go!1065 VIP user11@VIP hcli02 echo $HOME

5000.4.9 Page 60 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” The user is prompted to add a key to the cache:

The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is.

The server's rsa2 key fingerprint is: ssh-rsa 1024 43:ef:44:90:0b:d1:5c:89:ce:75:83:07:a1:eb:bf:39 If you trust this host, enter "y" to add the key to PuTTY's cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, enter "n".

If you do not trust this host, press Return to abandon the connection.

Store key in cache? (y/n)

The user responds with “y” to add the key to the cache.

The plink command is issued a second time from the Windows command prompt and should return the results of the remote command. In this case “echo $HOME” would return the home directory of VIP® user11.

c:\Landmark\Nexus-VIP5000.4.9\Nexusexec>plink -pw go!1065 VIPuser11@VIP hcli02 echo $HOME

Returns:

home/server1/VIP user11

Configuring the Nexus Environment for Parallel Processing on Linux Clusters

You can configure Nexus®-VIP® 5000.4.9 to submit simulation jobs from a Windows system to other Linux nodes, each of which has the Nexus® and VIP® simulators installed on a local disk, or has access to a shared filesystem with the Nexus®-VIP® software installed.

Verify Intel MPI Availability on All Nodes in the Linux Cluster

The Nexus® job submittal software uses Intel MPI for parallel processing; both Nexus® and VIP® require the Intel MPI libraries to be readable from each node in the cluster. The preferred installation method is to install the Nexus®-VIP® software to a shared

5000.4.9 Page 61 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” filesystem, because Intel MPI gets installed automatically when you install the software. If for some reason individual node installation is required, and Intel MPI has been removed from a node, you can only install it by uninstalling and re-installing the Nexus®-VIP® 5000.4.9 software.

Set the Nexus Environment Variables for Parallel Computing

You must set the Nexus® environment variables described in the Installation chapter on all the Linux systems which will run jobs submitted by the Nexus® Job Submitter. This is normally done in a user’s .cshrc or .profile files, which are run upon creation of a shell process. The key environment variables are:

• NEXUS_SIM - Identifies the location of the simulator on the workstation.

• NEXUS_SCRIPT - Identifies the location of the job submission scripts on the workstation.

• LICSRV_LICENSE_FILE - Identifies the location of the license.dat that contains the required license keys.

5000.4.9 Page 62 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

Establish Linux-to-Linux SSH Connectivity

Similarly to the Windows to Linux communication discussed previously, each Linux node must be able to communicate with the others via SSH protocol without being prompted for a password. The following steps must be performed for each Linux username utilized for Nexus® simulations.

Log on to the Linux master node as a user who will submit Nexus® jobs and attempt to SSH to one of the nodes in the cluster. To log on, type the following command at the command prompt:

ssh

If this is the first attempt to ssh between machines the user will be prompted with the following message:

The authenticity of host 'VIP hcln01 (192.168.77.111)' can't be established.

RSA key fingerprint is d5:c0:82:04:6c:a4:48:d9:b3:00:e6:2d:d4:02:07:20.

Are you sure you want to continue connecting (yes/no)?

Enter “yes”. This adds the node to a known_hosts file in the $HOME/.ssh directory.

The directory and file are automatically created by the system the first time this step is performed. Subsequent ssh connection attempts to the same node will not repeat the above message and the user will see a password prompt. Repeat this step for each node in the cluster.

If no other messages or password prompts appear, but rather a shell prompt for the cluster node appears, SSH authentication keys have been cached and connectivity is configured for trusted command and login execution. No further action is required for the target node. Type “exit” to leave the shell, then repeat the test for all the additional cluster nodes. If all nodes allow trusted (passwordless) connections, you have completed this step and are ready to run.

If a password prompt appears, trusted command and login execution must then be configured to remove the password prompt. This is accomplished by running “ssh-keygen – t rsa” which will create three files in $HOME/.ssh:

5000.4.9 Page 63 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

• authorized_keys • id_rsa • id_rsa_pub

Note: $HOME/.ssh must have read/write/execute permissions granted to the user only (mode 700) or ssh will not function correctly. This is a requirement of the ssh software.

From the master node enter:

ssh-keygen -t rsa

The system responds:

Generating public/private rsa key pair Enter file in which to save the key (/[userhome]/.ssh/id_rsa):

Press Enter to accept the default. The system responds

Enter passphrase (empty for no passphrase):

If your company’s IT department requires ssh passphrases, you will need to run the ssh- agent to have passwordless access. Configuring this is beyond the scope of this document. Otherwise, press Enter so that no passphrase is set. The system responds

Enter same passphrase again:

Press Enter. The system responds

Your identification has been saved in /[userhome]/.ssh/id_rsa. Your public key has been save in /[userhome]/.ssh/id_rsa.pub. The key fingerprint is:

Xx:...... :xx [user]@[host]

The id_rsa and id_rsa_pub files will now exist in $HOME/.ssh. Navigate to the $HOME/.ssh directory and execute the following command to create the authorized_keys:

cp id_rsa.pub authorized_keys

All necessary files now exist in $HOME/.ssh on the master node. If all nodes on the cluster share the same $HOME, no further action is required. If all nodes have a different $HOME on each node the following steps must be performed from the $HOME on each node in the cluster.

5000.4.9 Page 64 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

1. Manually create a .ssh directory (mkdir .ssh).

2. Change the permissions on the node to allow read/write/execute for only the user (chmod 700 .ssh)

3. Copy or sftp the authorized_keys, id_rsa, and id_rsa_pub files from the master node $HOME/.ssh directory to the $HOME/.ssh directory on each node.

When the process is finished, repeat the simple ssh test from the master node to all other nodes to insure that trusted ssh connectivity has been configured correctly. A password prompt should not appear when each test is performed.

5000.4.9 Page 65 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Enhancements and New Functionality

The following new features have been implemented in the 5000.4.9 release of Nexus® and VIP :

Nexus Simulator

• Both full-field and sector models which use the boundary-flux capability may now be run in parallel.

• An additional input form for Nexus rock property (compaction) tables is available, in which the entries in the table are based upon pressure change from initial conditions (DP), rather than based upon absolute pressure.

• Nexus can now be connected to the RESOLVE software from Petroleum Experts at any network node, and Nexus well controls can be modified by RESOLVE. This is done through a PROC function (resolve) in the surface network data input.

• A new run tuning option, AUTOPILOT, has been added. This option causes Nexus to make small modifications to input data where experience has shown they can be beneficial to performance without significantly affecting the simulation results. Additionally, Nexus Auto-Pilot also can make modifications to solver parameters to improve the run performance.

• Initialization options have been provided to better preserve transition zones around the gas-oil and water-oil contacts when overreading saturation arrays: avoiding the creation of hydrocarbons where none existed before the overreads (HONOR_WZONE), and avoiding the creation of gas in the oil zone or oil in the gas zone where none existed before the overreads (HONOR_GZONE).

• A new automated domain-decomposition method has been added for parallel runs, in which the subgrids are determined using an algorithm which is not dependent upon information related to the grid structure (ZOLTAN). This algorithm is better suited to models with multiple local grid refinements than the automated method first implemented in Nexus, which remains available.

• Nexus spreadsheet output has been enhanced with the addition of a new spreadsheet which includes flow data along the wellbore; it is also now possible to change the format of spreadsheets upon restart. The WELLBORE spreadsheet contains outlet flow rates at nodes within the wellbore, including the perforations; it differs from the PERFS spreadsheet, which contains the rates at the sand face. Keywords now exist to reset spreadsheet formats to the default upon restart, which could not be done in prior Nexus releases.

5000.4.9 Page 66 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • Error checking of Nexus input data has been improved. This may lead to run failures of input data that worked in previous versions of Nexus. Some new checks includes reasonable phase viscosities (at any conditions, the oil phase must be more viscous than the gas phase) in PVT tables and validation of required network constraints when an inactive network item becomes active. Structured grid array modifications FTRANS, OVER, and VOVER which affect gridblocks in a coarsened region are now treated as an error; this input had been silently ignored in the past. It should be noted that FTRANS, OVER, and VOVER data can be applied to coarsened blocks in the OVERRIDE data.

• Many new network features have been added, including

– Manifold connections can be defined; these have multiple possible values of NODEIN and NODEOUT. The active NODEIN and NODEOUT at any time can be input as user data or can be determined by a procedure.

– Users have the ability to assign network nodes to STATIONs.

– Nexus can perform heat transfer computations for pipes submerged in the ocean which accounts for the convective transfer due to ocean movement,

– The SEQUENTIAL option for the automated well workover feature has been modified to have two options related to workover ordering (WAIT/NOWAIT).

– The default network temperature (NETTEMP) can now be specified at multiple times within the surface data, and it will be honored until changed. Users may now, for example, specify ambient temperatures that vary seasonally.

– Compressors may now have a mechanical efficiency specified.

– Simulated results for water cut, gas-oil ratio, and tracked condensate production may now be plotted for stations, connections, and connection lists.

– Complex wellbores with loops, such as wellbores with multiple ICD connections between adjacent packers, can now be modeled.

• Many enhancements and improvements have been made to Nexus procedures, including:

– New predefined variables have been added which indicate whether the network or any constraints have been changed due to user input.

– All vector/array type variables in procedures can now be allocated with user- specified dimensions.

5000.4.9 Page 67 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” – Three additional output files are available for procedure output, and new printing capabilities have been added, so users can build clearer reports indicating how procedures are affecting the network.

– Multiple new functions have been provided, expanding significantly what can be done within procedures. A partial list includes functions to get mobile fluids in place, properties of connections, WAG information, network connectivity, network potential pressures, and fluid velocities in connections; additional functions can solve for well and partial network potentials (rather than solving the full network). See the Nexus Keyword Document for the full range of available procedure functions and their capabilities.

SimDataStudio™

• Users can build boundary-flux sector models from within SimDataStudio. This includes both setting up the ISECTOR array to define the sectors in the full-field run and setting up all the necessary input for the sector run, including which sectors to include and the location of the full-field flux files.

• Error checking of input data has been significantly improved.

SurfNet™

• Users can plot constraints on charts when plotting the simulated value corresponding to the constraint, providing visual evidence of whether a constraint is active or not.

• Users can include constraint values alongside corresponding simulated data in spreadsheets, for post-processing in other tools.

• Users can view a timetable of events for any network node or connection; the timetable lists significant changes over the lifetime of the item.

Nexus Desktop™

• Users now have control (in the View menu) over whether included files are themselves checked for further included files when input data is selected for a Nexus or VIP job. This can greatly speed up the preparation for submitting a large input deck with multiple levels of include files, but the user will not be notified by the Nexus Desktop interface if certain files are missing from the input.

5000.4.9 Page 68 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Fixed Issues

The following customer reported problems have been fixed in the 5000.4.9 release of Nexus® and VIP :

Nexus Simulator

• Well incorrectly shuts in for exceeding water cut when network reinitialization occurs (Defect 925108)

• Invalid UNSATGAS data is not caught by Standalone, causing Nexus to crash (Defect 925790)

• Nexus multi-reservoir and processor licenses not properly released when the simulation run terminates (Defect 926645)

• Including non-WAG wells in a WELLLIST passed to a WAG procedure call causes Nexus to crash (Defect 927465)

• Potential reports requested by OUTSTART EQUILREGION are incomplete for parallel runs (Defect 927759)

• Procedure calls related to REGION information do not work correctly when the region number is a variable (Defect 927843)

• Procedure functions are desired to allocate arrays whose size is determined by the PROC (Enhancement 927998)

• Procedure functions to retrieve additional information about WAG well cycles are wanted (Enhancement 928328)

• Workover delay parameter DELT is ignored when it should be applied (Defect 929360)

• Nexus crashes in a prediction model with a surface network containing SEPNODE input with FTOTAL = 0 (Defect 929366)

• Wellnode connections do not get the correct properties from the WELLBORE table (Defect 930007)

• Well perforations located at measured depths less than the measured depth of the well node are not connected (Defect 930009)

• Many network divergences are seen in a model converted to Nexus from VIP (Defect 930063)

5000.4.9 Page 69 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • Nodes would not have to have their temperature redefined if the NETTEMP keyword only sets temperatures that are not explicitly input (Enhancement 930305)

• Standalone fails to report a data input error for a well constraint when NOREPORT is specified in the case file (Defect 930364)

• Nexus multi-reservoir case crashes when the model includes TRACKREG input (Defect 930481)

• Nexus input files with more than 1000 characters on a single line cause errors in Nexus 5000.4.8 that did not occur in prior releases (Defect 930482)

• Scaling of USER imbibition curves is incorrect (Defect 930555)

• SATDEBUG output is incorrect for some combinations of endpoint scaling arrays and hysteresis options (Defect 930557)

• Fluid tracking reports in multi-reservoir cases incorrectly show zero production in all reservoirs except the first (Defect 930808)

• Method assignments are wrong when the number of methods in a multi-reservoir case changes upon restart (Defect 931166)

• Standalone can crash when component names in a multi-reservoir compositional model do not match (Defect 931905)

• RFT reports for horizontal wells would benefit greatly if measured depth information was also output (Enhancement 932023)

• Activation and deactivation of targets in PROCs can lead to some active targets being ignored (Defect 932046)

• Reporting of active constraint when wells are pressure-controlled at both bottomhole and tubing head is ambiguous (Defect 932100)

• Coarsening gridblocks which have negative bulk volume due to bad corner points can cause initialization failures (Defect 932467)

• At the time the water injection rate changes in a model, wells shut in unexpectedly for backflow, then re-open very soon afterward (Defect 932493)

• Polymer injection runs with SHEAR_GRID FACE behave incorrectly when run in parallel (Defect 932496)

• Nexus parallel run hangs when processing OVERRIDE data which includes IRELPM array input (Defect 932505)

5000.4.9 Page 70 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • Nexus spreadsheet files contain spurious tracer output in a model which uses fluid tracking (Defect 932595)

• Nexus fails to recognize a pair of targets as equivalent, and the run fails to converge (Defect 932630)

• Nexus tracer concentrations are incorrectly computed in parallel runs (Defect 932699)

• A well behaves differently in serial and parallel runs (Defect 932706)

• When SATDEBUG is missing from WINDOW input, requesting SATDEBUG output in Nexus causes the software to crash (Defect 932762)

• Restart runs without GRID_FILES in the case file incorrectly cause Standalone to abort (Defect 932769)

• The procedure function which sets the hydraulic method number for a well fails for a WAG well (Defect 932850)

• Well connections which are active during a single-reservoir run are deactivated unexpectedly when the same data is used for one reservoir in a multi-reservoir run (Defect 932887)

• Shut-in wells have production ratios like GOR and WCUT computed for them under some circumstances, which cause PROCs based upon these ratios to behave incorrectly (Defect 933028)

• Nexus crashes when perfs are removed from wells when restarting (Defect 933824)

• Inconsistent behavior of INITIALIZE_ONLY or of missing recurrent data files between Windows and Linux runs (Defects 934014 and 934104)

• Model which runs on Windows fails on Linux with endpoint scaling errors (Defect 934110)

• Elevation profiles applied to wells with WELLHEAD nodes that are re-specified without DEPTH data cause bad depth computations (Defect 934226)

• Nexus simulation run fails with violation of Pmax in surface network (Defect 934433)

• Procedure function to define constraints does not work as documented (Defect 934491)

• Round-off error in saturation OVERRIDE data causes model initialization to fail (Defect 935166)

5000.4.9 Page 71 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • A multi-reservoir model fails to converge when relatively large pore volume overrides are made in the recurrent OVERRIDE data (Defect 935285)

• An incorrectly computed derivative related to the near-critical IFT option causes convergence failures (Defect 935943)

• Salinity initialization is incorrect for one reservoir in a multi-reservoir run (Defect 936159)

• Nexus incorrectly converts certain stream-splitting nodes to simple nodes if they are deactivated and reactivated (Defect 936506)

• The network initialization on a second Newton iteration is not working as intended when a PROC is active (Defect 936507)

• Timestep control criteria when using VIP -style timestepping in Nexus now can be disabled with a NONE keyword (Enhancement 936527)

• Procedure function workover does not reset perforation status at the proper time (Defect 936548)

• The network targeting logic is wrong when a gaslift connection is included in the list of targeted connections but is not constrained by the target (Defect 936639)

• Oil recovery fraction not correctly reported in REGION plot data (Defect 936797)

• Field-level PLOT data is incorrectly written for a multi-reservoir model (Defect 936837)

• A multi-reservoir model with different start times for each reservoir hangs when run in parallel (Defect 936875)

• A procedure which returns the ONTIME set for a well would be useful (Enhancement 937235)

• Use of the geomechanics coupling feature fails to read the pore volume overrides correctly (Defect 937263)

• Nexus attempts and fails to allocate zero size arrays when no wells are active (Defect 937475)

• Connections given a zero rate target do not reopen when the target is changed (Defect 937530)

• ONTIME factors set using a procedure function are not honored (Defect 937658)

5000.4.9 Page 72 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • Condensate tracking in a compositional model does not capture obvious gas coning correctly (Defect 937796)

• Conversion of water injectors to gas injectors causes multiple unexpected well shut- ins (Defect 937830)

• Nexus crashes when a connection is switched from pressure-drop correlation hydraulics to a hydraulic table by a procedure (Defect 938327)

• Network divergences occur after changing the WAG cycle of a well (Defect 938328)

• Initialization of water and gas saturation with overreads should provide a user option to force water and gas zones to be honored (Enhancements 938645 and 938646)

• Nexus should allow different region identifier arrays for pressure threshold and transmissibility multiplier functionality (Enhancement 938648)

• Nexus crashes after issuing warning messages about perf equation elimination (Defect 939042)

• Nexus fails when attempting to restart with fewer relative permeability methods than were defined in the initial run (Defect 939651)

• Addition of an ICD does not affect the well rate in a compositional model (Defect 940043)

• Overrides of permeability arrays do not affect the PLUS face transmissibilities correctly (Defect 940490)

• Including WCUT, GOR, and tracking values would be useful in FLOSTA and CONNLIST classes of plot data (Enhancement 940722)

• SSNOSORT has no affect when entered for a restart run which used sorted spreadsheets (Defect 940782)

• Oscillations caused by conflicts between a QGSMAX constraint and values in an OPTLGR table could be handled better (Enhancement 940963)

• In a procedure, the set_wagparam function sets the value of a different parameter than the one specified (Defect 941325)

• FTRANS data is not applied to gridblocks in a region which is coarsened, but the user is given no indication that the data is not being honored (Defects 941418 and 942196)

• It would be useful to be able to run sector models defined with the boundary flux option in parallel (Enhancement 941513)

5000.4.9 Page 73 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • Requesting MAP output of saturation endpoint arrays in a parallel run causes Nexus to crash (Defect 941581)

• Pressure behavior of very heavy oil in a compositional model is not reasonable (Defect 941699)

• Nexus crashes when a separator is defined without a water PVT method specified (Defect 941761)

• High water-cut wells in a target which are shut in because they cannot meet a minimum flow constraint cause network divergences (Defect 941800)

• Headings in the Well Reservoir Volume Cumulative Summary are misaligned (Defect 941813)

• Some network cumulative values are incorrectly reset to zero upon restart (Defect 942194)

• When DZW is used in hydraulics methods, Nexus treats it also as a datum for correction, which it should not do (Defect 942213)

• Standalone fails to notify user of an invalid controlling or controlled connection when trying to use a connection to a SINK or source for remote control (Defect 942625)

• Oil recovery is incorrectly computed for some reservoirs in a multi-reservoir run (Defect 942812)

• Wells which are constrained by both THP and BHP can lead to network divergences under certain circumstances (Defect 942927)

• Targets which require wells to flow at rates below their specified minimum rate can lead to too many wells shutting in, causing the target not to be met (Defect 942930)

SimDataStudio™

• SimDataStudio™ should be able to help users build boundary-flux sector models (Enhancement 911047)

• Users would like to have both standard and user comments when generating Nexus datasets from within SimDataStudio™ (Enhancement 917447)

• SimDataStudio™ does not allow the user to remove the well economic limit (Defect 931936)

5000.4.9 Page 74 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” SurfNet™

• Model start and end times should be shown with the time step controller, or in a tooltip (Enhancement 827647)

• SurfNet™ cannot correctly display well perforations when the number of perforations in a given layer of the model is greater than 27 (Defect 930856)

• Various SurfNet™ case file import issues have been resolved (Defects 935443, 935444, and 936030)

Nexus Desktop, Job Submittal, and Installation

• The Nexus Desktop should allow users to choose whether or not to validate all include files before submitting a run (Enhancement 941276)

Nexus View

• Grid data sometimes cannot be read or displayed when multi-reservoir models are loaded into Nexus View (Defect 934172)

• The default value for the number of gridblocks in a model which forces the loading to be done in a layer-by-layer fashion is too small for 64-bit computers (Defect 936566)

Documentation

• Manual example for the REGDATA keyword is incorrect, and causes Standalone to report an error when used in sample data (Defect 854393)

• Nexus Keyword Document should explain why only one well file is recommended (Defect 922757)

• The explanation of how minimum rate constraints are applied is incomplete, and does not explain why wells can flow at rates which are smaller than the specified minimum rate (Defect 923480)

• SurfNet help does not work correctly when accessed from Internet Explorer 10 (Defect 925278).

• The description of the ALQ GASRATE conflicts with a mention of the same keyword in the Notes section (Defect 929913)

5000.4.9 Page 75 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • Nexus unit system documentation is confusing and incorrect in its declaration of some units, like cumulative gas volumes (Defect 930134)

• Explanation of PINCHOUT keyword could use more detail (Enhancement 931397)

• It is not documented well that there are differences between the contents of INIT and RECUR classes of map output as generated by Nexus, and those contents when generated by VIP (Defect 933902)

• The descriptions of the INITIALIZE_ONLY keyword in the Nexus Keyword Document are unclear and appear to conflict with other sections of the documentation (Defect 934107)

• The keyword IMPESUPSTREAM is misspelled in the documentation, which can cause confusion (Defect 938686)

• The documentation incorrectly states that numerical derivatives are the default in Nexus computations (Defect 939513)

• The MULT card definition for structured grid input doesn’t clearly indicate there are two different input forms, depending on the number of values the user provides (Defect 940503)

• FTRANS documentation for structured grid input incorrectly claims that standard connections are not modified by this keyword; additionally, FTRANS documentation is confusing because the two different input forms are not cross-referenced to one another (Defects 941420 and 943569)

• An explanation of the difference between the PVR and PV arrays is requested (Enhancement 941512))

5000.4.9 Page 76 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Known Issues

The following known issues exist in the 5000.4.9 release of Nexus and VIP :

General

• E2V, SimDataStudio™, and SimResults™ do not run on Linux systems

Nexus Simulator

• Users cannot currently apply grid functions to non-default region sets in a structured- grid model (Enhancement 839670)

• Some arrays written to the VDB do not appear to have correct minimum and maximum values recorded (Defect 850908)

• A multi-reservoir model fails due to an overconstrained system (Defect 912468)

• Some OUTSTART EQUILREGION reports can be incomplete for parallel runs (Defect 942968)

• Linux and Windows runs may show slightly different performance statistics for the same run

• Simulations with very large wellbore constants may have wells shutting in for backflow due to round-off error

• When using simultaneous targets in Nexus (the default), PROCs should not call the functions which re-solve the network or the network potential if target rates are being changed by the PROC

VIP

• Some VIP models which would run in older versions of VIP crash with floating-point errors; this is because VIP now aborts when invalid computations occur. In many cases, choosing different solver options can avoid the crash.

• The fix for defect 899842 may cause previously running models to exit with input data errors. This will occur if values for ANGLA or ANGLV fall outside the ranges of -360 to 360 degrees or 0 to 180 degrees, respectively. Values outside these ranges are almost input error.

5000.4.9 Page 77 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • The two-point scaling option END2P does not behave as described in the VIP Technical Reference manual; for the two-point option, KRWRO and KRGRO are not neglected as the manual states. To obtain the behavior described in the VIP Technical Reference, remove the KRWRO and KRGRO arrays from the input.

• VIP miscalculates the effective water viscosity around wells. The effect is usually small, so this defect is not likely to be fixed, as it will cause answers to change.

Nexus Desktop/Job Submission

• Standalone jobs cannot be stopped from the job submitter; they must be stopped manually by killing the Standalone process (Defect 820657)

• The Nexus Desktop STOP button does not affect jobs running remotely, whether queuing is used or not (Defects 868232 and 884980)

• The “Generate SPN” checkbox on the job submitted does nothing for jobs which are submitted to a remote system (Defect 928069)

• When the pathname to the OPTIONS file in the Nexus case file includes the path element “..”, the Nexus Desktop parallel mode is locked to Autodecompose (Defect 942608)

• Extremely long case names may cause job submission to fail.

• Job submission to a remote Windows system is not supported.

• System time differences between the submitting system and a remote system to which the job is being submitted can sometimes cause job failure

SimDataStudio™

• SimDataStudio™ does not correctly handle VIP input data with commas; it does not treat a comma as white space the way VIP oes (Defect 836440)

• SimDataStudio™ does not recognize the STATION keyword (Defect 925947)

• VAITS initialization is not supported in Nexus mode; INTSAT will be used

• Not all Nexus functionality is exposed by SDS

• Some VIP keywords are not correctly converted by SDS into Nexus keywords

5000.4.9 Page 78 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • Switching from Nexus mode to VIP mode within SDS is highly discouraged, because the resulting VIP model, and any models derived from it, are likely to contain invalid data

Nexus View

• Filtering of RECUR data by a filter based upon INIT data is not possible (Enhancement 869318)

• Network elevation profiles are not displayed in Nexus View (Enhancement 871709)

• Data clipping doesn’t always work correctly for values near an endpoint of the clipping range (Defect 875573)

• Radial VIP models do not display correctly (Defect 877574)

• Nexus View cannot display ECLIPSE dual-porosity models read from EGRID files.

SimConvert

• SimConvert cannot build a VDB from a plot file which exceeds 2 GB (Enhancement 859923)

• SimConvert does not provide unit information for plotfiles exported from a VDB (Defect 862158)

• SimConvert does not allow the user to exclude timesteps when importing a map file into a VDB (Enhancement 883951)

• SimConvert fails to load a large Rescue file (Defect 901196)

SurfNet™

• SurfNet™ displays an incorrect number of perforations for some dual-porosity models (Defect 926301)

Documentation

• SimDataStudio™ documentation does not cover all the features which have been implemented. The new HTML help feature is intended to address most of these features.

5000.4.9 Page 79 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” SimResults™

• Some data from Nexus® PLOT files (binary or formatted) is displayed incorrectly, while the same PLOT data stored in a VDB is displayed correctly. PLOT files exported from a VDB by SimConvert also display incorrectly. The workaround is to import PLOT data into the VDB before viewing. (Defect 895259)

• SimResults sometimes crashes when trying to load data from the Open entry under the File menu (Defect 914160). Changing the SimResults executable to run under Windows XP compatibility mode seems to work around the problem. Contact Landmark Customer Support if you need details on this workaround.

5000.4.9 Page 80 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” Contacting Landmark Customer Support

Landmark Customer Support operates Technical Assistance Centers (TACs) in Malaysia, the United Kingdom, and the United States. Customer Support provides technical assistance on Landmark software applications. The website for Landmark is:

Landmark (http://www.landmarksoftware.com)

Requests for support can be made by:

• Landmark Customer Support Portal

See Submitting a Request for Technical Assistance below.

• Email

[email protected]

• Telephone

See Technical Assistance Centers below.

Submitting a Request for Technical Assistance

To submit a request for technical assistance:

1. Open Landmark Customer Support Portal (http://www.landmarksoftware.com/Pages/ Support.aspx) in a browser.

2. Hover the mouse cursor over the Sign In To Landmark Portals area on the right of the webpage. Text boxes for your registered email account and password appear.

3. Log in. The Sign In To Landmark Portals area is renamed to Landmark Portals.

4. In the Landmark Portals area, select Customer Support Portal. The Support Portal Home page appears in the browser.

5. In the Case & Defect Information area on the right, select Create A New Case. The Add Case page appears in the browser.

6. Fill in the requested information.

Provide:

• Details about your technical concern, including any error messages.

5000.4.9 Page 81 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?” • Workflow steps where the problem occurred.

• Attachments of screen shots that capture the problem.

7. Click Submit.

A support analyst in the nearest Technical Assistance Center will respond to your request.

Technical Assistance Centers

The hours of operation are:

8:00 a.m. - 5:00 p.m., local time

Monday-Friday, excluding holidays

The phone numbers for the Technical Assistance Centers are:

• Asia Pacific, Malaysia

+61-8-9481-4488

Toll Free +1-800-803-687 (Malaysia)

• Europe, Africa, Middle East, Eurasia, United Kingdom

+44-1372-868686

• Latin America, USA

+1-713-839-3405 (Spanish, Portuguese, English)

• North America, USA

+1-713-839-2200 (Houston, TX, USA)

Toll Free +1-877-435-7542

For more information about contacting Customer Support, see:

http://www.landmarksoftware.com/Pages/ContactSupport.aspx

5000.4.9 Page 82 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of:

Halliburton | Landmark Software & Services 2107 CityWest Blvd, Building 2, Houston, Texas 77042-3051, USA P.O. Box 42806, Houston, Texas 77242, USA Phone:713-839-2000, FAX: 713-839-2015 Internet: www.halliburton.com/landmark

Trademarks 3D Drill View, 3D Drill View KM, 3D Surveillance, 3DFS, 3DView, Active Field Surveillance, Active Reservoir Surveillance, Adaptive Mesh Refining, ADC, Advanced Data Transfer, Analysis Model Layering, ARIES, ARIES DecisionSuite, Asset Data Mining, Asset Decision Solutions, Asset Development Center, Asset Development Centre, Asset Journal, Asset Performance, AssetConnect, AssetConnect Enterprise, AssetConnect Enterprise Express, AssetConnect Expert, AssetDirector, AssetJournal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver Advisor, AssetOptimizer, AssetPlanner, AssetPredictor, AssetSolver, AssetSolver Online, AssetView, AssetView 2D, AssetView 3D, Barrier Assurance Monitoring, BLITZPAK, CartoSnap, CasingLife, CasingSeat, CDS Connect, CGMage Builder, Channel Trim, COMPASS, Contract Generation, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataServer, DataStar, DataVera, DBPlot, Decision Management System, DecisionSpace, DecisionSpace 3D Drill View, DecisionSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace Atomic Meshing, DecisionSpace Base Module, DecisionSpace Data Quality, DecisionSpace Desktop, DecisionSpace Dropsite, DecisionSpace Geosciences, DecisionSpace GIS Module, DecisionSpace GRC Module, DecisionSpace Nexus, DecisionSpace Reservoir, DecisionSuite, Deeper Knowledge. Broader Understanding., Depth Team, Depth Team Explorer, Depth Team Express, Depth Team Extreme, Depth Team Interpreter, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery 3D, Discovery Asset, Discovery Framebuilder, Discovery PowerStation, Discovery Suite, DMS, Drillability Suite, Drilling Desktop, DrillModel, DrillNET, Drill- to-the-Earth-Model, Drillworks, Drillworks ConnectML, Drillworks Predict, DSS, Dynamic Frameworks to Fill, Dynamic Reservoir Management, Dynamic Surveillance System, EDM, EDM AutoSync, EDT, eLandmark, Engineer’s Data Model, Engineer’s Desktop, Engineer’s Link, ENGINEERING NOTES, eNotes, ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker, ezTracker2D, ezValidator, FastTrack, Field Scenario Planner, FieldPlan, For Production, FrameBuilder, Frameworks to Fill, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, Geologic Interpretation Component, Geometric Kernel, GeoProbe, GeoProbe GF DataServer, GeoSmith, GES, GES97, GesFull, GESXplorer, GMAplus, GMI Imager, Grid3D, GRIDGENR, H. Clean, Handheld Field Operator, HHFO, High Science Simplified, Horizon Generation, I2 Enterprise, iDIMS, iEnergy, Infrastructure, iNotes, Iso Core, IsoMap, iWellFile, KnowledgeSource, Landmark (as service), Landmark (as software), Landmark Decision Center, LandNetX, Landscape, Large Model, Lattix, LeaseMap, Limits, LithoTect, LogEdit, LogM, LogPrep, MagicDesk, Make Great Decisions, MathPack, MDS Connect, MicroTopology, MIMIC, MIMIC+, Model Builder, NETool, Nexus (as service), Nexus (as software), Nexus View, Object MP, OneCall, OpenBooks, OpenJournal, OpenLink, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWire Client, OpenWire Server, OpenWorks, OpenWorks Development Kit, OpenWorks Production, OpenWorks Well File, Operations Management Suite, PAL, Parallel-VIP, Parametric Modeling, Permedia, Petris WINDS Enterprise, PetrisWINDS, PetroBank, PetroBank Explorer, PetroBank Master Data Store, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PLOT EXPRESS, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family, Power Interpretation, PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, PowerModel, PowerView, PrecisionTarget, Presgraf, PressWorks, PRIZM, Production, Production Asset Manager, PROFILE, Project Administrator, ProMAGIC Connect, ProMAGIC Server, ProMAX, ProMAX 2D, ProMax 3D, ProMAX 3DPSDM, ProMAX 4D, ProMAX Family, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+, QUICKDIF, Quickwell, Quickwell+, Quiklog, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real Freedom, Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production Surveillance, Real Time Surveillance, Real-time View, Recall, Reference Data Manager, Reservoir, Reservoir Framework Builder, RESev, ResMap, Resolve, RTOC, SCAN, SeisCube, SeisMap, SeisMapX, Seismic Data Check, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisWorks PowerView, SeisWorks2D, SeisWorks3D, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert, SimDataStudio, SimResults, SimResults+, SimResults+3D, SIVA+, SLAM, Smart Change, Smart Deploy, Smart Flow, Smart Skills, Smart Start, Smart Sustain, Smart Transform, Smart Vision, SmartFlow, smartSECTION, smartSTRAT, Spatializer, SpecDecomp, StrataMap, StrataModel, StratAmp, StrataSim, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SurfNet, SynTool, System Start for Servers, SystemStart, SystemStart for Clients, SystemStart for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, T-Grid, The Engineer’s DeskTop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, TracPlanner Xpress, Trend Form Gridding, Trimmed Grid, Tubular Basic, Turbo Synthetics, Unconventional Essentials, VESPA, VESPA+, VIP, VIP-

5000.4.9 Page 83 of 84 July 2014 Nexus® and VIP® Software Release Notes

Go To “What’s in this Release?”

COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, vSpace, vSpace Blueprint, vSpace Onsite, WavX, Web Editor, Well H. Clean, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellSolver, WellXchange, WOW, Xsection,You’re in Control. Experience the difference., ZAP!, ZEH, ZEH Plot, ZetaAnalytics, Z-MAP, Z-MAP Plus, and ZPS are trademarks, registered trademarks, or service marks of Halliburton.

All other trademarks, service marks, and product or service names are the trademarks or names of their respective owners.

Note The information contained in this document is subject to change without notice and should not be construed as a commitment by Halliburton. Halliburton assumes no responsibility for any error that may appear in this manual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore, this statement may not apply to you.

5000.4.9 Page 84 of 84 July 2014