Queries regarding submission of coding challenge for LFX Spring term Mentorship 2026 #1332
codeEvolveZenith345
started this conversation in
General
Replies: 1 comment
-
|
Others are providing github repositories, but the output of the LLM is a
result, and any report that is produced from the github code will be the
starting point.
Personally, I don't see why .txt or .md wouldn't be acceptable; content is
more important than format.
…On Fri, Jan 16, 2026 at 3:23 AM Lakshya Saxena ***@***.***> wrote:
Greetings to the RISC-V community,
My name is Lakshya Saxena, a Computer Science undergraduate at Indian
Institute of Information Technology (IIIT-A). My technical skills are
Artificial Intelligence, Software Development and Technical Writing.
About two weeks ago I came across the project AI-assisted extraction of
architectural parameters from RISC-V specifications, Since then I have
been working on the coding challenge that was mentioned there. I have
completed and reviewed it.
I am highly motivated and Interested to contribute to the community under
the mentorship of experienced mentors (Ajit Dingankar ***@***.***
<https://github.com/adingank-qualcomm>) and Allen Baum ***@***.***
<https://github.com/allenjbaum>) ) to contribute to the RISC-V ecosystem.
Automating parameter extraction from RISC-V specs will accelerate hardware
design and verification by providing developers with accurate, structured
architectural data instead of manual specification parsing. This makes
RISC-V more accessible to newcomers and enables better tooling for the
growing open-source hardware community.
My Main query is on the format of Coding challenge submission it allows only `.doc, .docx or .pdf`
while my submission is a git repository to keep it structured.
Please clarify it to me. I suppose a brief README in the submission file with Repository URL is best format for submission.
Best Regards,
Lakshya Saxena.
—
Reply to this email directly, view it on GitHub
<#1332>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHPXVJUUF6KSDVRCHKQ3Z2D4HDC4PAVCNFSM6AAAAACR44QICCVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZGM2TENZQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings to the RISC-V community,
My name is Lakshya Saxena, a Computer Science undergraduate at Indian Institute of Information Technology (IIIT-A). My technical skills are Artificial Intelligence, Software Development and Technical Writing.
About two weeks ago I came across the project
AI-assisted extraction of architectural parameters from RISC-V specifications, Since then I have been working on the coding challenge that was mentioned there. I have completed and reviewed it.I am highly motivated and Interested to contribute to the community under the mentorship of experienced mentors (Ajit Dingankar (@adingank-qualcomm) and Allen Baum (@allenjbaum) ) to contribute to the RISC-V ecosystem.
Automating parameter extraction from RISC-V specs will accelerate hardware design and verification by providing developers with accurate, structured architectural data instead of manual specification parsing. This makes RISC-V more accessible to newcomers and enables better tooling for the growing open-source hardware community.
Best Regards,
Lakshya Saxena.
Beta Was this translation helpful? Give feedback.
All reactions