Skip to content

mumax 3.10β

Pre-release
Pre-release
Compare
Choose a tag to compare
@barnex barnex released this 29 Sep 08:30
· 145 commits to master since this release

You would need CUDA 10 and Nvidia driver 410.48 (Linux) and 411.31 (Windows) to run mumax3.10β.
Binaries for older CUDA versions are NOT RECOMMENDED and only provided for compatibility reasons (e.g. for supercomputers)

This version includes

  • Fixed sign in field-like Slonczewski torque (see issue #99 for the details)
  • Fixed boundary conditions in exchange field calculation (see pull request #115 for the details; thanks to Attila Kakay for reporting)
  • Support for Nvidia GPUs from Maxwell to Turing architectures; Fermi is now deprecated.
  • Relax() now supports user-defined threshold contributed by @jsampaio (see issue #146 and pull request #148 for the details).
  • mumax3-convert can now render arrows with scalar colorplots (see pull request #152 for the details)
  • Adaptive time step with finite temperature. Ref: http://doi.org/10.1063/1.5003957
  • User-defined field terms (for a detailed example see supplementary materials Ref. https://doi.org/10.1088/1361-6463/aa8601)
  • skyrmion / bubble position estimation and 2D moving window (see pull request #135)
  • Runge-Kutta 56 solver (see Ref: http://doi.org/10.1063/1.5003957)
  • Point-wise FixedLayer quantity.
  • mumax3 binary can now handle *.go input files directly.
  • 3D voronoi tessellation contributed by @peytondmurray
  • Creation of bibtex file (references.bib) in output directory with relevant references specific to your simulation.
  • mumax3-fft, a post-processing tool, has been moved to https://github.com/mumax/mumax3-fft
  • SnapshotAs(...) contributed by @kkingstoun
  • Vector fields, e.g., B_eff, can now be accessed in mx3 script via HostCopy() method.
  • mumax3-convert can now handle wildcards on Windows.
  • Option to use open boundary conditions instead of Neumann boundary conditions.

There is also plethora of fixes, including contributions from @joh, @syockit, @kkingstoun, @LLizardi, @kakutsmann, @ivlis and @jsampaio.

Finally, we would like to thank everybody who kindly shared mumax3 benchmark results with us.