Excluding merged inits

[okofish]

Changes

• Add an EvaluationParameters option to include/exclude inits that merged with another init (set to exclude by default)

Comments

• It turns out that in large scale computations ~99.9% of inits end up with this conclusion reason (which is good; it means the shared trie is very effective). These are of limited scientific interest, and discarding them massively reduces the size of output files.
• We may eventually want a generic mechanism for choosing the conclusion reasons to keep/discard. This could then be exposed on the command line.

---

This change is 

[maxitg]

Reviewed 2 of 2 files at r1.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @okofish)

---

libPostTagSystem/PostTagSearcher.hpp, line 55 at r1 (raw file):

    Checkpoints checkpoints = {};
    bool includeUnevaluatedStates = false;
    bool includeMergedStates = false;

We need to either fix the failing test or make includeMergedStates = true by default.

[okofish]

Reviewable status: 2 of 3 files reviewed, all discussions resolved (waiting on @okofish)

---

libPostTagSystem/PostTagSearcher.hpp, line 55 at r1 (raw file):

Previously, maxitg (Max Piskunov) wrote…

We need to either fix the failing test or make includeMergedStates = true by default.

I set includeMergedStates = true for this test.