The University Libraries at UNCG currently track the state of a computer, determining whether or not a particular computer is in use. This data is compiled into a database, and a web app pulls from this database to show a map and number of available computers. As of Fall 2017, the data had not been used to determine which computers are used more frequently, aside from counting the number of times a computer transitions into/away from the 'in-use' state. This project attempts to correlate the usage of these computers with various factors, including: campus scheduling, equipment configuration, placement, population in the library, and area weather. Using this data, this project also uses machine learning to determine the best placement of computers for future allocation, and possible reconfiguration of equipment and space.
Final Project: The final project will be a team based data-science project utilizing available public data sets. In the first week of the course, the students split into teams and will be presented with a set of tentative project ideas to choose from. Novel ideas for projects will be awarded with a 5% bonus grading. After completing each course topic, the teams will have to give a short presentation (3-5 mins) and a report (1 page) of their progress with the project. The projects will be open-source and the teams will have to use GitHub as their code repository. Upon completion of the project the teams will present their software along with the results in form of a presentation (20 minutes) in the class. The teams will also prepare a poster of their project outlining the methodologies, visualizations, and results of their project. The teams will present their posters in a seminar accessible to other students and faculty at the Computer Science and Engineering Department. In addition to the poster presentation, graduate students will have to write a technical paper (minimum 5 pages, template at http://www.ieee.org/documents/trans_jour.docx (Links to an external site.)Links to an external site.) on their assigned project.
Elements highlighted:
Short presentation (3-5 mins) (I believe we've done these)
Report (1 page) (were we supposed to have done these?)
I think that we had some marginal consensus that creating import libs is fine, under certain circumstances and with some conditions? Please correct me if I'm mistaken.
I'd suggest the import routines be broken out so that they can be used by multiple notebooks, as we all seem to be working mostly in separate notebooks at this point. Other than that there doesn't seem to be a whole lot of code that would benefit from this kind of modularization.
In interest of making reading easier, I have a suggestion.
I've altered the first part of the GSOWeather.ipynb notebook in the manner I'm suggesting so you can see. In this case I've made a display method which takes an array as an argument, which can be fetched by either of our getWeather methods (one says All, and another says Hourly). The rest of the notebook can be easily altered in a similar manner. This is just to make it easier to maintain in the future. Thoughts?
As I'm looking at our utilization data, I think some statistics might be really low because we are including all the years for which usage doesn't exist. For example, it doesn't look as if BL001 was every in use in 2010, and I think that's because we didn't even have it at the time. But entries do exists - those entries are 0.0, not NaN. (I'm talking about the pickled data from LibData.pkl).
Do we have some dates for when computers were purchased/added to libraries? I think we should add code to discard entries for those computers before said dates and see if anything changes.
As mentioned in our meeting today, we can communicate a number of different ways. I'm comfortable with the following, but this is by-no-means an exhaustive, or even ordered, list of what I'm willing to use. Please mention in the comments if there is something missing, or if you have preferences towards a particular (mentioned or unmentioned) tool.
Prof. Mohanty suggested in class yesterday (Nov. 6) that we could present our project to a group of professionals on Nov. 27. It's the same day as the senior project presentations and some of those people will be looking at both sets of projects, and would be around 11am. If we participate, two of us would give about a 20 minute presentation. It's good exposure, and Prof. Mohanty said he could also make sure that (for example) the dean of libraries Dr. Martin Halbert was there, which would be good since our project particularly pertains to that and would ensure that it is seen.
It's right before exams, so we should have the project 90% completed by then. I'm down for it, what do you guys think? If we're going forward with it I'll need to email him by tomorrow morning.
We need to test our code in develop before merging into master - master is the gold standard that we really, really, don't want to screw up. Brown, do you have a test program in place? If not, can you respond with how you run your code so that we can look at it?