|
3351
|
My first slack bot! by @kathryn21 | Stardance
|
kathryn21
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @kathryn21 | Stardan Title: My first slack bot! by @kathryn21 | Stardance...
|
1792766982.5645115
|
1793371782.5645115
|
|
3352
|
My first slack bot! by @Niya | Stardance
|
Niya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Niya | Stardance
|
1792806749.4030976
|
1793411549.4030976
|
|
3353
|
My awesome macropad! by @zahra | Stardance
|
zahra
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zahra | Stardance
|
1792723741.0933719
|
1793328541.0933719
|
|
3354
|
Untitled by @shaurwadhawan | Stardance
|
shaurwadhawan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @shaurwadhawan | Stardance
|
1792634110.708118
|
1793238910.708118
|
|
3355
|
Flight Engine by @chrisyue321 | Stardance
|
chrisyue321
|
0
|
18.02
|
0
|
[]
|
[{"post_id": 20865, "ts": "202 [{"post_id": 20865, "ts": "2026-07-02T16:14:03Z", "hours": 2.3144, "text": "I built a basic propulsion module but I haven’t gotten around to really implementing it yet I just put in some code to add it into some of the modules but I have not tested it. I’ve mainly been focusing on debugging the dynamics modules as I ran some tests with verbose logging and it appears that there is either something wrong with the calculation of the aerodynamic coefficients or there is something fundamentally wrong with the equations of motion. Here is a screenshot of the erratic behavior (pitch oscillating wildly, roll switching oddly between 0 and 180 degrees, velocity oscillating, altitude behaving weirdly, and all manner of weird stuff."}, {"post_id": 20446, "ts": "2026-07-02T01:21:12Z", "hours": 1.4897, "text": "After starting a new project, I finished implementing V2 of the core data structures, 6DOF equations of motion, and aerodynamic model. I built some unit tests to make sure everything is working properly. Below is an attached screenshot of the test working (I think I may have forgotten to push the testing file to GitHub and only pushed the test functions instead of the file w/ the code that logs the runs)"}, {"post_id": 19550, "ts": "2026-06-30T21:31:17Z", "hours": 14.2117, "text": "I have forgotten to write devlogs on Stardance, I started the project but completely forgot to link my Hackatime. I have been working on the engine on and off for around 3 weeks now. The first version was intended to have a aerodynamic model class with all of the parameters such as coefficient of lift (and its derivatives with respect to variables like angle of attack) among others. However, the dynamics and math appeared to be extremely inconsistent and the simulation as a whole had poor stability. Tweaking the parameters (wingspan, chord, etc) of the wing just slightly caused large fluctuations. I was only able to achieve the stability demonstrated in the screenshots below with an essentially perfectly tuned NACA airfoil. It still does dive a bit more than I was expecting (aka what ChatGPT and Gemini were both expecting since I do not have a lot of extensive experience in aeronautics). Due to these unresolved issues I have started a new version of the engine which I plan to add a bunch of unit tests to to ensure every module is working as intended, I accidentally overwrote GitHub commit history in the process rip :(."}]...
|
Title: Flight Engine by @chrisyue321 | Stardance
Title: Flight Engine by @chrisyue321 | Stardance
Devlogs:
I have forgotten to write devlogs on Stardance, I started the project but completely forgot to link my Hackatime. I have been working on the engine on and off for around 3 weeks now. The first version was intended to have a aerodynamic model class with all of the parameters such as coefficient of lift (and its derivatives with respect to variables like angle of attack) among others. However, the dynamics and math appeared to be extremely inconsistent and the simulation as a whole had poor stability. Tweaking the parameters (wingspan, chord, etc) of the wing just slightly caused large fluctuations. I was only able to achieve the stability demonstrated in the screenshots below with an essentially perfectly tuned NACA airfoil. It still does dive a bit more than I was expecting (aka what ChatGPT and Gemini were both expecting since I do not have a lot of extensive experience in aeronautics). Due to these unresolved issues I have started a new version of the engine which I plan to add a bunch of unit tests to to ensure every module is working as intended, I accidentally overwrote GitHub commit history in the process rip :(.
After starting a new project, I finished implementing V2 of the core data structures, 6DOF equations of motion, and aerodynamic model. I built some unit tests to make sure everything is working properly. Below is an attached screenshot of the test working (I think I may have forgotten to push the testing file to GitHub and only pushed the test functions instead of the file w/ the code that logs the runs)
I built a basic propulsion module but I haven’t gotten around to really implementing it yet I just put in some code to add it into some of the modules but I have not tested it. I’ve mainly been focusing on debugging the dynamics modules as I ran some tests with verbose logging and it appears that there is either something wrong with the calculation of the aerodynamic coefficients or there is something fundamentally wrong with the equations of motion. Here is a screenshot of the erratic behavior (pitch oscillating wildly, roll switching oddly between 0 and 180 degrees, velocity oscillating, altitude behaving weirdly, and all manner of weird stuff....
|
1792695164.661953
|
1793299964.661953
|
|
3356
|
My awesome macropad! by @Cheese | Stardance
|
Cheese
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Cheese | Stardance
|
1792741769.1867337
|
1793346569.1867337
|
|
3357
|
Tactora by @ramsuhrut_10 | Stardance
|
ramsuhrut_10
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Tactora by @ramsuhrut_10 | Stardance
|
1792504115.5732045
|
1793108915.5732045
|
|
3358
|
Asteroid Tracker by @ppdeshmukh80 | Stardance
|
ppdeshmukh80
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Asteroid Tracker by @ppdeshmukh80 | Stardan Title: Asteroid Tracker by @ppdeshmukh80 | Stardance...
|
1792695007.6646426
|
1793299807.6646426
|
|
3359
|
My awesome macropad! by @thespidaeCorsair | Starda My awesome macropad! by @thespidaeCorsair | Stardance...
|
thespidaeCorsair
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @thespidaeCorsair | Title: My awesome macropad! by @thespidaeCorsair | Stardance...
|
1792522242.1534953
|
1793127042.1534953
|
|
3360
|
parting the keys by @vin0 | Stardance
|
vin0
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: parting the keys by @vin0 | Stardance
|
1792568854.8198433
|
1793173654.8198433
|
|
3361
|
Platformer game by @jayvenandrews13 | Stardance
|
jayvenandrews13
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Platformer game by @jayvenandrews13 | Stard Title: Platformer game by @jayvenandrews13 | Stardance...
|
1792601568.1459067
|
1793206368.1459067
|
|
3362
|
My awesome macropad! by @svatsaa | Stardance
|
svatsaa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @svatsaa | Stardanc Title: My awesome macropad! by @svatsaa | Stardance...
|
1792565409.229607
|
1793170209.229607
|
|
3363
|
Untitled project by @aquawarrior | Stardance
|
aquawarrior
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @aquawarrior | Stardanc Title: Untitled project by @aquawarrior | Stardance...
|
1792651675.1319456
|
1793256475.1319456
|
|
3364
|
My awesome macropad! by @bxoygs | Stardance
|
bxoygs
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @bxoygs | Stardance
|
1792795996.078127
|
1793400796.078127
|
|
3365
|
My awesome macropad! by @Chalie | Stardance
|
Chalie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Chalie | Stardance
|
1792601648.1476874
|
1793206448.1476874
|
|
3366
|
Starfish by @sai_was_taken | Stardance
|
sai_was_taken
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Starfish by @sai_was_taken | Stardance
|
1792478925.8920395
|
1793083725.8920395
|
|
3367
|
My awesome macropad! by @Akshita | Stardance
|
Akshita
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Akshita | Stardanc Title: My awesome macropad! by @Akshita | Stardance...
|
1792526091.7681525
|
1793130891.7681525
|
|
3368
|
My first slack bot! by @awjg | Stardance
|
awjg
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @awjg | Stardance
|
1792734722.1880581
|
1793339522.1880581
|
|
3369
|
x by @abby_g009 | Stardance
|
abby_g009
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: x by @abby_g009 | Stardance
|
1792666497.5991476
|
1793271297.5991476
|
|
3370
|
My first slack bot! by @shaurwadhawan | Stardance
|
shaurwadhawan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @shaurwadhawan | Sta Title: My first slack bot! by @shaurwadhawan | Stardance...
|
1792777908.8424737
|
1793382708.8424737
|
|
3371
|
My awesome macropad! by @vineshdevunoori741 | Star My awesome macropad! by @vineshdevunoori741 | Stardance...
|
vineshdevunoori741
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @vineshdevunoori741 Title: My awesome macropad! by @vineshdevunoori741 | Stardance...
|
1792515218.0232208
|
1793120018.0232208
|
|
3372
|
Are we cooked? by @lawrencedoe08 | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Are we cooked? by @lawrencedoe08 | Stardanc Title: Are we cooked? by @lawrencedoe08 | Stardance...
|
1792529677.2283256
|
1793134477.2283256
|
|
3373
|
VTOL Fixed Wing by @ibandla16 | Stardance
|
ibandla16
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: VTOL Fixed Wing by @ibandla16 | Stardance
|
1792640912.6745434
|
1793245712.6745434
|
|
3374
|
TAR CNC Machine by @Hridum | Stardance
|
Hridum
|
0
|
14.1
|
0
|
[]
|
[{"post_id": 27315, "ts": "202 [{"post_id": 27315, "ts": "2026-07-12T19:51:12Z", "hours": 1.1006, "text": "Quick Fixes Updated X axis connectors to be simpler and more intuitive Readjusted spacing for Y and Z axis because of changes from X Axis Also readjusted spacing for Bearing Blocks & Linear Rails on X axis due to change Reorganized structure or machine to Upper and Lower Axes"}, {"post_id": 24528, "ts": "2026-07-08T04:23:26Z", "hours": 5.325, "text": "Added more support/connection brackets Basically just added more brackets for structure and support. While designing brackets for connecting the X and Y axis, I at first had conjured up a complex, round-about bracket, but then after I finished the design, I realized all I had to do was make some aluminum extrusion and little longer and design a MUCH simpler bracket. So that was like an hour wasted. Also adjusted tool head position even more to move it closer to the center of the cutting plate"}, {"post_id": 20246, "ts": "2026-07-01T19:52:06Z", "hours": 2.4847, "text": "3D Printed Supports Added many 3D printed support brackets/connectors to make sure CNC machine is structurally sound, specifically X-axis connectors and stepper motor supports Edited assembly by moving back tool head so that’s its closer to the center of the cutting plate"}, {"post_id": 6040, "ts": "2026-06-10T04:42:32Z", "hours": 3.9881, "text": "Basic Draft complete Completed basic drafts of the X, Y, and Z axis for the CNC machine. X and Y axis were already basically done, but now Z axis includes clamp for the Makita Router. The CAD file was huge and slowed down my computer, so I split the 3 axis into 3 different file, which heavily improved performance and decreased time just sitting there waiting for things to load. Also I made a few mistakes and everything was at random angles which messed up some measurements, but I fixed those, which also took a while, since I had to re-assemble everything and make sure the tiny misalignments didn’t appear."}, {"post_id": 998, "ts": "2026-06-02T19:37:21Z", "hours": 1.1975, "text": "Designed and added brackets to bottom structure for support. Also replaced linear rail supports from 2040 Extrusion to 2020 Extrusion to save materials and space. Assembly has gotten pretty big, so program runs slow and sometimes freezes when trying to save. When I was changing out the extrusions, I accidentally moved the linear rails out of place and had to align them back into their original positions, which took some finessing."}]...
|
Title: TAR CNC Machine by @Hridum | Stardance
Dev Title: TAR CNC Machine by @Hridum | Stardance
Devlogs:
Designed and added brackets to bottom structure for support. Also replaced linear rail supports from 2040 Extrusion to 2020 Extrusion to save materials and space. Assembly has gotten pretty big, so program runs slow and sometimes freezes when trying to save. When I was changing out the extrusions, I accidentally moved the linear rails out of place and had to align them back into their original positions, which took some finessing.
Basic Draft complete Completed basic drafts of the X, Y, and Z axis for the CNC machine. X and Y axis were already basically done, but now Z axis includes clamp for the Makita Router. The CAD file was huge and slowed down my computer, so I split the 3 axis into 3 different file, which heavily improved performance and decreased time just sitting there waiting for things to load. Also I made a few mistakes and everything was at random angles which messed up some measurements, but I fixed those, which also took a while, since I had to re-assemble everything and make sure the tiny misalignments didn’t appear.
3D Printed Supports Added many 3D printed support brackets/connectors to make sure CNC machine is structurally sound, specifically X-axis connectors and stepper motor supports Edited assembly by moving back tool head so that’s its closer to the center of the cutting plate
Added more support/connection brackets Basically just added more brackets for structure and support. While designing brackets for connecting the X and Y axis, I at first had conjured up a complex, round-about bracket, but then after I finished the design, I realized all I had to do was make some aluminum extrusion and little longer and design a MUCH simpler bracket. So that was like an hour wasted. Also adjusted tool head position even more to move it closer to the center of the cutting plate
Quick Fixes Updated X axis connectors to be simpler and more intuitive Readjusted spacing for Y and Z axis because of changes from X Axis Also readjusted spacing for Bearing Blocks & Linear Rails on X axis due to change Reorganized structure or machine to Upper and Lower Axes...
|
1792500843.141138
|
1793105643.141138
|
|
3375
|
Godot Game by @levyz | Stardance
|
levyz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Godot Game by @levyz | Stardance
|
1792774115.671431
|
1793378915.671431
|
|
3376
|
My first slack bot! by @Akshita | Stardance
|
Akshita
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Akshita | Stardance
|
1792727424.3287108
|
1793332224.3287108
|
|
3377
|
My awesome macropad! by @stefq | Stardance
|
stefq
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stefq | Stardance
|
1792810145.480207
|
1793414945.480207
|
|
3378
|
My awesome macropad! by @shaurya_singh | Stardance
|
shaurya_singh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @shaurya_singh | St Title: My awesome macropad! by @shaurya_singh | Stardance...
|
1792640925.6453846
|
1793245725.6453846
|
|
3379
|
Catch the parcel by @srijayan | Stardance
|
srijayan
|
0
|
0.89
|
0
|
[]
|
[{"post_id": 9557, "ts": "2026 [{"post_id": 9557, "ts": "2026-06-15T22:40:58Z", "hours": 0.8922, "text": "Here’s what I’m working on: I’m building a game called “Catch the parcel” and I took inspiration from a game i used to play on my granny’s nokia when i was little (I don’t exactly know what it was called, but I will replicate the idea behind that game). Here’s how the game works: The setting is a blue background, with green ground, and there is a cart on the ground which can be moved in the x direction, there are parcels falling from the sky, at the beginning they are falling slow but as the time progresses, the rate of parcels falling down would increase. The goal of this game is to collect as many parcels, while making sure no more than 3 parcels fall on the ground. As of now, I just planned one difficulty level, after completing that I would build multiple speed levels, and then later leaderboards and stuff. That’s basically what I’ve figured out till now, I will start building the project now. I have attached a picture/sketch of how it will look like. (Please dont mind my drawing)"}]...
|
Title: Catch the parcel by @srijayan | Stardance
Title: Catch the parcel by @srijayan | Stardance
Devlogs:
Here’s what I’m working on: I’m building a game called “Catch the parcel” and I took inspiration from a game i used to play on my granny’s nokia when i was little (I don’t exactly know what it was called, but I will replicate the idea behind that game). Here’s how the game works: The setting is a blue background, with green ground, and there is a cart on the ground which can be moved in the x direction, there are parcels falling from the sky, at the beginning they are falling slow but as the time progresses, the rate of parcels falling down would increase. The goal of this game is to collect as many parcels, while making sure no more than 3 parcels fall on the ground. As of now, I just planned one difficulty level, after completing that I would build multiple speed levels, and then later leaderboards and stuff. That’s basically what I’ve figured out till now, I will start building the project now. I have attached a picture/sketch of how it will look like. (Please dont mind my drawing)...
|
1792529699.5005796
|
1793134499.5005796
|
|
3380
|
Untitled project by @Prajuna | Stardance
|
Prajuna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Prajuna | Stardance
|
1792810125.3163357
|
1793414925.3163357
|
|
3381
|
WonderWild by @fernandazam319 | Stardance
|
fernandazam319
|
0
|
0.8
|
0
|
[]
|
[{"post_id": 24263, "ts": "202 [{"post_id": 24263, "ts": "2026-07-07T18:30:34Z", "hours": 0.7981, "text": "i made the simple mechanics for my game and created the sprites. next step: add images to make it less plain"}]...
|
Title: WonderWild by @fernandazam319 | Stardance
Title: WonderWild by @fernandazam319 | Stardance
Devlogs:
i made the simple mechanics for my game and created the sprites. next step: add images to make it less plain...
|
1792774525.3603978
|
1793379325.3603978
|
|
3382
|
Advanced Weather Station by @CircuitCyborg | Stard Advanced Weather Station by @CircuitCyborg | Stardance...
|
CircuitCyborg
|
0
|
15.05
|
0
|
[]
|
[{"post_id": 68863, "ts": "202 [{"post_id": 68863, "ts": "2026-09-15T22:07:30Z", "hours": 9.1072, "text": "Well Well Well Seems a few months have passed since my last devlog. I guess it’s time to update the two people watching (HI). In the last few months I have completed it seems about 9 hours of tracked time. In this time I have: Reworked how the base station PCB is designed for better ergonomics, created V1 of the Base station case, the Power injector case V1, Wind Direction module V1, the outdoor temp and humidity sensor module V1. I also began working on attaching the sensor modules to the sensor tree. Up next create a base code to make this function, and redesign the base station case for the new form of the base station PCB. I will also begin to set up the shipping Repository for the project. Now that I’ve shown that I’m still alive, signing out for the next few days since the virtual event is almost over."}, {"post_id": 5171, "ts": "2026-06-08T21:05:11Z", "hours": 5.9472, "text": "PCB Design. Over the last week, I have created the schematic and footprint for the Base station, and the POE Injector. I then created a few different versions throughout the week for the sensor module. One version had the compute module separate from the sensors to be able to place the Pico for computation indoors, then just have an RJ45 cable between that and the sensors. The next version attached almost all sensors to the compute module to simplify, and used potentiometers for the wind speed and direction. The current version uses hall effect sensors for a rain gauge, wind speed, and wind direction. More updates soon."}]...
|
Title: Advanced Weather Station by @CircuitCyborg Title: Advanced Weather Station by @CircuitCyborg | Stardance
Devlogs:
PCB Design. Over the last week, I have created the schematic and footprint for the Base station, and the POE Injector. I then created a few different versions throughout the week for the sensor module. One version had the compute module separate from the sensors to be able to place the Pico for computation indoors, then just have an RJ45 cable between that and the sensors. The next version attached almost all sensors to the compute module to simplify, and used potentiometers for the wind speed and direction. The current version uses hall effect sensors for a rain gauge, wind speed, and wind direction. More updates soon.
Well Well Well Seems a few months have passed since my last devlog. I guess it’s time to update the two people watching (HI). In the last few months I have completed it seems about 9 hours of tracked time. In this time I have: Reworked how the base station PCB is designed for better ergonomics, created V1 of the Base station case, the Power injector case V1, Wind Direction module V1, the outdoor temp and humidity sensor module V1. I also began working on attaching the sensor modules to the sensor tree. Up next create a base code to make this function, and redesign the base station case for the new form of the base station PCB. I will also begin to set up the shipping Repository for the project. Now that I’ve shown that I’m still alive, signing out for the next few days since the virtual event is almost over....
|
1792547477.79242
|
1793152277.79242
|
|
3383
|
My awesome macropad! by @Sharad | Stardance
|
Sharad
|
0
|
0.9
|
0
|
[]
|
[{"post_id": 10458, "ts": "202 [{"post_id": 10458, "ts": "2026-06-17T05:57:41Z", "hours": 0.8992, "text": "I am working on my macropad. Still getting used to VS Code as it is my first time, so it is a bit of a learning curve!"}]...
|
Title: My awesome macropad! by @Sharad | Stardance Title: My awesome macropad! by @Sharad | Stardance
Devlogs:
I am working on my macropad. Still getting used to VS Code as it is my first time, so it is a bit of a learning curve!...
|
1792500852.5827794
|
1793105652.5827794
|
|
3384
|
My awesome macropad! by @marzbanc26 | Stardance
|
marzbanc26
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @marzbanc26 | Stard Title: My awesome macropad! by @marzbanc26 | Stardance...
|
1792572803.7156065
|
1793177603.7156065
|
|
3385
|
My HACKPAD!!! by @Quickmando | Stardance
|
Quickmando
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My HACKPAD!!! by @Quickmando | Stardance
|
1792705673.2242715
|
1793310473.2242715
|
|
3386
|
My first slack bot! by @samda0824 | Stardance
|
samda0824
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @samda0824 | Stardan Title: My first slack bot! by @samda0824 | Stardance...
|
1792525838.4883034
|
1793130638.4883034
|
|
3387
|
My awesome macropad! by @wannabeoiiiiii | Stardanc My awesome macropad! by @wannabeoiiiiii | Stardance...
|
wannabeoiiiiii
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @wannabeoiiiiii | S Title: My awesome macropad! by @wannabeoiiiiii | Stardance...
|
1792702129.043808
|
1793306929.043808
|
|
3388
|
My awesome macropad! by @BugHunter | Stardance
|
BugHunter
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @BugHunter | Starda Title: My awesome macropad! by @BugHunter | Stardance...
|
1792795775.3377469
|
1793400575.3377469
|
|
3389
|
Untitled project by @aquoria | Stardance
|
aquoria
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @aquoria | Stardance
|
1792561693.0800278
|
1793166493.0800278
|
|
3390
|
Rat clone by @youngzheimer | Stardance
|
youngzheimer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Rat clone by @youngzheimer | Stardance
|
1792712840.90355
|
1793317640.90355
|
|
3391
|
Run 999 miles to beat the game! by @PhantomPorter Run 999 miles to beat the game! by @PhantomPorter | Stardance...
|
PhantomPorter
|
0
|
2.39
|
0
|
[]
|
[{"post_id": 6629, "ts": "2026 [{"post_id": 6629, "ts": "2026-06-11T03:36:33Z", "hours": 1.2428, "text": "Worked on a stage hazard that requires you to slide under. This came with changing how collisions work at all, which I couldn’t finish for right now."}, {"post_id": 3236, "ts": "2026-06-06T02:00:39Z", "hours": 1.1447, "text": "Added a parry action for the player, with sounds and all."}]...
|
Title: Run 999 miles to beat the game! by @Phantom Title: Run 999 miles to beat the game! by @PhantomPorter | Stardance
Devlogs:
Added a parry action for the player, with sounds and all.
Worked on a stage hazard that requires you to slide under. This came with changing how collisions work at all, which I couldn’t finish for right now....
|
1792486330.4398613
|
1793091130.4398613
|
|
3392
|
My awesome macropad! by @priyamk | Stardance
|
priyamk
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @priyamk | Stardanc Title: My awesome macropad! by @priyamk | Stardance...
|
1792493408.1085527
|
1793098208.1085527
|
|
3393
|
My awesome macropad! by @TCNCRTR | Stardance
|
TCNCRTR
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @TCNCRTR | Stardanc Title: My awesome macropad! by @TCNCRTR | Stardance...
|
1792932763.732745
|
1793796763.732745
|
|
3394
|
My awesome macropad! by @justjason | Stardance
|
justjason
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @justjason | Starda Title: My awesome macropad! by @justjason | Stardance...
|
1792713183.7103245
|
1793317983.7103245
|
|
3395
|
MY SWEET PRINCE by @Vini | Stardance
|
Vini
|
1
|
12.0
|
64
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-23T03:59:47Z", "hours": 12.0, "multiplier": 5.52, "payout": 64, "blessing": "neutral", "text": "This project has taken a significant amount of my life I know it only says 12h but that’s just the amount of time i’ve been working on it since stardance started", "repo": "https://github.com/wildevi26250-tech/MY-SWEET-PRINCE", "demo": "https://celadon-semifreddo-4bbbb5.netlify.app/"}]...
|
[{"post_id": 8904, "ts": "2026 [{"post_id": 8904, "ts": "2026-06-14T20:20:33Z", "hours": 1.8322, "text": "Yesterday I made this settings menu work it has full screen volume controls and level saves. I also added some of the finishing touches to the last level. I once again ask for people to test my game and give me feedback thank you and good bye"}, {"post_id": 7912, "ts": "2026-06-13T06:05:23Z", "hours": 2.1731, "text": "I fixed alot of stuff and added a half of a settings menu"}, {"post_id": 7331, "ts": "2026-06-12T07:07:40Z", "hours": 3.8925, "text": "Fixed alot of stuff and added new level"}, {"post_id": 4081, "ts": "2026-06-07T08:36:17Z", "hours": 1.4181, "text": "BUGS & MINOR IMPROVEMENTS"}, {"post_id": 2608, "ts": "2026-06-05T07:14:08Z", "hours": 2.9469, "text": "ADDED LIGHTING MAJOR GAME FEATURES MUSIC FOR EACH LEVEL"}]...
|
Title: MY SWEET PRINCE by @Vini | Stardance
Devlo Title: MY SWEET PRINCE by @Vini | Stardance
Devlogs:
ADDED LIGHTING MAJOR GAME FEATURES MUSIC FOR EACH LEVEL
BUGS & MINOR IMPROVEMENTS
Fixed alot of stuff and added new level
I fixed alot of stuff and added a half of a settings menu
Yesterday I made this settings menu work it has full screen volume controls and level saves. I also added some of the finishing touches to the last level. I once again ask for people to test my game and give me feedback thank you and good bye
Ships:
This project has taken a significant amount of my life I know it only says 12h but that’s just the amount of time i’ve been working on it since stardance started...
|
1793084092.3168957
|
1793170492.3168957
|
|
3396
|
black hole by @siddharth_karuturi | Stardance
|
siddharth_karuturi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: black hole by @siddharth_karuturi | Stardan Title: black hole by @siddharth_karuturi | Stardance...
|
1792633793.7027168
|
1793238593.7027168
|
|
3397
|
Moonshine by @kritik | Stardance
|
kritik
|
1
|
58.21
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-08T01:46:24Z", "hours": 47.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a materials science engine meant to try and come up with candidates for novel materials with a high likleyhood of stability and validity for more advanced algorithms. The challenging part was integrating all the different tools being used, as well as perfectly tuning all tools to create accurate structures in as little time as possible. I am proud of the beautiful structures created by this algorithm. What to know to test this project is that its very unlikely a new material will be found on the first few tries, this has to be run for a while so start at the beta processing layer and run what is in the Alpha Arrays file. There is also lots of inaccuracies in this pipeline due to using off the self locally hosted LLM’s so you might have to run each layer a few times and not all candidates will be made.", "repo": "https://github.com/K200811/Project-MoonshineV2-Live", "demo": "https://github.com/K200811/Project-MoonshineV2-Live/releases/tag/v1.0.0"}]...
|
[{"post_id": 28069, "ts": "202 [{"post_id": 28069, "ts": "2026-07-14T02:58:00Z", "hours": 6.2922, "text": "IMPORTANT NOTE MOONSHINE TAKES A FEW HOURS TO RUN FOR THE BETA AND GAMMA LAYERS, SO JUST CHECK THE TERMINAL THAT OPENS UP WITH THE UI TO MAKE SURE EVERYTHING IS WORKING AND JUST WAIT YOU CAN ALSO SEE IT WORKING THROUGH THAT TERMINAL OUTPUT JUST MAKE SURE TO DOWNLOAD OLLAMA AND THE TWO AI MODELES THAT GO WITH IT, GEMMA THREE AND DEEPSEAK R1 . . . . In this last devlog I am showing how I turned my python project into a file that anyone can download and use on there Mac device without fiddling with python files and github repos. And boy was that a adventure. Firstly I know quite a bit about building python projects and everthing to do with building projects inside VSCode. I know ABSOLUTLY NOTHING about turning that into something others can easily use. The battles I faught with learning about file paths and directories and temp folders and the whole bajazz was enough to make Roman warriors run. But nontheless with Claude as my sensie and enough caffine to send a todler to the moon I was able to figure it out and Im going to outline some of it now. Firstly this project is a multi script project where you run each stage (Alpha - Epsilon) and check the output for each and move onto the next stage and so on jsut becuase thats how I liked it best. Now to comuncate information through differtent scripts I used JSON’s. But when packaging a python project you must make it so that insted of just writting with open (, …) the filename cant just be a name, it has to be a whole path. Learning that fact and how to implement that was a strugle. Then came the strugle of makeing a master script. At the begining of my master script I was importing each python file for each stage. That mixed with not having a run function in each stage and using if “name” == “ main ” to run all the main code for each stage resulted in a kathuple amount of erros and problems such as scripts not running, multiple windows being created, and more. The last bug problem was how to package everything together. I tried command after command with nothing working, only to then learn of how I must move all my files into the Dict folder created when packaging in order to make suer everything works properly. Now I just have to put this in a github release and everyone can use the executable file I have made."}, {"post_id": 26802, "ts": "2026-07-11T20:06:17Z", "hours": 4.9181, "text": "Realizing the importance of A UI for this I had base 44 whip up a UI you can connect to the python backend once you download it so you can see the stats of the algorithm running"}, {"post_id": 24366, "ts": "2026-07-07T21:33:11Z", "hours": 30.3122, "text": "MOONSHINE PROJECT FULLY FINISHED. In this devlog I am going to share how I was able to finally complete the Moonshine algorithm into a system that can autonomously generate novel crystal structures. Firstly The Beta and Gamma processing layers were changed to use locally hosted ollama models for the AI reasoning capabilities. In the Gamma layer a few changes were made as well. After constant experimenting with different AI models and architectures for the pipeline this was the one that I landed on. In the Gamma layer Ollama uses Deepseek to generate parameters for PyXtal crystal structure generation. I learned through constant experimentation that the PyXtal library’s randomness for crystal structure generation is much worse than I thought initially. Initially I thought with 10-20 tries the right structure would be generated. But no. Now what happens is the pipeline takes the parameters generated by deepseek and creates 500 pyXtal crystal structures. This adds about 3 minutes to the compute time for each candidate coming in from the Beta Processing Layer, but increases total accuracy by about 40%. The reason this helps is because PyXtal doesn’t get the structure right the first time, so by creating 500 and then picking the lowest energy generation we get the best structure we can from PyXtal. The next change made was the CHGNet relaxation phase inside of the Gamma Processing Layer. Initially I was using a random combination of convergence values, and structure optimizers. I changed that so now there are two layers to the relaxation phase. The first phase is a rough, low level, coarse relaxation that creates a rough initial structure, this is done by keeping the convergence value at 0.01 and using the basic UnitCellFillter optimizer. In the more stricter final relaxation pass the convergence value is tightened to 0.001 and the more advanced FrechetCellFilter is used. This has two benefits. firstly after the first pass the structure can be checked for validity and discarded if it is invalid before moving onto more expensive relaxation, secondly the structure created by PyXtal is relaxed more gently, by first getting an initial form and then being tightened down to its final form instead of taking the initial broken PyXtal structure and immediately forcing it into a tight final structure. It’s kind of like working with clay when making pots. Next comes the new Delta Processing Layer. The delta processing layer tests the structures made by the Gamma Processing layer further by subjecting it to a suite of tests. Atomic overlap, composition, coordination number plusability, oxidation number plusability, and structure matching against the materials project is tested on the crystal. This is done five times per candidate in beta since gamma produces five structures per candidate. This effectively tests validity and novelty for each structure. Finally comes the new Epsilon Processing Layer. This layer analyzes the structures created to give a better understanding of what we created, along with creating slab structures for the unit cell structure. Slab structures are just unit cell structures repeated into 3d space. Unit cell analysis returns density, unit cell volume, lattice parameters, final space group symmetry, local atomic geometry, bond lengths, bond angles, and prototype classification. Then comes the slab analisis. First the slabs are created by pymatgen, the main library used in this entire project, and analyzed for the following: surface symmetry, polarity, surface normal vectors, scale factors, center of mass alignment, termination layer composition, candidate adsorption sites, and total surface area. Slabs are created along the three Miller indices; there are just numbers that tell how the crystal is sliced in 3d space in reference to the three axes, (1,0,0) (1,1,0) and (1,1,1). And that’s the algorithm I spent over a month on. Now I have to just leave it running for a while and see if it finds any new crystal materials."}, {"post_id": 10331, "ts": "2026-06-17T00:19:18Z", "hours": 8.4331, "text": "I finished the Gamma Processing layer. This is the part of the file that takes in the formulas we created and screened in the Beta Processing Layer and then creates there structures and run a few initial validity tests on them. . First we start off with importing all the infinity stones of materials science. Then we get into our functions . First comes the Initial Super Gamma function. Ooooo fancyyy. No just kidding, I named everything so that I could tell which step of the process it came in just by reading the name. Initial tells me its the first and the Keyword super tells me its one of if not the first function to be run. Since keeping the order of every function run is super important for this to be built well this helps a lot. In the Initial Super Gamma Function we have a LLM, whos job is to take a look at the formula we created in the Beta Processing Layer and figure out what are the correct inputs to put into PyXtal for that formula. I will get into PyXtal in a bit . Next comes the SubGammaFunction. This function is nothing more than a overglorified string parser. It takes the output from the LLM, finds the key information we want, Dim, Group, Species, NumIons, and extracts them into variables we can input into PyXtal. Now all that seams straight forward right? So you can imagine my surprise when I was getting error after error in parsing the LLM response. I was so confused for some reason it could not extract the species from the response???? Yeah no it turned out I spelled species wrong in the function call. :) I know I make complaint jokes but its bugs, erros, and moments like that , that really make coding such a laugh, even those moments I really so enjoy. . Now back to the project! After parsing out all the information we can finally get to the interesting part 😈. CREATING AWESOME CRYSTAL STRUCTURES!!!!! PyXtal is a python tool that lets us randomly generate structures that don’t disobey fundamental laws of chemistry, such as Wyckoff positioning. The main challenge I had to overcome here was maintaining the structural group I had assigned to this crystal. PyXtal would be actively trying to create the best structure it thought was best but I wanted to preserve certain geometries to test since that is the most important thing in crystal creation . ANOTHER HUGE PROBLEM, I KEPT RUNNING OUT OF FREE CREDITS TO USE THE HUGGINGFACE AI MODELS. In the middle I tried to switch to Ollama locally hosted models I have before, but the remembered why I left them, THEY TAKE FOREVER. . After we create the PyXtal structures we run them through CHGNet to relax the structures, PyXtal SUCKS at creating low energy, high stability structures, its good at creating structures that don’t break certain rules such as Wyckoff positioning. After CHGNet relaxes the structure. It gives up the Stress values on the structure and the forces acting on the lattice of the crystal. We run 2 small loops to check each value and make sure its under 0.1 which is the value that is considered unstable for both metrics. If it passes the tests then its structure file is stored."}, {"post_id": 5973, "ts": "2026-06-10T00:36:20Z", "hours": 4.5428, "text": "Firstly I wrapped up the first step of this pipeline. I firstly changed Array Process to Alpha Process, and inside of it created functions for each step of that process making everything clean, professional, and modular. . After that I created a file called BetaProcess and restarted the Chemistry Checks there since there turned out to be MANY more steps to that process than what I had initially thought. Now what happens is firstly the Arrays we created in the Alpha Process are sent to deep seek to be put back together into molecular formulas. I this requires a new overly long prompt that details out all the steps the AI must take and chemistry rules and exceptions it must consider. I took some time in perfecting this prompt. After we get the reconstructed molecule we have to parse it out. Right now the LLM gives the molecule along with a whole response. I originally tried using Re to parse out the molecular formula. That didn’t work so then I had to format the LLM response to keep the answer at the end so I could just run normal string parsing to get the molecule. Then its shot off to the same LLM and prompt as the last devlog to find out how plausible the molecule is. . The challenges in this phase were making sure the deepsake model could put together even the hardest type of molecules so a big part of this was continuous testing and modifying of the prompt. . LLM’s are strange in how they always feel the need to have a 2 page explanation for every response. Because of that a bug challenge was figuring out how to parse out the information we want from each LLM response. . I was getting a headache looking at the outputs of this phase. Just words and number mushing together everywhere. So then I spent a lot of time formatting the output of this phase to make the information readable, understandable, and intuitive to follow."}, {"post_id": 4311, "ts": "2026-06-07T15:55:11Z", "hours": 3.3108, "text": "I started building the version 2 of Project Moonshine, a algorithm that’s meant to discover new crystals. This new engine takes a input of a reference material such as NH4H2PO4, and then breaks it into individual elements. It then systematically replaces every element with every element from the periodic table to generate THOUSANDS of potential new crystals. I got this idea from how real materials science discovery takes place. Scientists in a simulation mix and mash elements, using there extensive knowledge of chemistry to create new materials they think could work. Then atoms and elements are changed more to see what else can be created. . After we have our candidates I decided to first run initial screenings on the candidates to remove the ones that obviously won’t form stable crystals. I was initially going to test everything so we don’t lost any new crystals, but from version 1 I learned the enormous amount of time and compute that takes place in running high accuracy tests on these candidates (about 5 hours per test per molecule), and considering the fact I have over 10,000 CANDIDATES! and factoring in I want to finish this within the decade, I decided to run initial screenings. . I use the Qwen 2.5 model for plausibility analysis and deep seek to reconstruct the crystals from there array form that we created them in. When creating the candidates we break everything up into arrays, I thought the process of putting them back together would be as simple as counting the amount of times they appear in a array and then creating the empirical formula based on those subscripts of the elements. BUT NO. CHEMISTRY HAS 1000 RULES AND A 1000 MORE EXCEPTIONS IN MOLECULE FORMING. Instead of coding in every single one of these rules and exceptions , I decided to just use a AI model with strong reasoning. I am currently testing if this system for testing works. . Next I plan on improving the Chemistry rule set that these AI’s use so that I can make more accurate judgments about molecular forming and stability."}]...
|
Title: Moonshine by @kritik | Stardance
Devlogs:
Title: Moonshine by @kritik | Stardance
Devlogs:
I started building the version 2 of Project Moonshine, a algorithm that’s meant to discover new crystals. This new engine takes a input of a reference material such as NH4H2PO4, and then breaks it into individual elements. It then systematically replaces every element with every element from the periodic table to generate THOUSANDS of potential new crystals. I got this idea from how real materials science discovery takes place. Scientists in a simulation mix and mash elements, using there extensive knowledge of chemistry to create new materials they think could work. Then atoms and elements are changed more to see what else can be created. . After we have our candidates I decided to first run initial screenings on the candidates to remove the ones that obviously won’t form stable crystals. I was initially going to test everything so we don’t lost any new crystals, but from version 1 I learned the enormous amount of time and compute that takes place in running high accuracy tests on these candidates (about 5 hours per test per molecule), and considering the fact I have over 10,000 CANDIDATES! and factoring in I want to finish this within the decade, I decided to run initial screenings. . I use the Qwen 2.5 model for plausibility analysis and deep seek to reconstruct the crystals from there array form that we created them in. When creating the candidates we break everything up into arrays, I thought the process of putting them back together would be as simple as counting the amount of times they appear in a array and then creating the empirical formula based on those subscripts of the elements. BUT NO. CHEMISTRY HAS 1000 RULES AND A 1000 MORE EXCEPTIONS IN MOLECULE FORMING. Instead of coding in every single one of these rules and exceptions , I decided to just use a AI model with strong reasoning. I am currently testing if this system for testing works. . Next I plan on improving the Chemistry rule set that these AI’s use so that I can make more accurate judgments about molecular forming and stability.
Firstly I wrapped up the first step of this pipeline. I firstly changed Array Process to Alpha Process, and inside of it created functions for each step of that process making everything clean, professional, and modular. . After that I created a file called BetaProcess and restarted the Chemistry Checks there since there turned out to be MANY more steps to that process than what I had initially thought. Now what happens is firstly the Arrays we created in the Alpha Process are sent to deep seek to be put back together into molecular formulas. I this requires a new overly long prompt that details out all the steps the AI must take and chemistry rules and exceptions it must consider. I took some time in perfecting this prompt. After we get the reconstructed molecule we have to parse it out. Right now the LLM gives the molecule along with a whole response. I originally tried using Re to parse out the molecular formula. That didn’t work so then I had to format the LLM response to keep the answer at the end so I could just run normal string parsing to get the molecule. Then its shot off to the same LLM and prompt as the last devlog to find out how plausible the molecule is. . The challenges in this phase were making sure the deepsake model could put together even the hardest type of molecules so a big part of this was continuous testing and modifying of the prompt. . LLM’s are strange in how they always feel the need to have a 2 page explanation for every response. Because of that a bug challenge was figuring out how to parse out the information we want from each LLM response. . I was getting a headache looking at the outputs of this phase. Just words and number mushing together everywhere. So then I spent a lot of time formatting the output of this phase to make the information readable, understandable, and intuitive to follow.
I finished the Gamma Processing layer. This is the part of the file that takes in the formulas we created and screened in the Beta Processing Layer and then creates there structures and run a few initial validity tests on them. . First we start off with importing all the infinity stones of materials science. Then we get into our functions . First comes the Initial Super Gamma function. Ooooo fancyyy. No just kidding, I named everything so that I could tell which step of the process it came in just by reading the name. Initial tells me its the first and the Keyword super tells me its one of if not the first function to be run. Since keeping the order of every function run is super important for this to be built well this helps a lot. In the Initial Super Gamma Function we have a LLM, whos job is to take a look at the formula we created in the Beta Processing Layer and figure out what are the correct inputs to put into PyXtal for that formula. I will get into PyXtal in a bit . Next comes the SubGammaFunction. This function is nothing more than a overglorified string parser. It takes the output from the LLM, finds the key information we want, Dim, Group, Species, NumIons, and extracts them into variables we can input into PyXtal. Now all that seams straight forward right? So you can imagine my surprise when I was getting error after error in parsing the LLM response. I was so confused for some reason it could not extract the species from the response???? Yeah no it turned out I spelled species wrong in the function call. :) I know I make complaint jokes but its bugs, erros, and moments like that , that really make coding such a laugh, even those moments I really so enjoy. . Now back to the project! After parsing out all the information we can finally get to the interesting part 😈. CREATING AWESOME CRYSTAL STRUCTURES!!!!! PyXtal is a python tool that lets us randomly generate structures that don’t disobey fundamental laws of chemistry, such as Wyckoff positioning. The main challenge I had to overcome here was maintaining the structural group I had assigned to this crystal. PyXtal would be actively trying to create the best structure it thought was best but I wanted to preserve certain geometries to test since that is the most important thing in crystal creation . ANOTHER HUGE PROBLEM, I KEPT RUNNING OUT OF FREE CREDITS TO USE THE HUGGINGFACE AI MODELS. In the middle I tried to switch to Ollama locally hosted models I have before, but the remembered why I left them, THEY TAKE FOREVER. . After we create the PyXtal structures we run them through CHGNet to relax the structures, PyXtal SUCKS at creating low energy, high stability structures, its good at creating structures that don’t break certain rules such as Wyckoff positioning. After CHGNet relaxes the structure. It gives up the Stress values on the structure and the forces acting on the lattice of the crystal. We run 2 small loops to check each value and make sure its under 0.1 which is the value that is considered unstable for both metrics. If it passes the tests then its structure file is stored.
MOONSHINE PROJECT FULLY FINISHED. In this devlog I am going to share how I was able to finally complete the Moonshine algorithm into a system that can autonomously generate novel crystal structures. Firstly The Beta and Gamma processing layers were changed to use locally hosted ollama models for the AI reasoning capabilities. In the Gamma layer a few changes were made as well. After constant experimenting with different AI models and architectures for the pipeline this was the one that I landed on. In the Gamma layer Ollama uses Deepseek to generate parameters for PyXtal crystal structure generation. I learned through constant experimentation that the PyXtal library’s randomness for crystal structure generation is much worse than I thought initially. Initially I thought with 10-20 tries the right structure would be generated. But no. Now what happens is the pipeline takes the parameters generated by deepseek and creates 500 pyXtal crystal structures. This adds about 3 minutes to the compute time for each candidate coming in from the Beta Processing Layer, but increases total accuracy by about 40%. The reason this helps is because PyXtal doesn’t get the structure right the first time, so by creating 500 and then picking the lowest energy generation we get the best structure we can from PyXtal. The next change made was the CHGNet relaxation phase inside of the Gamma Processing Layer. Initially I was using a random combination of convergence values, and structure optimizers. I changed that so now there are two layers to the relaxation phase. The first phase is a rough, low level, coarse relaxation that creates a rough initial structure, this is done by keeping the convergence value at 0.01 and using the basic UnitCellFillter optimizer. In the more stricter final relaxation pass the convergence value is tightened to 0.001 and the more advanced FrechetCellFilter is used. This has two benefits. firstly after the first pass the structure can be checked for validity and discarded if it is invalid before moving onto more expensive relaxation, secondly the structure created by PyXtal is relaxed more gently, by first getting an initial form and then being tightened down to its final form instead of taking the initial broken PyXtal structure and immediately forcing it into a tight final structure. It’s kind of like working with clay when making pots. Next comes the new Delta Processing Layer. The delta processing layer tests the structures made by the Gamma Processing layer further by subjecting it to a suite of tests. Atomic overlap, composition, coordination number plusability, oxidation number plusability, and structure matching against the materials project is tested on the crystal. This is done five times per candidate in beta since gamma produces five structures per candidate. This effectively tests validity and novelty for each structure. Finally comes the new Epsilon Processing Layer. This layer analyzes the structures created to give a better understanding of what we created, along with creating slab structures for the unit cell structure. Slab structures are just unit cell structures repeated into 3d space. Unit cell analysis returns density, unit cell volume, lattice parameters, final space group symmetry, local atomic geometry, bond lengths, bond angles, and prototype classification. Then comes the slab analisis. First the slabs are created by pymatgen, the main library used in this entire project, and analyzed for the following: surface symmetry, polarity, surface normal vectors, scale factors, center of mass alignment, termination layer composition, candidate adsorption sites, and total surface area. Slabs are created along the three Miller indices; there are just numbers that tell how the crystal is sliced in 3d space in reference to the three axes, (1,0,0) (1,1,0) and (1,1,1). And that’s the algorithm I spent over a month on. Now I have to just leave it running for a while and see if it finds any new crystal materials.
Realizing the importance of A UI for this I had base 44 whip up a UI you can connect to the python backend once you download it so you can see the stats of the algorithm running
IMPORTANT NOTE MOONSHINE TAKES A FEW HOURS TO RUN FOR THE BETA AND GAMMA LAYERS, SO JUST CHECK THE TERMINAL THAT OPENS UP WITH THE UI TO MAKE SURE EVERYTHING IS WORKING AND JUST WAIT YOU CAN ALSO SEE IT WORKING THROUGH THAT TERMINAL OUTPUT JUST MAKE SURE TO DOWNLOAD OLLAMA AND THE TWO AI MODELES THAT GO WITH IT, GEMMA THREE AND DEEPSEAK R1 . . . . In this last devlog I am showing how I turned my python project into a file that anyone can download and use on there Mac device without fiddling with python files and github repos. And boy was that a adventure. Firstly I know quite a bit about building python projects and everthing to do with building projects inside VSCode. I know ABSOLUTLY NOTHING about turning that into something others can easily use. The battles I faught with learning about file paths and directories and temp folders and the whole bajazz was enough to make Roman warriors run. But nontheless with Claude as my sensie and enough caffine to send a todler to the moon I was able to figure it out and Im going to outline some of it now. Firstly this project is a multi script project where you run each stage (Alpha - Epsilon) and check the output for each and move onto the next stage and so on jsut becuase thats how I liked it best. Now to comuncate information through differtent scripts I used JSON’s. But when packaging a python project you must make it so that insted of just writting with open (, …) the filename cant just be a name, it has to be a whole path. Learning that fact and how to implement that was a strugle. Then came the strugle of makeing a master script. At the begining of my master script I was importing each python file for each stage. That mixed with not having a run function in each stage and using if “name” == “ main ” to run all the main code for each stage resulted in a kathuple amount of erros and problems such as scripts not running, multiple windows being created, and more. The last bug problem was how to package everything together. I tried command after command with nothing working, only to then learn of how I must move all my files into the Dict folder created when packaging in order to make suer everything works properly. Now I just have to put this in a github release and everyone can use the executable file I have made.
Ships:
I made a materials science engine meant to try and come up with candidates for novel materials with a high likleyhood of stability and validity for more advanced algorithms. The challenging part was integrating all the different tools being used, as well as perfectly tuning all tools to create accurate structures in as little time as possible. I am proud of the beautiful structures created by this algorithm. What to know to test this project is that its very unlikely a new material will be found on the first few tries, this has to be run for a while so start at the beta processing layer and run what is in the Alpha Arrays file. There is also lots of inaccuracies in this pipeline due to using off the self locally hosted LLM’s so you might have to run each layer a few times and not all candidates will be made....
|
1792997694.8511636
|
1793084094.8511636
|
|
3398
|
My first slack bot! by @Chalie | Stardance
|
Chalie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Chalie | Stardance
|
1792579764.7268426
|
1793184564.7268426
|
|
3399
|
My awesome macropad! by @nathan_chan3000 | Stardan My awesome macropad! by @nathan_chan3000 | Stardance...
|
nathan_chan3000
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @nathan_chan3000 | Title: My awesome macropad! by @nathan_chan3000 | Stardance...
|
1792504063.7605739
|
1793108863.7605739
|
|
3400
|
Space Debris Tracking Platform by @anishissharma11 Space Debris Tracking Platform by @anishissharma11 | Stardance...
|
anishissharma11
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Space Debris Tracking Platform by @anishiss Title: Space Debris Tracking Platform by @anishissharma11 | Stardance...
|
1792748886.2465436
|
1793353686.2465436
|