Giter VIP home page Giter VIP logo

turing's Introduction

Opus as a Turing Machine

DOI

Given only a series of input tapes, Opus learns to compute solutions for the A::B problem with 100% accuracy at 24 steps, and Rule 110 for a 12-token tape over 12 steps (accuracy over large runs not yet measured).

See:

turing's People

Contributors

ctjlewis avatar victortaelin avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

turing's Issues

fix: loop indicator token unstable for Rule 1

Again, a really weird example of the copy error.

The last test run showed 4 errors, but it was actually the same error for Rule 1 four times. The batch start index was wrong after the refactor, it basically ran the same tests over and over again. Whoops.

For Rule 1 (and presumably other 1-y rules that were not tested, e.g. 11, 111), the LOOP token fails to indicate the following sequence correctly, and the model writes a 1. It's pretty hard to understand how it makes this mistake, since it has never seen a one in that position, but again I chalk it up to it having its attention balanced between several other things at once and it being slightly overwhelmed. Hard to reach a more technical conclusion at this point.

2024-04-21T22:37:02.4949028Z TAPE 1/9 0░ 1░ 2░ 3░ 4░ 5█ 6█ 7█ 8█ 9█                       | TAPE 1/9 0░ 1░ 2░ 3░ 4░ 5█ 6█ 7█ 8█ 9█                      
2024-04-21T22:37:02.4949791Z PRINT 1/9 ░ ░ ░ ░ ░ █ █ █ █ █                                | PRINT 1/9 ░ ░ ░ ░ ░ █ █ █ █ █                               
2024-04-21T22:37:02.4950371Z LOOP                                                         | LOOP                                                        
2024-04-21T22:37:02.4951008Z   ░  0░  1░  ░ ░ ░: 0 → █   0█                               | 1    

Goal will be to adjust the tape so this transition is less error-prone somehow, from the PRINT to the looping over the indices.

patch: automata issues

Notes for later.

Run:
https://github.com/SpellcraftAI/turing/actions/runs/8773913109

Logs:
https://productionresultssa8.blob.core.windows.net/actions-results/f7cbc876-64e1-488f-8a9e-402f25624733/workflow-job-run-9995a1ec-1db8-510e-fb2a-93c27ceb2b21/logs/job/job-logs.txt?rsct=text%2Fplain&se=2024-04-21T19%3A50%3A13Z&sig=3RrB4tjMVVg3vHMhV1%2BB%2BLLkbslsRMZpsSeSE34x9Iw%3D&sp=r&spr=https&sr=b&st=2024-04-21T19%3A40%3A08Z&sv=2021-12-02

Errors: 6

  • 4x "Five" hallucination.[1]
  • 2x Spaces padding for TAPE statement.[2]

[1]

2024-04-21T17:41:57.7013398Z TAPE 5/9   0█ 1░ 2█ 3░ 4█ 5█ 6█ 7█ 8░ 9█                     | TAPE 5/9   0█ 1░ 2█ 3░ 4█ 5█ 6█ 7█ 8░ 9█                    
2024-04-21T17:41:57.7014289Z PRINT 5/9   █ ░ █ ░ █ █ █ █ ░ █                              | PRINT 5/9   █ ░ █ ░ █ █ █ █ ░ █                             
2024-04-21T17:41:57.7014817Z                                                              |                                                             
2024-04-21T17:41:57.7015386Z   ░  0█  1░  ░ █ ░: 2 → █   0█                               | 5

[2]

2024-04-21T19:16:37.1773857Z TAPE 0/9   0░ 1░ 2░ 3░ 4░ 5░ 6░ 7░ 8█ 9█                     | TAPE 0/9  0                                                 

patch: termination index

Again, own notes for later.

This shows a good example of how sensitive this system is to copy errors given everything that it's doing at once.

2024-04-21T20:53:54.1557534Z TAPE 0/9 0░ 1░ 2░ 3░ 4░ 5█ 6░ 7█ 8░ 9░                       | TAPE 0/9 0░ 1░ 2░ 3░ 4░ 5█ 6░ 7█ 8░ 9░                      
2024-04-21T20:53:54.1558294Z PRINT 0/9 ░ ░ ░ ░ ░ █ ░ █ ░ ░                                | PRINT 0/9 ░ ░ ░ ░ ░ █ ░ █ ░ ░                               
2024-04-21T20:53:54.1558862Z LOOP                                                         | LOOP                                                        
2024-04-21T20:53:54.1559498Z   ░  0░  1░  ░ ░ ░: 0 → ░   0░                               |   ░  0░  1░  ░ ░ ░: 0 → ░   0░                              
2024-04-21T20:53:54.1560163Z  0░  1░  2░  ░ ░ ░: 0 → ░   1░                               |  0░  1░  2░  ░ ░ ░: 0 → ░   1░                              
2024-04-21T20:53:54.1560950Z  1░  2░  3░  ░ ░ ░: 0 → ░   2░                               |  1░  2░  3░  ░ ░ ░: 0 → ░   2░                              
2024-04-21T20:53:54.1561585Z  2░  3░  4░  ░ ░ ░: 0 → ░   3░                               |  2░  3░  4░  ░ ░ ░: 0 → ░   3░                              
2024-04-21T20:53:54.1562216Z  3░  4░  5█  ░ ░ █: 1 → █   4█                               |  3░  4░  5█  ░ ░ █: 1 → █   4█                              
2024-04-21T20:53:54.1562850Z  4░  5█  6░  ░ █ ░: 2 → █   5█                               |  4░  5█  6░  ░ █ ░: 2 → █   5█                              
2024-04-21T20:53:54.1563478Z  5█  6░  7█  █ ░ █: 5 → █   6█                               |  5█  6░  7█  █ ░ █: 5 → █   6█                              
2024-04-21T20:53:54.1564128Z  6░  7█  8░  ░ █ ░: 2 → █   7█                               |  6░  7█  8░  ░ █ ░: 2 → █   7█                              
2024-04-21T20:53:54.1564918Z  7█  8░  9░  █ ░ ░: 4 → █   8█                               |  7█  8░  9░  █ ░ ░: 4 → █   8█                              
2024-04-21T20:53:54.1565580Z  8░  9░   ░  ░ ░ ░: 0 → ░   9░  9/9                          |  8░  9░   ░  ░ ░ ░: 0 → ░   9░  8       

Somehow, the termination index is actually what's breaking here. It will always be the same as the last index, in this example, 9/9, because the tape's final index is 9:

9░  9/9

Yet it writes:

9░  8  

And probably was going to write 8/9 or 8/8 (the tape is currently stopped when there's an error). Either way, it's a surprising error to make, since the correct token is only 2 or 3 tokens away, 9[token] 9/9.

So, this has to be changed. There still should remain a stop token, but it will not be the index. I assume (hope) it's just one too many numeric series to keep track of, and just attending to the final missing position:

8░  9░   ░ [IMPLIES STOP]

Might help, though the hope was that including the index would allow for it to learn the association of the final index as the stop token for that step in the training set, and removing it may make it stop the loop less reliably, which would be a problem.

Will try to change to a separate unique token. In past situations with this problem, when it's this stable and just on the edge, removing a little bit of data from each step log can get it over the finish line.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.