Coreform Cubit FAQs


General Cubit questions

What is Cubit?

Answer: Cubit is an advanced meshing pre-processor based on decades of Cubit development. For more than two decades, we have worked with Sandia National Laboratories as a major contributor to the Cubit development team. And since 2019, Coreform has been the authorized distributor of Cubit for academic and commercial use. Coreform has taken the best of Cubit and added a whole lot more to make Cubit.

How do I cite Coreform software in my publication?

Answer: When citing Coreform software, please use the following APA standards.

When mentioning software in text, use the proper name of the software, along with the version number. For example,

"We used Cubit XX.X to generate the meshes…"

When citing Coreform software in-text, use the following:

(Cubit, 2018)

When citing Coreform software in a bibliography, use the following:

Cubit (Version XX.X) [Computer software]. Orem, UT: Coreform LLC. Retrieved from http://coreform.com

See guidelines in section 7.08 of Publication Manual of the American Psychological Association, (6th ed., 1st printing) for citing software.

What are the differences between Coreform Cubit and Sandia National Laboratories' Cubit?

Answer: Coreform works jointly with Sandia to co-develop the government-use version of Cubit. Coreform Cubit includes the on-going joint Coreform and Sandia development to the Cubit kernel, plus unique additional functionality.

How many mesh elements can Cubit generate?

Answer: The number of elements depends on whether you are running a 32- or 64-bit system and the amount of memory your system has. When a computer needs to swap to disk, the meshing time is increased. There are Cubit users who are regularly generating meshes over 500 million elements on a 64-bit Windows machine with 128 gigabytes of memory. Cubit can generate a 27 million element mesh on an 8 gigabyte machine in less than a minute and over 100 million element mesh on a 32 gigabyte machine in 30 minutes.

What element types does Cubit support?

Answer: Cubit can generate tetrahedral, hexahedral, and hybrid meshes.

Does Cubit support hybrid meshing?

Answer: Yes, Cubit supports hybrid meshes. Pyramids and wedges can be used on adjacent surfaces to transition between volumes with tet and hex meshes.

Does Cubit allow boundary layer meshing?

Answer: Yes, Cubit includes the ability to create boundary layers.

How is Cubit licensed for use on stand-alone computers and on a network?

Answer: Cubit can be licensed on a per seat basis for stand-alone machines or on a concurrent use basis for local area network users. For example, a company with five Cubit licenses may have two licenses installed on two stand-alone computers and the remaining three licenses can be installed on a local area network. All authorized network users can access Cubit, three users at any given time. See Cubit Licensing for more information.

Formats and support

What operating systems are supported?

Answer: Cubit versions are available for Windows, Linux, and Mac. Cubit supports the following 64-bit platforms:

  • Linux with glibc 2.5+ and libstdc++ v4.4+ 64-bit (e.g. Red Hat 6, Fedora 12, SUSE 12, Debian 6, Ubuntu 10.04)
  • Windows 7, 8, 8.1, and 10 64-bit
  • Mac OS X 10.10, 64-bit

OpenGL 3.2 or greater is recommended. (A software-based implementation of OpenGL 3.2 is provided as an alternative, but may slow the process.)

Coreform does not support 32-bit platforms.

What are the minimum hardware requirements?

Answer: Coreform recommends the following minimum hardware requirements:

  • 4GB RAM (8GB or more recommended)
  • 1GB disk space
  • Graphics card and driver capable of supporting OpenGL 3.2 (A software-based implementation of OpenGL 3.2 is provided as an alternative, but may slow the process.)
  • 1280 x 1024 screen resolution

NOTE: More memory and faster processors are recommended for meshes with very large mesh element counts.

What geometry and mesh file formats does Cubit support?

Answer: Cubit works with most CAD tools and solvers. See Cubit Translators for information about supported file formats.

Is software training available?

Answer: Coreform offers three levels of training.

  • Basic. Cubit GUI, features, and project planning.
  • Advanced. Cubit advanced features and tips.
  • Customization. Creating custom components using C++ and Python.

See Training for more information.

Activation and installation.

When I launch Cubit, the Product Activation screen appears.

Answer: Cubit requires a valid license file before it will launch. The license file can be located on the same computer as Cubit or on a network license server. The license type that you purchased will determine whether Cubit can be run on network or a standalone computer. See Product Activation for detailed information about activating Cubit.

How do I activate Cubit?

Answer: Please see Product Activation for more information on installing Cubit on a stand-alone computer or network.

NOTE: Network installations require that additional software called RLM-Server license manager be installed on a computer that will act as the license server for network computers that will run Cubit. RLM-Server and installation instructions are available here.

How do I find the hostID to use in the activation process?

Answer: Use the rlmutil utility to find the hostID that RLM uses for activation. The options are "rlmutil rlmhostid ether".

Node-locked In a terminal window, navigate to the Cubit\bin folder (for example, "c:\Program Files\Cubit 16.0\bin" or "/opt/Cubit 16.0/bin"). Type "rlmutil rlmhostid ether"

Floating In a terminal window, navigate to the RLM-Server folder and type "rlmutil rlmhostid ether"

Error: "Unable to save license to…"

Answer: If you receive this error in the Product Activation window, you might not have write permission to the /bin/licenses folder. However, the license may have been generated on the Coreform server. Visit your My Licenses page and scroll to the bottom of the page to download the license file to the Cubit/bin/license folder.

NOTE: If this error occurs on the RLM-Server network server, the license file should be downloaded to the RLM-Server folder. (See Network Troubleshooting below)

Error: "Failed to checkout features from license file."

Answer: If you receive this error in the Product Activation window, you might be running Cubit on a virtual machine. By default, VM is not enabled in the license. Please contact Coreform to request that VM be enabled in your license.

How to specify the install location for Cubit on a Linux machine.

Answer: You can install Cubit to a specific folder. For example, the following method will install Cubit to /home/user:

  • Download the .deb file.

  • # extract the collapsing-contents of the .deb file
    ar vx Cubit-XX.X-Lin64.deb

  • # install the data files (the files will go into /opt)
    sudo tar -zx --directory=/home/user -f data.tar.gz (will make a /home/user/opt/Cubit-XXX/ folder)

  • # extract the control files
    tar zxvf control.tar.gz

  • To install the desktop shortcuts for this modified location, modify the coreform-Cubit-XXX.desktop file under this installation, then run xdg-desktop-menu to install it.

How to install Cubit on Linux without a deb or rpm tool.

Answer: Some distributions of Linux do not have a deb or rpm tool. Cubit can be installed using the following method:

  • Download the .deb file.

  • # extract the collapsing-contents of the .deb file
    ar vx Cubit-XX.X-Lin64.deb

  • # install the data files (the files will go into /opt)
    sudo tar -zx --directory=/ -f data.tar.gz

  • # extract the control files
    tar zxvf control.tar.gz

  • # setup the license manager and desktop shortcuts
    sudo ./postinst

How to install Cubit on a Mac.

Answer: Cubit is distributed as a .dmg file and can be installed using the following method:

  1. Download the .dmg file from My Downloads in your account.
  2. Open the .dmg file.
  3. Drag the Cubit icon to Applications to install.
  4. Launch Cubit from the Applications folder. If you get an error about an unidentified developer, go to Security under System Preferences to allow Cubit.
  5. When Cubit launches for the first time, you will see the Product Activation window. Enter the product key and click Activate.

Mac Error: Unidentified developer on Mac.

Answer: If you get an error about an unidentified developer, go to Security under System Preferences to allow Cubit.

Mac Error: "Unable to save license to /Volumes/Cubit-XX.X.X-Mac64/Cubit-XX.X.app/…"

Answer: This error occurs when activating Cubit in the dmg image instead of the installed Cubit. When you open the dmg file, you must drap the Cubit application to the Applications folder to install Cubit. Then, launch Cubit from the Applications folder.

Help with the RLM license manager (www.reprisesoftware.com)

Answer: Coreform uses the RLM license manager from Reprise Softaware. Reprise has some useful FAQs. Visit the Reprise Sofware website for more information.

Network troubleshooting

What is the difference between RLM-Server and TrelisLM?

Answer: RLM-Server is the current name of the license server for managing floating licenses. It was previously named TrelisLM. RLM-Server includes a GUI for simplifying the activation process.

Common Network Problems

Answer:

  • Did you install RLM-Server and activate the license on the computer you will use as the license server?

    For network installations, two separate software programs must be installed. RLM-Server is the server software and Cubit is the client software. RLM-Server is available at RLM-Server Downloads

  • Did you activate the computer with RLM-Server installed?

    If RLM-Server is activated a license file with a .lic extension will be in the RLM-Server folder. Use the rlm_activate utility in the RLM-Server folder to activate the software, or visit your license page in your Coreform account. See RLM-Server Installation Instructions for more information.

  • Is the Coreform ISV server running?

    Sometimes after activation, the license server software needs to be restarted (Does not require a reboot of the machine). Check to see that the Coreform server is running. In a web browser on the server, type http://localhost:5053. This should open the Reprise License Server Administration page. In the left column, click Status. You should see three tables. In the ISV Servers table you should see Coreform port 5055 running Yes. If not, click on Reread/Restart Servers in the left column. Check again by clicking Status.

  • Is there another RLM ISV server also using port 5055?

    Other software using RLM may be using the same port number. Change the port number for Cubit to avoid conflicts.

  • Did you install and configure Cubit on the client?

    After RLM-Server is installed and activated (A .lic file is in the RLM-Server folder), ensure that Cubit is configured properly on each network client computer. When Cubit launches, it will request a license from the RLM-Server license server, so it needs to know where RLM-Server is located. The client machine must be able to access the server over the network. In the Cubit Product Activation window, select Floating: Connect to a license server. Enter the Hostname or IP Address of the computer where RLM-Server is installed. The default port is 5053. The Product Activation window is under the Help menu.

Unable to write license file on the license server using the rlm_activate tool.

Answer: When activating RLM-Server using the rlm_activate tool, be sure to run as root or admin. This will allow you to have read/write access to the installation location.

Error: "Communication error with license server. To activate Cubit…"

Answer: This error message is associated with Cubit 14.0.5. It means that a valid license file is not found. To fix this problem, check to see that a valid license file is located in the Cubit\bin\licenses folder.

Error: "Failed to connect to or get license from license server"

Answer: There may be several possible reasons why Cubit is not able to access the RLM-Server server license:

  • Cubit/license version mismatch. If the version of Cubit is newer than the version permitted by the floating license, update the license or use the matching version of Cubit. This may occur when a new version of Cubit is released. The download for Cubit is updated but the floating license on the license server is not updated. The floating license can be updated by running the activation process again using the product key found on the My Licenses page.

  • RLM-Server is not installed. Cubit and RLM-Server must be installed for a floating license to work. RLM-Server is the server software that is installed on a network server or workstation that will act as the license server. It must be installed and activated with a valid license file before a network installation of Cubit can be used.

  • RLM-Server is not activated. After installing RLM-Server, use the rlm_activate command line utility located in the RLM-Server installation folder to activate RLM-Server over the Internet. It will communicate with the Coreform server and download a floating license file.

  • RLM-Server is not running. During the installation, RLM-Server should start automatically. To check the status of the server, type "http://localhost:5054/" in a web browser. The Reprise License Server Adminstration page will open. On the left sidebar can click Status to see if the Coreform server is running. To start the Coreform server, click Reread/Restart Servers.

  • Network communication error. RLM-Server must be installed on a network server or workstation that acts as the license server. This server must be accessible to the workstation where Cubit is installed. This includes configuring a firewall to allow access to the server. Cubit will not work properly if it cannot communicate with RLM-Server.

How to Configure RLM to Manage Software from Multiple Vendors

Answer: RLM-Server is based on RLM from Reprise Software. Reprise provides two methods for using RLM with software from two different software vendors:

  • Separate RLM installations and ISV servers
  • Single RLM installation that manages two ISV servers (recommended)

It is recommended that you use a single RLM installation and have it manage two ISV servers. By default, the RLM server uses port 5053 to communicate with the ISV software. All ISV software should use the same port 5053, but each ISV server will use a unique port. For example, ISV A on port 5055 and ISV B on port 5056 would both use port 5053 to communicate with the RLM license server. All ISV license files should be in the same folder.

For more information, see Managing Software from Multiple Publishers on the Reprise Software website.

How do I suppress the DENIED messages in the server log?

Answer: The RLM-Server log will show a DENIED message when Cubit requests a license for features that the serve does not have. To suppress this message, create a text file in the RLM-Server installation called "coreform.opt" with the text "NOLOG denied". While with will suppress the DENIED license message, it may potentially limit the ability to identify when licenses are not checked out properly.

How do I restart (stop/start) the RLM-Server?

Answer: The RLM-Server can be restarted from the RLM-Server Administration page. To access this page, type "http://localhost:5054/" in a web browser. Use the commands on the left sidebar.

If your server does not have a GUI, you can use the following command (as root):

  • Linux: /etc/init.d/rlm.sh restart
  • Windows: "rlmutil rlmreread" from the C:\Program Files\RLM-Server folder.

Stopping and starting RLM-Server — Linux

  • $ sudo /etc/init.d/rlm.sh stop
  • $ sudo /etc/init.d/rlm.sh start

Stopping and starting RLM-Server — Windows

  • Search for Services app
  • Select RLM in the list of services
  • Click Stop the service to stop RLM
  • Click Start the service to start RLM

How do I stop and remove the RLM-Server?

Answer: The RLM-Server can be removed from a server with the following commands:

Remove the RLM service.

  • Redhat-based systems: (root) chkconfig --del rlm.sh
  • Debian-based systems: (root) update-rc.d rlm.sh remove

Then remove all the files that are part of the installation.

  • rm /etc/init.d/rlm.sh
  • rm -rf /opt/RLM-Server

How do I setup Cubit on a cluster?

Answer: There are two ways you might setup Cubit on a HPC cluster. The license manager can be installed on a node or a computer not part of the cluster. Any Cubit installation on an HPC should have a floating license, regardless of where the RLM server is installed.

First Option: We recommend that RLM-Server be installed on a computer (Windows or Linux) that is not part of the HPC cluster. The instructions for installing and activating RLM-Server on that computer are the same as any normal computer (See Cubit Network Installation Instructions). If the external computer has an Internet connection, you can run the rlm_activation on that node, otherwise you can use the Offline Activation option.

After the RLM-Server is installed and the license activated, install Cubit software on the cluster nodes and point back to the external machine running the license manager. This can be done by starting Cubit on the node and when the Activation Dialog appears, enter the IP address or hostname of the license server, or by manually creating a remote.lic file in the /bin/licenses folder of each node. Cluster nodes can have a shared file system, so it is likely that Cubit is installed 'once' with only one remote.lic file to create, then that installation is used by multiple nodes in the cluster.

Second Option: The RLM-Server can be run on a node on the cluster. The license activation is done in the same way as described in the first option, depending on whether the node has Internet connection or not.

After the RLM-Server is installed on a node, install Cubit software on the cluster nodes. You can manually create a remote.lic file in the /bin/licenses folder of the node, or start Cubit on each node and when the Activation Dialog appears, enter the IP address or hostname of the server node within the cluster instead of the IP address or name of the cluster itself.

NOTE: Indirect GLX was disabled by default in Xorg 1.17. Starting with XQuartz version 2.7.9, to enable indirect GLX and to allow remote visualization on the cluster you will have to issue at the terminal command prompt of your mac: defaults write org.macosforge.xquartz.X11 enable_iglx -bool true

Help with RLM-Server (www.reprisesoftware.com)

Answer: Coreform uses the RLM-Server license manager from Reprise Softaware. Reprise has some useful FAQs. Visit the Reprise Sofware website for more information.

Linux-specific issues

How to install Cubit using Linux commands.

Answer: You can install Cubit using the following teminal commands:

  • For Debian based Linux OS:
    sudo dpkg -i ./Cubit-15.2.2-Lin64.deb

  • For Red Hat based Linux OS:
    sudo rpm -ivh ./Cubit-15.2.2-Lin64.rpm

How to specify the install location for Cubit on a Linux machine.

Answer: You can install Cubit to a specific folder. For example, the following method will install Cubit to /home/user:

  • Download the .deb file.

  • # extract the collapsing-contents of the .deb file
    ar vx Cubit-XX.X-Lin64.deb

  • # install the data files (the files will go into /opt)
    sudo tar -zx --directory=/home/user -f data.tar.gz (will make a /home/user/opt/Cubit-XXX/ folder)

  • # extract the control files
    tar zxvf control.tar.gz

  • # setup the license manager and desktop shortcuts
    sudo ./postint

  • To install the desktop shortcuts for this modified location, modify the coreform-Cubit-XXX.desktop file under this installation, then run xdg-desktop-menu to install it.

How to install Cubit on Linux without a deb or rpm tool.

Answer: Some distributions of Linux do not have a deb or rpm tool. Cubit can be installed using the following method:

  • Download the .deb file.

  • # extract the collapsing-contents of the .deb file
    ar vx Cubit-XX.X-Lin64.deb

  • # install the data files (the files will go into /opt)
    sudo tar -zx --directory=/ -f data.tar.gz

  • # extract the control files
    tar zxvf control.tar.gz

  • # setup the license manager and desktop shortcuts
    sudo ./postinst

Ubuntu GUI delay problem

Answer: Cubit's graphics engine may not work properly if you are using the nouveau video driver. This problem should be resolved by using a Nvidia proprietary driver.

Customization

Can I customize the Cubit GUI?

Answer: The Cubit GUI allows for the creation of custom components and the modification of panels, menus, and toolbars using the CubitInterface. CubitInterface is an API for interacting with the CUBIT libraries. Documentation for CubitInterface can be found here.

How can I localize the Cubit GUI for a different language?

Answer: The Cubit GUI can be localized using Qt Liguist (free download) and the Cubit translation file. Many text strings can be translated to another language or customized for your organization. Please see the video on localizing Cubit.

Coreform Forum

Take advantage of this great resource to find answers and post questions. about geometry, meshing, importing/exporting, and more.