search

ianfhunter / TeamCrab

Group Project for CS4098
MIT License
0 stars 1 forks source link

Problem simulator hates Belarus #42

Closed scottcunningham closed 10 years ago

scottcunningham commented 10 years ago

Problems need to be less frequent than currently - in the IE/Belarus scenario, I keep getting insanely high costs for Belarus which throws the whole game off

NEW PROBLEM AT SITE Belarus List of problems to occur at site to date: module or product fails acceptance tests (fails to meet real requirements) a site falls behind more than 25% on a task module fails to integrate properly a site falls behind more than 25% on a task module fails to integrate properly Module: Framework - Progress: 1635.0 - Expected Cost: 600 - Actual Cost: 3440.4

This is obviously a ridiculous amount of problems as it's almost 600% of the expected cost for a week-long project

lardnerl commented 10 years ago

This is kind of a fundamental problem with how the logic of the problem engine has been given to us. Even with nothing wrong, there is a base chance of 66%(worst case is 96%) of a problem occurring every day. This is offset a large amount by a constant set in the config file, however if this number is set to far the rest of the problem settings effectively have no impact.

On 11 March 2014 20:41, Scott Cunningham notifications@github.com wrote:

Problems need to be less frequent than currently - in the IE/Belarus scenario, I keep getting insanely high costs for Belarus which throws the whole game off

NEW PROBLEM AT SITE Belarus List of problems to occur at site to date: module or product fails acceptance tests (fails to meet real requirements) a site falls behind more than 25% on a task module fails to integrate properly a site falls behind more than 25% on a task module fails to integrate properly Module: Framework - Progress: 1635.0 - Expected Cost: 600 - Actual Cost: 3440.4

This is obviously a ridiculous amount of problems as it's almost 600% of the expected cost for a week-long project

Reply to this email directly or view it on GitHubhttps://github.com/ianfhunter/TeamCrab/issues/42 .

scottcunningham commented 10 years ago

I think we need to change it regardless and leave a note in the README. As it is, the simulation is always very very very late.

On 11 March 2014 20:58, lardnerl notifications@github.com wrote:

This is kind of a fundamental problem with how the logic of the problem engine has been given to us. Even with nothing wrong, there is a base chance of 66%(worst case is 96%) of a problem occurring every day. This is offset a large amount by a constant set in the config file, however if this number is set to far the rest of the problem settings effectively have no impact.

On 11 March 2014 20:41, Scott Cunningham notifications@github.com wrote:

Problems need to be less frequent than currently - in the IE/Belarus scenario, I keep getting insanely high costs for Belarus which throws the whole game off

NEW PROBLEM AT SITE Belarus List of problems to occur at site to date: module or product fails acceptance tests (fails to meet real requirements) a site falls behind more than 25% on a task module fails to integrate properly a site falls behind more than 25% on a task module fails to integrate properly Module: Framework - Progress: 1635.0 - Expected Cost: 600 - Actual Cost: 3440.4

This is obviously a ridiculous amount of problems as it's almost 600% of the expected cost for a week-long project

Reply to this email directly or view it on GitHub< https://github.com/ianfhunter/TeamCrab/issues/42> .

Reply to this email directly or view it on GitHubhttps://github.com/ianfhunter/TeamCrab/issues/42#issuecomment-37349012 .

scottcunningham commented 10 years ago

Maybe just change the problem variable in config?

scottcunningham commented 10 years ago

Looks fine to me, yolo