New video of Sophie is now up: https://www.youtube.com/watch?v=XOGrdHn7wBU Finally got her head working in a reproducible manner. I had completely broken about seven of her previous micro-servos. But the burnt-out ones weren't the big problem - I just connect suspect servos my Arduino UNO and if my control servo can run the 'Sweep' sketch but the suspect servo cannot, I know it's dead and in the bin it goes. However, one servo was damaged but still working - except it caused some kind of feedback that made all other micro servos connected to the same circuit go haywire - even brand new ones. Luckily the faulty servo in question was old and had spraypaint on it, so I could tell it apart from the others. But that was very confusing - at first I thought it might be related to the small magnets that hold her faceplate on, but this is not the case. Rogue servos are definitely something to watch out for in future. Anyway, now that I have measurable, standardised voltage going into all of the micro servos, I'd like to upgrade her neck again. She can actually shake her head (but not in the above video as it is addressed straight-to-camera), but she still cannot nod her head as it weighs too much and the neck servo overheats rapidly. Heads are relatively heavy things (especially with long hair). The breakthrough with Sophie has been splitting her up into separate subsystems and separate circuits, then focusing on only ONE subsystem/circuit - in my case her head. For a beginner like me, it was just too confusing and labour intensive to attempt programming her head, speech, neck, arms and hands all simultaneously. When errors occured I was having a real hard time pinning down which motors were affected, how badly they were affected and why. Having to tear down one large, complex system is waaaay harder than troubleshooting something far smaller. So focusing only on her head solved this problem.

Question: How are we going to solve keeping all the motors, pumps, computers, sensors, and other heat-producing gizmos inside a real robowaifu cooled off anons?

Robowaifus will need power to run, and since they will be mobile this means a mobile power system too. ITT post info on batteries and other mobility capable power systems. --- > related-thread : (>>5080) >=== -add crosslink

over the last year I´ve worked on making a full scale nanny android (or nandroid for short, her name is "Emmy") over the last 10 months and decided to post the progress (this is a SFW project)

I think we need to figure out how to fit a womb onto a waifubot. Where's the fun in having sex if you can't procreate?

Repost from a thread on /b/;
>"If you're like me and want to fuck a qt battlebot and get her pregnant, the best place to put an artificial womb is where a normal womb would be on a normal girl. The metal exterior could simply be a bunch of metal plates that unfold to allow space for the womb pod inside. The baby is probably safest inside the battlebot, and if she has good calibration then there shouldn't be problems with her falling and hurting the baby. After giving birth the metal plates could automatically fold back up again, shrinking the womb pod inside so she is combat effective again."

Well /robowaifu/? Feasible?

Your project is really disgusting >=== Notice #2: It's been a while since I locked this thread, and hopefully the evil and hateful spirit that was dominating some anons on the board has gone elsewhere. Accordingly I'll go ahead and unlock the thread again provisionally as per the conditions here: >>12557 Let's keep it rational OK? We're men here, not mere animals. Everyone stay focused on the prize we're all going for, and let's not get distracted. This thread has plenty of good advice in it. Mine those gems, and discard the rest. Notice:

I realize it's a bit grandiose (though probably no more than the whole idea of creating a irl robowaifu in the first place) but I want to begin thinking about how to create a working robowaifu 'brain', and how to create a special operating system to run on her so she will have the best chance of remaining an open, safe & secure platform. OS Language Choice C is by far the single largest source of security holes in software history, so it's out more or less automatically by default. I'm sure that causes many C developers to sneer at the very thought of a non-C-based operating system, but the unavoidable cost of fixing the large numbers of bugs and security holes that are inevitable for a large C project is simply more than can be borne by a small team. There is much else to do besides writing code here, and C hooks can be generated wherever deemed necessary as well. C++ is the best candidate for me personally, since it's the language I know best (I also know C too). It's also basically as low level as C but with far better abstractions and much better type-checking. And just like C, you can inline Assembler code wherever needed in C++. Although poorly-written C++ can be as bad as C code in terms of safety due to the necessity of it being compatible with C, it also has many facilities to not go there for the sane coder who adheres to simple, tried-and-true guidelines. There is also a good C++ project already ongoing that could be used for a clustered unikernel OS approach for speed and safety. This approach could save drastic amounts of time for many reasons, not the least of which is tightly constrained debugging. Every 'process' is literally it's own single-threaded kernel, and mountains of old-style cruft (and thinking) typical with OS development simply vanishes. FORTRAN is a very well-established language for the sciences, but a) there aren't a lot of FORTRAN coders, and b) it's probably not the greatest at being a general-purpose language anyway. I'm sure it could be made to run robotics hardware, but would probably be a challenge to turn into an OS. There are plenty of dujour SJW & coffee languages out there, but quite apart from the rampant faggotry & SJWtardism plainly evident in most of their communities, none of them have the kind of industrial experience and pure backbone that C, C++, or FORTRAN have. D and Ada are special cases and possibly bear due consideration in some year's time, but for now C++ is the obvious choice to me for a Robowaifu OS foundation, Python probably being the best scripting language for it. (1 of 2) >=== -fmt cleanup

Hi /robowaifu/, I've stumbled here after doing some research into creating a robowaifu stock portfolio. My thinking was I am never going to be able to build a robowaifu from scratch but will buy one when they become available. I want to contribute somehow to their development so I am creating a stock portfolio where I buy only stocks that I believe are working towards robo waifus either literally or by just advancing the tech that would be needed. GPUs, Semiconductors, AI, VR, Robotics, Batterys, Silicon. My current portfolio: >NVDA - Nvidia - GPUs used in AI / Machine Learning >AMD >TSM - TSMC. The world's biggest and most advance semiconductor foundry. >INTC - Intel >ABB - ABB Ltd - Swedish-Swiss company in automation technology, robotics, heavy electrical equipment. >IRBT - iRobot - Home Robotics >MSFT - Microsoft - They are investing heavy into AI and have one of the largest AI chat bots "Xiaoice". >TER - Teradyne >IBM Other suggestions: >TSLA - Tesla - Humanoid robotics

AI Natural Language Processing general thread

>"Natural language processing is a field of computer science, artificial intelligence, and computational linguistics concerned with the interactions between computers and human (natural) languages."
en.wikipedia.org/wiki/Natural_language_processing
https://archive.is/OX9IF

>Computing Machinery and Intelligence
en.wikipedia.org/wiki/Computing_Machinery_and_Intelligence
https://archive.is/pUaq4

m.mind.oxfordjournals.org/content/LIX/236/433.full.pdf

I hope to have useful links and images in the future, this is just a quickly thrown together glorified character sheet maker at this point. Ok so you can program, but HOW to make her thoughts work? At least on a creative level. I don't have much to contribute other than my rather obsessive what-ifs, I hope this is useful somehow. A few questions you might want to ask yourself before typing up some kind of bio or writing down conversations and quotes you imagine she would say are... 1. How close to the canon do I want to be? 2. How much canon is there? 3. How would I want to make her mine vs someone else's interpretation of the same character? Take note of those answers, if your memory sucks record them in a method you are comfortable with. I think typing might be faster for most. And you might want to revisit what you wrote here sometimes when making certain personality design choices. Use your answers here as a basic guide. For the most part, just go through writer's sites for character questionnaires. And before you omit a question, think of how could you use the basics of what it is asking to build your waifu's personality? For example, if a question rubs you off the wrong way politically, still use that question. But answer in your own way or even reword the question. Some of these types of questions are supposed to make you think hard about what shaped your character's dislikes, which is still important to what makes a person themselves. You may need to revisit some of these or even omit certain ones entirely. But try to figure out how to get that info in somehow later. This process can take a long time and be frustrating, but I think it has a place in the waifubot creation experience. Also, try think how would your waifu react if the story went differently at some point. This can get really dramatic real easy, but it doesn't have to. Just start with simple things like what would she say if asked to tell a joke? What does she find funny? What does she find cringey? Things like that, and don't be afraid to make what they call a 'brain dump'. Pretty much just type with minimal breaks and type everything that comes to your mind about the topic. You might get some useful info amongst the 'why am I doing this?' 'I need to take a shit' quotes. Also just use some of those story prompts. Also, try to use the more realistic day to day ones, like things that could happen in real life. Less exciting but pretty sure you aren't going on fantasy journeys with her IRL. Using these types of prompts will give her more to say on mundane everyday things, vs Skyrim politics. (But that could be fun sometimes)