amahabal/pyseqsee

Python framework for writing programs to solve complex problems not amenable to brute force. The architecture is a descendant of Douglas Hofstadter and Melanie Mitchell's Copycat architecture.

pyseqsee's Issues

Review LTM for extensibility

Need unit-test for pyseqsee_create_app

It is cumbersome to test this currently. This is the feature most liable to break with any changes in farg.core.

In batch mode viewer, show more details in left pane

The left pane only shows the input problems, and to get any sort of stats, one needs to click it.

Would be nicer to make that a tad more informative.

Setup all windows of the UI

• Button row at top;
• Menu-bar;
• Canvas;
• Mechanism to have multi-tiled UI;
• Commentry widget;
• Driven through config files.

Start creating tests for the new Bongard domain

Keep adding tests, so that we know that the code there works (although we cannot of course test that the documentation that goes with it produces that code...).

I should also get into the habit of running tests before submitting. I just did, and a Seqsee test broke sometime in the last two days, that I cannot fix today.

Seqsee flags polluting GetSubprocessArguments in batch and SxS

This may be easy to fix, but I have not investigated yet.

Add the subcommand "farg test"

Currently, I use nosetests, and do the following:

nosetests --pdb tests/ tests/seqsee

It would be nice to have "farg test", and best if it picked up files in the current directory instead of installed files.

Add screenshots to documentation

For instance, the batch mode execution with the pie charts and histograms showing will be useful to someone looking at the docs but not running the system.

LTM Viewer

The LTM viewer was removed because of its many dependencies. Redo in pure tkinter.

Create design-doc for multi-project version of Seqsee

As I wish to build a core FRAG library --- and make Seqsee but one instance of this --- I need careful planning. So a design-doc is in order.

Early exit when there are no more codelets

This would not occur in a "normal" app where routine codelets are continually being added, but I hit this in Bongard. Currently, there is a single codelet that is added once. After it is finished running, there is nothing left to happen: we should display a message and exit (as opposed to spinning wheels).

Create release for PyPi

To ease installation, PySeqsee should be released on PyPi. I've never done that before, so I'm hoping somebody could help out here.

farg.core.exceptions is a mess, fix that

Too much boiler-plate in definition of new spaces

This can certainly be cut down.

Imports don't work

For me, it doesn't run correctly, and causes import errors when I run, for example python3 farg/apps/seqsee/run_seqsee.py --sequence="2 3 5 7 11", and outputs \

Traceback (most recent call last):
File "farg/apps/seqsee/run_seqsee.py", line 14, in
from farg.apps.seqsee.batch_ui import SeqseeBatchUI
ImportError: No module named 'farg'

However, it works perfectly when run using python3 -m farg.apps.seqsee.run_seqsee --sequence="2 3 5 7 11". Would it be okay if I modify the documentation to reflect this? I'm not aware of a simple way to change the folder structure to make it work.

History: add a GUI viewer

Currently, there is a way to inspect history. When the --history flag is passed in, we drop into a python interpreter that can show a few things.

It would be nice to have a UI for that, would make it quicker to inspect things.

Check in the new numeric "bongard" demo app

The final code should accompany the step-by-step building of the app.

Refactor LTM, allow selective saving

Currently, when saving an LTM, the last state within current run is saved. It would be better to be able to push only the salient items and edges out instead of the whole graph.

This requires some rejiggering (mostly of LTM manager, but tweaking other LTM related classes is also a good idea)

Mailing list for bugs and checkins

Remove perl version?

Do you want to keep the perl version as part of the project? Or could I delete it or move it to a separate branch?

History: track more events and parents

The history is only as good as it records things faithfully. Currently, a few events get added to the history, but there are more things that we can do with tracking.

One kind of thing we track is various counts: this could be a low hanging fruit for things to add to history (mindful of not overdoing it and slowing things down a lot).

Add mission statemement

Change name

The current name, PySeqsee, doesn't reflect what this project has become, a library for creating projects using Hofstadter's ideas. Could we rename it throughout to something that better represents what it does?

Rewrite section on brief introduction

In batch mode, LTM seems always to be loaded

This should be controllable via a flag. There is a flag, but it does not get propagated well to inner runs, it seems.

Add documentation on farg command line tool

Modify documentation to describe the following features

• farg create <app> initializes an app
• farg remove <app> deletes an app's folder

Also add setup.py install step to install documentation.

History: more kinds of inspections

Currently, passing in --history, we drop into a python shell where we can poke around.

At this point, the full history is available, and thus one may in principle to any sort of exploration. However, utilities can make this easier. The shell already has some predefined things (such as s() for a summary of history). But more utilities to explore more aspects of history could be useful.

These should be written in a way that can be used from the GUI as well, once it exists (see #35). The current items are easily adaptable to that view.

Make updating docs easier

@amahabal could you modify the github pages settings so the root directory for the website is docs/_build/html? That way the docs would auto update by just doing make html, without switching over to the gh-pages branch and modifying it.

In documentation, make clear what is incomplete

Make it clear what is missing from the framework itself, and also what is missing from the documentation.

Write basic controller

Controller is the VM that the UI talks to; implement "Take one step" and such. It will throw exceptions for such things as "Need more terms".

Failure to run after refactoring; Import.Error: No module named ltm.node

Before the refactoring of the code and renaming of Spike --> IncreaseActivation, the test code ran.

After the refactoring, running the test code produces a crash-on-startup.

Error report is below.

---

Christophers-MacBook-Air:PySeqsee honey$ pwd
/Users/honey/Dropbox/Python/PySeqsee

Christophers-MacBook-Air:PySeqsee honey$ ls
COPYING README data docs farg scrap setup.py tests

Christophers-MacBook-Air:PySeqsee honey$ python3 farg/apps/seqsee/run_seqsee.py --sequence="2 3 5 7 11"
Initialized a GUI run mode
Traceback (most recent call last):
File "farg/apps/seqsee/run_seqsee.py", line 68, in
SeqseeMain().main(sys.argv)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/main.py", line 200, in main
self.ProcessFlags()
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/main.py", line 176, in ProcessFlags
self.run_mode = self.CreateRunModeInstance()
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/main.py", line 137, in CreateRunModeInstance
ui_class=self.gui_class)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/run_mode/gui.py", line 20, in init
stopping_condition_fn=stopping_condition_fn)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/apps/seqsee/gui/gui.py", line 47, in init
GUI.init(self, *_kwargs)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/ui/gui/init.py", line 52, in init
stopping_condition=stopping_condition_fn)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/apps/seqsee/controller.py", line 59, in init
Controller.init(self, *_args)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/controller.py", line 73, in init
self.ltm = LTMManager.GetLTM(self.ltm_name)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/ltm/manager.py", line 42, in GetLTM
ltm = LTMGraph(filename)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/ltm/graph.py", line 41, in init
self._LoadNodes(up)
File "/Users/honey/Dropbox/Python/PySeqsee/farg/core/ltm/graph.py", line 56, in _LoadNodes
node = unpickler.load()
ImportError: No module named ltm.node