|
5416
|
Untitled project by @Mr_Ghost | Stardance
|
Mr_Ghost
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Mr_Ghost | Stardance
|
1793573439.8550572
|
1794178239.8550572
|
|
5417
|
Baguette Simulator 2: Breader and Butter by @AceMa Baguette Simulator 2: Breader and Butter by @AceMaestro | Stardance...
|
AceMaestro
|
0
|
3.12
|
0
|
[]
|
[{"post_id": 9039, "ts": "2026 [{"post_id": 9039, "ts": "2026-06-15T02:46:33Z", "hours": 1.4164, "text": "actual nothing burger hour, all i got fer it was some exotic colors"}, {"post_id": 8978, "ts": "2026-06-14T22:58:20Z", "hours": 1.7056, "text": "one dang card preset took 50 minutes; its over"}]...
|
Title: Baguette Simulator 2: Breader and Butter by Title: Baguette Simulator 2: Breader and Butter by @AceMaestro | Stardance
Devlogs:
one dang card preset took 50 minutes; its over
actual nothing burger hour, all i got fer it was some exotic colors...
|
1793170152.2900345
|
1793774952.2900345
|
|
5418
|
My first slack bot! by @dfe | Stardance
|
dfe
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @dfe | Stardance
|
1792939807.199996
|
1793803807.199996
|
|
5419
|
Fuzz pedal by @mitulsanikal | Stardance
|
mitulsanikal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Fuzz pedal by @mitulsanikal | Stardance
|
1793260489.410312
|
1793865289.410312
|
|
5420
|
My awesome macropad! by @romeo | Stardance
|
romeo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @romeo | Stardance
|
1793174071.8990128
|
1793778871.8990128
|
|
5421
|
Untitled project by @stephen_stanchev | Stardance
|
stephen_stanchev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @stephen_stanchev | Sta Title: Untitled project by @stephen_stanchev | Stardance...
|
1793480079.556409
|
1794084879.556409
|
|
5422
|
My first slack bot! by @g4bbydonut | Stardance
|
g4bbydonut
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @g4bbydonut | Starda Title: My first slack bot! by @g4bbydonut | Stardance...
|
1793573446.2699149
|
1794178246.2699149
|
|
5423
|
My first slack bot! by @Mr_Ghost | Stardance
|
Mr_Ghost
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Mr_Ghost | Stardanc Title: My first slack bot! by @Mr_Ghost | Stardance...
|
1793400908.4031909
|
1794005708.4031909
|
|
5424
|
My awesome macropad! by @sb26shlokkalt | Stardance
|
sb26shlokkalt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sb26shlokkalt | St Title: My awesome macropad! by @sb26shlokkalt | Stardance...
|
1793209857.8751369
|
1793814657.8751369
|
|
5425
|
My first slack bot! by @Sammy-P | Stardance
|
Sammy-P
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Sammy-P | Stardance
|
1793450994.2418928
|
1794055794.2418928
|
|
5426
|
A sidescrolling minimalistic boss rush thing (seco A sidescrolling minimalistic boss rush thing (second boss and polish!) by @dfe | Stardance...
|
dfe
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A sidescrolling minimalistic boss rush thin Title: A sidescrolling minimalistic boss rush thing (second boss and polish!) by @dfe | Stardance...
|
1792918234.9451792
|
1793782234.9451792
|
|
5427
|
My first slack bot! by @RmSchep | Stardance
|
RmSchep
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @RmSchep | Stardance
|
1793414966.5310986
|
1794019766.5310986
|
|
5428
|
Untitled project by @Arda | Stardance
|
Arda
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Arda | Stardance
|
1793450852.4135575
|
1794055652.4135575
|
|
5429
|
Simple ball physics by @Unknown | Stardance
|
Unknown
|
1
|
3.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-02T23:29:05Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made an simple physics engine with rust one of the most hardest language and this was tough i learned a lot of things on the way. for people to use this they just need to use cargo install ball-engine", "repo": "https://github.com/parth2152012/ball-engine", "demo": "https://youtu.be/wHnqk7BGGVs"}]...
|
[{"post_id": 1087, "ts": "2026 [{"post_id": 1087, "ts": "2026-06-02T22:12:11Z", "hours": 2.0731, "text": "Hi everyone i have finished my project"}, {"post_id": 988, "ts": "2026-06-02T19:25:04Z", "hours": 1.3894, "text": "Hello everyone so i am currently working on a rust project trying to make an physics engine of balls currently i can draw the balls and simulate them i will now try to add ball collision i will keep all of you updated after this project i am planing to make like an 2d game engine :)"}]...
|
Title: Simple ball physics by @Unknown | Stardance Title: Simple ball physics by @Unknown | Stardance
Devlogs:
Hello everyone so i am currently working on a rust project trying to make an physics engine of balls currently i can draw the balls and simulate them i will now try to add ball collision i will keep all of you updated after this project i am planing to make like an 2d game engine :)
Hi everyone i have finished my project
Ships:
I made an simple physics engine with rust one of the most hardest language and this was tough i learned a lot of things on the way. for people to use this they just need to use cargo install ball-engine...
|
1793545021.48833
|
1793631421.48833
|
|
5430
|
MarketPULSE by @lucasdsandoval30 | Stardance
|
lucasdsandoval30
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: MarketPULSE by @lucasdsandoval30 | Stardanc Title: MarketPULSE by @lucasdsandoval30 | Stardance...
|
1793371642.5908022
|
1793976442.5908022
|
|
5431
|
Down to Earth by @AlexG | Stardance
|
AlexG
|
0
|
7.12
|
0
|
[]
|
[{"post_id": 35585, "ts": "202 [{"post_id": 35585, "ts": "2026-07-27T03:39:58Z", "hours": 1.6594, "text": "I made the dairy containers rotatable, so you can pick between whole, almond, or oat."}, {"post_id": 12828, "ts": "2026-06-21T00:19:29Z", "hours": 1.8975, "text": "Added arrows to switch between screen on the 2d side, and a countertop and simple movement and viewing controls on the 3d side."}, {"post_id": 12165, "ts": "2026-06-19T21:27:09Z", "hours": 2.89, "text": "Added a notebook to record customers’ orders and updated the cursor."}, {"post_id": 1454, "ts": "2026-06-03T14:30:49Z", "hours": 0.6728, "text": "I added a scoring system to see how good you did based on what the requested drink was"}]...
|
Title: Down to Earth by @AlexG | Stardance
Devlog Title: Down to Earth by @AlexG | Stardance
Devlogs:
I added a scoring system to see how good you did based on what the requested drink was
Added a notebook to record customers’ orders and updated the cursor.
Added arrows to switch between screen on the 2d side, and a countertop and simple movement and viewing controls on the 3d side.
I made the dairy containers rotatable, so you can pick between whole, almond, or oat....
|
1793249416.3037324
|
1793854216.3037324
|
|
5432
|
My first slack bot! by @Rlritter4 | Stardance
|
Rlritter4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Rlritter4 | Stardan Title: My first slack bot! by @Rlritter4 | Stardance...
|
1793433375.2504153
|
1794038175.2504153
|
|
5433
|
Google by @Ahmed_Gayipov | Stardance
|
Ahmed_Gayipov
|
1
|
3.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-16T16:39:34Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a similar working version of google", "repo": "https://github.com/Cr7-is-the-best/my3-python", "demo": "https://github.com/Cr7-is-the-best/my3-python.git"}]...
|
[{"post_id": 996, "ts": "2026- [{"post_id": 996, "ts": "2026-06-02T19:35:10Z", "hours": 2.6653, "text": "Look at the Google that i made so far"}]...
|
Title: Google by @Ahmed_Gayipov | Stardance
Devlo Title: Google by @Ahmed_Gayipov | Stardance
Devlogs:
Look at the Google that i made so far
Ships:
I made a similar working version of google...
|
1792878853.5403235
|
1793742853.5403235
|
|
5434
|
Untitled by @Thiago20 | Stardance
|
Thiago20
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Thiago20 | Stardance
|
1793494555.5819688
|
1794099355.5819688
|
|
5435
|
A robotic arm with openCV based on Arduino UNO by A robotic arm with openCV based on Arduino UNO by @angelina | Stardance...
|
angelina
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A robotic arm with openCV based on Arduino Title: A robotic arm with openCV based on Arduino UNO by @angelina | Stardance...
|
1793444145.5671623
|
1794048945.5671623
|
|
5436
|
Untitled by @dev_khang_tran | Stardance
|
dev_khang_tran
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @dev_khang_tran | Stardance
|
1793231674.8693357
|
1793836474.8693357
|
|
5437
|
My first slack bot! by @priyanka | Stardance
|
priyanka
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @priyanka | Stardanc Title: My first slack bot! by @priyanka | Stardance...
|
1793317823.0755394
|
1793922623.0755394
|
|
5438
|
My awesome macropad! by @Gooderswills | Stardance
|
Gooderswills
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Gooderswills | Sta Title: My awesome macropad! by @Gooderswills | Stardance...
|
1792914511.3446581
|
1793778511.3446581
|
|
5439
|
Untitled project by @FIlip | Stardance
|
FIlip
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @FIlip | Stardance
|
1793368454.415826
|
1793973254.415826
|
|
5440
|
Stardance by @olive | Stardance
|
olive
|
0
|
10.76
|
0
|
[]
|
[{"post_id": 995, "ts": "2026- [{"post_id": 995, "ts": "2026-06-02T19:34:45Z", "hours": 10.7592, "text": "I danced"}]...
|
Title: Stardance by @olive | Stardance
Devlogs:
I Title: Stardance by @olive | Stardance
Devlogs:
I danced...
|
1793436990.8798938
|
1794041790.8798938
|
|
5441
|
My awesome macropad! by @Coffee | Stardance
|
Coffee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Coffee | Stardance
|
1793512554.4355724
|
1794117354.4355724
|
|
5442
|
My awesome macropad! by @JensenHuangFan | Stardanc My awesome macropad! by @JensenHuangFan | Stardance...
|
JensenHuangFan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @JensenHuangFan | S Title: My awesome macropad! by @JensenHuangFan | Stardance...
|
1792925439.028996
|
1793789439.028996
|
|
5443
|
My awesome macropad! by @chaudhry_mohammad | Stard My awesome macropad! by @chaudhry_mohammad | Stardance...
|
chaudhry_mohammad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @chaudhry_mohammad Title: My awesome macropad! by @chaudhry_mohammad | Stardance...
|
1793454835.4777303
|
1794059635.4777303
|
|
5444
|
My awesome macropad! by @CosmicChaos13th | Stardan My awesome macropad! by @CosmicChaos13th | Stardance...
|
CosmicChaos13th
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @CosmicChaos13th | Title: My awesome macropad! by @CosmicChaos13th | Stardance...
|
1793461936.007123
|
1794066736.007123
|
|
5446
|
NovaPad by @block | Stardance
|
block
|
0
|
7.02
|
0
|
[]
|
[{"post_id": 15710, "ts": "202 [{"post_id": 15710, "ts": "2026-06-25T15:45:34Z", "hours": 1.4883, "text": "Worked on fixing the screw holes and writing code. for securing the top plate, I decided to go without the heated inserts, due to lack of space, but I had plenty of space for securing the board. I’m not really sure what I want the NovaPad to do yet, so for now I just have each button typing a different number, with the rotary encoder controlling volume and OLED screen displaying “NovaPad” for now. I think I will leave this up for later me, and use it when I need it kind of. It should be easy to customize when I want something changed."}, {"post_id": 4483, "ts": "2026-06-07T20:16:28Z", "hours": 4.4544, "text": "Got the design for the case mostly done! Although I have just ran into an issue where I made the holes for the heated inserts 4mm, instead of the recommended 4.7mm, so I’ll have to find a way to make room for that."}, {"post_id": 2815, "ts": "2026-06-05T17:16:27Z", "hours": 0.5147, "text": "Finished the layout and traces for the PCB! I’ve also decided to finally name my MacroPad… NovaPad! Along the way I realized just how hard drawing traces is, and learned a lot too. I’d also ran into an issue when I had centered the LED’s on each of the keys, where some of the pads were too close, giving me DRC errors, forcing me to move all of the LED’s down 4mm. Next thing I have to do is design the case. (The tracker kind of stopped working for some reason, and this took me almost five hours, NOT 30 minutes)"}, {"post_id": 1736, "ts": "2026-06-03T22:21:25Z", "hours": 0.5658, "text": "Finished the Schematic! Name is a work in progress."}]...
|
Title: NovaPad by @block | Stardance
Devlogs:
Fin Title: NovaPad by @block | Stardance
Devlogs:
Finished the Schematic! Name is a work in progress.
Finished the layout and traces for the PCB! I’ve also decided to finally name my MacroPad… NovaPad! Along the way I realized just how hard drawing traces is, and learned a lot too. I’d also ran into an issue when I had centered the LED’s on each of the keys, where some of the pads were too close, giving me DRC errors, forcing me to move all of the LED’s down 4mm. Next thing I have to do is design the case. (The tracker kind of stopped working for some reason, and this took me almost five hours, NOT 30 minutes)
Got the design for the case mostly done! Although I have just ran into an issue where I made the holes for the heated inserts 4mm, instead of the recommended 4.7mm, so I’ll have to find a way to make room for that.
Worked on fixing the screw holes and writing code. for securing the top plate, I decided to go without the heated inserts, due to lack of space, but I had plenty of space for securing the board. I’m not really sure what I want the NovaPad to do yet, so for now I just have each button typing a different number, with the rotary encoder controlling volume and OLED screen displaying “NovaPad” for now. I think I will leave this up for later me, and use it when I need it kind of. It should be easy to customize when I want something changed....
|
1793029651.8964195
|
1793634451.8964195
|
|
5448
|
My first slack bot! by @Ema | Stardance
|
Ema
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Ema | Stardance
|
1793317830.2949874
|
1793922630.2949874
|
|
5449
|
My awesome macropad! by @MikeyKunnn | Stardance
|
MikeyKunnn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @MikeyKunnn | Stard Title: My awesome macropad! by @MikeyKunnn | Stardance...
|
1793515941.774736
|
1794120741.774736
|
|
5450
|
Untitled project by @paperdragon | Stardance
|
paperdragon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @paperdragon | Stardanc Title: Untitled project by @paperdragon | Stardance...
|
1793483690.0019696
|
1794088490.0019696
|
|
5451
|
Chess.com stats slack bot by @marcsello | Stardanc Chess.com stats slack bot by @marcsello | Stardance...
|
marcsello
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-02T22:33:39Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a Slack bot that returns data from the chess.com api. This is my first backend project and it was a lot of fun.", "repo": "https://github.com/MarcselloDev/chesscomstatsslackbot", "demo": "https://hackclub.enterprise.slack.com/archives/C0B7SD8GBTQ"}]...
|
[{"post_id": 1094, "ts": "2026 [{"post_id": 1094, "ts": "2026-06-02T22:26:19Z", "hours": 1.4853, "text": "Created the Slack Bot Commands: /chesscomprofile Displays stats about a user on Chess.com. /chesscomgames Displays the last 3 games of a user on Chess.com in the current month. /chesscompuzzle Returns a link to a random daily puzzle on Chess.com."}]...
|
Title: Chess.com stats slack bot by @marcsello | S Title: Chess.com stats slack bot by @marcsello | Stardance
Devlogs:
Created the Slack Bot Commands: /chesscomprofile Displays stats about a user on Chess.com. /chesscomgames Displays the last 3 games of a user on Chess.com in the current month. /chesscompuzzle Returns a link to a random daily puzzle on Chess.com.
Ships:
I made a Slack bot that returns data from the chess.com api. This is my first backend project and it was a lot of fun....
|
1793605904.2878482
|
1793692304.2878482
|
|
5452
|
My first slack bot! by @llint | Stardance
|
llint
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @llint | Stardance
|
1793552248.6887877
|
1794157048.6887877
|
|
5453
|
Untitled project by @hasib_noori | Stardance
|
hasib_noori
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @hasib_noori | Stardanc Title: Untitled project by @hasib_noori | Stardance...
|
1793465394.3952918
|
1794070194.3952918
|
|
5454
|
Macro pad! by @stephenfromcolorado | Stardance
|
stephenfromcolorado
|
0
|
0.29
|
0
|
[]
|
[{"post_id": 1107, "ts": "2026 [{"post_id": 1107, "ts": "2026-06-02T22:45:16Z", "hours": 0.2878, "text": "I made the pcb for the macro pad ts took like a hour but freeking hacka time is so bad"}]...
|
Title: Macro pad! by @stephenfromcolorado | Starda Title: Macro pad! by @stephenfromcolorado | Stardance
Devlogs:
I made the pcb for the macro pad ts took like a hour but freeking hacka time is so bad...
|
1793404272.8029988
|
1794009072.8029988
|
|
5455
|
Robotic Actuator by @cloudcake8 | Stardance
|
cloudcake8
|
0
|
3.41
|
0
|
[]
|
[{"post_id": 8960, "ts": "2026 [{"post_id": 8960, "ts": "2026-06-14T22:13:58Z", "hours": 1.6961, "text": "finally figured out why my 2 phases werent looking right so the feaaturescript im using to generate the cyclodial profile only generates it with one tooth fully “in”, making it so that if i want another disc exactly 180 degrees out of phase, i need to have an even amount of pins and an odd amount of teeth for it to work so instead of 16:1 i’m running 15:1 and im switching from 2 bearings to 1 pressfit bearing because i thought about it and there really isn’t any thrust forces present in the gearbox so its probably fine, i might add some sort of bearing retainment though just in case, otherwise its just going to be retaining compounded in"}, {"post_id": 8564, "ts": "2026-06-14T07:15:59Z", "hours": 0.8597, "text": "ok so i want to run ball bearings for all of my pins on the cycloid, did some preliminary research and right now with my cycloid disc setup it would have required 196 individual bearings (but i think i can get it down by a lot by narrowing my cyclodial discs) theres a lot im confused about but im working it out slowly, specifically how do i make sure my output shaft is strong enough to support a whole joint"}, {"post_id": 4057, "ts": "2026-06-07T07:29:55Z", "hours": 0.8506, "text": "figuring out what motors and how the structure of the gearbox will look like doing some research on motors, i am choosing the WK8110 frameless outrunner frameless because i want to fit a cyclodial reduction inside of it (mini cheetah style) outrunner because they have more torque (i am trying to target high torque without too much of a reduction ratio so i can have some backdrivability so whatever joint this is on acts as if its connected directly to the motor, hence the “quasi” direct drive) i think i’ll also use some cheap motor controller, most likely a simpleFOC board of some sort (aliexpress clones), because they are super cheap and i think they should be good enough for at least testing on a desk. if i do testing and they explode on me or can’t handle the current or something, i’ll splurge on some vesc based motor controller OR maybe an odrive board (or odrive clone on aliexpress) for the complete robot of whatever i’m making (quadruped?) i’ve found i want to target around ~16:1 for the ratio, because lowkey these motors have like no torque from their spec sheets so i need a higher ratio than ideal (to get all the benefits of “quasi direct drive” its ideal to have a lower ratio so its a more direct connection to the motor kinda), this ratio should get me around 40 ish max nm of torque (woah! lowkey a lot!) so maybe i can do some jumps or something if the robot is light enough not sure about what encoder setup i’ll use, did some digging on amazon for bearings and bushings to support everything, i think i’ll do m4 or m3 sleeve bushings for the outer pins and the inner pins, and some random bearing for the inner eccentric bearing and i’ll support everything with massive bearings so that the outrunner is properly alligned to the stator (need to find 90mm id bearings that arent really expensive, or figure out how to package cheaper smaller bearings to constrain the motor) i just spent a lot of time thinking about how everything will package and rotating around the model to think about it from different angles not sure what material i will do the cycloid discs out of (probably just 6061 alu, laser cut from some online service), and for the enclosure i think i’ll do some nylon composite filament for strength and heat resistance (or maybe just PLA for this prototype) otherwise, i think this session gave me a pretty solid mental image of what the whole actuator will look like and i’m excited to design the rest of it"}]...
|
Title: Robotic Actuator by @cloudcake8 | Stardance Title: Robotic Actuator by @cloudcake8 | Stardance
Devlogs:
figuring out what motors and how the structure of the gearbox will look like doing some research on motors, i am choosing the WK8110 frameless outrunner frameless because i want to fit a cyclodial reduction inside of it (mini cheetah style) outrunner because they have more torque (i am trying to target high torque without too much of a reduction ratio so i can have some backdrivability so whatever joint this is on acts as if its connected directly to the motor, hence the “quasi” direct drive) i think i’ll also use some cheap motor controller, most likely a simpleFOC board of some sort (aliexpress clones), because they are super cheap and i think they should be good enough for at least testing on a desk. if i do testing and they explode on me or can’t handle the current or something, i’ll splurge on some vesc based motor controller OR maybe an odrive board (or odrive clone on aliexpress) for the complete robot of whatever i’m making (quadruped?) i’ve found i want to target around ~16:1 for the ratio, because lowkey these motors have like no torque from their spec sheets so i need a higher ratio than ideal (to get all the benefits of “quasi direct drive” its ideal to have a lower ratio so its a more direct connection to the motor kinda), this ratio should get me around 40 ish max nm of torque (woah! lowkey a lot!) so maybe i can do some jumps or something if the robot is light enough not sure about what encoder setup i’ll use, did some digging on amazon for bearings and bushings to support everything, i think i’ll do m4 or m3 sleeve bushings for the outer pins and the inner pins, and some random bearing for the inner eccentric bearing and i’ll support everything with massive bearings so that the outrunner is properly alligned to the stator (need to find 90mm id bearings that arent really expensive, or figure out how to package cheaper smaller bearings to constrain the motor) i just spent a lot of time thinking about how everything will package and rotating around the model to think about it from different angles not sure what material i will do the cycloid discs out of (probably just 6061 alu, laser cut from some online service), and for the enclosure i think i’ll do some nylon composite filament for strength and heat resistance (or maybe just PLA for this prototype) otherwise, i think this session gave me a pretty solid mental image of what the whole actuator will look like and i’m excited to design the rest of it
ok so i want to run ball bearings for all of my pins on the cycloid, did some preliminary research and right now with my cycloid disc setup it would have required 196 individual bearings (but i think i can get it down by a lot by narrowing my cyclodial discs) theres a lot im confused about but im working it out slowly, specifically how do i make sure my output shaft is strong enough to support a whole joint
finally figured out why my 2 phases werent looking right so the feaaturescript im using to generate the cyclodial profile only generates it with one tooth fully “in”, making it so that if i want another disc exactly 180 degrees out of phase, i need to have an even amount of pins and an odd amount of teeth for it to work so instead of 16:1 i’m running 15:1 and im switching from 2 bearings to 1 pressfit bearing because i thought about it and there really isn’t any thrust forces present in the gearbox so its probably fine, i might add some sort of bearing retainment though just in case, otherwise its just going to be retaining compounded in...
|
1793180871.0182781
|
1793785671.0182781
|
|
5456
|
ATLAS by @Scout | Stardance
|
Scout
|
1
|
1.33
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-08T20:27:31Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "This is ATLAS, a Image search and geo recognition tool that uses VLMs (Visual Language Models) to scan a string of images, guess where they were taken, and supply estimated coordinates. (As said in my Dev log the coordinates may be off wildly, this is a known issue being worked on currently) The code is being worked on every week and major updates are to come, V3.3 is not the final model. I plan a V4 very soon…", "repo": "https://github.com/ScoutV41/ATLAS", "demo": "https://github.com/ScoutV41/ATLAS/releases/tag/D1"}]...
|
[{"post_id": 25712, "ts": "202 [{"post_id": 25712, "ts": "2026-07-10T04:30:44Z", "hours": 0.3333, "text": "D-LOG #2 (Based on work from the past month, was on vaca sorry for taking forever) Build: ATLASV3.3(L) Biggest changes: Full luminance curve pre-pass Instead of just thresholding each frame’s brightness individually, the script now buckets every image into 5-minute slots, builds a brightness curve across the entire dataset, and derives actual sunrise/sunset intervals from where the curve crosses DAY_THRESHOLD (20.0). There’s also a MIN_DAY_DURATION floor (1 hour) so a passing cloud or a lens flare can’t fake a fake “day.” Anything outside a real daylight window gets logged as NIGHT_CURVE_SKIPPED and skipped before the VLM even sees it saves a ton of compute on a big folder. Results get merged: Shadow angle -> circular mean across models, flagged DISAGREE if spread > 45° Shadow length / density / rock texture / volcanic features -> majority vote Plant types / rock colors -> unioned into one combined list Latitude derivation Previous versions only estimated longitude. v3.3 adds a day-length-based latitude calc, it finds the longest daylight interval in the dataset, converts that duration into a sunset hour angle, and solves for latitude using solar declination for the day of year. Search area validation Both derived coordinates now get checked against a Haversine distance from a defined SEARCH_CENTER / SEARCH_RADIUS_KM, with a clean ✅ / ❌ status line and a fallback bounding box printed if the point lands outside the circle. Habitat classifier got smarter HABITAT_RULES is now a proper rule list -> each biome match is a lambda checking keyword hits across plant types, rock color, and vegetation density instead of a flat tally. Sonoran/Chihuahuan/Mojave/Colorado Plateau/Cascades/Sierra-Great Basin/High Desert/Mixed Conifer are all still in there, just with tighter matching logic. Parser resilience parse_field() handles models that randomly bold their output ( SHADOW_ANGLE: etc.) and normalizes stray ° symbols and none/n/a/null variants down to “unknown” so downstream math doesn’t choke on garbage strings. Known issue, flagging this for myself before I forget The longitude calc in main() is currently hardcoded, not pulling from the actual solar_noon_avg computed earlier in the run: day_of_year = 138 # May 18th eot = 3.65 # Verified EoT for Day 1 noon_secs = 84495 # Verified 23:28:15 UTC trajectory That’s leftover from debugging against the sample dataset, it means every run right now spits out the same longitude regardless of what images you actually feed it, which is obviously not the goal. Latitude is properly dynamic (built off intervals from the real daylight curve), longitude isn’t yet. Top priority fix for the next patch, need to swap those three constants for the real per-dataset solar_noon_avg / Julian day / EoT calc instead of the frozen debug values. Next up Wire the real solar_noon_avg (already computed in compute_solar_noon()) into the longitude block instead of the hardcoded Day 1 constants Maybe expand HABITAT_RULES matching beyond simple keyword hits, closer to weighted scoring Look into whether internvl2_5-4b is pulling its weight in the ensemble or just adding runtime for marginal disagreement value"}, {"post_id": 2525, "ts": "2026-06-05T01:55:27Z", "hours": 1.4319, "text": "Devlog - 01 A few weeks ago I almost helped find $20K buried somewhere in the American southwest. ATLAS is the image recognition pipeline I built to try. It Works by taking a feed of images (50+ for best results, I used 625 for my tests) sending them through Various Local VLMs for inference. (Via LM Studio) I’ve been working on this project for weeks, decided to share it with everyone here. Currently I am working on Version 3.3. Previous models of ATLAS only utilized one VLM for inference, I had noticed the outputs to be significantly off course. So In V3.3 I designed it to use an ensemble system. Instead of using one model, it cross checks data between 2 or more. Then determines the winning output from all models. This way if one model hallucinates and the others don’t, Your data wont be skewed… Though I am still working out some bugs, as V3.3 has been off course by a MARGIN. It runs a user defined boundary. So instead of having to manually check coordinates yourself you’d know if it was incorrect instantly. Though V3.3 doesn’t really respect the boundary, so I need to get that fixed. -(My latest test ran 4,355Km off target. this is a known geometry bug in the coordinate derivation, not the inference pipeline itself) The speed at which ATLAS Processes images depends entirely on your hardware and number/type of model(s) you are using. Example: (Using qwen 2.5 7B (Q4_K_M), and Moondream 2 (Q4) 600 Frames Estimated Times Best tier GPU: RTX 4090, Dual RTX 3090s, Mac Studio M3 Ultra, etc… Runtime: Qwen 2.5 7B ~0.25 seconds Moondream2 ~0.08 seconds Total: 3 to 4 minutes High Tier GPU: RTX 4080, RTX 4070 Ti Super, M3 Max, etc… Runtime Qwen 2.5 7B ~0.60 seconds Moondream2 ~0.20 seconds Total: 6 to 8 minutes Mid tier GPU: RTX 4060 Ti (16GB), RTX 4070, M3 Pro, etc… Runtime Qwen 2.5 7B ~2.00 seconds Moondream2 ~0.50 seconds Total: 22 to 30 minutes Low tier GPU: RTX 3050, GTX 1660 Super, Base M1/M2 Mac, etc… Runtime: Qwen 2.5 7B ~5.00 seconds Moondream2 ~1.20 seconds Total: 1 to 1.5 hours CPU Only: Core i9 / Ryzen 9 (32GB DDR5 RAM), etc… Runtime: Qwen 2.5 7B ~35.00 seconds Moondream2 ~7.00 seconds Total: 6 to 8 hours (tested on RX 9070 XT 16GB) Updated features: Global Luminance Profiling: maps brightness across the entire dataset to skip night frames before inference, saves ~10% compute Triple-Model Consensus Pass: runs 3 VLMs in parallel and cross-checks outputs to filter hallucinations Orbital Mechanics Longitude Tracking: derives longitude from solar noon timing in image timestamps Haversine Validator: checks derived coordinates against the search boundary using spherical earth math Currently working on fixing shadow angle calculation (Keeps returning unknown for certain vectors), and Search area constraint bias. (Image shows V3.3 running with a Tri-Qwen ensemble)"}]...
|
Title: ATLAS by @Scout | Stardance
Devlogs:
Devlo Title: ATLAS by @Scout | Stardance
Devlogs:
Devlog - 01 A few weeks ago I almost helped find $20K buried somewhere in the American southwest. ATLAS is the image recognition pipeline I built to try. It Works by taking a feed of images (50+ for best results, I used 625 for my tests) sending them through Various Local VLMs for inference. (Via LM Studio) I’ve been working on this project for weeks, decided to share it with everyone here. Currently I am working on Version 3.3. Previous models of ATLAS only utilized one VLM for inference, I had noticed the outputs to be significantly off course. So In V3.3 I designed it to use an ensemble system. Instead of using one model, it cross checks data between 2 or more. Then determines the winning output from all models. This way if one model hallucinates and the others don’t, Your data wont be skewed… Though I am still working out some bugs, as V3.3 has been off course by a MARGIN. It runs a user defined boundary. So instead of having to manually check coordinates yourself you’d know if it was incorrect instantly. Though V3.3 doesn’t really respect the boundary, so I need to get that fixed. -(My latest test ran 4,355Km off target. this is a known geometry bug in the coordinate derivation, not the inference pipeline itself) The speed at which ATLAS Processes images depends entirely on your hardware and number/type of model(s) you are using. Example: (Using qwen 2.5 7B (Q4_K_M), and Moondream 2 (Q4) 600 Frames Estimated Times Best tier GPU: RTX 4090, Dual RTX 3090s, Mac Studio M3 Ultra, etc… Runtime: Qwen 2.5 7B ~0.25 seconds Moondream2 ~0.08 seconds Total: 3 to 4 minutes High Tier GPU: RTX 4080, RTX 4070 Ti Super, M3 Max, etc… Runtime Qwen 2.5 7B ~0.60 seconds Moondream2 ~0.20 seconds Total: 6 to 8 minutes Mid tier GPU: RTX 4060 Ti (16GB), RTX 4070, M3 Pro, etc… Runtime Qwen 2.5 7B ~2.00 seconds Moondream2 ~0.50 seconds Total: 22 to 30 minutes Low tier GPU: RTX 3050, GTX 1660 Super, Base M1/M2 Mac, etc… Runtime: Qwen 2.5 7B ~5.00 seconds Moondream2 ~1.20 seconds Total: 1 to 1.5 hours CPU Only: Core i9 / Ryzen 9 (32GB DDR5 RAM), etc… Runtime: Qwen 2.5 7B ~35.00 seconds Moondream2 ~7.00 seconds Total: 6 to 8 hours (tested on RX 9070 XT 16GB) Updated features: Global Luminance Profiling: maps brightness across the entire dataset to skip night frames before inference, saves ~10% compute Triple-Model Consensus Pass: runs 3 VLMs in parallel and cross-checks outputs to filter hallucinations Orbital Mechanics Longitude Tracking: derives longitude from solar noon timing in image timestamps Haversine Validator: checks derived coordinates against the search boundary using spherical earth math Currently working on fixing shadow angle calculation (Keeps returning unknown for certain vectors), and Search area constraint bias. (Image shows V3.3 running with a Tri-Qwen ensemble)
D-LOG #2 (Based on work from the past month, was on vaca sorry for taking forever) Build: ATLASV3.3(L) Biggest changes: Full luminance curve pre-pass Instead of just thresholding each frame’s brightness individually, the script now buckets every image into 5-minute slots, builds a brightness curve across the entire dataset, and derives actual sunrise/sunset intervals from where the curve crosses DAY_THRESHOLD (20.0). There’s also a MIN_DAY_DURATION floor (1 hour) so a passing cloud or a lens flare can’t fake a fake “day.” Anything outside a real daylight window gets logged as NIGHT_CURVE_SKIPPED and skipped before the VLM even sees it saves a ton of compute on a big folder. Results get merged: Shadow angle -> circular mean across models, flagged DISAGREE if spread > 45° Shadow length / density / rock texture / volcanic features -> majority vote Plant types / rock colors -> unioned into one combined list Latitude derivation Previous versions only estimated longitude. v3.3 adds a day-length-based latitude calc, it finds the longest daylight interval in the dataset, converts that duration into a sunset hour angle, and solves for latitude using solar declination for the day of year. Search area validation Both derived coordinates now get checked against a Haversine distance from a defined SEARCH_CENTER / SEARCH_RADIUS_KM, with a clean ✅ / ❌ status line and a fallback bounding box printed if the point lands outside the circle. Habitat classifier got smarter HABITAT_RULES is now a proper rule list -> each biome match is a lambda checking keyword hits across plant types, rock color, and vegetation density instead of a flat tally. Sonoran/Chihuahuan/Mojave/Colorado Plateau/Cascades/Sierra-Great Basin/High Desert/Mixed Conifer are all still in there, just with tighter matching logic. Parser resilience parse_field() handles models that randomly bold their output ( SHADOW_ANGLE: etc.) and normalizes stray ° symbols and none/n/a/null variants down to “unknown” so downstream math doesn’t choke on garbage strings. Known issue, flagging this for myself before I forget The longitude calc in main() is currently hardcoded, not pulling from the actual solar_noon_avg computed earlier in the run: day_of_year = 138 # May 18th eot = 3.65 # Verified EoT for Day 1 noon_secs = 84495 # Verified 23:28:15 UTC trajectory That’s leftover from debugging against the sample dataset, it means every run right now spits out the same longitude regardless of what images you actually feed it, which is obviously not the goal. Latitude is properly dynamic (built off intervals from the real daylight curve), longitude isn’t yet. Top priority fix for the next patch, need to swap those three constants for the real per-dataset solar_noon_avg / Julian day / EoT calc instead of the frozen debug values. Next up Wire the real solar_noon_avg (already computed in compute_solar_noon()) into the longitude block instead of the hardcoded Day 1 constants Maybe expand HABITAT_RULES matching beyond simple keyword hits, closer to weighted scoring Look into whether internvl2_5-4b is pulling its weight in the ensemble or just adding runtime for marginal disagreement value
Ships:
This is ATLAS, a Image search and geo recognition tool that uses VLMs (Visual Language Models) to scan a string of images, guess where they were taken, and supply estimated coordinates. (As said in my Dev log the coordinates may be off wildly, this is a known issue being worked on currently) The code is being worked on every week and major updates are to come, V3.3 is not the final model. I plan a V4 very soon…...
|
1793602251.9766426
|
1793688651.9766426
|
|
5457
|
A Bluey themed Hackpad by @Gopike | Stardance
|
Gopike
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A Bluey themed Hackpad by @Gopike | Stardan Title: A Bluey themed Hackpad by @Gopike | Stardance...
|
1793145230.9724221
|
1793750030.9724221
|
|
5458
|
Untitled by @pngyn | Stardance
|
pngyn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @pngyn | Stardance
|
1793235067.2179997
|
1793839867.2179997
|
|
5459
|
My first slack bot! by @spookfish | Stardance
|
spookfish
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @spookfish | Stardan Title: My first slack bot! by @spookfish | Stardance...
|
1793573286.8935394
|
1794178086.8935394
|
|
5460
|
My awesome macropad! by @leanne_nis | Stardance
|
leanne_nis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @leanne_nis | Stard Title: My awesome macropad! by @leanne_nis | Stardance...
|
1793393363.6658263
|
1793998163.6658263
|
|
5461
|
My first slack bot! by @leanne_nis | Stardance
|
leanne_nis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @leanne_nis | Starda Title: My first slack bot! by @leanne_nis | Stardance...
|
1793166648.1874158
|
1793771448.1874158
|
|
5462
|
Untitled project by @leanne_nis | Stardance
|
leanne_nis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @leanne_nis | Stardance
|
1793393598.2886987
|
1793998398.2886987
|
|
5463
|
/HEXpi/ by @moorejn4 | Stardance
|
moorejn4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: /HEXpi/ by @moorejn4 | Stardance
|
1793458381.6703637
|
1794063181.6703637
|
|
5464
|
Cosmic platforms by @Vicmin_7 | Stardance
|
Vicmin_7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cosmic platforms by @Vicmin_7 | Stardance
|
1793443768.9017642
|
1794048568.9017642
|
|
5465
|
Soldering Hot Plate by @ondy | Stardance
|
ondy
|
0
|
5.32
|
0
|
[]
|
[{"post_id": 48051, "ts": "202 [{"post_id": 48051, "ts": "2026-08-16T10:28:04Z", "hours": 3.6211, "text": "devlog 1.0 Finally we are moving from the planning part to the hardware one, the reason last devlog was 2 months ago is that hardware is really time consuming and i didnt have much time this summer. Anyway since i dont have access to a 3d printer i had to be creative: so i made the base out of wood, its a hardwood and (hopefully) shouldnt char. I know it looks uneven but trust the process, the part thats sticking out will be used for controls. The hotplate it self is lifted by 3 big blots to isolate it from the rest. I was also testing the thermistor actually works the way i intended and everything seems to be working just fine(check las devlog schematic for more info). In the next few days i will finally start soldering everything and hopefully i can get this thing working by the end of Stardance😭"}, {"post_id": 3000, "ts": "2026-06-05T22:33:53Z", "hours": 1.0542, "text": "devlog 0.1 - made complete wiring diagram from components i researched in the last devlog, had to add varistor + fuse for protection and resistor with the NTC thermistor to make voltage divider; currently waiting for components to arrive; this is just a simple wiring diagram dont look too closely at it😭🙏"}, {"post_id": 1550, "ts": "2026-06-03T17:13:31Z", "hours": 0.645, "text": "devlog 0.0 - spent some time researching specific hardware components to make sure they will work together, some of those were real hassle - next time can i start designing the wire layout –had to use this boring ah image😭🙏"}]...
|
Title: Soldering Hot Plate by @ondy | Stardance
D Title: Soldering Hot Plate by @ondy | Stardance
Devlogs:
devlog 0.0 - spent some time researching specific hardware components to make sure they will work together, some of those were real hassle - next time can i start designing the wire layout –had to use this boring ah image😭🙏
devlog 0.1 - made complete wiring diagram from components i researched in the last devlog, had to add varistor + fuse for protection and resistor with the NTC thermistor to make voltage divider; currently waiting for components to arrive; this is just a simple wiring diagram dont look too closely at it😭🙏
devlog 1.0 Finally we are moving from the planning part to the hardware one, the reason last devlog was 2 months ago is that hardware is really time consuming and i didnt have much time this summer. Anyway since i dont have access to a 3d printer i had to be creative: so i made the base out of wood, its a hardwood and (hopefully) shouldnt char. I know it looks uneven but trust the process, the part thats sticking out will be used for controls. The hotplate it self is lifted by 3 big blots to isolate it from the rest. I was also testing the thermistor actually works the way i intended and everything seems to be working just fine(check las devlog schematic for more info). In the next few days i will finally start soldering everything and hopefully i can get this thing working by the end of Stardance😭...
|
1793332191.9416063
|
1793936991.9416063
|
|
5466
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792925364.2252955
|
1793789364.2252955
|
|
5467
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792885768.4801598
|
1793749768.4801598
|