Adams Basic Package > Adams View > Adams View > Dialog box - F1 help > P - Z > Solver Settings - Executable

Solver Settings - Executable

Settings → Solver → Executable
Sets the type of Adams Solver to run.
 
For the option:
Do the following:
Category
Set to Executable.
Executable
Select:
■Internal - Run Adams Solver from within Adams View and animate the results as they are calculated, which is the default
■External - Perform a Simulation with Adams Solver while in Adams View, but without seeing the model update on your screen during the simulation. Adams View automatically plays an animation of the simulation when the simulation is complete.
■Write Files Only - Instruct Adams View to write out the files that are needed to run a simulation using Adams Solver from outside of Adams View. The files include the:
■Command (.acf) file, which contains the commands necessary to run the desired simulation.
If you select Internal, you can perform either an Interactive Simulation or a Scripted simulation. If you select External or Write Files Only, you can only perform a scripted simulation. Adams View issues an error if you try to perform an interactive simulation after choosing either of these options.
If you selected Internal or External, you can set the following options:
Solver Library
Set it to use the standard Adams Solver executable (leave it blank) or a user-defined or customized Adams Solver library. A customized Adams Solver library is required if you used subroutines to define any objects in your model, such as motions or forces. For more information, see the following:
Note: On Linux, you can use the Adams Toolbar to set the Adams Solver library to run and create different tools on the Adams Toolbar for each library you have.
Choice
Select either:
■FORTRAN - Our existing version of Adams Solver.
■C++ - Our new, C++-based version of Adams Solver, which promises to be faster, provide new linear analysis capabilities, and have an improved methodologies. For a detailed comparison, see section Adams Solver C++ vs. FORTRAN.
As you create modeling objects in Adams View, it lets you know whether or not they are compatible with the C++ version or the FORTRAN. If you use the Adams Solver C++, please provide us with feedback through the Adams Feedback Database at http://simcompanion.mscsoftware.com/KB8019304. Be sure to select the product Adams Solver (C++). For more information on the different solvers, see Release Notes and Adams Solver (C++) help.
Verify First
Set to yes to verify your model before running a simulation. See Model Verify Tool dialog box help.
Hold License
Set whether or not the Adams Solver license is checked back in once the simulation is complete. By default, Adams View does not check the license back in for another user. You must exit Adams View before other users can use the Adams Solver license.
■If you set Hold License to Yes, then Adams View checks out the necessary licenses when you perform a model verify operation (because of the degrees of freedom calculation, which uses Adams Solver) or any type of simulation using the internal Adams Solver. It only releases the licenses when you exit Adams View or when you run a simulation using the external Adams Solver.
■If you set Hold License to No, Adams View releases all Adams Solver licenses (static, kinematic, and dynamic) in these cases:
♦You run a simulation using the external Adams Solver (as before).
♦After a model verify operation.
♦When you reset after a single simulation using the internal Adams Solver.
♦After a parametric analysis (licenses are held throughout the parametric analysis)
More
Select to display options for setting the remote computer on which to run Adams Solver.
Remote Compute
■Linux only; not displayed when running on Windows
■Enter the name of the remote host where you run Adams Solver or leave blank to use local machine. The option you select depends on where the Adams Solver is licensed at your site.
Note: Network access and multi-task package licenses allow you to submit tasks to Adams Solver while Adams View runs on one of many desktop workstations. To see if you can submit multiple tasks to Adams Solver, check the licensing information on the password certificate that is included in the Installer’s Kit. If you do not know the type of license you have, check with the administrator who installed the Adams.
If you set Remote Compute to Yes, the following options are available:
Node Name
Enter the node ID of the remote computer.
MDI Directory
Enter the name of the Adams Solver installation directory on the remote machine.
Remote Directory
Specify a directory that Adams Solver uses to write out its files and search for input files. The directory is optional. You need to specify it only if the user’s file system is not automounted on the remote machine upon log in.
The following options are available for Adams Solver (C++) only
Thread Count
Adams Solver (C++)
Specify the number of parallel threads that Adams Solver (C++) uses when performing the simulation. The number of threads, n, must be an integer in the range of 1 to 128. The default value is 1. This value will be applied even if the field is left blank. Also, this field will not reset to its default value of 1 when one clicks the Defaults button. By executing multiple threads in parallel across multiple processors, Adams Solver (C++) can reduce the walltime required for a simulation.
Typically, the optimal number of threads is between N and 2N, where N is the number of processors (including virtual processors in the case of Pentium processors with HyperThreading enabled, refer below note for more information).
Note: The Intel® Pentium® 4 processor introduced a feature called Hyper Threading, where a single physical processor can support more than one logical instruction stream, simulating multiple logical processors on a single physical processor. For many applications and environments, this capability may offer performance improvements over non-Hyper Threading processors. If multiple analysis jobs are running concurrently, however, there may be performance degradations. If an installation determines this to be the case, hyper threading should be disabled. This can be done on a permanent basis through BIOS operations or, for Windows platforms, hyper threading may be disabled on a process by process basis using the “hyperthreads” keyword.