Editing User:SL/Borg Logic Gates

I'm mostly just pondering whether it might be possible to make a hybrid borg-mechanical system at the moment.

In order to make borg logic reliable without forcing dwarves to stand around, we may need to base it on a memory gate first. The memory gate requires water. We can use the simple one from my water/mechanism-connected logic gates: http://dwarffortresswiki.net/index.php/User:SL/Logic_Gates#Memory

The kitten logic gates sound more optimal, but I want to see where this leads.

You would build the memory gate on top of a reservoir, aquifer, or ocean. I'll explain what to link the SET and CLEAR inputs and the OUTPUT to if/when I come up with designs for the rest of the logic gates. :P

=== NOT gate ===
 ###
  ^
  ^
  ^
 ###
 DvD
 DvD
 DvD
 ###

INPUT : All the doors, labelled D. Your input is some lever, or something else, which you want to negate the value of.
SET OUTPUT: 'v' tiles are pressure plates set to detect dwarves, linked to the SET output on a memory gate. They are given a pathing priority with the highest possible value (Important!).
CLEAR OUTPUT: '^' tiles are pressure plates set to detect dwarves, linked to the CLEAR output on a memory gate. They are given a pathing priority with the lowest possible value (Important!).

How it works: If the INPUT is ON, the doors are opened, and newly calculated paths will be routed over the SET OUTPUT pressure plates. If the doors are closed, newly calculated paths will be routed over the CLEAR OUTPUT pressure plates instead. This will unfortunately cause dwarves who have already calculated a path through the now-closed doors to run into the doors and exclaim "WTF."
@@ Line 1: / Line 1: @@
-I'm mostly just pondering borg logic at the moment.
+I'm mostly just pondering whether it might be possible to make a hybrid borg-mechanical system at the moment.
-In order to make borg logic reliable without forcing dwarves to stand around, we may need to base it on a memory gate first. The memory gate requires either water or an animal:
+In order to make borg logic reliable without forcing dwarves to stand around, we may need to base it on a memory gate first. The memory gate requires water. We can use the simple one from my water/mechanism-connected logic gates: http://dwarffortresswiki.net/index.php/User:SL/Logic_Gates#Memory
-This one uses water: http://dwarffortresswiki.org/index.php/User:SL/Logic_Gates#Memory
-This one uses a kitten (or other animal): http://dwarffortresswiki.org/index.php/User:Bidok#Memory
-If you use my water-based memory gate, put it on top of a reservoir, aquifer, or ocean. If you use Bidok's, just make sure the door is non-pet-passable, put an animal inside, and have the door leads to a hall that leads to the activity zone (whereever the pets meet normally).
+The kitten logic gates sound more optimal, but I want to see where this leads.
-As I design each gate, I'll explain what to link the SET and CLEAR inputs and the OUTPUT to.
+You would build the memory gate on top of a reservoir, aquifer, or ocean. I'll explain what to link the SET and CLEAR inputs and the OUTPUT to if/when I come up with designs for the rest of the logic gates. :P
-Note: It is possible for both the SET and CLEAR outputs to be triggered at the same time on the memory gate with these designs. With the water-based memory gate, this may result in an unpredictible output for a small amount of time. With the kitten based gate, well, I'm not sure what the kitten will do. The hatch would be open, so it couldn't try to go to the door, but would it try to walk up to the hatch, or would it keep standing on the pressure plate until the hatch closed?
-Also, these gates are only theoretical and have not yet been tested.
-So far, from the NOT gate's design, it looks like these would probably respond slowly (slower than water gates), and would disrupt dwarf tasks on top of it. Not so good. Hmm.
 === NOT gate ===
   ###
- B^B
+  ^
- B^B
+  ^
- B^B
+  ^
-  O#O
+  ###
-  FvF
+  DvD
-  FvF
+  DvD
-  FvF
+  DvD
   ###
-'O': Service doors, normally locked - so that you can get in to perform maintenance on the pressure plates and whatnot.
+INPUT : All the doors, labelled D. Your input is some lever, or something else, which you want to negate the value of.
-INPUT : All the floodgates, labelled F, and the bars or grates, labelled B. Your input is some lever, or something else, which you want to negate the value of.
+SET OUTPUT: 'v' tiles are pressure plates set to detect dwarves, linked to the SET output on a memory gate. They are given a pathing priority with the highest possible value (Important!).
-SET OUTPUT: 'v' tiles are pressure plates set to detect dwarves, linked to the SET output on a memory gate. They are given a pathing priority with the highest possible value (Important!). They should each also be linked to the adjacent 'F's or 'B's in case a dwarf is trapped inside.
+CLEAR OUTPUT: '^' tiles are pressure plates set to detect dwarves, linked to the CLEAR output on a memory gate. They are given a pathing priority with the lowest possible value (Important!).
-CLEAR OUTPUT: '^' tiles are pressure plates set to detect dwarves, linked to the CLEAR output on a memory gate.
 How it works: If the INPUT is ON, the doors are opened, and newly calculated paths will be routed over the SET OUTPUT pressure plates. If the doors are closed, newly calculated paths will be routed over the CLEAR OUTPUT pressure plates instead. This will unfortunately cause dwarves who have already calculated a path through the now-closed doors to run into the doors and exclaim "WTF."
-That's all so far. From the looks of it, it probably isn't worth working on any further, so I wouldn't expect anything further on this page.