I have a question here: how are these two ini parameters related?
[image]
ImageInterfaceCalScanRotation
and
[hardware]
ScanRotation
Great question.
The basic difference is that the [hardware] keywords such as:
OperatingVoltagePresent=1 ; non-zero = high voltage interface present
BeamCurrentPresent=1 ; non-zero = beam current interface present
BeamSizePresent=1 ; non-zero = beam size interface present
BeamModePresent=1 ; non-zero = beam mode (scan/spot) interface present
MagnificationPresent=1 ; non-zero = magnification interface present
AutoFocusPresent=1 ; non-zero = auto-focus interface present
ROMPeakingPresent=1 ; non-zero = ROM based (instrument) peaking interface is present
ColumnConditionPresent=1 ; non-zero = column condition interface present
ReflectedLightPresent=1
TransmittedLightPresent=1
HysteresisPresent=0
ImageShiftPresent=0
and your specific one:
ScanRotationPresent=0 ; non-zero = scan rotation interface present (Cameca SX100 and JEOL 8200/8500 only)
tells our software if that hardware/instrument function is present and/or supported (or utilized) by the driver interface. So if you did *not* want to automate your magnification read and writing for example, you could set that keyword to zero and then no magnification reads or writes would go to the instrument.
The value of the scan rotation tells the software what value the scan rotation should be set to upon software start up...
For example, on my instrument (I don't use the rota veri command so I am always reading in direct data values), the scan wants to be set to 9.0 degrees from the default mechanical position on start up for my beam scan rectangle to be orthogonal to the stage axes. So my keyword looks like this:
ScanRotation=9.0 ; default scan rotation value to send on startup
Now, as for the [image] section of the probewin.ini file, that is specifically intended for analog image acquisition and stage extent calibration. That is, to calibrate the beam scan images to stage coordinates so each pixel in the BSE or SE image is absolutely registered to the stage coordinate system using a 2 or 3 point fiducial reference system.
The reason for doing this is so the stage acquired analysis positions are properly displayed on the analog signal images. Also it allows for precise alignment for creating automatic mosaics from random images or grids of images.
This requires that beam scan be calibrated in micron or mm stage units in X and Y and that also the scan rotation be specified. This is because although the instrument is supposed to keep the scan rotation constant as the mag is changed, there is often a small amount of scan rotation "drift" going through the different beam scan mag coils.
Previously, Probe for EPMA used a single calibration for the entire range, but now Probe for EPMA uses a similar calibration system to Probe Image, in that one may specify multiple beam scan calibrations over a range of magnifications and now, also the keV setting since that can sometimes also have a small effect on the beam scan calibration as well.
In Probe for EPMA these beam scan calibrations are specified in the [image] section of the Probewin.ini file as seen here for my old probewin.ini file:
ImageInterfaceImageIxIy=1.3333 ; SX100 Video Ix/Iy (4:3 for SX100)
ImageInterfaceCalNumberOfBeamCalibrations=1
ImageInterfaceCalKeV="15.0"
ImageInterfaceCalMag="400.0"
ImageInterfaceCalXMicrons=943.8 ; SX100 Video X calibration in um
ImageInterfaceCalYMicrons=714.3 ; SX100 Video Y calibration in um
ImageInterfaceCalScanRotation="9.0"
Note that because the IxIy image aspect ratio is not 1:1, the X and Y calibration must also be close to that ratio. Also, note that your Probewin.ini file might not have the "ImageInterfaceCalNumberOfBeamCalibrations" keyword, but it defaults to 1.
If you want to utilize additional calibration points, so for example, the software can interpolate different calibrations for different scan coils, that is done as shown here:
ImageInterfaceCalNumberOfBeamCalibrations=3
ImageInterfaceCalKeV="15.0,15.0,15.0"
ImageInterfaceCalMag="400.0,800.0,1600.0"
ImageInterfaceCalXMicrons="943.8,471,235.8" ; SX100 Video X calibration in um
ImageInterfaceCalYMicrons="714.3,357,178.5" ; SX100 Video Y calibration in um
ImageInterfaceCalScanRotation="9.0,9.2,9.4"
Right now these are edited by hand, but Probe Software is working on a new and very slick set of code that allows the user to very easily calibrate beam scan images and automatically save the calibrations.
Note also that if more than one value is defined per keyword, the values must be comma separated and all enclosed in double quotes as shown above. The reference manual has a short description of this here:
http://www.probesoftware.com/download/PROBEWIN.pdf#page=73Let me know if you have further questions.
If you can't see some "in-line" images in a post, try "refreshing" your browser!