<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://www.simulace.info/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Vasodzh</id>
	<title>Simulace.info - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://www.simulace.info/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Vasodzh"/>
	<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php/Special:Contributions/Vasodzh"/>
	<updated>2026-07-27T13:14:58Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.1</generator>
	<entry>
		<id>http://www.simulace.info/index.php?title=WS_2021/2022&amp;diff=22484</id>
		<title>WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=WS_2021/2022&amp;diff=22484"/>
		<updated>2022-02-08T12:28:47Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Semestral papers from winter term 2021/2022. Please, put here links to the pages with your paper. First you need to have your [[Assignments WS 2021/2022|assignment approved]]&lt;br /&gt;
&lt;br /&gt;
[[Carsharing_Fleet_Optimization|Carsharing Fleet Optimization]], Sergei Shcherbinin [[User:Shcs00|shcs00]] 16:57, 20 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
[https://www.simulace.info/index.php/Optimizing_the_Process_of_Baking_Wedding_Sweets#Model_Source_Code Optimizing the Process of Baking Wedding Sweets], [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 15:25, 21 January 2022 (CET)&lt;br /&gt;
&lt;br /&gt;
[https://www.simulace.info/index.php/A_b_test A/B test] By Vaso Dzhinchvelashvili 27 January 2022 (CET)&lt;br /&gt;
&lt;br /&gt;
[https://www.simulace.info/index.php/Is_it_possible_to_stop_fake_news Is it possible to stop fake news], [[User:Mart13|Tomáš Martínek (mart13)]] ([[User talk:Mart13|talk]]) 14:41, 30 January 2022 (CET)&lt;br /&gt;
&lt;br /&gt;
[https://www.simulace.info/index.php/Scooter_rental Scooter rental], Liudmila Kalashnikova, 31 January 2022&lt;br /&gt;
&lt;br /&gt;
[[Covid-19-vaccination|Effects of COVID-19 vaccination on the spread of infection]], Laura Kundmüller, 1 February 2022&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22291</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22291"/>
		<updated>2022-01-28T18:57:01Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &amp;lt;br&amp;gt;&lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
&lt;br /&gt;
* Expectation of the metric&lt;br /&gt;
* Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
&lt;br /&gt;
'''Delta''' – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
&lt;br /&gt;
'''Experiment length months''' – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
&lt;br /&gt;
'''Sample size''' – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
&lt;br /&gt;
'''Sample size power''': how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
&lt;br /&gt;
'''Sample size Lehr’s rule''': How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Sample size formula''': How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Is random= 1 – is not random''' – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula for a sample size to achieve, say, 95% chance of detecting a difference. OR you can just use my calculator, which is easier.&lt;br /&gt;
'''Which I think is really something noone did before'''&lt;br /&gt;
&lt;br /&gt;
=Code=&lt;br /&gt;
Code, explanatory letter and examples of generated CSVs&lt;br /&gt;
[[File:Archive_sim.zip]]&lt;br /&gt;
&lt;br /&gt;
=Literature=&lt;br /&gt;
https://stats.stackexchange.com/questions/11131/sample-size-formula-for-an-f-test&lt;br /&gt;
&lt;br /&gt;
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2876926/&lt;br /&gt;
&lt;br /&gt;
https://sphweb.bumc.bu.edu/otlt/mph-modules/bs/bs704_confidence_intervals/bs704_confidence_intervals5.html&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22290</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22290"/>
		<updated>2022-01-28T18:47:04Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &amp;lt;br&amp;gt;&lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
&lt;br /&gt;
* Expectation of the metric&lt;br /&gt;
* Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
&lt;br /&gt;
'''Delta''' – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
&lt;br /&gt;
'''Experiment length months''' – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
&lt;br /&gt;
'''Sample size''' – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
&lt;br /&gt;
'''Sample size power''': how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
&lt;br /&gt;
'''Sample size Lehr’s rule''': How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Sample size formula''': How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Is random= 1 – is not random''' – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator.&lt;br /&gt;
'''Which I think is really something noone did before'''&lt;br /&gt;
&lt;br /&gt;
=Code=&lt;br /&gt;
Code, explanatory letter and examples of generated CSVs&lt;br /&gt;
[[File:Archive_sim.zip]]&lt;br /&gt;
&lt;br /&gt;
=Literature=&lt;br /&gt;
https://stats.stackexchange.com/questions/11131/sample-size-formula-for-an-f-test&lt;br /&gt;
&lt;br /&gt;
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2876926/&lt;br /&gt;
&lt;br /&gt;
https://sphweb.bumc.bu.edu/otlt/mph-modules/bs/bs704_confidence_intervals/bs704_confidence_intervals5.html&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22289</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22289"/>
		<updated>2022-01-28T18:43:33Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &amp;lt;br&amp;gt;&lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
&lt;br /&gt;
* Expectation of the metric&lt;br /&gt;
* Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
&lt;br /&gt;
'''Delta''' – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
&lt;br /&gt;
'''Experiment length months''' – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
&lt;br /&gt;
'''Sample size''' – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
&lt;br /&gt;
'''Sample size power''': how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
&lt;br /&gt;
'''Sample size Lehr’s rule''': How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Sample size formula''': How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Is random= 1 – is not random''' – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Code=&lt;br /&gt;
Code, explanatory letter and examples of generated CSVs&lt;br /&gt;
[[File:Archive_sim.zip]]&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22288</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22288"/>
		<updated>2022-01-28T18:42:59Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &amp;lt;br&amp;gt;&lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
&lt;br /&gt;
'''Delta''' – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
&lt;br /&gt;
'''Experiment length months''' – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
&lt;br /&gt;
'''Sample size''' – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
&lt;br /&gt;
'''Sample size power''': how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
&lt;br /&gt;
'''Sample size Lehr’s rule''': How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Sample size formula''': How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Is random= 1 – is not random''' – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Code=&lt;br /&gt;
Code, explanatory letter and examples of generated CSVs&lt;br /&gt;
[[File:Archive_sim.zip]]&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22287</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22287"/>
		<updated>2022-01-28T18:40:48Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
&lt;br /&gt;
'''Delta''' – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
&lt;br /&gt;
'''Experiment length months''' – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
&lt;br /&gt;
'''Sample size''' – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
&lt;br /&gt;
'''Sample size power''': how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
&lt;br /&gt;
'''Sample size Lehr’s rule''': How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Sample size formula''': How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Is random= 1 – is not random''' – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Code=&lt;br /&gt;
Code, explanatory letter and examples of generated CSVs&lt;br /&gt;
[[File:Archive_sim.zip]]&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Archive_sim.zip&amp;diff=22286</id>
		<title>File:Archive sim.zip</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Archive_sim.zip&amp;diff=22286"/>
		<updated>2022-01-28T18:40:38Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: Vasodzh uploaded a new version of File:Archive sim.zip&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Archive_sim.zip&amp;diff=22285</id>
		<title>File:Archive sim.zip</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Archive_sim.zip&amp;diff=22285"/>
		<updated>2022-01-28T18:37:49Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22284</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22284"/>
		<updated>2022-01-28T18:32:34Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
&lt;br /&gt;
'''Delta''' – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
&lt;br /&gt;
'''Experiment length months''' – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
&lt;br /&gt;
'''Sample size''' – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
&lt;br /&gt;
'''Sample size power''': how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
&lt;br /&gt;
'''Sample size Lehr’s rule''': How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Sample size formula''': How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Is random= 1 – is not random''' – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22283</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22283"/>
		<updated>2022-01-28T18:32:14Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
Delta – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
&lt;br /&gt;
'''Experiment length months''' – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
&lt;br /&gt;
'''Sample size''' – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
&lt;br /&gt;
'''Sample size power''': how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
&lt;br /&gt;
'''Sample size Lehr’s rule''': How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Sample size formula''': How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
&lt;br /&gt;
'''Is random= 1 – is not random''' – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22282</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22282"/>
		<updated>2022-01-28T18:31:25Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
Delta – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
Experiment length months – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
Sample size – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
Sample size power: how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
Sample size Lehr’s rule: How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
Sample size formula: How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
Is random= 1 – is not random – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22281</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22281"/>
		<updated>2022-01-28T18:31:11Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
Delta – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
Experiment length months – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
Sample size – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
Sample size power: how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
Sample size Lehr’s rule: How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
Sample size formula: How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
Is random= 1 – is not random – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22280</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22280"/>
		<updated>2022-01-28T18:30:24Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|600px|]]&lt;br /&gt;
[[File:Df_view2.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
Delta – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
Experiment length months – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
Sample size – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
Sample size power: how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
Sample size Lehr’s rule: How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
Sample size formula: How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
Is random= 1 – is not random – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22279</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22279"/>
		<updated>2022-01-28T18:29:59Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|300px|]]&lt;br /&gt;
[[File:Df_view2.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
Delta – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
Experiment length months – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
Sample size – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
Sample size power: how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
Sample size Lehr’s rule: How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
Sample size formula: How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
Is random= 1 – is not random – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22278</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22278"/>
		<updated>2022-01-28T18:28:10Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|300px|]]&lt;br /&gt;
[[File:Df_view2.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
Delta – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
Experiment length months – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
Sample size – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
Sample size power: how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
Sample size Lehr’s rule: How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
Sample size formula: How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
Is random= 1 – is not random – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Conclusions (business point of view)=&lt;br /&gt;
1)	All formulas give pretty much the same number of users. So any of them can be used.&lt;br /&gt;
2)	All formulas AND simulation display same number of users when it is 80% chance to detect a difference. That means, standard betta =20% is used in all the formulas. &lt;br /&gt;
Here is how I know that:&lt;br /&gt;
For the same parameters but monthly flow of 10 000 users (any huge number), the csv file generated the following statistics:&lt;br /&gt;
 [[File:Resultofab.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here we can see that when last column (chance of detection of non random difference) is close to 80%, all formulas give pretty much the same sample size.&lt;br /&gt;
In case you run a test for Facebook, monthly users of the feature can be far more then 10k.&lt;br /&gt;
3)	Formulas can be used only if you are satisfied with 20% chance of not detection. Otherwise, you should either be a good mathematician to be able to theoretically create a formula to get a formula for a sample size to get, say, 95% chance of detecting a difference. OR you can just use my calculator&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Resultofab.jpg&amp;diff=22277</id>
		<title>File:Resultofab.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Resultofab.jpg&amp;diff=22277"/>
		<updated>2022-01-28T18:27:59Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22276</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22276"/>
		<updated>2022-01-28T18:21:32Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
==Outcome of the simulation==&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|300px|]]&lt;br /&gt;
[[File:Df_view2.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:csv_file.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
Delta – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
Experiment length months – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
Sample size – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
Sample size power: how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
Sample size Lehr’s rule: How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
Sample size formula: How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
Is random= 1 – is not random – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22275</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22275"/>
		<updated>2022-01-28T18:20:59Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
=Results=&lt;br /&gt;
There are results of the simulation and results of the work (from a business point of view). First, we will see what is an actual outcome&lt;br /&gt;
&lt;br /&gt;
==Outcome of the simulation==&lt;br /&gt;
The result is the following. Here you can see what you can expect, if the delta is ±16% (both sides) and experiment held for 0.1… 1.3 months. &lt;br /&gt;
For the line 153, 0.16% delta can be noticed in 1 month with 11% chance.&lt;br /&gt;
&lt;br /&gt;
[[File:Df_view.jpg|300px|]]&lt;br /&gt;
[[File:Df_view2.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
11% is low. Now analyst understands that either he should be expecting higher difference (which is hard to achieve by replacing 1 feature with another), or state to a product manager (owner of the feature) that there is no reason to conduct an experiment with existing limitations (monthly user flow, delta (expected difference)).&lt;br /&gt;
&lt;br /&gt;
For the convenience the results are exported to out_ui.csv file, that can be found in the same repository where jupyter code was saved.&lt;br /&gt;
For me it is in a root folder:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.jpg|300px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When downloading a file, the same table is visible, so it might be more convenient to navigate to the .csv file:&lt;br /&gt;
&lt;br /&gt;
[[File:repo.csv_file|300px|]]&lt;br /&gt;
&lt;br /&gt;
What else is exported:&lt;br /&gt;
Delta – expected difference. ‘what happens if the difference in metrics is 1%?’&lt;br /&gt;
Experiment length months – ‘what happens if we wait 0.1 month (first line)?’&lt;br /&gt;
Sample size – these many users will we get if we wait 0.1 month with a monthly flow of 100 users   (note, users are divided equally into two groups, so if there is 100 monthly user flow, there will be 50-50 users in both groups).&lt;br /&gt;
Sample size power: how many users do we need according to pyhton function, if we need to detect 1% difference (and have some variation)&lt;br /&gt;
Sample size Lehr’s rule: How many users do we need according to Lehr’s rule of thumb to detect 1% difference.&lt;br /&gt;
Sample size formula: How many users do we need according to statistical formula from the article to detect 1% difference.&lt;br /&gt;
Is random= 1 – is not random – what is a chance we will notice the difference in 0.1 month if the real difference in means is 1% (3.9% chance for the first line – really low)&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Csv_file.jpg&amp;diff=22274</id>
		<title>File:Csv file.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Csv_file.jpg&amp;diff=22274"/>
		<updated>2022-01-28T18:20:19Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Repo.jpg&amp;diff=22273</id>
		<title>File:Repo.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Repo.jpg&amp;diff=22273"/>
		<updated>2022-01-28T18:19:25Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Df_view2.jpg&amp;diff=22272</id>
		<title>File:Df view2.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Df_view2.jpg&amp;diff=22272"/>
		<updated>2022-01-28T18:18:29Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Df_view.jpg&amp;diff=22271</id>
		<title>File:Df view.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Df_view.jpg&amp;diff=22271"/>
		<updated>2022-01-28T18:16:25Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22270</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22270"/>
		<updated>2022-01-28T18:15:17Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;br /&gt;
&lt;br /&gt;
4)	Please don’t brake the calculator intentionally: I tried to add all the required Catches of errors and suggestions on what can be fixed, but there is always a way to brake a code…&lt;br /&gt;
The bigger monthly sample size is, the bigger is a calculation time.&lt;br /&gt;
Now, pressing the button…&lt;br /&gt;
&lt;br /&gt;
5)	If there were no errors in the input, there is a timer-alike feature added, which will shed some light on how long is left for the calculations to finish. &lt;br /&gt;
[[File:Timer.jpg|400px|]]&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Timer.jpg&amp;diff=22269</id>
		<title>File:Timer.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Timer.jpg&amp;diff=22269"/>
		<updated>2022-01-28T18:15:06Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22268</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22268"/>
		<updated>2022-01-28T18:14:07Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|500px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|500px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|400px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22267</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22267"/>
		<updated>2022-01-28T18:13:49Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|700px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|600px|]]&lt;br /&gt;
&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22266</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22266"/>
		<updated>2022-01-28T18:13:30Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|700px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Ui.jpg|700px|]]&lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Ui.jpg&amp;diff=22265</id>
		<title>File:Ui.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Ui.jpg&amp;diff=22265"/>
		<updated>2022-01-28T18:13:16Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22264</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22264"/>
		<updated>2022-01-28T18:12:03Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
&lt;br /&gt;
[[File:Second_Block_of_code.jpg|700px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22263</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22263"/>
		<updated>2022-01-28T18:11:52Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
[[File:Second_Block_of_code.jpg|700px|]]&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Second_Block_of_code.jpg&amp;diff=22262</id>
		<title>File:Second Block of code.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Second_Block_of_code.jpg&amp;diff=22262"/>
		<updated>2022-01-28T18:11:35Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22261</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22261"/>
		<updated>2022-01-28T18:10:58Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot1.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
&lt;br /&gt;
 [[File:Block_of_code.jpg|700px|]]&lt;br /&gt;
&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22260</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22260"/>
		<updated>2022-01-28T18:10:14Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
[[File:Screenshot1.jpg|250px|]]&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
 [[File:Block_of_code.jpg|250px|]]&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22259</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22259"/>
		<updated>2022-01-28T18:05:47Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
[[File:Screenshot1.jpg]]&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
 [[File:Block_of_code.jpg]]&lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Block_of_code.jpg&amp;diff=22258</id>
		<title>File:Block of code.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Block_of_code.jpg&amp;diff=22258"/>
		<updated>2022-01-28T18:05:34Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=File:Screenshot1.jpg&amp;diff=22257</id>
		<title>File:Screenshot1.jpg</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=File:Screenshot1.jpg&amp;diff=22257"/>
		<updated>2022-01-28T18:04:23Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22256</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22256"/>
		<updated>2022-01-28T18:02:00Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
 [[File:[[File:Example.jpg]][[File:[[File:Example.jpg]]]]]]&lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
 &lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22255</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22255"/>
		<updated>2022-01-28T17:57:47Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Name:''' Sample size calculation for A/B test&amp;lt;br&amp;gt;&lt;br /&gt;
'''Author:''' Vaso Dzhinchvelashvili &lt;br /&gt;
'''Method:''' Monte Carlo&amp;lt;br&amp;gt;&lt;br /&gt;
'''Tool:''' Python&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Some theory=&lt;br /&gt;
A/B test is a test enabling to see how the feature influenced the performance (some target metric)&lt;br /&gt;
&lt;br /&gt;
α (Alpha) is the probability of Type I error in any hypothesis test–incorrectly rejecting the null hypothesis&lt;br /&gt;
&lt;br /&gt;
β (Beta) is the probability of Type II error in any hypothesis test–incorrectly failing to reject the null hypothesis.  (1 – β is power).&lt;br /&gt;
&lt;br /&gt;
=Problem definition=&lt;br /&gt;
Imagine you are the analyst and there is a real problem: you need to understand how many observations do you need, and how long should you conduct an experiment&lt;br /&gt;
==Limitations==&lt;br /&gt;
Normally, there are many experiments held within a same company, therefore, for a purity of an experiments, users should not be intersected (cannot participate in two different experiments at a same time) =&amp;gt; longer you conduct an experiment, more experiments are getting postponed, therefore development of a product is stopped/slowed down. &lt;br /&gt;
&lt;br /&gt;
So I hardcoded 3 months as a maximum length of an experiment, this way there is lower chance calculations will take an inappropriate time. &lt;br /&gt;
&lt;br /&gt;
Let’s assume there is an ‘old’ feature, and ‘new’ feature is developed to replace the old one. The company needs to decide which feature should be used and which one should be sunsetted (exluded from the product). Both features cannot exist outside the experiment.&lt;br /&gt;
&lt;br /&gt;
==Goal==&lt;br /&gt;
Your goal(as an analyst who uses the calculator) is to understand if a new feature is increasing/decreasing the target metric. You want an assumption to be statistically significant.&lt;br /&gt;
==What you have==&lt;br /&gt;
In real life situation there could be the following inputs:&lt;br /&gt;
&lt;br /&gt;
1 Historical information on how users performed in the past for the old feature.&lt;br /&gt;
Expectation of the metric&lt;br /&gt;
Variation of the metric&lt;br /&gt;
&lt;br /&gt;
2 How many users access the feature monthly&lt;br /&gt;
&lt;br /&gt;
3 Also, you have some assumptions: you expect a new feature to increase/decrease the metric by 0-x% (both sides). Of course, you want your metric to skyrocket (+10000%) but in reality, you don’t expect more than, say, 20% raise.&lt;br /&gt;
As mentioned, you can’t hold an experiment longer then 3 months. You might of course. But for the sake of evaluation of my work in somewhat appropriate time (calculation takes some time) I hardcoded the maximum length. But it could be changed in the code.&lt;br /&gt;
&lt;br /&gt;
4 Lastly, there is some chance you are ready to take, to be wrong when assuming a difference was random/not random (i.e. because of a new feature) – normally 5%.&lt;br /&gt;
&lt;br /&gt;
These parameters should be entered in the UI (how explained below)&lt;br /&gt;
&lt;br /&gt;
=Model=&lt;br /&gt;
The calculator uses Monte Carlo method to calculate the chances to see a nonrandom difference in means for samples. &lt;br /&gt;
&lt;br /&gt;
Also, the script uses 2 different formulas and 1 python function to calculate sample size needed to achieve some confidence level (as turned out, all the formulas are tuned for 80% accuracy, however, from the literature review it is not obvious where is a betta, as all the Z/T and other statistics have only alpha in the formulas).&lt;br /&gt;
&lt;br /&gt;
=How to run the simulation=&lt;br /&gt;
1)	Add UI-Copy1 clean file to a Jupiter notebook:&lt;br /&gt;
 &lt;br /&gt;
2)	Run the first block of code:&lt;br /&gt;
 &lt;br /&gt;
It should take not more then 20-30 seconds.&lt;br /&gt;
3)	Run the second block of code:&lt;br /&gt;
 &lt;br /&gt;
It should also be launched pretty fast. &lt;br /&gt;
As a result, the following UI should be visible. (I didn’t have to install any other software/libraries, but read on the internet someone had problems):&lt;br /&gt;
 &lt;br /&gt;
As it can be seen, all the parameters from the real life problem can be inserted to the calculator.&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=WS_2021/2022&amp;diff=22254</id>
		<title>WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=WS_2021/2022&amp;diff=22254"/>
		<updated>2022-01-28T17:42:21Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Semestral papers from winter term 2021/2022. Please, put here links to the pages with your paper. First you need to have your [[Assignments WS 2021/2022|assignment approved]]&lt;br /&gt;
&lt;br /&gt;
[[Carsharing_Fleet_Optimization|Carsharing Fleet Optimization]], Sergei Shcherbinin [[User:Shcs00|shcs00]] 16:57, 20 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
[https://www.simulace.info/index.php/Optimizing_the_Process_of_Baking_Wedding_Sweets#Model_Source_Code Optimizing the Process of Baking Wedding Sweets], [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 15:25, 21 January 2022 (CET)&lt;br /&gt;
&lt;br /&gt;
[https://www.simulace.info/index.php/A_b_test A/B test] By Vaso Dzhinchvelashvili&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test_v2&amp;diff=22253</id>
		<title>A b test v2</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test_v2&amp;diff=22253"/>
		<updated>2022-01-28T17:27:13Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: Created page with &amp;quot;sample text&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;sample text&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=A_b_test&amp;diff=22252</id>
		<title>A b test</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=A_b_test&amp;diff=22252"/>
		<updated>2022-01-28T17:22:38Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: Created page with &amp;quot;Sample text&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Sample text&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22241</id>
		<title>Assignments WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22241"/>
		<updated>2021-12-27T14:42:48Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, put here your assignments. Do not forget to sign them. You can use &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; (four tildas) for an automatic signature. Use Show preview in order to check the result before your final sumbition.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, strive to formulate your assignment carefully. We expect an adequate effort to formulate the assignment as it is your semestral paper. Do not forget that your main goal is a research paper. It means your simulation model must generate the results that are specific, measurable and verifiable. Think twice how you will develop your model, which entities you will use, draw a model diagram, consider what you will measure. No sooner than when you have a good idea about the model, submit your assignment. And of course, read [[How to deal with the simulation assignment|How to deal with the simulation assignment]].&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Topics on gambling, cards, etc. are not welcome.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| type  = content&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
In order to avoid possible confusion, please, check if you have added '''approved''' in bold somewhere in our comment under your submission. If there is no '''approved''', it means the assignment was not approved yet.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Spread of covid19 in closed/open area markets ==&lt;br /&gt;
&lt;br /&gt;
In winter 2021 in Czechia the christmas markets were banned due to another covid19 infection wave. On the other hand people are free to go into shopping malls. It would be interesting to use existing data about covid19 virus transmission in agent based simulation to see how many people get infected and in what speed depending on whether they are in a christmas (open) market, or in a shopping mall (closed). The main goal will be to see if the simulation would backup the decision that has been made about christmas markets.&lt;br /&gt;
&lt;br /&gt;
Possible research papers that contain data about covid spreading&lt;br /&gt;
* [https://www.kaggle.com/guidant/covid19-evolution-transmission-spatialpatterns/ Kaggle notebook - Covid19, Evolution, Transmission, Spatial Patterns]&lt;br /&gt;
* [https://link.springer.com/article/10.1007/s10668-020-00884-x/ Research - Understanding COVID-19 transmission, health impacts and mitigation: timely social distancing is the key]&lt;br /&gt;
&lt;br /&gt;
This simulation would be realised using NetLogo.&lt;br /&gt;
&lt;br /&gt;
Summary:&lt;br /&gt;
&lt;br /&gt;
'''WHAT will be simulated'''&lt;br /&gt;
* market place, which can be both open space or closed space.&lt;br /&gt;
* people with or without masks, who will walk from shop to shop, with some intention and some of them will be virus carriers&lt;br /&gt;
* virus, which will spread in places where people go through (depending on the closed/open area, the infection rates will differ)&lt;br /&gt;
&lt;br /&gt;
'''GOAL of the simulation'''&lt;br /&gt;
* answer the question: &amp;quot;Where is the virus spread more significant? At the market place, or at the shopping mall?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Angel Kostov, xkosa20&lt;br /&gt;
&lt;br /&gt;
: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 11:58, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Effects of COVID-19 vaccination on the spread of infection ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Currently, there is a new wave of infection in the COVID-19 pandemic with high number of infections. In Germany, for example, more than 50,000 new infections are currently reported every day. To reduce the infection rate, a wide variety of measures have been implemented. One of these measures are the vaccination and masks. Vaccination can reduce the risk of infection and the likelihood of transmissibility. A simulation is conducted to vividly identify the extent to which vaccination could contain the pandemic.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The purpose of the simulation is to show how COVID-19 vaccination affects the spread of the pandemic. I will use an agent-based model in order to simulate the scenario in a simplified form based on existing scientific data. In addition, current COVID-19 measures are considered.  &lt;br /&gt;
&lt;br /&gt;
Subjects of the simulation: &lt;br /&gt;
&lt;br /&gt;
Environment: &lt;br /&gt;
* A village with around 6.000 inhabitants&lt;br /&gt;
* Simplified: The village is closed that is new people cannot come in and people of the village cannot go out &lt;br /&gt;
&lt;br /&gt;
Agents: &lt;br /&gt;
* Vaccinated persons&lt;br /&gt;
* Unvaccinated persons &lt;br /&gt;
* Simulations with different vaccination rates to compare the different infection courses&lt;br /&gt;
&lt;br /&gt;
Further measures: &lt;br /&gt;
* All people wear masks&lt;br /&gt;
* Nobody wears a mask  &lt;br /&gt;
&lt;br /&gt;
Start: &lt;br /&gt;
* Few agents are unknowingly infected (e.g. 0,1% of the inhabitants = 6 people) &lt;br /&gt;
* Movement of agents intended to reflect the daily behavior of people in real life in a simplified form.&lt;br /&gt;
* One agent can infect another agent with a certain probability if they are close to each other. &lt;br /&gt;
* The probability of an infection depends on the measure (vaccination / mask)&lt;br /&gt;
&lt;br /&gt;
'''Goal:'''&lt;br /&gt;
* Identify the infection course with different vaccination rates and measures. &lt;br /&gt;
* Showing the importance of vaccination.&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Possible data sources'''&lt;br /&gt;
&lt;br /&gt;
https://www.rki.de/SharedDocs/FAQ/COVID-Impfen/FAQ_Liste_Wirksamkeit.html&lt;br /&gt;
&lt;br /&gt;
Chia, P. Y., Xiang Ong, S. W., Chiew, C. J., Ang, L. W., Chavatte, J.-M., Mak, T.-M., Cui, L., Kalimuddin, S., Chia, W. N., Tan, C. W., Ann Chai, L. Y., Tan, S. Y., Zheng, S., Pin Lin, R. T., Wang, L., Leo, Y.-S., Lee, V. J., Lye, D. C., &amp;amp; Young, B. E. (2021). Virological and serological kinetics of SARS-CoV-2 Delta variant vaccine-breakthrough infections: A multi-center cohort study. Clinical Microbiology and Infection, S1198743X21006388. https://doi.org/10.1016/j.cmi.2021.11.010&lt;br /&gt;
&lt;br /&gt;
Eyre, D. W., Taylor, D., Purver, M., Chapman, D., Fowler, T., Pouwels, K., Walker, A. S., &amp;amp; Peto, T. E. (2021). The impact of SARS-CoV-2 vaccination on Alpha and Delta variant transmission [Preprint]. Infectious Diseases (except HIV/AIDS). https://doi.org/10.1101/2021.09.28.21264260&lt;br /&gt;
&lt;br /&gt;
Harder, T., Külper-Schiek, W., Reda, S., Treskova-Schwarzbach, M., Koch, J., Vygen-Bonnet, S., &amp;amp; Wichmann, O. (2021). Effectiveness of COVID-19 vaccines against SARS-CoV-2 infection with the Delta (B.1.617.2) variant: Second interim results of a living systematic review and meta-analysis, 1 January to 25 August 2021. Eurosurveillance, 26(41). https://doi.org/10.2807/1560-7917.ES.2021.26.41.2100920&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Laura Kundmueller&lt;br /&gt;
&lt;br /&gt;
: OK, but, please, elaborate it a bit. How exactly should the simulation look like, kinds of agents, etc. And mainly: the sources of data, etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:00, 10 December 2021 (CET)&lt;br /&gt;
:: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 00:13, 17 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation of genetic algorithm: Travelling Salesman Problem ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The topic of this simulation is an old graph problem, Travelling Salesman Problem. My approach would be based on genetic learning algorithm. A random map will be generated at the start. Salesman is travelling in a car with some gas. The gas is used as he travels, it can be recharged at gas stations but it costs money. The map contains some hills and flat roads, which have a different cost of gas when going through. &lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
* to find the optimum path between the towns.&lt;br /&gt;
&lt;br /&gt;
'''The parameters are:'''&lt;br /&gt;
* number of agents (travelling salesmen)&lt;br /&gt;
* gas in car&lt;br /&gt;
* money&lt;br /&gt;
&lt;br /&gt;
* number of towns&lt;br /&gt;
* number of hills&lt;br /&gt;
* number of gas stations&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Mart13]] ([[User talk:Mart13|talk]]) 09:57, 9 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: Although this isn't a true agent-based simulation, we sometimes accept topics from artificial intelligence and other related fields. However, it is necessary to elaborate it in deep. How exactly the algorithm will work. What is the goal (not the goal of the agent, but the goal of this work)? Etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:03, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: &lt;br /&gt;
Algorithm:&lt;br /&gt;
* Basic genetic learning, gene is a path of an agent. My idea is that every patch of map has a different cost of going through. The agents must decide where to go and in which order.&lt;br /&gt;
* Fitness function is a score of an agent (the score of its path).&lt;br /&gt;
* I would like to implement mutation and crossover.&lt;br /&gt;
&lt;br /&gt;
Additional parameters to those introduced earlier:&lt;br /&gt;
* number of population&lt;br /&gt;
* number of mutations&lt;br /&gt;
* number of crossovers&lt;br /&gt;
&lt;br /&gt;
Goal of work:&lt;br /&gt;
* graphical interpretation of AI learning&lt;br /&gt;
&lt;br /&gt;
[[User:Mart13|Tomáš Martínek (mart13)]] ([[User talk:Mart13|talk]]) 11:49, 11 December 2021 (CET)&lt;br /&gt;
: '''Approved'''&lt;br /&gt;
&lt;br /&gt;
== Optimizing the process of baking wedding sweets ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
There is a wedding tradition in Czech Republic of baking wedding sweets and then handing them out to the guests of the weeding as a form of invitation. Process of baking usually takes whole day and several helpers in the kitchen are needed. Into paper baskets are usually packaged two types of sweets: several small ones with 3 different flavours and one so-called &amp;quot;rohový koláč&amp;quot;. Which are then delivered by the bride to wedding guests. For the purpose of this simulation are process and needed ingredients simplified.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
The goal is to optimize the number of helpers in the kitchen and find optimal amount of basic ingredients for specified number of guests.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Discrete simulation - SIMPROCESS&lt;br /&gt;
&lt;br /&gt;
'''Entities:'''&lt;br /&gt;
* sweets&lt;br /&gt;
* paper baskets&lt;br /&gt;
* baking trays&lt;br /&gt;
&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* pastry-cooks&lt;br /&gt;
* bride&lt;br /&gt;
* flour&lt;br /&gt;
* sugar&lt;br /&gt;
* curd&lt;br /&gt;
* plum jam&lt;br /&gt;
* poppy seed filling&lt;br /&gt;
&lt;br /&gt;
'''Process steps'''&lt;br /&gt;
* order for paper basket&lt;br /&gt;
* preparing sweets: small ones (3 different flavours), &amp;quot;rohove kolače&amp;quot; sweets (using all flavours)&lt;br /&gt;
* baking in the oven&lt;br /&gt;
* sugar coating&lt;br /&gt;
* packaging&lt;br /&gt;
* delivery&lt;br /&gt;
&lt;br /&gt;
'''Data:'''&lt;br /&gt;
* https://www.svetsvateb.cz/2021/02/623262-svatebni-kolacky/&lt;br /&gt;
* https://megvkuchyni.cz/recepty/speciality/svatebni-special-jak-na-svatebni-kolacky/&lt;br /&gt;
* experience&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 10:16, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: OK, maybe. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:05, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Carsharing company fleet optimization ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Recently, carsharing becomes more and more popular in large cities. Short-term rental (from several minutes to 24 hours) of a car with possibility to drop it anywhere in the allowed area in the city attracts people who for some reasons do not want to use their own vehicles. However, it is not always convenient. If the fleet is relatively small, the probability that a car will be somewhere close by is also quite low. Cars also must be refueled or recharged sometimes by external staff, which would increase cost of the fleet maintenance with increasing of the fleet size.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The proposing agent-based simulation will reproduce real situation with shared cars.&lt;br /&gt;
Two types of agents are planned:&lt;br /&gt;
* cars with different states (waiting, in rent, maintenance) and characteristics (mileage, fuel level)&lt;br /&gt;
* drivers - users of the service, who rent the cars and have their own behavior, including decision making on taking a car, driving style, and so on.&lt;br /&gt;
Some data for the model will be obtained as personal observations of two carsharing services operating in Prague, [https://anytimecar.cz/ Anytime] and [https://www.uniqway.cz/ Uniqway] (for example, number of available cars, which is visible in mobile applications). Another source of data would be statistics collected by other services abroad, for example, by operating in Russia service Yandex.Drive[https://www.statista.com/statistics/1224178/daily-use-duration-of-car-sharing-vehicles-in-moscow-by-vehicle-type/].&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
to find out optimal fleet size and structure and price policy to maximize revenue of a carsharing company.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Shcs00|Sergei Shcherbinin (shcs00)]] ([[User talk:Shcs00|talk]]) 12:34, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: I like the idea. Please, do not hesitate to contact the companies directly for the data. They are sometimes willing to help if you require just general, non sensitive data. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:08, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How long would it take to find love ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There is such thing as Drake formula used to calculate a chanse to meet an alien https://en.wikipedia.org/wiki/Drake_equation&lt;br /&gt;
Also there is an article https://e-lub.net/annuals/why.htm - to sum up, it is Drakes formula used to calculate a chance to meet a love of your life in London&lt;br /&gt;
&lt;br /&gt;
So What I want to do is to let user enter some parameters of what he/she thinks the perfect person is and based on the entered parameters we will see how long would it take to meet a perfect person in a city (say, Prague).&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Data about the city would be taken from official sources (might be Eurostat or some other data that is gathered by Czech statistical office)&lt;br /&gt;
User will enter all the parameters and then see when will he meet a person. &lt;br /&gt;
Of course for the sake of achievability some things will be simplified. For example I don't think I will actualy add millions of agents, Maybe hundreds would be enough.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
To see how year passes after year and love is still not found:) Or maybe to understand that lowering the expectations could correspond to finding a love faster&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo or AnyLogic&lt;br /&gt;
&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;br /&gt;
&lt;br /&gt;
: To be honest, althought it is a funny idea, the problem, in fact, is verification. You would deal with soft properties and attitudes, nothing what could be measured. Even the article wasn't apparently meant to be serious.&lt;br /&gt;
: Please, try finding something else. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 19:17, 17 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;UPD:&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
== Sample size for a/b test ==&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There are different approaches on how to calculate sample size for A/B test when measuring difference in means for treatment and control group:&lt;br /&gt;
1 Calculation through power of a test&lt;br /&gt;
2 Rule of thumb for power of a test: https://stats.stackexchange.com/questions/11131/sample-size-formula-for-an-f-test &lt;br /&gt;
3 some other formula https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2876926/&lt;br /&gt;
4 Formula derived from confidence interval https://sphweb.bumc.bu.edu/otlt/mph-modules/bs/bs704_confidence_intervals/bs704_confidence_intervals5.html&lt;br /&gt;
&lt;br /&gt;
And I think there should be more. They give different results&lt;br /&gt;
&lt;br /&gt;
Another problem is in type 1, type 2 error: researcher cannot always detect the difference or can detect the difference where there is no difference.&lt;br /&gt;
More importantly, in formulas the type 2 error is not used at all, whereas obviously it should be included in the models somehow, maybe as one of the axioms... &lt;br /&gt;
so the goal of simmulation is to illustrate the relation of type 1, type 2 errors, sample size, difference of means and the fact of rejecting/accepting null hypothesis. It will be a tool, which gives the researcher the answer 'how many observations do you need to detect the difference in a test'.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Simulate an A/B test: set distribution parameters for control and treatment groups, for different sample sizes. Calculate statistics (a;pha,betta, p-value) for the tests&lt;br /&gt;
Compare number of observations to the ones derived from formulas - this way the correct one could be picked.&lt;br /&gt;
&lt;br /&gt;
Illustrate real chances of type 1 and type 2 errors.&lt;br /&gt;
Illustrate how enhancing the difference in means leads (or doesn't) to decrease of needed sample size/ rise of significance.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
Pick the best method for calculation of sample size.&lt;br /&gt;
Have a clear understanding how to design a/b test, based on some inputs (expectations)&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Python, monte-carlo&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;br /&gt;
&lt;br /&gt;
== Scooter rental ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Today in almost each big city you can find a huge number of scooter which can be rented. The main feature of scooter rental is that you can take it at one point in the city and return it to another when you finish your route.&lt;br /&gt;
If there is no scooter nearby, then obviously a potential client will not take it. In addition, people prefer to ride with friends, so the likelihood of renting a scooter is higher if there are several of them at one point.&lt;br /&gt;
The more scooters there are in the city, the more chances that people will use this service, however, scooter support also requires additional resources and extra costs.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The goal of agent-based simulation is to define optimal number of scooters for specific city and its destribution within the city to maximize income of the company.&lt;br /&gt;
Two types of agents will be used:&lt;br /&gt;
*scooters with a list of states (rented, broken, available, available + near other scooters) and characteristics such as, for example, charge level.&lt;br /&gt;
*clients with different characteristics (for example, alone, with friend, maximal suitable distance to a scooter)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Agent-based simulation in NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:liudmila_kalashnikova| Liudmila Kalashnikova (liudmila_kalashnikova)]]&lt;br /&gt;
&lt;br /&gt;
'''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 00:24, 17 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Is it possible to stop fake news? ==&lt;br /&gt;
&lt;br /&gt;
Fake news is a global problem and it is getting worse every year. Is it possible to stop fake news? Fake news are made by people named &amp;quot;trolls&amp;quot;. These trolls make fake news and send them to people. On the other side of the table are elfs, who defend people from fake news and send &amp;quot;fake news warnings&amp;quot;. When people receive fake news, they have basicaly three choices: resend it as it is (basicaly become troll), resend it with &amp;quot;fake news warning&amp;quot; (become elf) or dont resend it. Can elfs beat trolls and defend the majority of system from fake news? &lt;br /&gt;
&lt;br /&gt;
'''Possible parameters of simulation'''&lt;br /&gt;
* number of trolls at the start&lt;br /&gt;
* possibility to become a troll (the rest to 1 is posibility to become an elf)&lt;br /&gt;
* troll's number of resends &lt;br /&gt;
* elf's number of resends &lt;br /&gt;
* troll's possibility to resend&lt;br /&gt;
* elf's possibility to resend&lt;br /&gt;
&lt;br /&gt;
* and possibly many more which I cant now think about.&lt;br /&gt;
&lt;br /&gt;
'''Additional idea:'''&lt;br /&gt;
&lt;br /&gt;
Elfs can change to Trolls (and vice versa) in time. It would depend on how many information from who did they receive. For example, if a troll gets after some time more warnings from elfs than fake news from trolls, he become an elf too. &lt;br /&gt;
&lt;br /&gt;
'''Articles about fake news spread'''&lt;br /&gt;
* https://www.nytimes.com/2021/11/22/world/europe/belarus-migrants-facebook-fake-news.html&lt;br /&gt;
* https://semantic-visions.com/resource/defending-the-covid-19-vaccination-pipeline&lt;br /&gt;
* https://www.cits.ucsb.edu/fake-news/spread&lt;br /&gt;
* https://thenextweb.com/news/ai-isnt-going-to-stop-fake-news-syndication&lt;br /&gt;
* https://www.bbc.co.uk/bitesize/articles/z6kxxyc&lt;br /&gt;
* https://ischool.syr.edu/fake-news-why-people-believe-how-it-spreads-and-what-you-can-do-about-it/&lt;br /&gt;
* https://futurism.com/fake-news-study-spread&lt;br /&gt;
&lt;br /&gt;
'''Goals of simulation are answers to these questions:'''&lt;br /&gt;
* How many trolls do you need to get to the majority of people and how many resends they should perform (in average)?&lt;br /&gt;
* How many elfs do we need if there is X number of trolls? And how many resends should elfs do?&lt;br /&gt;
* Where are the boundaries to these numbers?&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Tomáš Martínek (mart13)]] ([[User talk:Mart13|talk]]) 00:42, 13 December 2021 (CET)&lt;br /&gt;
'''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 00:22, 17 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation 3D print==&lt;br /&gt;
&lt;br /&gt;
The simulation would focus on printing a 3D model on a 3D printer. This model would be made of multiple materials, so a 3D printer would need a material storage and a switch between them. Each material needed a different temperature and time to print parts of the model, also each material has a different financial value. At the same time, there is a need to consider providing additional cooling that slows down the print to prevent it from warping. There is also a need to consider the influence of the environment, such as ambient temperature, wind or nozzle clogging.&lt;br /&gt;
&lt;br /&gt;
'''Measurement parameters'''&lt;br /&gt;
* time of making&lt;br /&gt;
* production cost&lt;br /&gt;
* nozzle temperature&lt;br /&gt;
* time between transitions&lt;br /&gt;
* condition of materials&lt;br /&gt;
* etc&lt;br /&gt;
&lt;br /&gt;
''' Goals'''&lt;br /&gt;
* Measure how long it takes for the model to print.&lt;br /&gt;
* What is its financial demands if we take into account the price of the material and the time of its printing.&lt;br /&gt;
* If additional cooling needs to be switched on.&lt;br /&gt;
&lt;br /&gt;
'''Tool'''&lt;br /&gt;
* Simprocess or vensim - advice?&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Ondřej Pišl&lt;br /&gt;
&lt;br /&gt;
:: This is good example for a calculation, but not for a simulation. In case of System Dynamics it should focus on one parameter and its dynamics - for example material consumption. What all parameters it is influenced by, including complexity of the printed model and also probability should also come in (random variables) - print failure, model collapse (and its relation to model complexity). The goal of the simulation then could be a simulation, that will tell the user most probable material consumption for the input given by the user. Modify the proposal in this way and then the Vensim could be the viable way. [[User:Oleg.Svatos|Oleg.Svatos]] ([[User talk:Oleg.Svatos|talk]]) 22:05, 19 December 2021 (CET)&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22240</id>
		<title>Assignments WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22240"/>
		<updated>2021-12-27T08:12:40Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, put here your assignments. Do not forget to sign them. You can use &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; (four tildas) for an automatic signature. Use Show preview in order to check the result before your final sumbition.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, strive to formulate your assignment carefully. We expect an adequate effort to formulate the assignment as it is your semestral paper. Do not forget that your main goal is a research paper. It means your simulation model must generate the results that are specific, measurable and verifiable. Think twice how you will develop your model, which entities you will use, draw a model diagram, consider what you will measure. No sooner than when you have a good idea about the model, submit your assignment. And of course, read [[How to deal with the simulation assignment|How to deal with the simulation assignment]].&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Topics on gambling, cards, etc. are not welcome.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| type  = content&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
In order to avoid possible confusion, please, check if you have added '''approved''' in bold somewhere in our comment under your submission. If there is no '''approved''', it means the assignment was not approved yet.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Spread of covid19 in closed/open area markets ==&lt;br /&gt;
&lt;br /&gt;
In winter 2021 in Czechia the christmas markets were banned due to another covid19 infection wave. On the other hand people are free to go into shopping malls. It would be interesting to use existing data about covid19 virus transmission in agent based simulation to see how many people get infected and in what speed depending on whether they are in a christmas (open) market, or in a shopping mall (closed). The main goal will be to see if the simulation would backup the decision that has been made about christmas markets.&lt;br /&gt;
&lt;br /&gt;
Possible research papers that contain data about covid spreading&lt;br /&gt;
* [https://www.kaggle.com/guidant/covid19-evolution-transmission-spatialpatterns/ Kaggle notebook - Covid19, Evolution, Transmission, Spatial Patterns]&lt;br /&gt;
* [https://link.springer.com/article/10.1007/s10668-020-00884-x/ Research - Understanding COVID-19 transmission, health impacts and mitigation: timely social distancing is the key]&lt;br /&gt;
&lt;br /&gt;
This simulation would be realised using NetLogo.&lt;br /&gt;
&lt;br /&gt;
Summary:&lt;br /&gt;
&lt;br /&gt;
'''WHAT will be simulated'''&lt;br /&gt;
* market place, which can be both open space or closed space.&lt;br /&gt;
* people with or without masks, who will walk from shop to shop, with some intention and some of them will be virus carriers&lt;br /&gt;
* virus, which will spread in places where people go through (depending on the closed/open area, the infection rates will differ)&lt;br /&gt;
&lt;br /&gt;
'''GOAL of the simulation'''&lt;br /&gt;
* answer the question: &amp;quot;Where is the virus spread more significant? At the market place, or at the shopping mall?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Angel Kostov, xkosa20&lt;br /&gt;
&lt;br /&gt;
: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 11:58, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Effects of COVID-19 vaccination on the spread of infection ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Currently, there is a new wave of infection in the COVID-19 pandemic with high number of infections. In Germany, for example, more than 50,000 new infections are currently reported every day. To reduce the infection rate, a wide variety of measures have been implemented. One of these measures are the vaccination and masks. Vaccination can reduce the risk of infection and the likelihood of transmissibility. A simulation is conducted to vividly identify the extent to which vaccination could contain the pandemic.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The purpose of the simulation is to show how COVID-19 vaccination affects the spread of the pandemic. I will use an agent-based model in order to simulate the scenario in a simplified form based on existing scientific data. In addition, current COVID-19 measures are considered.  &lt;br /&gt;
&lt;br /&gt;
Subjects of the simulation: &lt;br /&gt;
&lt;br /&gt;
Environment: &lt;br /&gt;
* A village with around 6.000 inhabitants&lt;br /&gt;
* Simplified: The village is closed that is new people cannot come in and people of the village cannot go out &lt;br /&gt;
&lt;br /&gt;
Agents: &lt;br /&gt;
* Vaccinated persons&lt;br /&gt;
* Unvaccinated persons &lt;br /&gt;
* Simulations with different vaccination rates to compare the different infection courses&lt;br /&gt;
&lt;br /&gt;
Further measures: &lt;br /&gt;
* All people wear masks&lt;br /&gt;
* Nobody wears a mask  &lt;br /&gt;
&lt;br /&gt;
Start: &lt;br /&gt;
* Few agents are unknowingly infected (e.g. 0,1% of the inhabitants = 6 people) &lt;br /&gt;
* Movement of agents intended to reflect the daily behavior of people in real life in a simplified form.&lt;br /&gt;
* One agent can infect another agent with a certain probability if they are close to each other. &lt;br /&gt;
* The probability of an infection depends on the measure (vaccination / mask)&lt;br /&gt;
&lt;br /&gt;
'''Goal:'''&lt;br /&gt;
* Identify the infection course with different vaccination rates and measures. &lt;br /&gt;
* Showing the importance of vaccination.&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Possible data sources'''&lt;br /&gt;
&lt;br /&gt;
https://www.rki.de/SharedDocs/FAQ/COVID-Impfen/FAQ_Liste_Wirksamkeit.html&lt;br /&gt;
&lt;br /&gt;
Chia, P. Y., Xiang Ong, S. W., Chiew, C. J., Ang, L. W., Chavatte, J.-M., Mak, T.-M., Cui, L., Kalimuddin, S., Chia, W. N., Tan, C. W., Ann Chai, L. Y., Tan, S. Y., Zheng, S., Pin Lin, R. T., Wang, L., Leo, Y.-S., Lee, V. J., Lye, D. C., &amp;amp; Young, B. E. (2021). Virological and serological kinetics of SARS-CoV-2 Delta variant vaccine-breakthrough infections: A multi-center cohort study. Clinical Microbiology and Infection, S1198743X21006388. https://doi.org/10.1016/j.cmi.2021.11.010&lt;br /&gt;
&lt;br /&gt;
Eyre, D. W., Taylor, D., Purver, M., Chapman, D., Fowler, T., Pouwels, K., Walker, A. S., &amp;amp; Peto, T. E. (2021). The impact of SARS-CoV-2 vaccination on Alpha and Delta variant transmission [Preprint]. Infectious Diseases (except HIV/AIDS). https://doi.org/10.1101/2021.09.28.21264260&lt;br /&gt;
&lt;br /&gt;
Harder, T., Külper-Schiek, W., Reda, S., Treskova-Schwarzbach, M., Koch, J., Vygen-Bonnet, S., &amp;amp; Wichmann, O. (2021). Effectiveness of COVID-19 vaccines against SARS-CoV-2 infection with the Delta (B.1.617.2) variant: Second interim results of a living systematic review and meta-analysis, 1 January to 25 August 2021. Eurosurveillance, 26(41). https://doi.org/10.2807/1560-7917.ES.2021.26.41.2100920&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Laura Kundmueller&lt;br /&gt;
&lt;br /&gt;
: OK, but, please, elaborate it a bit. How exactly should the simulation look like, kinds of agents, etc. And mainly: the sources of data, etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:00, 10 December 2021 (CET)&lt;br /&gt;
:: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 00:13, 17 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation of genetic algorithm: Travelling Salesman Problem ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The topic of this simulation is an old graph problem, Travelling Salesman Problem. My approach would be based on genetic learning algorithm. A random map will be generated at the start. Salesman is travelling in a car with some gas. The gas is used as he travels, it can be recharged at gas stations but it costs money. The map contains some hills and flat roads, which have a different cost of gas when going through. &lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
* to find the optimum path between the towns.&lt;br /&gt;
&lt;br /&gt;
'''The parameters are:'''&lt;br /&gt;
* number of agents (travelling salesmen)&lt;br /&gt;
* gas in car&lt;br /&gt;
* money&lt;br /&gt;
&lt;br /&gt;
* number of towns&lt;br /&gt;
* number of hills&lt;br /&gt;
* number of gas stations&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Mart13]] ([[User talk:Mart13|talk]]) 09:57, 9 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: Although this isn't a true agent-based simulation, we sometimes accept topics from artificial intelligence and other related fields. However, it is necessary to elaborate it in deep. How exactly the algorithm will work. What is the goal (not the goal of the agent, but the goal of this work)? Etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:03, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: &lt;br /&gt;
Algorithm:&lt;br /&gt;
* Basic genetic learning, gene is a path of an agent. My idea is that every patch of map has a different cost of going through. The agents must decide where to go and in which order.&lt;br /&gt;
* Fitness function is a score of an agent (the score of its path).&lt;br /&gt;
* I would like to implement mutation and crossover.&lt;br /&gt;
&lt;br /&gt;
Additional parameters to those introduced earlier:&lt;br /&gt;
* number of population&lt;br /&gt;
* number of mutations&lt;br /&gt;
* number of crossovers&lt;br /&gt;
&lt;br /&gt;
Goal of work:&lt;br /&gt;
* graphical interpretation of AI learning&lt;br /&gt;
&lt;br /&gt;
[[User:Mart13|Tomáš Martínek (mart13)]] ([[User talk:Mart13|talk]]) 11:49, 11 December 2021 (CET)&lt;br /&gt;
: '''Approved'''&lt;br /&gt;
&lt;br /&gt;
== Optimizing the process of baking wedding sweets ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
There is a wedding tradition in Czech Republic of baking wedding sweets and then handing them out to the guests of the weeding as a form of invitation. Process of baking usually takes whole day and several helpers in the kitchen are needed. Into paper baskets are usually packaged two types of sweets: several small ones with 3 different flavours and one so-called &amp;quot;rohový koláč&amp;quot;. Which are then delivered by the bride to wedding guests. For the purpose of this simulation are process and needed ingredients simplified.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
The goal is to optimize the number of helpers in the kitchen and find optimal amount of basic ingredients for specified number of guests.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Discrete simulation - SIMPROCESS&lt;br /&gt;
&lt;br /&gt;
'''Entities:'''&lt;br /&gt;
* sweets&lt;br /&gt;
* paper baskets&lt;br /&gt;
* baking trays&lt;br /&gt;
&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* pastry-cooks&lt;br /&gt;
* bride&lt;br /&gt;
* flour&lt;br /&gt;
* sugar&lt;br /&gt;
* curd&lt;br /&gt;
* plum jam&lt;br /&gt;
* poppy seed filling&lt;br /&gt;
&lt;br /&gt;
'''Process steps'''&lt;br /&gt;
* order for paper basket&lt;br /&gt;
* preparing sweets: small ones (3 different flavours), &amp;quot;rohove kolače&amp;quot; sweets (using all flavours)&lt;br /&gt;
* baking in the oven&lt;br /&gt;
* sugar coating&lt;br /&gt;
* packaging&lt;br /&gt;
* delivery&lt;br /&gt;
&lt;br /&gt;
'''Data:'''&lt;br /&gt;
* https://www.svetsvateb.cz/2021/02/623262-svatebni-kolacky/&lt;br /&gt;
* https://megvkuchyni.cz/recepty/speciality/svatebni-special-jak-na-svatebni-kolacky/&lt;br /&gt;
* experience&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 10:16, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: OK, maybe. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:05, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Carsharing company fleet optimization ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Recently, carsharing becomes more and more popular in large cities. Short-term rental (from several minutes to 24 hours) of a car with possibility to drop it anywhere in the allowed area in the city attracts people who for some reasons do not want to use their own vehicles. However, it is not always convenient. If the fleet is relatively small, the probability that a car will be somewhere close by is also quite low. Cars also must be refueled or recharged sometimes by external staff, which would increase cost of the fleet maintenance with increasing of the fleet size.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The proposing agent-based simulation will reproduce real situation with shared cars.&lt;br /&gt;
Two types of agents are planned:&lt;br /&gt;
* cars with different states (waiting, in rent, maintenance) and characteristics (mileage, fuel level)&lt;br /&gt;
* drivers - users of the service, who rent the cars and have their own behavior, including decision making on taking a car, driving style, and so on.&lt;br /&gt;
Some data for the model will be obtained as personal observations of two carsharing services operating in Prague, [https://anytimecar.cz/ Anytime] and [https://www.uniqway.cz/ Uniqway] (for example, number of available cars, which is visible in mobile applications). Another source of data would be statistics collected by other services abroad, for example, by operating in Russia service Yandex.Drive[https://www.statista.com/statistics/1224178/daily-use-duration-of-car-sharing-vehicles-in-moscow-by-vehicle-type/].&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
to find out optimal fleet size and structure and price policy to maximize revenue of a carsharing company.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Shcs00|Sergei Shcherbinin (shcs00)]] ([[User talk:Shcs00|talk]]) 12:34, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: I like the idea. Please, do not hesitate to contact the companies directly for the data. They are sometimes willing to help if you require just general, non sensitive data. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:08, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How long would it take to find love ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There is such thing as Drake formula used to calculate a chanse to meet an alien https://en.wikipedia.org/wiki/Drake_equation&lt;br /&gt;
Also there is an article https://e-lub.net/annuals/why.htm - to sum up, it is Drakes formula used to calculate a chance to meet a love of your life in London&lt;br /&gt;
&lt;br /&gt;
So What I want to do is to let user enter some parameters of what he/she thinks the perfect person is and based on the entered parameters we will see how long would it take to meet a perfect person in a city (say, Prague).&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Data about the city would be taken from official sources (might be Eurostat or some other data that is gathered by Czech statistical office)&lt;br /&gt;
User will enter all the parameters and then see when will he meet a person. &lt;br /&gt;
Of course for the sake of achievability some things will be simplified. For example I don't think I will actualy add millions of agents, Maybe hundreds would be enough.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
To see how year passes after year and love is still not found:) Or maybe to understand that lowering the expectations could correspond to finding a love faster&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo or AnyLogic&lt;br /&gt;
&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;br /&gt;
&lt;br /&gt;
: To be honest, althought it is a funny idea, the problem, in fact, is verification. You would deal with soft properties and attitudes, nothing what could be measured. Even the article wasn't apparently meant to be serious.&lt;br /&gt;
: Please, try finding something else. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 19:17, 17 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;UPD:&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
== Sample size for a/b test ==&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There are different approaches on how to calculate sample size for A/B test when measuring difference in means for treatment and control group:&lt;br /&gt;
1 Calculation through power of a test&lt;br /&gt;
2 Rule of thumb for power of a test: https://stats.stackexchange.com/questions/11131/sample-size-formula-for-an-f-test &lt;br /&gt;
3 some other formula https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2876926/&lt;br /&gt;
4 Formula derived from confidence interval https://sphweb.bumc.bu.edu/otlt/mph-modules/bs/bs704_confidence_intervals/bs704_confidence_intervals5.html&lt;br /&gt;
&lt;br /&gt;
And I think there should be more. They give different results&lt;br /&gt;
&lt;br /&gt;
Another problem is in type 1, type 2 error: researcher cannot always detect the difference or can detect the difference where there is no difference.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Simulate an A/B test, set distribution parameters for control and treatment groups, calculate sample sizes based on formulas and understand which approach is correct and how often it can be used.&lt;br /&gt;
Illustrate real chances of type 1 and type 2 errors.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
Pick the best method for calculation of sample size.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Python, monte-carlo&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;br /&gt;
&lt;br /&gt;
== Scooter rental ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Today in almost each big city you can find a huge number of scooter which can be rented. The main feature of scooter rental is that you can take it at one point in the city and return it to another when you finish your route.&lt;br /&gt;
If there is no scooter nearby, then obviously a potential client will not take it. In addition, people prefer to ride with friends, so the likelihood of renting a scooter is higher if there are several of them at one point.&lt;br /&gt;
The more scooters there are in the city, the more chances that people will use this service, however, scooter support also requires additional resources and extra costs.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The goal of agent-based simulation is to define optimal number of scooters for specific city and its destribution within the city to maximize income of the company.&lt;br /&gt;
Two types of agents will be used:&lt;br /&gt;
*scooters with a list of states (rented, broken, available, available + near other scooters) and characteristics such as, for example, charge level.&lt;br /&gt;
*clients with different characteristics (for example, alone, with friend, maximal suitable distance to a scooter)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Agent-based simulation in NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:liudmila_kalashnikova| Liudmila Kalashnikova (liudmila_kalashnikova)]]&lt;br /&gt;
&lt;br /&gt;
'''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 00:24, 17 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Is it possible to stop fake news? ==&lt;br /&gt;
&lt;br /&gt;
Fake news is a global problem and it is getting worse every year. Is it possible to stop fake news? Fake news are made by people named &amp;quot;trolls&amp;quot;. These trolls make fake news and send them to people. On the other side of the table are elfs, who defend people from fake news and send &amp;quot;fake news warnings&amp;quot;. When people receive fake news, they have basicaly three choices: resend it as it is (basicaly become troll), resend it with &amp;quot;fake news warning&amp;quot; (become elf) or dont resend it. Can elfs beat trolls and defend the majority of system from fake news? &lt;br /&gt;
&lt;br /&gt;
'''Possible parameters of simulation'''&lt;br /&gt;
* number of trolls at the start&lt;br /&gt;
* possibility to become a troll (the rest to 1 is posibility to become an elf)&lt;br /&gt;
* troll's number of resends &lt;br /&gt;
* elf's number of resends &lt;br /&gt;
* troll's possibility to resend&lt;br /&gt;
* elf's possibility to resend&lt;br /&gt;
&lt;br /&gt;
* and possibly many more which I cant now think about.&lt;br /&gt;
&lt;br /&gt;
'''Additional idea:'''&lt;br /&gt;
&lt;br /&gt;
Elfs can change to Trolls (and vice versa) in time. It would depend on how many information from who did they receive. For example, if a troll gets after some time more warnings from elfs than fake news from trolls, he become an elf too. &lt;br /&gt;
&lt;br /&gt;
'''Articles about fake news spread'''&lt;br /&gt;
* https://www.nytimes.com/2021/11/22/world/europe/belarus-migrants-facebook-fake-news.html&lt;br /&gt;
* https://semantic-visions.com/resource/defending-the-covid-19-vaccination-pipeline&lt;br /&gt;
* https://www.cits.ucsb.edu/fake-news/spread&lt;br /&gt;
* https://thenextweb.com/news/ai-isnt-going-to-stop-fake-news-syndication&lt;br /&gt;
* https://www.bbc.co.uk/bitesize/articles/z6kxxyc&lt;br /&gt;
* https://ischool.syr.edu/fake-news-why-people-believe-how-it-spreads-and-what-you-can-do-about-it/&lt;br /&gt;
* https://futurism.com/fake-news-study-spread&lt;br /&gt;
&lt;br /&gt;
'''Goals of simulation are answers to these questions:'''&lt;br /&gt;
* How many trolls do you need to get to the majority of people and how many resends they should perform (in average)?&lt;br /&gt;
* How many elfs do we need if there is X number of trolls? And how many resends should elfs do?&lt;br /&gt;
* Where are the boundaries to these numbers?&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Tomáš Martínek (mart13)]] ([[User talk:Mart13|talk]]) 00:42, 13 December 2021 (CET)&lt;br /&gt;
'''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 00:22, 17 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation 3D print==&lt;br /&gt;
&lt;br /&gt;
The simulation would focus on printing a 3D model on a 3D printer. This model would be made of multiple materials, so a 3D printer would need a material storage and a switch between them. Each material needed a different temperature and time to print parts of the model, also each material has a different financial value. At the same time, there is a need to consider providing additional cooling that slows down the print to prevent it from warping. There is also a need to consider the influence of the environment, such as ambient temperature, wind or nozzle clogging.&lt;br /&gt;
&lt;br /&gt;
'''Measurement parameters'''&lt;br /&gt;
* time of making&lt;br /&gt;
* production cost&lt;br /&gt;
* nozzle temperature&lt;br /&gt;
* time between transitions&lt;br /&gt;
* condition of materials&lt;br /&gt;
* etc&lt;br /&gt;
&lt;br /&gt;
''' Goals'''&lt;br /&gt;
* Measure how long it takes for the model to print.&lt;br /&gt;
* What is its financial demands if we take into account the price of the material and the time of its printing.&lt;br /&gt;
* If additional cooling needs to be switched on.&lt;br /&gt;
&lt;br /&gt;
'''Tool'''&lt;br /&gt;
* Simprocess or vensim - advice?&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Ondřej Pišl&lt;br /&gt;
&lt;br /&gt;
:: This is good example for a calculation, but not for a simulation. In case of System Dynamics it should focus on one parameter and its dynamics - for example material consumption. What all parameters it is influenced by, including complexity of the printed model and also probability should also come in (random variables) - print failure, model collapse (and its relation to model complexity). The goal of the simulation then could be a simulation, that will tell the user most probable material consumption for the input given by the user. Modify the proposal in this way and then the Vensim could be the viable way. [[User:Oleg.Svatos|Oleg.Svatos]] ([[User talk:Oleg.Svatos|talk]]) 22:05, 19 December 2021 (CET)&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22205</id>
		<title>Assignments WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22205"/>
		<updated>2021-12-12T12:53:05Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, put here your assignments. Do not forget to sign them. You can use &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; (four tildas) for an automatic signature. Use Show preview in order to check the result before your final sumbition.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, strive to formulate your assignment carefully. We expect an adequate effort to formulate the assignment as it is your semestral paper. Do not forget that your main goal is a research paper. It means your simulation model must generate the results that are specific, measurable and verifiable. Think twice how you will develop your model, which entities you will use, draw a model diagram, consider what you will measure. No sooner than when you have a good idea about the model, submit your assignment. And of course, read [[How to deal with the simulation assignment|How to deal with the simulation assignment]].&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Topics on gambling, cards, etc. are not welcome.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| type  = content&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
In order to avoid possible confusion, please, check if you have added '''approved''' in bold somewhere in our comment under your submission. If there is no '''approved''', it means the assignment was not approved yet.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Spread of covid19 in closed/open area markets ==&lt;br /&gt;
&lt;br /&gt;
In winter 2021 in Czechia the christmas markets were banned due to another covid19 infection wave. On the other hand people are free to go into shopping malls. It would be interesting to use existing data about covid19 virus transmission in agent based simulation to see how many people get infected and in what speed depending on whether they are in a christmas (open) market, or in a shopping mall (closed). The main goal will be to see if the simulation would backup the decision that has been made about christmas markets.&lt;br /&gt;
&lt;br /&gt;
Possible research papers that contain data about covid spreading&lt;br /&gt;
* [https://www.kaggle.com/guidant/covid19-evolution-transmission-spatialpatterns/ Kaggle notebook - Covid19, Evolution, Transmission, Spatial Patterns]&lt;br /&gt;
* [https://link.springer.com/article/10.1007/s10668-020-00884-x/ Research - Understanding COVID-19 transmission, health impacts and mitigation: timely social distancing is the key]&lt;br /&gt;
&lt;br /&gt;
This simulation would be realised using NetLogo.&lt;br /&gt;
&lt;br /&gt;
Summary:&lt;br /&gt;
&lt;br /&gt;
'''WHAT will be simulated'''&lt;br /&gt;
* market place, which can be both open space or closed space.&lt;br /&gt;
* people with or without masks, who will walk from shop to shop, with some intention and some of them will be virus carriers&lt;br /&gt;
* virus, which will spread in places where people go through (depending on the closed/open area, the infection rates will differ)&lt;br /&gt;
&lt;br /&gt;
'''GOAL of the simulation'''&lt;br /&gt;
* answer the question: &amp;quot;Where is the virus spread more significant? At the market place, or at the shopping mall?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Angel Kostov, xkosa20&lt;br /&gt;
&lt;br /&gt;
: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 11:58, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Effects of COVID-19 vaccination on the spread of infection ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Currently, there is a new wave of infection in the COVID-19 pandemic with high number of infections. In Germany, for example, more than 50,000 new infections are currently reported every day. To reduce the infection rate, a wide variety of measures have been implemented. One of these measures are the vaccination and masks. Vaccination can reduce the risk of infection and the likelihood of transmissibility. A simulation is conducted to vividly identify the extent to which vaccination could contain the pandemic.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The purpose of the simulation is to show how COVID-19 vaccination affects the spread of the pandemic. I will use an agent-based model in order to simulate the scenario in a simplified form based on existing scientific data. In addition, current COVID-19 measures are considered.  &lt;br /&gt;
&lt;br /&gt;
Subjects of the simulation: &lt;br /&gt;
&lt;br /&gt;
Environment: &lt;br /&gt;
* A village with around 6.000 inhabitants&lt;br /&gt;
* Simplified: The village is closed that is new people cannot come in and people of the village cannot go out &lt;br /&gt;
&lt;br /&gt;
Agents: &lt;br /&gt;
* Vaccinated persons&lt;br /&gt;
* Unvaccinated persons &lt;br /&gt;
* Simulations with different vaccination rates to compare the different infection courses&lt;br /&gt;
&lt;br /&gt;
Further measures: &lt;br /&gt;
* All people wear masks&lt;br /&gt;
* Nobody wears a mask  &lt;br /&gt;
&lt;br /&gt;
Start: &lt;br /&gt;
* Few agents are unknowingly infected (e.g. 0,1% of the inhabitants = 6 people) &lt;br /&gt;
* Movement of agents intended to reflect the daily behavior of people in real life in a simplified form.&lt;br /&gt;
* One agent can infect another agent with a certain probability if they are close to each other. &lt;br /&gt;
* The probability of an infection depends on the measure (vaccination / mask)&lt;br /&gt;
&lt;br /&gt;
'''Goal:'''&lt;br /&gt;
* Identify the infection course with different vaccination rates and measures. &lt;br /&gt;
* Showing the importance of vaccination.&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Possible data sources'''&lt;br /&gt;
&lt;br /&gt;
https://www.rki.de/SharedDocs/FAQ/COVID-Impfen/FAQ_Liste_Wirksamkeit.html&lt;br /&gt;
&lt;br /&gt;
Chia, P. Y., Xiang Ong, S. W., Chiew, C. J., Ang, L. W., Chavatte, J.-M., Mak, T.-M., Cui, L., Kalimuddin, S., Chia, W. N., Tan, C. W., Ann Chai, L. Y., Tan, S. Y., Zheng, S., Pin Lin, R. T., Wang, L., Leo, Y.-S., Lee, V. J., Lye, D. C., &amp;amp; Young, B. E. (2021). Virological and serological kinetics of SARS-CoV-2 Delta variant vaccine-breakthrough infections: A multi-center cohort study. Clinical Microbiology and Infection, S1198743X21006388. https://doi.org/10.1016/j.cmi.2021.11.010&lt;br /&gt;
&lt;br /&gt;
Eyre, D. W., Taylor, D., Purver, M., Chapman, D., Fowler, T., Pouwels, K., Walker, A. S., &amp;amp; Peto, T. E. (2021). The impact of SARS-CoV-2 vaccination on Alpha and Delta variant transmission [Preprint]. Infectious Diseases (except HIV/AIDS). https://doi.org/10.1101/2021.09.28.21264260&lt;br /&gt;
&lt;br /&gt;
Harder, T., Külper-Schiek, W., Reda, S., Treskova-Schwarzbach, M., Koch, J., Vygen-Bonnet, S., &amp;amp; Wichmann, O. (2021). Effectiveness of COVID-19 vaccines against SARS-CoV-2 infection with the Delta (B.1.617.2) variant: Second interim results of a living systematic review and meta-analysis, 1 January to 25 August 2021. Eurosurveillance, 26(41). https://doi.org/10.2807/1560-7917.ES.2021.26.41.2100920&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Laura Kundmueller&lt;br /&gt;
&lt;br /&gt;
: OK, but, please, elaborate it a bit. How exactly should the simulation look like, kinds of agents, etc. And mainly: the sources of data, etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:00, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation of genetic algorithm: Travelling Salesman Problem ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The topic of this simulation is an old graph problem, Travelling Salesman Problem. My approach would be based on genetic learning algorithm. A random map will be generated at the start. Salesman is travelling in a car with some gas. The gas is used as he travels, it can be recharged at gas stations but it costs money. The map contains some hills and flat roads, which have a different cost of gas when going through. &lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
* to find the optimum path between the towns.&lt;br /&gt;
&lt;br /&gt;
'''The parameters are:'''&lt;br /&gt;
* number of agents (travelling salesmen)&lt;br /&gt;
* gas in car&lt;br /&gt;
* money&lt;br /&gt;
&lt;br /&gt;
* number of towns&lt;br /&gt;
* number of hills&lt;br /&gt;
* number of gas stations&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Mart13]] ([[User talk:Mart13|talk]]) 09:57, 9 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: Although this isn't a true agent-based simulation, we sometimes accept topics from artificial intelligence and other related fields. However, it is necessary to elaborate it in deep. How exactly the algorithm will work. What is the goal (not the goal of the agent, but the goal of this work)? Etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:03, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: &lt;br /&gt;
Algorithm:&lt;br /&gt;
* Basic genetic learning, gene is a path of an agent. My idea is that every patch of map has a different cost of going through. The agents must decide where to go and in which order.&lt;br /&gt;
* Fitness function is a score of an agent (the score of its path).&lt;br /&gt;
* I would like to implement mutation and crossover.&lt;br /&gt;
&lt;br /&gt;
Additional parameters to those introduced earlier:&lt;br /&gt;
* number of population&lt;br /&gt;
* number of mutations&lt;br /&gt;
* number of crossovers&lt;br /&gt;
&lt;br /&gt;
Goal of work:&lt;br /&gt;
* graphical interpretation of AI learning&lt;br /&gt;
&lt;br /&gt;
[[User:Mart13|Tomáš Martínek (mart13)]] ([[User talk:Mart13|talk]]) 11:49, 11 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Optimizing the process of baking wedding sweets ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
There is a wedding tradition in Czech Republic of baking wedding sweets and then handing them out to the guests of the weeding as a form of invitation. Process of baking usually takes whole day and several helpers in the kitchen are needed. Into paper baskets are usually packaged two types of sweets: several small ones with 3 different flavours and one so-called &amp;quot;rohový koláč&amp;quot;. Which are then delivered by the bride to wedding guests. For the purpose of this simulation are process and needed ingredients simplified.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
The goal is to optimize the number of helpers in the kitchen and find optimal amount of basic ingredients for specified number of guests.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Discrete simulation - SIMPROCESS&lt;br /&gt;
&lt;br /&gt;
'''Entities:'''&lt;br /&gt;
* sweets&lt;br /&gt;
* paper baskets&lt;br /&gt;
* baking trays&lt;br /&gt;
&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* pastry-cooks&lt;br /&gt;
* bride&lt;br /&gt;
* flour&lt;br /&gt;
* sugar&lt;br /&gt;
* curd&lt;br /&gt;
* plum jam&lt;br /&gt;
* poppy seed filling&lt;br /&gt;
&lt;br /&gt;
'''Process steps'''&lt;br /&gt;
* order for paper basket&lt;br /&gt;
* preparing sweets: small ones (3 different flavours), &amp;quot;rohove kolače&amp;quot; sweets (using all flavours)&lt;br /&gt;
* baking in the oven&lt;br /&gt;
* sugar coating&lt;br /&gt;
* packaging&lt;br /&gt;
* delivery&lt;br /&gt;
&lt;br /&gt;
'''Data:'''&lt;br /&gt;
* https://www.svetsvateb.cz/2021/02/623262-svatebni-kolacky/&lt;br /&gt;
* https://megvkuchyni.cz/recepty/speciality/svatebni-special-jak-na-svatebni-kolacky/&lt;br /&gt;
* experience&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 10:16, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: OK, maybe. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:05, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Carsharing company fleet optimization ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Recently, carsharing becomes more and more popular in large cities. Short-term rental (from several minutes to 24 hours) of a car with possibility to drop it anywhere in the allowed area in the city attracts people who for some reasons do not want to use their own vehicles. However, it is not always convenient. If the fleet is relatively small, the probability that a car will be somewhere close by is also quite low. Cars also must be refueled or recharged sometimes by external staff, which would increase cost of the fleet maintenance with increasing of the fleet size.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The proposing agent-based simulation will reproduce real situation with shared cars.&lt;br /&gt;
Two types of agents are planned:&lt;br /&gt;
* cars with different states (waiting, in rent, maintenance) and characteristics (mileage, fuel level)&lt;br /&gt;
* drivers - users of the service, who rent the cars and have their own behavior, including decision making on taking a car, driving style, and so on.&lt;br /&gt;
Some data for the model will be obtained as personal observations of two carsharing services operating in Prague, [https://anytimecar.cz/ Anytime] and [https://www.uniqway.cz/ Uniqway] (for example, number of available cars, which is visible in mobile applications). Another source of data would be statistics collected by other services abroad, for example, by operating in Russia service Yandex.Drive[https://www.statista.com/statistics/1224178/daily-use-duration-of-car-sharing-vehicles-in-moscow-by-vehicle-type/].&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
to find out optimal fleet size and structure and price policy to maximize revenue of a carsharing company.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Shcs00|Sergei Shcherbinin (shcs00)]] ([[User talk:Shcs00|talk]]) 12:34, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: I like the idea. Please, do not hesitate to contact the companies directly for the data. They are sometimes willing to help if you require just general, non sensitive data. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:08, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How long would it take to find love ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There is such thing as Drake formula used to calculate a chanse to meet an alien https://en.wikipedia.org/wiki/Drake_equation&lt;br /&gt;
Also there is an article https://e-lub.net/annuals/why.htm - to sum up, it is Drakes formula used to calculate a chance to meet a love of your life in London&lt;br /&gt;
&lt;br /&gt;
So What I want to do is to let user enter some parameters of what he/she thinks the perfect person is and based on the entered parameters we will see how long would it take to meet a perfect person in a city (say, Prague).&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Data about the city would be taken from official sources (might be Eurostat or some other data that is gathered by Czech statistical office)&lt;br /&gt;
User will enter all the parameters and then see when will he meet a person. &lt;br /&gt;
Of course for the sake of achievability some things will be simplified. For example I don't think I will actualy add millions of agents, Maybe hundreds would be enough.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
To see how year passes after year and love is still not found:) Or maybe to understand that lowering the expectations could correspond to finding a love faster&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo or AnyLogic&lt;br /&gt;
&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;br /&gt;
&lt;br /&gt;
== Scooter rental ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Today in almost each big city you can find a huge number of scooter which can be rented. The main feature of scooter rental is that you can take it at one point in the city and return it to another when you finish your route.&lt;br /&gt;
If there is no scooter nearby, then obviously a potential client will not take it. In addition, people prefer to ride with friends, so the likelihood of renting a scooter is higher if there are several of them at one point.&lt;br /&gt;
The more scooters there are in the city, the more chances that people will use this service, however, scooter support also requires additional resources and extra costs.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The goal of agent-based simulation is to define optimal number of scooters for specific city and its destribution within the city to maximize income of the company.&lt;br /&gt;
Two types of agents will be used:&lt;br /&gt;
*scooters with a list of states (rented, broken, available, available + near other scooters) and characteristics such as, for example, charge level.&lt;br /&gt;
*clients with different characteristics (for example, alone, with friend, maximal suitable distance to a scooter)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Agent-based simulation in NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:liudmila_kalashnikova| Liudmila Kalashnikova (liudmila_kalashnikova)]]&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22200</id>
		<title>Assignments WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22200"/>
		<updated>2021-12-10T18:37:21Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: /* How long would it take to find love */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, put here your assignments. Do not forget to sign them. You can use &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; (four tildas) for an automatic signature. Use Show preview in order to check the result before your final sumbition.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, strive to formulate your assignment carefully. We expect an adequate effort to formulate the assignment as it is your semestral paper. Do not forget that your main goal is a research paper. It means your simulation model must generate the results that are specific, measurable and verifiable. Think twice how you will develop your model, which entities you will use, draw a model diagram, consider what you will measure. No sooner than when you have a good idea about the model, submit your assignment. And of course, read [[How to deal with the simulation assignment|How to deal with the simulation assignment]].&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Topics on gambling, cards, etc. are not welcome.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| type  = content&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
In order to avoid possible confusion, please, check if you have added '''approved''' in bold somewhere in our comment under your submission. If there is no '''approved''', it means the assignment was not approved yet.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Spread of covid19 in closed/open area markets ==&lt;br /&gt;
&lt;br /&gt;
In winter 2021 in Czechia the christmas markets were banned due to another covid19 infection wave. On the other hand people are free to go into shopping malls. It would be interesting to use existing data about covid19 virus transmission in agent based simulation to see how many people get infected and in what speed depending on whether they are in a christmas (open) market, or in a shopping mall (closed). The main goal will be to see if the simulation would backup the decision that has been made about christmas markets.&lt;br /&gt;
&lt;br /&gt;
Possible research papers that contain data about covid spreading&lt;br /&gt;
* [https://www.kaggle.com/guidant/covid19-evolution-transmission-spatialpatterns/ Kaggle notebook - Covid19, Evolution, Transmission, Spatial Patterns]&lt;br /&gt;
* [https://link.springer.com/article/10.1007/s10668-020-00884-x/ Research - Understanding COVID-19 transmission, health impacts and mitigation: timely social distancing is the key]&lt;br /&gt;
&lt;br /&gt;
This simulation would be realised using NetLogo.&lt;br /&gt;
&lt;br /&gt;
Summary:&lt;br /&gt;
&lt;br /&gt;
'''WHAT will be simulated'''&lt;br /&gt;
* market place, which can be both open space or closed space.&lt;br /&gt;
* people with or without masks, who will walk from shop to shop, with some intention and some of them will be virus carriers&lt;br /&gt;
* virus, which will spread in places where people go through (depending on the closed/open area, the infection rates will differ)&lt;br /&gt;
&lt;br /&gt;
'''GOAL of the simulation'''&lt;br /&gt;
* answer the question: &amp;quot;Where is the virus spread more significant? At the market place, or at the shopping mall?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Angel Kostov, xkosa20&lt;br /&gt;
&lt;br /&gt;
: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 11:58, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Effects of COVID-19 vaccination on the spread of infection ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Currently, there is a new wave of infection in the COVID-19 pandemic with high number of infections. In Germany, for example, more than 50,000 new infections are currently reported every day. To reduce the infection rate, a wide variety of measures have been implemented. One of these measures are the vaccination and masks. Vaccination can reduce the risk of infection and the likelihood of transmissibility. A simulation is conducted to vividly identify the extent to which vaccination could contain the pandemic.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The purpose of the simulation is to show how COVID-19 vaccination affects the spread of the pandemic. I will use an agent-based model in order to simulate the scenario in a simplified form based on existing scientific data. In addition, current COVID-19 measures are considered.  &lt;br /&gt;
&lt;br /&gt;
Subjects of the simulation: &lt;br /&gt;
&lt;br /&gt;
Environment: &lt;br /&gt;
* A village with around 6.000 inhabitants&lt;br /&gt;
* Simplified: The village is closed that is new people cannot come in and people of the village cannot go out &lt;br /&gt;
&lt;br /&gt;
Agents: &lt;br /&gt;
* Vaccinated persons&lt;br /&gt;
* Unvaccinated persons &lt;br /&gt;
* Simulations with different vaccination rates to compare the different infection courses&lt;br /&gt;
&lt;br /&gt;
Further measures: &lt;br /&gt;
* All people wear masks&lt;br /&gt;
* Nobody wears a mask  &lt;br /&gt;
&lt;br /&gt;
Start: &lt;br /&gt;
* Few agents are unknowingly infected (e.g. 0,1% of the inhabitants = 6 people) &lt;br /&gt;
* Movement of agents intended to reflect the daily behavior of people in real life in a simplified form.&lt;br /&gt;
* One agent can infect another agent with a certain probability if they are close to each other. &lt;br /&gt;
* The probability of an infection depends on the measure (vaccination / mask)&lt;br /&gt;
&lt;br /&gt;
'''Goal:'''&lt;br /&gt;
* Identify the infection course with different vaccination rates and measures. &lt;br /&gt;
* Showing the importance of vaccination.&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Possible data sources'''&lt;br /&gt;
&lt;br /&gt;
https://www.rki.de/SharedDocs/FAQ/COVID-Impfen/FAQ_Liste_Wirksamkeit.html&lt;br /&gt;
&lt;br /&gt;
Chia, P. Y., Xiang Ong, S. W., Chiew, C. J., Ang, L. W., Chavatte, J.-M., Mak, T.-M., Cui, L., Kalimuddin, S., Chia, W. N., Tan, C. W., Ann Chai, L. Y., Tan, S. Y., Zheng, S., Pin Lin, R. T., Wang, L., Leo, Y.-S., Lee, V. J., Lye, D. C., &amp;amp; Young, B. E. (2021). Virological and serological kinetics of SARS-CoV-2 Delta variant vaccine-breakthrough infections: A multi-center cohort study. Clinical Microbiology and Infection, S1198743X21006388. https://doi.org/10.1016/j.cmi.2021.11.010&lt;br /&gt;
&lt;br /&gt;
Eyre, D. W., Taylor, D., Purver, M., Chapman, D., Fowler, T., Pouwels, K., Walker, A. S., &amp;amp; Peto, T. E. (2021). The impact of SARS-CoV-2 vaccination on Alpha and Delta variant transmission [Preprint]. Infectious Diseases (except HIV/AIDS). https://doi.org/10.1101/2021.09.28.21264260&lt;br /&gt;
&lt;br /&gt;
Harder, T., Külper-Schiek, W., Reda, S., Treskova-Schwarzbach, M., Koch, J., Vygen-Bonnet, S., &amp;amp; Wichmann, O. (2021). Effectiveness of COVID-19 vaccines against SARS-CoV-2 infection with the Delta (B.1.617.2) variant: Second interim results of a living systematic review and meta-analysis, 1 January to 25 August 2021. Eurosurveillance, 26(41). https://doi.org/10.2807/1560-7917.ES.2021.26.41.2100920&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Laura Kundmueller&lt;br /&gt;
&lt;br /&gt;
: OK, but, please, elaborate it a bit. How exactly should the simulation look like, kinds of agents, etc. And mainly: the sources of data, etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:00, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation of genetic algorithm: Travelling Salesman Problem ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The topic of this simulation is an old graph problem, Travelling Salesman Problem. My approach would be based on genetic learning algorithm. A random map will be generated at the start. Salesman is travelling in a car with some gas. The gas is used as he travels, it can be recharged at gas stations but it costs money. The map contains some hills and flat roads, which have a different cost of gas when going through. &lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
* to find the optimum path between the towns.&lt;br /&gt;
&lt;br /&gt;
'''The parameters are:'''&lt;br /&gt;
* number of agents (travelling salesmen)&lt;br /&gt;
* gas in car&lt;br /&gt;
* money&lt;br /&gt;
&lt;br /&gt;
* number of towns&lt;br /&gt;
* number of hills&lt;br /&gt;
* number of gas stations&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Mart13]] ([[User talk:Mart13|talk]]) 09:57, 9 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: Although this isn't a true agent-based simulation, we sometimes accept topics from artificial intelligence and other related fields. However, it is necessary to elaborate it in deep. How exactly the algorithm will work. What is the goal (not the goal of the agent, but the goal of this work)? Etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:03, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Optimizing the process of baking wedding sweets ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
There is a wedding tradition in Czech Republic of baking wedding sweets and then handing them out to the guests of the weeding as a form of invitation. Process of baking usually takes whole day and several helpers in the kitchen are needed. Into paper baskets are usually packaged two types of sweets: several small ones with 3 different flavours and one so-called &amp;quot;rohový koláč&amp;quot;. Which are then delivered by the bride to wedding guests. For the purpose of this simulation are process and needed ingredients simplified.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
The goal is to optimize the number of helpers in the kitchen and find optimal amount of basic ingredients for specified number of guests.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Discrete simulation - SIMPROCESS&lt;br /&gt;
&lt;br /&gt;
'''Entities:'''&lt;br /&gt;
* sweets&lt;br /&gt;
* paper baskets&lt;br /&gt;
* baking trays&lt;br /&gt;
&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* pastry-cooks&lt;br /&gt;
* bride&lt;br /&gt;
* flour&lt;br /&gt;
* sugar&lt;br /&gt;
* curd&lt;br /&gt;
* plum jam&lt;br /&gt;
* poppy seed filling&lt;br /&gt;
&lt;br /&gt;
'''Process steps'''&lt;br /&gt;
* order for paper basket&lt;br /&gt;
* preparing sweets: small ones (3 different flavours), &amp;quot;rohove kolače&amp;quot; sweets (using all flavours)&lt;br /&gt;
* baking in the oven&lt;br /&gt;
* sugar coating&lt;br /&gt;
* packaging&lt;br /&gt;
* delivery&lt;br /&gt;
&lt;br /&gt;
'''Data:'''&lt;br /&gt;
* https://www.svetsvateb.cz/2021/02/623262-svatebni-kolacky/&lt;br /&gt;
* https://megvkuchyni.cz/recepty/speciality/svatebni-special-jak-na-svatebni-kolacky/&lt;br /&gt;
* experience&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 10:16, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: OK, maybe. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:05, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Carsharing company fleet optimization ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Recently, carsharing becomes more and more popular in large cities. Short-term rental (from several minutes to 24 hours) of a car with possibility to drop it anywhere in the allowed area in the city attracts people who for some reasons do not want to use their own vehicles. However, it is not always convenient. If the fleet is relatively small, the probability that a car will be somewhere close by is also quite low. Cars also must be refueled or recharged sometimes by external staff, which would increase cost of the fleet maintenance with increasing of the fleet size.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The proposing agent-based simulation will reproduce real situation with shared cars.&lt;br /&gt;
Two types of agents are planned:&lt;br /&gt;
* cars with different states (waiting, in rent, maintenance) and characteristics (mileage, fuel level)&lt;br /&gt;
* drivers - users of the service, who rent the cars and have their own behavior, including decision making on taking a car, driving style, and so on.&lt;br /&gt;
Some data for the model will be obtained as personal observations of two carsharing services operating in Prague, [https://anytimecar.cz/ Anytime] and [https://www.uniqway.cz/ Uniqway] (for example, number of available cars, which is visible in mobile applications). Another source of data would be statistics collected by other services abroad, for example, by operating in Russia service Yandex.Drive[https://www.statista.com/statistics/1224178/daily-use-duration-of-car-sharing-vehicles-in-moscow-by-vehicle-type/].&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
to find out optimal fleet size and structure and price policy to maximize revenue of a carsharing company.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Shcs00|Sergei Shcherbinin (shcs00)]] ([[User talk:Shcs00|talk]]) 12:34, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: I like the idea. Please, do not hesitate to contact the companies directly for the data. They are sometimes willing to help if you require just general, non sensitive data. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:08, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How long would it take to find love ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There is such thing as Drake formula used to calculate a chanse to meet an alien https://en.wikipedia.org/wiki/Drake_equation&lt;br /&gt;
Also there is an article https://e-lub.net/annuals/why.htm - to sum up, it is Drakes formula used to calculate a chance to meet a love of your life in London&lt;br /&gt;
&lt;br /&gt;
So What I want to do is to let user enter some parameters of what he/she thinks the perfect person is and based on the entered parameters we will see how long would it take to meet a perfect person in a city (say, Prague).&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Data about the city would be taken from official sources (might be Eurostat or some other data that is gathered by Czech statistical office)&lt;br /&gt;
User will enter all the parameters and then see when will he meet a person. &lt;br /&gt;
Of course for the sake of achievability some things will be simplified. For example I don't think I will actualy add millions of agents, Maybe hundreds would be enough.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
To see how year passes after year and love is still not found:) Or maybe to understand that lowering the expectations could correspond to finding a love faster&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22199</id>
		<title>Assignments WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22199"/>
		<updated>2021-12-10T18:36:36Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, put here your assignments. Do not forget to sign them. You can use &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; (four tildas) for an automatic signature. Use Show preview in order to check the result before your final sumbition.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, strive to formulate your assignment carefully. We expect an adequate effort to formulate the assignment as it is your semestral paper. Do not forget that your main goal is a research paper. It means your simulation model must generate the results that are specific, measurable and verifiable. Think twice how you will develop your model, which entities you will use, draw a model diagram, consider what you will measure. No sooner than when you have a good idea about the model, submit your assignment. And of course, read [[How to deal with the simulation assignment|How to deal with the simulation assignment]].&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Topics on gambling, cards, etc. are not welcome.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| type  = content&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
In order to avoid possible confusion, please, check if you have added '''approved''' in bold somewhere in our comment under your submission. If there is no '''approved''', it means the assignment was not approved yet.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Spread of covid19 in closed/open area markets ==&lt;br /&gt;
&lt;br /&gt;
In winter 2021 in Czechia the christmas markets were banned due to another covid19 infection wave. On the other hand people are free to go into shopping malls. It would be interesting to use existing data about covid19 virus transmission in agent based simulation to see how many people get infected and in what speed depending on whether they are in a christmas (open) market, or in a shopping mall (closed). The main goal will be to see if the simulation would backup the decision that has been made about christmas markets.&lt;br /&gt;
&lt;br /&gt;
Possible research papers that contain data about covid spreading&lt;br /&gt;
* [https://www.kaggle.com/guidant/covid19-evolution-transmission-spatialpatterns/ Kaggle notebook - Covid19, Evolution, Transmission, Spatial Patterns]&lt;br /&gt;
* [https://link.springer.com/article/10.1007/s10668-020-00884-x/ Research - Understanding COVID-19 transmission, health impacts and mitigation: timely social distancing is the key]&lt;br /&gt;
&lt;br /&gt;
This simulation would be realised using NetLogo.&lt;br /&gt;
&lt;br /&gt;
Summary:&lt;br /&gt;
&lt;br /&gt;
'''WHAT will be simulated'''&lt;br /&gt;
* market place, which can be both open space or closed space.&lt;br /&gt;
* people with or without masks, who will walk from shop to shop, with some intention and some of them will be virus carriers&lt;br /&gt;
* virus, which will spread in places where people go through (depending on the closed/open area, the infection rates will differ)&lt;br /&gt;
&lt;br /&gt;
'''GOAL of the simulation'''&lt;br /&gt;
* answer the question: &amp;quot;Where is the virus spread more significant? At the market place, or at the shopping mall?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Angel Kostov, xkosa20&lt;br /&gt;
&lt;br /&gt;
: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 11:58, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Effects of COVID-19 vaccination on the spread of infection ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Currently, there is a new wave of infection in the COVID-19 pandemic with high number of infections. In Germany, for example, more than 50,000 new infections are currently reported every day. To reduce the infection rate, a wide variety of measures have been implemented. One of these measures are the vaccination and masks. Vaccination can reduce the risk of infection and the likelihood of transmissibility. A simulation is conducted to vividly identify the extent to which vaccination could contain the pandemic.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The purpose of the simulation is to show how COVID-19 vaccination affects the spread of the pandemic. I will use an agent-based model in order to simulate the scenario in a simplified form based on existing scientific data. In addition, current COVID-19 measures are considered.  &lt;br /&gt;
&lt;br /&gt;
Subjects of the simulation: &lt;br /&gt;
&lt;br /&gt;
Environment: &lt;br /&gt;
* A village with around 6.000 inhabitants&lt;br /&gt;
* Simplified: The village is closed that is new people cannot come in and people of the village cannot go out &lt;br /&gt;
&lt;br /&gt;
Agents: &lt;br /&gt;
* Vaccinated persons&lt;br /&gt;
* Unvaccinated persons &lt;br /&gt;
* Simulations with different vaccination rates to compare the different infection courses&lt;br /&gt;
&lt;br /&gt;
Further measures: &lt;br /&gt;
* All people wear masks&lt;br /&gt;
* Nobody wears a mask  &lt;br /&gt;
&lt;br /&gt;
Start: &lt;br /&gt;
* Few agents are unknowingly infected (e.g. 0,1% of the inhabitants = 6 people) &lt;br /&gt;
* Movement of agents intended to reflect the daily behavior of people in real life in a simplified form.&lt;br /&gt;
* One agent can infect another agent with a certain probability if they are close to each other. &lt;br /&gt;
* The probability of an infection depends on the measure (vaccination / mask)&lt;br /&gt;
&lt;br /&gt;
'''Goal:'''&lt;br /&gt;
* Identify the infection course with different vaccination rates and measures. &lt;br /&gt;
* Showing the importance of vaccination.&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Possible data sources'''&lt;br /&gt;
&lt;br /&gt;
https://www.rki.de/SharedDocs/FAQ/COVID-Impfen/FAQ_Liste_Wirksamkeit.html&lt;br /&gt;
&lt;br /&gt;
Chia, P. Y., Xiang Ong, S. W., Chiew, C. J., Ang, L. W., Chavatte, J.-M., Mak, T.-M., Cui, L., Kalimuddin, S., Chia, W. N., Tan, C. W., Ann Chai, L. Y., Tan, S. Y., Zheng, S., Pin Lin, R. T., Wang, L., Leo, Y.-S., Lee, V. J., Lye, D. C., &amp;amp; Young, B. E. (2021). Virological and serological kinetics of SARS-CoV-2 Delta variant vaccine-breakthrough infections: A multi-center cohort study. Clinical Microbiology and Infection, S1198743X21006388. https://doi.org/10.1016/j.cmi.2021.11.010&lt;br /&gt;
&lt;br /&gt;
Eyre, D. W., Taylor, D., Purver, M., Chapman, D., Fowler, T., Pouwels, K., Walker, A. S., &amp;amp; Peto, T. E. (2021). The impact of SARS-CoV-2 vaccination on Alpha and Delta variant transmission [Preprint]. Infectious Diseases (except HIV/AIDS). https://doi.org/10.1101/2021.09.28.21264260&lt;br /&gt;
&lt;br /&gt;
Harder, T., Külper-Schiek, W., Reda, S., Treskova-Schwarzbach, M., Koch, J., Vygen-Bonnet, S., &amp;amp; Wichmann, O. (2021). Effectiveness of COVID-19 vaccines against SARS-CoV-2 infection with the Delta (B.1.617.2) variant: Second interim results of a living systematic review and meta-analysis, 1 January to 25 August 2021. Eurosurveillance, 26(41). https://doi.org/10.2807/1560-7917.ES.2021.26.41.2100920&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Laura Kundmueller&lt;br /&gt;
&lt;br /&gt;
: OK, but, please, elaborate it a bit. How exactly should the simulation look like, kinds of agents, etc. And mainly: the sources of data, etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:00, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation of genetic algorithm: Travelling Salesman Problem ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The topic of this simulation is an old graph problem, Travelling Salesman Problem. My approach would be based on genetic learning algorithm. A random map will be generated at the start. Salesman is travelling in a car with some gas. The gas is used as he travels, it can be recharged at gas stations but it costs money. The map contains some hills and flat roads, which have a different cost of gas when going through. &lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
* to find the optimum path between the towns.&lt;br /&gt;
&lt;br /&gt;
'''The parameters are:'''&lt;br /&gt;
* number of agents (travelling salesmen)&lt;br /&gt;
* gas in car&lt;br /&gt;
* money&lt;br /&gt;
&lt;br /&gt;
* number of towns&lt;br /&gt;
* number of hills&lt;br /&gt;
* number of gas stations&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Mart13]] ([[User talk:Mart13|talk]]) 09:57, 9 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: Although this isn't a true agent-based simulation, we sometimes accept topics from artificial intelligence and other related fields. However, it is necessary to elaborate it in deep. How exactly the algorithm will work. What is the goal (not the goal of the agent, but the goal of this work)? Etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:03, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Optimizing the process of baking wedding sweets ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
There is a wedding tradition in Czech Republic of baking wedding sweets and then handing them out to the guests of the weeding as a form of invitation. Process of baking usually takes whole day and several helpers in the kitchen are needed. Into paper baskets are usually packaged two types of sweets: several small ones with 3 different flavours and one so-called &amp;quot;rohový koláč&amp;quot;. Which are then delivered by the bride to wedding guests. For the purpose of this simulation are process and needed ingredients simplified.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
The goal is to optimize the number of helpers in the kitchen and find optimal amount of basic ingredients for specified number of guests.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Discrete simulation - SIMPROCESS&lt;br /&gt;
&lt;br /&gt;
'''Entities:'''&lt;br /&gt;
* sweets&lt;br /&gt;
* paper baskets&lt;br /&gt;
* baking trays&lt;br /&gt;
&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* pastry-cooks&lt;br /&gt;
* bride&lt;br /&gt;
* flour&lt;br /&gt;
* sugar&lt;br /&gt;
* curd&lt;br /&gt;
* plum jam&lt;br /&gt;
* poppy seed filling&lt;br /&gt;
&lt;br /&gt;
'''Process steps'''&lt;br /&gt;
* order for paper basket&lt;br /&gt;
* preparing sweets: small ones (3 different flavours), &amp;quot;rohove kolače&amp;quot; sweets (using all flavours)&lt;br /&gt;
* baking in the oven&lt;br /&gt;
* sugar coating&lt;br /&gt;
* packaging&lt;br /&gt;
* delivery&lt;br /&gt;
&lt;br /&gt;
'''Data:'''&lt;br /&gt;
* https://www.svetsvateb.cz/2021/02/623262-svatebni-kolacky/&lt;br /&gt;
* https://megvkuchyni.cz/recepty/speciality/svatebni-special-jak-na-svatebni-kolacky/&lt;br /&gt;
* experience&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 10:16, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: OK, maybe. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:05, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Carsharing company fleet optimization ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Recently, carsharing becomes more and more popular in large cities. Short-term rental (from several minutes to 24 hours) of a car with possibility to drop it anywhere in the allowed area in the city attracts people who for some reasons do not want to use their own vehicles. However, it is not always convenient. If the fleet is relatively small, the probability that a car will be somewhere close by is also quite low. Cars also must be refueled or recharged sometimes by external staff, which would increase cost of the fleet maintenance with increasing of the fleet size.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The proposing agent-based simulation will reproduce real situation with shared cars.&lt;br /&gt;
Two types of agents are planned:&lt;br /&gt;
* cars with different states (waiting, in rent, maintenance) and characteristics (mileage, fuel level)&lt;br /&gt;
* drivers - users of the service, who rent the cars and have their own behavior, including decision making on taking a car, driving style, and so on.&lt;br /&gt;
Some data for the model will be obtained as personal observations of two carsharing services operating in Prague, [https://anytimecar.cz/ Anytime] and [https://www.uniqway.cz/ Uniqway] (for example, number of available cars, which is visible in mobile applications). Another source of data would be statistics collected by other services abroad, for example, by operating in Russia service Yandex.Drive[https://www.statista.com/statistics/1224178/daily-use-duration-of-car-sharing-vehicles-in-moscow-by-vehicle-type/].&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
to find out optimal fleet size and structure and price policy to maximize revenue of a carsharing company.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Shcs00|Sergei Shcherbinin (shcs00)]] ([[User talk:Shcs00|talk]]) 12:34, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: I like the idea. Please, do not hesitate to contact the companies directly for the data. They are sometimes willing to help if you require just general, non sensitive data. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:08, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How long would it take to find love ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There is such thing as Drake formula used to calculate a chanse to meet an alien https://en.wikipedia.org/wiki/Drake_equation&lt;br /&gt;
Also there is an article https://e-lub.net/annuals/why.htm - to sum up, it is Drakes formula used to calculate a chance to meet a love of your life in London&lt;br /&gt;
&lt;br /&gt;
So What I want to do is to let user enter some parameters of what he/she thinks the perfect person is and based on the entered parameters we will see how long would it take to meet a perfect person in a city (say, Prague).&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Data about the city would be taken from official sources (might be Eurostat or some other data that is gathered by Czech statistical office)&lt;br /&gt;
User will enter all the parameters and then see when will he meet a person. &lt;br /&gt;
Of course for the sake of achievability some things will be simplified. For example I don't think I will actualy add millions of agents, Maybe hundreds would be enough.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
To see how year passes after year and love is still not found:) Or maybe to understand that lowering the expectations could correspond to finding a love faster&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22198</id>
		<title>Assignments WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22198"/>
		<updated>2021-12-10T18:36:03Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, put here your assignments. Do not forget to sign them. You can use &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; (four tildas) for an automatic signature. Use Show preview in order to check the result before your final sumbition.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, strive to formulate your assignment carefully. We expect an adequate effort to formulate the assignment as it is your semestral paper. Do not forget that your main goal is a research paper. It means your simulation model must generate the results that are specific, measurable and verifiable. Think twice how you will develop your model, which entities you will use, draw a model diagram, consider what you will measure. No sooner than when you have a good idea about the model, submit your assignment. And of course, read [[How to deal with the simulation assignment|How to deal with the simulation assignment]].&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Topics on gambling, cards, etc. are not welcome.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| type  = content&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
In order to avoid possible confusion, please, check if you have added '''approved''' in bold somewhere in our comment under your submission. If there is no '''approved''', it means the assignment was not approved yet.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Spread of covid19 in closed/open area markets ==&lt;br /&gt;
&lt;br /&gt;
In winter 2021 in Czechia the christmas markets were banned due to another covid19 infection wave. On the other hand people are free to go into shopping malls. It would be interesting to use existing data about covid19 virus transmission in agent based simulation to see how many people get infected and in what speed depending on whether they are in a christmas (open) market, or in a shopping mall (closed). The main goal will be to see if the simulation would backup the decision that has been made about christmas markets.&lt;br /&gt;
&lt;br /&gt;
Possible research papers that contain data about covid spreading&lt;br /&gt;
* [https://www.kaggle.com/guidant/covid19-evolution-transmission-spatialpatterns/ Kaggle notebook - Covid19, Evolution, Transmission, Spatial Patterns]&lt;br /&gt;
* [https://link.springer.com/article/10.1007/s10668-020-00884-x/ Research - Understanding COVID-19 transmission, health impacts and mitigation: timely social distancing is the key]&lt;br /&gt;
&lt;br /&gt;
This simulation would be realised using NetLogo.&lt;br /&gt;
&lt;br /&gt;
Summary:&lt;br /&gt;
&lt;br /&gt;
'''WHAT will be simulated'''&lt;br /&gt;
* market place, which can be both open space or closed space.&lt;br /&gt;
* people with or without masks, who will walk from shop to shop, with some intention and some of them will be virus carriers&lt;br /&gt;
* virus, which will spread in places where people go through (depending on the closed/open area, the infection rates will differ)&lt;br /&gt;
&lt;br /&gt;
'''GOAL of the simulation'''&lt;br /&gt;
* answer the question: &amp;quot;Where is the virus spread more significant? At the market place, or at the shopping mall?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Angel Kostov, xkosa20&lt;br /&gt;
&lt;br /&gt;
: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 11:58, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Effects of COVID-19 vaccination on the spread of infection ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Currently, there is a new wave of infection in the COVID-19 pandemic with high number of infections. In Germany, for example, more than 50,000 new infections are currently reported every day. To reduce the infection rate, a wide variety of measures have been implemented. One of these measures are the vaccination and masks. Vaccination can reduce the risk of infection and the likelihood of transmissibility. A simulation is conducted to vividly identify the extent to which vaccination could contain the pandemic.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The purpose of the simulation is to show how COVID-19 vaccination affects the spread of the pandemic. I will use an agent-based model in order to simulate the scenario in a simplified form based on existing scientific data. In addition, current COVID-19 measures are considered.  &lt;br /&gt;
&lt;br /&gt;
Subjects of the simulation: &lt;br /&gt;
&lt;br /&gt;
Environment: &lt;br /&gt;
* A village with around 6.000 inhabitants&lt;br /&gt;
* Simplified: The village is closed that is new people cannot come in and people of the village cannot go out &lt;br /&gt;
&lt;br /&gt;
Agents: &lt;br /&gt;
* Vaccinated persons&lt;br /&gt;
* Unvaccinated persons &lt;br /&gt;
* Simulations with different vaccination rates to compare the different infection courses&lt;br /&gt;
&lt;br /&gt;
Further measures: &lt;br /&gt;
* All people wear masks&lt;br /&gt;
* Nobody wears a mask  &lt;br /&gt;
&lt;br /&gt;
Start: &lt;br /&gt;
* Few agents are unknowingly infected (e.g. 0,1% of the inhabitants = 6 people) &lt;br /&gt;
* Movement of agents intended to reflect the daily behavior of people in real life in a simplified form.&lt;br /&gt;
* One agent can infect another agent with a certain probability if they are close to each other. &lt;br /&gt;
* The probability of an infection depends on the measure (vaccination / mask)&lt;br /&gt;
&lt;br /&gt;
'''Goal:'''&lt;br /&gt;
* Identify the infection course with different vaccination rates and measures. &lt;br /&gt;
* Showing the importance of vaccination.&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Possible data sources'''&lt;br /&gt;
&lt;br /&gt;
https://www.rki.de/SharedDocs/FAQ/COVID-Impfen/FAQ_Liste_Wirksamkeit.html&lt;br /&gt;
&lt;br /&gt;
Chia, P. Y., Xiang Ong, S. W., Chiew, C. J., Ang, L. W., Chavatte, J.-M., Mak, T.-M., Cui, L., Kalimuddin, S., Chia, W. N., Tan, C. W., Ann Chai, L. Y., Tan, S. Y., Zheng, S., Pin Lin, R. T., Wang, L., Leo, Y.-S., Lee, V. J., Lye, D. C., &amp;amp; Young, B. E. (2021). Virological and serological kinetics of SARS-CoV-2 Delta variant vaccine-breakthrough infections: A multi-center cohort study. Clinical Microbiology and Infection, S1198743X21006388. https://doi.org/10.1016/j.cmi.2021.11.010&lt;br /&gt;
&lt;br /&gt;
Eyre, D. W., Taylor, D., Purver, M., Chapman, D., Fowler, T., Pouwels, K., Walker, A. S., &amp;amp; Peto, T. E. (2021). The impact of SARS-CoV-2 vaccination on Alpha and Delta variant transmission [Preprint]. Infectious Diseases (except HIV/AIDS). https://doi.org/10.1101/2021.09.28.21264260&lt;br /&gt;
&lt;br /&gt;
Harder, T., Külper-Schiek, W., Reda, S., Treskova-Schwarzbach, M., Koch, J., Vygen-Bonnet, S., &amp;amp; Wichmann, O. (2021). Effectiveness of COVID-19 vaccines against SARS-CoV-2 infection with the Delta (B.1.617.2) variant: Second interim results of a living systematic review and meta-analysis, 1 January to 25 August 2021. Eurosurveillance, 26(41). https://doi.org/10.2807/1560-7917.ES.2021.26.41.2100920&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Laura Kundmueller&lt;br /&gt;
&lt;br /&gt;
: OK, but, please, elaborate it a bit. How exactly should the simulation look like, kinds of agents, etc. And mainly: the sources of data, etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:00, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation of genetic algorithm: Travelling Salesman Problem ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The topic of this simulation is an old graph problem, Travelling Salesman Problem. My approach would be based on genetic learning algorithm. A random map will be generated at the start. Salesman is travelling in a car with some gas. The gas is used as he travels, it can be recharged at gas stations but it costs money. The map contains some hills and flat roads, which have a different cost of gas when going through. &lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
* to find the optimum path between the towns.&lt;br /&gt;
&lt;br /&gt;
'''The parameters are:'''&lt;br /&gt;
* number of agents (travelling salesmen)&lt;br /&gt;
* gas in car&lt;br /&gt;
* money&lt;br /&gt;
&lt;br /&gt;
* number of towns&lt;br /&gt;
* number of hills&lt;br /&gt;
* number of gas stations&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Mart13]] ([[User talk:Mart13|talk]]) 09:57, 9 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: Although this isn't a true agent-based simulation, we sometimes accept topics from artificial intelligence and other related fields. However, it is necessary to elaborate it in deep. How exactly the algorithm will work. What is the goal (not the goal of the agent, but the goal of this work)? Etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:03, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Optimizing the process of baking wedding sweets ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
There is a wedding tradition in Czech Republic of baking wedding sweets and then handing them out to the guests of the weeding as a form of invitation. Process of baking usually takes whole day and several helpers in the kitchen are needed. Into paper baskets are usually packaged two types of sweets: several small ones with 3 different flavours and one so-called &amp;quot;rohový koláč&amp;quot;. Which are then delivered by the bride to wedding guests. For the purpose of this simulation are process and needed ingredients simplified.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
The goal is to optimize the number of helpers in the kitchen and find optimal amount of basic ingredients for specified number of guests.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Discrete simulation - SIMPROCESS&lt;br /&gt;
&lt;br /&gt;
'''Entities:'''&lt;br /&gt;
* sweets&lt;br /&gt;
* paper baskets&lt;br /&gt;
* baking trays&lt;br /&gt;
&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* pastry-cooks&lt;br /&gt;
* bride&lt;br /&gt;
* flour&lt;br /&gt;
* sugar&lt;br /&gt;
* curd&lt;br /&gt;
* plum jam&lt;br /&gt;
* poppy seed filling&lt;br /&gt;
&lt;br /&gt;
'''Process steps'''&lt;br /&gt;
* order for paper basket&lt;br /&gt;
* preparing sweets: small ones (3 different flavours), &amp;quot;rohove kolače&amp;quot; sweets (using all flavours)&lt;br /&gt;
* baking in the oven&lt;br /&gt;
* sugar coating&lt;br /&gt;
* packaging&lt;br /&gt;
* delivery&lt;br /&gt;
&lt;br /&gt;
'''Data:'''&lt;br /&gt;
* https://www.svetsvateb.cz/2021/02/623262-svatebni-kolacky/&lt;br /&gt;
* https://megvkuchyni.cz/recepty/speciality/svatebni-special-jak-na-svatebni-kolacky/&lt;br /&gt;
* experience&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 10:16, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: OK, maybe. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:05, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Carsharing company fleet optimization ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Recently, carsharing becomes more and more popular in large cities. Short-term rental (from several minutes to 24 hours) of a car with possibility to drop it anywhere in the allowed area in the city attracts people who for some reasons do not want to use their own vehicles. However, it is not always convenient. If the fleet is relatively small, the probability that a car will be somewhere close by is also quite low. Cars also must be refueled or recharged sometimes by external staff, which would increase cost of the fleet maintenance with increasing of the fleet size.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The proposing agent-based simulation will reproduce real situation with shared cars.&lt;br /&gt;
Two types of agents are planned:&lt;br /&gt;
* cars with different states (waiting, in rent, maintenance) and characteristics (mileage, fuel level)&lt;br /&gt;
* drivers - users of the service, who rent the cars and have their own behavior, including decision making on taking a car, driving style, and so on.&lt;br /&gt;
Some data for the model will be obtained as personal observations of two carsharing services operating in Prague, [https://anytimecar.cz/ Anytime] and [https://www.uniqway.cz/ Uniqway] (for example, number of available cars, which is visible in mobile applications). Another source of data would be statistics collected by other services abroad, for example, by operating in Russia service Yandex.Drive[https://www.statista.com/statistics/1224178/daily-use-duration-of-car-sharing-vehicles-in-moscow-by-vehicle-type/].&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
to find out optimal fleet size and structure and price policy to maximize revenue of a carsharing company.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Shcs00|Sergei Shcherbinin (shcs00)]] ([[User talk:Shcs00|talk]]) 12:34, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: I like the idea. Please, do not hesitate to contact the companies directly for the data. They are sometimes willing to help if you require just general, non sensitive data. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:08, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How long would it take to find love ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There is such thing as Drake formula used to calculate a chanse to meet an alien https://en.wikipedia.org/wiki/Drake_equation&lt;br /&gt;
Also there is an article https://e-lub.net/annuals/why.htm - to sum up, it is Drakes formula used to calculate a chance to meet a love of your life in London&lt;br /&gt;
So What I want to do is to let user enter some parameters of what he/she thinks the perfect person is and based on the entered parameters we will see how long would it take to meet a perfect person in a city (say, Prague).&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Data about the city would be taken from official sources (might be Eurostat or some other data that is gathered by Czech statistical office)&lt;br /&gt;
User will enter all the parameters and then see when will he meet a person. &lt;br /&gt;
Of course for the sake of achievability some things will be simplified. For example I don't think I will actualy add millions of agents, Maybe hundreds would be enough.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
To see how year passes after year and love is still not found:) Or maybe to understand that lowering the expectations could correspond to finding a love faster&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
	<entry>
		<id>http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22197</id>
		<title>Assignments WS 2021/2022</title>
		<link rel="alternate" type="text/html" href="http://www.simulace.info/index.php?title=Assignments_WS_2021/2022&amp;diff=22197"/>
		<updated>2021-12-10T18:35:05Z</updated>

		<summary type="html">&lt;p&gt;Vasodzh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, put here your assignments. Do not forget to sign them. You can use &amp;lt;nowiki&amp;gt;~~~~&amp;lt;/nowiki&amp;gt; (four tildas) for an automatic signature. Use Show preview in order to check the result before your final sumbition.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Please, strive to formulate your assignment carefully. We expect an adequate effort to formulate the assignment as it is your semestral paper. Do not forget that your main goal is a research paper. It means your simulation model must generate the results that are specific, measurable and verifiable. Think twice how you will develop your model, which entities you will use, draw a model diagram, consider what you will measure. No sooner than when you have a good idea about the model, submit your assignment. And of course, read [[How to deal with the simulation assignment|How to deal with the simulation assignment]].&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
Topics on gambling, cards, etc. are not welcome.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Ambox&lt;br /&gt;
| type  = content&lt;br /&gt;
| text  = &amp;lt;div&amp;gt;&lt;br /&gt;
In order to avoid possible confusion, please, check if you have added '''approved''' in bold somewhere in our comment under your submission. If there is no '''approved''', it means the assignment was not approved yet.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Spread of covid19 in closed/open area markets ==&lt;br /&gt;
&lt;br /&gt;
In winter 2021 in Czechia the christmas markets were banned due to another covid19 infection wave. On the other hand people are free to go into shopping malls. It would be interesting to use existing data about covid19 virus transmission in agent based simulation to see how many people get infected and in what speed depending on whether they are in a christmas (open) market, or in a shopping mall (closed). The main goal will be to see if the simulation would backup the decision that has been made about christmas markets.&lt;br /&gt;
&lt;br /&gt;
Possible research papers that contain data about covid spreading&lt;br /&gt;
* [https://www.kaggle.com/guidant/covid19-evolution-transmission-spatialpatterns/ Kaggle notebook - Covid19, Evolution, Transmission, Spatial Patterns]&lt;br /&gt;
* [https://link.springer.com/article/10.1007/s10668-020-00884-x/ Research - Understanding COVID-19 transmission, health impacts and mitigation: timely social distancing is the key]&lt;br /&gt;
&lt;br /&gt;
This simulation would be realised using NetLogo.&lt;br /&gt;
&lt;br /&gt;
Summary:&lt;br /&gt;
&lt;br /&gt;
'''WHAT will be simulated'''&lt;br /&gt;
* market place, which can be both open space or closed space.&lt;br /&gt;
* people with or without masks, who will walk from shop to shop, with some intention and some of them will be virus carriers&lt;br /&gt;
* virus, which will spread in places where people go through (depending on the closed/open area, the infection rates will differ)&lt;br /&gt;
&lt;br /&gt;
'''GOAL of the simulation'''&lt;br /&gt;
* answer the question: &amp;quot;Where is the virus spread more significant? At the market place, or at the shopping mall?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
'''TOOL used for the simulation'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
* Agent based simulation&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Angel Kostov, xkosa20&lt;br /&gt;
&lt;br /&gt;
: '''Approved''' [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 11:58, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Effects of COVID-19 vaccination on the spread of infection ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Currently, there is a new wave of infection in the COVID-19 pandemic with high number of infections. In Germany, for example, more than 50,000 new infections are currently reported every day. To reduce the infection rate, a wide variety of measures have been implemented. One of these measures are the vaccination and masks. Vaccination can reduce the risk of infection and the likelihood of transmissibility. A simulation is conducted to vividly identify the extent to which vaccination could contain the pandemic.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The purpose of the simulation is to show how COVID-19 vaccination affects the spread of the pandemic. I will use an agent-based model in order to simulate the scenario in a simplified form based on existing scientific data. In addition, current COVID-19 measures are considered.  &lt;br /&gt;
&lt;br /&gt;
Subjects of the simulation: &lt;br /&gt;
&lt;br /&gt;
Environment: &lt;br /&gt;
* A village with around 6.000 inhabitants&lt;br /&gt;
* Simplified: The village is closed that is new people cannot come in and people of the village cannot go out &lt;br /&gt;
&lt;br /&gt;
Agents: &lt;br /&gt;
* Vaccinated persons&lt;br /&gt;
* Unvaccinated persons &lt;br /&gt;
* Simulations with different vaccination rates to compare the different infection courses&lt;br /&gt;
&lt;br /&gt;
Further measures: &lt;br /&gt;
* All people wear masks&lt;br /&gt;
* Nobody wears a mask  &lt;br /&gt;
&lt;br /&gt;
Start: &lt;br /&gt;
* Few agents are unknowingly infected (e.g. 0,1% of the inhabitants = 6 people) &lt;br /&gt;
* Movement of agents intended to reflect the daily behavior of people in real life in a simplified form.&lt;br /&gt;
* One agent can infect another agent with a certain probability if they are close to each other. &lt;br /&gt;
* The probability of an infection depends on the measure (vaccination / mask)&lt;br /&gt;
&lt;br /&gt;
'''Goal:'''&lt;br /&gt;
* Identify the infection course with different vaccination rates and measures. &lt;br /&gt;
* Showing the importance of vaccination.&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Possible data sources'''&lt;br /&gt;
&lt;br /&gt;
https://www.rki.de/SharedDocs/FAQ/COVID-Impfen/FAQ_Liste_Wirksamkeit.html&lt;br /&gt;
&lt;br /&gt;
Chia, P. Y., Xiang Ong, S. W., Chiew, C. J., Ang, L. W., Chavatte, J.-M., Mak, T.-M., Cui, L., Kalimuddin, S., Chia, W. N., Tan, C. W., Ann Chai, L. Y., Tan, S. Y., Zheng, S., Pin Lin, R. T., Wang, L., Leo, Y.-S., Lee, V. J., Lye, D. C., &amp;amp; Young, B. E. (2021). Virological and serological kinetics of SARS-CoV-2 Delta variant vaccine-breakthrough infections: A multi-center cohort study. Clinical Microbiology and Infection, S1198743X21006388. https://doi.org/10.1016/j.cmi.2021.11.010&lt;br /&gt;
&lt;br /&gt;
Eyre, D. W., Taylor, D., Purver, M., Chapman, D., Fowler, T., Pouwels, K., Walker, A. S., &amp;amp; Peto, T. E. (2021). The impact of SARS-CoV-2 vaccination on Alpha and Delta variant transmission [Preprint]. Infectious Diseases (except HIV/AIDS). https://doi.org/10.1101/2021.09.28.21264260&lt;br /&gt;
&lt;br /&gt;
Harder, T., Külper-Schiek, W., Reda, S., Treskova-Schwarzbach, M., Koch, J., Vygen-Bonnet, S., &amp;amp; Wichmann, O. (2021). Effectiveness of COVID-19 vaccines against SARS-CoV-2 infection with the Delta (B.1.617.2) variant: Second interim results of a living systematic review and meta-analysis, 1 January to 25 August 2021. Eurosurveillance, 26(41). https://doi.org/10.2807/1560-7917.ES.2021.26.41.2100920&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Author:''' Laura Kundmueller&lt;br /&gt;
&lt;br /&gt;
: OK, but, please, elaborate it a bit. How exactly should the simulation look like, kinds of agents, etc. And mainly: the sources of data, etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:00, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Simulation of genetic algorithm: Travelling Salesman Problem ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The topic of this simulation is an old graph problem, Travelling Salesman Problem. My approach would be based on genetic learning algorithm. A random map will be generated at the start. Salesman is travelling in a car with some gas. The gas is used as he travels, it can be recharged at gas stations but it costs money. The map contains some hills and flat roads, which have a different cost of gas when going through. &lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
* to find the optimum path between the towns.&lt;br /&gt;
&lt;br /&gt;
'''The parameters are:'''&lt;br /&gt;
* number of agents (travelling salesmen)&lt;br /&gt;
* gas in car&lt;br /&gt;
* money&lt;br /&gt;
&lt;br /&gt;
* number of towns&lt;br /&gt;
* number of hills&lt;br /&gt;
* number of gas stations&lt;br /&gt;
&lt;br /&gt;
'''Method'''&lt;br /&gt;
* NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Mart13|Mart13]] ([[User talk:Mart13|talk]]) 09:57, 9 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: Although this isn't a true agent-based simulation, we sometimes accept topics from artificial intelligence and other related fields. However, it is necessary to elaborate it in deep. How exactly the algorithm will work. What is the goal (not the goal of the agent, but the goal of this work)? Etc. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:03, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Optimizing the process of baking wedding sweets ==&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
There is a wedding tradition in Czech Republic of baking wedding sweets and then handing them out to the guests of the weeding as a form of invitation. Process of baking usually takes whole day and several helpers in the kitchen are needed. Into paper baskets are usually packaged two types of sweets: several small ones with 3 different flavours and one so-called &amp;quot;rohový koláč&amp;quot;. Which are then delivered by the bride to wedding guests. For the purpose of this simulation are process and needed ingredients simplified.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
The goal is to optimize the number of helpers in the kitchen and find optimal amount of basic ingredients for specified number of guests.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
Discrete simulation - SIMPROCESS&lt;br /&gt;
&lt;br /&gt;
'''Entities:'''&lt;br /&gt;
* sweets&lt;br /&gt;
* paper baskets&lt;br /&gt;
* baking trays&lt;br /&gt;
&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* pastry-cooks&lt;br /&gt;
* bride&lt;br /&gt;
* flour&lt;br /&gt;
* sugar&lt;br /&gt;
* curd&lt;br /&gt;
* plum jam&lt;br /&gt;
* poppy seed filling&lt;br /&gt;
&lt;br /&gt;
'''Process steps'''&lt;br /&gt;
* order for paper basket&lt;br /&gt;
* preparing sweets: small ones (3 different flavours), &amp;quot;rohove kolače&amp;quot; sweets (using all flavours)&lt;br /&gt;
* baking in the oven&lt;br /&gt;
* sugar coating&lt;br /&gt;
* packaging&lt;br /&gt;
* delivery&lt;br /&gt;
&lt;br /&gt;
'''Data:'''&lt;br /&gt;
* https://www.svetsvateb.cz/2021/02/623262-svatebni-kolacky/&lt;br /&gt;
* https://megvkuchyni.cz/recepty/speciality/svatebni-special-jak-na-svatebni-kolacky/&lt;br /&gt;
* experience&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Cerm18|Michaela Červinková (cerm18)]] ([[User talk:Cerm18|talk]]) 10:16, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: OK, maybe. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:05, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
== Carsharing company fleet optimization ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
Recently, carsharing becomes more and more popular in large cities. Short-term rental (from several minutes to 24 hours) of a car with possibility to drop it anywhere in the allowed area in the city attracts people who for some reasons do not want to use their own vehicles. However, it is not always convenient. If the fleet is relatively small, the probability that a car will be somewhere close by is also quite low. Cars also must be refueled or recharged sometimes by external staff, which would increase cost of the fleet maintenance with increasing of the fleet size.&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
The proposing agent-based simulation will reproduce real situation with shared cars.&lt;br /&gt;
Two types of agents are planned:&lt;br /&gt;
* cars with different states (waiting, in rent, maintenance) and characteristics (mileage, fuel level)&lt;br /&gt;
* drivers - users of the service, who rent the cars and have their own behavior, including decision making on taking a car, driving style, and so on.&lt;br /&gt;
Some data for the model will be obtained as personal observations of two carsharing services operating in Prague, [https://anytimecar.cz/ Anytime] and [https://www.uniqway.cz/ Uniqway] (for example, number of available cars, which is visible in mobile applications). Another source of data would be statistics collected by other services abroad, for example, by operating in Russia service Yandex.Drive[https://www.statista.com/statistics/1224178/daily-use-duration-of-car-sharing-vehicles-in-moscow-by-vehicle-type/].&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
to find out optimal fleet size and structure and price policy to maximize revenue of a carsharing company.&lt;br /&gt;
&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
'''Author:''' [[User:Shcs00|Sergei Shcherbinin (shcs00)]] ([[User talk:Shcs00|talk]]) 12:34, 8 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
: I like the idea. Please, do not hesitate to contact the companies directly for the data. They are sometimes willing to help if you require just general, non sensitive data. '''Approved'''. [[User:Tomáš|Tomáš]] ([[User talk:Tomáš|talk]]) 12:08, 10 December 2021 (CET)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How long would it take to find love ==&lt;br /&gt;
&lt;br /&gt;
'''Problem definition'''&lt;br /&gt;
&lt;br /&gt;
There is such thing as Drake formula used to calculate a chanse to meet an alien https://en.wikipedia.org/wiki/Drake_equation&lt;br /&gt;
Also there is an article https://e-lub.net/annuals/why.htm - to summ up, it is Drakes formula used to calculate a chance to meet a love of your life in London&lt;br /&gt;
So What I want to do is to let user enter some parameters of what he/she thinks the perfect person is and based on the entered parameters we will see how long would it take to meet a perfect person in a city (say, Prague).&lt;br /&gt;
&lt;br /&gt;
'''Simulation'''&lt;br /&gt;
&lt;br /&gt;
Data about the city would be taken from official sources (might be Eurostat or some other data that is gathered by Czech statistical office)&lt;br /&gt;
User will enter all the parameters and then see when will he meet a person. &lt;br /&gt;
Of course for the sake of achievability some things will be simplified. For example I don't think I will actualy add millions of agents, Maybe hundreds would be enough.&lt;br /&gt;
&lt;br /&gt;
'''The goal is:'''&lt;br /&gt;
To see how year passes after year and love is still not found:) Or maybe to understand that lowering the expectations could correspond to finding a love faster&lt;br /&gt;
'''Method:'''&lt;br /&gt;
agent-based simulation - NetLogo&lt;br /&gt;
&lt;br /&gt;
Author - Vaso Dzhinchvelashvili&lt;/div&gt;</summary>
		<author><name>Vasodzh</name></author>
		
	</entry>
</feed>