Attention drawfags and writefags! Your skills will be needed. The task of building and designing a robowaifu is a herculean quest. As great as this community is, /robowaifu/ simply does not have the manpower to real our goal of DIY robowaifus. Luckily for us there are several communities on the internet that we could find new recruits or allies to help us build our waifus: MGTOW - These guys know all about the legal pitfalls of marriage and the dangers of feminism. There is already a lot of talk about sex robots in MGTOW communities. It shouldn't be a hard sell to get them to come here. Incels - Guys that can't get laid. The opportunity for love and companionship should be enough to bring some of these guys over. We need to be careful when recruiting from some of their communities. We don't want to attract negative attention. Monster girls/furry/mlp fandoms - The only way these guys are going to be able to have their harpy/elf/goblin/anthro/pony/whatever gf is with a robowaifu. They have an interest in seeing us succeed. Again we need to be careful here not to attract the wrong kind of people that will bring us the wrong kind of attention. Male STEM students - Generally these guys aren't going to get laid until after they have established themselves. A robowaifu could really help them. This may be a harder sell because many of them have been brainwashed in university, but they have skills that we could really use. Transhumanists/biohackers - Many of the technologies involved in building a robowaifu could be used in transhumanist or biohacking applications such as building an avatar. They may have some interest in helping us out. We will need to be careful which transhumanist communities we go after as many of them are full of feminism, tumblr tier sexualities and genders, and SJW's. Cyberpunks and technophiles - These guys (and they are usually guys) are all around into technology and may just enjoy working on the kinds of projects we need to do. They are often into programming and AI.

If we were to be realistic about creating robot wives capable of forming seemingly genuine human actions such as fine motor skills, emotion, and rational thought while resembling a human with a few non-human features, i think the best way to approach this is to embrace the usage of soft robotics, computational parallelism, photonic integrated circuits, and low power analog systems. Computational Parallelism: Divide and conquer algorithms are often used to solve computational problems by dividing tasks up into smaller problems, solving them individually, and combining the results together to form one big output. This generates faster results and is already possible to achieve with conventional hardware, but most conventional hardware is limited to the amount of cores needed to effectively solve problems this way on a larger scale. It's a big hindrance to the speed of operations like this, so we'll need something more powerful. There are ASICs available on the market that were engineered to be used this way. However, they're too expensive, which drives me to the possibility of using Photonic integrated circuits. Photonic ICs: Photonic IC are exactly as the name implies: Integrated Circuits that make the use of Photons to computational operations as opposed to electrons. Manufacturing Photonic ICs is relatively more cost effective than if you were to try manufacturing conventional silicon ICs. Another huge advantage is that we can solve computational problems much faster with less power using photons without generating heat the same way conventional ICs do with electrons. The biggest caveat here is that this is still being researched and that special tooling would need to be made for us to build these in house. Soft Robotics: Soft robotics are the best option for creating human-like bodies for robots. Even better is that they often don't require too much power to actuate joints or muscles. Most soft materials use for soft robots are cost effective enough to be made with commonly found materials. I personally think making use of alginate hydrogel would be a smart idea for use in robots waifus because it is hydrophilic, and anti microbial. It is commonly used in medical applications such as wound dressings and drug delivery systems. It is also non-toxic which makes it a perfect candidate for use in robot waifus. I'd also entertain the idea of using other soft materials in conjunction with it for better results. Primarily, it can be used in forming fat-like deposits, skin layers, and artificial internal organs for robot waifus. I think it may also be possible for us to create internal lubrication systems for it due to the fact that it is primarily water based. Low Power Analog Systems: Low power analog systems are vague in definition, but the general idea here is that we can use things such as fiber optic wires, digital-to-analog converter chips, and digitizers to create a type of artificial nervous system that communicates with the rest of the hardware running signal transmitters over echo state networks. It's hard for me to accurately describe my visualization of this, but by now, I'm sure you get the point already. The only problem left to solve is power. How to we obtain it, and how much can we use? I don't know, but if we take the low power-high tech approach, it probably wouldn't become too much of an issue. I think that maybe the best way would be to use electrochemcial energy in some type of internal fuel cell to generate power. All of the systems described above would require less power than if we tried to use servos and silicon chips. I's also say that maybe we could take more inspiration from nature to create bio-mimicking features that we would find desirable. A lot of this is speculation that i got from dipping my toes into various topics and picking out what i think could be useful to finally end the hypergamy going on in the west. This is largely a cultural issue that is mulifaceted in every way and our efforts could be in vain if the feminists and roastoids find a way to outlaw open source tech. Not only should we be focusing on building robot wives to flips the tables in the dating and sexual market, but to also consider political and economic alternatives that absolutely strip and decentralize power from the hands of the elite. I personally think agorism is the way to go but that is a another topic for another time. Let me know what you guys think. Am i an idiot, or am i onto something?

Discussing the potential benefits of creating monster girls via robotics instead of 1 to 1 replicas of humans and what parts can be substituted to get them in production as soon as possible. Firstly is the fact that many of the animal parts that could be substituted for human one are much simpler to work with than the human appendages, which have a ton of bones and complex joints in the hands and feet, My primary example of this is bird/harpy species (image 1), which have relatively simple structures and much less complexity in the hands and feet. For example, the wings of the bird species typically only have around three or four joints total, compared to the twenty-seven in the human hand, while the legs typically only have two or three, compared to the thirty-three in the human foot. As you can guess, having to work with a tenth of the bones and joints and opposable thumbs and all that shit makes things incredibly easier to work with. And while I used bird species as an example, the same argument could be put forward for MG species with paws and other more simplistic appendages, such as Bogey (image 2) and insect hybrids (image 3). Secondly is intentionally making it appear to not be human in order to circumvent the uncanny valley. It's incredibly difficult to make completely convincing human movement, and one of the simplest ways around that is just to suspend the need for it entirely. We as humans are incredibly sensitive to the uncanny valley of our own species, even something as benign as a prosthetic limb can trigger it, but if we were to create something that we don't expect to move in such a way, it's theoretically entirely possible to just not have to deal with it (for the extremities part of it, anyways), leaving more time to focus on other aspects, such as the face. On the topic of face, so too could slight things be substituted there (again for instance, insect girls), in order to draw attention away from the uncanny valley until technology is advanced enough that said uncanny valley can be eliminated entirely. These possibilities, while certainly not to the taste of every anon, could be used as a way to accelerate production to the point that it picks up investors and begins to breed competition and innovation among people with wayyyyyyy more money and manpower than us, which I believe should be the endgoal for this board as a whole. . Any ideas or input is sincerely appreciated.

Post your prototypes and failures. We fail until we win. From now on with even more madness, while the prototypes are starting to look cute and have extras. Don't forget looking through the old threads here >>418 and here >>18800 to understand how we got to where we are now.

Decided it may be best to place my 3D digital modelling efforts in a separate thread to my work on 'Elfdroid Sophie'. I think this thread will still belong under "Personal Projects". At the moment the 3D modelling begins over on her thread: >>11644 >>11657 I'm using some source material from Masamune Shirow's 1987 OVA "Black Magic - M66" (which itself was based off his 1983 manga). However, as a child of the late eighties/early nineties, I loved 'Transformers', and I was also a big fan of the 'Heavy Gear' series (similar to MechWarrior), and Armored Core. So I often get the urge to create battle-ready robowaifus, but I can only create them virtually. Because obviously I cannot get hold of machine-guns, explosives, tank cannons, and rocket launchers IRL. Good thing, too, since if I were given access to live ammunition I would almost certainly blow myself into a flying streamer of giblets. But I digress. This thread may also be a good place for any equally deranged anons who wish to post images of military-grade robowaifus, either found online or their own creations? --- >lock cf. (>>30234)

Here we have Maslow's hiearchy of needs. A psychological theory that basically breaks down what a man needs and what he can seek out in life. This seems like a good framework to identify what niche your robowaifu can address in her function, and how exactly to accomplish that. I think the third tier up is what most of us seek from a robowaifu. No matter how inert your robowaifu is in function, even motionless plastic can give you a sense of connection if you project a personality onto it. What do you think? Does Maslow's hierarchy of needs as a theory relate to you and your projects? Is there anything to this at all?

Welcome all Nandroids fans to the Emmy thread, for discussing and posting about EtR. Please refrain from posting off-topic or non-Nandroid related things. --- Also, be sure to check out Emmy-Pilled's project thread! (>>25306) >=== -minor edit -add project crosslink

(Original thread >>406) Kiwi back from the dead with a thread for the discussion of actuators that move your waifu! Part Two! Let's start with a quick refresher! 1. DC motors, these use a rotating magnetic field created through commutation to rotate a rotor! They're one of the cheapest options and are 30 to 70 percent efficient usually. The bigger they are, the more efficient they tend to be. 2. Brushless motors, these use a controller to induce a rotating magnetic field by turning electromagnets on and off in a sequence. They trend 60 to 95 percent efficiency 3. AC motors, Though there are many different type, they function similarly to brushless motors, they simply rely on the AC electricity to turn their electromagnets on and off to generate their field. Anywhere from 15 to 95 percent efficiency. 4. Stepper motors, brushless motors with ferrous teeth to focus magnetic flux. This allows for incredible control at the cost of greater mass and lower torque at higher speeds. Usually 50 to 80 percent efficient but, this depends on control algorithm/speed/and quality of the stepper. 5. Coiled Nylon Actuators! These things have an efficiency rating so low it's best to just say they aren't efficient. What they are though is dirt cheap and easy as heck to make! Don't even think about them, I did and it was awful. 6. Hydraulics! These rely on the distribution of pressure in a working liquid to move things like pistons. Though popular in large scale industry, their ability to be used in waifu's has yet to be proven. (Boston Dynamics Atlas runs on hydraulics but, it's a power guzzler and heavy) 7. Pneumatics, hydraulics lighter sister! This time the fluid is air! This has the advantage in weight. They aren't capable of the same power loads hydraulics are but, who wants their waifu to bench press a car? 8. Wax motors, hydraulic systems where the working fluid is expanding melted parafin wax! Cheap, low power, efficient, and produce incredible torque! Too bad they're slow and hard to control. 9. Explosion! Yes, you can move things through explosions! Gas engines work through explosions! Artificial muscles can be made by exploding a hydrogen and oxygen mixture in a piston, then using hydrolysis to turn the water back into hydrogen and oxygen. None of this is efficient or practical but, it's vital we keep our minds open. Though there are more actuators, most are derivatives or use these examples to work. Things like pulleys need an actuator to move them. Now, let's share, learn, and get our waifu moving! >--- < add'l, related links from Anon:

So I'm thinking about design and realize some mistakes I made. There is likely no better short cut to advancing design than these fundamental principles as stated by Elon Musk. 1. Make The Requirements Less Dumb “Step one: Make the requirements less dumb. The requirements are definitely dumb; it does not matter who gave them to you. It’s particularly dangerous when they come from an intelligent person, as you may not question them enough. Everyone’s wrong. No matter who you are, everyone is wrong some of the time. All designs are wrong, it’s just a matter of how wrong,” explains Musk. 2. Try And Delete Part Of The Process “Step two: try very hard to delete the part or process. If parts are not being added back into the design at least 10% of the time, [it means that] not enough parts are being deleted. The bias tends to be very strongly toward ‘let’s add this part or process step in case we need it’. Additionally, each required part and process must come from a name, not a department, as a department cannot be asked why a requirement exists, but a person can,” says Musk. 3. Simplify Or Optimize “Step three: simplify and optimize the design. This is the most common error of a smart engineer — to optimize something that should simply not exist,” according to Musk. He, himself, has been a victim of implementing these steps out of order. He refers to a “mental straightjacket” that happens in traditional schools where you always have to answer the question regardless of whether the premise makes any sense at all. 4. Accelerate Cycle Time “Step four: accelerate cycle time. You’re moving too slowly, go faster! But don’t go faster until you’ve worked on the other three things first,” explains Musk. Here he uses another example of how these steps should occur in order. During a wrongheaded process you should simply stop, not accelerate. He says, “If you’re digging your grave, don’t dig it faster.”

The biggest hurdle to making quick progress in AI is the lack of compute to train our own original models, yet there are millions of gamers with GPUs sitting around barely getting used, potentially an order of magnitude more compute than Google and Amazon combined. I've figured out a way though we can connect hundreds of computers together to train AI models by using gradient accumulation. How it works is by doing several training steps and accumulating the loss of each step, then dividing by the amount of accumulation steps taken before the optimizer step. If you have a batch size of 4 and do 256 training steps before an optimizer step, it's like training with a batch size of 1024. The larger the batch size and gradient accumulation steps are, the faster the model converges and the higher final accuracy it achieves. It's the most effective way to use a limited computing budget: https://www.youtube.com/watch?v=YX8LLYdQ-cA These training steps don't need to be calculated by a single computer but can be distributed across a network. A decent amount of bandwidth will be required to send the gradients each optimizer step and the training data. Deep gradient compression achieves a gradient compression ratio from 270x to 600x without losing accuracy, but it's still going to be using about 0.5 MB download and upload to train something like GPT2-medium each optimizer step, or about 4-6 mbps on a Tesla T4. However, we can reduce this bandwidth by doing several training steps before contributing gradients to the server. Taking 25 would reduce it to about 0.2 mbps. Both slow and fast computers can contribute so long as they have the memory to hold the model. A slower computer might only send one training step whereas a fast one might contribute ten to the accumulated gradient. Some research needs to be done if a variable accumulation step size impacts training, but it could be adjusted as people join and leave the network. All that's needed to do this is a VPS. Contributors wanting anonymity can use proxies or TOR, but project owners will need to use VPNs with sufficient bandwidth and dedicated IPs if they wish that much anonymity. The VPS doesn't need an expensive GPU rental either. The fastest computer in the group could be chosen to calculate the optimizer steps. The server would just need to collect the gradients, decompress them, add them together, compress again and send the accumulated gradient to the computer calculating the optimizer step. Or if the optimizing computer has sufficient bandwidth, it could download all the compressed gradients from the server and calculate the accumulated gradient itself. My internet has 200 mbps download so it could potentially handle up to 1000 computers by keeping the bandwidth to 0.2 mbps. Attacks on the network could be mitigated by analyzing the gradients, discarding nonsensical ones and banning clients that send junk, or possibly by using PGP keys to create a pseudo-anonymous web of trust. Libraries for distributed training implementing DGC already exist, although not as advanced as I'm envisioning yet: https://github.com/synxlin/deep-gradient-compression I think this will also be a good way to get more people involved. Most people don't know enough about AI or robotics enough to help but if they can contribute their GPU to someone's robowaifu AI they like and watch her improve each day they will feel good about it and get more involved. At scale though some care will need to be taken that people don't agree to run dangerous code on their computers, either through a library that constructs the models from instructions or something else. And where the gradients are calculated does not matter. They could come from all kinds of hardware, platforms and software like PyTorch, Tensorflow or mlpack.