![]() ![]() It is known that visualization greatly alleviates software maintenance. Identifying anomalies, and more importantly, proposing actions to improve the quality is difficult. The source code defining a software may be very large and is characterized using a wide range of metrics and structural properties. Visualization plays an important role in assessing the quality of a software. ![]() Moose is the result of a collaborative effort, initiated at the University of Bern, which now comprises several companies and research groups spread all over the world. Going FurtherĬheck out Part 2 of this tutorial to expand this app beyond the Raspberry Pi to a full size PC.Moose is a platform for data and software analysis. Development Buildsĭevelopment builds of the software are available from the continuous integration server. Now, run the app with the new code changes. mvn packageĬopy the new ‘with-dependencies’ JAR file, found under the target/ directory, to the Raspberry Pi. Issue the following command to package changes into a new JAR file. Make any changes you would like to see.The classes that do the sound visualizations are in the .meter package, in the pixel-commons project.Open the ‘pixel-commons’ project from the directory where you cloned the Pixel APIs. Open the subproject named ‘sound-visualizer’ from the directory where you cloned the main Github project. Netbeans is the preferred IDE for PIXEL development. The main application is in this repository.The source code is available on Github Clone both repositories below. Install an init.d script to have the application start at every reboot. It avoids having to SSH into the Raspberry Pi to start the app if/when it re-boots. Having the application run at boot makes for a huge convenience. If you'd like to explore more information about this project or remix it and implement it yourself, here are some helpful resources and tips for going further with this project. ![]() Here is the Pixel board before the port housing is removed: E6000, or any other adhesive you have around, can be used to better secure the female jumper wire to the Pixel board. Then use the female end to connect to header pins on the Pixel board. You can also use hookup wire if you do not wish to cut your jumper wires. Using some female to female jumper wires, cut one in half, and solder the bare end directly to the microphone (or Sound Detector). A pair of needle nose pliers can be used to gently remove the port housing. ![]() The Pixel board uses Grove ports, while the SparkFun breakouts do not, so the port housing needs to be removed to attach the microphone. This project uses the SparkFun microphone or the SparkFun Sound Detector. The Pixel board has several ports for attaching input sensors or output components. Use this quick start guide to get familiar with the Pixel hardware. Come on back once you have your Pi booting into Rasbian. There is also plenty of great info to setup your Raspberry Pi on the Raspberry Pi Website. If you're new to Raspberry Pi, SparkFun has a Getting Started with Rasbian Guide. Suggested Readingīefore diving into this project, you may want to check out these other tutorials first. You could also use a beefy battery pack, such as this one, to power this project on the go. Thus, LiPo batteries were used to power the Raspberry Pi and the Pixel Board in conjunction with some boost circuitry. However, for this project, I wanted the entire setup to be mobile/wearable. Often the Raspberry Pi is powered from wall Adapter Power Supplies. A male to male USB cable is needed for this connection. The Raspberry Pi needs a serial connection to the Pixel. More info on this product can be found here. Additional SuppliesĪlso used in this project is the Pixel Board, which is used to control LED matrices. Here is a list of SparkFun parts used in this project, if you would like to follow along. The final project, displaying a quick Pac-Man demo. ![]()
0 Comments
Leave a Reply. |