Unable to use phononic temperature

47 views
Skip to first unread message

Peela baradwaj naidu

unread,
Sep 20, 2024, 3:43:05 PM9/20/24
to Vampire Users
Hello VAMPIRE users, 
I am trying to simulate spin dynamics in CGT using two two-temperature laser pulse program, I want my spin system to be coupled with phononic temperature rather than electronic temperature, However, I get an error with material:couple-to-phononic-temperature=on.
I am attaching my log file. I would greatly appreciate any help.
Thank You.
cgt.ucf
material.mat
input
log

gabo...@gmail.com

unread,
Sep 20, 2024, 5:35:06 PM9/20/24
to Vampire Users
Based on the VAMPIRE 6.0 source code in match.cpp [1],  it looks like the "material[1]:couple-to-phononic-temperature = on" changed to "material:use-phonon-temperature".  Thus, you could try making that change in your material.mat file.


Kind Regards,
Gavin
VAMPIRE user

Peela baradwaj naidu

unread,
Sep 22, 2024, 3:15:03 PM9/22/24
to Vampire Users
Hello Gavin, 
Thank you for the reply, my simulation works much better now, However, I had a few more questions, regarding sim:laser-pulse-power and sim-two-temperature-electron-phonon-coupling, what are the units for these parameters and default values? I found this paper by Dr Evans here. Are the default values the same as the values for Ni reported here ?
Thank You.

gabo...@gmail.com

unread,
Sep 22, 2024, 4:32:06 PM9/22/24
to Vampire Users
sim:laser-pulse-power has units of mJ/cm^2 and default value should be 20.0. The mJ/cm^2 units were introduced in VAMPIRE 5.0 [1].

sim:two-temperature-electron-phonon-coupling units should be Wm^-3K^-1 and default value should be 6.6E17.

That Ni article does not use the default values.  For sim:two-temperature-electron-phonon-coupling, it used 12.0E17 for Ni.

The exact sim:laser-pulse-power doesn't appear to be given the article.  Thus, the exact value would have to be requested from the corresponding author of the article.

From slide 24 of [2], though, shows sim:laser-pulse-power with the unitless value of 1.2 for Ni that looks to be about what was used in the Ni article figure.

It looks like VAMPIRE 3.0.3 was released in 2016.  So, the Ni article published in 2015 could be expected to have used a VAMPIRE version prior to 3.0.3.

vampire_versions.png

Reply all
Reply to author
Forward
0 new messages