Hi Matthew,

Thanks for your interest in Chapel. I think a performance-oriented application 
would make an excellent GSoC project. We don't have any GSoC mentors that are 
particularly experienced with cryptocurrency trading, but we may be able to 
work something out, e.g. having the mentor provide primarily Chapel expertise 
rather than application domain knowledge. 

Some things to consider for your project: If we are building an application 
meant to demonstrate Chapel's performance, what existing applications will we 
be able to benchmark against? Would the building blocks of this application be 
generally useful enough to implement as part of a library? Is there an 
equivalent library out there in other languages to compare against in both 
design and performance aspects?

I am not personally familiar with any Java+Chapel projects out there today, but 
it should be possible by utilizing both Java and Chapel's C interoperability 
features, e.g. calling Java from Chapel using JNI. If you are convinced this 
interoperability is necessary, demonstrating this could be a good first step 
for your project.

Best,
Ben


On 3/5/17, 9:03 PM, "Matthew Sedam" <[email protected]> wrote:

    Hello everyone!
    
    
    My name is Matthew Sedam, and I am interested in Chapel for Google Summer 
of Code 2017. I am particularly interested in writing an application in Chapel 
to show off its performance. For the past month or so, I have been writing an 
open source
     cryptocurrency trading bot in Java. Details can be found here: 
https://github.com/matthewsedam/cryptotrade. I was wondering if this could 
qualify for GSoC. The code that exists right now is very primitive.
     However, I have a working algorithm (tested manually) and a detailed 
design. Please see the GitHub issue referenced on the Readme for the initial 
0.1.0 release design. I have just discovered Chapel, and I believe it could 
revolutionize my open source project.
     I was thinking of using a combination of Chapel and Java. Can someone tell 
me if this would be considered or even favored over porting an existing 
application to use Chapel? The main goal would be to release 0.1.0, the first 
stable version for public use.
     See the issue referenced in the Readme for 0.1.0 details. A stretch goal 
would be implementing arbitrage between multiple exchanges, which would require 
heavy Chapel use. Please see the related issue.
    
    
    I am very passionate about this project. This has been an idea of mine for 
many years, and I believe I can use Chapel to enhance the performance of my 
application immensely.
    
    
    Please note that most of the code has not been written. I have spent my 
time planning (see open issues) as well as setting up a proper development 
system and environment.
    
    
    Thank you!
    
    
    Matthew Sedam
    
    




------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers

Reply via email to