Embedded Files
Introduction:
Our team has designed different layouts, models, and flow charts for potential ideas for the Nanolab GUI. Our team has focused our concepts towards simplicity and efficiency, enabling the user to reach their data most effectively and providing ease of use. There is going to be the main page that is either going to consist of buttons and/or pictures and subpages that correlate to the sensors. Our team has brought up the idea of having multiple interfaces regarding different ages, (people would log into the interface would need to input their age and the interface would act accordingly - the person can choose to switch interfaces, however).
Out main page will be simple and only contain icons and buttons for the user to navigate. There will be buttons for the sensors, data or graph, and camera.
Sketches regarding the data page. They will prvide the user the date, time, and what data/sensor point was recorded. The data page could use sesnor buttons to navigate the user the data points of each specific sensor, this could also lead to grpahs for each sensor. The graph feature will show graphs for each sensor.
Sketches regarding the graphs of each sensor. One possibility is when the user clicks the graph button, it will show the user ALL graphs of the sensors. If the user clicks one sensor, the chart dedicated to the sensor will show. Another possibility is showing the data points and time when the user clicks the sensor. The user can then choose what times they want to view the graph.
A whole sketch regarding the sensors. Another idea was implemented where if the user wants to view the graph of a certain sensor, the interface will prompt the user to input the desired time (or it could just be editable). Also, the volume will be calculated using a pixel-to-metric ratio via pictures from the experiments).
A gerneric sketch for the interface. Each page will lead to another. Main page has three main buttons that will lead to three subpages (Snesors, camera, and data).
Flowchart 1: Sensors
Flowchart 2: Camera
Flowcharts that model potentail solutions to the Nanolab GUI.
Flowchart 1: Flowchart for the senrors. The uer will choose a sensor on the GUI (which will be autonomaticlly determined if it is compantible), then the user will either be able to view the data files or graph recorded by the sesnor.
Flowchart 2: Flowchart for the camera. The user will be able to view the files of each picture taken; the user will be able to change/set their desired date to view the picture/s.
Conclusion:
After peer review, we concluded that a mass sensor is not needed, and Nanoracks will transfer data at least two times a day to see substantial results. The graphs are looked at positively; however, the user wants to interact with the time/or diagram within each data set. Our team addressed this by designing a feature where the user will choose a time/date period of their desire (for the graph), and there will also be options to switch between multiple charts (Bar, Line, and Pie). After review with the NASA team, graphs may not be necessary to experienced individuals (the interface should be primarily used for data collection), however, we can offer a feature where the data can be exported to excel.
Page updated
Google Sites
Report abuse