My final week, was just a lot of wrapping up. I wanted to make my program as user friendly as possible so that another person could use it if needed. I worked on the final paper and just need to make a edit to the end and that will be that. The outcome was a little different then what I expected, but all in all interesting. This paper is being planed to be turned into the IEEE conferance next year, along with four other papers. The one i
I have suffered a great loss this week. *tear streaming down cheek* I dropped my mouse and the little wheel broke. On top of that the batteries ran dry. darkness ensues me... lol. Anyway other then my "tragic loss" this week was mostly understanding the data that I got from last week. Tuesday I tried my hand at python again to make a script that read all the files and made a chart for each simulation and for the mutation rate. For some reason when I ran this script on the clemson network i got a different format then when I ran the script on cloud 9 servers. I thought it was weird but it was a constant in all the charts so i didn't panic over it.
Other then just data running I wrote a new article depicting the results and a presentation of it. I dont think those need to be here too.
This week was used to gather all the data I could. I had to run the genetic algorithm 210 times. There were some problems with the machines conking out, but all the data was gathered. I am using the campus network for the bulk of this project, so I needed to ssh into the computers. This was a bit arduous since I have a windows and the version of ssh that I have will not allow for keys. So in the lab I logged onto two mac and ssh'ed into all the machines that I had available and used one to house all the evaluations and BallPlate simulations. In another I housed the running programs. With this set up I was able to see if any run was killed, dying. This would usually happen because the machine conked out. Here's a pic
When the data was all compiled and sorted and plotted and all that jazz This was the chart that came out
The majority of this week was used to hunt down more bugs that either pop up or hide every now and again. I was able to discover two important things. The first was that my program needed to be fundamentally altered so that the correct data was being used. The second was that nearly all the data I got before was near useless. So I have to rerun them. One problem that arose was that I would get 0.0 values. This was interesting because I didn't get 0.0 values before. Before it was 0.1928 which meant that the machine took too long to respond. Then I would get 1.0E-4 which was an error on the programs part...references =1.... Now I have 0.0 which could have been on the fault of the evaluation program, It was found that when my program read the newest default value, it round to the four places, the default value started in the fifth place, so my program would cut it off. The newest value means that the computer is dying and needs to be reset.... I think.... But cant want to see what next week holds.
This week meet with more bugs. But the bugs where effectively discovered and dealt with. On
Monday I run the program but for some reason I would get default values instead of actual values, I couldn't figure it out but nonetheless I needed to get some data. I ended up running smaller programs to would equal a lager program. But as the week went by the number of runs that could be completed shrank. In any case, the bug is found, or maybe a different one.
I was able to make a UI for the whole program. Up to this point I had to change the actual file and recompile every time I had different parameters. This way I just run one file and be done with it.
On Friday I was able to get a tour of the data center at Clemson, it was fun. there was a lot of no touchy but I was okay.
This week was a bit of a bummer. Starting Monday I ran 10 programs set, meaning that I ran the genetic algorithm program, the program to test the individuals and one to visualize and help test the individuals. I run these program on 30 different machines and for what ever reason some of the runs stopped, others went on to some point then died. The bulk of the week was hunting down the problem. On Tuesday I thought that I found the problem, but it turned out to be the herald to the actual culprit. In the end on Thursday, my mentor and I saw that when the program used 40-ish or more threads the machines load would reach a max and anyone else who ran a program on that machine would over load my program. It was no ones fault, just a discovery of a limitation. The runs that where stopped still had good data and It would have been a shame if it all had to go to waste, so the second big project for the week was making a plan B, if a run did stop in the middle of running I could call this class and the run would continue with little change. The only thing that would not be available would be the time it takes. The run saves all the important data, and the time it takes is not quite as pertinent. other then that this program would/should pick up right where the last computation left off, making the runs usable.
The last bit of stuff I need to do is look up four papers pertaining to my research and annotate them, I think this will go to the next part of the paper I'm working on.
This week was fun. On Monday Dr.Remy asked me to make some minor alterations to my genetic algorithm code, no big deal. I ran that program on a cloud device and I was floored. My little computer would have been broken, and in fact froze once the initial command was sent, but I still was able to get the data from the computation, because it was on a cloud and my little trooper of a computer only sent the message cry. So all this week was testing my program,and gathering data. I made a presentations of sort. My mentor is building up to the final presentation so I'm glad for that. today some friends took me to a local pizza joint, and OMG. It was divine. Also there was a little mixer... i guess that is what it would be called... for some students who are participating an another Research for Undergraduate Experience , and my mentor and I where invited to go. I was very fun, and there was free food, which is always a plus.
First week at Clemson and it was okay. There is no other way to say it really. Back in El Paso, the weather is hot and dry, here it is warm and humid. Needless to say, I was not a happy camper. I was able to get nice housing that was close to my mentors building so big plus. As for my actual week, it didn't really start until Wednesday, because my mentor wasn't in town yet. But he gave me a paper by the last student to work with him, and told me to read it and make notes, do the same for the citations and tell my what you think. The paper was about Genetic Algorithms and the effects of noise levels. It was very interesting, I had some questions about some things though. When Dr.Remy was in town he answered them and I got the gist that this would be the subject of my summer. Dr.Remy asked me to make a Genetic Algorithm program, I'm using java for this. So far I have it working, there's a small bug, but I'm gonna squish it.
My first week was fun, the only think I can complain about is that the bed is like off the ground. Its weird
journal about my summer