AstroData AI

AstroData AI is a self-reported tool that allows users to upload telescope observation data and receive structured scientific analysis through a bilingual interface. The system performs deterministic scientific calculations using Python-based tools like Astropy and Photutils, with GPT-5.6 used only for generating explanations of results rather than performing calculations. The author states the goal is to make astronomical data analysis more accessible without sacrificing scientific rigor.

The project appears to be a single-person development effort built for an OpenAI hackathon. No revenue, customers or traction data are evidenced. The most important open question is whether the described scientific pipeline can reliably process real-world telescope data and produce reproducible results at scale — a claim not substantiated by evidence.

The description states that AstroData AI allows users to upload telescope observations and follow complete analysis through a visual, bilingual interface. For time-series and light-curve data, it performs:

• Schema and data-quality validation
• Missing-value and uncertainty checks
• Robust anomaly detection
• Lomb–Scargle periodicity analysis
• Box Least Squares transit detection
• Harmonic comparison and signal classification
• Phase-folded light-curve visualization
• Transit depth, duration, signal-to-noise, and event estimation
• Reproducible reports with file hashes and pipeline information

For FITS observations, it supports:

• Bias, dark, and flat calibration
• HDU selection
• Header and WCS inspection
• Two-dimensional star detection with Photutils
• Aperture photometry
• Uncertainty propagation
• Temporal and barycentric corrections
• Comparison-star analysis
• Astronomical catalog cross-matching
• Independent-observation validation guidance

The system uses a React and TypeScript frontend with a Python and FastAPI backend. Scientific calculations use Astropy, Photutils, NumPy, and SciPy. GPT-5.6 is used only for explanations of results, not for calculations.

The author states that AstroData AI was created to make astronomical data analysis more accessible without sacrificing scientific responsibility. The goal is not to let generative AI invent discoveries but to combine reproducible astronomical calculations with clear explanations.

The positioning has evolved from a hackathon project into a tool that claims to help students, citizen astronomers, and researchers perform initial quality-controlled reviews of observations. It explicitly states it does not claim to discover planets automatically, but rather identifies scientifically interesting candidates and explains why they deserve attention.

The description states that AstroData AI is intended for:

• Students learning astronomical data analysis
• Citizen astronomers inspecting observations
• Researchers performing initial quality-controlled reviews before using specialized workflows

No specific customer segments or personas are detailed. The author does not provide evidence of any existing user base or target market definition beyond these general categories.

Not evidenced. The description provides no information about pricing, monetization strategy, or business model.

The system is built with:

• Frontend: React and TypeScript
• Backend: Python and FastAPI
• Scientific libraries: Astropy, Photutils, NumPy, SciPy
• AI tools: GPT-5.6, Codex

Architecture separates deterministic scientific pipeline from GPT explanation layer. The author states that GPT-5.6 does not calculate anomalies or periods and does not receive original uploaded files. The system is designed to continue working even if the AI service is unavailable.

Not evidenced. No revenue, customer adoption, usage metrics, or product maturity data are provided beyond the author's own account of a hackathon submission.

Not evidenced. No information about existing competitors or market positioning is provided in the description.

• Single-person development effort (1 team member)
• No evidence of revenue, customers or traction
• Self-reported scientific pipeline without validation data
• GPT-5.6 used for explanations but not calculations, which may limit AI's utility
• Hackathon project context suggests early-stage development
• No information about scalability or production deployment

1. What specific telescope datasets have been tested and validated?
2. How is uncertainty propagation handled in the scientific pipeline?
3. What validation methods exist for the GPT explanations?
4. Are there any known limitations or edge cases in the current implementation?
5. What are the plans for scaling beyond the current single-developer scope?
6. How does the system handle different telescope data formats and calibration requirements?