May 4 - 10
In the last week of classes the testing group and I worked on getting recognition data through a Sousa study. The goal was to collect as much data as possible in order to help us with future analysis of recognition to achieve some improvement in this area. The study was set up by Kim, and we set up a day for testing. We sent emails to students in the department who would be interested in voluteering, and some others from certain classes who were looking for extra credit opportunities could also participate. It was a 10 min study where participants just had to draw figures including arrows, triangles, trusses, circles, etc. I decided that it would also be a good idea posting the link of the survey in Facebook. Majority of my friends on Facebook are college aged students from different career backgrounds, so this would provide variety to the study.
Link to they survey: http://srlweb.cs.tamu.edu/srlng/sousa/study/perform/187
Unfurtnunately, this was my last week collaborating with the group. This summer I will be starting an internship with Dell at Round Rock, TX. I am really excited and looking foward for this experience. In this semester I have learned many things towards the reasearch field. I have learned how a project such as Mechanix is handled, from its development, to how is tested and planning of programs where it can be used; to how to obtain funding, what is needed to present it in different conferences, and many more things. I want to thank Dr. Hammond for giving me this opportunity and the team for their help and guidance. You all made this a great semester for me! Thanks.
Friday, May 27, 2011
April
March 30 - April 5
At the beginning of this week I continued working on measurements testing. Now, drawing some formal stats on the correctness of the code. Even though I was having some trouble with set up issues, I was able to get some useful data. The next half of the week I attended SCOLA, Student Conference on Latino Affairs here at A&M, this took up almost all of time, so I was not able to get much more done.
April 6 - 12
April 13 - 19
April 20 - 26
This week, I helped out Kourtney doing some testing sessions with different participants for the measurement part of the code. She was assigned to write a paper about it, so we set up a survey and a testing session to contribute with the information for the document. Even though we had some difficulties, since the most updated code was not in the stable branch yet, thus not available online, we had to run Mechanix from our computers.
April 27 - May 3
At the beginning of this week I continued working on measurements testing. Now, drawing some formal stats on the correctness of the code. Even though I was having some trouble with set up issues, I was able to get some useful data. The next half of the week I attended SCOLA, Student Conference on Latino Affairs here at A&M, this took up almost all of time, so I was not able to get much more done.
April 6 - 12
April 13 - 19
April 20 - 26
This week, I helped out Kourtney doing some testing sessions with different participants for the measurement part of the code. She was assigned to write a paper about it, so we set up a survey and a testing session to contribute with the information for the document. Even though we had some difficulties, since the most updated code was not in the stable branch yet, thus not available online, we had to run Mechanix from our computers.
April 27 - May 3
Thursday, May 26, 2011
March
March 2 - 8
This week I went back to testing. The area that I focused the most was in the recognition of the more complicated trusses. However, I would still go through the complete process of the problems in order to review or be in the look out for any other bugs or small things that could be improved. During the testing, I would try to pay attention in the steps that I was drawing the images, and making note of which ways would cause most trouble.
March 9 - 15
At the beginning of the week, the testing group and I started looking into the measurements part that Kourtney has being working on. Up to now she was the only one testing this code as she was writing it, but now we are stepping in in order to help her out and report to her any other bugs or problems that we would find. The other half of this week was Spring Break.
March 16 - 22
The first half of this week was Spring Break, however during this couple of days, I worked for a bit in getting some images ready for Dr. Hammond, since she was submitting a poster about Mechanix. This was also a very new experience for me, since I had never worked in something like this. Even though my contribution wasn't huge, I'm still happy that I am now more familiar with this process.
March 23 - 29
After Spring Break, we continued testing for measurements. We met a couple of times with the rest of the testers and Kourtney in order to understand better her code and be able to test effectively. Some of the problems we found were that some extra lines were appearing, and an old piece of code was interfering with her code, so some 'Z' lines would appear in between the measurement lines.
This week I went back to testing. The area that I focused the most was in the recognition of the more complicated trusses. However, I would still go through the complete process of the problems in order to review or be in the look out for any other bugs or small things that could be improved. During the testing, I would try to pay attention in the steps that I was drawing the images, and making note of which ways would cause most trouble.
March 9 - 15
At the beginning of the week, the testing group and I started looking into the measurements part that Kourtney has being working on. Up to now she was the only one testing this code as she was writing it, but now we are stepping in in order to help her out and report to her any other bugs or problems that we would find. The other half of this week was Spring Break.
March 16 - 22
The first half of this week was Spring Break, however during this couple of days, I worked for a bit in getting some images ready for Dr. Hammond, since she was submitting a poster about Mechanix. This was also a very new experience for me, since I had never worked in something like this. Even though my contribution wasn't huge, I'm still happy that I am now more familiar with this process.
March 23 - 29
After Spring Break, we continued testing for measurements. We met a couple of times with the rest of the testers and Kourtney in order to understand better her code and be able to test effectively. Some of the problems we found were that some extra lines were appearing, and an old piece of code was interfering with her code, so some 'Z' lines would appear in between the measurement lines.
February
Feb 2 - 8
After having the code for the project in my computer, I started familiarizing myself to the code. Not an easy task, since there is a lot of work that has been done previously and I had never worked with such a project before. It was really interesting to see applied in something running everything that I have learned in the classroom. During this week, I started running Mechanix and going through some of the set of problems that were available in order to understand how it works from the console, so that I could better understand the code and how it is organized.
Feb 9 - 15
At the end of last week, I was assigned to do some testing along with Alyssa, who has been contributing to Mechanix for the past couple of semesters. Our goal was to start some kind of testing system and maybe set up a more formal way of reporting bugs. During this week, the team's focus was to fix as many bugs as possible, since testing sessions with around the corner. We set up two Google docs, one is a Testing Document guide for future testing reference. We give detailed instructions of specific aspects of the program that need to be tested and the procedure that the tester should follow. The other document was a log, of what instances of testing each one of us was doing. The bugs we would find, we would add them to bug list that was previously set up so that everyone would be aware of what needed to be done.
Feb 16 - 22
This week we had a couple of testing sessions with ME students. I volunteered to be present during the session to help out students as well as noting any problems and bugs that they would face. One of the main problems that we had was the server going down when all students were working, and the program would just freeze, once the server was up, students were more likely to loose their work. This caused some frustration on students... It was a good experience to participate in the session since I got to learn and reflect on the process that it takes for a software to be ready for publication. I mean, the team has worked for quiet some time in this project, and it seems like it is a lot, but once you present it to students, they just see what is not working... It was a good lesson for me to learn.
Feb 23 - March 1
During this week I prepared for hosting a testing session with ME students on my own. No one else was going to be able to make it, so I had to prepare to know what to do in case something went wrong. The most important thing was know how to bring the server back up if something happened, and know how to answer to students' questions. The session went fine, the server did not give trouble until almost the end, but I was able to bring it back up. I was really nervous at first, since I have only participated with the project for a couple of weeks, but it went great.
After having the code for the project in my computer, I started familiarizing myself to the code. Not an easy task, since there is a lot of work that has been done previously and I had never worked with such a project before. It was really interesting to see applied in something running everything that I have learned in the classroom. During this week, I started running Mechanix and going through some of the set of problems that were available in order to understand how it works from the console, so that I could better understand the code and how it is organized.
Feb 9 - 15
At the end of last week, I was assigned to do some testing along with Alyssa, who has been contributing to Mechanix for the past couple of semesters. Our goal was to start some kind of testing system and maybe set up a more formal way of reporting bugs. During this week, the team's focus was to fix as many bugs as possible, since testing sessions with around the corner. We set up two Google docs, one is a Testing Document guide for future testing reference. We give detailed instructions of specific aspects of the program that need to be tested and the procedure that the tester should follow. The other document was a log, of what instances of testing each one of us was doing. The bugs we would find, we would add them to bug list that was previously set up so that everyone would be aware of what needed to be done.
Feb 16 - 22
This week we had a couple of testing sessions with ME students. I volunteered to be present during the session to help out students as well as noting any problems and bugs that they would face. One of the main problems that we had was the server going down when all students were working, and the program would just freeze, once the server was up, students were more likely to loose their work. This caused some frustration on students... It was a good experience to participate in the session since I got to learn and reflect on the process that it takes for a software to be ready for publication. I mean, the team has worked for quiet some time in this project, and it seems like it is a lot, but once you present it to students, they just see what is not working... It was a good lesson for me to learn.
Feb 23 - March 1
During this week I prepared for hosting a testing session with ME students on my own. No one else was going to be able to make it, so I had to prepare to know what to do in case something went wrong. The most important thing was know how to bring the server back up if something happened, and know how to answer to students' questions. The session went fine, the server did not give trouble until almost the end, but I was able to bring it back up. I was really nervous at first, since I have only participated with the project for a couple of weeks, but it went great.
January
January 26 - February 1
During the first week, I worked in setting up the required accounts, software and tools. I downloaded Github and TortoiseGit to set up the repository on windows. Since the project is written in Java, I also set up Eclipse since it seemed to be the most useful for me and I was already familiar with it from previous class work. I also got to run Mechanix on my computer from the code as well as from the demo links. Being this my first interaction and experience joining a research project, there was a lot of new things to learn. For starters, I had never used a repository before. So the process of setting everything up may sound easy and quick, but there were many things I needed to get familiar with.
During the first week, I worked in setting up the required accounts, software and tools. I downloaded Github and TortoiseGit to set up the repository on windows. Since the project is written in Java, I also set up Eclipse since it seemed to be the most useful for me and I was already familiar with it from previous class work. I also got to run Mechanix on my computer from the code as well as from the demo links. Being this my first interaction and experience joining a research project, there was a lot of new things to learn. For starters, I had never used a repository before. So the process of setting everything up may sound easy and quick, but there were many things I needed to get familiar with.
Subscribe to:
Comments (Atom)