If you synchronize a parameter variation object to another one, the graphics settings are copied so that they are the same for both objects. However, size and position of the corresponding view objects are not synchronized automatically up to now. This missing feature has been implemented today.
Batch control window
Writing results to batch control tables has been improved: The receiving cells are now formatted to use the number of digits which have been set for the individual fit parameters.
Fit parameter factors
The definition of fit parameters in the list of fit parameters allows you to specify a factor. This number multiplies the original value in such a way that the value displayed in the first column of the list is the product of the original value and the factor. However, fit parameter values written to the batch control tables or extracted by OLE automation did not take into account the factor.
The behaviour has been improved in the following way: The dialog for fit options (File/Options/Fit) now allows you to check the option ‘Apply factor in fit parameter transfers’. If active, the factor is used in the batch control and for OLE automation transfers (in both directions, i.e. setting or reading values). If the option is unchecked, the program behaves as before.
The option is not stored as part of the configuration, but is stored for each user as default setting. Once switched on it stays on until you switch it off.
In addition, you can check or uncheck this option by new OLE automation methods called ‘apply_factor_in_fit_parameter_transfers’ and ‘do_no_apply_factor_in_fit_parameter_transfers’.
Temporary target values, third set available
We have introduced a third set for temporary target values which is used for “color and thickness values”. At the same time we have added a section about temporary target values to the documentation.
SPRAY help now online
Finally we have generated an online version of the SPRAY documentation. We recommend to use this source of information from now on – it will be updated most frequently.
Here is the link: SPRAY online help
New object computing absorption spectra
We have implemented a new type of detector: Objects of type ‘Absorbing material’ count rays which are absorbed in a selected material. After the ray-tracing the counts are normalized to the number of emitted rays. This results in an absorption spectrum.
Objects of this type can be used to measure absorption of light in objects which have a complex shape, like a silicon wafer with textured surfaces.
OLE server only
When I try to start the software I get the message: ‘This program can be used as OLE server only!’. What does that mean?
The program has been installed with a passport file which allows to run the program as OLE server only. It cannot be started as a normal desktop application.
Very likely you have downloaded the software from our website and installed it on your system. The download packages do not contain valid passport files, i.e. valid user licences. After the installation, you have to copy a valid passport file into the program directory.
In the case of SCOUT, the passport file is called scout_passport.wtp. If you installed CODE the name is code_passport.wtp.
In the case of a software purchase you should have received a passport file from us either by e-mail or with the setup CD. If you are evaluating the software you should have received a passport file with a demo licence by e-mail.
Can’t create object
I try to use CODE in VisualBasic but I get the error message ‘ActiveX can’t create the object’?
First check if the name of the OLE automation server in the VisualBasic command is correct. The server name of CODE is ‘code.colors’.
If this does not solve the problem, the registration of the OLE automation server is probably incorrect for some reason. When you run the setup program, CODE is registered as OLE automation server automatically. If this action failed, a call of the server in VisualBasic does not work. In this case you can do the registration manually.
Start a Windows command line by clicking on the Windows key on your keyboard followed by the letter ‘r’ (for run). You must have administrator rights to do registrations. If you are logged-in as a normal user, you can right-click the command line in ‘Start/accessories’ and select the option ‘Run as administrator’. Once the command line is available, type in the command
“c:\program files\code.exe” /regserver
where you should make sure that you use the double quotes as shown. The path of the program file code.exe must be adapted to your system, of course, i.e. it should point to the location of your code program.
If you work with different CODE versions on one computer, you might want to use the command
“c:\another_installation_folder\code.exe” /unregserver
in order to explicitly de-register a code program as OLE server.
Difference spectra
How can I display the difference of simulated and measured spectra?
Sometimes it is advantageous to inspect the difference of simulated and measured spectra in order to find out about appropriate model extensions. Please read the instructions below to activate the drawing of difference spectra.
Open the spectrum for which you want to see the difference with a right-click in the treeview. Select the local menu command File/Options/Difference/Show to turn on the difference display. This menu item is a checked property: Clicking on it changes its status from checked to unchecked or vice-versa.
The additional menu commands File/Options/Difference/Pen and File/Options/Difference/Line mode are used to control the appearance of the difference curve. Use these settings to clearly separate the difference curve from the simulated and measured spectra. You can use, for example, pen 3 (green by default) and line mode 3 (dashed).
No import routine
There is no import routine for my spectra. How can I get my data into the software?
If there is not import routine for your type of spectra, you should check first if your spectrometer system can export the spectra in a format which is recognized by our software. Most spectrometer packages can generate tables of the measured data in ASCII format which can be imported using the ‘xy-format’.
In desperate cases you can ask us to write an import routine for your type of spectra. We can do this if we get a description of the data format, and if it can be done with a reasonable amount of effort.