Problems During The Projects

From SFTropes
Jump to: navigation, search

This page is designed for groups to share any problems they ran into during group meetings, filming, development, etc. This page will help groups to learn more about teamwork and make all the students better group members for future classes.

Contents

Section A5

Group 1

I am in the A5 Group 1 section, and during our project the main problem that we encountered was unequal dilligence. As humans have varying degrees of willingness to work in groups, I expected that some members would end up doing more than others. However, in our group the distribution was outrageous. Essentially three out of five members doing all the work.

Apart form the differences in group members, the project was mostly a success. The 2 major problem we encountered in making our hackintosh was regarding it's CD Bootloader dependence and Audio Drivers. The Hackintosh will not boot independent from the TonyMacx86 boot loader from the CD drive. This was primarily due to the Chameleon bootloader's incorrect install which included with it Nvidia inject drivers for our ATI card that causes a partial kernel panic (Equivalent to a computer seizure). Chameleon has to be reinstalled but with a fresh install of the OS. Our next problem was the lack of fully functional audio ports. The PC came with 5.1 surround sound with digital out, but the only functioning output was the headphone jack stereo out. That too was a bit flaky. Everything else was 100% functioning.

Group 2

Our group had a few scheduling conflicts.  Because of two athletes in the group, late meetings and meetings without the whole group were often the case with us.  Nevertheless, when everyone could meet, we did, and even when only a few of us could meet, we still made progress.  We also designated work to everyone regardless of their attendance to these meetings to make everyone have a fair share of work.

Group 3

Group 4

Group 5

Our group ran into our own set of complications throughout the project., The first major problem we ran into was the fact that no one in our group had any computer hacking or various other useful computer skills. This caused us to have almost no idea of what we were going to do for the project at all. The second problem we ran into was scheduling conflicts. There were times when we would set up meetings, but at the last minute had to cancel them due to someone not being able to make it to the meeting. When we had finally decided on building a Rube Goldberg machine, the problem came up that we did not have the tools at school to be able to build the project at school, so we came to an agreement that I would build the project myself because i had access to all of the necessary tools and other materials needed while the other group members would continue to edit the blog and complete the badges. While building the machine, even more complications arose when the elements of the machine that we had planned on incorporating would not properly function in the way that we had initially intended to use them. After that, the design of the machine had to be extremely simplified from it's original state. After the machine was built, we ran into further complications during the presentation. At the hacker convention, when we demonstrated the machine, it did not work properly during any run of it, and then right before the final demonstration one of the marbles was lost, so the machine could not function any longer. I also came into problems while editing the videos for the final artifact. The movie making program that I was using crashed on me about 7 times, and had to redo a substantial amount of work.

Section J6

Group 1

First of all we lost one of our group members that would have been a great help working with our game. After that Alena was the only one who could code and that made her the only one of us able to work on the actual game. Another one of our problems was that it was hard for us to find a time when all of us could sit down and work on the project together. Instead everybody did their own thing and because of that it became harder to put everything together as one when it was time to present our work.

Now when I thin about it I think the fact that we chose to create something that only one person in our group really knew anything about was our biggest mistake. I think most people in the group wanted to help but felt totally useless when it came to coding. It is not something that you can just learn how to do over a night and therefore it was hard to make our group project a actual GROUP project.

Group 2

Group 3

Group 4

Group 5

The biggest problem we endured was giving our chatterbot sentience. We didn't seem to know how to program it the way that would make the user think it was a real person who was speaking through instant messaging. Once we figured out how to program the bot, the next step was how to start a conversation and keep it going without the user going on a tangent. We had to keep the conversation going the way we wanted it to go. That was the biggest problem with out project.

Section B6

Group 1

I think that the main problems that we ran into as a group were that we weren't in touch much outside of class and sometimes roles got confused. However, we eventually found a way to work that was effective and did well on the project, though the coding wasn't quite as presentation ready as we had hoped. Overall though things went well.

Another problem occurred during our development is choosing communication tools. Email is a good way to communicate with each other but not the best way. Using google docs to collaborate on the badge applications is one of the most successful way to communicate. However, on the code side, gitorious is not the best way to share code with each other. Promoting the Dropbox is great, but we didn't fully use Dropbox, kind of working on our own.

Group 2

Group 3

Our group had problems dividing responsibilities amongst each other. Some members did much of the hard technical work, while others simply wrote badge applications, and not many at that. We should have assigned concrete roles from the beginning to correct this issue.

Group 4

Group 5

We ran into problems implementing the facebook AI. We were able to get it working within the frame required by facebook, and had a few sample things going; but we couldn't figure out a way to get the facebook API to recognize our code the way it should-- in effect, we could write all the code that we wanted, but it wouldn't do anything because we couldn't like the facebook API with our code. This lead to us having a very primitive application.

Personal tools