You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
change MutationType method setDistribution() to setEffectDistributionForTrait(Nio<Trait>trait, string$distributionType, ...)
48
+
change MutationType method drawSelectionCoefficient() to drawEffectForTrait([Nio<Trait>trait = NULL], [integer$ n = 1])
49
49
add SLiMgui autofixing for all of the above changes in QtSLiMWindow::checkTerminationForAutofix()
50
-
add MutationType method setDefaultDominanceForTrait(Nio<Trait>trait, floatdominance) (approximately replacing writing into the dominanceCoeff property, but this should not autofix)
50
+
add MutationType method setDefaultDominanceForTrait(Nio<Trait>trait, floatdominance) (approximately replacing writing into the dominanceCoeff property, but this should not autofix)
51
51
transition MutationType's internals to keep a separate DE for each trait using a new EffectDistributionInfo struct
52
52
added C++ IsPureNeutralDFE() method to represent whether all of the effects of a given mutation type are all neutral
53
53
add Individual properties for each trait in the individual's species, allowing direct access
@@ -162,7 +162,7 @@ version 5.0 (Eidos version 4.0):
162
162
policy change: the 1D SFS graph and haplotype plot no longer depend upon the current chromosome range selection; that was weird, and doesn't work well in multichrom
163
163
policy change: the "remove fixed mutations" stage of the WF tick cycle is now after "offspring become parents" (no user-visible difference except WF tick cycle diagram)
164
164
policy change: mutationRuns= for initializeSLiMOptions() has been changed to [l$ doMutationRunExperiments=T]; pass mutationRuns= to initializeChromosome() instead
165
-
policy change (slight): the haplosome1Nullandhaplosome2Null parameters to addEmpty() now apply only to type "A" chromosomes, causing a minor break in backward compatibility
165
+
policy change (slight): the haplosome1Nullandhaplosome2Null parameters to addEmpty() now apply only to type "A" chromosomes, causing a minor break in backward compatibility
166
166
policy change: randomizeStrands must now usually be explicitly specified for both addRecombinant() and addMultiRecombinant();
167
167
the default is now NULL, and NULL errors so that T or F must be explicitly given unless it does not matter (i.e., there is no recombination)
168
168
policy change: fix #487, changing TSK_SIMPLIFY_KEEP_UNARY to TSK_SIMPLIFY_KEEP_UNARY_IN_INDIVIDUALS for retainCoalescentOnly=F (a change in simplification behavior)
0 commit comments