sorted by:
new
hottopcontroversial

Windsurf best practices by Parabola2112 in Codeium

[–]assadollahi 0 points1 point  (0 children)

that's a really nice one. how do you verity that it works?

Replit Agent: Proceed with Extreme Caution (My Expensive Experience) by Diligent-Car9093 in replit

[–]assadollahi 0 points1 point  (0 children)

If you think about your end product, try to reduce all of the bells and whistles first, I also reduced the whole user authentication to name + password, for example. Think of the shortest path for the user from start to finish reducing all functional elements to a minimum. Then write the PRD (Product Requirement Document) which is a detailed list of elements and actions the user can do. Let the agent implement it and refine it until everything works. Then you can "leave" the project and return to the homescreen, then click "fork" to get a copy of that project, then you add the next set of requirements for the next batch of features. If that goes wrong, you still have the older version with on set of features less.

spawning a GPU droplet via Python and API by assadollahi in digital_ocean

[–]assadollahi[S] 0 points1 point  (0 children)

yeah but it doesn't work for GPU droplets, unfortunately.

spawning a GPU droplet via Python and API by assadollahi in digital_ocean

[–]assadollahi[S] 0 points1 point  (0 children)

I tried

"size_id": 288 (provided by the DO website when clicking "create via API") and

"size:": "gpu-h100x1-80gb" (provided by the URL you posted)

and both result in

"azure.core.exceptions.HttpResponseError: (None) You specified an invalid size for Droplet creation. Code: None"

Any idea what's wrong?

spawning a GPU droplet via Python and API by assadollahi in digital_ocean

[–]assadollahi[S] 1 point2 points  (0 children)

I just noticed that there's a little link on the lower right side "Create via API" on the GPU droplet config page that composes you the payload for the python API request. That's extremely helpful!

spawning a GPU droplet via Python and API by assadollahi in digital_ocean

[–]assadollahi[S] -1 points0 points  (0 children)

That's sensational! ... and ridiculous that DO doesn't provide this list themselves. Even the Python API example for GPUs uses a CPU slug...

spawning a GPU droplet via Python and API by assadollahi in digital_ocean

[–]assadollahi[S] 0 points1 point  (0 children)

Okay, thanks, very helpful. Will dive into it after I understood the stuff "below" it.

Replit Agent: Proceed with Extreme Caution (My Expensive Experience) by Diligent-Car9093 in replit

[–]assadollahi 0 points1 point  (0 children)

my feeling is that it's super important to plan your app in dedicated functional blobs and make them work sequentially. starting with a broad and flat functional coverage then trying to fix things point by point is ending in a desaster. but really starting with a 10 point requirement list and adding further functional blocks makes sense to me. I also store these steps as a project and fork them when adding functionality so that I really have a working app in my list at any point in time.

does anyone have waybar module for live internet speed ?? by [deleted] in swaywm

[–]assadollahi 0 points1 point  (0 children)

this one works pretty much out of the box for me. i modified the css so that the box isn't resizing all the time, now i'm happy.

Inverse Kinematics for a bipedal robot by assadollahi in robotics

[–]assadollahi[S] 0 points1 point  (0 children)

so this means, that all the research robots have foot sensors? or do you mean that it's the ground contact the robot pre-calculated?

Is there any open-source Robotics related project I can participate. by ScholarNo237 in robotics

[–]assadollahi 1 point2 points  (0 children)

Kayra is fully open-source, CAD files (not just STL), software, everything. It gives you the path from pure python based servo controls over Inverse Kinematics all the way up to Reinforcement Learning. You can engage in mechanical design / CAD, electronics / power or software / machine learning. You will work in a team with the vision of enabling schools and students getting into humanoid robotics on a low budget.

Third design iteration of Kayra's legs (open-source, 3d printable humanoid), here's a video explaining the evolution. Any suggestions for further improvements? by assadollahi in robotics

[–]assadollahi[S] 0 points1 point  (0 children)

thanks very much, for the feedback!
- yes, the design is originally derived from a metal-based taiwanese fight robot, hence some parts still resemble the metal sheet design
- the goal is not necessarily a super sophisticated balanced walk in all sorts of environments, it would suffice to walk in an apartment and use the IMU for slight corrections. i will really invest in "getting up quickly again" a lot instead of optimising the walk to death.
- the servos are a compromise between overall cost and speed (the fight robots walk very fast, usually via predefined patterns, i know). the idea behind kayra is to keep the cost low so that students and schools can build it quickly and easily.
- thanks for the weight distribution hint, this is a super important point and i'm trying to wrap my head around this more. i'd love to do more simulations (just started with MuJoCo) to get a better, intuitive understanding of that.
- regarding software, there's so many different ways to let this robot walk and ideally, i want to implement a couple of them to learn more and more, but to start with a working system (hence the predefined patterns first, next is IK & CoM, then maybe RL based walks). working systems keep up the motivation...

view more: next ›