MAG_sl: X-ray resonant specular reflection from magnetic multilayers
Introduction Program Guide Conditions of use Access to MAG_sl Retrieve results Automation/fitting

Introduction

Fig.1 This page is a CGI interface to my program MAG_sl simulating x-ray resonant specular reflection from magnetic multilayers with the account for interface roughness or transition layers. In order to use this program please read first the paper by S.Stepanov and S.Sinha "X-ray resonant reflection from magnetic multilayers: Recursion matrix algorithm", Phys. Rev. B, v.61, No 22, p.15302-15311, (2000) on which it is based. In short, there is a resonant increase at the absorption edges of some rare-earth and transition elements in the electric multipole (e.g. quadrupole) part of x-ray scattering amplitude. In this case the scattering amplitude becomes a tensor with the orientation dependent on the orientation of the magnetic moment of respective atom. The x-ray scattering caused by those additional contributions is called "resonant magnetic scattering", although it is electric by nature. When all the magnetic moments are oriented in the same direction, one can probe the magnetization of the media (e.g. thin magnetic film or magnetic multilayer) with x-rays -- see Fig.1. The effect on x-ray scattering is the strongest when the magnetic field is applied along the direction of x-ray incidence (X-axis) and the incident x-rays are circularly polarized. In the other cases the effect may still exist but be less measurable. Again, please find more details in the paper and references therein.

The MAG_sl software makes use of the same recursive matrix algorithm (RMA) as other programs on this site: GID_sl, TER_sl, and TRDS_sl. Besides, all of these programs implement very similar input. Therefore, before learning MAG_sl it might be helpful to practice with a simpler software like TER_sl that simulates x-ray specular reflectivity from multilayers with no account for magnetic resonance effects.



Program Guide

This short guide provides some explanations on the MAG_sl data input and outlines the restrictions of this Web interface.

The MAG_sl program is executed on my office PC, that runs a Web server under Windows operating system. Since this PC is shared by all of the WEB users of my x-ray library, please, avoid overloading the server by running multiple tasks at the same time.

To obtain the results from MAG_sl you need to fill out the input form and click on the SUBMIT button. If your input is correct, the results will be presented as a figure and a link to respective downloadable ZIP file that contains all the data. Otherwise, a web page with respective error message will be returned.

In case the calculation succeeds, the downloadable ZIP file will contain the following ASCII files with the results of calculations:

The specification of substrate, x-rays, and scan parameters is pretty straightforward and perhaps does not require any comments.

The specification of surface layer profile is implemented with a simple script language. A typical syntax is:

; comments are allowed in any line, but should not contain special symbols like '"*?$!@%
period=15
 t=10 code=GaAs w0=0.8 sigma=2
 t=10 code=GaAs x=0.3 code2=AlAs x2=0.7 sigma=2
 t=10 code=SiGe rho=0.9 sigma=2
 t=10 x0=(5e-4,7e-6) tr=5
 t=10 w0=.5 tr=4
 t=10 w0=0.5
 t=10
;
 code=Fe t=35
 code=Gd t=50 F11=(-0.22,9.35) F1T=(0.37,9.65) mshare=1 mvector=(1 0 0)
 code=Gd t=50 F11=(-0.22,9.35) F1T=(0.37,9.65) mdensity=2.5 mvector=(1 0 0)
end period

Here:

Below is a practical example -- a profile for 15-period Gd/Fe multilayer with 50 Angstroms of resonantly reflecting Gd and 35 Angstroms of non-resonant Fe in each period. The magnetic momenta of all Gd atoms are assumed to be aligned along the direction of incident beam (x-axis):

period=15
 code=Gd t=50 F11=(-0.22,9.35) F1T=(0.37,9.65) mshare=1 mvector=(1 0 0)
 code=Fe t=35
end period

For the rest of parameters you are suggested to follow the common sense. To ensure that your input was correct, please verify respective listing file -- a file with the ".TBL" extension in the ZIPped archive referred from the MAG_sl results screen.



Access to MAG_sl

To simplify understanding the MAG_sl you can start with several templates listed below. They correspond to Figures 3 to 5 of the paper respectively. All the templates link to the same program and provide the same functionality. They differ by preloaded data to demonstrate some possible applications of MAG_sl.
Besides, when submitting the MAG_sl task, it is possible to check the progress watching option. The progress watching is obviously more comfortable, but it might not work with some old Web browsers. Also, it is a bit slower because of putting an additional load on the network and launching each 5 seconds a monitoring program on my computer. Welcome to try both of the ways and choose the most convenient for your needs.

 New of December-2012: POST-Method Templates

  1. Data corresponding to Fig.3 of the paper
     
  2. Data corresponding to Fig.4 of the paper
     
  3. Data corresponding to Fig.5 of the paper
     

GET-Method Templates
This is an older, but better tested method. Generally it works very well except for
known problems with the IE browser & some firewalls when the structure description
exceeds 2K bytes (with some firewalls the restriction may be even 1K bytes).

  1. Data corresponding to Fig.3 of the paper
     
  2. Data corresponding to Fig.4 of the paper
     
  3. Data corresponding to Fig.5 of the paper
     



Retrieve results

Here is a tool to retrieve the results of finished jobs if you know the job ID. Some possible uses of this tool are:

  1. You started a job with the progress watch option; the server returned the job ID and began reporting the progress. However, you found that the calculations would take too long. Then, you may break the connection and retrieve the data later on with this tool. If the calculations are not finished, the tool will resume the watch process.
  2. The data are accidentally deleted from your client computer and you want another copy of them. In this case you should be aware that results are usually stored on the server for about one day after respective job is finished.
Job ID:



X
Site navigation: