Add files via upload

README.md

@@ -1 +1,44 @@
-# CAIRAD
+# CAIRAD
+Implements the CAIRAD techique for detecting noisy values in a dataset. Does this with an analysis of coappearance between values. Can output whether or not a record is noisy (i.e. includes 1 or more noisy values), or remove all noisy values and replace them with missing values. 
+
+CAIRAD specification from:
+
+*Rahman, M. G., Islam, M. Z., Bossomaier, T., & Gao, J. (2012, June). Cairad: A co-appearance based analysis for incorrect records and attribute-values detection.* In The 2012 International Joint Conference on Neural Networks (IJCNN) (pp. 1-10). IEEE. Available at [http://doi.org/10.1109/ijcnn.2012.6252669](http://doi.org/10.1109/ijcnn.2012.6252669)
+
+For more information, please see Associate Professor Zahid Islam's website [here](http://csusap.csu.edu.au/~zislam/)
+
+## BibTeX
+```
+@inproceedings{rahman2012cairad,
+ author = {Rahman, Md Geaur, Islam, Md Zahidul, Bossomaier, Terry, and Gao, Junbin},
+ title = {CAIRAD: A Co-appearance based Analysis for Incorrect Records and Attribute-values Detection},
+ booktitle = {Proceedings of IEEE International Joint Conference on Neural Networks (IJCNN 12)},
+ date = {10-15 June}
+ year = {2012},
+ isbn = {978-1-4673-1488-6},
+ doi = {10.1109/IJCNN.2012.6252669}
+ location = {Brisbane, QLD, Australia},
+ pages = {2190--2199},
+ url ={https://ieeexplore.ieee.org/abstract/document/6252669},
+ publisher = {IEEE},
+ keywords = {data pre-processing, data cleansing, data mining, noise detection},
+}
+```
+
+
+## Installation
+Either download CAIRAD from the Weka package manager, or download the latest release from the "**Releases**" section on the sidebar of Github. A video showing the installation and use of the package can be found [here](https://www.youtube.com/watch?v=JUyKobCxruI)
+
+## Compilation / Development
+This repository houses a Netbeans project. Load the project into Netbeans to work on the package. Alternatively, download CAIRAD.java and import it into your Weka project to use it in your code.
+
+## Valid options are:
+
+`-T`
+coappearanceThreshold - Coappearance Threshold, tau in original paper.
+
+`-L`
+coappearanceScoreThreshold - Coappearance Score Threshold, lambda in original paper.
+
+`-M`
+makeNoisyMissing - Make detected noise into missing values. 

build.xml

@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<!-- By default, only the Clean and Build commands use this build script. -->
+<!-- Commands such as Run, Debug, and Test only use this build script if -->
+<!-- the Compile on Save feature is turned off for the project. -->
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
+<!-- in the project's Project Properties dialog box.-->
+<project name="CAIRAD" default="default" basedir=".">
+    <description>Builds, tests, and runs the project CAIRAD.</description>
+    <import file="nbproject/build-impl.xml"/>
+    <!--
+
+    There exist several targets which are by default empty and which can be 
+    used for execution of your tasks. These targets are usually executed 
+    before and after some main targets. They are: 
+
+      -pre-init:                 called before initialization of project properties
+      -post-init:                called after initialization of project properties
+      -pre-compile:              called before javac compilation
+      -post-compile:             called after javac compilation
+      -pre-compile-single:       called before javac compilation of single file
+      -post-compile-single:      called after javac compilation of single file
+      -pre-compile-test:         called before javac compilation of JUnit tests
+      -post-compile-test:        called after javac compilation of JUnit tests
+      -pre-compile-test-single:  called before javac compilation of single JUnit test
+      -post-compile-test-single: called after javac compilation of single JUunit test
+      -pre-jar:                  called before JAR building
+      -post-jar:                 called after JAR building
+      -post-clean:               called after cleaning build products
+
+    (Targets beginning with '-' are not intended to be called on their own.)
+
+    Example of inserting an obfuscator after compilation could look like this:
+
+        <target name="-post-compile">
+            <obfuscate>
+                <fileset dir="${build.classes.dir}"/>
+            </obfuscate>
+        </target>
+
+    For list of available properties check the imported 
+    nbproject/build-impl.xml file. 
+
+
+    Another way to customize the build is by overriding existing main targets.
+    The targets of interest are: 
+
+      -init-macrodef-javac:     defines macro for javac compilation
+      -init-macrodef-junit:     defines macro for junit execution
+      -init-macrodef-debug:     defines macro for class debugging
+      -init-macrodef-java:      defines macro for class execution
+      -do-jar:                  JAR building
+      run:                      execution of project 
+      -javadoc-build:           Javadoc generation
+      test-report:              JUnit report generation
+
+    An example of overriding the target for project execution could look like this:
+
+        <target name="run" depends="CAIRAD-impl.jar">
+            <exec dir="bin" executable="launcher.exe">
+                <arg file="${dist.jar}"/>
+            </exec>
+        </target>
+
+    Notice that the overridden target depends on the jar target and not only on 
+    the compile target as the regular run target does. Again, for a list of available 
+    properties which you can use, check the target you are overriding in the
+    nbproject/build-impl.xml file. 
+
+    -->
+</project>

manifest.mf

@@ -0,0 +1,3 @@
+Manifest-Version: 1.0
+X-COMMENT: Main-Class will be added automatically by build
+