Updating readme.

README.md

@@ -1,6 +1,11 @@
 # dtype-next
 
-Next generation high performance Clojure numerics stack and toolkit.
+Next generation high performance Clojure toolkit.
+
+
+[![Clojars Project](https://clojars.org/cnuernber/dtype-next/latest-version.svg)](https://clojars.org/cnuernber/dtype-next)
+
+[![Build Status](https://travis-ci.com/cnuernber/dtype-next.svg?branch=master)](https://travis-ci.com/cnuernber/dtype-next)
 
 tech.datatype has been a great library for TechAscent and has allowed us to produce
 quite a lot of high performance software.  We were able to push the Clojure
@@ -16,16 +21,21 @@ Some expected items:
    the system needs to produce the right answers with less type specific code.
 *  Full native memory support.  Malloc, free, memset, memcpy.  Just the basics but
    guaranteed to be available.
-   
-   
+
+
 Checkout the [api documentation](https://cnuernber.github.io/dtype-next/)
-   
+
 ## Native Test
 
-* In order to get mmap working on the native test I had to grab the larray .so from the 
+* In order to get mmap working on the native test I had to grab the larray .so from the
   uberjar and load it manually.  Not a big issue at the end of the day but I was having
   problems getting graal native to package resources.
-
+
+Use the scripts to get graal and compile test.  The code is located under native-test; so far
+reader/writing/copying all work for native and jvm heap datasets.  Tensors work but appear to
+really make the executable size larger; potentially this is the insn bindings which perhaps could
+be optional.
+
 
 ## Graal Native