A comprehensive and full-featured computational physics suite for boundary-element analysis of electromagnetic scattering, fluctuation-induced phenomena (Casimir forces and radiative heat transfer), nanophotonics, RF device engineering, electrostatics, and more. Includes a core library with C++ and python APIs as well as many command-line applications.
Description:
I am using scuff-static from the SCUFF-EM package to calculate the polarizability of a given geometry. However, I am experiencing discrepancies in the .pol file outputs generated on two different machines, despite identical SCUFF-EM installations, geometry files, and computational setups. The calculated polarizability values differ significantly between the two machines.
So, I’m seeking guidance on whether the differences in polarizability results could be due to hardware-specific floating-point behavior or optimization settings. Any suggestions for further debugging steps would be appreciated.
System Information:
Old Computer:
- Processor: Intel Xeon E3-1240 v5 @ 3.50GHz
- OS: Ubuntu 22.04 LTS
- SCUFF-EM Version: Latest from GitHub (cloned Sept 20, 2024)
- GCC Version: 11.4.0
- Parallelization: Disabled (also tested with it enabled)
New Computer:
- Processor: Intel Xeon w9-3475X @ 4.40GHz
- OS: Ubuntu 22.04 LTS
- SCUFF-EM Version: Latest from GitHub (cloned Sept 29, 2024)
- GCC Version: 11.4.0
- Parallelization: Disabled (also tested with it enabled)
Steps Taken:
Polarizability Calculation Setup:
- Used identical geometry files (.scuffgeo) and mesh files (.msh) on both machines.
- Executed scuff-static with identical parameters to calculate polarizability and generate .pol files.
Identical SCUFF-EM Installations:
- Verified that both machines have the same scuff-static binary (MD5 checksum matches).
- Checked the linked libraries with ldd and confirmed they are the same on both machines.
Floating-Point Precision:
- Tried forcing both single and double precision using the -ffloat-store flag, but the discrepancies persisted.
Parallelization:
- Disabled OpenMP and rebuilt SCUFF-EM on both machines, but the issue remained.
HDF5:
- Built SCUFF-EM without HDF5 support (--without-hdf5) on both machines due to missing hdf5.h.
Processor Differences:
- Suspect hardware-specific floating-point behavior or CPU optimizations could be influencing the results, as the two machines have different processors.
Description: I am using
scuff-staticfrom the SCUFF-EM package to calculate the polarizability of a given geometry. However, I am experiencing discrepancies in the.polfile outputs generated on two different machines, despite identical SCUFF-EM installations, geometry files, and computational setups. The calculated polarizability values differ significantly between the two machines. So, I’m seeking guidance on whether the differences in polarizability results could be due to hardware-specific floating-point behavior or optimization settings. Any suggestions for further debugging steps would be appreciated.System Information:
Old Computer: - Processor: Intel Xeon E3-1240 v5 @ 3.50GHz - OS: Ubuntu 22.04 LTS - SCUFF-EM Version: Latest from GitHub (cloned Sept 20, 2024) - GCC Version: 11.4.0 - Parallelization: Disabled (also tested with it enabled)
New Computer: - Processor: Intel Xeon w9-3475X @ 4.40GHz - OS: Ubuntu 22.04 LTS - SCUFF-EM Version: Latest from GitHub (cloned Sept 29, 2024) - GCC Version: 11.4.0 - Parallelization: Disabled (also tested with it enabled)
Steps Taken:
Polarizability Calculation Setup: - Used identical geometry files (
.scuffgeo) and mesh files (.msh) on both machines. - Executedscuff-staticwith identical parameters to calculate polarizability and generate.polfiles.Identical SCUFF-EM Installations: - Verified that both machines have the same
scuff-staticbinary (MD5 checksum matches). - Checked the linked libraries withlddand confirmed they are the same on both machines.Floating-Point Precision: - Tried forcing both single and double precision using the
-ffloat-storeflag, but the discrepancies persisted.Parallelization: - Disabled
OpenMPand rebuilt SCUFF-EM on both machines, but the issue remained.HDF5: - Built SCUFF-EM without HDF5 support (
--without-hdf5) on both machines due to missinghdf5.h.Processor Differences: - Suspect hardware-specific floating-point behavior or CPU optimizations could be influencing the results, as the two machines have different processors.
Polarizability Output Example: -Old Computer (
.polfile):1 1.890611e+05 -1.725563e+03 -1.659733e+03 -3.674112e+03 7.411941e+04 5.667919e+03 2.177547e+03 7.735191e+03 5.733074e+04
-New Computer (
.polfile):1 2.037505e+05 -9.477865e+03 1.499895e+03 -3.625262e+03 7.411565e+04 5.433866e+03 2.154151e+03 7.835898e+03 5.710962e+04