Paper Map

Research at Kary

Kary Foundation has always been about research. With a very small team†1, we have done more innovative research than many of the hugest companies. Our fields of research includes many, but our mission as advancing the state of computation, and bringing it to anyone has always remained the same.

    Only 3 researchers!

We have done an enormous scale of R&D to find out best ways to done computing, interacting with it and most importantly making it comfortable for anyone to use. However our mission has never been a way for us to limit ourselves and we have always been looking for any computational challenges that interested us and even working with many great firms developing computational solutions for the ever evolving world out there.



      KaryScript is a programming language that compiles to JavaScript. Our sole goal with the project was to figure out the most readable syntax for a third generation programming language with almost all the common features. KaryScript's syntax is designed to be as much as possible "linear", "easy to write" and "easy to read". Some examples of this can be said as:

        • Pipes: Pipes are designed to convert an expressing like (x (y (z))) into (z) -> (y) -> (x). That is far more readable and linear.
        • Markdown Tables: KaryScript takes the table notation introduced within Markdown language and brings that into programming. So 2D objects and arrays are now possible within KaryScript.


                In development of software with massive string processing†2 Regular Expressions become very limiting and there isn't any room for improvement. Wildcard (The syntax of RegExp†3) is a very limiting one that very soon riches a development-hell. As we had huge business with the language we found that we can no longer use it. What we did was to start a research to find a substitution for the syntax to address the following issues:

                  Computer Languages, Text Editors, Data Scanners, Data Mining Tools...
                  The naming is due to the use of single characters as operators
                • There is no whitespace in wildcard. That makes managing the code very hard.
                • Because you have no whitespace in wildcard you can't have comments either and there are also no support for comments in the language. Without comments any codes gets bad over time.
                • Using single characters as commands are very band and confusing so you can't really read the code when it gets huge

                  In the other hand wildcard is very fast because the tying takes so much tiny fragment of the time. We tried many experiments and the result was the Orchestra Language. Orchestra is a visual language which makes the development really simple, super fast†4 and very much readable.

                  Orchestra compiles to wildcard so you can use the result everywhere the RegEx is available without sacrificing any of your fast RegExp engines. We also have equipped Orchestra's IDE with a second reverse-compiler that compiles RegExp into Orchestra. This way you can load any of the existing RegExes you have and edit them as if they were Orchestra code. More than Orchestra optimizes and adds safety to your code. It safely compiles Unicode and non-basic English characters and takes care of special chars, match groups and grammars to ensure your code always works the same on every machine.

                    This one is a bit interesting, Visual programming languages turned out to be really bad because with many features the languages ends uy with many blocks and for finding these blocks you have to search them which is equal to the work you do in the programming, however there comes configuring each block. RegExes are very simple so the language is really fast if it be in a visual environment


                      It was spring of 2015 that we had a talk with Energy Lab's team at BHRC†5. One thing we understood was Code19†6 has no computation support. The standard is based on static building envelope evaluation which is not used in many of the countries these days.

                        Iran's National Road, Building and Urban Development Research Center
                        Iranian standard for building energy efficiency

                      We started by creating a building heat transfer coefficient (H) computation algorithm. We designed it to be modular and programmable in some certain levels. This way we could compute H in the normal manner but also with the specific formulas and data provided by Code19 (and any other standard based on same system). In order to make our algorithm comfortable we developed an SketchUp plugin that was integrated to OpenStudio's†7 plugin for SketchUp†8. So that modelers could open their existing OpenStudio models and then add the attributes†9 not supported by OpenStudio.

                        OpenStudio is an open source interface developed by U.S. National Renewable Energy Laboratory for EnergyPlus (main building energy simulation software used by possibly the whole industry)
                        A very interesting implementation in which HeatStudio takes advantage of the shared namespace between SketchUp extensions. This way HeatStudio gets plugin of SketchUp and OpenStudio, both at a same time.
                        Building type, Thermal bridges

                        Kary Framework

                        At the start we had a library of foundation's shared .NET code base, Trough the time it changed to be a string formatting library and se we developed Kary Framework. It brings four library four our interests:

                        • Kary.Base — The base for Kary Framework. It implements a rich string manipulation system for shaping textual user interfaces.
                        • Kary.Intactus — A mathematical notation engine that renders formulas via plain text to bring notations to textual UI.
                        • Kary.Numerica — An arbitrary precision numerical type for .NET that supports up to 56 billion digit.
                        • Kary.Calculat — Fork of NCalc math evaluator engine for .NET with an improved grammar and type casting switcher that also has support for Kary.Numerica.

                              Kary Graph

                              In order to practice large scale UI software design†10 we started some UI experiments, one code named Hedron Experiment 4 started to interest us in creating a visual graph theory studio.

                                Particularly in order to develop our visual language

                              Graph brings a rich graph editor in company with an interactive mathematica notebook-like environment to work on graphs. Our intention was to build a tool for data analysis but soon it became so easy to use that we now believe it's the most potential software for educational and scientifically use too.


                                    Arendelle is our very minimal and stylish sketching programming language for kids. It was a very massive project of us (containing 30+ sub-projects†11.) that was a very good road for us as we had the chance to study a variety of language implementation designs and theories and also studied the design of the most language tooling software around.

                                      5 compilers and interpreters, 3 IDEs, 5 code highlighting servers, 2 console REPLs, A language/context aware IDE autocomplete server, 3 Editor Language Supports, A code formatter, 3D print model generator, So many sample projects, Documentation tool, A book, etc…

                                    Arendelle has many innovative ideas that makes it potentially the best textual language for the sake of education. These key features includes:

                                      • Intelligent Grammars — Arendelle grammars are smart so they bring another level of high-level thinking to programming. For example, for all kinds of repeating structures†12, Arendelle introduces only one grammar†13 And it's Arendelle's job to understand if the grammar is a conditional or a range based loop.
                                      • Higher order file system abstractions — We designed an abstraction layer for namespaces and classes to map them into file system by making storage and procedures act in harmony as files. This way we could easily educated children about the concepts of scopes via modules and namespaces.
                                      • Redefined Procedure Return System — We shaped Arendelle's function return system based on a new idea. Arendelle loads a space called @return for each function. User gets to fill the space with what ever that is going to be returned and then at the function's ending that value will be returned as the result of the calling.
                                        For loop, while loop…
                                        You can use [ 10 , pr ] or [ #x < 10 , pr ], It's Arendelle's jobs to understand what kind of loop you mean.