Differences

This shows you the differences between two versions of the page.

--- projects [2015/08/11 20:45] – jarek
+++ projects [2015/08/17 12:02] – jarek
@@ Line 2: / Line 2: @@
 \\
-===Data visualization in Skydive===
+=====Data visualization in Skydive=====
 **Supervisor: Jarek Gryz**
-Skydive is a prototype system designed for database visualization using a concept of the socalled
+Skydive is a prototype system designed for database visualization using a concept of the so called
 data pyramid. The system is composed of three modules (DB - Database Module, D2I -
 Data-to-Image module, and VC - Visualizaton Client). Each is designed to use a different type
@@ Line 16: / Line 16: @@
 Currently the system support three presentation models implemented within the Visualization
 Component, namely:
 • a 2D heat-map;
 • a 2.5 D heat-map by 3D barchart; and
 • a 2.5 D terrain (by mesh and UV-mapping).
@@ Line 29: / Line 32: @@
 . Add support for specular and normal maps for 2.5 D terrain presentation model.
-Background Requirements
+Required Background: CSE 3421, Java programming course, (C programming course a plus)
-• Java programming course
 \\
-===Genome-wide identification of plant micro RNAs===
+=====Genome-wide identification of plant micro RNAs=====
@@ Line 80: / Line 83: @@
 \\
+=====Dynamic Interface Detection and Control Project=====
-===Dynamic Interface Detection and Control Project===
 **Supervisor: Michael Jenkin**
@@ Line 175: / Line 176: @@
 \\
-====== Hunting for Bugs in Logging: applying JPF to log4j ======
+====== JPF in a Jar ======
 **Supervisor:** Franck van Breugel
 Description:
-Java PathFinder (JPF) is a tool that can detect bugs in Java code.
+JPF, which is short for Java PathFinder, is an open source
-The Java library Apache log4j allows developers to control which log
+tool that has been developed at NASA's Ames Research Center.
-statements are output.  In the past, Dickey et al. [1] have attempted
+The aim of JPF is to find bugs in Java code.  Instead of
-to detect bugs in log4j by means of JPF with very limited succes.
+using testing to find those bugs, JPF uses model checking.
+The facts that JPF is downloaded hundreds of times per month
+and that some of the key papers on JPF have been cited more
+than a thousand times reflect the popularity of JPF. In
+fact it is the most popular model checker for Java.
+A study done by Cambridge University in 2014 found that the
+global cost of debugging code has risen to $312 billion annually.
+Furthermore, on average software developers spend 50% of their
+programming time with finding and fixing bugs.  As a consequence,
+advocating the use tools, such as JPF, may have significant impact.
+Installing JPF is far from trivial.  The tool itself has been
+implemented in Java.  Therefore, it should, in theory, be
+feasible to encapsulate JPF in a Java archive (jar) file.
+This would make it significantly simplifying the installation
+process of JPF and, therefore, make the tool more easily
+accessible to its potential users.
-Recently, in collaboration with Shafiei (NASA) we have developed
+The aim of this project is to attempt to put JPF in a jar.
-an extension of JPF called jpf-nhandler.  The aim of this project
+Since JPF relies on a number of configuration files, so-called
-is to apply this extension to log4j.
+Java properties files, incorporating these properly into the
+jar is one of the challenges.  Setting JPF's classpath is
+another challenge.  Since JPF changes almost on a daily basis,
+our modifications to JPF should ideally be limited to only a
+few classes, yet another challenge.
-[1] David A. Dickey, B. Sinem Dorter, J. Michael German, Benjamin D. Madore, Mark W. Piper, Gabriel L. Zenarosa. "Evaluating Java PathFinder on Log4J."  2011.
+In this project you may collaborate with graduate students
+of the DisCoVeri group (discoveri.eecs.yorku.ca) and
+computer scientists of NASA.  For more information, feel
+free to send email to franck@cse.yorku.ca.
 **Required Background:** General CSE408x prerequisites