Presets and Defaults¶

Using a preset¶

AMSinput always first uses the Defaults preset as included by SCM. Next the Defaults preset defined by the user (if any). Finally, a preset matching the current task will be loaded (either from SCM or defined by the user).

When you switch the Task, AMSinput will try to load a matching preset.

If you have saved matching presets yourself these will be used instead of the standard presets, thus allowing you to set your own defaults as you like them. A matching preset is a preset that has the same name as the Task selected, user-defined presets are searched first. If no matching preset is found, AMSinput will load a preset matching the Single Point task (which is always available). For presets to match, spaces and minus signs are ignored.

You can also load any preset you like using the Preset command from the File menu. This preset will be applied just as the other presets, so it does make a difference when you load the preset.

Color Code¶

The input fields use a color coding to warn you they have been modified:

• No special color: the field has its original default value.
• Yellow: the field has been changed by the user (only).
• Green: the field has been changed by the preset (only).
• Red: the field has been changed by the preset, and next by the user.

The pull-down menus in the panel bar use a similar color-coding to point you to fields that have been changed:

• No special color: all fields in the panel have their original default value.
• Yellow: some fields have been changed by the user.
• Green: some fields has been changed by the preset.
• Red: some fields has been changed by the preset, and some (possibly also) by the user.

Make your own presets¶

It is very easy to make your own presets, collecting all or a few default values for the typical jobs you like to perform.

By default presets are saved in the $HOME/.scmgui/Tpl directory. This can be changed by setting the SCM_TPLDIR environment variable.

To make your own preset, follow these steps (in AMSinput):

• edit all the fields as you would like them to be stored in a preset.
• select ‘Save as preset…’ from the Preset menu, or ‘Save as full preset…’
• specify a name
• click on Save

If you now check your Preset menu you will find a new entry.

The name of the preset is the file name you have chosen, but without the .tpl extension.

The difference between a Full Preset and a ‘normal’ Preset is that a Full Preset will save all input options, and a ‘normal’ preset will save only the yellow, green or red fields (options that have been changed by the user or by the active template).

If you wish to store only fields that you have changed yourself in the preset, make sure you start with the None preset.

If you save a preset with the same name as one of the default presets, it will effectively replace that preset. One exception: the SCM supplied Defaults are always read first, and thus cannot be replaced.

Some presets are only available for specific methods. For example, the Fragment Analysis preset is only available for ADF. You can get this behavior for your own presets by pre-pending the name of your preset by the name of the method for which it should be available. For example “ADF_My_Defaults”, or “BAND_My_band_Defaults”.

To delete your own preset(s), use the ‘Delete Preset’ command from the Preset menu.

Multiple presets are used¶

The default values that are used when you start AMSinput are generated as follows:

• Use the Defaults preset supplied by SCM
• Use the Defaults preset that the user has defined, if any
• Use the ‘Single Point’ preset, either supplied by SCM or one that is defined by the user (if any)
• Any user selected preset, directly or implicitly (by changing the Task).

Input options remarks¶