If something happens in 25 % of all cases in every generation, what will the frequency converge to in the long run?

I just saw this map http://consang.net/images/c/c4/Globalcolourlarge.jpg (available on Archive.org if it would ever disappear) and become curious about how inbred people actually are.

3 scenarios:

  1. In quite a few countries around 25 % of all marriages are between cousins. If that number is constant over the generations, how inbred is the average person living in such a country?

  2. In the worst countries around 50 % of all marriages are between cousins. Same question as in (1).

  3. And the same the question for the countries with only 1 % cousin marriages.

Where do these three scenarios converge? Naïvely I figured it should be at 50 %, 100 % and 2 % but I can’t really motivate that guess.

What are the requirements and use cases on doing a Front End Technical Architecture?

I’m basically new to creating architectural stuffs and I’m now asked to create a “Technical Front End Architecture”, but my understanding for that term is that I need to list all the tools that I’m gonna use to build a front end website. I don’t know if I’m in the correct path but I’m totally lost.

Any suggestions or articles to refer on what to anticipate during this process of creating “Front End Technical Architecture”?

Using the same entity for different use cases

Suppose I have a User entity with name and age attributes. A User can own Boxes. A Box has the name and color attributes. Business rules dictate that one User can own at most 5 boxes. So, in this case, the User can be the aggregate root and whenever a new Box is bought by a User, I can do

class User {   private boxes: Box[];   private MAX_BOXES = 5;    // snip    addBox(Box box) {     if (this.boxes.count > MAX_BOXES) {       throw new BoxLimitException();     }      this.boxes.add(box);   } } 

However, when I want to edit one Box‘s (or a User, for that matter) attributes, the box limit business rule is no longer needed so I should be able to just modify it directly, without going through the aggregate, i.e.:

box->paint(GREEN); 

But, according to what I’ve read on DDD, you’re not supposed to do that, since you’re breaking the bounded context of the aggregate root. Should I have different Box entities depending on the use case? Specially since a Box might have its own business rules independent of those of a User aggregate.


I already asked a similar question, but it got no answers, so I tried with this new, simpler example, to better explain my doubts.

DDD different aggregates for the same model but different sagas / use cases?

I have an invoice aggregate that I create with a lot of data:

$  invoice = Invoice::create(     InvoiceId::generate(),     $  lines, // Collection of lines     InvoiceNumber::create('1'),     $  address, // Address value object     Currency::EUR(),     null,     $  discounts // Collection of discounts for lines and the invoice itself ); 

So this works perfectly fine when I create a new invoice or edit an existing invoice. But what if I just want to cancel an invoice?

The CancelInvoiceCommand contains just the identifier and the handler then needs to instantiate the aggregate. But I don’t have nor do I need all the data above. So can I simply do something like this?

$  invoice = Invoice::createForStateChange($  invoiceId); $  invoice->cancel(); 

The problem with that is, it will use the same aggregate object that implements Invoice::create() as well. The problem I try to understand is, that when I do that, the aggregate will be in an invalid state because it has a lot other methods as well to operate on the data that is available when create() was used but not when createForStateChange() was used.

Do I have to always create an aggregate root with all available data or can I have also another aggregate that addresses the same domain but a different process / part of it? So I would have a more simplified aggregate that just relies on having the id present?

enzo thrust some cases of agony that can

aspect results on account that Lyriana is enzo thrust guaranteed safe with constituents coming only from common supply. Additionally it is tested very effective through ladies who had been satisfied by using the product themselves. Learn A sore male organ is high-quality addressed speedily, as an alternative than left out. These are 5 steps guys can take to get on the avenue to health. "walk it off, soldier!" that's the phrase most guys…

enzo thrust some cases of agony that can

If a wizard casts a fireball indoors, wouldn’t that start a fire in most cases?

If a wizard casts a fireball indoors, wouldn’t that start a fire in most cases? Same with wall of fire, wouldn’t everything combustible nearby be engulfed in flames?

I imagine if a wizard was in my house and hit me with a fireball, the whole neighbourhood would be up in flames in short order, how do dm’s handle this?

I can’t shutdown windows 10. and when booting up in specific cases i get a graphical error

So this started after installing antergos linux on my legacy bios machine (same hdd). When i shutdown windows it just goes to the log-in screen and if i try to shutdown it from the log-in screen, nothing happens.

Oh and when i shutdown the system by holding the power button then booting again into windows i get a graphical error(or a glitched image). the only way to fix this is to boot into antergos then shutdown (restarting won’t temp fix it) after that i can boot into windows again.

How to generate all possible test cases of length $n$ for comparison sorts

Comparison sorts only care about the relative order of elements, not their exact values. So if the relative order of two arrays are the same, a comparison sort algorithm will act the same way on those two arrays.

For example, [0, 3, 1, 9, 1] is the same as [-3, 12, 7, 13, 7], since their relative orders are the same.

I want to generate all possible test cases of length $ n$ for comparison sorts that all possible relative orders are considered, and no two different test cases have the same relative order.

The number of possible test cases of length $ n$ is given by A000670.

Here are all possible test cases of length 0:

[] 

Here are all possible test cases of length 1:

[0] 

Here are all possible test cases of length 2:

[0, 0] [0, 1] [1, 0] 

Here are all possible test cases of length 3:

[0, 0, 0] [0, 0, 1] [0, 1, 0] [0, 1, 1] [0, 1, 2] [0, 2, 1] [1, 0, 0] [1, 0, 1] [1, 0, 2] [1, 1, 0] [1, 2, 0] [2, 0, 1] [2, 1, 0] 

Is there a generic way rather than brutal force to generate these test cases?

What are those random variables’ distributions? (the cases below)


Forty-four babies—a new record at the time—were born in one 24-hour period at the Mater Mothers’ Hospital in Brisbane, Queensland, on December 18, 1997. There were eighteen girls and twenty-six boys, and the observed mean and standard deviations for birthweights were (in grams)

enter image description here

Suggest a distribution, including parameter estimates, for each of the following random variables: (a). The time between births; (b). The time between births of boys; (c). The number of births in an hour; (d). The number of girls born between two boys; (e). The number of girls in ten births; (f). The average birthweights for both the boysand the girls.

I don’t know what distributions d and f are, and their parameters.

Thank you for your time.

GAE Standard: In what cases would I actually require a single instance to run permanently vs. spinning up only when there’s user activity?

I’m looking to create a website on GAE utilizing the Node.js Standard environment. The website will be a two-sided marketplace (similar to Fiverr, Uber, Airbnb, etc.) where I’d be performing back-end logic and CRUD updates with the Cloud Firestore database. I’m also looking to leverage Firebase Authentication, Cloud Storage, Cloud Functions, and Cloud Messaging.

Given my use case above, am I okay with just using the F1 instance class with the auto_scaling option that only creates an instance with actual user activity on my website (assuming low user activity)? If not, why?

What limitations should I keep in mind that may cause me problems right off the bat or in the near future? Roughly how much user activity would make this impractical? Why?

Thanks in advance.