MuMax
Overlapping Regions
Say we have the default region 0, some region 1, and some region 2 that is within region 1. If we set Ku1 = 1e4, then do Ku1.SetRegion(1, 1e5), then region 2 will take 1e4. If, on the other hand, we do Ku1.SetRegion(0, 1e4) and `Ku1.SetRegion(1e5), then region 2 will take 0. To get region 2 to match with region 1, we have to separately call Ku1.SetRegion(1, 1e5) and Ku1.SetRegion(2, 1e5).
MuMax Movie from Snapshots
ffmpeg -framerate 25 -i Data/m%06d.png -r 25 -pix_fmt yuv420p mag.mp4
Adding a New Energy Term
- In the
cuda/directory, add the required.cufile - Run
maketo generate the wrapper and.ptxfiles (may need to specify some options if it does not work for some compute capabilities, see the comments incuda/Makefile) - Add the corresponding
.gofiles, which calls the function defined in the automatically generated wrapper file (if this is not clear, look at existing examples, e.g. withcuda/exchange.go) - Add a file in the
engine/directory (typically this is not necessary, butengine/exchange.goshould be modified accordingly) - Add the new field to the effective field in
engine/effectivefield.go(assuming it wasn't just a simple modification of e.g. the exchange field). cdtocmd/mumax3and rungo install. The binary will be in$GOPATH/bin
Energy in Output Table is Zero
Probably forgot to set the saturation magnetization Msat.