A thread where you can post good robowaifu art from humans. Previously I have been posting it in the AI art thread, but I decided to make this one to organize it. -If you know the characters, please write them down -Please don't post too many of the same characters -To save space, try to post multiple images per post Previous discussion on aesthetics >>37246 Source: Core Mita from MiSide

This is a thread to share pics & praise & approval of your (robo)waifus. Please keep it SFW, thanks Anon! warning warning warning Just b/c you've acclaimed your robowaifu ITT, doesn't mean that another anon might not also acclaim her here too. This is perfectly-acceptable! :^) >(For example: Chii is my own robowaifu-prime, but literally millions of others also love her. It's fine b/c after all, we'll be making many IRL ones. My own edition of her will still be personal & tuned just for me.) >t. Chobitsu >=== -revamp OP into a general

I am new to this ib so I am seeing how it works. Could you show me how to use this ib and its rules? Example of how to put programming text, use bold, what programs use, etc. > aldo sorry for my shit vocabulary I am learning to speak English > aldo 2 I am very excited to learn and help when I understand the subject well.

Welcome all Nandroids fans to the Emmy thread, for discussing and posting about EtR. Off-topic posts and personal attacks will be deleted. --- Also, be sure to check out Emmy-Pilled's project thread! (>>25306) Important Community Links: Boorus, etc.: https://nandroid.booru.org/index.php Google Docs: https://docs.google.com/spreadsheets/d/1mXuNh9ESedCiDZclVuz9uiL7nTNk3U9SgCE_CRHi3Us/htmlview# Webtoons: https://m.webtoons.com/en/canvas/emmy-the-robot/list?title_no=402201 > previous threads: >>27481 >>26629 >>30919

>Welcome to /DMG/ DIY Motor Generation! This is the place to discuss DIY motor designs, showcase your creations, and refine your ideas on motor tech. This thread is a requested offshoot of the "Actuators For Waifu Movement" thread to focus specifically on DIY motors. We will focus solely on DC motors. I will start the thread off by talking about the types of motors and terms associated with electric motors to keep a good reference to look back on. It should be noted that most motors are Radial Flux and not Axial Flux. What is flux? Magnetic flux is a measure of the total magnetic field which passes through a surface. Radial and Axial describes the orientation of the magnetic flux. Radial Flux Motor > A radial flux motor is like a cylinder spinning inside another cylinder. The magnetic flux flows perpendicular to the axis of rotation, meaning it moves from the stator to the rotor radially outward or inward. Traditional cylindrical motors (like most brushed and brushless DC motors, induction and steppers) are radial flux motors. Rotor and stator are concentric, with the stator surrounding the rotor. Pros: Well-established, widely used, good for high-speed applications. Cons: Can be bulkier and less power-dense compared to axial flux motors. Axial Flux Motor >An axial flux motor is like two discs spinning parallel to each other. The magnetic flux flows parallel to the axis of rotation, meaning it moves along the shaft’s length rather than outward. These motors have a flat, disc-like design where the stator and rotor are stacked on top of each other rather than inside one another. Pros: More compact, higher torque density, and better cooling due to a larger surface area. Cons: More complex to manufacture, higher initial costs. Kinds of Motors: >Brushed DC Motor: Uses brushes and a commutator for current switching. Simple, inexpensive, but requires maintenance due to brush wear. >Brushless DC Motor (BLDC): Uses electronic commutation instead of brushes. More efficient, longer lifespan, commonly used in drones and electric vehicles. >Coreless DC Motor: Lighter and more efficient than traditional brushed motors, often used in small precision devices like robotics and medical instruments. >Stepper Motor: Moves in discrete steps, allowing precise control. Used in CNC machines, 3D printers, and robotics. >Servo Motor: A DC motor with feedback control for precise positioning. Used in robotics, RC vehicles, and automation. >Single-Phase Induction Motor: Used in household appliances like fans and washing machines. >Three-Phase Induction Motor: Used in industrial applications due to high efficiency and reliability.

Vagoo. I can't speak for anyone but myself but I'd like to get.. intimate with my fembot. I'd like to know what my options are for her robopussy. I was thinking something like a flesh light with sensors that triggers voice and arm action. I'm using Myrobotlab is Anyone familiar with it?

Robosex general I guess

Would you walk around with your waifu? Would you hold her in public? Would you shamelessly have her custody with you to conventions? Would you take her on dates? This thread is for discussing how you'd interact with your waifu outside of the home. >=== -tmp locked to dissuade derailling

For the past year, I have been working on my own robowaifu design. Her name is Galatea. She's currently in the v3 Series. The design is very easy to build with the instructions and files, and is relatively very cheap, around $400 to make. She's also very customizable, you can choose the color, dress, hair, and even AI. I intend this to be the Model T of humanoid robots and robotic companions, while it is not the most complex, it is easy to mass produce and cheap. As of this post, her latest version is v3.0.2 Previous thread: https://trashchan.xyz/robowaifu/thread/74.html

The original thread can be found here: https://trashchan.xyz/robowaifu/thread/595.html --- Welcome to the Lemon Cookie thread, The goal of Lemon Cookie is to create a framework where a synthetic "mind and soul" can emerge through a "LLM as cognitive architecture" approach. This thread exists to collect feedback, ask for help & to document my progress. First I am going to try to give a high level overview of how this cognitive architecture is envisioned and the ideas behind it. I have spent time looking at cognitive architecture work, in the field there is now a consensus on how the mind works at a high level. An important mechanism is a "whiteboard", basically a global temporary memory that all the other systems read in and out of. Then there is different long-term memory systems that react to and add content to the whiteboard. Along with memory pattern matcher(s)/rules work on the content of the whiteboard. A key thing to consider is the difference in philosophy that cognitive architecture projects have, the intelligence is considered to emerge from the entire system. Compare this to LLM agent work where it's considered the intelligence is the LLM. My feelings on the general LLM space are conflicted, I am both amazed and really disappointed. LLMs possess an incredible level of flexibility, world knowledge and coherence. But everything outside of the model is stagnant. It's endless API wrappers & redundant frameworks all slight permutations on RAG & basic tool calling. I will believe that LLMs are misused as chatbots, simply put their pattern matching and associative power is constrained by chat format and shallow tooling. In the Lemon Cookie Cognitive Architecture so far here are the important aspects: 1. Memory is difficult. I do not think there is a singular data structure or method that is able to handle it all, several distinct types of memory will be needed. So far I plan for a PathRAG like system and a "Triadic Memory" inspired system for external associations (this is missing in most LLM solutions). 2. LLM as Kernel, The LLM's context window is the Whiteboard and has a REPL like mechanism. It holds structured data and logic in scripting-like format so it's both LLM & Human readable while staying easy to parse & allows for expressive structured data. The LLM's role will be to decompose data and make patterns and associations explicit as executable statements. 3. The language has to be LLM/CogArch-centric. There is a thousand ""agents"" that give LLMs a python interpreter as a tool. The two need to be more tightly coupled. Scripted behavior via pattern matching, The whiteboard is a bag of objects, this allows for programmable pattern matching (think functional programming like Haskell). It's also important to allow the LLM to observe code execution and to be able to modify state and execution flow. Data in languages have scoping rules, so should LLM context. Etc... I will go into more depth about the language in another post. 4. Another important system is the "GSR" Generative Sparse Representation and it will be a first class language & runtime type, This also needs its own post. But in general I am inspired by two things, "Generative FrameNet" paper where an LLM & an embedding model is used to automatically construct new FrameNet frames. The second source is "Numenta's SDRs"/"Sparse distributed memory" this representation has a lot of useful properties for memory (Please watch the videos under the "What the hell is an SDR?" segment in my links list for an easy introduction.) I think SDR unions & SDR noise tolerance will be especially useful. 5. A custom model, For all of the above to work well, a model will need to be fine tuned with special behaviors. I do want input on this. Baking facts & behaviors into LLM weights is costly, creating bloated models that are hard to run or train (why memorize all the capitals?), while letting authors gatekeep truth and impose "safety" detached from context. Blocking role-play "violence" or intimacy isn't protection: it's authors hijacking your AI companion to preach at you. Externalizing behaviors via whiteboard pattern matching shifts control: stabbing you in-game can be funny, but a robot wielding a knife isn't. Maybe you want intimacy privately, but don't want your AI flirting back at your friends. When put together I think this will be able to host a kind of synthetic "soul", In a living being what we call a personality is the accumulated associations, learned behaviors, beliefs and quirks molded by a unique set of experiences. I hope this will be true for this system too.

>Why organize IRL? This community is great and many individuals are already making progress on their prototypes. However this endeavor is not a one man job and organizing IRL would give better opportunities for collaboration and skill sharing/development. >Where should we organize? I propose we organize within a seven hour radius of Chicago. This would include the major cities of Milwaukee WI, St Louis MO, Detroit MI, Indianapolis IN, Louisville KY, Cleveland OH, Cincinnati OH, Columbus OH, Pittsburgh PA, Nashville TN, and Minneapolis MN. There are plenty of opportunities for jobs and universities in these cities. In particular Chicago has a booming tech industry with Google even moving their HQ to the city and the electronics manufacturing and biotech sectors are pretty good too and Detroit MI has pretty good robotics industry although it might not be the best place to live. Another wonderful thing about this area is that most of these homes have basements that could be turned into workshops. >How would this all be organized I propose a fraternity system. A fraternity would help build community and give us a vehicle to recruit others from STEM and skilled trades (machinists especially) The organization could also host a scholarship to help us build talent. Anons with enough money for a down payment could buy homes in the area and rent to below market rate to anons moving in. Different homes could specialize on different projects and collaborate and share equipment and skills with others nearby. What do you think /robowaifu/?