karths commited on
Commit
b9b7a6b
·
verified ·
1 Parent(s): de23917

Update app.py

Browse files
Files changed (1) hide show
  1. app.py +1 -8
app.py CHANGED
@@ -92,7 +92,7 @@ def main_interface(text):
92
  for model_path, model in models.items():
93
  quality_name = get_quality_name(model_path)
94
  avg_prob = model_prediction(model, text, device)
95
- if avg_prob >= 0.90: # Only consider probabilities >= 0.90
96
  results.append((quality_name, avg_prob))
97
  logging.info(f"Model: {model_path}, Quality: {quality_name}, Average Probability: {avg_prob:.3f}")
98
 
@@ -146,14 +146,7 @@ def render_html_output(top_qualities):
146
 
147
  example_texts = [
148
  ["The algorithm does not accurately distinguish between the positive and negative classes during edge cases.\n\nEnvironment: Production\nReproduction: Run the classifier on the test dataset with known edge cases."],
149
- ["The system must handle at least 10,000 simultaneous users without performance degradation.\n\nEnvironment: Server-side processing\nReproduction: Conduct load testing simulating 10,000 users."],
150
- ["There is a lack of consistency in code reviews, leading to varied quality in commits.\n\nEnvironment: Development team\nReproduction: Review the last month's commit logs and code review histories."],
151
-
152
- ["The API documentation is outdated, leading to incorrect usage by developers.\n\nEnvironment: Online documentation portal\nReproduction: Compare the endpoint documentation against the latest API code base."],
153
- ["The current system architecture does not support horizontal scaling, which is necessary for handling increased loads.\n\nEnvironment: System architecture review\nReproduction: Analyse the current deployment and propose necessary changes for scalability."],
154
- ["Users experience data loss when the network connection is unstable during data transmission.\n\nEnvironment: Mobile app, unstable network conditions\nReproduction: Test the data sync feature under various network conditions."],
155
 
156
- ["The build fails intermittently on the CI server due to timing issues in test scripts.\n\nEnvironment: CI server Jenkins\nReproduction: Trigger the build process multiple times and note the occurrence of failures."],
157
  ["The regression tests do not cover scenarios involving concurrent user sessions.\n\nEnvironment: Test automation suite\nReproduction: Update the test scripts to include tests for concurrent sessions."],
158
  ["There is frequent miscommunication between the development and QA teams regarding feature specifications.\n\nEnvironment: Inter-team meetings\nReproduction: Audit recent communication logs and meeting notes between the teams."],
159
  ["The service-oriented architecture does not effectively isolate failures, leading to cascading failures across services.\n\nEnvironment: Microservices architecture\nReproduction: Simulate a service failure and observe the impact on other services."]
 
92
  for model_path, model in models.items():
93
  quality_name = get_quality_name(model_path)
94
  avg_prob = model_prediction(model, text, device)
95
+ if avg_prob >= 0.995: # Only consider probabilities >= 0.90
96
  results.append((quality_name, avg_prob))
97
  logging.info(f"Model: {model_path}, Quality: {quality_name}, Average Probability: {avg_prob:.3f}")
98
 
 
146
 
147
  example_texts = [
148
  ["The algorithm does not accurately distinguish between the positive and negative classes during edge cases.\n\nEnvironment: Production\nReproduction: Run the classifier on the test dataset with known edge cases."],
 
 
 
 
 
 
149
 
 
150
  ["The regression tests do not cover scenarios involving concurrent user sessions.\n\nEnvironment: Test automation suite\nReproduction: Update the test scripts to include tests for concurrent sessions."],
151
  ["There is frequent miscommunication between the development and QA teams regarding feature specifications.\n\nEnvironment: Inter-team meetings\nReproduction: Audit recent communication logs and meeting notes between the teams."],
152
  ["The service-oriented architecture does not effectively isolate failures, leading to cascading failures across services.\n\nEnvironment: Microservices architecture\nReproduction: Simulate a service failure and observe the impact on other services."]