CrossPlan simplification problems

[LStrachan]

Last decided was to get rid of the drone IDs and stick only to drone colony IDs which can only create().

• What happens with real data where the colonies drones come from are unknown?

Currently there is a rule that only mated colonies produce drones.

• Option to get rid of this rule in droneColonies since no genetic information comes from the father so virgin colonies would be enough (though this isn't biologically accurate).

  Another option is to keep mating to the drones in the cross plan, creating a DCA from founderQueens MapPop and using dronePackages made from DCA to mate with VirginColonies

  • Problem with this is when the number of virginColonies gets too large and the numbers of dronePackages would be huge

Possibility to ignore the mated virgin queen rule but only in the initial set up from the founderQueens?

[LStrachan]

Notes taken from the last meeting

[JerBub]

we can create function for setting up founder colonies. This function should allow crating drones from virgin queens. In neext step we would have colonies with virgin queens and drones. Now, we can cross colony to colony.

[janaobsteter]

OK, summarising the options again:

• keep the option to mate with drones specifically in the cross plan --> downside: this is complicated since we have about 10 different options to mate a queen and the cross function has a lot of parameters
• only allow mating with colonies in the cross plan --> downside: this means that initial drone colonies must be mated to drone packages (and not via cross plan) which could be computationally demanding & what happens when people have real pedigrees and want to mate to specific drones
• get rid of the rule that only mated colonies can produce drones --> can this bit us in the ass later on?
• create a function "createInitialMatedColonies" in which the rule of not creating drones from the virgin colonies could be breached --> downside: this is yet another functions which doesn't help in trying to simplify things

[janaobsteter]

Also, when the cross was complex, we had three auxiliary functions:

• crossDroneGroups
• crossDroneID
• crossColonyID

If we don't allow mating with drone IDs anymore, do we still need them?

[gregorgorjanc]

Done in devel:

https://github.com/HighlanderLab/SIMplyBee/commit/c9576aac81565b876b081a27716d9521cb654e5e https://github.com/HighlanderLab/SIMplyBee/commit/ef119ab6ebd876fba7501d4da498a03a64668b29 https://github.com/HighlanderLab/SIMplyBee/commit/55b6b8c9c52a23126b1e0c8f640ecb2195af072f https://github.com/HighlanderLab/SIMplyBee/commit/0d655da974f0f4d145988ec1d822fae6abec437c https://github.com/HighlanderLab/SIMplyBee/commit/c9576aac81565b876b081a27716d9521cb654e5e