A community OpenClaw memory plugin that wires OpenClaw sessions into the MemU engine

gametiny --------------------------------------------------------------------------- I was inspired by the mini game consoles based on the energy efficieng 3V Attiny85 MCU that can run for hours on a CR2032 3V button battery. Attiny Joypad created by Daniel Champagne.. (Electro L.I.B) 2018 GPL V3 is a great platform with the 4 way directional buttons/joystick and another fire button to write games on. The other platform called Attiny Arcade created by webbloggles is also a great mini game console with the simplicity of having only two buttons. Both platforms inspired me to create something taking the best from both worlds. This game board I called gametiny is based on the Attiny Joypad created by Daniel Champagne. I modified it to add a header for USBasp programmer that doubles up as a socket for the OLED plus adding a switch to pull PB3 to ground. This allows the interrupt codes to work for both PB1 and PB3, making it easier to convert games written for the Attiny arcade to work on Attiny joypad. Schematics and games converted to work on gametiny can be found here https://github.com/cheungbx/gametiny Links Original Tiny Joypad design by Daniel Champagne. https://sites.google.com/view/arduino-collectionLinks Original Attiny Arcade keychain kit http://webboggles.com/attiny85-game-kit-assembly-instructions/ I converted these games for the AttinyArcade (originally created by Andy Jackson - Twitter: @andyhighnumber) to work for gametiny. https://github.com/andyhighnumber/Attiny-Arduino-Games Arduino board driver for attiny85 https://raw.githubusercontent.com/damellis/attiny/ide-1.6.x-boards-manager/package_damellis_attiny_index.json schematics and source codes in https://github.com/cheungbx/gametiny I purchased the parts from these taobao links. 128x64 i2c mono OLED - https://item.taobao.com/item.htm?spm=a1z09.2.0.0.52cd2e8dEH1bEe&id=553116768996&_u=i106a08oda4a USBasp programmer https://detail.tmall.com/item.htm?id=573399213944&spm=a1z09.2.0.0.67002e8dEmFVw9&_u=i106a08o8c9c attiny 85 DIP8 chips https://item.taobao.com/item.htm?spm=a1z09.2.0.0.2e622e8dl6mZNt&id=35831130850&_u=i106a08o4917 buttons and other misc. items - https://item.taobao.com/item.htm?spm=a1z09.2.0.0.52cd2e8dEH1bEe&id=552220368876&_u=i106a08oc0d5 Transistors from HK Shumshuipo - Ip Liu Street electronic shops. *** WARNING *** Inserting the battery or the OLED or the header in the wrong direction may cause permanent damage to the ATTiny85 chip and/or the OLED, and/or the USB port of your computer Beware of different pin layout of OLED from different manfacturers that may swap the positions of VCC and GND, and SCL and SDA. ATtiny85 boards with USB ports are not suitable for this project. The bootloader on such boards uses up almost half of the program memory space with insufficient space for game program. Unless you know how to solder surface mount components (SMD), buy the raw/bare dual in line ATtin85 for this project. and use an IC socket. Programming the ATtiny85 is a bit tricky. Not every Arduino UNO, NANO board will work. Clone Nano/Uno from China may not work. USBasp programmer is preferred. You need to create the cable to connect the Tiny Boy header to the USBasp header as shown in the schematics at the bottom right *** TIPS *** Game buttons are all 6x6 tap-tic buttons. The up/down/left/right buttons can be replaced by a 5-direction mini joystick-like integrated button. Use small PC speakers or buzzers without an internal beeper circuit as sound output, Test out the circuit on a breadboard first before soldering on a circuit board. Use laminated (isolated) wire for connection between points. Use the small soldering tip and apply flux.

Sublinear-space ZKP system in Rust: a streaming prover that uses only O(√T) memory to commit wires/Z/Q via KZG (BN254) with blocked IFFT and aggregate-only Fiat–Shamir. Supports eval/coeff bases, deterministic dev SRS, and pairing checks. Includes CLI prover/verifier and tests.

VeriPy is a python based Verilog/Systemverilog automation tool. It automates ports/wire/reg/logic declarations, sub-module Instantiation, embedded python, IO spec flow, memory wrapper generation, various code generation plugins and configurable code generation. The VeriPy Wiki has more the detailed documentation.

High performance memory efficient serialization library with direct wire access

Shape Memory Alloy Resistance Tracking library for Arduino, which currently uses DPM8600 series power converter to activate NiTi-based wires

Kinetics model for Shape Memory Alloy wire based continuum robots

OneWire lets you access 1-wire devices made by Maxim/Dallas, such as temperature sensors and ibutton secure memory. Library for arduino

Persistent memory plugin for AI coding agents. Captures decisions, corrections, and patterns across sessions.

CC-FlexiMIDI-V1R0-03.09.2009 and CC-FlexiMIDI-V1R1-03.09.2009 : Updated to CC-FlexiMIDI-V1R2-12.29.2019 on December 29, 2019 ================================ BACKGROUND: CC-FlexiMIDI-V1R0-03.09.2009 - A Hardware M.I.D.I. Interface Program Pak Cartridge for the Tandy Radio Shack TRS-80 Color Computer 1, 2 and 3, including clones and compatibles (Tano Dragon 64, Dragon Data D32, D64 and D200, Tandy Data Products TDP-100, etcetera) by "Little" John Eric Turner and his father "Big" John Robert (J.R.) Turner. Copyright 09 March 2009. Originally released as Open-Source Hardware on March 9, 2009. Subsequently released under a Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) License on 21 May 2019. ENJOY! Note that the original design is crap, however, a debugged version is forthcoming from "Uncle" Robert "The R.A.T." Allen Turner. CC-FlexiMIDI-V1R0-03.09.2009 has been updated to CC-FlexiMIDI-V1R1-03.09.2009 by R.A. Turner on May 21, 2019, just over ten years after the initial release of Version 1, Revision 0. Version 1, Revision 1 is Copyright (C) 2019 by the above mentioned parties and is released under a Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) License on 21 May 2019. =============================== DESCRIPTION: This project is an updated version of the "CC-FlexiMIDI-V1R0-03.09.2009", a hardware MIDI Interface Card for the Tandy Radio Shack TRS-80 Color Computer 1,2 and 3, Dragon Data Dragon D32, D64 and D200, Tandy Data Products TDP-100, Tano Dragon 64 and other clones and compatibles. The original "CC-FlexiMIDI-V1R0-03.09.2009" was designed by my nephew, "Little John", on March 8-9, 2009 as a learning excercise. He was teaching himself to use E.A.G.L.E. in order to design products for the TRS-80 Color Computer line of computers, with the help of his father, my brother, "Big John" or "J.R." as he is known to me. The "CC-FlexiMIDI-V1R0-03.09.2009" was among his very first (learning the art of circuit design) works. It is a terrible design only because he knew nothing about circuit design at the time and it does not appear that his father, "Big John" (J.R.) offered any input in regards to this particular design. I, "Uncle" Robert "The R.A.T." Allen Turner, have decided to polish up the design a bit and lay out a manufacturable Printed Circuit Board which I will release under a Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) License. As such, I will analyze "Little John's" original design and then provide my improved version. The original "CC-FlexiMIDI-V1R0-03.09.2009" design files, as provided by "Little John" and his father (J.R.) are contained in the "Original (Deprecated)" folder of this archive and should be referenced for this initial analysis of the design. ================================ ANALYSIS OF ORIGINAL DESIGN: Load up the "CC-FlexiMIDI-V1R0-03.09.2009.sch" schematic file and have it handy for this discussion. Starting with Page 1 of the schematic, we see the expected cartridge (program pak) plug followed by an oddly interesting series of "purported" interrupts, labeled IRQ0* and IRQ1* (the "*" indicates low-level triggering, or active low). These "Interrupts", IRQ0* and IRQ1* appear to go, through disable jumpers, to Pins 1 and 2 of the CoCo Cartridge (Program PAK) Connector. This is both ODD and INTERESTING because Pins 1 and 2 of that connector are -12V and +12V, respectively, on ALL CoCo 1's, TDP-100's and ALL Multi-Pak Interfaces. Both of these pins are +12V on the Dragon computers. Those self-same pins, however, are NOT connected to anything on ANY stock, unmodified, CoCo 2 or 3 computers. I am thus forced to draw the following conclusion: "Little John" apparently allowed for using Pins 1 and 2 of a CoCo 2 or 3 Cartridge Slot to connect to any desired interrupt within the CoCo 2 or 3. That is, a CoCo 2 or 3 might be modified to connect Pins 1 and/or 2 of the Cartridge Slot to any of the CPU Interrupts, the PIA Interrupt (CART*), G.I.M.E. (A.C.V.C.) Interrupts (CoCo 3 only), etcetera. This is an UNECCESSARY feature of the "FlexiMIDI" design and my initial inclination was to omit it from the design. However, since there are jumpers that allow these "hacked in" custom interrupts to be disabled (removed) via JP1 and/or JP2 or connected together (wire or'ed) via JP3, I have decided to leave them in the design should anyone be so inclined as to use this custom interrupt scheme for experimentation or otherwise. Also on Page 1 is a fairly standard RESET switch which I would imagine could prove to be quite convenient but potentially problematic if the device is plugged into a Multi-Pak Interface (RESET* is buffered in a single direction in the M.P.I. and should not be triggered from any cartridge plugged into the M.P.I.), Power ON L.E.D. (which I assume might be quite distracting) and some pull-up resistors for the interrupts, custom and legit. Lastly, there is a 220uF Electrolytic Capacitor for Vcc (+5V) filtering. Ideally, a low ESR Electrolytic should be used, however, paralleling a 220uF Electrolytic with a .1uF Ceramic Disc should provide approximately the same result as a single Low ESR type. Moving on to Page 2, we see a crystal oscillator comprised of three inverters, three resistors and a crystal rated at 1 to 2 MHz. The third inverter actually acts as a buffer and "shaper". Schmitt Trigger inverters are used, although this is not actually necessary it does provide a nice, sharp square wave. Without the hysteresis provided by the schmitt triggers the waveform would appear quasi-sinusoidal at the crystal frequency if viewed on an oscilloscope, but would still function just fine. The output of that third inverter, the buffer stage, is fed into a pair of toggling D type Flip-Flops which provide a divide by two output and a divide by four output, either of which may be selected by jumper JP4. Ideally, we want a solid 500KHz squarewave as the ACIA Clock (which "Little John" labeled "MIDICLOCK" or "MIDICLK"). If a 1MHz crystal is used we would place JP4 on Pins 1 and 2. With a 2MHz crystal we would connect JP4 Pins 2 and 3. This is flexible in that it allows the use of either a 1MHz or 2MHz crystal, whichever might be handy. In my case, and for the redesign, I have a large stock of 16MHz half-can oscillators and so this is what I will be using in the redesign. The 500KHz then, will be derived from the 16MHz oscillator by using the 16MHz to clock a binary counter. At the bottom left of Page 2, we also see three inverters used to invert A7, A4 and A3. This appears to be part of the "address decoding" scheme. Lastly, we see the decoupling capacitors for the inverters and "d-flops". This page (page 2) of the design is fairly solid and well designed. Moving on to page 3, we see the "heart" of the "CC-FlexiMIDI-V1R0-03.09.2009" MIDI Interface Pak. A 74LS133 13-Input NAND is used for address decoding. The 74LS133 in conjunction with the aforementioned inverters and the ACIA enable lines fully decode the ACIA into two consectutive memory addresses. With this, we can now decipher the addressing of the device. This will be done by writing A15 - A0 and filling in the "bit status" required to enable the ACIA, as follows: ========================================================================= | A15 A14 A13 A12 | A11 A10 A09 A08 | A07 A06 A05 A04 | A03 A02 A01 A00 | |=================|=================|=================|=================| | 1 1 1 1 | 1 1 1 1 | 0 1 1 0 | 0 1 1 x | |=================|=================|=================|================== | F | F | 6 | x | ========================================================================= Looking at the above table and noting that A0 selects one of the two internal ACIA registers, it is clear that "Little John" mapped the ACIA to 0xFF66 and 0xFF67. This seems ODD because the most popular MIDI Packs designed for use with the Tandy Radio Shack TRS-80 Color Computer decode the ACIA to 0xFF6E and 0xFF6F. A bit of research, however, led to the discovery that the original CoCo MIDI Pack, "The Colorchestra", mapped the ACIA at 0xFF66 and 0xFF67. The "Colorchestra" was released in 1985 by "Color Horizons" and I own two of them. The aforementioned "research" was simply me looking at the "Colorchestra" P.C.B. and deciphering the address decoding which turns out to be 0xFF66-67. I assume that "Little John" arrived at the 0xFF66-67 addressing in a similar manner as to that just mentioned. It would be relatively easy to redesign the "FlexiMIDI" to respond to both sets of addresses thus guaranteeing compatibility with everything. I have decided, however, that the redesign will feature a semi-programmable address decoder allowing the ACIA to be mapped to any two consecutive addresses within the 0xFF6n area. This will allow the "Flexi-MIDI" to be even more flexible. Setting the address decoder to respond to 0xFF66-67 will make the device "Colorchestra" compatible, whilst setting the decoder to respond to 0xFF6E-6F will make it compatible with the MIDI Interfaces produced by Speech Systems, MusicWare, Rulaford Research, Glenside CoCo Club and other CoCo MIDI Packs. As mentioned, it would be relatively easy to hardwire the decoder to respond to both the 0xFF66-67 and the 0xFF6E-6F address ranges, but I feel that this is unneccesary. Next, we see the 6850 ACIA. This is the "true heart" of the device - a hardware serial port. Looking at the 6850 section of this page of the schematic, we see yet another oddly interesting Interrupt Selection circuit. It is in the form of a 2x4 Jumper Block. This appears to allow selection of any 1 of 4 interrupts to be triggered by the ACIA. IRQ0* and IRQ1* are the previously mentioned "custom" interrupts. NMI* is the 6809 or G.I.M.E./A.C.V.C. Non-Maskable Interrupt Input. The last interrupt on the 2x4 block is the CART* interrupt. This is actually the 6809 or G.I.M.E. IRQ* line that is passed through a PIA inside the CoCo/Dragon. This, the CART* interrupt is the one that should be used for compatibility. The remaining circuitry on Page 3 are fairly standard circuits for MIDI IN, OUT and THROUGH. These go to 5-pin headers. It appears that "Little John" intended for MIDI Cable ends to be soldered to these headers. The redesign will feature 5-pin DIN MIDI connectors. I do see some potential problems with these MIDI IN, OUT and THRU connections on "Little John's" original design. The first problem that I notice is that the MIDI Ground Pins are connected to the same Ground (common or GND) as the computer and MIDI Pack circuitry. This is no good as it violates the MIDI specification and defeats the purpose of the opto-isolator. Thus, the redesign will sever the ground connection of the DIN connectors from the ground connection of the MIDI Interface Pak circuitry. Next, the 330 Ohm (330R) pull-up resistor connected to the output of the opto-isolator should probably be 270R, however, the device should work fine with the 330R resistor. The redesign will have this changed to 270R. The 10K resistor connected to the "BASE" of the opto-isolator darlington-transistor pair should not be needed. I will allow for it in the redesign for testing purposes. The output of the opto-isolator is sent through two schmitt trigger inverters before being applied to the "Receive Data" input of the ACIA. I am drawing the following conclusion in regards to those two inverters: It seems the design was originally intended for use with a Sharp PC-900 or PC-900V digital opto-isolator which has an internal schmitt trigger, the hysteresis of which provides nice, sharp waveform edges. It appears that "Little John" decided, instead, to use a 6N138 opto-isolator, which does not have hysteresis (schmitt triggering) and thus he must have included the two inverters to alleviate this perceived problem. I am relatively certain, however, that these two inverters are unneccessary and thus I will remove them in the redesign. Had I not used two of the inverters in the hex-inverter package for address decoding, I might have left these two inverters in the redesign, however, I decided the savings of one chip was worth eliminating these two inverters. Hopefully, results will be satisfactory. That is about it for the initial analysis of "Little John's" original design. I shall now proceed to design a slightly improved and, hopefully, manufacturable version of "Little John's CC-FlexiMIDI-V1R0-03.09.2009" Hardware M.I.D.I. Interface Pack. This redesign will be titled: "CC-FlexiMIDI-V1R1-03.09.2009". ================================ THE REDESIGN: Load up the NEW design from the CURRENT folder in the archive and use it to follow this discussion. Starting with Page 1 of the schematic, I will start the redesign with the Cartridge Program Pak Slot Plug (Edge-Card or Edge-Fingers). This is what will actually plug into the cartridge port on the computer or Multi-Pak Interface (M.P.I.). Next, I will add an edge card socket wired in parallel to the edge-fingers. This is based on "Little John's" Universal Footprint which means that you can fit either a 40-pin card socket or a 40-pin header. This will allow an additional cartridge or other hardware to be plugged directly into the MIDI Interface, thus eliminating the need for a "y-cable" or Multi-Pak Interface. The +5V is filtered with a 220uF Electrolytic Capacitor in parallel with a .1uF Ceramic Disc or Dacron/Polyester/Mylar capacitor. A Power ON L.E.D. indicator is included here, along with an enable/disable jumper. Removing the jumper disables the Power ON L.E.D. should it become a distraction. Next, I'll add in the "CUSTOM" Interrupts, including their jumpers. The jumpers should be REMOVED from all of these if the device is to be used with a CoCo 1 and/or M.P.I. (Multi-Pak Interface) or with ANY of the CoCo Clones and/or compatibles, including the Dragon. In actuality, these jumpers should never be needed and thus should never be installed - they are for experimental purposes only. Removing the jumpers prevents the accidental application of +/-12V to the IRQ* output pin of the ACIA which would fry the ACIA. I have included 680R "failsafe" resistors, but it is likely that they would not prevent a fried ACIA. Lastly, I have included the RESET Switch for convenience. The RESET switch should NEVER be pressed if the device is inserted in a Multi-Pak Interface as you may blow the 74LS367 in the M.P.I. That is about it for Page 1 of the redesign. Moving on to Page 2: This page is exclusively dedicated to the Baud Rate Generator for the ACIA. Starting at the left, we see the bypass capacitors for the 74LS590 counter. I have used both a 10uF Electrolytic and a .1uF (100nF) Ceramic Disc. This would be important for a ripple counter, however, the LS590 is a synchronous counter and so the Electrolytic could be omitted. I chose to leave it in. There is also a bypass capacitor for the 16MHz oscillator can. I created a dual-footprint for the oscillator can which allows the use of a full or half can oscillator. The 16MHz is fed into the LS590 counter which provides a choice of ten different clocks for the ACIA. For compatibility with existing standard MIDI packs for the CoCo, the 500KHz clock should be selected. The LS590 has an output register which is clocked by the same 16MHz that clocks the counter section. The enable pin of the oscillator is connected to system RESET* which prevents it from oscillating when the system is in a reset state. This pin could have been left floating causing the oscillator to always oscillate. It will work either way. Page 3 is the semi-programmable address decoder. The 74LS133 in conjunction with the two inverters decodes 0xFF6n - the output will go low on any access to the 0xFF6x range. Only 12 of the 13 inputs to the LS133 were needed. The unused input could be connected to Vcc, E or RESET*. It is important to gate the E Clock in at some point and it could have been done here. I chose to connect the input to RESET*. The ACIA actually has an E Clock input which gates it with the E-Clock so it probably does not need to be gated to the address decoder, though, as you'll see, I gated the E-Clock into the next stage. The 74LS138 decodes 1 of 8 sets of even/odd addresses in the 0xFF6n range (it is enabled by the output of the LS133 and the E-Clock).) So, when any address in the 0xFF6n range appears on the address buss during the high time of the E-clock, the LS138 is enabled and decodes A1-A3 into 1-of-8 chip selects. For maximum compatibility, the 0xFF6E-F output should be selected. Page 4: This is the 6850 ACIA. This should be either a 68B50 or a 63B50 or 63C50 for operation at up to 2MHz CPU Clocks. This should be pretty self-explanatory. The 6850 datasheet can fill in any necessary details. Page 5: This is a fairly standard MIDI IN circuit. There are two optocouplers here: a 6N138 and a PC-900 - You should use ONLY ONE, not both. R9 is only needed if you use the 6N138. The diode is a 1N4148 or 1N914A. Page 6: This is a fairly standard MIDI Out circuit. Page 7: This is the final page and is a fairly standard MIDI Thru circuit. It simply echoes the MIDI In. Well, that's about it for a redesign of "Little John's" original. I am ordering some prototype boards to see if this thing will work. Updated to CC-FlexiMIDI-V1R2-12.29.2019 on December 29, 2019 - This minor update: A Universal 5-Pin DIN component was created and the GND Connection was reconnected to MIDI OUT and MIDI THRU. NO GND connection was made to MIDI IN. This should now create a proper MIDI Interface.

This microservice was developed with Spring Boot to process wire transfers, verifying the current state in the H2 in-memory database and the fields of the request body model, to validate what the next state would be, using software Design Patterns such as the Pattern State and Strategy.

Develop a complete mathematical model of a shape memory alloy (SMA) wire actuated by an electric current and a bias spring. The operation of the SMA actuator involves different physical phenomena, such as heat transfer, phase transformation with temperature hysteresis, stress–strain variations and electrical resistance variation accompanying the phase transformation. We model each of these phenomena in a modular fashion.

Actual Project file https://drive.google.com/file/d/1RCJ271K1B5Ig839c_0UCq8oWn5mpz7EN/view?usp=sharing Introduction This project was part of the embedded system design course, and uses face recognition to control a servo lock. The face recognition has been done using the Eigenfaces algorithm (Principle Component Analysis or PCA) and implemented using the Python API of OpenCV. Open Source Project source It's a slight modification of the Raspberry Pi Face Recognition Treasure Box project by Tony Dicola on the Adafruit Learning System. The code has been modified at places to replace the use of the RPIO library (which has issues running on the new Raspberry Pi 2 Model B+) with the standard RPi.GPIO library. The project has also been implemented to work as an automated home lock system which unlocks for the owner of the house and doesn't for any other visitor. It also plays an appropriate voice message. IMPLEMENTATION DETAILS This slight modification also changed the way of installing the dependencies,OpenCV & Python version and also the installation of updated GPIO ports for Raspberry B+. The modifications that has done here also includes the .wave sound files that tends to start or stop depending upon the door recognition status. OpenCV Installation This project depends on the OpenCV computer vision library to perform the face detection and recognition. Unfortunately the current binary version of OpenCV available to install in the Raspbian operating system through apt-get (version 2.3.x) is too old to contain the face recognition algorithms used by this project. However you can download, compile, and install a later version of OpenCV to access the face recognition algorithms. Note: Compiling OpenCV on the Raspberry Pi will take about 3 hours of mostly unattended time. Make sure you have some time to start the process before proceeding. First you will need to install OpenCV dependencies before you can compile the code. Connect to your Raspberry Pi in a terminal session and execute the following command: sudo apt-get update sudo apt-get install build-essential cmake pkg-config python-dev libgtk2.0-dev libgtk2.0 zlib1g-dev libpng-dev libjpeg-dev libtiff-dev libjasper-dev libavcodec-dev swig unzip Answer yes to any questions about proceeding and wait for the libraries and dependencies to be installed. You can ignore messages about packages which are already installed. Next you should download and unpack the OpenCV source code by executing the following commands: wget http://downloads.sourceforge.net/project/opencvlibrary/opencv-unix/2.4.10/opencv-2.4.10.zip unzip opencv-2.4.10.zip Note that this project was written using OpenCV 2.4.10, although any 2.4.x version of OpenCV should have the necessary face recognition algorithms. Now change to the directory with the OpenCV source and execute the following cmake command to build the makefile for the project. Note that some of the parameters passed in to the cmake command will disable compiling performance tests and GPU accelerated algorithms in OpenCV. I found removing these from the OpenCV build was necessary to help reduce the compilation time, and successfully compile the project with the low memory available to the Raspberry Pi. cd opencv-2.4.9 cmake -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_INSTALL_PREFIX=/usr/local -DBUILD_PERF_TESTS=OFF -DBUILD_opencv_gpu=OFF -DBUILD_opencv_ocl=OFF After this command executes you should see details about the build environment and finally a '-- Build files have been written to: ...' message. You might see a warning that the source directory is the same as the binary directory--this warning can be ignored (most cmake projects build inside a subdirectory of the source, but for some reason I couldn't get this to work with OpenCV and built it inside the source directory instead). If you see any other error or warning, make sure the dependencies above were installed and try executing the cmake command again. Next, compile the project by executing: make This process will take a significant amount of time (about 3 hours), but you can leave it unattended as the code compiles. Finally, once compilation is complete you can install the compiled OpenCV libraries by executing: sudo make install After this step the latest version of OpenCV should be installed on your Raspberry Pi. Python Dependencies The code for this project is written in python and has a few dependencies that must be installed. Once connected to your Raspberry Pi in a terminal session, execute the following commands: sudo apt-get install python-pip sudo apt-get install python-dev sudo pip install picamera sudo pip install RPi.GPIO You can ignore any messages about packages which are already installed or up to date. These commands will install the picamera library for access to the Raspberry Pi camera, and the GPIO library for access to the Pi GPIO pins and PWM support. Hardware The Hardware required for this project are as follows: Raspberry Pi ( I prefer Model 2 B+) Raspberry Pi Camera Micro Servo One Push Button Power Supply for the Servo (5V Source) One 10K resistor for pull down Breadboard and Jumper wires for connections The necessary circuit diagrams and further explanations are explained in depth in the original pdf accompanying the project. Kindly go through it first.

On Friday, August 23, 1912, four-year-old Bobby Dunbar along with his family were staying at their family cabin in Louisiana on Swayze Lake, a heavily wooded area that was more like a swamp. The 11 party members included Bobby's parents Lessie and Percy Dunbar, Bobby's brother Alonzo, as well as several other family and friends. On that day, Percy Dunbar, Bobby's father, had to leave for work much to young Bobby's dismay, who, in a tantrum about his father leaving, broke the strap of his straw hat. Lessie, Bobby's mother, was preparing for a fish fry. Bobby then expressed that he wanted to go with Paul Mizzi, a family friend, to the lake to shoot garfish. Paul often took Bobby horseback riding and had an affectionate nickname for him, "Heavy". His mother allowed it and the rest of the boys in the party decided to join. Later, the group of boys were called back for lunch and they started making their way back, though from here the details get fuzzy. Paul recalled putting Bobby's brother Alonzo on his shoulders, joking with Bobby, "get out of the way, Heavy, or I'll run you over." Bobby's response, what some newspapers report as his last words, was characteristic to his personality, retorting, "you can't do it. You ain't no bigger than me." When they returned back to camp, Lessie realized her son, Bobby, was no longer with the group and was missing. She and Paul began to call out for Bobby in a panic and at one point Lessie fainted into the dirt. Three men from the party began to search north on the wagon trail behind the camp, in case Bobby had gone after his father. On their search, they ran into Percy on his way back from working, who raced to camp when he heard of Bobby's disappearance. By that night, with no trace of Bobby, searchers began to look for Bobby's body. They used dynamite to blast throughout the lake while a thick cable with massive hooks stretched across the length to drag the depths. After the night was over, divers also went into the lake to search any coves the hooks were unable to reach or places where a body could get trapped in the weeds. The only corpse they turned up from these efforts was that of a deer. Because Bobby's body had not been recovered in the lake, searchers believed he could have been killed by an animal, with the most likely predator being an alligator. Searchers even cut alligators open hoping they might find his remains inside, to no avail. By Saturday, August 24th, about 500 men had come to search for Bobby. Searchers even did a test using a straw hat with a broken strap like the one Bobby had on to test how long it could float, finding that it could float uninhibited for hours, leading searchers to believe there should have at least been some evidence of Bobby's hat. The stress of Bobby's disappearance caused his mother Lessie to become grievously ill and most of the family had to return to their home in Opelousas, Louisiana. Paul Mizzi, who had been the last adult to see Bobby alive, along with two other men who had been guests at that fateful fish fry that day would stay and continue to search for weeks more. Searchers found a solitary set of bare footprints leading toward a railroad trestle bridge heading out of the swamp, with still no body or even a trace of evidence to prove he had been killed by an animal. Those who continued the desperate search began to question if Bobby could have been kidnapped. It was speculated that someone in a small boat could have taken him through the north end of the lake into the bayou or someone on foot could have taken him on the trail or down the train tracks. Searchers had run into stragglers walking along the tracks and began to question if one of them could have taken Bobby. By August 26th, the authorities had also contacted the police in New Orleans about 130 miles away to search for Bobby there, giving those invested in the theory of his kidnapping further hope and official validation. Percy Dunbar would also go to New Orleans himself to distribute 700 copies of Bobby's picture and talked with many reporters. A detective agency made postcards with a picture and description of Bobby and mailed them to town and county officials from East Texas to Florida. The description of Bobby that was widely distributed read, "age four years and four months; full size for age; stout but not fat; large, round blue eyes; light hair and very fair skin, with rosy cheeks. Left foot had been burned when a baby and shows a scar on the big toe, which is somewhat smaller than big toe on the right foot. Wore blue rompers and a straw hat; without shoes." The Dunbar's whole home town of Opelousas held out hope that Bobby was still alive and together contributed to a $1,000 reward, which was "to be paid to any person or persons who will deliver to his parent's alive little Robert Clarence Dunbar. No questions asked." In 1912, this was a relatively enormous amount, roughly equivalent to about $22,000 today. However, after over eight months with no sign of Bobby, the unused reward money was returned to the townspeople who had donated it, but only a week after a major lead in the case broke. In April, 1913, a wire from the Ladies of Hub came to alert the Dunbars that an old tinker/peddler named William Cantwell Walters was spotted in the small town of Hub in southern Mississippi with a boy resembling Bobby, though his foot had been too covered in grime for anyone to get a good look. Walters had given authorities various and inconsistent answers about who the child belonged to, saying it was his own, his sister's, et cetera. Eventually the Ladies had witnessed Walters whipping the child, finally giving a citizens' committee enough to temporarily detain Walters and examine the boy, which they then firmly believed was Bobby, but asked the Dunbars to send further photo evidence. The Dunbars remained skeptical until they in turn received photos of the boy, and at this point the Dunbars traveled to Mississippi to see him in person, still not sure if it was their Bobby. The boy they had found had a scar on his left foot, as well as a mole on his neck where Bobby had one. However, he refused to answer to the name Bobby and when Lessie tried to hold him, he refused to interact with her. Lessie asked to see the boy again the next day and in their time together was able to give him a bath. At this point, she felt without any doubt that they had found Bobby. In a wave of emotion, she's recalled as shouting, "thank God, it is my boy" before fainting. Meanwhile, William C. Walters, the man whom the boy was taken from, was insistent that the boy was not Bobby Dunbar, but in fact Bruce Anderson. Walters claimed the boy was the illegitimate son of his brother and a woman named Julia Anderson, who had cared for his elderly parents back home in Barnesville, North Carolina. Julia Anderson was a single mom who did in fact work as a field hand and a caretaker for William Walters's parents. Walters claimed that Julia had given him the boy willingly, which Julia did confirm, though she disputed some of the details of his story, telling the paper, "Walters left Barnesville, North Carolina, with my son, Charles Bruce, in February of 1912, saying that he only wanted to take the child with him for a few days on a visit to the home of his sister. I have not seen the child from that day to this. I did not give him the child, I merely consented for him to take my son for a few days." Some were skeptical at his motives to claim he was given consent to take the child, as kidnapping was a capital offense in Louisiana and he could be just trying to avoid the kidnapping charge. He wrote to the Dunbars explaining so much and begged them to send for her, saying, "I know by now you have decided. You are wrong, it is very likely I will lose my life on account of that and if I do the Great God will hold you accountable." A newspaper in New Orleans arranged to bring Julia Anderson to Mississippi so she could identify the boy as well and she arrived in Opelousas on May 1st, 1913. However, stepping into the Dunbar's hometown, Julia Anderson was essentially already on enemy territory, as the town had already decided that the boy was Bobby Dunbar, who had miraculously come back to them. His return was made into a huge spectacle and he rode through town and into the square on a fire engine covered in flowers. When Julia Anderson met the boy, he did not react well to her, much like he had originally acted with Lessie Dunbar, though he may still have been reeling from the many sudden changes in his life, including the fact that in his beautiful new home he had just been given a pony and a bicycle. Additionally, Anderson had been missing her son for even longer than the Dunbars. It had been 15 months since she had allowed Walters to take Bruce and he had never returned with him. Similar to Lessie Dunbar, at first Anderson also had trouble identifying the boy as her son, but soon after stated that "her mother's heart" knew that the boy was her son. However, unlike with Lessie Dunbar, Anderson's initial uncertainty was not easily forgiven by the press. The press largely demonized her for having three children by two different men and it was implied she was a prostitute. Others called her illiterate and naive. They also called attention to the fact that she had lost all of her children within just a year. She had to give her daughter up for adoption, she had a baby who died a sudden death that she was wrongfully blamed for, then Bruce was taken from her. An article written in the New Orleans Item wrote of Anderson, "she had not seen her son since February of 1912, she had forgotten him. Animals don't forget, but this big, coarse country woman, several times a mother, she forgot." A court-appointed arbiter ruled that the boy was the Dunbar's missing son rather than Anderson's, as Anderson had no lawyer, no money, and no allies in Opelousas. She left town and the boy was uncontestedly allowed to remain Bobby Dunbar. William Walters went through a two-week trial that was described by some as "sensational", at which he was convicted of kidnapping and sentenced to life in prison. After just two years in jail, William Walters' verdict was overturned on an appeal and he was granted a new trial on a technicality. As for the boy, he grew up and lived as Bobby Dunbar. At 18, he fell in love with a girl named Marjorie from a nearby town. They married in 1935 and had four children. He passed away in 1966, always believing he was Bobby Dunbar, but this story doesn't end there. Skipping forward to 1999, Bobby Dunbar's granddaughter, Margaret Dunbar Cutright, began looking deeper into her family's history. Cutright had always been especially intrigued by the family legend of her grandfather's kidnapping and had asked her grandmother to tell her the story many times in her childhood. It was then a story that she told to her own children. A scrapbook with over 400 articles about the Dunbar case was given to Cutright by her father. She writes of the project, "the scrapbook was like a jigsaw puzzle without the picture on the box, and over the next few months, I lost myself in trying to piece it together." She was especially affected by an editorial cartoon from 1913 titled "Fifty Years From Now", in which a bearded old man sits in a chair with his grandson looking at newspapers from the Dunbar kidnapping trial and asks, "Grandpa, do you think we'll ever know for certain what our right name is." Cutright instantly noticed discrepancies in how newspapers were reporting the events. For example, there were at least two different reported versions of Lessie and Bobby's reunion. One paper stated that Lessie recognized Bobby immediately, while the other described Lessie as unsure, even including a quote from Lessie saying, "I do not know, I am not quite sure." She also found that Percy and Lessie had originally told the papers that the boy didn't look like their son, and that his eyes were too small. Some newspapers also reported Bobby didn't recognize his father, mother, or brother Alonzo. She also was disturbed to read the many biased accounts of Julia Anderson from the time and to read that from Anderson's perspective, she had felt that the Dunbars had kidnapped her son. Linda Tarver, the granddaughter of Julia Anderson, says of the family perception, "all of us cousins grew up, we knew that we had an uncle that had been taken by the Dunbar family in Opelousas, Louisiana. We always said kidnapped. We said they kidnapped him." Cutright continued her search obsessively, researching at small town libraries, archives, and courthouses all over the south. Eventually, the idea of testing her grandfather's DNA came up. Cutright's father, Bobby Dunbar Jr., agreed to give a DNA sample to compare with a sample given by one of her great-uncles, a son of Bobby's brother Alonzo. This was a controversial choice and many in the family urged Dunbar to leave the past alone. Gerald Dunbar, one of Cutright's uncles, said of the matter, "no matter how a DNA test turns out, there's going to be a sense of loss. What is to be truly gained." Exactly, when the test results came back, shockingly, the samples did not match, leaving Bobby's son Robert Dunbar Jr. himself surprised. He said of the outcome, "my intent was to prove that we were Dunbars. The results didn't turn out that way, and I have had to do some readjusting of my thinking. But I would do it again." Still, although this test proves that the boy was not Bobby Dunbar, there does not seem to have been a test administered to prove that the boy was in fact Bruce Anderson. Hollis Rawls, Anderson's son, had expressed a willingness to submit DNA before he passed away, but even without confirmation of that DNA evidence, many were apt to believe that Bobby Dunbar had actually been Bruce Anderson. In terms of incorrectly identifying himself as a Dunbar, Bobby Dunbar Jr. recalled a conversation he had with his father when he was a teenager in which he asked his father how he knew he was Bobby Dunbar and remembered his father telling him, "I know who I am, and I know who you are, and nothing else makes a difference." This settles the mystery of the boy that was found and yet the chilling mystery surrounding the boy lost continues to persist. Many wonder what actually happened to Bobby Dunbar that day. Some continue to believe that he was eaten by an animal, such as an alligator or a bear, though no evidence such as clothing was ever found to suggest that. Some wonder if he was actually kidnapped after all. In an interview in 1932, Bobby Dunbar, who was probably Bruce Anderson, recalled a memory of his time with William Walters in which he revealed that he remembered that there was another boy with him who fell off the wagon and died and was buried. Some wondered if the memory had been a memory of suggestion, as there had been theories posed by the prosecution at Walters's trial that he could have kidnapped both Anderson and Dunbar. Psychologically, some posit these theories could have allowed the boy to rationalize Bruce Anderson's death and allowed a narrative as Bobby Dunbar to begin.

My partner and I created from scratch a fully pipe-lined digital computer datapath for our Fundamentals of Computer Organization Class, which we programmed solely in verilog and implemented in Xlinx's Vivado Design Suite 2017.2. Our digital datapath optimally runs sets of MIPS Assembly instructions in hex for conducting a full search based motion estimation with a variable block size. We divided up the process into 5 different sections to better keep track of the values on the wires and improve functionality; these sections from left to right were the Instruction Fetch (IF), Instruction Decode (ID), Execution (EX), Memory (ME), and Write Back (WB) stages. Arithmetic calculations were achieved through our Arithmetic Logic Unit (ALU) and we utilized muxes in order to select the necessary value needed for the successful completion of each instruction. The correct value to be selected by each mux was determined by our Controller component. Optimization of the speed and resource usage of the processor was accomplished through pipe-lined registers, forwarding, and hazard detection.

Skip to content Setup.ampedwireless.com Amped Wireless Setup | amped Wireless amped wireless setup setup ampedwireless com Why is setup.ampedwireless.com not working? There may be several aspects because of which a user is unable to access the setup.ampedwireless.com interface of the router. A user loses his control and management from the router if he fails to access the web interface of the Amped router. For quick help, you can also check the manual guide that comes with the router or can also search for the Online manual guide over the Internet. Follow the below steps to troubleshoot the issue If there is a wired connection between the router and your computer, make sure the physical connection is correct. Make sure the switch is turned on with which you have connected the Power cable of the wireless router. If you are typing the LAN IP address of the router in the address bar, make sure you are typing correctly. The default LAN IP address of the Amped router is 192.168.0.254. Ensure that the computer is not connected to any other wireless network at the same time. If there is a wireless connection between the devices, make sure the computer is within the wireless range of the router. Close the current browser and launch it again. Delete the history and cache memory of a browser using the settings tab. Try again to access the setup.ampedwireless.com interface. Use Google Chrome, internet explorer, and Mozilla. Any other browser may be the reason you get denied from accessing the setup.ampedwireless.com window. If the Setup Wizard directly appears, instead of the web menu Dashboard, it may be the reason that the router has not been configured yet. Reset the router by holding the reset button for around 10 to 20 seconds. It will revert the default settings into the router. When the reset process is done, complete the setup wizard or skip it to access the Dashboard. Note: If all the above troubleshooting steps fail to resolve the setup.ampedwireless.com issue, you can call the Support team of the Amped to resolve the issue. We are available for our users 24 hours a clock to resolve any kind of issue a user is facing. How to login into the Amped Wireless range extender? Amped Wireless range extender can interact through the web interface of the setup.ampedwireless.com interface. To interact with the web menu Dashboard, you need to go through the login window of the Amped range extender. You cannot perform the login process if you don’t know the correct login credentials of the Amped extender login window. The default username of the Amped extender is “admin” and the default password is “admin”. amped router login Steps to log into the Amped wireless range extender Open a browser on the computer connected to the extender’s network. Type ampedsetupwireless.com in the address bar and hit enter If you fail to enter, type the LAN IP address of the range extender in the address bar. The LAN IP address of the Amped range extender is 192.168.0.254. The default Amped range extender login window appears on the screen. Type “admin” in the username field as the default credentials and type the password you typed earlier during the login process. If you haven’t changed the default password type “admin” in the provided field. Both the username and password are case-sensitive. Note: You need to hold the shift key before typing an uppercase letter and release the key before typing a lowercase letter. Click Login and the web menu Dashboard of the Amped range extender appears. Now you can change the settings and features of the Amped range extender. Note: While performing the login process, make sure you are typing the correct login credentials, otherwise you will be denied from accessing the web interface of the Amped range extender. How to setup an Amped wireless range extender via setup.ampedwireless.com? Optimum placement of a range extender is vital to fetch robust Wi-fi speed from the main network. The location plays an important role in determining the performance level of the range extender. You can also take the help of a Quick setup guide that comes with the range extender to perform correct steps during the setup process. Note: Connect your computer to the extender via Ethernet cable to avoid sudden disconnection during the setup process. Follow the below steps to set up the Amped rec 10 range extender Unbox the range extender and take out the quick setup guide, warranty card, and a power cable. Adjust the antennas of the Amped wireless range extender. Connect the range extender to an available electric outlet near the main router. Note down the default Wireless settings from the back of your range extender Use the default Wireless settings to connect wirelessly to the computer, Go to the computer, open the Wi-fi settings and search for the available Wi-fi networks. Connect to the default network name of the range extender. Once you get connected to the range extender’s network, launch a browser. Type setup.ampedwireless.com on the address bar of the browser and hit enter. You can also type 192.168.0.254 as the URL of the browser. The setup.ampedwireless.com configuration page appears on the screen. Select the “Wireless range extender” option and click Next to proceed. Click Scan to find Wi-fi networks nearby to extend. The Wi-fi devices available near the Wi-fi appear on the screen. Select the Wi-fi network you want to extend. Type the Wi-fi password in the provided field to connect to it. Click Next. Follow the above step twice, if you are connecting the range extender to a dual-band router. Now, follow the onscreen instructions to proceed with further steps. Personalize the Wi-fi settings of the extended network. Users are recommended to change the default wireless settings. Assign a new network name and Wi-fi password to the extended network. A new network name must be unique to allow users to connect to the extender’s network. If you want to create a hidden network select the “Hide SSID” option. To connect to a hidden network, a user has enter the network name in the Wi-fi list manually Once done, click Next. Now you can review the configuration settings you made Note down the wireless and other administrative settings you made for future use. Click Finish when it’s done. The extender starts the reboot process to apply the settings you made. Wait for a couple of minutes until the reboot process is complete. Note: Once the setup process is done, you can relocate the range extender to the desired location. Place the range extender midway between the router and your computer for better results. You can take the help of the Wi-fi LED of the range extender to find a good spot to place the range extender. If the LED blinks blue the range extender is at a good spot and if the LED blinks red, it means you need to bring the range extender close to the router. How to update the firmware of the Amped wireless range extender? The firmware plays an important role in removing the bugs of the range extender and escalating the performance of your device. New firmware is stored in the flash memory of the device. New firmware is responsible for removing bugs and adding new features to the range extender. It improves the mechanism of administrative settings and refines the networking protocols. Steps to update the firmware of the Amped wireless range extender Visit the downloading center of the Amped extender i.e www.ampedwireless.com /support. Type in the model version and product name in the provided fields. Click Download when prompted. Remember the location where you saved the downloaded firmware file. Do not forget to extract the firmware file. It will give you convenience while uploading the file into the ampedsetupwireless.com interface. Open a browser on the computer connected to the extender’s network. Type ampedsetupwireless.com in the address bar and hit enter If you fail to enter, type 192.168.0.254.in in the address bar. The default Amped range extender login window appears on the screen. Type “admin” in the username field as the default credentials and type the password you typed earlier during the login process. If you haven’t changed the default password type “admin” as the default credentials Both the username and password are case-sensitive. Note: You need to hold the shift key before typing an uppercase letter and release the key before typing a lowercase letter. Click Login and the web menu Dashboard of the Amped range extender appears. From the main navigation panel, click on the Management tab then click on the Firmware Upgrade tab. Scroll down the firmware upgrade page. Click “Choose file” and navigate the cursor to locate the file. Select the file then click Upload when prompted to begin the upgrade process. Wait for a few minutes to let the process complete. Do not interrupt the installation process, it may lead to failure in the update process. When the process gets completed, the Amped range extender automatically reboots. Note: You can check the confirmation of the update process through the status tab of the ampedsetupwireless.com window. Make sure you have already read the release notes of the firmware to know the settings that will get erased during the update process. How to Connect to the Amped Range extender? The connection process is one of the important processes through which a user connects the amped range extender to the router. You can connect the Amped range extender to the router via a wired connection and the wireless connection. The wired connection is done through the Ethernet cable and the wireless connection is done via the WPS connection method. Here are the things you need to keep in mind before the connection process. Place the range extender about halfway midway through the router and the Wi-fi dead zone. Fix the range extender in a ventilating or a mounting area to receive the clear Wi-fi signals. Keep the extender away from electronic or radioactive appliances. Make sure there are no walls or metallic objects between the router and the range extender. Steps to connect to the Amped range extender Plugin the range extender directly to a power outlet near the main router Wait until the Power LED turns solid green. Now press the WPS button on your router. Go to the range extender, press, and hold the WPS button for around 3 seconds. Wait for a couple of seconds to establish the connection between the router and the range extender When the LED changes from the blinking to the stable, it means the connection got established. If you have a dual-band router, repeat the above step to connect to the 5GHz frequency band. When the connection gets established, relocate the extender to a suitable location. Check the signal LED, if the signals are strong the LED blinks white. If the signals are weak, the LED blinks red which means you need to bring the router closer to the range extender. Now go to the computer and search for the available Wi-fi networks. Use the default Wireless settings given on the back of the range extender to connect to the computer. The default Wireless name will end with the _EXT. For example Amped_EXT. Type default network key in the provided field and click Connect. When it gets connected to the extended network, launch a browser. Type setup.ampedwireless.com in the address browser and hit enter. You can also type 192.168.0.254 as the URL of the browser. The setup.ampedwireless.com configuration page appears on the screen. Now you can proceed to begin the setup process. Note: New users recommended connecting the range extender to the router through a wired connection. You can use the Ethernet cable of the router to create a wired connection between the devices. If you face any obstruction during the setup process, you can call our executives anytime to resolve the issue you are facing. Archives November 2021 Categories Uncategorized Copyright © All right reserved Created By: Fansee Themes Amped Wireless Setup

Claude Code plugin marketplace for Wire. Persistent memory, context management, and more.

Shape Memory Alloy (SMA) Finite Element Analysis using ABAQUS software, for a SMA wire and a SMA composite structure

Part of the Sentry by Protectus. Project to interpret bytes off the wire, storing connection metadata and per-second volume information in Mongo. Released as open source in memory of Pete Garvin.

A lightweight, multi-mode database written in Rust with support for both key-value and SQL workloads. RustyDB provides a REST API, MySQL wire protocol compatibility, and flexible deployment options from in-memory to persistent storage.

Claude Code Plugins is an open-source add-on suite that turns Claude Code into a programmable workspace. It gives you composable workflows, automatic project memory, skill packs, lifecycle hooks, sub-agents, and typed commands—all wired with minimal config.

Code for the paper "Soft-wired long-term memory in a natural recurrent neuronal network".

Poc with InMemory mongoDb, and http client stub.

Semantic memory library for RAG — get your 80 gigs of wet-wired recall.

Bio-Inspired drone with flapping wings actuated by muscle-like Shape Memory Alloy micro-wires

This repository contains the work on the topic "Data-driven simulation of functional fatigue in shape memory alloy wires". This work is part of my project work at the Institute of Mechanics at TU Dortmund University

This project wires AntiGravity's AI agents directly into NotebookLM via MCP. Instead of re-pasting context into every conversation, agents query a dedicated NotebookLM notebook that acts as the project's long-term memory — saving tokens, reducing hallucination, and keeping knowledge grounded in your actual documents.

A local-first AI stack for LM Studio. Docker-powered RAG pipeline with pgvector, SearXNG, and TEI embeddings, plus 8 pre-wired MCP tool servers for web search, PDF reading, file access, persistent memory, screenshots, and more. No API keys, no cloud AI — everything runs on your hardware.

This project is a memory game where i wired leds to certain gpios on my esp32. The code hosts a webserver and the leds flash in a sequence that starts at one led. every iteration adds a new random led and the previous ones are the same. the user then has the chance to match the sequence with buttons on the hosted webpage.

Hardware: The physical or touchable elements of a computer are known as hardware. When people express with reference a computer, they customary indicate the hardware. Hardware is a combined term.it incorporates not only the computer but also the wires, affix, power supply units and outer device such as the keyboard, mouse, monitor, audio speakers, printers, and so on. The style is used to differentiate these fixed components of a system from the variable software or data integrant, which perform, stores, or transmits. Software: images The non-touchable part of the computer is called software. Software relates to the programs that indicate the computer what to perform. Software create the computer productive. Software is the common name provides to all the programs (indications) and data required to create the computer powerless. The term software indicates to the non-physical components of a computer system. Windows, Visual Basic, Norton Antivirus, Microsoft Word, Microsoft Excel, Microsoft power point, word pad are the illustrations of software. At the end of our exchange of views about computer we conclude that: It is a machine. It is without life object. It requires outside interference for it to start. It can only do process for which it is create. It is electronic. It is developed by electronic circuits. It starts on electrical power. It is automatic. Once runs, it carry on to run without outside interference. It can juggle data, these significant principles. It can operate arithmetic operations like as adding up, deduct, multiplication and division. It can complete data. It has memory. It has the ability to recollect what it has perform.it can store indications in its memory and obey these through unaided. It can operate logical operations. It can be awarded a set of indications that tell what it must perform and how it must functions it. It can construct outputs upon finalizations of these functions and indications. Potentials of Computer: Speed: A computer can operate data hasty than any other machine styles operate parallel works. Repetition: A computer can untiring operations the similar functions millions of times in absolutely the similar path without obtaining dig out and exhausted the path a human accountant would. Accuracy: A computer’s fasten- speed operations are Keep Company by high- correctness outputs. No other system can have as higher correctness as a computer system. Logical Operations: The computer can put up decisions starting point on some circumstances and take substitute course of process accordingly. Store and Recall information: The computer is same as human brains it can remembers factuality, indications and information and hark back means recall them when required. Self-Checking: The computer confirms the correctness of its own expressions by means of an identity check. Self-operating: At the time data and the program are fixed into the computer’s brains or memory, the computer is able of performing the indications on its own, without human interference. Restrictions of the Computer A computer cannot procreate information on its own. A computer cannot faultless wrong indications. A computer cannot come up with an exact the same and original decision.