Speech:Spring 2018 Daniel Rubin Log


 * Home
 * Semesters
 * Spring 2018
 * Proposal
 * Report
 * Information - General Project Information
 * Experiments - List of speech experiments

Week Ending February 5th, 2018

 * Task:

1/30 : Today we had the task of figuring out what group we were going to be in; which consisted of: systems, experiments, data, modeling, and software groups. Once our group was completely formed we started to discuss different ways that we could communicate with each other. We also had the task of figuring out how our schedules could coincide with each other; in order to meet up weekly; so, that we could collaborate together within our group. Additionally, I decided to go in and further try to understand the lessons that were taught within class today via the wiki.

2/1 : Reviewed other students entries.

2/2 : Today's tasks including getting together to figure out what each of our team members strengths and weaknesses were. We also discussed an initial ideas of how we should attack the project and discuss what sum of each individual task we would all work on to contribute to our Capstone. We also work together to set some tasks that are specifically required in order to proliferate within our specific group. I needed to read up on some documentation as to educate myself further on speech recognition. Additionally, I had the task of working through the first train experiment.

2/4 : Read Student Logs.


 * Results:

1/30 : The results were that; I joined into the systems group which is an ideal fit which correlates with what I want to do with my education; once I graduate. As a group we were able to create two separate methods of communication for collaboration. We all agreed upon utilizing slack as the first form of communication. When I received that invite, I had to setup a slack account; with my school email. We also all joined a text message group, through our cell phones. I feel that this is a great way for us to maintain a constant form of communication in order to positively achieve the class goals for the semester..

2/1 : Reviewed other students entries.

2/2 : For the results are meeting was very successful as we were able to individually figure it out are individual strengths and weaknesses. My strengths included being good at networking security and an IT generalist my weaknesses are that I tend to overthink programming but typically can work through the problems. We also decided on Yashna playing the role of project leader. We determine some individual task that we were each going to implement towards are project proposal. In regards to the actual initial experiment I was able to complete the majority of the initial train but ran out of time before the server was able to complete all of the tasks. I also met with students from every other team and joined a unified Discord Channel for our class.

2/4 : Read Student Logs.


 * Plan:

1/30 : Currently the group plan is to meet together every Friday at UNH Manchester, in order to work together and figure out means of how to attack the projects; that we are assigned and help us to support each other to deal with the situations that might arise within the project/ class. Additionally, I am studying up on how voice recognition systems work, the potential system situations that we might face, and beginning to research more on how to work with a Redhat based environment.

2/1 : Reviewed other students entries.

2/2 : The plan continues to be figuring out new methods to work towards our project proposal and also figuring out how to gain server room access. Continue spending time going through the previous semesters material and submissions and trying to extrapolate all the data that will benefit us within the class and assist future students with their projects.

2/4 : Read Student Logs.


 * Concerns:

1/30 : Currently the only concern I have; is trying to correctly a lot my time for the semester. There are no other concerns at this moment in time

2/1 : Reviewed other students entries.

2/2 : As in the previous comment the only concern I have is being able to allocate my time accordingly. Besides that I do not have any concerns.

2/4 : Read Student Logs.

Week Ending February 12, 2013
2/6 : Today's initial task during class was figuring out the different objectives that would need to be completed through this week and the entire semester. Professor Jonas helped us work through what some of the potential objectives might be. Additionally, we individually had a few small questions in which Professor Jonas addressed. We were specifically advised by Professor Jonas that we might need to look into potential power issues involving some of the servers; dealing with power consumption and tripping the fuses. We had the task of sitting together and figuring out what would be the most crucial, secondary, extra tasks each week. We discussed how the project proposal outline would be effectively illustrated.
 * Task:

2/7 : Reviewed logs.

2/9 : To get together and have our weekly Friday meeting at UNH Manchester. We have the task of figuring out and continuing to formulate what the critical tasks would be, weekly. We worked together to assign individualized goals that would help support our systems group approach towards working though capstone. We all began to start utilizing a project management tool called Asana (found by Yashna) in order to help us focus on the tasks at hand.

2/10 : Reviewed logs.


 * Results:

2/6 : By discussing some of the potential situations that might arise with Professor Jonas during class, we were able to figure out some resolutions to methods that we might under take. After going into the server room, it was clearly evident that the power strip that was being utilized by the servers was most likely inadequate (testing is necessary). The result of us sitting together to figure out a hierarchical order of the goals that we had set in place, helped us to understand what are the most crucial items to present within our project proposal.

2/7 : Reviewed logs.

2/9 : After getting together we were able to devise exactly what tasks each of us would address. Additionally by working together we were able to help formulate the contents of our project proposal. We organized and set up some of the tasks in Asana.

2/10 : Reviewed logs.


 * Plan:

2/6 : Our plan is to continue to put our project proposal ideas together; as a group. We will meet on Friday Feb. 9th as planned for our weekly meet. I will also be continuing to read through the wiki material and attempt to figure out my train results. Additionally, we went into the UNH Manchester Server room in order to learn and figure out how the servers were structured, where particular items were located, figure out the hardware and software requirements that I would need to be able to work through the weekly objectives throughout the entire semester.

2/7 : Reviewed logs.

2/9 : My plan is to meet with Yashna on Tuesday before and after class in order to begin to set up the server 1. We will first be imaging one of the existing server’s hard disks that is distinctly, functioning well, so; that we can get the server up and running. I will be bringing in hardware tools and software in order to complete this task. We will then mount and network the server, but after completing our tasks; we will remove it until our group is able to get the correct licensing, IP addresses and other designations corrected accordingly.

2/10 : Reviewed logs.


 * Concerns:

2/6 : Currently I do not have any concerns.

2/7 : Reviewed logs.

2/9 : My concerns are making sure that all of the hardware and software will functionally work on the new server we are going to install; otherwise I have no concerns.

2/10 : Reviewed logs.

Week Ending February 19, 2013

 * Task:

2/13 : Talk with Professor Jonas about some of the specific requirements that he desires to have for the new server implementations. Enhance our existing proposal to make it shine. (Use 2014 - 2015-2016 project proposals as a model) Focus on enhancing narrative. (Make it like we were attempting to get money for this project.) Speak about the points that enhance the groups narrative Maybe have a timeline with milestones. Begin a new train run. Install the hardware that is needed to setup the first server. Clone the most stable server that has a SATA base (To support hardware compatibility). Continued to work on acoustic and language modeling. Attempt to diagnose why the some of the servers are having video issues. Find out about obtaining licenses for the RedHat Distros.

2/14 : Reviewed student logs.

2/15 : Today's task was meeting with Yashna to do Server Room modifications and add-ons. Figure out a way to resolve the connectivity issues with a few of the servers. Figure out why certain servers are unable to connect to the physical VGA monitors, create new server labels for all of the servers. Figure out the power demands for all of the servers, move servers into racks, run a new 5 hour train, and verify overall connectivity. Speak with Professor Jonas about the requirements for installing Nginx version 1.9.0; or better, figure out the requirements for installing Nmap on Rome, ask about where to place a specific shared location on one of the servers.

2/16 : Meet with group at UNH Manchester. Helped to confirm the use of chmod, in order to give the class access to the mnt/main/sandbox, continuing to work on project proposal for group and entire class, add specific content for the 2017 system and tools sections of the project proposal. Discuss how we are going to present out groups status updates during class, look up additional tools to be added to the servers; that might be beneficial for ours and future classes.


 * Results:

2/13 : The results for today’s class were; after speaking with Professor Jonas about some of specific requirements that would be necessary for to complete my tasks are as follows; if it was okay to image on of the SATA servers in order to implement it on the new server hardware. The result was Professor Jonas was okay with either a system image copy or fresh system install (both are acceptable). Asking him about if we were allowed to install Nginx version 1.9.0 or better on one of the servers; Professor Jonas’s response was installing it on Rome was fine, installing it on Caesar was not okay; and installing it on one of the drone servers is okay but further investigation would be necessary. Whether or not we were able to partition the hard drive for a shared storage location to protect intellectual property; the conclusion was we are not allowed to create a partition on one of the drone servers but instead; create the sandbox location in mnt/main. In response to enhancing our project proposal; we were able to discuss additional details that will be set forth and added to the next iteration to our project proposal.

2/14 : Reviewed student logs.

2/15 : The results for today, before coming to school; I was able to resolve the video graphics issue that two of the servers were facing; where they were unable to connect to a VGA monitor, in the server room. This was accomplished by the utilization of two different scripts including scripts from the following website http://www.itechlounge.net/2016/10/linux-change-installation-and-boot-video-resolution-on-centos-rhel-7/ and  (I will still be looking at the Xorg.*.log ’s). Once I got to school; Yashna and I sent out a message to the entire class via discord, to notify everybody that we will be shutting the servers down in order to do load testing. Upon completion of the load testing, I discovered that the servers were utilizing an excess of over 26 amps (exact results are contained within an excel spreadsheet that we created). We then reconnected all of the servers and made sure that all servers had network connectivity. Then we reordered the server configuration; because, there were no server sleds available; so, we had to remove an existing sled from Majestix and installing it 3U below Methusalix. We then continued to mount one of the servers onto the new sled; then installing two additional servers above the new server and using only clips to mount those two remaining servers. I was also able to connectivity issues with Brutus and Majestix; that we were made aware of via Discord.

2/16 : Meet with group at UNH Manchester. For today’s result I was able to indicate how to set the current folders permissions that Chris was setting utilizing a chmod calculator in order to know what permissions to grant mnt/main/sandbox too. We all worked specifically on a section of the project presentation in order to make it more robust and complete. I discussed with Professor Jonas that two of the servers need ECC DDR3 10600 Buffered RAM for two of the new servers. Unfortunately due to expenses; Professor Jonas indicated that we will probably not be able to utilize two of the three new servers. So, because of that, he gave me a new order for the servers to be in on the rack mount; removing the old Obelix server, shifting up idefix, then shifting everything else up to fill up any gaps within the server rack. Additonally, we discussed some new potential tools that we might be able to implement in the future. Here are some of the tools that I discovered that could be potentially beneficial to our class and future classes: Htop, Apachetop, Ftptop, powertop, and Ntopng


 * Plan:

2/13 : The plan is to now figure out which server is best to image, decide how to better enhance our project proposal, figure out a solution to the video not outputting to the physical VGA monitor, and obtain load testing hardware.

2/15 : Reviewed student logs.

2/16 : Figure out how we will be getting a new power strip. Additionally, look into low price RAM options to potentially get up the two servers that currently do not have RAM.

2/17 : Meet with group at UNH Manchester. Remove Obelix and reconfigure and adjust the new server layout that Professor Jonas has indicated. Research prices for a new rack mounted power distribution box. Clone Asterix in order to deploy on new server hardware. Continue to decode and test train.


 * Concerns:

2/13 : My only concern is that we will have the correct hardware to set up the new servers.

2/14 : Only concern I still have is regarding the server hardware and whether we have the correct parts/hardware for the new servers.

2/15 : Figuring out how we are going to deal with the power demand issues.

2/16 : At this time; I have no concerns.

Week Ending February 26, 2013

 * Task:

2/20 : Reviewed student logs. Post the power consumption totals of all of the servers.

2/21 : Today my task is to decide a method to clone Asterix. I will let everyone know via discord that I will be shutting down Asterix, in order to do my work. I need to identify what /dev/sd* contains the boot grub and the main system image. I will need to create a two different persistent boot loadable operating systems, in order to be able to externally see and clone the existing HDD’s. I will also be glad to teach anybody that wants to come learn what I am doing. I will need to bring in my external HDD Bay as well as USB drives for the hardware aspect of the cloning process.

2/22 : Reviewed student logs.

2/23 : Task today is for me to attempt to configure the BootGrub that will be implemented on the new server that will be named Automatix.

2/24 : My task today is to meet with Yashna in order to reconfigure and remove servers to conform to the new server arrangement scheme. Have the systems group meeting and begin making new cables for future server setups (to allow for proper cable management). Verify server backup integrity.

2/20 : Reviewed student logs. This is the Power consumption totals that Yashna and I got, for testing the total power draw /’s; from all of the following servers.
 * Results:

Amps	Watts	voltage	Total Amps Total Watts

Brutus	  2.192	250	114	26.183	    2985

Asterix	  2.868	327	114

Obelix 1  1.439	164	114 Obelix-2  2.447	279	114 Miraculix 2.737	312	114 Majestix  3.035	346	114 Idefix	  2.929	334	114 Methusalix 2.904	331	114 Caesar	  4.316	492	114 Rome	  1.316	150	114

2/21 : My results for today are as follows. In regards to figuring out which method to utilize, in order to clone Asterix; I first attempt to utilize a tool called Acronis. The problem that I faced with Acronis is the software flags the system as a server and wants me to purchase a server edition of the software; which is over a thousand dollars and is completely not feasible for our current environment. I then decided to utilize DD copy; because, it is a freely distributed and installed by default in most Linux distros. Tri then came to learn and observe. I utilized his help to figure out exactly what partitions need to be cloned. I loaded into a Debian distro in order to observe the attached file systems. Rose came and joined us and I continued to start teaching and demonstrating the things that we were currently implementing on the servers to Rose and teach Tri and Rose on how to boot into a persistent bootable Debian distro; and how to identify HDD volumes and clone am image of Asterix. These were the currently connected partitions:

Open GParted

/dev/sda1 67.75 GiB

/dev/sda2 14.91 GiB

/dev/sdb 14.65 GiB

/dev/sdc 149.05 GiB

After figuring out the exact partitions, I indicated that both of the /dev/sda partitions were going to be designated as the source locations to clone and the /dev/sdc location as the cloning target location. Once, I triple checked that the correct locations were indicated in the DD script that I was about to run was correct; I began the cloning process.

2/22 : Reviewed student logs.

2/23 : After figuring out why the BootGrub partition wasn’t being pushed to the clone copy via DD I continued to take steps to reobtain the BootGrub image off of the /dev/sdb location. I believe the new BootGrub should work correctly; but, I will not be sure until the new server is complete.

2/24 : My results for the task of the new server arrangement scheme while working with Yashna was extremely successful. Per Professor Jonas’ request; we removed the two DR610 servers, that do not have the correct RAM inside of them, out of the rack then removed the old obelix out of the rack completely. Unfortunately, we were not able to utilize the sled from the old obelix because it was an older style sled. We then removed the other new Power Edge 1950 server from right above Caesar, and we were able to utilize that sled for where we removed the sled from the old obelix server. Now that the old obelix location was empty (minus the new sled), we shifted idefix up to that location, then moved the new del1950 (the new Automatix server) into idefixs’ old location, then we reconfigured the wiring and then proceeded to turn on all of the servers, and verify network connectivity. The next results for the day was being able to all meet via Discord for our weekly meeting. During this meeting we discussed what each of us did this week and what we will be doing for upcoming weeks. Finally, Yashna and I began the process of making new network cables for the server so in the upcoming weeks we can modify the servers wiring scheme. I in detail discussed and began teaching Yashna on how to properly wire Cat5e Ethernet cables utilizing the T568B standard. I also pushed the new BootGrub onto my cloning image.


 * Plan:

2/20 : Reviewed student logs.

2/21 : Create additional cabling for new wiring scheme and cable organiziation. Research pricing on new rack hardware including power supply, and/or DDR3 10600 Buffered RAM, possibly also look into getting some proper cable ties and an additional sled.

2/22 : Reviewed student logs.

2/23 : Server room configure BootGrub asterix.

2/24 : To continue the operating system installation of Automatix. Look into a power error message that I received on one of the servers, but have not had a chance to further investigate. I believe that the issue is related to a dead CMOS battery. If this is the case, I will make sure I get permission from Professor Jonas to replace.


 * Concerns:

2/20 : Reviewed student logs.

2/21 : My only concern for today is hoping that the server cloning process will go smoothly. Otherwise, no concerns.

2/22 : Reviewed student logs.

2/23 : Server room configure BootGrub asterix.

2/24 : My only concern is the continuation of the new server installation going smoothly. Otherwise, I do not have any concerns.

Week Ending March 5, 2013

 * Task:

2/27 : Today's task included; meeting up for class, filling in Professor Jonas on our weekly achievements, and working with group on where we are currently at in reference to our project proposal. Another major task for today is to go into the server room and figure out exactly what needs to get done within the next week by discussing current status with Professor Jonas. Also, meet with some of the other students and see what their groups are currently working on.

3/1 : Reviewed student logs.

3/2 : Reviewed student logs.

3/3 : Today's task is to meet up with Yashna and Lamia in order to work on the servers and replace batteries on Asterix. We will be having our weekly meeting via discord, and I will be partitioning the Automatix 3.5 SAS HDD for new server utilization. Once partitioning is complete, I will be re-imaging the newly partitioned hard drive for Automatix. Additionally, we will hopefully be able to obtain a label maker so that we can relabel all of the servers; accordingly.

3/5 : Reviewed student logs, and go over my tasks for the coming week.


 * Results:

2/27 : Met with group and reviewed what everyone did for the week so we could tell Professor Jonas what our accomplishments were. After the discussion with Professor Jonas regarding our weekly achievements; our group went through on where we currently stand with our tasks that were indicated within the project proposal. I was officially told by Professor Jonas that it would be okay to start replacing the CMOS battery on Asterix. I discussed with Chris exactly certain methods that are utilize in order to verify recovery data on the backup server. Then I saw Professor Jonas after everyone else had left school except for Lamia, while Professor Jonas, Lamia and I were in the server room we discussed the current situation we are facing with the current power scheme, limited ram availability, and figuring out that we will be able to utilize Methusalix as another drone server by removing the currently utilized SAS HDD.

3/1 : Reviewed student logs.

3/2 : Reviewed student logs.

3/3 : After getting into the server room, I noticed that some of the servers were over heating. I sent out a message via Discord that I would specifically be shutting Idefix down; because, Idefix was extremely hot and the power indicator on the front of the server was flashing. I then proceeded to shut Idefix down. I then began verifying the cloning partition integrity and began to verify the exact space requirements that would be necessary for me to partition. We then began our meeting exactly when Yashna joined me in the server room. During our meeting we discussed where we currently were in regards to the project proposal and what we will be doing. After that, Lamia came and joined us, at the end of our group meeting and we began to work on the servers. We started out by relabeling all of the servers both front and back. We then replaced the CMOS battery on Asterix and reset the default time and date settings in BIOS. We then realized that all of the servers were needing CMOS battery replacements. I only had four batteries to donate, so we also replaced batteries on Automatix, Idefix, and Miraculix (date and time change was also implemented on all of these servers in BIOS). Prior to replacing these batteries, we let everyone know that we will be shutting certain servers down, at certain points in time, we then logged into each server and continued with the “shutdown now” command. We modified the power stripe locations of both Automatix and Asterix. In order to partition the new Automatix 3.5 SAS HDD we had to boot into a persistent bootable Debian version of Linux. Then we went into a partitioning editor in order to modify the hard drives as follows: Ext4 as 56.79 MB (with flag Pri, Act.) Master Boot Record and Track 0 100 MB Unlabeled 67.26 GB (with flag Pri.) Additionally, I taught both Lamia and Yashna the steps that we would be taking in order to manually modify and configure the new Automatix drone server.

3/5 : Reviewed student logs and inform entire class on discord that I will be reallocating the power distribution scheme for all of the servers; on either Tuesday after class, or Saturday.


 * Plan:

2/27 : The plan is to come in on Saturday to continue working on the servers. I believe that Lamia and Yashna will both be joining me. I have some CMOS batteries that I will be bringing in and donating to the school for server use. Additionally, I will be repartitioning the new Automatix 3.5 SAS HDD in order to correctly image the clone.

3/1 : Reviewed student logs.

3/2 : Reviewed student logs.

3/3 : Plan is to figure out how we will be getting the additional CMOS batteries for the rest of the servers. Additionally I will have to research what battery the PowerEdge 2900 server requires as a CMOS battery and figure out where we will be getting the correct network Ethernet cables to perform proper cable management.

3/5 : Reviewed student logs. Meet with Jonas on Tuesday after class to obtain the new rack mounted power source and begin setting up the new power scheme.

2/27 : I currently have no concerns.
 * Concerns:

3/1 : Reviewed student logs.

3/2 : Reviewed student logs.

3/3 : My only concern is that the new Automatix drone will work properly. Otherwise, I have no other concerns.

3/5 : Reviewed student logs, my concerns are still making sure that the new drone servers will be up and functional in a reasonable amount of time.

Week Ending March 12, 2013
Task

3/6 : The first task for today was to go to the server room in order to get the MBR up and functioning on the Automatix drone server. The next task that I would face was to figure out how I will be implementing to correct power scheme for the power. Then I would begin working on the Traubadix drone server. Then I had the task of meeting up with the systems group, in order to discuss everything that we would be presenting to that class today. Then the next task will be to work with Chris and Cam to figure out how to log into the backup server and see if we can figure out if the backup server is functioning.

3/7 : Reviewed student logs

3/8 : Reviewed student logs

3/10 : My task today is to go into the server room and redo the server power scheme. I also have the task of having my weekly group meeting; via, discord.

Results

3/6 : My result in going to the server room today, in order to get the master boot record functioning; so, that the new Automatix server can be up and running, was successful. My preliminary attempts to getting the server working; was utilizing a flash drive, that I partition with the master boot record. This showed that everything was operational and the next steps were going to be; to modify the name IP address and license for the server. Unfortunately, during class, it was indicated that the server that was cloned was utilizing RedHat 6.6; but, we now I needed to make sure that we implemented 6.8, onto the automatix server. The next result was figuring out how I was going to run all the power; to all the servers. After looking at the current configuration, obtaining the rack mounted power distribution block, and talking with professor Jonas; I was able to indicate how the new configuration was going to be implemented. The task meeting with the systems group in order to figure out what we were going to discuss during the class meeting was successful; because, we were all able to allocate what we had done the previous week. Then we went into the tech room, to figure out what was going on with the backup server and see if we can get it functioning. After looking into the back of servers and reviewing many previous log entrees; from previous semesters, we couldn’t figure out why the clone wasn't functioning correctly. After class, I spoke with Professor Jonas again and after talking with him about what we encountered in the tech room, he indicated to me that, the virtual machine on the backup server was acting as a hard drive. This gives us a lot more insight in how to get the backups correctly functioning again.

3/7 : Reviewed student logs

3/8 : Reviewed student logs

3/10 : My results today for re-configuring the power scheme today, was very successful. I was able first let everyone know on Discord that the servers were all going to be down. Then I removed all of the existing power cables; in order to be able to sort and reorder them. I then moved the existing power supply up 3U; so, that I could install the new rack mounted power distribution block where Professor Jonas indicated, that he would like the new unit to be placed. I then individually bound and sorted all the cables, rewired some of the power source wall connections, made sure that everything was neat and organized, and then re-powered everything and made sure all the servers were ready. Finally I SSH’ed into each server, in order to verify network connectivity and then emailed the entire class that all the servers were back up and running. I took pictures before and after, to show the difference between what it looked like before, I was able to sort the power cables and the clean result upon completion.

Plan

3/6 : The plan is to now come in on Saturday and configure the whole entire power scheme. Have our weekly group meeting online via Discord. And begin to figure out how the backup system can be fixed, into a correctly functioning state.

3/7 : Reviewed student logs

3/8 : Reviewed student logs

3/10 : My plan is to know go in and redo all the network cables into a nice clean configuration. (Update: Professor Jonas has now indicated that he no longer wants the ethernet cables organized due to potential usage needs, and to only modify these cables if something should go down.)

Concerns

3/6 : My only concern is making sure that the new rack mounted power distribution bank. Will function correctly. Otherwise I have no other concerns.

3/7 : My only concern is still making sure that the new rack mounted power distribution bank. Will function correctly. No other concerns.

3/8 : Only concern is still about the new rack mounted power distribution bank. No other concerns.

3/10 : No concerns at this time.

Week Ending March 26, 2013
Task:

3/12 : (Spring break.) Discuss with my Avengers group on what servers we would want to acquire.

3/21 : Reviewed logs.

3/24 : My first task for the day is to let everybody know that, I will be temporarily turning off Miraculix, go to the server room and now restart the cloning process; but, instead of utilizing Asterix for cloning, I will be cloning Miraculix. The next task for the day will be to have our weekly group meeting via the Discord systems channel. Another task will be to find a good hard disk drive, to use on Traubadix.

3/25 : Reviewed logs.

3/26 : My tasks for today will be to reimage Automatix again; because, the first time the network driver seems to be corrupt. Another task is to then image the Traubadix drone. Another task is once these drones are imaged, I will have to modify their hostnames and IP addresses. Finally I will attempt to modify the new drones network schemes.

Results:

3/12 : (Spring break.) After discussing with my Avengers group; via discord, about what servers we would be wanting; we figured out that we would be wanting Asterix; because, it had LDA installed on it, and Idefix & Obelix because; of good naming conventions.

3/21 : Reviewed logs.

3/24 : My results for today; include, making sure to inform everyone, that I will be temporarily turning off Miraculix, begin the cloning process of the Miraculix drone server, have our weekly Discord meeting, reimage the Automatix drone server, and locate a properly working hard disk drive for Traubadix. My results for making sure that I inform everyone via Discord; that I will be temporarily disconnecting Miraculix, was successful, because, I was able to post it and announce that, it was going to be turned off. Additionally, I was able to login to Miraculix and verify that nobody was running any processes; via, the “top” command. Yashna and I then had our weekly meeting; via, our Discord Channel. Next, I shut down the Miraculix server and created an image of the Miraculix drone; to be used for cloning. Miraculix was the perfect choice; because, it had previously been indicated that it was able to run a decode, which would utilize LDA (which is 'latent dirichlet allocation) and was running RedHat 6.8. I partitioned the hard disk drive; so, I could re-image the Automatix server with the image that I just created from Miraculix. After that; everything was set for Yashna and I, to begin re-imaging the Automatix drone server. Once, Automatix was done being imaged, Yashna and I worked together; in -order to rename the new server, and have it connected to the local area network. I took quite a while, trying to figure out the network connectivity portion; but, I believe there was some type of error with a network interface.

3/25 : Reviewed logs.

3/26 : today's results; included, re-imaging the Automatix drone server again; because, of a corrupted network driver, get the Traubadix server up and running, modify the hostnames + IP addresses, and modify the network schemes. I actually went to our campus, at two separate points of the day; for a few hours each. First, I re-imaged the Automatix drone, again. This process went fairly smoothly; because, I was able to do a bit sector repair during the re-imaging process. I then re-imaged the Traubadix server; as well. Next, I modified the server names and IP addresses. Finally, I begin to modify the network schemes and after quite some time; I was able to obtain network connectivity on Traubadix (ping only).

Hardware Addresses for Traubadix: eth0     Link encap:Ethernet  HWaddr 00:19:B9:E7:30:66 eth1     Link encap:Ethernet  HWaddr 00:19:B9:E7:30:68

Modified Network Configuration for the Traubadix eth0 and eth1:

eth0: DEVICE=eth0 IPADDR=192.168.10.5 NETMASK=255.255.255.0 NETWORK=192.168.10.1 BROADCAST=192.168.10.255 #HWADDR=00:19:B9:E7:30:66 TYPE=Ethernet UUID=40e2e969-44e2-4b1f-9f33-39148dbc8981 ONBOOT=yes NM_CONTROLLED=no BOOTPROTO=static

eth1: DEVICE=eth1 TYPE=Ethernet UUID=eb490f03-656b-47ec-b159-73d1b7bc4672 ONBOOT=yes NM_CONTROLLED=yes IPADDR=172.16.0.5 NETWORK=172.16.0.0 NETMASK=255.255.255.0 GATEWAY=172.16.0.11 BROADCAST=172.16.0.255 BOOTPROTO=static #HWADDR=00:19:B9:E7:30:68 DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth1" LAST_CONNECT=1490300821

Plan:

3/12 : (Spring break.) The plan for coming weeks is to figure out new methods, which would ultimately help everybody have reduced errors; in their decoding processes; and improving the overall functionality of the Sphinx voice recognition system.

3/21 : Reviewed logs.

3/24 : My plan is to come back on Monday in order to re-image Automatix again and begin working on the Traubadix drone server.

3/25 : Reviewed logs.

3/26 : My plan is to continue working on the network scheme for both Automatix and Traubadix.

Concerns:

3/12 : (Spring break.) No concerns at this time.

3/21 : Reviewed logs.

3/24 : The concern that I am currently having is, hoping that the Automatix clone, will not have network driver issues; during the next imaging. Besides that, I have no other concerns at this time.

3/25 : Reviewed logs.

3/26 : My concerns are now getting the new drone servers to network properly. No other concerns at the moment.

Week Ending April 2, 2013
3/29 : My first task for today is to do some additional research on how LDA is utilized and implemented. My next for the day, is to meet with tri; after one of our classes together, and work on training and decoding; on, Traubadix. Finally I’ll begin to try to figure out why there is an RSA certificate error between certain servers and Caesar.
 * Task:

3/31 : My tasks for today is to meet with Yashna; at our UNH Manchester campus. We will then have our weekly group meeting via Discord. After that, we will work together on our URC poster. Finally; we will work together on getting the Asterix drone server up and running.

4/1 : Reviewed student logs.

4/2 : Reviewed student logs.


 * Results:

3/29 : In regards to my first task for the day on researching how LDA is utilized and implemented is utilized and implemented; I have potentially identified some new methods on how to get LDA to properly function. From where it currently stands, I believe that it is a python package that utilizes (numpy). I feel that a properly configured LDA will potentially have a lot of great benefits and hopefully decrease the word error rate score. In regards to the Tasca meeting with tree after class and working on running a decode an unseen data, on Traubadix, was both successful and unsuccessful; in different ways. Initial reason that it was unsuccessful is because, decoding on multiple servers has run into some type of issue; with RSA authentication. As far as I currently know, the only two servers that are correctly decoding are Asterix and Idafix. I'm wondering why this is and if it potentially is caused by some type of modification to one of the scripts that are utilized in decoding. Now on the other hand, while working with Tri, I was able to successfully run decode; on unseen data, on Asterix.

[dir1000@asterix etc]$ tail -8 scoring.log

| Sum/Avg | 4173 60938 | 46.6   43.7    9.7   10.5   63.9   92.6 | |=================================================================|    |  Mean   |  1.3   19.2 | 55.8   37.1    7.2   18.2   62.4   92.6 | | S.D.   |  0.5   16.5 | 22.2   19.6    8.8   32.0   33.7   24.3 | | Median |  1.0   15.0 | 50.0   38.9    4.3    7.7   62.5  100.0 | `-'

After working with tri for about 5 hours, we are still, uncertain of what is causing the decode error on certain server.

3/31 : Task meeting with Yashna at UNH Manchester was successful. We were both able to meet up and begin working on are URC poster. We both had worked on the URC poster, imported some great content and picture for the poster’s design. We finished up with all the contents needed to add on to our poster and gave it to Chris. We had to make a few modifications because the file that was sent, was corrupted. Because of that, we decided to add the data on word document and email it to our systems group. We then began working on reimaging Asterix again, because, something wasn't allowing for correct network connectivity. After reimaging Asterix, we renamed the hostname of the Asterix server. Then we modified the entire IP scheme; including, the networking paths, IP's and DNS addresses. We potentially think that there is either an issue with the hardware or the Ethernet cables that help the Asterix server connect to both the LAN and WAN. We will have to continue to work on this; this Tuesday.

4/1 : Reviewed student logs.

4/2 : Reviewed student logs.


 * Plan:

3/29 : My plan is to now run a longer train and decode on unseen data, and attempt to continue to improve on the word error rate. Additionally I will continue to do research on how to have LDA available to all of the servers.

3/31 : The plan is to continue to figure out why the similar networking scheme implementation that worked on Traubadix, is not working on Asterix. I am wondering if it has to do with cabling or the NIC card; itself. I will also continue researching how to properly implement LDA across all of the servers.

4/1 : Reviewed student logs.

4/2 : Reviewed student logs.
 * Concerns:

3/29 : My concern for today is figuring out why some of the servers are not properly decoding. Besides this I have no additional concerns.

3/31 : I'm slightly concerned about potentially having a hardware issue on Asterix. Hopefully it is just a bad cable or something improperly set up Alma networking scheme. Besides this, I do not have any other concerns.

4/1 : Reviewed student logs.

4/2 :Reviewed student logs.

Week Ending April 9, 2013

 * Task:

4/4 : Met with Jaden and Lamia.

4/5 : Met with Tri and Jaden.

4/6 : Met with Professor Jonas.

4/7 : Reviewed Logs

4/9 : Worked with Tri and online Discord meeting.


 * Results:

4/4 : Met with Jaden and Lamia.

4/5 : Met with Tri and Jaden.

4/6 : Met with Professor Jonas.

4/7 : Reviewed Logs

4/9 : Worked with Tri and online Discord meeting.


 * Plan:

4/4 : Met with Jaden and Lamia.

4/5 : Met with Tri and Jaden.

4/6 : Met with Professor Jonas.

4/7 : Reviewed Logs 4/9 : Worked with Tri and online Discord meeting.


 * Concerns:

4/4 : Met with Jaden and Lamia.

4/5 : Met with Tri and Jaden.

4/6 : Met with Professor Jonas.

4/7 : Reviewed Logs

4/9 : Worked with Tri and online Discord meeting.

Week Ending April 16, 2013
4/10 : Task today is to work with Jaden, Tri, Lamia, and Isaac; on new ideas towards Avengers progression. Private information logged separately.
 * Task:

4/11 : Reviewed student logs.

4/12 : Task today is to meet with Tri and Lamia; to work towards Avengers Progression. Private information logged separately.

4/13 : Reviewed student logs.

4/14 : Task today is to meet with Tri at our campus. I will reclone Automatix again, and try to get the new Network Interface Drivers; up and running. Also; to work with Isaac; via, telephone and VNC viewer. Private information logged separately.

4/15 : Task today is to work towards Avengers progression. Private information logged separately.


 * Results:

4/10 : The task of working with Jaden, Tri, Lamia, and Isaac; on new ideas towards Avengers progression; was successful. Results are private.

4/11 : Reviewed student logs.

4/12 : The task of meeting with Tri and Lamia; to work towards Avengers Progression; was a success. Results are private.

4/13 : Reviewed student logs.

4/14 : The tasks of meeting with Tri at our campus and then working with Isaac; towards the progression of the Avengers team; was was fantastic and somewhat groundbreaking. I re-cloned Automatix, loaded the new network drivers, and attempted to get Automatix running with the new Network Interface Card "NIC" and actually got some basic connectivity, but,something is definitely wrong with this server. I will continue to troubleshoot Automatix and figure out a way to get it up and running. Results are private.

4/15 : The task of working towards Avengers progression, was successful, today. Results are private.


 * Plan:

4/10 : Plan is private.

4/11 : Reviewed student logs.

4/12 : Plan is private.

4/13 : Reviewed student logs.

4/14 : Plan is private.

4/15 : Plan is private.


 * Concerns:

4/10 : My concern for today is, hoping that my new implementation will correctly parse. Otherwise; no other concerns.

4/11 : Reviewed student logs.

4/12 : My concern today is figuring out how to effectively get my new idea to correctly train/ decode.

4/13 : Reviewed student logs.

4/14 : Only concern today is; trying to get Automatix to properly connect to the network.

4/15 : Worked towards Avengers Progression. Private information logged separately; for Professor Jonas.

Week Ending April 23, 2013

 * Task:

4/17 : Class

4/18 : URC

4/19 : Met with Tri and Jaden

4/20 : Worked on improving error rate.


 * Results:

4/17 : Class

4/18 : URC

4/19 : Met with Tri and Jaden

4/20 : Worked on improving error rate.


 * Plan:

4/17 : Class

4/18 : URC

4/19 : Met with Tri and Jaden

4/20 : Worked on improving error rate.


 * Concerns:

4/17 : Class

4/18 : URC

4/19 : Met with Tri and Jaden

4/20 : Worked on improving error rate.

Week Ending April 30, 2013

 * Task:


 * Results:


 * Plan:


 * Concerns:

Week Ending May 7, 2013

 * Task:


 * Results:


 * Plan:


 * Concerns: