"A" on my Senior design project(Software Engineering) ....almost out dis bytch

[videogamestashbox.com]

Over the last big hill !!!
(mostly nothing but random electives left)



​

EDIT:
For clarity, depending on the program it's called "Senior Design Project" or "Capstone Project".
Which is a class in your senior year that consist of a single project that is supposed to demonstrate your ability to use/apply all the material taught throughout the various classes taken in the program(Software Engineering in my case) to solve a "real world" problem.​

 

[Neo. The Only. The One.]

Then fix the coli, nikka!

 

[videogamestashbox.com]

Then fix the coli, nikka!

Yooooooo!!!! hahaha


OH shyt, I didn't see that one coming​

 

[MajesticLion]

Niceness

 

[thenatural]

That's tight man. What were some of the details of your project if I may ask?

 

[UWasntThere]

How old are you? Where do you go?

 

[DrDoom]

Congrats man

 

[videogamestashbox.com]

That's tight man. What were some of the details of your project if I may ask?

NUTSHELL:
It was a data visualization project commissioned by a research group at a library.

Prior to us coming in:

• They took a bunch of materials related to some old English author.
• Digitized materials related to them via OCR
• Hand corrected the OCR ...cause OCR damn near always fukks up(at least any time i've used the software)
• Then housed the data on an open sourced system for Library science called Omeka
• Added meta data
• exported data to a CSV file
• created 1 or 2 proof of concept visualizations in house that references those csv files

Tasks we had to perform(3 parts):

• Add functionality to pre existing visualizations
• Create new visualizations(part I worked on)
• Add functionality to the Omeka backend administration

New Visualizations:
I used the Vis.js library vis.js to create an interactive timeline to visualize the data. React tables were also used but I didn't work on that part.
I was working on adding tables using the danfo.js Library(similar to pandas dataframes) Creating a DataFrame - Danfo.js
I showed everybody mockups of the timeline and table system I was going to use during the 1st Cycle. Then halfway through the 2nd Cycle one of the guys on the Libraries internal team came in with react tables which undercut what I was working on(Less work for me tho). So I just focused on the vis.js timeline.

Only real hangup was that the Omeka backend API pulls take like 12 seconds to aggregate/relay the data.
As a result when you start up the Visualization you have to wait for that 12sec.
I was looking to get around that by...

1. do a regular API pull and save the data locally to the browser on the first run of the visualization
2. pull from local browser storage on subsequent runs of the visualization for instant usage
3. while visualization is active run a webworker in the background to perform an API pull of up to date data
4. save the up to date data to the local browser storage.
5. rinse and repeat steps 2-4 on all visits to the visualization ...step 1-4 if browser cache is cleared

The catch was that webworkers can't access local / session storage in the browser.
While working on a workaround they decided to just run a CRON job periodically that creates an updated CSV file with all the data needed for the visualizations.

 

[Ghost Utmost]

Oh so you may Senior now Breh?



Good shyt Brethren! Gratz!

 

[Alix217]

Congrats

 

[the bossman]

NUTSHELL:
It was a data visualization project commissioned by a research group at a library.

Prior to us coming in:

• They took a bunch of materials related to some old English author.
• Digitized materials related to them via OCR
• Hand corrected the OCR ...cause OCR damn near always fukks up(at least any time i've used the software)
• Then housed the data on an open sourced system for Library science called Omeka
• Added meta data
• exported data to a CSV file
• created 1 or 2 proof of concept visualizations in house that references those csv files

Tasks we had to perform(3 parts):

• Add functionality to pre existing visualizations
• Create new visualizations(part I worked on)
• Add functionality to the Omeka backend administration

New Visualizations:
I used the Vis.js library vis.js to create an interactive timeline to visualize the data. React tables were also used but I didn't work on that part.
I was working on adding tables using the danfo.js Library(similar to pandas dataframes) Creating a DataFrame - Danfo.js
I showed everybody mockups of the timeline and table system I was going to use during the 1st Cycle. Then halfway through the 2nd Cycle one of the guys on the Libraries internal team came in with react tables which undercut what I was working on(Less work for me tho). So I just focused on the vis.js timeline.

Only real hangup was that the Omeka backend API pulls take like 12 seconds to aggregate/relay the data.
As a result when you start up the Visualization you have to wait for that 12sec.
I was looking to get around that by...

1. do a regular API pull and save the data locally to the browser on the first run of the visualization
2. pull from local browser storage on subsequent runs of the visualization for instant usage
3. while visualization is active run a webworker in the background to perform an API pull of up to date data
4. save the up to date data to the local browser storage.
5. rinse and repeat steps 2-4 on all visits to the visualization ...step 1-4 if browser cache is cleared

The catch was that webworkers can't access local / session storage in the browser.
While working on a workaround they decided to just run a CRON job periodically that creates an updated CSV file with all the data needed for the visualizations.

Congrats breh. Do you already have a job lined up? What do you hope to do career wise