II.5 - Agrogenom genomic blocks of evolutionary events (first pass)

Blocks of evolutionary events ( gene duplication, D, or transfer, T) involving several neighbour genes ; this is a first pass of running the script getblockevents.py to find congruent neighbouring events across gene family trees.This will allow (at the next step) to pick the optimal events amongst the set of mutually exclusive events retained as possible for a gene tree node at the previous step (see item #II.4).<br><br>getblockevents_out.<b>l.</b>*/ folders are results of parallel jobs searching for neighbouring genes in extant ("leaf") genomes involved in similar events, i.e. <b>leaf blocks</b>; each job searched separately within a set of replicon (or contigs). This search is performed with a greedy algorithm covering chromosome; "gap" genes without signal for a congruent event are first allowed, and then tested for compatibility and eventually rejected if negative.<br>getblockevents_out.<b>a</b>.*/ folder is the result of the single job that searched for leaf blocks linking to the same events in gene trees, to reconstruct the one <b>ancestral block</b> of genes from which descend the extant blocks of co-evolved gene.<br><br>The file structure in <i>getblockevents_out.</i><i>l.</i><i>*/</i> folders is similar:- <i>blocks/</i> folder: one file per replicon listing genes involved in a block- <i>before_split_blocks.stats</i> file: stats on blocks generated by the greedy algorithm recognizing similar events based on their event characteristics, i.e. the sets of possible recipient and donor species;- <i>transferred_blocks.stats</i> file: stats on blocks after the compatibility of common events with gap gene trees was checked and incopatibility resolved by splitting the initial blocks into several blocks.<br>[omitted here for space sake, several Gb altogether]:- <i>block_trees/</i> folder: the gene trees associated to the block events - <i>replicon.shelve</i> file: the serialized Python objects containing all the genes borne by a replicon/contig and the event block that link them.<br> file structure in <i>getblockevents_out.a</i><i>.</i><i>*/:</i>- <i>ancestral_blocks</i> file: list of all ancestral blocks and the leaf blocks they link to;<br>[similar files as described above for leaf blocks]- <i>blocks_events.mat</i> file: summary of block events recorded between donor and recipient (ancestral) species pairs[omitted here for space sake, several Gb for 1 file]:- <i>ancblocks.shelve</i> file:the serialized Python objects containing all the ancestral blocks and the leaf blocks linked to them