made a new wiki type page where people can find more about the type of comet they want to know about and also learned how to handle multiple pages at once in a vercel site
made a new wiki type page where people can find more about the type of comet they want to know about and also learned how to handle multiple pages at once in a vercel site
when i started Where the Meteor at, the idea was pretty straightforward : ask for someone’s location , account for the condition in their sky ,and tell them how many meteors they could realistically see instead of just throwing the theoretical ZHR at them.
The first couple of sessions were mostly about figuring out the logic and getting the Flask backend to work . I was learning as i went , breaking things , debugging them , and occasionally wondering why did i even pick this project because of the back and forth
but i finally gave the UI the project Deserved.
The redesign
I took a lot of inspiration from Teenage Engineering’s Industrial design language . I wanted the interface to feel like a scientific instrument rather than another generic AI dashboard as it looked before .
SO i went with a warm off-white background ,near-black text and a sharp orange accent .Syne handles the big heading while jetbrains mono gives the measurement and data a technical , instrument-panel feel.
I also re-worked the layout around how someone would actually use the tool . Location search and sky condition sit in their sidebar , while the meteor shower gets the main stage . The estimated meteor count is the first thing you notice and the more detailed information stays tucked inside expandable rows until you need it .
those rows contain things like radiant altitude , viewing direction air quality and the best viewing window .I also kept the hourly chart so you can get a better idea of how the condition change instead of relying on one number .
The goal was to make the interface feel engineered not just decorated. No unnecessary elements ; just a strong grid , deliberate typography , and i especially love the orange accents
Conclusion
This project has been a bit out of my comfort zone i started out learning and experimenting with Flask , and ended up with a project that combines astronomy environmental data , calculation and interface design.
The direction the UI took was amazing .It finally feels like a coherent product instead of a collection of features i managed to get working.
The next step is to finish the final check , update the documentation , and ship it
If you spot a bug or have an idea for improving the prediction ; feel free to open an issue or submit a PR. I’d genuinely love to see what people do with it
After setting up the initial project the next step was to figure out how to approach the firmware without making the first prototype unnecessarily complicated
Ai assistance was used as a reference for choosing a firmware folder structure and planning a simple architecture . The idea was to keep the code separated into modules so that individual component could be changed later without having to rewrite the entire system.
the initial structure uses PlatformIO with the Arduino framework for the ESP32 . The Sensor-related files were placed in a separate sensor folder , with for climate control , power management and controller logic as the project develops.
The First piece of firmware work was the sensor abstraction . A common Sensor interface and a SensorData structure were created , along with two sensor implementation : FakeSensor and Sht31Sensor
The fake senor returns fixed temperature and humidity values which makes it possible to develop the basic firmware without having the physical sensor connected . The Sh31 implementation is intended to read actual temperature and humidity measurement using Adafruit SH31 library.
The initial main.cpp was written to select a sensor, initialize it and print its reading through the serial monitor . This gives the project a starting point for checking the senor interface before moving on to climate control.
There is still issue to resolve with Sh31 Library being recognized by VS Code .The Physical sensor has not yet been tested with the ESP32(due to lack of funding) ,so real reading have not been verified. Fan Control , humidification and automatic humidity regulation are also pending .
For now the focus is on getting the sensor layer working reliably before adding more features. Once the ESP32 can read actual environmental data , the next step will be to start building the control logic
today i laid the foundation of Myco OS , an open source ecosystem planned for low cost mushroom cultivation. The objective is to build a system that is inexpensive , reliable , scalable, and fully repairable using commodity hardware
I’m trying to integrate my engineering skills will my passion of farming to make a functional project which may really make an impact on my life and other activity
These Priciple will guide every hardware and software decision through development
The GitHub Repo was initialized with the Mit License, CERN open hardware License . The repo structure was planned for firmware hardware cad dashboard doc
the first prototype will focus on the core environmental controller:
Features for next release
QR Tracking, Multi Chamber networking and ‘’’.myco’’’ will be planned and worked upon after the first release
Existing cultivation system are often expensive , proprietary, or difficult to repair .MycoOS Aims to Provide reproducibly open hardware Alternative that anyone can build modify and maintain
made cad for base and arm took me 4 hors as i was learning cad itself (solid works) the frustration came when i forgot to time-lapse and when i did it crashed and didn’t save the video also wrote documentation on assembly of the robot as well as wiring also made a bom.csv for the project finally and updated the readme a little bit improved the formatting and revised all the previously written readme documentation
next will be working on servo mount and brackets in cad and assembly and will learn more of cad
Story: it was my first time using cad (solid works) so i wasn’t able to sketch and and when i did it was off center so i did try and also as i was new i didn’t knew the difference bw parts and assemble so i tried making the whole robot in one go which was devastating and i has to start a google times
man i love vibe coding was just learning here and there how to vibe code trying get along it and seeing ,did a bit of ammature practice
first devlog
this is going to be about how this project is gonna be traced
firstly i would scrap the comets and hardcode them into my dataset
then i would make a engine that would calculate showers and predict them I’m using flask as I’m proficient in python to connect it to a html and then i would calculate how much meteor is visible ,viable angle using parameter like aqi sky clarity and latitude longitude i would later add dynamic location picker using map (in v0 u need to log latitude and longitude manually)
finnaly done with the how the machine(lamp) reacts to touch and used ai to finally ease of some work and stream line workflow the ai helped code a wonder full website
motion of servo has been completed, mood and reaction of the lamp is set (are there any free simulation app i can try to test the movement).did the initial commit and next will be working on touch sensing to give a pet vibe to the lamp so it can react to user touch
it has 8 modes hardcoded
neutral
happy
sad
alert
sleep
excited
look left
look right
which help it give the vibe and im trying to follow Disney animation rule and kind of fine tune the animation speed so it matches the luxo vibe that im going for
added active boards logic to the game
for eg if a person clicks on the one particular block of the small ttt the next player has to select the any available box of the box from the bigger ttt also if that box is filled /occupied then payer can choose any block which is available
next up gonna improve the ui and the ux trying to highlight the box would love recommendation for css
making a web version of super tic tac toe and making sure basic io work ,logic still not