Hello,
Sorry for the slow reply. (Here I will refer to the full magnetoelastic module as "the module", and mumax that has the effective magnetoelastic effective field as "regular mumax") There are a few different things to mention:
1:
As far as I can tell, minimize() and relax() were not updated for the module. I think you have to use run() in order to get the benefits of the module. This is unfortunate for hysteresis problems, since run() is so much slower than relax or minimize, although it can be done if you need to. However, if you just want a hysteresis loop, you might not need the module; I would expect the hysteresis behavior to be mostly the same if you just use the effective field term in normal mumax, if all you care about is the hysteresis behavior.
So when you call minimize/relax, it is reverting back to the purely magnetic solver, with the caveat that the effective term for the magnetoelastic term doesn't work, so there are kind of two problems. As part of the up date to the module, they did change the magnetoelastic energy term (which minimize/relax call upon), so it no longer depends on exx/eyy/ezz directly, but instead references normstrain and u (which doesn't get set properly for minimize/relax since they did not exist). So it both falls back to the old solver, and with a 0 magnetoelastic effective term. So if you want to use the effective field form, use a binary that is just regular mumax.
2:
That said, you can still set exx and it should work with run(). The syntax you used is correct for regular mumax. For the module, it should also work, as it's listed as a type of excitation in the paper, but I have not tested this very much myself. In my very limited testing, it doesn't seem to lead to the response in u (and normstrain) you would expect, so I would try to verify it is working as you expect. You might need to use FrozenDispVal and FrozenDisploc instead.
3:
You don't need to initialize du (i'm not sure if it hurts anything or if it's just cosmetic. Probably just cosmetic)
4:
If you want to set a cubic anisotropy, make sure you set Kc2 as well (kc3 gets computed automatically), as well as anisc1 and anisc2 for the directions. Kc1 by itself won't do anything.
5:
For the magnetoelastic module, you need to set a fixdt value, as it does not have adaptive timestepping built in. This can be fairly sensitive, especially as you make the mesh smaller. In the paper, they use a relatively large value of 1e-13, but you may need to shrink this down to 1e-14 or smaller. It depends on things like cell size, exchange strength etc. You want it as large as possible for speed, but care needs to be taken.
Best,
Josh L.