Difference between revisions of "COMSOL"
Moskalenko (talk | contribs) |
|||
Line 5: | Line 5: | ||
<!--CONFIGURATION: OPTIONAL (|1}} means it's ON)--> | <!--CONFIGURATION: OPTIONAL (|1}} means it's ON)--> | ||
|{{#vardefine:conf|}} <!--CONFIGURATION--> | |{{#vardefine:conf|}} <!--CONFIGURATION--> | ||
− | |{{#vardefine:exe|}} <!--ADDITIONAL INFO--> | + | |{{#vardefine:exe|1}} <!--ADDITIONAL INFO--> |
|{{#vardefine:job|}} <!--JOB SCRIPTS--> | |{{#vardefine:job|}} <!--JOB SCRIPTS--> | ||
|{{#vardefine:policy|}} <!--POLICY--> | |{{#vardefine:policy|}} <!--POLICY--> | ||
Line 34: | Line 34: | ||
{{#if: {{#var: exe}}|==Additional Information== | {{#if: {{#var: exe}}|==Additional Information== | ||
− | + | If you are using COMSOL GUI to run your analyses make sure to specify the number of CPU cores in your gui session when starting COMSOL. Otherwise, COMSOL will attempt to use all physical cpu cores on the compute node, which will result in terrible performance. | |
+ | |||
+ | You can specify the number of available CPU cores in the job automatically using the SLURM_CPUS_ON_NODE environment variable, so the comsol startup command should be | ||
+ | comsol -np ${SLURM_CPUS_ON_NODE} | ||
|}} | |}} |
Revision as of 15:20, 18 October 2023
Description
COMSOL Multiphysics® is a general-purpose simulation software for modeling designs, devices, and processes in all fields of engineering, manufacturing, and scientific research. In addition to using multiphysics modeling for your own projects, you can also turn your models into simulation applications and digital twins for use by other design teams, manufacturing departments, test labs, customers, and more.
Environment Modules
Run module spider comsol
to find out what environment modules are available for this application.
System Variables
- HPC_COMSOL_DIR - installation directory
- HPC_COMSOL_BIN - executable directory
Additional Information
If you are using COMSOL GUI to run your analyses make sure to specify the number of CPU cores in your gui session when starting COMSOL. Otherwise, COMSOL will attempt to use all physical cpu cores on the compute node, which will result in terrible performance.
You can specify the number of available CPU cores in the job automatically using the SLURM_CPUS_ON_NODE environment variable, so the comsol startup command should be
comsol -np ${SLURM_CPUS_ON_NODE}