Bio x AI Hackathon
  • Welcome to the Bio x AI Hackathon
  • Getting Started
    • Quickstart
    • Important Links
  • Developers
    • BioAgents
    • CoreAgents
    • Eliza Agent Framework
    • Knowledge Graphs
    • .cursorrules
    • Starter-repos
    • Plugin Guide
  • Vision and Mission
    • Bio x AI Hackathon
    • The Problems in Science
    • TechBio
    • Guidance from the Judges
      • Important Datasets and Code Repositories
      • Reading List
      • Common Mistakes for Developers new to Academia
    • Hackathon Ideas
      • Full Projects
        • The Complexity Slider - Finding Hypotheses at the Limits of Human Knowledge
        • [Hard Mode] Metadata Generation on datasets with No Manuscript or Code Associated
        • Inverse Reproducibility - Given Manuscript and Data, Make the Code
        • Atlas of Research Methods Formatted for Agentic Reuse
        • Utilizing Knowledge Graphs for the Detection of Potential Null Results
        • Creating an Iterative Publication Stack by Linking Together Existing Tooling
        • Longevity Atlas: Building a Decentralized Knowledge Network with Agentic Research Hypothesis Engine
        • CoreAgent Track - Opportunities to work with BioDAOs
        • SpineDAO Chronos Project Spec
      • Individual Plugins
        • Plug-ins for every piece of research tooling known to humankind
        • Reproducibility Assistant - Code Cleaning, Dockerization, etc
        • Finding and Differentiating Cardinal vs Supporting Assertions
        • [Easier Mode] Metadata Generation on Datasets Given the Manuscript and Code Repository
        • Sentiment Analysis on Existing Citations, Dissenting vs Confirming
        • Agentic Metadata Template Creation for Standard Lab Equipment
  • Ops
    • Calendar
      • Key Dates
      • Office Hours
    • Judges and Mentors
      • Communicating to Judges and Mentors
      • BioAgent Judging Panel
      • CoreAgent Judging Panel
      • Mentors
    • Prize Tracks
    • Hackathon Rules
    • Kickoff Speakers
    • FAQ
Powered by GitBook
On this page
  1. Ops

FAQ

PreviousKickoff Speakers

Last updated 1 month ago

Who can participate?

Everyone is welcome! Whether you're a seasoned developer, a budding designer, a researcher, or just someone with a passion for innovation, we encourage you to join.

What skills are needed?

We're looking for a diverse range of skills, including programming, data science, research, and communication. Don't worry if you're not an expert in everything – hackathons are about learning and collaboration.

Can I work in a team?

Yes, absolutely! We encourage team collaboration. Teams are a great way to combine different skills and build more ambitious projects. We recommend teams of [insert recommended team size].

Do I need to have a project idea beforehand?

No, you don't need to have a fully formed idea before the hackathon. We'll have brainstorming sessions and project pitches at the beginning of the event. Also check out Hackathon Ideas

What resources will be provided?

Check out Starter-repos Guidance from the Judges. Also, Prime Intellect is happy to give $100 to each developer in the event, just ask for compute credits on the !

What kind of support will be available?

Mentors with expertise in various fields will be available to provide guidance and support throughout the hackathon. We'll also have technical support staff to assist with any technical issues.

Can I continue working on my project after the hackathon?

Yes, you're welcome to continue working on your project after the hackathon. We encourage you to share your work with the community.

Where can I ask more questions?

Join the ! There's a "Hackathon Chat" Channel

How do I form a team?

Can I create multiple plugins in a single repository?

While you can use a monorepo structure for development, we recommend splitting your plugins into separate repositories for better modularity and reusability. This allows other in the future to easily reuse your plugins and better complies with the Eliza Guidelines. If you do use a monorepo structure, make sure each plugin follows the ElizaOS plugin structure and can be published independently at the end of the event. The end goal is to have your plugins published to ElizaOS in a way that makes them reusable and modular.

Join the ! There's a "Join a Team" Channel

Discord
Discord
Discord