Forums - Open Redstone Engineers
2 tick CCA! - Printable Version

+- Forums - Open Redstone Engineers (https://forum.openredstone.org)
+-- Forum: ORE General (https://forum.openredstone.org/forum-39.html)
+--- Forum: Projects & Inventions (https://forum.openredstone.org/forum-19.html)
+---- Forum: Completed Projects (https://forum.openredstone.org/forum-21.html)
+---- Thread: 2 tick CCA! (/thread-12890.html)



2 tick CCA! - Zijkhal - 08-07-2017

It pretty much is the 3 tick CCA (by Alex_You, Koyarno, Nikkeru_), but desynced (and a bit of redesign for LSB), so the comparators at the end receive an updated signal only 1 tick after the inputs are received, but because minecraft, the comparators use the signal values from 1 tick later for the output, so even though the carry signal reaches the comparators 2 ticks after the input, the comparator instantly uses that for its output. (I'd argue its not quite insta-logic, as this one does not go to great lengths to exploit the insta-comparators, simply uses the natural desynced nature of the adder to get one semi-instant comparator (only instant for one of the comparator inputs))

To be extra safe, unpower the adder before a next number is fed, but that may not be necessary

You can find it in the middle of my plot (ZCube), I have a raw, paste model, and a check it if you dont belive me one Wink


RE: 2 tick CCA! - Koyarno - 08-07-2017

(08-07-2017, 08:51 PM)Zijkhal Wrote: To be extra safe, unpower the adder before a next number is fed, but that may not be necessary

can you please test all state desyncs, since being always consistent is a cca trademark kinda


RE: 2 tick CCA! - Zijkhal - 08-08-2017

(08-07-2017, 09:09 PM)Koyarno Wrote:
(08-07-2017, 08:51 PM)Zijkhal Wrote: To be extra safe, unpower the adder before a next number is fed, but that may not be necessary

can you please test all state desyncs, since being always consistent is a cca trademark kinda

How should I do that? Test with all 4 input options, each with / without Carry in from the previous half-adder?

Logged back in, with the exact same test inputs now Cout does not wanna work like it did yesterday, copy pasted it to a different spot, now MSB is 1 tick late compared to the rest, but works fine on the one I copied, like what is going on? Are these comps really that finicky?


RE: 2 tick CCA! - LambdaPI - 08-08-2017

They are. I once made "3 tick" cca that used a similar concept.