Speech:Spring 2018 Yashna Giri Log


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

Week Ending February 5th, 2013

 * Task: 01/30/2018 - Today was the day where we were going to find out what group we were going to be in. Professor told us that he was going to get rid of the Tools group while the Systems group would take care of most of the Tools group tasks. There are total of 5 groups and they are: Systems, Software, Data, Modeling and Experiment. I am in the Systems group and I am really excited and looking forward to learning new things. We are total of 4 people in the group and I am looking forward to working with each of them because I believe the best way to learn is through collaborating and in a Team. After my group members introduced themselves to each other we spoke about our schedules and came in to a conclusion that we shall meet once a week and use slack and group text message to communicate with each other.

02/03/2018 - So, as per our previous plan I, Camden, Chris and Daniel met yesterday Friday the 2nd and went over the strength and weaknesses of each team member. The meeting was a successful one because we knew about one another better so, that we know how each one can contribute in the project and how each of them could also overcome their weaknesses by learning and collaborating together. The goal of this project is to work collaboratively while working on the areas which are your strengths and also identifying your weaknesses and learn from it with your Team members. We found out that Daniel's strength was Networking, Security and General IT while his weakness was programming, Camden's strength included IT technical support, servers, linux, networking and his weakness included programming also. Well he is not bad at it but he would prefer something with servers and clouds than "programming". While Chris's strength included that he was experienced in linux, developing applications and he was a good programmer and his weakness was that he wasn't much experience at server administration. My strength was Project Management, Database admin and general IT while my weakness is programming. So, we all agreed upon I playing more so, as a role of a "Project Manager" and making sure keeping track of all our work. Furthermore, also working with the group and learning about servers and linux is my ultimate goal too. I am currently working as a entry level "Project lead" for a company also so, what I am doing in my capstone is very much relatable to my work right now and what I plan on doing after my graduation. We also created a "TODO" list. I am assigned to send Professor an email regarding if we could access the server room? (as being the point of communication) this week.

02/04/2018- Today I went over the previous semesters System groups student logs.

02/05/2018- Today I went over the previous semesters Tools groups student logs.


 * Results:01/30/2018- The results are that all my group members and I set up slack. Chris invited us to join slack and we signed up for it. Also, we decided to create a "Group text message" so, that we all are able to communicate properly without any problem.

02/03/2018- The results are that the first meeting was a huge success and now we have depth knowledge of the strength and weakness of each team members. We also decided on what each individual will focus on more according to their strength.

02/04/2018- Finished up reading the Systems group students logs from previous semester.

02/05/2018- Finished up reading the Tools group students logs from previous semester.


 * Plan: 01/30/2018- We will have a group meeting every Friday.

02/03/2018- We planned on sending Professor Jonas a quick email on whether if we are allowed to access the server room? Furthermore, we plan on working for our project proposal this week.

02/04/2018- Finish up reading the Systems groups logs from the previous semester

02/05/2018- As a group we planned on meeting an hour before class to discuss our further plans.
 * Concerns: 01/30/2018 - As of now I do not have any concerns.

02/03/2018- As of now my concern is if Professor will allow us to access the server room or not?

02/04/2018- As of now I have no concerns.

02/05/2018 - As of now the concern is to get started with the project proposal.

Week Ending February 12, 2013

 * Task: 02/08/2018 - In the class on 02/06/2018 we had already decided few things what we need to focus on for the rest of the week. Professor.Jonas was really helpful. We got the access to the server room and me and my group spent some time there and did some brainstorming. We worked on brainstorming ideas on how we could make the system better and what are some real goals we can accomplish and what are some bonuses which would be great to add to our existing goals. Today I am working on drafting a rough draft for the project proposal for my team which is due on Sunday. Also I shared an amazing website called www.aasna.com which will help us keep track of our work. This software basically keeps track of team work and manages projects. I have used this at my work  once and I plan on using it more because it's an amazing application.

02/09/2018- As I have already mentioned in my previous log that our group always meets every Friday. We met today and discussed about the rough draft of the project proposal which I had prepared and made necessary changes on it as per all my team members input. Also, today we decided on what the team members will be working on.

Servers for Daniel Tools for Myself Storage was for Chris Networking was for Camden.

However, I and my Team agreed on me helping each of them with whatever they are responsible for because I volunteered to do so. I wanted an exposure of each responsibilities my team members are responsible for and they are really good at it and I wanted hands on experience so, why not. Also, my team and I looked on the application which I found and I've used before for Project Management called "Aasana" so, far the team members like it.

02/11/2018- Myself and Daniel decided that we were going to set up the server and I'm excited because I never had done that before. We decided to set up the server before our class on Tuesday the 13th.

02/12/2018- Today I researched a bit on my share of the work because I'm responsible for the Tools section in the systems group.


 * Results: 02/08/2018- I drafted a rough draft for the project proposal.

02/09/2018- We successfully decided what each member of group is responsible for and our plans for the capstone project for the rest of the month. We successfully finished our "Rough draft" of the project proposal also.

02/11/2018- One of my team member Daniel and decided to meet before class and set up one of the server in the server room.

02/12/2018- I was quite not successful with what I was looking for.


 * Plan: 02/08/2018- As I have already mentioned before in the previous log that my team and I meet every Friday at 6 so, I plan on showing my teammates the rough draft I have drafted for the project proposal and add on to it if they have more ideas to add upon.

02/09/2018- I will be inviting the rest of the class in the Project I created at "Aasana.com" which will help rest of the students keep track of their work and furthermore, we all can see what each of them are working on which will help us with the future evaluation also.

02/11/2018-I will be meeting Daniel before class to set up one of the servers in the server room.

02/12/2018- I will research on it more and go back to the students log from the Tools group past semester and see if I can find what I'm looking for if not I will research and talk to my team mates about it.


 * Concerns: 02/08/2018- I hope my team likes the rough draft tomorrow which I have drafted.

02/09/2018- I tried inviting all the students but Aasna is having some issues. I was able to invite only some of them. I need to look into it and try to figure things out.

02/11/2018- I am worried. I hope I don't blow up anything while setting up the server because I have never set up servers before but on the other hand it's better to try something new and learn from it rather than not trying.

02/12/2018- No concerns as of now.

Week Ending February 19, 2013

 * Task: 02/15/2018 - Today Daniel and I met around 5:30 and worked at the Server room. We tried to figure out ways to resolve the connection issues with the servers. We found out that few of the servers were unable to connect to the physical VGA monitors, In addition, to that we created new server labels for all of the servers. We figured out the power demands for all of the servers, moved servers into racks, ran a new 5 hour train. In the morning Tri and I had met and he was the one who helped me run my 5 hour train because I was getting some errors but that was quick fix. After he helped me I put how my codes worked in the class discord so, that anybody who was having trouble with running the train could look into it.  I am extremely thankful to Daniel because he was a great mentor. I have never worked with hardwares before or the servers but he demonstrated and taught me everything while I was doing it. it didn't even felt like I was working on all these things for the first time.

02/16/2018- Today we had a meeting with our whole group on our project proposal. This was a friday meeting as usual and we spoke about our accomplishments this week and what we will work on in the future. We also discussed on how we will be presenting our materials to our Professor in next class and decided mutually that Daniel will give updates on it to the Professor in the class.

02/17/2018- Reviewed logs.

02/19/2018-Today Camden and I met in school and worked in the server room. Camden had tried to reconfigure the DNS file (/etc/resolv.conf) on Saturday, after he successfully updated it he thought he broke something because he wasn't able to reconnect. That's why him and I decided to go to there server room today to see everything was OKAY!


 * Results: 02/15/2018 - After Daniel and I met today we sent out a message to the class through discord and notified that we will be shutting the servers down in order to perform the load testing. After we finished our load testings we wrote all our results down in a spreadsheet that we had created in Danie's computer. After that we again connected the servers to make sure that they had network in them. After that we reordered the server configuration because we were unable to find the sleds in the server room hence, had to remove sled from Majestix and installed it to the 3 U below Methusalix. We installed two servers in addition to whatever we had previously.

02/16/2018- Today's meeting was successful we hammered a lot out in 3 hours about the project proposal and possible tasks we could work on in the future.

02/17/2018- Reviewed logs.

02/19/2018- So, after Cam and I went to the server room today, we found out that Asterisk didn't have a broken DNS and it was only off. It seemed to have occurred nearly the same time as the DNS update. It is unknown at this time if the two are related or not.


 * Plan: 02/15/2018- My plan at this moment is to work at the project proposal so that it looks better than what the rough draft is. Daniel and I planned on working about obtaining a load testing hardware as well.

02/16/2018 - The results were that we decided on the project presentation and proposal and Daniel will be the one giving updates to Professor Jonas. Daniel had discussed with Professor Jonas when he met him on Friday about adding things to the servers but because of the expenses professor told him that they won't be able to utilize the new servers. instead he gave an order to remove Obelix and shift Idefix so, I believe I'll be helping Daniel with that this week. We also looked into few tools which we could install once we get the permission from our professor.

02/17/2018- Reviewed logs.

02/19/2018- Camden and I decided to send Professor Jonas an email regarding the issue so, that he could advice on what we could do before taking any further steps.


 * Concerns: 02/15/2018- The concern at this moment is the lack of hardwares in the server room so, we need to make sure we have the right tools to install the servers and run it smoothly.

02/16/2018 - Finishing the project proposal on time and with the right amount of information is very important. Hopefully our project proposal turns out to be good and not a disaster like the rough draft. Fingers crossed.

02/17/2018- Reviewed logs.

02/19/2018- My concern at this time is what kind of feedback are we going to get from our Professor.

Week Ending February 26, 2013

 * Task: 02/23/2018 - Today I worked with Camden after 5:30 at school. We usually have our group meeting on Friday but decided to move our meetings to Saturday as Daniel has a time limitation. We looked into how Rome is connected to Caesar to get a better understanding. We knew how Rome is Mounted to Caesar and could confirm this configuration by looking at:

```more /etc/fstab```

here we could see:

```caesar:/mnt/main       /mnt/main               nfs```

Next, we looked into the link for /usr/local. After spending some time slamming our heads against the wall trying to figure out why we couldn't understand Romes link. We look at Asterix's file structure and could see the link right away. We concluded that Rome does not have its /usr/local linked to begin with.

We also LS -AL of all the install directories on Rome into txt files so we could do a diff on the install directories after we install nginx and nmap. The .txt files are saved as a snapshot in Rome /root/documents/snapshot_02232018

we will be conferring with Jonas the necessary steps to proceed with installation and also adding documentation to the Wiki on how to complete an install.

02/24/2018 - Today is Saturday and Daniel and I decided to meet up and work on our servers. We met around 12 at school in the server room. I am enjoying working hands on with the servers and understanding it more every time I work on it. Daniel sent out the message to the entire class on Discord in regards to the Idefix being shut down and having the old obelix server removed so that Idefix can take it's present location. While he was sending the message I began to unmount specific servers from the rack, removed PowerEdge R610 from the Rack, adjusted the slid location to be mounted, so that Majestic can have it's own slid. We are also going to be looking for a good 3.5 sas drive for the new PowerEdge 1950. Also, Daniel taught me how to make cat5 Ethernet cables from scratch.

02/25/2018- Today I worked on Researching most of the time about the Error Logging Tools for linux which will tell us if there are any errors. I found few tools and shared it with my team mates over slack. Camden found one to be useful and not very generic. Below is the link:

https://www.tecmint.com/best-linux-log-monitoring-and-management-tools/

I found Log watch one to be extra and not very generic. I'll meet my team mates on Tuesday and we'll further discuss about it and once all of us agree upon a specific tool will ask professor if we could install the tool or not.

02/26/2018- As I have already mentioned before I and Camden met today after work around 5:30 PM. We first ensured that Caesar was not mounted. then ensured there was no symbolic link for /usr/local. Then got a new snapshot of the directories. Then disconnected Rome from the local network, keeping an outside-internet connection. Created a file for installation discovery (a repository)

``` nano /etc/yum.repos.d/nginx.repo ``` then installed Nginx ```yum install nginx``` confirmed nginx was installed ``` service nginx start ... [OK]...``` then captured a new snapshot of the directories.

Next, we need to compose a list of the effected files by completing a *diff* from snapshot 1 to snapshot 2. I was not immediately confident onhow to read the diff output So i want to review before passing it by Jonas.


 * Results: 02/23/2018- Found out that the Rome has been unlinked.

02/24/2018 - Removed old obelix server and put Idefix in it's present location and made sure all the servers were running fine and free of errors. Also, learned how to make the cat5 Ethernet cables from scratch.

02/25/2018- I think that Log watch one is  extra and not very generic. I'll meet my team mates on Tuesday and we'll further discuss about it and once all of us agree upon a specific tool will ask professor if we could install the tool or not.

02/26/2018- Installed Nginix (Load Balancer) successfully.


 * Plan: 02/23/2018- We will be conferring with Jonas the necessary steps to proceed with installation and also adding documentation to the Wiki on how to complete an install.

02/24/2018 - Camden and I are meeting on Monday after 5:30 to further review what should be done with Rome being unlinked and also sending Professor an email.

02/25/2018- I'll meet my team mates on Tuesday and we'll further discuss about all the tools I found via my research and once all of us agree upon a specific tool will ask professor if we could install the tool or not.

02/26/2018- We need to compose a list of the effected files by completing a *diff* from snapshot 1 to snapshot 2. I was not immediately confident onhow to read the diff output So i want to review before passing it by Jonas.


 * Concerns: 02/23/2018- Who unlinked Rome before us???? that is what is concerning me the most.

02/24/2018 - There are few equipments which are missing and making our lives harder however, we didn't give up and worked with whatever we have and fortunately everything worked fine.

02/25/2018-No concerns as of now.

02/26/2018- No concerns as of now.

Week Ending March 5, 2013

 * Task: 02/27/2018 :Today is Tuesday and we have a class. However, I and Camden as per our plan met before class and reviewed the installation of NGinix on Rome. We compared the differences between snapshots and determined there were little alterations made to the existing files. This allowed us to determine if it was safe for use. When in class Professor Jonas informed us that  there are no plans to move not planning to move it to Caesar.

03/01/2018- Today I researched on the top 10 error logging tools and I am still deciding on sticking with Log watch. However, I am planning on asking Camden to review it and also my other group members if we all agree that Log watch would be the best error logging tool for linux then we will plan on installing it sometimes next wek.

Below is the link which will give us an idea about installation, configuration, running the Log watch and what the reports will look like:

https://www.digitalocean.com/community/tutorials/how-to-install-and-use-logwatch-log-analyzer-and-reporter-on-a-vps

03/02/2018- Camden and I worked on getting the Nginx running. We also reviewed Log watch installations and the pros and cons of it. We are certainly having an issue with Nginix at this moment. When we looked into it we found out that the systems firewall was blocking Nginx. We also found out that there might be an issue with SElinux. We both are planning on looking at it and hoping to fix the issue in next two weeks (Fingers crossed). Now, moving on to Logwatch - Logwatch is a log analysis program that parses through system logs and generates periodic reports based on criteria specified by the user. These reports are generated immediately after Logwatch has run (normally every night) and can be sent by e-mail to a network administrator.

I did a lot of research on Log watch but seems like the output results of it is not what we expect it to be. I am going to have to look into details and research more on other error logging tools.

03/04/2018- Successfully met with Lamia from the software group and Daniel R from my group in the server room. I've been working with Dan R past couple of weeks on the servers. Dan R. is an awesome teacher. Below are the List of things I, Lamia and Dan R. did at the server room today:

-Added couple of more screws to secure the rack of servers.

-Relabeled all of the drones both the front and the back side of the rack.

-Relabeled Methusalix which is called the Traubadix now. Professor Jonas gave Methausalix a new name.

-Changed the cmos battery for a couple of the drones. Automatix, Asterix, Idefix and Miraculix has new cmos batteries now.

- Those batteries were brought by Dan and that is very nice of him. Dan brought 4 new cmos batteries all together and decided to donate it to the school. - Dan replaced 2 and allowed Lamia and I to replace the other 2 batteries.

-Manually configured date/time (under BIOS settings) after replacing the cmos battery

-Changed power strip location for Asterix and Automatix

-Installed bootable O.S in Automatix and  had to partition it manually.

-Dan taught Lamia and I all the steps to take when manually configuring Automatix to copy over Asterix on it.

The following needs new cmos batteries:

-Rome, Caesear, Obelix, Majestix need new cmos batteries


 * Results:02/27/2018 :Later in the afternoon, after class added Rome back to the rest of the network and remounted Caesar. However, did not put the symbolic link back (the one at/usr/local) as Nginx is located in the /usr folder.

03/01/2018- Discovered the process of installing, configuring, running the log watch and what the reports will look like once the Log Watch runs.

https://www.digitalocean.com/community/tutorials/how-to-install-and-use-logwatch-log-analyzer-and-reporter-on-a-vps

03/02/2018- Found out that the Nginx was having some issues. Also, the firewall was blocking Nginx, there might also be an Selinux.

03/04/2018- Worked successfully on the servers and configurations. Below are the results:

-Added couple of more screws to secure the rack of servers.

-Relabeled all of the drones both the front and the back side of the rack.

-Relabeled Methusalix which is called the Traubadix now. Professor Jonas gave Methausalix a new name.

-Changed the cmos battery for a couple of the drones. Automatix, Asterix, Idefix and Miraculix has new cmos batteries now.

- Those batteries were brought by Dan and that is very nice of him. Dan brought 4 new cmos batteries all together and decided to donate it to the school.

- Dan replaced 2 and allowed Lamia and I to replace the other 2 batteries.

-Manually configured date/time (under BIOS settings) after replacing the cmos battery

-Changed power strip location for Asterix and Automatix

-Installed bootable O.S in Automatix and  had to partition it manually.

-Dan taught Lamia and I all the steps to take when manually configuring Automatix to copy over Asterix on it


 * Plan:02/27/2018 :Meeting with Camden may be on Thursday/ Friday and work on setting up the functionality of load balancer and also work on a proper server map and maintenance log.

03/01/2018- Meeting with Camden on Friday and working with running Nginx and also reviewing Log watch tool.

03/02/2018- Researching more on Log tool and possibly meeting Camden before class and looking into Nginx and researching more on why it is causing problems.

03/04/2018- I plan on researching cmos battery for Caesar (Power edge 2900), also plan on helping Dan with cleaning up cables and managing them better so, that it looks much cleaner and nicer.


 * Concerns:02/27/2018 :No big such concerns as of now because our group is effectively communicating and making sure that we are on the top of everything we do. And if anybody is stuck in something we make sure to help them get through it.

03/01/2018- Log watch is a good tool but not sure if it exactly what we are looking for?

03/02/2018- As the systems firewall is blocking Nginx it's important to find out what the actual issue is and be on the top of our Task timeline. I am worried that the whole problem with Nginx will take a while getting solved.

03/04/2018- As of now I do not have any concerns. I need to figure out about the Error logging tool myself. Hopefully I'll be able to figure that out next week and start with the installation process.

Week Ending March 12, 2013

 * Task: 03/06/2018- Today we had a class and all of the group members gave status report to Prof.Jonas on where we all stand as a group. For our group professor gave us important review and suggestions which was really helpful. I will be working on my research for the error logging Tools for Linux. We decided not to move forward with Log watch because the output results are not what we expect it to be.

03/07/2018- Moving on with my research the three powerful error logging tools I think would be beneficial are : Gray Log, Petiti and Nagios. However, I think among these three Gray Log and Nagios are my top 2 preference.
 * Gray log is very compatible with Load Balancer integration which Camden is working on. So, that's a plus point.

03/10/2018- I reviewed the Wiki logs from the previous semesters tools group. I plan on reviewing it more throughout the spring break. So, I am sticking with my top 3 preference. Just waiting on my team members to respond. I should get their response by tonight and upon their response will email professor Jonas.


 * Results: 03/06/2018 As we decided not to move on with Log watch anymore hence, I researched for a bit and came across the three new powerful error logging tools for Linux.

03/07/2018- I narrowed down my research and found my top 3 prefered Error loggings tools.

03/10/2018- Sent out the message on slack to all my group members on my top 3 preference of the Error logging tool.


 * Plan: 03/06/2018- I will be researching more on depth about the three error logging tools I came across which think which is powerful and could be installed in the server.

03/07/2018- Once everybody is in the same page and we all agree on on error logging tool. I will send an email to Jonas and ask if I could install the tool.

03/10/2018- I spoke to Camden and we have planned on meeting either tomorrow the 11th or Monday the 12th and start with the installation once everybody approves of the tool including Professor. Also, I plan on reviewing and start updating the system wiki page as per the email of Professor Jonas. I will meet Camden either tomorrow or the day after tomorrow and get started with it.


 * Concerns: 03/06/2018 -No concerns as of now.

03/07/2018- No concerns as of now.

03/10/2018- No concerns as of now.

Week Ending March 26, 2013

 * Task: 03/20/2018- Today I met with my new team "Avengers" as well as met with my group "Systems". The meeting with my team was successful as we spoke about each of us have been working on and how could we possibly contribute going further. My new team "Avengers" decided that we will be meeting every Tuesday after class because that works the best for everybody's schedule and that way we are able to communicate effectively and properly. Also, today before meeting with the "Avengers" I met with my system group. Professor Jonas had assigned responsibilities to the system group during the spring break that Chris and Camden will be working on the Server Cloning while myself and Dan R will be working on the Data Backup however, on today's class as Dan R was absent Chris and Camden started looking into the data backup so, now we are wondering if we could switch tasks? We are awaiting on professor's confirmation for that.

03/23/2018- Today I worked on creating a short document for the future capstone student on Nagios. Nagios is also known as Nagios Core and is a free and open source computer-software application that monitors systems, networks and infrastructure. I also went through the logs from last semester because I plan on starting the experiments this weekend.

03/24/2018- Today my task included: Having group meeting with my systems group, cloning Miraculix with Daniel R, checking to see if we could get a good HDD for Traubadix- if the HDD is good then Dan.R and I will start installing a new copy of Redhat 6.8 onto it. Also, fiscally log into the new drone and rename the server for Traubadix and Rellocate the IP for Traubadix.

03/26/2018-Today I had ran the training/decoding for unseen data for the "Avengers" but I gotten error when I tried to create the experiment folder for the training addExp.pl -s. I tried multiple times but it wouldn't let me kept throwing an error. My group mate Camden offered me to help during the class session on Tuesday the 27th. Also met with Tri this morning and planned on modifying the Perl script parseLMTrans.pl. Professor Jonas wanted him to edit. I wanted to see what Data Group was doing so, definitely would love to be a part of this because this is something completely out of my comfort zone.


 * Results: 03/20/2018- I shared with my new team "Avengers" what Dan and I have been working on and to my surprise many of my team members had an idea what we been working on. Also, we set up our discord channel for the Avengers team and that has been really helpful. We have been able to communicate efficiently and purposefully.

03/23.2018- Created a document on Nagios core I have yet to finish it up and upload it on wiki for the future capstone students.

03/24/2018- The results included the following- 1) Dan R sent a message to everyone on our discord channel that we were currently shutting Miraculix so that we could start the cloning process. 2)Re-imaged the Automatix with the image that was created from Miraculix. 3)After Automatix had been re-imaged worked on renaming the new server.

03/26/2018- Today was not very productive as I couldn't ssh into Caesar or any of the drones and on top of that when I tried running the experiments it kept throwing an error. However there was one good outcome this morning. I met with Tri and we decided on working on the Perl scripts Professor Jonas had given him to modify going further.


 * Plan: 03/20/2018- My plan is to work with Daniel R. this weekend on either Data Backup or cloning the servers as I have mentioned above we are still waiting on Professor Jonas to tell us what we should do Cloning the servers or the data backup? as Chris and Camden had already started the Data Backup process I believe.

03/23/2018- I plan on reading more logs and plan on uploading the document which has about Nagios for the systems/ tools group next semester.

03/24/2018- I plan on meeting Dan. R on Monday or Tuesday because we were having some network issues. So, in order to resolve that we plan on meeting either Monday or Tuesday.

03/26/2018- My plan is to meet Camden on Tuesday and get the error resolved.
 * Concerns: 03/20/2018- Now that we are divided into two teams and plus working with our own group things are going to get very different. I need to learn how to manage my time and work efficiently with both my team and my group.

03/23/2018- My concern at this moment is there is so much to do and so little time. But I'm learning on managing my time well compared to before.

03/24/2018- Concern at this moment is resolving the network issue. Everything was all set for the cloning but because of the network issue failure and we were only allowed to be in the server room until 3 so we had to leave.

03/26/2018- Why can't I create a addExp.pl-s experiment folder?

Week Ending April 2, 2013

 * Task: 03/28/2018- As in my previous logged I stated I wasn't able to SSH into Caesar or any of the drones later in class found out I was having a VPN issue. However, the problem seems to be resolved now because I can perfectly login and run my decoding for unseen data on 5 hour train.

03/29/2018- This morning Tri and I met outside the school and worked on editing the Perl script. We removed both the brackets and dash character on both transcript and the language model.

For example:

[???]text -> text

-[???]text -> text

text[???] -> text

[???/text] -> text

03/31/2018- Today Daniel and I worked on reimaging Asterix again, because something wasn't allowing for correct network connectivity. After reimaging Asterix, we renamed the hostname of the Asterix server. 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. In addition, to this we worked on the URC Poster for our System Groups. The poster Camden shared with us had some issues and we weren't able to open it so Dan and I brainstormed ideas on what we want to put on our URC Posters. Because the poster template Camden sent us had some issues we put our ideas and contents on the word document and shared it with Chris and Camden and informed them they could add their thoughts into it and can copy and paste it on the template which has no issues.

04/02/2018- Today I ran a 30 hour unseen data. However, it crashed at the first time and I tried again the second time. The work is still on progress. I will share the result once it's complete. For the most of the part I also spent my time on research.


 * Results: 03/28/2018- My result for training/ decoding for unseen data on 5 hour train data is 63.9%

| 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 |

`-'

Successful Completion.

03/29/2018- The result Tri and I got is:

|=================================================================|    |  Mean   |  1.3   19.3 | 55.9   37.4    6.7   17.2   61.3   92.4 | | S.D.   |  0.5   16.5 | 22.1   19.7    8.5   30.6   32.6   24.6 | | Median |  1.0   15.0 | 51.4   39.1    4.0    7.1   61.5  100.0 | `-'
 * Sum/Avg | 4173 61273 | 46.8   44.1    9.1   10.0   63.2   92.3 |

03/31/2018- The results included: -Re-imaged Asterix and Renamed the Hostname of the Asterix server. - Modified the entire IP scheme which included networking paths, IP's and DNS addresses. - Worked on the URC poster. 04/02/2018-


 * Plan: 03/28/2018- My Plan is to Run more experiments this week. Hopefully a 30 hour Train by the end of this week.

03/29/2018- I plan on meeting with Tri hopefully during the weekend and work on editing the Perl scripts further.

03/31/2018- I plan on meeting Dan Tuesday and fix the issue we are running into potentially due to the hardware or the ethernet cables that isn't helping Asterix server connect to LAN and WAN.

04/02/2018- The result is on progress.


 * Concerns: 03/28/2018- I have never done anything with Perl before so, the real challenge is learning the Perl scripting one at a time. Also, Rose Salemi from the Data group was super helpful and she helped me get started with the basic perl scripting in class showing me a website which taught perl from scratch.

03/29/2018- My concern at this moment is I am still very new to Perl scripting so it's a little challenging but overall I am enjoying working with Tri because he is so helpful and willing to teach me.

03/31/2018- My concern at this moment is to figure out what's going on with the connectivity system of the Asterix server?

04/02/2018- At first when my 30 hour unseen data crashed I was worried however, when I tried for the second time seems like it's working. I am still awaiting on the result though.

Week Ending April 9, 2013

 * Task: 04/04/2018- Rephrasing back to the previous logs of mine as I am responsible for the Tools (Researching & Installing) best error logging tools while I found the one where my group and I came to a conclusion that was perfect for installation then we got divided into two bigger groups and professor Jonas assigned each of my "System group" member what was expected to be done. While I and Daniel were responsible for cloning he told us to specifically focus on areas that he assigned us so, I was no longer able to install the Nagios. Hence, Camden suggested me to do a write up on Nagios and upload it on the wiki page under "Systems group" . So, that spring 2019 students can look into it and install this awesome tool. Below is the link to Nagios document on"Systems group".

https://foss.unh.edu/projects/index.php/Speech:Spring_2018_Systems_Group

Furthermore, I was able to run a 30 hour train successfully after a crash at the first time but now I got a result of my 30 hrs unseen data.

04/06/2018- Today morning Tri and I met and today was all about research. We researched on finding the best variables possible for the tests. I went through the logs of the previous semesters (the bigger teams). Also my system groups finalized our posters.

04/08/2018- Today I worked with Camden on researching about rsnapshot. Rsnapshot is supposed to operate but it is not and at the same time it isn't giving any errors either. Hence, why we planned to research about it on depth.

04/09/2018- Today I met with Tri and we worked on editing our scripts to get the lowest percentage results. I can't talk much about it on this page but however, as a group we all agreed that we need to first ensure and check with the Professor on what we can share what we cannot and how much information we can give to the guardians.


 * Results: 04/04/2018- The result is that now the Nagios documentation is done and uploaded on wiki page under "Systems group". Spring 2019 students my group and I highly encourage you to install Nagios because it's a very awesome and powerful too which is also an open-source tool and is great for error logging, log monitoring and other good reasons which can be found in the "System Group"s document.

My 30 hours unseen data result is as below:

| Sum/Avg | 3912 55254 | 50.3   39.2   10.5    9.6    59.3    91.9 |

|===================================================================|

| Mean   |  1.3   18.1 | 59.2   33.4    7.4   18.3    59.1    91.9 |

| S.D.   |  0.5   16.2 | 22.5   19.3    9.4   38.8    40.4    25.5 |

| Median |  1.0   13.0 | 56.7   33.3    3.6    6.3    58.3   100.0 |

`---'

Successful Completion

04/06/2018- Today's meeting was successful however, it was more of a researching together and sharing our ideas and testing the experiments.

04/08/2018- Research is still on progress.

04/09/2018- Meeting was successful, Tri and I edited scripts. But I can't talk much about the scripts. This process is getting so confusing.


 * Plan: 04/04/2018- This week I plan on running two more experiments and also meet up with Dan. R on Sat like always and work in the server room. Also, I will read more logs.

04/06/2018- I plan on meeting with Tri this weekend or on Monday and work further.

04/08/2018- Camden and I decided once we finish our research we will definitely document the result of our research on our "Systems Group 2018" wiki page for the next years spring semester students.

04/09/2018- Plan is to confirm with Jonas tomorrow as a group on what information can be shared and what cannot.


 * Concerns: 04/04/2018- As of now I have no concerns.

04/06/2018- As of now my concern is being a little clueless on the strategies of getting the word error rate count lower.

04/08/2018- As of now there is no much concern.

04/09/2018- I feel like everyone has the same concern this week. We want to help spring 2019 semester students but at the same time we cannot write down our steps here, we want to make sure Data and Modeling are working together however, there is a conflict on what information can we give it to them and what we shouldn't. Hopefully! we sort this out tomorrow in class.

Week Ending April 16, 2013
04/14/2018- Email from Professor Jonas. Now system group has few things which needs to be taken care of. Camden assigned Chris, I and Dan what needs to be done.
 * Task: 04/10/2018- Met with the group today after class. Today was supposed to be a trade but that didn't happen from both the team. However, we decided to split among two groups Daniel is leading one group within the Avengers and Steve is leading another group within the Avengers.

04/16/2018 - I am planning to run an experiment today.


 * Results: 04/10/2018- Now we have two small groups within the Avengers. I can't disclose much what our small groups are doing.

04/14/2018- I am assigned to finish up the documentation for what has been installed in Rome. Additionally, I finished up my task for Avengers and submitted my report to the Avengers.

04/16/2018- I need to run an experiment and will document the results accordingly.


 * Plan: 04/10/2018- Plan is to finish the task Steve Assigned us.

04/14/2018- Plan is to finish up the documentation for Rome this week.

04/16/2018- Running experiment, Checking with the group if anything needs my attention. As of now we are doing pretty good. Both my Avengers and System groups.We are constantly in touch and communicating well.
 * Concerns: 04/10/2018- Time management is the concern.

04/14/2018- No concerns as of now.

04/16/2018- No concerns as of now.

Week Ending April 23, 2013

 * Task: 04/18/1028- Met with my Avengers group yesterday 04/17/2018 after class. We had a good discussion and everybody was given their respective task they need to finish. I can't mention about the task here but I have a folder where I have everything in so later I can print and give it to Jonas.

04/19/2018- Ran my 30 hours seen data with new genTrans and also worked on my Avenger's stuff (can't mention here).

04/20/2018- Worked on what I was assigned for this week for my Avengers group (I can't say it here). Had a meeting with my Systems group also and checked our statuses.

04/23/2018- Met with Tri, Worked with him (Regarding Avengers stuff) I have it on my personal worksheet what I did.


 * Results: 04/18/2018- I am assigned to partner up with Isac and we will be working on things related to the Avengers.

04/19/2018- My 30 hours seen with newgenTrans result is:

[yg3@caesar etc]$ tail -8 scoring.log | Sum/Avg | 3992 58136 | 74.9   18.5    6.6    7.9   33.0   87.7 | |=================================================================|     |  Mean   |  1.3   18.8 | 76.8   18.3    4.8   16.9   40.0   87.9 | | S.D.   |  0.5   16.0 | 18.0   15.6    7.2   31.3   35.2   30.3 | | Median |  1.0   15.0 | 78.1   16.3    0.0    4.4   33.3  100.0 | `-'

Successful Completion [yg3@caesar etc]$

04/20/2018- Online meeting was successful, finished what I was assigned for this week for my Avengers team.

04/23/2018- Meeting is successful, also communicating with the Avengers group mates along side.


 * Plan: 04/18/2018- I and Isac plan on meeting tomorrow once I get off work and finish the assigned Task.

04/19/2018- I plan on communicating with Lamia and get whatever needs to get done this week from my side.

04/20/2018- I plan on communicating with the Avengers team and finish up whatever needs to finish up.

04/23/2018- Communicating and getting things done, Implementing strategies.


 * Concerns: 04/18/2018- No concerns as of now.

04/19/2018 - No concerns as of now i think all my team members are doing great.

04/20/2018- Time Management. But we are getting there. All my Team mates are extremely hardworking.

04/23/2018- None as of now.

Week Ending April 30, 2013

 * Task: 04/27/2018- Met with Tri on 4/26/2018 and did our research (Avengers related) Can't write here.

04/29/2018- I was sick this week but was in constant touch with my group mates both systems and avengers. For System groups Camden asked us all to look into the previous reports and we plan on finishing our reports by the end of this week.

04/30/2018-


 * Results: 04/27/2018- Communicated with the group via discord on what we found

04/29/2018- This was a slow week for me compared to any weeks before because I fell sick.

04/30/2018-


 * Plan: 04/27/2018- Research, More research and Finish what needs to be done this week for Avengers

04/29/2018- Co-ordinate with both the group members. I have been assigned tasks this week will plan on finishing it.

04/30/2018-


 * Concerns: 04/27/2018- Stressing because of Time management.. I am sure all of us are.

04/29/2018- Less time, more work.

04/30/2018-

Week Ending May 7, 2013

 * Task:


 * Results:


 * Plan:


 * Concerns: