Parameters

The Parameters dock is used for passing special variables that are applied:

• when first attaching a new individual's data

• when hitting Refresh (to reload the individual's data anew)

• when executing a Luna script

Parameters (Luna) versus configurations (Lunascope): note that the Param tab described here passes instructions to the core Luna engine; in contrast, the Config tab is used to specify settings that are specific to the Lunascope viewer.

It can sometimes be necessary to specify parameters to allow data to be loaded - e.g. if the annotations have a nonstandard YMD date format, one would add date-format=YMD or else Lunascope would give an error when first trying to load those. This is equivalent to the options that come before the main Luna script:

luna s.lst 1 date-format=YMD th=2.5 @param.txt -o out.db < script.txt

i.e. in the above,

• date-format is a special variable that controls Luna's behavior

• th is a user-defined variable, i.e. that is required by the script.txt Luna script, for example

• @param.txt includes a file of other parameter values; here one would directly Load param.txt into this dock (and add other options as desired)

Aliases and remapping

One common use of parameter files is to rename signals (alias) and annotations (remap). If these are defined on loading, then the Signals and Annotation docks will display those mapped labels, rather than the originals.

By default Luna includes some default mappings (unless annot-remap=F and/or nsrr-remap=F is set). The Parameters tab can be used to view the currently defined variables, and also to show the current set of (internal and/or user-defined) signal and annotation mappings:

Loading parameter files

You can specify a parameter file when initiating Lunascope from the command line with the -p option:

lunascope s.lst -p param.txt

which will pre-populate this dock with that file.