【POJ2096】【Collecting Bugs】
来源:互联网 发布:淘宝秒杀专区在哪 编辑:程序博客网 时间:2024/05/01 03:53
Collecting Bugs
Time Limit: 10000MS Memory Limit: 64000KTotal Submissions: 3515 Accepted: 1735Case Time Limit: 2000MS Special Judge
Description
Ivan is fond of collecting. Unlike other people who collect post stamps, coins or other material stuff, he collects software bugs. When Ivan gets a new program, he classifies all possible bugs into n categories. Each day he discovers exactly one bug in the program and adds information about it and its category into a spreadsheet. When he finds bugs in all bug categories, he calls the program disgusting, publishes this spreadsheet on his home page, and forgets completely about the program.
Two companies, Macrosoft and Microhard are in tight competition. Microhard wants to decrease sales of one Macrosoft program. They hire Ivan to prove that the program in question is disgusting. However, Ivan has a complicated problem. This new program has s subcomponents, and finding bugs of all types in each subcomponent would take too long before the target could be reached. So Ivan and Microhard agreed to use a simpler criteria --- Ivan should find at least one bug in each subsystem and at least one bug of each category.
Macrosoft knows about these plans and it wants to estimate the time that is required for Ivan to call its program disgusting. It's important because the company releases a new version soon, so it can correct its plans and release it quicker. Nobody would be interested in Ivan's opinion about the reliability of the obsolete version.
A bug found in the program can be of any category with equal probability. Similarly, the bug can be found in any given subsystem with equal probability. Any particular bug cannot belong to two different categories or happen simultaneously in two different subsystems. The number of bugs in the program is almost infinite, so the probability of finding a new bug of some category in some subsystem does not reduce after finding any number of bugs of that category in that subsystem.
Find an average time (in days of Ivan's work) required to name the program disgusting.
Two companies, Macrosoft and Microhard are in tight competition. Microhard wants to decrease sales of one Macrosoft program. They hire Ivan to prove that the program in question is disgusting. However, Ivan has a complicated problem. This new program has s subcomponents, and finding bugs of all types in each subcomponent would take too long before the target could be reached. So Ivan and Microhard agreed to use a simpler criteria --- Ivan should find at least one bug in each subsystem and at least one bug of each category.
Macrosoft knows about these plans and it wants to estimate the time that is required for Ivan to call its program disgusting. It's important because the company releases a new version soon, so it can correct its plans and release it quicker. Nobody would be interested in Ivan's opinion about the reliability of the obsolete version.
A bug found in the program can be of any category with equal probability. Similarly, the bug can be found in any given subsystem with equal probability. Any particular bug cannot belong to two different categories or happen simultaneously in two different subsystems. The number of bugs in the program is almost infinite, so the probability of finding a new bug of some category in some subsystem does not reduce after finding any number of bugs of that category in that subsystem.
Find an average time (in days of Ivan's work) required to name the program disgusting.
Input
Input file contains two integer numbers, n and s (0 < n, s <= 1 000).
Output
Output the expectation of the Ivan's working days needed to call the program disgusting, accurate to 4 digits after the decimal point.
Sample Input
1 2
Sample Output
3.0000
Source
Northeastern Europe 2004, Northern Subregion
#include <iostream>#include <cstring>#include <cmath>#include <queue>#include <stack>#include <list>#include <map>#include <set>#include <string>#include <cstdlib>#include <cstdio>#include <algorithm>using namespace std; int n,s;double dp[1010][1010];int main(){ while(scanf("%d%d",&n,&s) != EOF){memset(dp,0,sizeof(dp));for(int i=n;i>=0;i--){for(int j=s;j>=0;j--){if(i == n && j == s)continue;double p1 = ((double)i*(s-j))/n/s;double p2 = ((double)(n-i)*j)/n/s;double p3 = (double(n-i)*(s-j))/n/s;double p0 = 1.0 - (double(i*j))/n/s;dp[i][j] = p1*dp[i][j+1] + p2*dp[i+1][j] + p3*dp[i+1][j+1]+1;dp[i][j] = dp[i][j] / p0;}}printf("%.4lf\n",dp[0][0]);} return 0;}
0 0
- poj2096 - Collecting Bugs
- Collecting Bugs(poj2096)
- POJ2096------Collecting Bugs
- 【POJ2096】【Collecting Bugs】
- poj2096 Collecting Bugs
- 【POJ2096】Collecting Bugs
- poj2096 Collecting Bugs
- poj2096 Collecting Bugs----期望复习
- POJ2096--Collecting Bugs--概率DP
- POJ2096-Collecting Bugs(概率DP)
- 【poj2096】Collecting Bugs 期望dp
- poj2096 Collecting Bugs(概率dp)
- poj2096 Collecting Bugs(概率dp)
- [POJ2096]Collecting Bugs(期望dp)
- 【poj2096】Collecting Bugs(期望dp)
- POJ2096:Collecting Bugs(概率dp & 期望)
- POJ2096 Collecting Bugs 解题报告【概率DP】
- [poj2096][动态规划DP]Collecting Bugs
- C语言函数参数压栈顺序为何是从右到左?
- MarkDown
- Scala入门到精通——第二十二节 高级类型 (一)
- #第二周1001题解#
- burp suite使用(三)--- intruder收集关键信息
- 【POJ2096】【Collecting Bugs】
- Hibernate二级缓存使用(ehcache)
- rethat中ip地址的设定
- IOS--商品的添加与删除
- [读书笔记—效率]《超级整理术》- [日]泉正人
- 自定义ActionBar+fragment实现页面切换
- Codeforces 148D Bag of mice (概率dp)
- mysql 经典sql收集
- Hello,World