Jacob Christiansen
Team Leader, Coder
I was responsible for our front end development as well as being our team lead. Largely what I learned was how to be a software designer. I knew how to code and to plan before this class, however to succeed in this class it took a lot more. I learned how to conduct meetings and break down problems so different parts of the group could work on things at different times. I also learned how to work with other software designers outside of our group through meetings with both our client Dr Toby Hocking, as well as the designer of the open source software we extended on github, @cmdColin. To successfully create a project on the scale as this one took much more than just knowing how code. The much more important thing was all of the infrastructure we put in place. That was what took the most time and what ultimately made us successful.
|
Allen Clarke
Architect, Coder
I have been responsible for our backend server as well as helping with the database and ensuring we can connect the server to NAU's GPU Cluster, Monsoon. Throughout the project, one of the biggest challenges for me was understanding how range requests work. They are not like traditional GET requests a server receives from a browser because they do not return an entire file, but a byte range from within the file. Implementing a server that handles range requests was a big accomplishment for me and I was able to do so by modifying an existing python library and extending it to meet the needs set by JBrowse on the web browser.
|
Yuanyuan Fu
Release Manager, Coder
I am responsible for the design of the basic interface, and set up a database to ensure that the database can store data and models and return the models required by the user to the server. In this process, the biggest challenge is that each marker has a variety of information and multiple markers need to be stored each time. I can build Berkeley Database through python code to achieve fast storage and retrieval of data.
|
John Jackson
Recorder, Editor, Coder
I acted as the team's document editor, formatting our written documents, proofreading, and line-editing to establish consistency. In this capacity I grew familiar with the software LaTeX and with the standards of professional software documents. In the second semester I was tasked with using Travis-CI to simulate a request from the server to Monsoon. One thing I learned, while iterating toward a working travis.yml file, was to use a shebang line so our test file was run as Python rather than a bash script.
|
