Replies: 2 comments 1 reply
-
|
@avinxshKD There is no prioritization. If you like to implement something during the application period, you are free to start from whatever that is easy for you. For the GSoC coding period itself, crucial features should be implemented. You could check with the C++ and Verilog implementations as a start. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks for the guidance, @pradeeban. That makes sense, hve started digging into the C++ and Verilog source. I'll share a link to my progress once I have a working demo ready for feedback....Thanks |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @mvk2, @rahuljagwani1012, and @pradeeban,
I’m Avinash, a developer with experience building end-to-end systems. I’ve been following the project closely and caught the recent discussion in #172 regarding the Julia implementation. It’s great to see the communication layer and file-watching logic already taking shape.
I’m very interested in contributing to the 350-hour Julia reference implementation for GSoC 2026. Given my background in building end-to-end systems, I want to help expand the core logic beyond just the communication layer.
I’ve been looking through the Python source, specifically how the GraphML workflows are handled in concore-lite. I’m interested in exploring how to port these to native Julia structures using multiple dispatch to ensure we get the performance benefits Julia is known for.
Are there specific modules or existing Python examples you’d prioritize for the Julia implementation? I'd love to start prototyping a "Julia-fied" version of the control logic or the parser to share with the community soon.
Looking forward to hearing your thoughts
Best regards,
Avinash
Beta Was this translation helpful? Give feedback.
All reactions