Introduction & Interest in Julia Reference Implementation (GSoC 2026)

[avinxshKD]

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

[pradeeban]

@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.

[avinxshKD]

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

[pradeeban]

Sounds good!

[avinxshKD]

Hi @pradeeban,

Following up, I've pushed my initial prototype here:
https://github.com/avinxshKD/concore-jl

Current implementation includes:

GraphML workflow parsing — load_graph() extracts node definitions with PID parameters
PID controller execution — Type-stable execute_step() with state management
File-based communication — read_input(), write_output(), unchanged() mirroring concore's IPC pattern
FileWatching integration — watch_and_execute() for reactive triggers

I've started reviewing the C++ and Verilog implementations as you suggested. Should I prioritize aligning with the C++ protocol handling, or focus on expanding the GraphML workflow engine first?

Happy to get feedback on the approach, thanks

Screenshots demonstrating the prototype in action. So far, hve invested approximately 20–25 hours into this initial prototype. And I’m excited to continue contributing further.

[pradeeban]

awesome!