top of page

FAQ

GENERAL INFORMATION​

 

What is Iris Hacks? 

Iris Hacks is a 3-day online hackathon targeting middle school students. Participants will work on projects in AI across three tracks: Healthcare, Safety, and Education. 

​

Who can participate in Iris Hacks? 

Students from grades 6-8 are eligible to participate. 

 

What are the dates and duration of the next hackathon? 

The hackathon is a 3-day event, stretching from Friday, January 10th to Sunday, January 12th.

 

Is there a fee to participate? 

No, participation in Iris Hacks is free of charge. 

​​

​

REGISTRATION

​

How do I register for the hackathon? 

You can register through our Google Form, linked on our home page. Complete the registration form with your details before the start of the hackathon. 

 

Can I participate individually or do I need a team? 

You can participate individually or in teams of 2-4 members. Teams can be formed before the event or during the kickoff session. 

​

​​​

EVENT STRUCTURE

​

What is the structure of the hackathon? 

The hackathon includes workshops, project development, and mentorship over 3 days. Participants will attend sessions on OpenAI, Python programming, and web development, and work on projects within their chosen track. 

 

What tracks are available for projects? 

There are three tracks: AI in Healthcare, AI in Safety, and AI in Education. 

 

​​​

RESOURCES AND TOOLS

 

What tools and platforms will be used? 

We will use Flask for web development, Teachable Machine, and TensorFlow, and DALL·E, ChatGPT, Whisper, GPT-01, API Keys for AI models. We will use Discord for communication and Devpost for project submission. 

 

Will there be any workshops or mentoring sessions? 

Yes, there will be multiple workshops on OpenAI, Python, Flask, and deploying applications, as well as ongoing mentor support throughout the hackathon. 

 

​​​

PROJECT SUBMISSION

 

How do we submit our projects? 

Projects must be submitted on Devpost by the specified deadline. Submissions should include a project description, screenshots or demo video, and a link to the Glitch-deployed application. 

 

Can we use pre-existing code? 

All project work must be done during the hackathon timeframe. However, you can use open-source libraries and tools. 

 

​​​

JUDGING AND PRIZES

 

How will projects be judged? 

Projects will be judged based on creativity, functionality, impact, and presentation. 

 

What prizes are available? 

Prizes will be awarded to top team overall as well as best safety solution, best education tool, best healthcare innovation, and workshop warrior. Details can be found on our Prizes page.

 

​​​

PARTICIPATION GUIDELINES

 

What are the guidelines for team formation? 

Teams can consist of 2-4 members and can be formed before the event or during the kickoff session. 

 

What is the code of conduct? 

Participants must adhere to a code of conduct that promotes respect, inclusivity, and collaboration. Harassment, discrimination, and inappropriate behavior will not be tolerated. 

 

How do we communicate with the team and organizers? 

Communication will be facilitated through Discord. The invitation link can be found on our home page.

 

​

​TECHNICAL SUPPORT

 

What if I have technical issues during the hackathon? 

Technical support will be available throughout the event. You can reach out for help via the designated support channels on Discord. 

 

How do I report unacceptable behavior or other issues? 

Report any unacceptable behavior or issues to the organizers at gill.s.jaiveer@gmail.com or sidarutla@gmail.com

 

​

​POST-HACKATHON

​

What happens after the hackathon?

After the hackathon, there will be a feedback session. Participants can provide feedback and stay connected with the community for future events and opportunities. 

 

How can I stay involved in future events?

Stay connected through our community platforms and look out for announcements regarding future hackathons and STEM events.

PHONE

(669) 246-0126

(408) 838-9157

CONNECT

  • Discord
  • Instagram

EMAIL

bottom of page