Frequently Asked Questions

Laptops are not recommended for heavy modeling workloads. For occasional use, the following has been tested successfully:

Dell XPS 16 (Model 9640)
Intel Core Ultra 9 185H
64 GB RAM
RTX 4060 GPU
2 TB NVMe SSD
Windows 11 Pro

Laptops are not recommended for heavy modeling workloads. For occasional use, the following has been tested successfully:

Each ITASCA program lists minimum and recommended system requirements on its product page. Minimum requirements will run the software but do not guarantee performance. Recommended systems are intended for practical, real‑world use.

ITASCA consulting engineers use high‑performance desktop systems internally. Example configurations currently in production include:

AMD-Based Desktop

CPU: Ryzen Threadripper PRO 5975WX
Memory: 64 GB minimum
GPU: GeForce RTX 4060
Storage: NVMe SSD (OS) + high‑capacity data drive
OS: Windows 11 Pro (24H2)

Intel-Based Desktop

CPU: Core i9‑13900K
Memory: 128 GB
GPU: GeForce RTX 4060
Storage: NVMe SSD (OS) + high‑capacity data drive
OS: Windows 11 Pro (24H2)

General rule: Faster processors result in faster calculations.

CPU model comparisons across manufacturers (Intel vs. AMD) are not straightforward, and real‑world performance varies based on system configuration. ITASCA software is not compiled or optimized for any specific CPU architecture.

Most—but not all—features of ITASCA programs are multithreaded. Only multithreaded features benefit from multiple cores or processors.

Multiple physical CPUs are most effective when running multiple models in parallel
A single model sees little benefit from multiple physical CPUs

Optimal configuration:
A single physical CPU with high core count and high clock speed

General rule: More RAM is better.

RAM stores the active model during runtime. Performance degrades significantly when RAM is fully utilized and disk swapping occurs.

RAM Channels (Important)

ITASCA software is highly dependent on memory bandwidth. For best performance:

Populate RAM evenly across all available memory channels
Example: 4 × 16 GB sticks perform better than 1 × 64 GB stick
Follow motherboard vendor guidelines for memory slot population

Recommended

4K-capable GPU (3840 × 2160)
OpenGL v3.3+ for best performance and features

Minimum requirement: OpenGL v1.5

Windows

Supported: 64‑bit Windows 11
Windows 10 is not officially supported but is expected to function

Linux

Supported: Ubuntu 22.04.5 LTS (Jammy Jellyfish)
Requires a valid ITASCA web license
No additional cost vs. Windows
GUI and command‑line versions available
Model files are fully cross‑platform
Distributed as a Debian package; container installer available on request

WEB LICENSES

Verify that you have been assigned as a user of the license. Go to itascalicenses.com, login, and click Licenses I Use and ensure that the license you are trying to use is listed. If not, contact the license manager to add you as a user.
In the Itasca software program you are trying to use, go to Help – License – Specify License location. Ensure that only Web license is checked. Make sure you are using the same email and password you use to log on to itascalicenses.com.

Click the Test button. If the email address or password is incorrect, the test will let you know.
The web license requires an internet connection. If you are not connected to the internet, the test will also indicate this.
Ensure your computer clock is correct. Visit https://time.is to check your clock, most computers have the clock synchronized automatically, but you can also use the 3^rd party free software Dimension 4 http://www.thinkman.com/dimension4/index.htm to sync your clock more often than Windows does by default. Note that when pressing the Test button on the License Location dialog, it may show that your time is correct, even when it isn’t.
Ensure that other users (or yourself) are not using the license. For every seat in a license, you can run two instances on the same computer. So, if you have a single-seat license, and if a user on another computer is using the license, you will not be able to use it at the same time.
Itasca software using a web license needs to be able to communicate with the URL https://gateway.itascacloud.com/prod on port 443. Ensure that your firewall is open to that URL on port 443. Note that this is the standard SSL port and will be open for most systems.

USB HARDLOCK KEY

There are a range of problems that may arise related to the user’s key (also sometimes referred to as the USB key, hardware lock, hardlock, or dongle) that secures Itasca software. The steps below, which move from least to most severe, are actions the end-user can take prior to contacting Itasca for technical support in the event that there is a key-related problem at program startup. For complete information about troubleshooting the Thales USB key, please download Thales End User Troubleshooting Guide and visit their website.

STANDARD (DESKTOP) LICENSE

1) Cycle the key through the other USB ports.

Often, a key problem can come from a conflict or corruption in the settings that match up the key, the key driver, and the specific USB port in use (all three components are in play to make any USB device work). This situation most commonly occurs when the key provided for use with the Itasca software gets plugged in before the software is installed, causing Windows to automatically assign an incorrect driver to that port/key pair.

To perform this step, remove the key and put it into a different USB port. If the step works, popup notifications like the ones below will appear in the lower right corner of the screen (the exact pop-ups and text will vary depending on the Windows operating system in use).

followed by

If this occurs, try the software again. At this juncture, it should work. Also, the key should be able to be put back in the original USB port and work correctly. If this doesn’t happen on the first new USB port you try, continue working through all the available USB ports on a machine before moving on to the next step.

2) Download and install the latest drivers for the key from the Thales website.

It is recommended that the security key be removed before running the driver installation.

This step is quite safe; the SafeNet installation will not overwrite a newer driver with an older one. Updating to a newer driver through a clean installation can clear up the problems stemming from cases of conflict, corruption, or other issues related to the presence of earlier Sentinel USB key drivers.

3) Download and run the the “SSD CleanUp” utility from Thales and retry installation.

The “SSD Cleanup” utility is provided on the same page of the Thales website as the latest driver download. Note there are two versions available, one for 32-bit and one for 64-0bit Windows. The user must select the appropriate version. These are listed last on the “Windows Drivers & Utilities” table.

This utility removes all traces of the current and any past Sentinel key driver installations. To use, we recommend the following steps:

Uninstall the Itasca software.
Remove the USB key from the computer.
Run SSD Cleanup.
Reboot the computer.
Run the downloaded driver installation from Step 2 above.
Re-install the Itasca software.
Plug in the USB key.
Run the software.

During this sequence, be sure to follow any instructions to reboot the computer as they appear.

What Next?

If none of the steps described on this page resolves the problem, please contact Itasca.

It will be helpful to provide a screenshot of the key error message you receive when starting the code, if possible. Be sure to provide the name and version of the Itasca software you are running, the operating system you are using, and the exact text of the error(s) or warning(s) that occur on startup.

NETWORK LICENSE

Set-up License

ON THE SERVER

Unplug all USB keys from the server.
Download the latest security drivers and server software HERE and install it. Make certain the installation is successfully completed and Sentinel Protection Installer 7.7.1 appears in Settings/Apps/Apps & Features. Reboot the machine, if offered.
Plug the keys back into the server. Make certain the key light comes on and does not go off.

ON THE CLIENT MACHINE

Install Itasca software and specify license server location in the settings:

CHECK COMMUNICATION PORTS

First, check which license key you have:

RED Sentinel SuperPro network USB key
GREEN Sentinel HL network USB key

Make certain that communication is possible between the client computer and the server on ports 6001, 6002 (for RED keys) and additionally port 1947 (for GREEN keys). A firewall or other network security system blocking traffic on any of these ports is the most common cause of trouble connecting to a network server.

ON THE SERVER

Make sure the Sentinel Protection Server, Sentinel Keys Server, and Sentinel LDK License Manager services are running in the services app. If either is not running, re-install the security drivers from the link above making sure they are installed with administrative rights and installation proceeds to the end. If there are troubles during installation, see step 4 below.
Launch a browser and navigate to Sentinel License Monitor at http://localhost:6002 for RED keys or Sentinel Admin Control Center at http://localhost:1947 for GREEN keys (you may have to allow JavaScript, if asked). You should see the keys present (although they will not be identified as anything other than SuperPro or Sentinel HL Max keys).
Install ICGTools from https://www.itascacg.com/software/downloads/icgtools. Launch the “LicenseLocation” application. Set the location to Server with the server name “localhost”. Scan for keys. Make certain it can see the network key(s). This will confirm that Itasca tools can see network keys locally on the server.
If any problems persist, uninstall *all* drivers from the server and then use the SSDCleanup utility HERE to fully clean up the system from Sentinel drivers. Then reboot and reinstall the latest drivers as mentioned above.

ON THE CLIENT MACHINE

From the client machine, attempt to connect to the server on a web browser, using http://serverIP:6002 or http://serverIP:1947. If you cannot connect, then either ports 6001, 6002, or 1947 has been blocked or the network driver has not been properly installed on the server. If it doesn’t list a key, then the server computer is probably not seeing the key locally either (troubleshoot the server). If someone else has checked out the license, the network monitor should notify you of that and give you the IP address of the person who has checked the license out.

There are a range of problems that may arise related to the user’s key (also sometimes referred to as the USB key, hardware lock, hardlock, or dongle) that secures Itasca software. The steps below, which move from least to most severe, are actions the end-user can take prior to contacting Itasca for technical support in the event that there is a key-related problem at program startup. For complete information about troubleshooting the Thales USB key, please download Thales End User Troubleshooting Guide and visit their website.

STANDARD (DESKTOP) LICENSE

1) Cycle the key through the other USB ports.

Often, a key problem can come from a conflict or corruption in the settings that match up the key, the key driver, and the specific USB port in use (all three components are in play to make any USB device work). This situation most commonly occurs when the key provided for use with the Itasca software gets plugged in before the software is installed, causing Windows to automatically assign an incorrect driver to that port/key pair.

To perform this step, remove the key and put it into a different USB port. If the step works, popup notifications like the ones below will appear in the lower right corner of the screen (the exact pop-ups and text will vary depending on the Windows operating system in use).

followed by

If this occurs, try the software again. At this juncture, it should work. Also, the key should be able to be put back in the original USB port and work correctly. If this doesn’t happen on the first new USB port you try, continue working through all the available USB ports on a machine before moving on to the next step.

2) Download and install the latest drivers for the key from the Thales website.

It is recommended that the security key be removed before running the driver installation.

This step is quite safe; the SafeNet installation will not overwrite a newer driver with an older one. Updating to a newer driver through a clean installation can clear up the problems stemming from cases of conflict, corruption, or other issues related to the presence of earlier Sentinel USB key drivers.

3) Download and run the the “SSD CleanUp” utility from Thales and retry installation.

The “SSD Cleanup” utility is provided on the same page of the Thales website as the latest driver download. Note there are two versions available, one for 32-bit and one for 64-0bit Windows. The user must select the appropriate version. These are listed last on the “Windows Drivers & Utilities” table.

This utility removes all traces of the current and any past Sentinel key driver installations. To use, we recommend the following steps:

Uninstall the Itasca software.
Remove the USB key from the computer.
Run SSD Cleanup.
Reboot the computer.
Run the downloaded driver installation from Step 2 above.
Re-install the Itasca software.
Plug in the USB key.
Run the software.

During this sequence, be sure to follow any instructions to reboot the computer as they appear.

What Next?

If none of the steps described on this page resolves the problem, please contact Itasca.

It will be helpful to provide a screenshot of the key error message you receive when starting the code, if possible. Be sure to provide the name and version of the Itasca software you are running, the operating system you are using, and the exact text of the error(s) or warning(s) that occur on startup.

ON THE SERVER

Unplug all USB keys from the server.
Download the latest security drivers and server software HERE and install it. Make certain the installation is successfully completed and Sentinel Protection Installer 7.7.1 appears in Settings/Apps/Apps & Features. Reboot the machine, if offered.
Plug the keys back into the server. Make certain the key light comes on and does not go off.

ON THE CLIENT MACHINE

Install Itasca software and specify license server location in the settings:

CHECK COMMUNICATION PORTS

First, check which license key you have:

RED Sentinel SuperPro network USB key
GREEN Sentinel HL network USB key

Make certain that communication is possible between the client computer and the server on ports 6001, 6002 (for RED keys) and additionally port 1947 (for GREEN keys). A firewall or other network security system blocking traffic on any of these ports is the most common cause of trouble connecting to a network server.

ON THE SERVER

Make sure the Sentinel Protection Server, Sentinel Keys Server, and Sentinel LDK License Manager services are running in the services app. If either is not running, re-install the security drivers from the link above making sure they are installed with administrative rights and installation proceeds to the end. If there are troubles during installation, see step 4 below.
Launch a browser and navigate to Sentinel License Monitor at http://localhost:6002 for RED keys or Sentinel Admin Control Center at http://localhost:1947 for GREEN keys (you may have to allow JavaScript, if asked). You should see the keys present (although they will not be identified as anything other than SuperPro or Sentinel HL Max keys).
Install ICGTools from https://www.itascacg.com/software/downloads/icgtools. Launch the “LicenseLocation” application. Set the location to Server with the server name “localhost”. Scan for keys. Make certain it can see the network key(s). This will confirm that Itasca tools can see network keys locally on the server.
If any problems persist, uninstall *all* drivers from the server and then use the SSDCleanup utility HERE to fully clean up the system from Sentinel drivers. Then reboot and reinstall the latest drivers as mentioned above.

ON THE CLIENT MACHINE

From the client machine, attempt to connect to the server on a web browser, using http://serverIP:6002 or http://serverIP:1947. If you cannot connect, then either ports 6001, 6002, or 1947 has been blocked or the network driver has not been properly installed on the server. If it doesn’t list a key, then the server computer is probably not seeing the key locally either (troubleshoot the server). If someone else has checked out the license, the network monitor should notify you of that and give you the IP address of the person who has checked the license out.

Standard Single License

All software products released after June 1, 2008 allows up to two instances of the software to cycle on a single computer”

Web License

A Web license allows two instances of the software, per seat, to cycle on any computer connected to the network for version 7 or above of FLAC3D, 3DEC or PFC. Two instances can also be run with FLAC2D version 9 or above. 3DEC 5.2, FLAC 8 and 8.1, and Griddle 2 can run one instance of the software per seat. Older versions of the software do not support web licenses.

Network License

A Network license allows two instances of the software, per seat, to cycle on any computer connected to the network for version 7 or above of FLAC3D, 3DEC or PFC. Two instances can also be run with FLAC2D version 9 or above. Older versions of FLAC3D, 3DEC or PFC and all versions of Griddle, FLAC and UDEC can run one instance of the software per seat.

Your software serial number can be found in the letter included with your software shipment. It is also included on the tag attached to your blue (standard) or red (network) USB hardlock key.

You can also find your serial number using your software, provided your USB hardlock key is installed on your computer or network as follows.

For UDEC

Click the Console tab beneath the File menu item.

Option 1: You will see the serial number displayed on the third line in the Console.

Option 2: At any time you can type “Print Security” in the command line at the bottom of the Console and hit the “Enter” key.

For FLAC

Click the Console tab beneath the File menu item.

Option 1: You will see the serial number displayed on the second line in the Console.

Option 2: You can also see the serial number displayed in the black Command Prompt display.

For 3DEC , FLAC3D, FLAC2D or PFC

Click the Command line beneath the Console pane. Type “LIST Security” and hit the “Enter” key.

For XSite

Click the About XSite tab beneath the Help menu item.

A window will pop-up indicating your license serial number as shown below.

Software Title	Publish Date
3DEC	Version 9.0 released Jan 2024 Version 7.0 released Sept 2020 Version 5.2 released Nov 2016 Version 5.0 released Aug 2013 Version 4.1 released Dec 2007 Version 3.0 released Mar 2003 Version 2.0 released Dec 1998 Version 1.5 released Mar 1994 Version 1.3 released — 1991 Version 1.2 released — 1990 Version 1.1 released — 1989 Version 1.0 released — 1988
FLAC (FLAC/Slope)	Version 8.1 released Oct, 2019 Version 8.0 released Mar, 2016 Version 7.0 released Oct, 2011 Version 6.0 released Aug 2008 Version 5.0 released Apr 2005 Version 4.0 released Sep 2000 Version 3.4 released Sep 1998 Version 3.3 released Apr 1995 Version 3.2 released Nov 1992 Version 3.0 released Sep 1991 Version 2.2 released Jun 1989 Version 2.1 released Nov 1988 Version 2.0 released Mar 1987 Version 1.0 released Feb 1986
FLAC2D	Version 9.0 released April 2023
FLAC3D	Version 9.0 released April 2023 Version 7.0 released July 2019 Version 6.0 released Apr 2017 Version 5.0 released Nov 2012 Version 4.0 released Dec 2009 Version 3.1 released Dec 2006 Version 3.0 released Oct 2005 Version 2.1 released Mar 2002 Version 2.0 released May 1997 Version 1.1 released Jan 1996 Version 1.0 released Aug 1994
Griddle	Version 3.0 released July 2025 Version 2.0 released Dec 2020 Version 1.0 released Sep 2016
PFC2D	Version 9.0 release Oct 2024 Version 7.0 released July 2021 Version 6.0 released Dec 2018 Version 5.0 released April 2014 Version 4.0 released Dec 2008 Version 3.1 released Nov 2004 Version 3.0 released Nov 2002 Version 2.0 released Jun 1999 Version 1.1 released Mar 1995 Version 1.0 released Dec 1994
PFC3D	Version 9.0 release Oct 2024 Version 7.0 released July 2021 Version 6.0 released Dec 2018 Version 5.0 released April 2014 Version 4.0 released Oct 2008 Version 3.1 released Aug 2005 Version 3.0 released Jun 2003 Version 2.0 released Nov 1999 Version 1.1 released Nov 1995
UDEC	Version 7.0 released July 2019 Version 6.0 released Feb 2014 Version 5.0 released May 2011 Version 4.0 released Oct 2004 Version 3.1 released Dec 1999 Version 3.0 released Oct 1996 Version 2.0 released Nov 1993 Version 1.8 released Jun 1992 Version 1.7 released May 1991 Version 1.6 released — 1990 Version 1.5 released — 1989 Version 1.4 released — 1988 Version 1.3 released — 1987 Version 1.2 released — 1986 Version 1.1 released — 1985
XSite	Version 4.0 released May 2024 Version 3.0 released Aug 2019 Version 2.0 released Aug 2018

Yes. ITASCA software is designed to be highly flexible and can be coupled with other numerical models and external software in several ways. Coupling can be achieved through both native integrations within the ITASCA ecosystem and open, script-based interfaces such as FISH and Python.

Native ITASCA Coupling

ITASCA provides built-in, tightly integrated couplings between several of its core products, allowing efficient multi-physics and multi-method simulations:

FLAC / FLAC3D ↔ PFC
Enables continuum–discrete coupling, where deformable continua (FLAC/FLAC3D) interact directly with granular or fractured media represented by discrete elements (PFC).
FLAC / FLAC3D ↔ MPM (MPoint)
Supports coupling between continuum zones and material point representations, allowing large-deformation or transition-to-flow behavior to be modeled seamlessly.

These native couplings are optimized for performance, stability, and data exchange, with shared solution cycles and synchronized time stepping.

Coupling via FISH

All ITASCA codes include FISH, a powerful embedded scripting language that allows users to:

Exchange data between ITASCA codes during a simulation
Control solution logic, loading sequences, and coupling workflows
Implement custom constitutive behavior or interaction laws

FISH-based coupling is commonly used to link simulations at runtime or to implement loose or semi-tight coupling strategies between different models.

Coupling via Python

For advanced workflows or integration with third-party tools, ITASCA software supports Python-based coupling, enabling:

Communication with external solvers and analysis tools
Automation of multi-model or multi-scale simulations
Integration with data analytics, machine learning, or pre-/post-processing pipelines

Python coupling is especially useful when ITASCA simulations are part of a larger digital workflow or when linking to non-ITASCA codes.

Whether generated interactively or manually, the basic description of most Itasca models is a data file. A data file is a standard text file containing commands that completely specify a model, from model creation to additional sequential operations required to undertake physical simulations.

At first exposure, the fact that Itasca software uses data files to describe the model may seem antiquated, perhaps a relic of 1970’s program design. To the contrary, this form of model description has proven to be quite valuable. It is integral to the powerful modeling capability of Itasca sofware. As our user interface design matures, our goal is not to remove the command-driven interface but, instead, to simplify its use, making simulations easier to undertake while retaining the flexibility that this design enables.

Below are a few reasons that using a data file description is advantageous.

Compact Representation

Even the most complex models can be created by a set of data files that are generally not more than a few hundred lines in length. In fact, the vast majority of models are far smaller. This fact means that the complete description of your model resides in a text file that is only a few kilobytes in size. As a result, it is trivial to share your model with others, email it to Itasca for support, archive your model for future reference, and use versioning software to track changes.

Repeatability

Itasca works very hard to ensure that the same version of the code and the same data file will always produce the same result to machine precision. This means that when you send Itasca, your colleagues, or your clients a data file, you know that the result will be unchanging. Thus it is not necessary to archive the complete results of a modeling effort, which may be many gigabytes of save and result files. Instead, one can just retain the data file and the code version used to execute it.

History and Path Dependence

Except for the most trivial models using the simplest of materials, the path used to reach the solution is a very important part of the model description. A data file allows the sequence of events to be described clearly and flexibly. Many programs may offer excavation sequence options, but the data file allows any sequence of events to be made as needed. This includes changes to boundary conditions, changes to material properties, changes to fluid interactions, etc., as well as changes to the excavation sequencing. If one were to design a graphical user interface to include the entire list of options available via a data file, the result would be complex, requiring clumsy tools to edit and change.

Flexibility

The data file allows the user maximum flexibility in model creation and processing, including the order in which things are specified. While there is a standard sequence of simulation steps recommended for simple models (e.g., geometry creation, naming of regions, material and property specification, boundary conditions, initial conditions, solving, excavating, solving, etc.), every model is different. Often complex models require modifications to the standard simulation progression. Itasca is committed to the idea of not constraining users to a small set of simulation options, providing users with the ability and tools to undertake physical simulations in the way they see fit.

Scripting

The ability to combine model-creation commands with scripting in Itasca software is tremendously powerful. For instance, an entire class of models can be investigated by trivially changing a set of initial parameters within a data file. Application of complex sequences, geometries, property distributions, etc. may be automated with a script in a way that would be very time consuming and difficult to replicate in a traditional graphical user interface. In addition, in-depth model querying and the inclusion of new physical phenomena, not built into the software, can be introduced via user-created scripts that execute during cycling.

One downside to such a command-driven interface is that it can seem imposing to new users, who may have the impression that mastery of a large number of complex commands is necessary to undertake the simplest of modeling efforts. In truth, the learning curve is faster than being confronted by a complex graphical user interface that has numerous tools with a plethora of buttons in different panes—something we have all experienced. The commands have been purposefully structured using descriptive and consistent terminology, making it easy to read a data file and understand the operations it invokes. Interactive command documentation is available as you create and edit a data file, and an inline command construction utility is also available. Both simplify the model construction process substantially.

On high resolution (e.g., 4K) displays, issues may occur, such as small and offset plot items within plot windows, or the text editor occupying only a fraction of the Edit pane.

If you are experiencing these or similar issues when using version 6 (or higher) of 3DEC, FLAC2D, FLAC3D, PFC2D, PFC3D, or UDEC on Windows 10, the following is recommended to automatically scale these applications via the operating system:

1. Before starting your Itasca application, right-click on the application-GUI executable and select the Properties menu item. The installation default location (typical in most cases) is the C:\Program Files\Itasca\Itasca Program\exe64 folder.
2. Select the Compatibility tab and click on the Change high DPI settings button.

3. Enable the High DPI scaling override checkbox and select the System option.

4. Click the OK button.
5. Click the Apply button and then finally the OK button.
6. Start your Itasca application.

Now that your Itasca application DPI settings are controlled by Windows you do not have to repeat this process should you modify your display resolution. This process must be repeated for each affected Itasca application.

Please note that older versions of Windows 10 may display the compatibility tab as follows, skipping a step.

When no USB security key/dongle is present, users have the option to continue using Itasca software in “Demonstration Mode”. This mode includes all options and does not expire. The size of model that you can solve/cycle is however limited and other restrictions may apply as indicated below for the current software version.

REQUEST DEMO DOWNLOAD

Title	Limitation
3DEC	Maximum of 50 blocks and 1,000 zones.
FLAC2D	Maximum of 1,000 zones.
FLAC3D	Maximum of 1,000 zones and 100 structural elements.
FLAC/Slope	Now freeware. Fully functional, perpetual license. Free technical support is no longer provided but paid technical support is available.
MassFlow	Maximum block model size of 10,000 blocks.
Griddle	Griddle is a mesh generation plug-in for Rhinoceros 3D CAD (version 6 or 7). A full version of Rhino trial software is available to download from Robert McNeel & Associates. Saving and plug-ins will stop working after 90 days without purchase. In demonstration mode, the following limitations are in effect for Griddle: BlockRanger Saves output volume mesh in VRML format only GInt Functionality to keep meshes separate (OutputMesh=Separate) is not available (all meshes will be merged in the output) SplitIntersections option is not available GSurf Number of elements in the output mesh is limited to 5,000 Functionality to keep meshes separate (OutputMesh=Separate) is not available (all meshes will be merged in the output) GVol Number of elements in the output mesh is limited to 10,000 GHeal Automatic mesh repair, AutomaticHeal, is not available GExtract Only separation of a single surface (SingleSurface) is available in demonstration mode
MINEDW	This demo version can open any size model for viewing. It can only run and save models with less than 10,000 elements.
PFC	The PFC demo includes both PFC2D and PFC3D programs. The demo permits the cycling of a maximum of 1,000 balls or 1,000 clumps (not exceeding a total of 1,000 balls), up to 1,000 rigid blocks, and up to 10 discrete fractures.
UDEC	The PFC demo includes Maximum of 200 rigid blocks or 150 deformable blocks or 560 kB of memory.
XSite	Maximum of 100,000 nodes. A demonstration mode water mark will also appear across the plot window.

Yes, you can run the following Itasca software in the cloud with a web license.

3DEC 7.0 or above
FLAC3D 7.0 or above
PFC 7.0 or above
FLAC 8.0 or above
FLAC2D 9.0 or above

The software has been tested on both AWS and Azure. For a tutorial on getting started with AWS, see this link. A similar tutorial for Azure will follow soon.

In ITASCA software, the zone maximum shear strain increment (SSI) plot-item is defined by (ε₃-ε₁), where SSI is the square root of the second invariant of the strain increment deviator. All definitions are listed below. LEARN MORE

Stress/Strain Invariants

In ITASCA software, assuming S_ij is the deviatoric part of the stress tensor σ_ij, and e_ij is the deviatoric part of the strain tensor ε_ij, the stress/strain invariants in ITASCA software are defined and summarized below.

For example, in a triaxial compression test, the cell pressure in the xy-plane is 100, the vertical compression pressure in the z-direction is 400, the stress tensor in the sample is thus

According to equations below, we have

Itasca Software
Frequently Asked Questions

General Product & Licensing