Speech:Spring 2018 Christopher Nobrega Log


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

Week Ending February 5th, 2018
Task — Get assigned a team and meet with them towards the end of class.
 * 01/30/2018:

Results — Today we had our first meeting as a team after class. We figured out which days everyone was available and discussed how we would communicate

as a group. We decided that we would meet in-person as a team every week on Friday to discuss our progress, issues we ran into, etc.. We also decided that we would use

Slack to communicate when we are not together. I set up a new Slack channel and emailed everyone in the group an invitation. I discussed TORQUE with Camden,

neither of us had any experience with it (nobody else in the group did either). I read through TORQUE's wiki page https://wiki.archlinux.org/index.php/TORQUE and

noticed that at the top it bluntly recommends not using TORQUE if you are only attempting to increase compilation throughput (which I believe we are).

Camden mentioned that we could look into using Docker as a possible alternative (which many of us have used previously). Camden and I also discussed that if we

are going to be setting up any new servers, how we might go about it without affecting any of the other students.

Plan — Our plan for this week is to meet in person on Friday at 6:00pm (and every Friday going forward).

Concerns — My only concerns at the moment are figuring out exactly what we will include in our project proposal.

Task — Set up the development environment on my laptop (in addition to my desktop) and continue reading through the logs from previous semesters.
 * 02/01/2018:

Results — For today's results I also set up the development environment on my laptop (in addition to my desktop). I installed the virtual private network

software (Pulse Secure), I installed PuTTY, logged into Caesar through PuTTY (caesar.unh.edu as the ip, 22 as the port (default)), updated my password, and ran

the keygen command to allow my to access the other servers without having to login to each. I also think that I have a better idea of what this semester will

look like after reading other student's logs from previous semesters.

Plan — Our plan for this week is to meet in person on Friday at 6:00pm (and every Friday going forward).

Concerns — My concerns at the moment are figuring out what we will include in our project proposal and after reading other the logs from previous students I'm

concerned that any ideas we put forward to improve the system infrastructure are not going to be allowed (in order to preserve the "current state"). Which is

understandable but frustrating.

Task — Today I am meeting with my team on campus to discuss the details of what we will be working on, how will are going to divide the work, etc.. This is
 * 02/02/2018:

our first meeting outside of class, we plan to continue meeting as a team every Friday at 6:00.

Results — For today's results I met with my team on campus to discuss the details of our project. This was our first meeting outside of class, we plan to

continue meeting as a team every Friday at 6:00. The meeting went well, we discussed each member's strengths and weaknesses, what we had learned from reading student logs

from previous semesters, and ideas that we might use for the project proposal. A few of the ideas we discussed include: looking at old server logs for issues that students

have encountered in the past, creating a list of tools installed on the server, creating a sitemap on a local webpage, looking into the server's security (checking open ports,

vulnerability, integrity, etc.), evaluating the backup system, creating a service window (scheduled down-time), creating a folder for deletions, looking into TORQUE, fixing

the messy IP scheme, installing the new hard drives, etc.. We probably won't include them all, we are planning to prioritize them how much they will benefit the users. We

also decided that our main focus is going to be on maintenance, integrity, performance, and security.

Plan — Our plan is to email the professor to ask for access to the server room. We will also meet in person on Tuesday after class and again on Friday at 6:00.

Concerns — I do not have any significant concerns right now.

Task — Today I am going to try to run an experiment. I also plan to read through more of the logs from previous semesters.
 * 02/03/2018:

Results — For today's results I managed to get much further in running an experiment than my first attempt. I created a new experiment under 0303

https://foss.unh.edu/projects/index.php/Speech:Exps_0303_018 and I followed the instructions on this wiki page https://foss.unh.edu/projects/index.php/Speech:Run_Train_Setup_Script.

The experiment ran for a while until it failed at module 99 (Convert to Sphinx2 format models). It gave me a few parameters to try to rerun it with, which I will look into next.

Here is a screenshot of the message it displayed https://www.dropbox.com/s/uh3x0s8hj2h25er/Screenshot%20%28147%29.png?dl=0. Camden also ran into the same issue.

Plan — Our plan for this week is to meet in person on Tuesday after class and again on Friday at 6:00.

Concerns — I do not have any significant concerns right now.

Week Ending February 12, 2018
Task — Today I am going to be meeting with my team during and/or after class (if there is a lecture). Hopefully we can decide which items to focus on for
 * 02/06/2018:

our first draft of the project proposal (we already have a few ideas from our last meeting).

Results — During class We talked to prof. Jonas about some of the items we need to complete. Some of the things that we are considering working on include:

checking the internals of the new machines, figuring out how to install the new machines (there are no racks), checking the state of the backup (every week

something should run), look at the power strip (fuse keeps blowing?), checking the power draw of the servers, look at the changes that Zach made, consider

normalizing all of the machines (impact?), etc.. We also got feedback from Jonas on a few of our ideas (to add monitoring that will alert us if the server goes

down and implementing login load balancing). Prof. Jonas liked both of the ideas so long as they were low impact.  After class we met in the server room to

discuss which ideas specifically we wanted to include in our project proposal. I took notes and we weighed each idea out considering how much of an impact they

would have on the users and prioritized them by how beneficial we thought they would be. In the end we decided that the main tasks we wanted to focus on for our

project proposal included: setting up the new servers, evaluating the backup system, normalizing the machines, implementing load balancing for users (login, etc.),

and looking for tools to better analyze the logs. We also have a list of bonus ideas in-case we are able to complete the above tasks earlier than expected.

Plan — Our plan for this week is to meet on campus this Friday at 6:00. We will also be working on the draft for our project proposal. I will personally

be working on getting the experiment to successfully run (it looks like I'm getting close).

Concerns — I do not have any significant concerns right now. It is becoming much more clear what we will be working on over the next few weeks.

Task — Today I am going to meeting with my team outside of class on campus at 6:00 (for the second time). Our plan is to work on our project proposal draft.
 * 02/09/2018:

I posted my notes from our previous meeting about which features we wanted to focus on and Yashna is putting together a rough draft (of our draft). During our

meeting we are going to make sure that it is all set and make any changes that are necessary.

Results — We met as a team on campus today. We reviewed the project proposal draft Yashna had put together from my notes. Worked on laying out the timeline

for our proposal and decided how we would divide the work. I also found a student license option for Asana (a project management tool that we are using), which

might allow us to invite all of the other students so we can keep all of our tasks in one place. Yashna is going to fill out the form to request the license (since

the project is under her account). For my tasks I am going to be creating a local file storage system for all of the teams, collaborating with Camden on adding a

custom monitoring system, and evaluating the state of the backup system (state, redundancy, etc.).

Plan — I will personally be working on getting the experiment to successfully run (it looks like I'm getting close). I talked to a few students from other

groups who got to module ninety-nine in running a train where it exits and then asks you to run it again using another parameter. Nobody is sure if this is

supposed to be an "error" or if that is considered a success (I am leaning towards it being an error). I am going to continue looking into the logs since it seems

like there are a few errors to see if I can figure anything out. I am also going try to figure out what each of the parameters are supposed to do and what effects

they might have if I re-run the train with them.

Concerns — I do not have any significant concerns right now. It is becoming much more clear what we will be working on over the next few weeks.

Task — My task for today is to get the experiment to run successfully (past module ninety-nine). I will also be reading the logs from previous semesters.
 * 02/10/2018:

Results — After having a discussion with Camden during our meeting, it looks like module ninety-nine may be the last module in running a train. It looks like

it stops at module ninety-nine to wait for input, and once it gets input from the console it says done. Now I'm not sure if "done" means that it successfully completed

or if it just means that it is done running (and should be re-run). Other students in the class believe that module ninety-nine is the last module, but I'm not sure.

Plan — I am going to try to find more information about running the train in the logs from previous semesters. I want to make sure that I am running the train

successfully.

Concerns — I do not have any significant concerns right now.

Task — My task for today is to read Zach's logs from the previous semester (as requested by prof. Jonas). I am also going to look at what else I need to do
 * 02/11/2018:

to validate that I have successfully finished running my first experiment.

Results — I continued reading through Zach's logs from the previous semester. I am starting to get a better understanding of the changes he made. I also

started reading through the next steps in running an experiment in the wiki.

Plan — I am going to meet with my group this Tuesday (during and/or after class). We will also meet this Friday on campus at 6:00pm.

Concerns — I do not have any significant concerns right now.

Week Ending February 19, 2018
Task — Today I am going to be meeting with my team during and/or after class (if there is a lecture).
 * 02/00/2016:

Results — Today I briefly met with my team during class and then went with Daniel to the server room to get a head start on installing the new servers.

We started by opening up the new servers to check if they were missing any components, etc.. The first server we opened was did not have any ram. I

searched through the server room and the storage room, but the only ram I found was super outdated. So we will need Jonas to get us the ram we need if we

want to set up that server. Next Camden joined us and we opened up the second server. It had ram but it was missing a hard drive. We found one in the

server room and installed it. Camden and Daniel went to work on figuring out how to mount the new server/s without rack mounts. I sent out a notification

to the class that we would be taking one of the servers temporarily offline and I also informed prof. Jonas. While they were working on that I began to

work on fixing the issue with the server not working with the monitor. After that I also looked into what we need to do after mounting and cloning the new

servers (updating licenses, IP addresses, etc.). I spent some time on Google and found this link

https://superuser.com/questions/207342/what-must-be-changed-for-cloned-linux-systems?rq=1. Which contains a Linux command (sys-unconfig) that should walk us

through making all of the necessary changes. For future reference: I found that you need to be logged in as the root user in order to shut the server down.

Below are the relevant commands that I used in the process.

su - rootpass (to login as root)

shutdown now (to shutdown) (Will come back to update)

Plan — My plan for this week is to meet with my group on campus this Friday at 6:00. I am planning on creating the local directory for file sharing on

the server as well as starting on at least one of my other tasks (assuming that creating the local directory for file sharing is not going to take a long time. Concerns — I do not have any significant concerns right now.

Task — Today I am going to be meeting with my team outside of class on campus at 6:00 (for the third time). Our plan of items to discuss (from Camden) includes
 * 02/16/2016:

going over any changes we have made to the server room since we last met, ensuring that everyone can run a train, wrapping up the final proposal, and determining

the best way to have a summary of what we're working on prepared for when Jonas asks us during class.

Results — We had our third meeting as a team and for the majority of the time we worked on fleshing out our section of the project proposal. I personally worked

on taking the goals from the timeline of our previous draft and fleshed them out to explain more about what we would be doing and who would be responsible for doing

what. We also decided what to do for when Jonas asks us for a status update. We will be meeting as a team thirty minutes before class each week to give Daniel an

overview of what each of us have been working on. Daniel will then present our changes to prof. Jonas during class.

Plan — My plan for the remainder of this week is to work on setting up the local file sharing directory for the class on the servers and to wrap up running

my first experiment. Concerns — I do not have any significant concerns right now.

Task — Today I am going to be working on finishing up running my first experiment. I've successfully run a train, now I need two finish the last two steps.
 * 02/17/2016:

Results — I successfully ran an experiment. Here is a link to the entry in the wiki https://foss.unh.edu/projects/index.php/Speech:Exps_0303_025.

|=================================================================|     | Sum/Avg |   41    777 | 69.9   21.8    8.4    5.5   35.6   90.2 | |=================================================================|     |  Mean   |  1.3   24.3 | 72.5   20.5    7.0   12.7   40.2   89.1 | | S.D.   |  0.5   22.0 | 22.0   18.8   11.2   23.3   25.4   30.4 | | Median |  1.0   19.0 | 71.4   19.5    3.1    3.0   38.8  100.0 | `-'

Plan — My plan for tomorrow is to work on setting up the file sharing directory for all of the teams (as outlined in our proposal). Concerns — I do not have any significant concerns right now.

Task — Today I am going to work on setting up the file sharing directory for all of the teams (as outlined in our proposal)
 * 02/18/2016:

Results — Today I added a new directory called sandbox (cd /mnt/main/sandbox/). This directory can be accessed by anyone from any server. You can use it

for sharing and storing files with each other without breaking prof. Jonas's rules about not using third party file sharing services. Don't forget that you can

use FileZilla to drag and drop files (if you are not comfortable with the command line). I created sub-directories for each team (data, experiments, modeling,

software, and systems) and a general directory for everyone to use. I also notified all of the teams about this new file sharing system.  I also updated all of

the folder permissions (chmod 770) to make sure everyone had the correct access to use the new sharing directories.

Plan — I am going to look into adding a recycle folder with a chron job that cleans it out periodically (thanks to a suggestion from Camden) for the file

sharing directory. I will also be meeting with my group thirty minutes before class next Tuesday. Concerns — I do not have any significant concerns right now.

Week Ending February 26, 2018
Tasks — Today I am going to be meeting with my team before class to discuss any changes we've made (that Daniel will present to prof. Jonas).
 * 02/19/2018:

I will also be meeting with them after class to discuss our next steps. Results — Today I met with my team before class to discuss the changes we've made (that Daniel presented to prof. Jonas during class). My

personal changes / update included: added file sharing directory for each team, fixed the file sharing directory permissions issue, added a

recycling directory to the file sharing directory, started working on a chron job to clean out the recycling directory periodically, and

finished running a five hour experiment successfully. After class we discussed what each of us would be work on for the next week and we decided

to move our weekly meetings from every Friday on-campus to every Saturday online (due to time conflicts within our group).

Plan — My plan for this week is to work on the chron job to periodically clean out the shared file directory's recycle bin. I will also be

looking at the possibility of evaluating each file in the recycling bin and deciding whether to delete them or not based on the date they were

moved to the recycling directory (that way anyone who moves a file to the recycling directory will have the same amount of time to change their

mind and move the file out as everyone else).

Concerns — I do not have any significant concerns right now.

Tasks — Today I will be working on updating our section of the project proposal to reflect the changes that prof. Jonas requested in an email
 * 02/20/2018:

(he wanted our group sections to look more like a previous semester).

Results — Today I worked on updating our section of the project proposal to reflect the changes that prof. Jonas requested in an email. I

updated our group's section to look more like that of a previous semester. We then received another email from prof. Jonas that he appreciated

the changes we had made but the rest of the class had not updated their sections respectively and that we would lose more points (as a class) by

having inconsistent formatting than we would gain from having updated our section alone. We informed the rest of the class that they needed to

update their sections by 9:00 (when the assignment was due) or if they could not we would revert our changes to the old formatting. We couldn't

get every group to update their section in-time so I reverted our changes, but Rose asked Jonas for an extension (which we got). The team

leaders then decided which format we would all update our sections to follow and I spent the rest of the night updating our section to reflect that.

Plan — My plan for the rest of the week is to meet with my team outside of class for our fourth weekly discussion. We are planning to discuss

what each of us are currently working on, what each of us plan to work on next, and any issues / concerns that anyone has. I will also be looking

into evaluating the current state of the backup system. Concerns — I do not have any significant concerns right now.

Tasks — Today I will be meeting with my team outside of class for our fourth weekly discussion. We are planning to discuss what each of us
 * 02/24/2018:

are currently working on, what each of us plan to work on next, and any issues / concerns that anyone has. These weekly meetings tend to go

pretty smoothly so I don't have any concerns that this week's with be any different. One change to this week's meeting however is that we will

be meeting online instead of in-person to better accommodate everybody's schedules. I don't think it will have a big effect on the value of the

meeting though. Results — Today I met with my team outside of class for our weekly discussion. We discussed what each of us are currently working on, what

each of us plan to work on next, and any issues / concerns that anyone has. I told my team that I have been working on required updates to the

project proposal and that I will be working on evaluating the backup system next.

Plan — My plan for the remainder of this week is to begin evaluating the state of the backup system. Concerns — I do not have any significant concerns right now.

Tasks — Today I am going to begin researching how I should approach evaluating the backup system. I am going to start by looking through
 * 02/25/2018:

the wiki for any information from previous semesters. Results — Today I started looking through the wiki for any information about the backup system. I found this entry in the wiki:

https://foss.unh.edu/projects/index.php/Speech:Backups I'm not sure how up to date the information is so I am going to conduct a few tests

that prof. Jonas requested to ensure that the backup system is working as expected (creating a file, waiting a week, and seeing if it can be

retrieved from the backup system).

Plan — My plan is to meet with my team before class on Tuesday to discuss what each of us accomplished this week so that Daniel can

present our changes to Jonas during class. Concerns — I do not have any significant concerns right now.

Week Ending March 5, 2018
Task — Today I am going to be meeting with my team before class to discuss any changes we've made (Daniel will present our changes to prof.
 * 02/27/2018:

Jonas during class). After class we will meet as a team (again) to discuss what we intend to work on for the rest of this week.

Results — Today I met with my team before class to discuss the changes we've made (that Daniel presented to prof. Jonas during class). My

personal changes / update included: working on the project proposal, started reading the previous semester's backup system documentation,

started reading the rsync documentation, found the installed version of rsync, started experimenting with rsync in a remote test machine to get

familiar with it before making any changes on the production machines, and that I will be evaluating the state of the actual backup system this week.

Plan — My plan for this week is to begin evaluating the state of the backup system.

Concerns — I do not have any significant concerns right now.

Task — Today I am going to be setting up a test directory with a few files that I will make incremental changes to over the course of the next
 * 03/02/2018:

week that I can use as a reference point when I'm testing the backup system (I will be able to see which files were successfully backed up and what

point in time they were backed up).

Results — I created a test directory and a test file that I will be making changes to over the course of this week. I will use this directory

and the files within it as a reference point when I'm testing the backup system (I will be able to see which files were successfully backed up and what

point in time they were backed up). I also continued to read the existing documentation on the wiki about the backup system to help improve my

understanding of how the current implementation is set up across the multiple servers.

Plan — My plan is to meet with my team outside of class on Saturday and begin really testing the backup system this weekend. During our meeting

each of us will share what changes we have made, any issues we have run into, and what we will be working on between Friday and class next week.

Concerns — I do not have any significant concerns right now.

Task — I am going to be meeting with my team outside of class today. During our meeting each of us will share what changes we have made, any
 * 03/03/2018:

issues we have run into, and what we will be working on between Friday and class next week.

Results — We each discussed the changes we have made and what we will be working on next. We also decided that during our next meeting will

will evaluate the timeline from the proposal to make sure that we are still on track. I updated the backup system test directory today as well (to

allow me to see which files were successfully backed up and what point in time they were backed up when I begin conducting actual tests with the backup system).

Plan — My plan is to work testing the backup system from now until our next class.

Concerns — I do not have any significant concerns right now.

Task — Today I am going to be working on testing the backup system.
 * 03/04/2018:

Results — I started out by re-reading the existing documentation about the backup system on the wiki. Then I decided I would find the backup

snapshots and make sure that they were still updating automatically (as expected). However, I quickly found that the documentation on the wiki was

outdated and a lot has changed. To start with, I found some of the daily backup snapshots on rome but when I checked what day they were last

modified it was in 2016. Next I decided I should login directly to the backup server to check the snapshots on there. However, the backup server

has been renamed since the documentation was last updated so I could not connect to it. Camden recommended checking the hosts file on Rome to see

if it listed the updated ip address for the backup server. I found that it did have a new ip address (capstonebackup 172.16.0.25), however I was

unable to connect to it (I couldn't ping it either). I updated the backup system test directory today as well (to allow me to see which files were

successfully backed up and what point in time they were backed up when I begin conducting actual tests with the backup system).

Plan — My plan is to meet with my team before class to discuss any changes we've made (Daniel will present our changes to prof.

Jonas during class). After class we will meet as a team (again) to discuss what we intend to work on for the rest of this week.  I will

personally be focused on finding out why I cannot connect to the backup server.

Concerns — I do not have any significant concerns right now.

Look at snapshots (Rome)

su - (login as root)

cd ~

cd /root/.snapshots

ls -l (see last modified)

Find ip of backup machine

ssh rome

su - (login as root)

cd /etc/

cat hosts

capstonebackup 172.16.0.25

tried ssh to name and ip from rome and putty

cannot connect to host capstonebackup port 22: No route to host

cannot connect to host 172.16.0.25 port 22: No route to host

Can't ping either

Week Ending March 12, 2018
I do not have any electricity or internet due to a winter storm. I have informed the other members in my group of my predicament and will

continue my work where I left off once I get power back.

Week Ending March 26, 2018
Task — Today I will be meeting with my team (Guardians) for the first time and my group (systems) before class. During my meeting
 * 03/20/2018:

with my team we will introduce ourselves, share our strengths and weaknesses, discuss team leadership, objectives, etc.. During my

meeting with my group (systems) we will discuss any changes made during spring break, issues that came up, and what our objectives are

for the upcoming week.

Results — During the meeting with my team (Guardians), we introduced ourselves, discussed strength and weaknesses, elected Camden

to be our leader, and establishes a basic framework for how we will set and approach our objectives.

Plan — My plan for this week is to focus on getting more familiar with what the other groups have been working on and collaborate

with Camden to get the backup system back up and running.

Concerns — I do not have any significant concerns right now.

Task — Today, Camden and I are going to be working on restoring the backup system.
 * 03/21/2018:

Results — We found a lot of information about the existing backup system and started attempting to diagnose the issues. We found

that the backup system is trying to use a machine at 195.168.1.5 but there's no machine there... found the rsnapshot config file at

/etc/rsnapshot.conf, enabled ssh on the backup machine (you can access it at 172.16.0.22, needs to be accessed from rome? (seems to

hang when accessed from Caesar)), and found some information about the vm (VMkernel localhost 5.5.0 #1 SMP Release build-3116895 Oct 2 2015

12:27:22 x86_64 GNU/Linux) among other things.

Plan — Our plan is to come to campus again this week to continue working on restoring the backup system.

Concerns — I do not have any significant concerns right now.

Task — Today I will be meeting with my team for our first weekly discussion (outside of class) and I will also be meeting with
 * 03/24/2018:

my group for our weekly discussion. I am also going to be doing some research related to the backup system and how the overall system

works as discussed with my team at our previous meeting.

Results — I met with both my team and my group outside of class. My team discussed what we've been working on and delegated tasks

for each of us to complete by the end of the week. I am going to be working with Dan on looking into the LDA's next week.

Plan — My plan for the remainder of this week is to continue working with Camden on getting the backup system up and running.

Concerns — I do not have any significant concerns right now.

Task — Today Camden and I will be meeting on-campus to continue working on restoring the backup system.
 * 03/26/2018:

Results — We found that the ESXi virtual machine that was supposed to be hosting the RedHat server is missing. We tried accessing

it through both the vSphere local website and the local client, but neither method worked. We also found that the entire directory intended

to hold the vSphere ESXi management tool is missing.

Plan — We have emailed professor Jonas about our concerns and have asked him if we can wipe the current mess that is the backup

system and re-do everything with a clean install of Ubuntu, instead of messing around with vmware. We should be able to get a new backup

system up-and-running in half the time it will take to restore the existing one to a functional state and it should eliminate all of the issues

that we are currently dealing with for future capstone projects.

Concerns — I do not have any significant concerns right now.

Week Ending April 2, 2018
Task — Today I will be meeting with my group on-campus after class. I will either continue working on the backup system with Camden today or
 * 03/27/2018:

I might help Dan with licensing the new servers they have set up.

Results — Camden and I installed Red Hat on the backup server, configured the network and dns, created a backup folder on rome and the backup

server, backup server can now connect to rome and rome can connect to the backup server, using rome's secondary ip address (not primary), we were

not able to mount it (check nfs utils?). Internet shows no connection but local area network (LAN) works.

https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.0/html/Administration_Guide/ch09s02s02s04.html

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-nfs-server-config-exports

Red Hat account information (not registered)

backupManager

Back Manager

Root Password (same as other machines)

Plan — I will be meeting with Camden on campus later this week to continue working on getting the backup machine up and running.

Concerns — My only concern right now is getting a Red Hat license. We know from prof. Jonas that UNH has access to a few thousand Red Hat licenses,

but we don't know where they are or how to get one.

Task — Today I will be meeting with Camden on-campus to continue working on the backup machine.
 * 03/29/2018:

Results — I met with Camden on-campus to continue working on the backup machine. We ran into prof. Jonas and asked him where we could find the Red Hat

licenses allocated to UNH. He told us that we should talk to Bruce Johnston at the UNH IT department. I went to the UNH IT department to talk with Bruce

Johnstone about getting a Red Hat license. Bruce said that he would send me an email with some of the information of how to get the license. I eventually got

the email but it looks like a complex process, so I am going to be going through it to try to figure out how to actually get the license this week.

Plan — After speaking with prof. Jonas we are going to Check to make sure that caesar is licensed, check if we can copy the package we need nft

from rome, add documentation for registering red hat on the wiki (w/big red note "use these sparsely"). I am also going to run a 5 hour train on

Miraculix with LDA disabled to establish a baseline result for Miraculix.

Concerns — I do not have any significant concerns right now.

Task — Today I will be running a 5 hour train on Miraculix with LDA disabled to establish a baseline result for Miraculix.
 * 00/30/2018:

Results — I encountered a few errors trying to run my trains. Camden is looking into what caused the errors. While I was waiting, I started working on

updating the existing backup server documentation (in a separate document) to reflect all of the changes that Camden and I are making.

Plan — Tomorrow I will be meeting with my team (Guardians) for our second meeting outside of class.

Concerns — I do not have any significant concerns right now.

Task — Today I will be meeting with my team (Guardians) and my group (systems) outside of class.
 * 03/31/2018:

Results — Today I met with my team (Guardians) to discuss what each of us have accomplished and what we will be working on for the upcoming week. I also

started looking into the audio files as Rose asked with audacity. I also continued looking into RNN and I found a log from last semester that claimed they had

evaluated RNN and found that it did not provide any significant improvements.

Plan — For the next week I will be focused on running trains with various parameters and settings as a part of my task from the Guardians team. For my work

with the systems group I will be helping out with the various posters we have to do and collaborating with Camden on wrapping up our work on setting up the backup server.

Concerns — I do not have any significant concerns right now.

Week Ending April 9, 2018
Task — Today I will be helping Dan figure out how to change the welcome message that appears when logging into Traubadix (it currently shows the welcome message
 * 04/03/2018:

from the server we cloned onto Traubadix). I will also be meeting with my group (systems) before class to find out what they want to present as our changes for this week

to prof. Jonas when he goes around to each group asking for our status reports.

Results — I found out how to change the welcome message that appears when logging into Traubadix (it previously showed the welcome message from the server we cloned

onto Traubadix). I found that the welcome screen message that appears is formally called the motd (message of the day) and it can be found and edited for each server in a

file called motd within the /etc/ directory. https://serverfault.com/questions/407033/how-can-i-edit-the-welcome-message-when-ssh-start

Plan — My plan for the rest of this week is to work on tasks for my team (Guardians).

Concerns — I do not have any significant concerns right now.

Task — Today I am going to work with Camden to create the URC poster for the systems group. If I have time I will also continue to look into registering the Red Hat servers.
 * 04/04/2018:

Results — Today I worked with Camden to create the URC poster for the systems group. I am going to share the poster with the other members of our team to see if they

have any feedback, see any issues, etc. and if they do not I will submit the poster to prof. Jonas by the end of this week (as both a .pdf and a .pptx).

Plan — My plan for the rest of this week is to work on tasks for my team (Guardians), and to make sure our URC poster is submitted to prof. Jonas on time.

Concerns — I do not have any significant concerns right now.

Task — Today I am going to work on figuring out how to get the Red Hat registration licenses.
 * 04/07/2018:

Results — Today I worked on figuring out how to get the Red Hat registration licenses. I am also taking notes of the steps I take along the way to provide future Capstone students

with documentation on how to access the licenses (it does not appear to be a straight-forward process at the moment)... I started by attempting to access cinnabar.unh.edu (a UNH server

where the licenses are supposedly held), the instructions had a preview image of cinnabar.unh.edu that showed a html dashboard, but nothing came up when I went to that address. I then

thought that maybe it required me to be on the UNH vpn to access the server, so I downloaded pulse secure and tried again... it still would not connect. I then asked Camden and Dan if

they could access the server (in case the issue was on my end specifically) and they could not either. Camden however pinged the server and found that it was up, and that it should

redirect you to something... but it doesn't. I continued reading through the emails that were forwarded to me to see if I missed anything.

Plan — My plan for the rest of this week is to continue trying to decode the Red Hat registration instructions and continue looking into LDA for my team (Guardians).

Concerns — I do not have any significant concerns right now.

Task — Today I will be looking into the audio files with Audacity as I discussed with Rose previously. My goal is to figure out if the .sph files sample rate, bandwidth, or frequency
 * 04/08/2018:

are going to give us any trouble and/or effect our results. I am going to start by trying to figure out what the deal is with the audio file's extension. I remember prof. Jonas mentioning

that the .sph files are similar to .wav files but I'm not sure how they will work with audacity.

https://cmusphinx.github.io/wiki/tutorialtuning/

https://cmusphinx.github.io/wiki/faq/#q-what-is-sample-rate-and-how-does-it-affect-accuracy

https://cmusphinx.github.io/wiki/faq/#q-what-is-sample-rate-and-how-does-it-affect-accuracy/

Results — I read all of the articles and documentation Rose had found. I am still working on figuring this out, but I now have a better understanding of how everything works together.

Plan — My plan for this upcoming week is to continue looking into the audio files for Rose and LDA for my team (Guardians). I will also try to wrap up getting the new Red Hat licenses

to register the machines.

Concerns — I do not have any significant concerns right now.

Week Ending April 16, 2018
Task — Today I will meet with my team (Guardians) after class and with my group (systems) before class. I also plan to finish getting the Red Hat registration licenses.
 * 04/10/2018:

Results — I went to the server room to see if I could access cinnabar.unh.edu from Caesar. Most of the instructions are written with the assumption that you are accessing

the website from the Red Hat machine you are registering. I tried accessing the website from computer both on my own network, through the UNH vpn, and on the UNH network previously

(none of them worked). I eventually figured out that something is messed up with cinnabar's ssl certificate (which results is most browsers automatically blocking you from accessing it).

I managed to get around this restriction by manually adding an exemption for the website in Firefox. This allowed me to actually get to the cinnabar.unh.edu login screen. I tried logging

in with my University of New Hampshire account, but it was denied.

Plan — I'm going to continue reading though the emails now that I've figured out how to get to the login screen to see if I can find the required account credentials. If they are not

in the email I will have to ask prof. Jonas or get in touch with Bruce.

Concerns — I do not have any concerns at the moment.

Task — Today for my team (Guardians) I will be going through each server and checking what version of Python is installed for both the user directories and the root directories.
 * 04/13/2018:

I will also be working on a few tasks that I can't share on the wiki due to the competition.

Results — After going through each server and checking what version of Python is installed (as of 04/14/2018), I found that every server is running Python 2.7.13 except for Obelix

and Rome which are running 2.6.6. It appears that Idefix does not have Python installed. I have shared a spreadsheet of these results with prof. Jonas and with my team (Guardians).

Plan — I am going to wait for a response from Jonas regarding the above results. If he thinks it is worth maintaining documentation in the wiki about what version of python each

server is running I will document it in the wiki.

Concerns — I do not have any concerns at the moment.

Task — My initial plan for today was to document the results from yesterday on the wiki, however prof. Jonas informed me that the results are no longer correct as prof. Jonas has
 * 04/14/2018:

since updated all eight servers to python 2.7.13. And I might have actually checked the versions after his update as most of them match up (PYTHON 2.7.13) except for the ones that aren't

linked (which are also the ones I highlighted as possible issues).

Results — I am going to go through all of the servers again to confirm what prof. Jonas claimed (that all of the eight servers have been updated to python 2.7.13). I will document

the results of that on the wiki.

Plan — Next I am going to try to wrap up the license registrations.

Concerns — I do not have any concerns at the moment.

Task — Today I will be working on a few items for my team (Guardians) and I am going to try to wrap up the license registrations for the new Red Hat servers.
 * 04/06/2018:

Results — After reading through all of the documentation for registering the Red Hat licenses (again), I have determined that we have no clue what and/or where the login information is

or who has it. I will have to ask prof. Jonas or get in touch with Bruce to see where we can find it.

Plan — I will be meeting with my team (Guardians) and my group (Systems) before class.

Concerns — I do not have any concerns at the moment.

Week Ending April 23, 2018
Task — Today I am going to meet with my group (systems) before class to discuss what we want to present to prof. Jonas as our changes during the status
 * 04/17/2018:

check. I will gather the changes from everyone and then I will present the information to prof. Jonas in class during the status reports.

Results — Today I met with my group (systems) before class to discuss what we want to present to prof. Jonas as our changes during the status check.

However, prof. Jonas decided to skip the status check this week.

Plan — My plan for the rest of this week is to wrap up the Red Hat registrations for the new machines (assuming I get a response from Bruce about the

account credentials) and I will be working with my team (Guardians).

Concerns — I do not have any concerns right now.

Task — Today I am going to be reading logs from the other members of my team and group.
 * 04/21/2018:

Results — Today I read logs from the other members of my team and group.

Plan — I am going to wait for a response about Red Hat registration account, work on assignments for my team (Guardians).

Concerns — I do not have any concerns right now.

Task — Today I am going to be reading the logs from my other team members (Guardians) to catch up on what everyone is working on.
 * 04/22/2018:

I think that it will help when I am working on my section of the final report to have a better understanding of what everyone experienced in more

detail than the quick status updates posted in the Discord discussion.

Results — Read logs.

Plan — Wait for response about Red Hat registration account, work on assignments for my team (Guardians).

Concerns — I do not have any concerns right now.

Task — Today I am going to be researching how we can fix the speed of the backup system. Reading the logs from my other team members (Guardians) to catch up on what everyone is working on.
 * 04/23/2018:

I think that it will help when I am working on my section of the final report to have a better understanding of what everyone experienced in more

detail than the quick status updates posted in the Discord discussion.

Results — I worked on a rough draft for my section of the final report.

Plan — I am going to be meeting with my team (Guardians) and my group (systems) tomorrow before and after class.

Concerns — I do not have any concerns right now.

Week Ending April 30, 2018
Task — Today I am going to continue researching how to speed up rsync for the backup system (Camden mentioned that he ran into a few issues with the performance).
 * 04/24/2018:

Results — Today I continued to research how to speed up rsync for the backup system. I found a few articles and forum posts that all said you should copy the directory

that you are attempting to backup prior to ruuning rsync (because rsync is slow and works by backing up files based on the changes (so if you haven't backed up anything yet

every single file needs to be transferred to the backup machine, not just the files that changed since the previous backup)). A few of the articles also mentioned parameters

that you should avoid to increase the backup speed (like z). Here are two of the articles I found while I was researching this:

https://superuser.com/questions/109780/how-to-speed-up-rsync

http://sebastianraschka.com/Articles/2014_python_lda.html

Plan — Next I am going to be working on the Guardians report.

Concerns — Aside from hoping that everyone completes their evaluations in time, I do not have any concerns right now.

Task — Today I am going to be working on the Guardians report.
 * 04/28/2018:

Results — Today I began working on my portion of the Guardians report (focused on LDA). I drafted a rough outline of the section and will continue to add more details and

clean it up over the next few days.

Plan — Tomorrow I am going to be meeting with my team (Guardians) and my group (Systems) outside of class.

Concerns — Aside from hoping that everyone completes their evaluations in time, I do not have any concerns right now.

Task — Today I am going to be meeting with my team (Guardians) and my group (Systems) outside of class.
 * 04/29/2018:

Results — Today my team (Guardians) did not have a meeting since everyone has been active on Discord there is not as much of a need for it. I had a quick discussion with my

group (Guardians) over discord instead of our weekly meeting to discuss what each of us are working on, anything we need help with, and what we will be working on for the remainder

of the semester.

Plan — Tomorrow I will continue working on the Guardians report and the wiki documentation for the systems group.

Concerns — Aside from hoping that everyone completes their evaluations in time, I do not have any concerns right now.

Task — Today I am going to be working on the Guardians report and the wiki documentation for the systems group.
 * 04/30/2018:

Results — We decided to change the format of our final report to match the report from 2015 (since we think Jonas will prefer that format). However, this eliminated the section

that I had been working on for LDA. I'm going to focus on the wiki documentation to see what is missing and what we can improve to help future capstone classes.

Plan — Tomorrow I am going to be meeting with my team (Guardians) and my group (Systems) after class.

Concerns — Aside from hoping that everyone completes their evaluations in time, I do not have any concerns right now.

Week Ending May 7, 2018
Task — Today I am going to be working on the final report.
 * 05/01/2018:

Results — Today I worked on the final report, I began by transcribing the overview and our initial goals from our proposal. I started adding a rough description

of each section for our results (performance, integrity, reliability, and documentation). I will continue to flesh this out over the next few days.

Plan — I will continue to flesh out our section of the final report over the next few days.

Concerns — I do not have any concerns right now.

Task — Continuing to work on the final report and reviewing the logs of other students.
 * 05/03/2018:

Results —

Plan — I will continue to flesh out our section of the final report over the next few days.

Concerns — I do not have any concerns right now.

Task — Continuing to work on the final report and reviewing the logs of other students.
 * 05/04/2018:

Results —

Plan — I will continue to flesh out our section of the final report over the next few days.

Concerns — I do not have any concerns right now.

Task —
 * 00/00/2018:

Results —

Plan —

Concerns —