Genetic maps (linkage groups) contain tracks with markers, whose position is based on genetic linkage and is measured in 'cM' (centimorgans).

Creating genetic maps with markers is usually done in two steps (see below for the "shortcut" trick using DeriveMapListFrom):

  • create a map set with empty maps using 'add maps' command and
  • add markers with command 'add markers'.        

This section describes the procedure of adding maps.

The control INI file should have the information about the new map set, its location in the map set tree, the OrganismId, the list of map names, their accession and size, as well as other house-keeping information like ProcessRun, or DbSequences.

; Run description: if specified, a custom description will be used. Will be ignored if a RunId is specified.
;                  otherwise, "Added maps for {MapSet Accession No.}." will be used.
RunDescription="Added maps for Sorghum bicolor BTx623-IS320C"

; Organism ID (required): organism ID should exist.
; Display name (required): a name shown in MapSetTree.
; Description: please try to provide detailed description with proper credits.
Description="A set of ~10k markers, derived from 437-line recombinant inbred population of BTx623 and IS320C.
Original publication:
Resolution of Genetic Map Expansion Caused by Excess Heterozygosity in Plant Recombinant Inbred Populations
Sandra K. Truong, Ryan F. McCormick, Daryl T. Morishige and John E. Mullet"
; AccessionNo: accession of the genome build. See
; Source ID: database or institution that the MapSet/sequence originate
; DistanceUnit: choose 'cM' for genetic maps.
;               We suggest to add physical maps along with sequences. So use 'add sequences' instead of 'add maps'.

; 1. Using existing MapSetTree node
; Node ID: if specified, the MapSet with the new sequences will be placed on this node.
; 2. Adding new MapSetTree node to a parent node
; Parent node ID: if specified, the MapSet with the new sequences will be placed under this parent node as a child.
; 3. Adding new MapSetTree node under a new root node
; Root node name: usually an organism name. Ignored if the root name already exists.
;RootNodeName="Oryza sativa test"
; Root node order number: order of the root node in the MapSetTree. By default, 0.

; Number format culture: specifies a culture name used to parse numbers in data. Default value is en - English.
;                        e.g. de - German, es - Spanish, fr - French. For more cultures,
; Lists all the chromosomes, scaffolds or linkage groups.
; DeviveMapListFrom: if present, the map names and sizes will be derived from the file with marker mappings. The map start and end positions will
; correspond to lowest and highest coordinates of markers for each map
; AddModes: choose a mode to add name, mapping, qualifiers or sequence among
;           1. AddOrDie (default): add if not exists; die (throw exception) otherwise.
;           2. AddOrUpdate: add if not exists; update otherwise.
;           3. AddOrSkip: add if not exists; skip otherwise.

; The ID columns below are used in loading maps.
; Oracle: If there is no sequence/trigger assigned to these columns, you must specify a sequence for them.

You can instruct PersephoneShell to derive the list of maps from the file with marker mapping. The map names and sizes will be extracted from the marker file referenced in another control file, used for loading the markers. The map start and end positions will correspond to the lowest and highest coordinates of the markers on each map. To enable this, replace the explicit list of maps in [Maps] section with DeriveMapListFrom record:


Test the files:

PS> add map -c maps.ini -t

and then run the loading process for real:

PS> add map -c maps.ini -v

Please see the sample files in Samples\Map folder.