Superliga stats & predictions

Introduction to Volleyball Superliga Croatia

The Croatian Volleyball Superliga stands as one of the most prestigious leagues in Europe, showcasing a high level of competition and skill. Tomorrow's matches are eagerly anticipated by fans and experts alike, promising thrilling encounters between top-tier teams. This guide provides an in-depth analysis of the upcoming matches, complete with expert betting predictions to help you make informed decisions.

Overview of Tomorrow's Matches

Tomorrow's schedule features some of the most exciting matchups in the league. Each game is not only a display of athletic prowess but also a strategic battle that can influence the standings significantly.

• Team A vs Team B: Known for their strong defense, Team A will face off against Team B's powerful offense.
• Team C vs Team D: A classic rivalry that promises intense competition and high stakes.
• Team E vs Team F: Both teams have been on a winning streak, making this match a must-watch.

Each match offers unique dynamics and potential outcomes, making them perfect for both casual viewers and seasoned bettors.

Detailed Match Analysis

Tactical Insights and Strategies

• Serving Strategies: Effective serves can disrupt opponents' formations and create scoring opportunities.
<|repo_name|>josephlewis1988/Stream-Analysis<|file_sep|RFID Tagging System ==================== This project contains two parts: 1) An RFID tag reader system written using Python 3. 2) An iOS application written using Swift 5. ## RFID Tag Reader The RFID tag reader is written using Python 3 and requires Python libraries `pyserial` (for serial communication) and `mysql.connector` (for database connection). The program reads RFID tags sent from an RC522 RFID module connected via USB-to-Serial cable. The program connects to MySQL database where it writes data about each tag read by RFID module. The program also reads from database where it retrieves data about each tag read by RFID module. ### Requirements - Python 3 - pyserial - mysql.connector ### Installation Clone or download repository files into local directory: bash git clone https://github.com/josephlewis1988/RfidTaggingSystem.git Install required Python packages: bash pip install pyserial mysql.connector ### Usage To run program use command below: bash python rfid_reader.py [database name] [database user] [database password] For example: bash python rfid_reader.py rfid_database root rootpassword12345 ## iOS Application This application was developed using Xcode version 11.6 running on macOS Catalina version 10.15.6.  ### Requirements - Xcode version 11.x or later (11.x recommended) - iOS Simulator or device running iOS version 13.x or later (13.x recommended) ### Installation Clone or download repository files into local directory: bash git clone https://github.com/josephlewis1988/RfidTaggingSystem.git Open `RfidTaggingSystem-iOS` folder within Xcode. ### Usage Build application within Xcode then run either on simulator or physical device.<|repo_name|>josephlewis1988/Stream-Analysis<|file_sep # Imports required modules/packages/libraries... import time import sys import serial import mysql.connector # Creates connection object with MySQL server... connection = mysql.connector.connect(host='localhost', database=sys.argv[1], user=sys.argv[2], password=sys.argv[3]) # Creates cursor object... cursor = connection.cursor() # Sets up serial port connection parameters... ser = serial.Serial('/dev/tty.usbmodem14201', baudrate=9600) ser.flushInput() # Function used when writing data to MySQL database... def writeToDatabase(rfid_tag): try: cursor.execute("INSERT INTO rfid_tags (rfid_tag) VALUES ('%s')" % rfid_tag) connection.commit() print("RFID tag added.") except: print("RFID tag already exists.") # Function used when reading data from MySQL database... def readFromDatabase(): try: cursor.execute("SELECT * FROM rfid_tags") results = cursor.fetchall() if len(results) == 0: print("No records found.") return None else: for row in results: print(row) except: print("No records found.") while True: # Loops continuously until program is terminated... rfid_tag = ser.readline().decode('utf-8').rstrip() # Reads line from serial port... if len(rfid_tag) != 0: if not rfid_tag.isdigit(): continue # Checks if string contains only numbers... if int(rfid_tag[:1]) == 0x02: writeToDatabase(rfid_tag[1:]) # Writes data to MySQL database... elif int(rfid_tag[:1]) == 0x03: readFromDatabase() # Reads data from MySQL database... time.sleep(0.5)<|repo_name|>josephlewis1988/Stream-Analysis<|file_sep Collins Joseph Lewis Project Title ============= RFID Tagging System Description =========== This project contains two parts: 1) An RFID tag reader system written using Python 3. 2) An iOS application written using Swift. ## Part One Part one consists of an RFID tag reader system written using Python. The program reads RFID tags sent from an RC522 RFID module connected via USB-to-Serial cable. The program connects to MySQL database where it writes data about each tag read by RFID module. The program also reads from database where it retrieves data about each tag read by RFID module. ## Part Two Part two consists of an iOS application written using Swift. This application allows users to add new tags into database as well as view existing tags stored within database. Application also allows users delete tags from within table view as well as clear all existing entries stored within table view. Users may also view all existing entries stored within table view which are currently active at time they press "View All" button. Users may also search for specific entry stored within table view which matches search query entered into text field above table view. Application uses Core Data framework which stores entries locally on device so no internet connectivity required when accessing app functions. <|repo_name|>josephlewis1988/Stream-Analysis<|file_sepKwadwoOkyereBonsu/CS301-FinalProject<|file_sep|RFID-TAGGED-WARDROBE-BLOCKCHAIN-SOLUTIONS| ================================================= A blockchain solution for tracking lost items based off RFID technology Installation Instructions: -------------------------- **Pre-requisites:** Make sure you have installed node.js , npm , yarn , truffle globally **Step-by-step instructions** * Clone this repo git clone https://github.com/KwadwoOkyereBonsu/CS301-FinalProject.git * Navigate inside cloned repo cd CS301-FinalProject * Install dependencies yarn install * Run Truffle migrations truffle migrate * Start Ganache GUI ganache-cli * Start server node server.js Visit http://localhost:3000 Front-end Codebase Structure: ------------------------------ ├── package.json ├── public │   ├── favicon.ico │   └── index.html ├── src │   ├── App.css │   ├── App.js │   ├── App.test.js │   ├── index.css │   ├── index.js │   └── register.css └── yarn.lock Smart Contract Codebase Structure: ----------------------------------- contracts/ migrations/ test/ truffle-config.js Other Files / Folders: ----------------------- All other files/folders are ignored by gitignore file because they're needed only while developing this app Important Files/Folders Description: ------------------------------------ **Server related files** server.js : Express server file containing all API endpoints used by React front-end app **Smart contract related files** truffle-config.js : Configuration file used while deploying smart contracts onto ganache network **React front-end related files** App.js : Main react component containing all other components rendered onto browser window How To Use The App? ------------------- Step-by-step instructions are provided below : 1.) Go through installation instructions provided above 2.) Open Ganache GUI & start it up (Make sure you've started Ganache CLI too ) 3.) Visit http://localhost:3000 & sign up / login with any account created inside ganache gui 4.) Create new Wardrobe item & assign it your unique id number 5.) Search for your wardrobe item again & see details including location history etc ... Additional Features Implemented : --------------------------------- * We've implemented some additional features like showing locations visited by wardrobe item after its creation * We've implemented some additional security checks like checking whether user logged-in is same user who created wardrobe item etc ... * We've implemented some additional error handling code snippets like checking whether wardrobe item already exists etc ... Known Bugs / Issues : --------------------- We were unable to implement feature that allowed us transfer ownership over wardrobes between different accounts because we ran out of time Future Improvements : --------------------- We plan improve our codebase further so we'll be able implement transfer ownership feature mentioned above <|file_sep const WardrobeContract = artifacts.require('./Wardrobe.sol'); const assert = require('assert'); contract('Wardrobe Contract Tests', function(accounts){ beforeEach(async function(){ // Deploying new contract before every test case gets executed ... this.wardrobeContract = await WardrobeContract.new(); }); describe('Testing Wardrobe Contract', function(){ it('Test creating wardobe should fail if user tries creating multiple wardrobes with same ID', async function(){ // Creating first wardrobe ... await this.wardrobeContract.createWardrobe(12345678901234567890,{from : accounts[0]}); try{ // Creating second wardrobe ... await this.wardrobeContract.createWardrobe(12345678901234567890,{from : accounts[0]}); assert(false); }catch(error){ assert(true); } }); it('Test creating wardobe should pass if user creates multiple wardrobes with different IDs', async function(){ // Creating first wardrobe ... await this.wardrobeContract.createWardrobe(12345678901234567890,{from : accounts[0]}); try{ // Creating second wardrobe ... await this.wardrobeContract.createWardrobe(98765432109876543210,{from : accounts[0]}); assert(true); }catch(error){ assert(false); } }); it('Test getting owner should return expected result after creating wardobe', async function(){ // Creating first wardrobe ... await this.wardrobeContract.createWardrobe(12345678901234567890,{from : accounts[0]}); let ownerAddress = await this.wardrobeContract.getOwner.call(12345678901234567890); assert.equal(ownerAddress,'0x18E14A6aFe89459bEAab703036EdcfAC75C53aDe'); }); it('Test getting description should return expected result after creating wardobe', async function(){ }); }); });<|repo_name|>KwadwoOkyereBonsu/CS301-FinalProject<|file_sep Thurs June 18th Meeting Minutes Meeting Agenda: 1.) Discuss previous week meeting minutes ... Attendees: Collin Beckman, Kwadwo Okyere-Bonsu, Saurabh Patel, Sara Shafiq, Zachary Peterson Meeting Notes: Last week meeting minutes were discussed thoroughly ... No issues were found hence everyone agreed upon them ... Next Steps: Continue working towards final submission deadline ... Next Meeting Date: Friday June 26th @12pm CST Any Other Business: None ... Meeting Adjourned.<|repo_name|>KwadwoOkyereBonsu/CS301-FinalProject<|file_sep Wednesday June 23rd Meeting Minutes Meeting Agenda: 1.) Discuss previous week meeting minutes ... Attendees: Collin Beckman, Kwadwo Okyere-Bonsu, Saurabh Patel, Sara Shafiq, Zachary Peterson Meeting Notes: Last week meeting minutes were discussed thoroughly ... No issues were found hence everyone agreed upon them ... Next Steps: Continue working towards final submission deadline ... Next Meeting Date: Thursday June 24th @12pm CST Any Other Business: None ... Meeting Adjourned.<|repo_name|>KwadwoOkyereBonsu/CS301-FinalProject<|file_sep ADHD Final Project Proposal Document | BlockChain Solution For Tracking Lost Items Using RFDI Technology | ========================================================================================================================== Collin Beckman | Kwadwo Okyere-Bonsu | Saurabh Patel | Sara Shafiq | Zachary Peterson Proposal Document Contents: I.) Project Title : BlockChain Solution For Tracking Lost Items Using RFDI Technology II.) Problem Statement : As we know today people usually lose there stuff very often especially clothes these days because many people buy more clothes than what they need .... Losing clothes becomes even more frequent during events like Halloween , weddings etc .... When people lose there clothes they get really upset since they spent quite alot money buying those clothes .... Some people even end up buying duplicate clothes just so they don't feel bad about losing old ones .... This wastes alot money hence we decided making something that can help solve problem associated with losing stuff especially clothes .... III.) Proposed Solution : Our proposed solution involves building web-app using following tech-stack : Backend Tech Stack : NodeJS + ExpressJS + Webpack + Mocha + Chai + Truffle Framework + Ganache CLI + Solidity Language Frontend Tech Stack : ReactJS + Redux IV.) Project Timeline : We plan finishing our project around mid-June since we're going back home next month hence we won't have enough time working remotely once we're back home .... So our goal is finishing our project around mid-June so we'll have enough time fixing bugs , testing codebase thoroughly etc ... V.) Milestones : Week Ending June , July , August : Complete development phase including coding entire web-app according to requirements specified above Week Ending September : Finishing touches including bug fixes , adding unit tests etc ... VI.) Deliverables : Working prototype demo video demonstrating how web-app works VII.) Additional Information : Additional information regarding our proposal document can be found here --> https://docs.google.com/document/d/1HJzQoG9nXgNcLqk_5gU7lFtuyNvV95PnCgZDgLLpgYs/edit?usp=sharing Final Submission Date : June End Any Questions Regarding Our Proposal Document ? Feel free asking questions regarding proposal document anytime during office hours <|repo_name|>KwadwoOkyereBonsu/CS301-FinalProject<|file_sep Likert Scale Survey Results | =================================== Name | Email Address | Role In Group | Likert Scale Survey Responses | Collin Beckman | [email protected] | Full Time Student Developer | Strongly Agree | Kwadwo Okyere-Bonsu | [email protected] | Full Time Student Developer | Strongly Agree | Saurabh Patel | [email protected] | Full Time Student Developer | Strongly Agree | Sara Shafiq | [email protected] | Full Time Student Developer | Strongly Agree | Zachary Peterson [email protected] Full Time Student Developer Strongly Agree | Survey Questions Asked During Likert Scale Survey: Do you believe your group members contributed equally? Yes! Everyone contributed equally throughout entire duration starting from ideation phase until final submission phase ... Everyone participated actively during meetings discussing ideas sharing opinions etc .... Are you satisfied with your group members? Yes! Everyone did great job contributing equally throughout entire duration starting from ideation phase until final submission phase ... Everyone participated actively during meetings discussing ideas sharing opinions etc .... Did your group work together effectively? Yes! Everyone did great job contributing equally throughout entire duration starting from ideation phase until final submission phase ... Everyone participated actively during meetings discussing ideas sharing opinions etc .... Did your group communicate effectively? Yes! Everyone did great job contributing equally throughout entire duration starting from ideation phase until final submission phase ... Everyone participated actively during meetings discussing ideas sharing opinions etc .... Were conflicts resolved effectively? There weren't any conflicts arising throughout entire duration starting from ideation phase until final submission phase hence conflicts didn't need resolving .... If conflicts arose then everyone would've worked together collaboratively solving conflicts efficiently since everyone contributed equally throughout entire duration starting from ideation phase until final submission phase ... Was workload distributed fairly among group members? Everyone did great job contributing equally throughout entire duration starting from ideation phase until final submission phase ... Everyone participated actively during meetings discussing ideas sharing opinions etc .... Is there anything else you'd like us know regarding how your group worked together? Nothing else needs mentioning since everyone did great job contributing equally throughout entire duration starting from ideation phase until final submission phase ...... If yes please explain here..... Thank You! Final Submission Date : June End <|repo_name|>KwadwoOkyereBonsu/CS301-FinalProject<|file_sep Mickael Muthucumarana Final Project Presentation Slides | ===================================================================== Mickael Muthucumarana Final Project Presentation Slides Contents: Slide Number One Slide Content: Slide Number Two Slide Content: Slide Number Three Slide Content: Slide Number Four Slide Content: Slide Number Five Slide Content: Slide Number Six Slide Content: Slide Number Seven Slide Content:
 Slide Number Eight Slide Content:
 Slide Number Nine Slide Content:
 Slide Ten Slide Content:
 Slide Eleven Slide Content:
 Slide Twelve Slide Content:
 Final Submission Date : June End <|repo_name|>KwadwoOkyereBonsu/CS301-FinalProject<|file_sep **Week Ending May Week One Meeting Minutes** Meeting Agenda: 1.) Discuss initial proposal document submitted last week ... Attendees: Collin Beckman, Mickael Muthucumarana, Sara Shafiq, Saurabh Patel, Zachary Peterson Meeting Notes: Initial proposal document submitted last week was discussed thoroughly amongst team members present today . It was decided that proposed solution presented inside initial proposal document seems good enough but requires few minor changes/improvements before moving forward . After thorough discussion amongst team members present today following changes/improvements were suggested for proposed solution presented inside initial proposal document :- Proposed Frontend Tech Stack Should Be Changed From React To Angular Since Angular Provides Better User Interface Components Compared To React Which Will Result In Better User Experience For Users Visiting Our Website Using Frontend Web App . Proposed Backend Tech Stack Should Be Changed From NodeJS To Django Since Django Is More Secure Compared To NodeJS Plus Django Comes With Built-In Authentication Feature Which Can Save Us Lot Of Development Time Since We Won't Need To Build Authentication Feature From Scratch . Proposed Blockchain Smart Contract Language Should Be Changed From Solidity To Vyper Since Vyper Is More Secure Compared To Solidity Plus Vyper Is Written In Python Which Will Allow Us Reuse Code Snippets Written Inside Backend Codebase If Needed . These Changes Were Agreed Upon By All Members Present Today Hence Initial Proposal Document Will Be Updated According To These Changes Before Next Meeting Where We Plan Discuss How Our Proposed Solution Works In Detail Starting From Ideation Phase Until Final Submission Phase . Next Steps: Update initial proposal document according changes/improvements suggested above before next meeting where we plan discuss how our proposed solution works in detail starting form ideation phase until final submission phase . Next Meeting Date: Wednesday May Week Two @12pm CST Any Other Business: None ... Meeting Adjourned.


**Week Ending May Week Two Meeting Minutes** Meeting Agenda: 1.) Discuss updated initial proposal document submitted last week ... Attendees: Collin Beckman, Mickael Muthucumarana, Sara Shafiq, Saurabh Patel, Zachary Peterson Meeting Notes: Updated initial proposal document submitted last week was discussed thoroughly amongst team members present today . It was decided that updated proposed solution presented inside updated initial proposal document seems good enough but requires few minor changes/improvements before moving forward . After thorough discussion amongst team members present today following changes/improvements were suggested for updated proposed solution presented inside updated initial proposal document :- Proposed Frontend Tech Stack Should Include Redux Since Redux Provides Global State Management Across Entire React Component Tree Which Will Allow Us Easily Access State Across Entire React Component Tree Without Passing Props Downwards Through Several Components In React Component Tree . Proposed Backend Tech Stack Should Include Postgresql As Database Since Postgresql Is More Secure Compared To SQLite Plus Postgresql Allows Concurrent Access By Multiple Users At Once Which Will Allow Multiple Users Accessing Our Website Simultaneously Without Any Performance Issues . These Changes Were Agreed Upon By All Members Present Today Hence Updated Initial Proposal Document Will Be Updated According To These Changes Before Next Meeting Where We Plan Start Building Prototype Based On Updated Proposed Solution Presented Inside Updated Initial Proposal Document . Next Steps: Update updated initial proposal document according changes/improvements suggested above before next meeting where we plan start building prototype based on updated proposed solution presented inside updated initial proposal document . Next Meeting Date: Wednesday May Week Three @12pm CST Any Other Business: None ... Meeting Adjourned.


**Week Ending May Week Three Meeting Minutes** Meeting Agenda: 1.) Discuss prototype built based off updated proposed solution presented inside updated initial proposal document submitted last week ... Attendees: Collin Beckman, Mickael Muthucumarana, Sara Shafiq, Saurabh Patel, Zachary Peterson Meeting Notes: Prototype built based off updated proposed solution presented inside updated initial proposal document submitted last week was discussed thoroughly amongst team members present today . It was decided that prototype built seems good enough but requires few minor changes/improvements before moving forward . After thorough discussion amongst team members present today following changes/improvements were suggested for prototype built :- Frontend Prototype Needs Few Minor Tweaks Here And There Including Styling Related Tweaks Like Color Scheme Used Throughout Entire Frontend Prototype Needs Changing Because Current Color Scheme Looks Kind Of Drab And Doesn't Look Very Appealing Visually Speaking . Backend Prototype Needs Few Minor Tweaks Here And There Including Security Related Tweaks Like Adding Rate Limiting Middleware So That Malicious Users Won't Be Able Spamming Our Website With Too Many Requests At Once Plus Adding HTTPS Support So That Data Sent Between Client And Server Over Internet Isn't Sent Over Plain Text But Instead Sent Over Encrypted Form Thus Making It Much Harder For Malicious Third Parties Trying Intercept Data Sent Between Client And Server Over Internet. These Changes Were Agreed Upon By All Members Present Today Hence Prototype Built Will Be Tweaked According To These Changes Before Next Meeting Where We Plan Thoroughly Test Prototype Built Including Writing Unit Tests For Backend Codebase . Next Steps: Tweak prototype built according changes/improvements suggested above before next meeting where we plan thoroughly test prototype built including writing unit tests for backend codebase . Next Meeting Date: Wednesday May Week Four @12pm CST Any Other Business: None ... Meeting Adjourned.


**Week Ending May Week Four Meeting Minutes** Meeting Agenda: 1.) Discuss prototype tweaked according changes/suggestions made after discussing prototype initially submitted last week plus discuss unit tests written after thoroughly testing tweaked prototype ... Attendees: Collin Beckman , Mickael Muthucumarana , Sara Shafiq , Saurabh Patel , Zachary Peterson Meeting Notes: Prototype tweaked according changes/suggestions made after discussing prototype initially submitted last week plus unit tests written after thoroughly testing tweaked prototype seemed good enough hence no major/minor tweaks needed anymore besides few small tweaks here and there mostly related styling concerns which doesn't affect functionality whatsoever so these small tweaks will be done later once major/minor tweaks needed affecting functionality aren't needed anymore plus these small tweaks mostly related styling concerns doesn't affect functionality whatsoever so these small tweaks won't affect functionality whatsoever either. After Thorough Discussion Amongst All Members Present Today Following Additional Suggestions Were Made Regarding Tweaked Prototype Submitted Last Week Plus Unit Tests Written After Thoroughly Testing Tweaked Prototype :- Prototype Needs Few Small Styling Related Tweaks Here And There Including Changing Font Type Used Throughout Entire Frontend Prototype Because Current Font Type Looks Kind Of Drab And Doesn't Look Very Appealing Visually Speaking Plus Changing Font Size Used Throughout Entire Frontend Prototype Because Current Font Size Seems Too Big Or Too Small Depending On Device Screen Size Used Viewing Frontend Prototype. Prototype Also Needs Few Small Functional Related Tweaks Here And There Including Adding Login Logout Functionality So That Only Authorized Users Can View Certain Pages Within Frontend Prototype Because Currently Anyone Can View Any Page Within Frontend Prototype Regardless Of Whether They're Authorized Or Not. Unit Tests Written After Thoroughly Testing Tweaked Prototype Also Needs Few Small Tweeks Here And There Including Adding Coverage Report Tool Like Istanbul So That Developers Can See What Percentage Of Lines Of Code Are Being Tested By Unit Tests Written After Thoroughly Testing Tweaked Prototype Because Currently Developers Don't Know What Percentage Of Lines Of Code Are Being Tested By Unit Tests Written After Thoroughly Testing Tweaked Prototype. These Additional Suggestions Were Agreed Upon By All Members Present Today Hence Additional Small Tweeks Will Be Done According To These Additional Suggestions Before Next Meeting Where We Plan Begin Writing Detailed Documentation Describing How Our Proposed Solution Works Starting From Ideation Phase Until Final Submission Phase . Next Steps: Do Additional Small Tweeks According Additional Suggestions Made During Today's Meet Up Before Next Meet Up Where We Plan Begin Writing Detailed Documentation Describing How Our Proposed Solution Works Starting From Ideation Phase Until Final Submission Phase. Next Meet Up Date: Thursday May Week Five @12pm CST Any Other Business: None... Meet Up Adjourned.











**Week Ending May Week Five Meet Up Minutes** Meet Up Agenda: Discuss detailed documentation describing how our proposed solution works starting form ideation phasr untill final submisison phasr documented last meet up date plus discuss survey results obtained after conducting survey among classmates regarding how effective groups worked together plus discuss likert scale survey results obtained after conducting likert scale survey among ourselves regarding how effective groups worked together. Meet Up Attendees: Collin Beckman, Mickael Muthucumarana, Sara Shafiq, Saurabh Patel, Zachary Peterson. Meet Up Notes: Detailed documentation describing how our proposed solution works starting form ideation phasr untill final submisison phasr documented last meet up date seemed good enough besides few minor typos/errors spotted while reviewing documentation detailed documentation describing how our proposed solution works starting form ideatoin phasr untill final submisison phasr documented last meet up date seemed good enough besides few minor typos/errors spotted while reviewing documentation detailed documentation describing how our proposed solutioon works starting form ideatoin phasr untill final submisison phasr documented last meet up date seemed good enough besides few minor typos/errors spotted while reviewing documentation detailed documentation describing how our proposed solutioon works starting form ideatoin phasr untill final submisison phasr documented last meet up date seemed good enough besides few minor typos/errors spotted while reviewing documentation detailed documentation describing how our propsoed solutioon works starting form ideatoin phasr untill finall submisison phasr documented last meet up date seemed good enough besides few minor typos/errors spotted while reviewing documetnation. Survey Results Obtained After Conducting Survey Among Classmates Regarding How Effective Groups Worked Together Spotted Few Concerns Regarding How Effective Groups Worked Together Among Classmates Who Took Survey Concerning How Effective Groups Worked Together Especially Concerning Conflicts Resolution Among Group Members Plus Concerns Reguarding Workload Distribution Among Group Members Since Most People Believed Workload Wasn't Distributed Fairly Among Group Members Although Some People Believed Group Members Contributed Equally While Others Believed Some Group Members Contributed More Than Others While Still Others Believed Some Group Members Contributed Less Than Others Although Most People Believed Group Communicated Effectively While Still Others Believed Communication Wasn't Effective Enough Although Most People Said They Weren'T Satisfied With Group While Still Others Said They Weren'T Satisfied With Certain Individuals Within Group Even Though Most People Said They Believed Their Groups Contributed Equally While Still Others Said They Didn'T Believe Their Groups Contributed Equally Although Most People Said Conflicts Weren'T Resolved Effectively While Still Others Said Conflicts Weren'T Resolved At All Even Though Most People Said Workload Wasn'T Distributed Fairly Among Group Members While Still Others Said Workload Was Distributed Fairly Among Group Members Even Though Most People Said Groups Worked Effectively While Still Others Said Groups Didn'T Work Effectively Even Though Most People Didn'T Believe Their Groups Communicated Effectively While Still Others Believed Their Groups Communicated Effectively Even Though Most People Didn'T Believe Their Groups Resolved Conflicts Effectively While Still Others Believed Their Groups Resolved Conflicts Effectively Even Though Most People Didn'T Believe Their Groups Distributed Workload Fairly Among Group Members While Still Others Believed Their Groups Distributed Workload Fairely Among Group Members Even Though Most People Didn'T Believe Their Groups Contributed Equally While Still Others Believed Their Groups Contributed Equally Even Though Most People Didn'T Believe They Weren'Satisfied With Their Own Personal Contribution Within Own Personal Own Personal Personal Personal Personal Personal Personal Personal Personal Personal Personnal Personnal Personnal Personnal Personnal Personnal Personnal Personnal Persons Own Own Own Own Own Own Own Own Own OwngroupsssssssssssssssssssssssEven Though Majority Opinion About How Effective Various Different Different Different Different Different Different Different Different Different Different Different Diffrent Diffrent Diffrent Diffrent Diffrent Diffrent Diffrent Diffrent Differnt Differnt Differnt Differnt Differnt Differnt Differences Within Various Various Various Various Various Various Various Varous Varous Varous Varous Varous Varous Varous Varous Variouseveralseveralseveralseveralseveralseveralseveralseveralseveralseveralseveralseveralseveralseveralseveralgroupsvariousdifferentdifferentdifferentdifferentdifferentdifferentdifferentdifferentdifferrntdifferrndifferrndifferrndifferrndifferrndifferrndifferrndifferrndiffrrnvariousvariousvariousvariousvariousvariousvariousvariouseventhoughmajorityopinionabouthoweffectivetheseveralgroupswerewhenaskedsurveycarriedoutamongclassmatesregardinghoweffectivetheirgroupsworktogetherwasdividedamongclassmatesintothreecategoriesnamelyyesnoandundecidedwhereyesindicatedthatpeoplebelieveitwasveryeffectiveandnoindicatedthatpeoplebelieveitwasnotveryeffectiveandundecidedindicatedthatpeopleareunsurewhetheritwasveryeffectiveornotwithrespecttoconflictresolutionamonggroupmemberstheanswersthatcameforthefromsurveywereoneofeachwhereonepersonbelieveithastoworkeffectivleyresolvingconflicsthwileanotherpersonbelieveithastoworkineffectivleyresolvingconflicsthwileonepersonisunsurewhetherithasworkineffectivleyresolvingconflicstheresultsobtainedafterconductingsurveyregardinghoweffectiveworkloadisdistributedamonggroupmembersamongclassmateswhorespondedsurveyobtainedresultshowingsomepeoplebelieveitsfairothersbelievetheirequallyandstillotherbelievetheirunfairalthoughmostpeoplebelieveitsfairsomepeoplebelieveitheirunfaireventhoughmostpeoplebelieveitisfairothersbelieveitheirunfairwithrespecttowhethergroupsworkeffectivelyoreffectivleygroupsworksomepeoplebelievetheywork