1.1. Install on Windows 10

1.1.3. Download the Application

To download the quoFEM app, navigate to the quoFEM Download page which should resemble Fig. 1.2.4.5. The download page contains a list of downloadable files and directories.

../../../../_images/quoFEMDownload.png

Fig. 1.1.3.5 quoFEM download page.

Click on the file with a name ending with Windows_Download.zip to download the quoFEM app. In the pop-up window, click on the Download button in the bottom right corner.

After the download is completed, extract the zip archive to a location in your filesystem. We suggest extracting it to the C:/SimCenter/ folder. You can create a shortcut that points to the quoFEM.exe executable of the application and move this shortcut to your Desktop for easy access.

Tip

Using an external compressor program, such as 7-Zip, can significantly reduce the zip archive extraction time compared to the Windows default extraction function.

1.1.4. Test the Installation

Once the installation procedure has been completed, it is a good practice to run some basic checks. Navigate to the location where you placed the application and open it by running the quoFEM.exe executable.

Note

Since the SimCenter is not registered as a Windows vendor, our apps are not recognized by the operating system as signed applications. You may receive a warning message that lets you know about the risks involved in running unsigned applications from unknown sources when you start the quoFEM app application for the first time. It is safe to bypass that warning when running SimCenter applications.

Once the application starts, you should see the user interface shown in Fig. 1.1.4.5. We recommend running the example problem Two-Dimensional Truss: Sampling, Reliability and Sensitivity to test the application.

../../../../_images/quoFEM1.png

Fig. 1.1.4.5 quoFEM application on startup.

1.1.5. Troubleshooting

If the analysis fails, please see the troubleshooting page.

Note

When analysis fails, a quick check is to inspect the local working directory path in the preference menu. The below could lead to the analysis failure

  • The path is located under a cloud folder, e.g. OneDriver, Box (may give file-not-found error due to the real-time cloud-only sync)

  • The path contains non-alphabetic characters (may give an encoding error)

  • The path contains empty space (low likelihood, but it may give the file-not-found error)

  • The path is located under a different driver from the app executable (.exe) path, e.g. one is under C drive, and the other is under E drive (may give a permission error)