.
FRDCSA | internal codebases | Manager
Homepage

[Project image]
Manager

Architecture Diagram: GIF
Code: GitHub

Jump to: Project Description | Parent Description | Capabilities

Project Description

Manager has evolved to be a central component in the FRDCSA design, although it isn't yet operational.

Communication with other systems involves: carrying on dialogs with the user (Audience) to accomplish tasks (PSE) via plans (Verber) and other planning modules (BusRoute / Event-System / Meeting / etc). However, it must know certain things about the user's habits (RSR), preferences (CRITIC), background knowledge (CLEAR), and environment (PhysicalSecurity / Machiavelli), in order to synthesize coherent schedules.

Here is a sample of the presence detection system in action:

	Broadcast, person has arrived at 20050109211125
	Broadcast, person has departed at 20050109211131
	Broadcast, person has arrived at 20050109211141
	Broadcast, person has departed at 20050109211206
	Broadcast, person has arrived at 20050109211208
	Broadcast, person has departed at 20050109211351
	Broadcast, person has arrived at 20050109211404
      

It will therefore autonomously execute certain actions: for instance, briefing the user on destination and safety before driving, tasks upon waking up, initiating sleep learning, reminding the user to perform basic chores when appropriate, frequent hand exercise, bathroom and sleep breaks, keep a polyphasic sleep schedule,

It derives much, conceptually, from the Friday and Electric Elves system from ISI, as well as many other awareness systems. Currently, it interacts heavily with MKAS, and in the future will provide capabilities to SVRE.

To quote a rather illicit source as read to me by CLEAR: The Magician must therefore take the utmost care in the matter of purification, "firstly", of himself, "secondly", of his instruments, "thirdly", of the place of working. Ancient Magicians recommended a preliminary purification of from three days to many months. During this period of training they took the utmost pains with diet. They avoided animal food, lest the elemental spirit of the animal should get into their atmosphere. They practised sexual abstinence, lest they should be influenced in any way by the spirit of the wife. Even in regard to the excrements of the body they were equally careful; in trimming the hair and nails, they ceremonially destroyed the severed portion. They fasted, so that the body itself might destroy anything extraneous to the bare necessity of its existence. They purified the mind by special prayers and conservations. They avoided the contamination of social intercourse, especially the conjugal kind; and their servitors were disciples specially chosen and consecrated for the work.

Capabilities

  • Fix issue with resource-manager not working.
  • Can apply the action learning stuff that I develop to the logging mechanisms of manager/Guardian,etc.
  • manager: use command-log-mode.el package to record which commands are being invoked.
  • resource-manager: rbsla_prebuilt_0.2.zip
  • Implement something that sends a message to the notification manager - which should interface with the world-state-monitor - when say the erc client finishes loading, etc, as notifications.
  • Note that more important than resource-manager is js-rapid-response
  • Have the SPSE2 IEM2 system integrate with the manager system that records task completion, have it note how long it took for a task to get completed, apply machine learning to predict the length of the tasks based on the description and other slots, then analyze existing plans and put an estimated range on the duration in order to help with the planning process.
  • Make it so you can sync a buffer with the phone software, so you can edit in a to.do file stuff that will be executed with the interactive execution manager.
  • Use KNext on equipment manuals to extract properties that apply to the inventory manager.
  • For now, write inventory manager to not use freekbs2, make it work with Flora2 instead.
  • For workhorse, use GATE as the corpus manager, etc.
  • Add exception handling to manager::Dialog stuff.
  • Actually make use of kbfs and databases as well for data-manager.
  • Add to data-manager the gamer planner/game player
  • Add to data-manager the ability to handle backups across multiple machines.
  • The inventory manager should also include semantic data about the products, such as product manuals, etc.
  • Create a function for pulling SPSE2 to the forefront of the window manager
  • Notification-manager, hey
  • Notification-manager, blahblah
  • Notification-manager, echo hi
  • Notification-manager, hi
  • Notification-manager, restart
  • Agenda: manager> manager working> Fri Sep 24 14:09:00 CDT 2010
    ("due-date-for-entry" "150451" "1 hours")
  • Agenda: manager> manager working> Fri Sep 24 14:08:00 CDT 2010
    ("due-date-for-entry" "150448" "1 hours")
  • Agenda: manager> manager working> Fri Sep 24 14:06:00 CDT 2010
    ("due-date-for-entry" "150441" "1 hours")
  • Agenda: manager> manager working> Fri Sep 24 14:05:00 CDT 2010
    ("due-date-for-entry" "150439" "1 hours")
  • Agenda: manager> manager working> Fri Sep 24 14:04:00 CDT 2010
    ("due-date-for-entry" "150436" "1 hours")
  • Agenda: manager> manager working> Fri Sep 24 14:03:00 CDT 2010
    ("due-date-for-entry" "150432" "1 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 22 06:00:00 CDT 2010
    ("due-date-for-entry" "150200" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 15 06:00:00 CDT 2010
    ("due-date-for-entry" "149574" "3 hours")
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Wed Sep 1 06:00:00 CDT 2010%' 148684" "3 hours")
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 1 06:00:00 CDT 2010%' 148685" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 1 06:00:00 CDT 2010
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Wed Sep 1 06:00:00 CDT 2010
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 25 06:00:00 CDT 2010
    ("due-date-for-entry" "148241" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 18 06:00:00 CDT 2010
    ("due-date-for-entry" "147935" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 11 06:00:00 CDT 2010
    ("due-date-for-entry" "147372" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 4 06:00:00 CDT 2010
    ("due-date-for-entry" "146073" "3 hours")
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Sun Aug 1 06:00:00 CDT 2010
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Fri Jul 30 19:22:21 CDT 2010
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jul 21 06:00:00 CDT 2010
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jul 14 06:00:00 CDT 2010
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jul 7 06:00:00 CDT 2010
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 30 06:00:00 CDT 2010
    ("due-date-for-entry" "142916" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 23 06:00:00 CDT 2010
    ("due-date-for-entry" "141254" "3 hours")
  • Notification-manager, this is a test
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 16 06:00:02 CDT 2010
    ("due-date-for-entry" "140651" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 9 06:00:00 CDT 2010
    ("due-date-for-entry" "140105" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 2 06:00:00 CDT 2010
    ("due-date-for-entry" "138465" "3 hours")
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Tue Jun 1 06:00:02 CDT 2010
    ("due-date-for-entry" "138383" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed May 26 06:00:00 CDT 2010
    ("due-date-for-entry" "137975" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed May 12 06:00:00 CDT 2010
    ("due-date-for-entry" "136464" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed May 5 06:00:00 CDT 2010
    ("due-date-for-entry" "135377" "3 hours")
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Sat May 1 06:00:01 CDT 2010
    ("due-date-for-entry" "134268" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Apr 28 06:00:00 CDT 2010
    ("due-date-for-entry" "133925" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Apr 21 06:00:00 CDT 2010
    ("due-date-for-entry" "132391" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Apr 14 06:00:00 CDT 2010
    ("due-date-for-entry" "131135" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Apr 7 06:00:00 CDT 2010
    ("due-date-for-entry" "129524" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Mar 10 06:00:00 CST 2010
    ("due-date-for-entry" "127301" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Mar 3 06:00:00 CST 2010
    ("due-date-for-entry" "127264" "3 hours")
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Mon Mar 1 06:00:00 CST 2010
    ("due-date-for-entry" "127156" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jan 13 06:00:00 CST 2010
    ("due-date-for-entry" "125600" "3 hours")
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Fri Jan 1 06:00:00 CST 2010
    ("due-date-for-entry" "125517" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 23 06:00:00 CST 2009
    ("due-date-for-entry" "125173" "3 hours")
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Tue Dec 1 06:00:00 CST 2009
    ("due-date-for-entry" "124395" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Nov 25 06:00:00 CST 2009
    ("due-date-for-entry" "122100" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Oct 28 06:00:01 CDT 2009
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Oct 21 06:00:00 CDT 2009
    ("due-date-for-entry" "115401" "3 hours")
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Thu Oct 1 06:00:00 CDT 2009
    ("due-date-for-entry" "114544" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 30 06:00:00 CDT 2009
    ("due-date-for-entry" "114455" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 19 06:00:00 CDT 2009
    ("due-date-for-entry" "113535" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jul 8 06:00:00 CDT 2009
    ("due-date-for-entry" "113214" "3 hours")
  • Agenda: myfrdcsa/codebases/internal/manager/systems/todo/doc/check-on-these> Mon Jun 1 06:00:00 CDT 2009
    ("due-date-for-entry" "112963" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Mar 4 06:00:00 CST 2009
    ("due-date-for-entry" "107857" "3 hours")
    ("skipped" "107857")
  • Build in encryption for android phone manager software.
  • Write a report system for how on task we are based on the manager agenda system.
  • Add a capability to know what NOT to say in public for Android TTS manager system.
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Feb 11 06:00:00 CST 2009
    ("due-date-for-entry" "105776" "3 hours")
    ("skipped" "105776")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Feb 4 06:00:00 CST 2009
    ("due-date-for-entry" "105394" "3 hours")
    ("skipped" "105394")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jan 21 06:00:00 CST 2009
    ("due-date-for-entry" "104701" "3 hours")
    ("skipped" "104701")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jan 14 06:00:00 CST 2009
    ("due-date-for-entry" "104473" "3 hours")
    ("skipped" "104473")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jan 7 06:00:00 CST 2009
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 31 06:00:00 CST 2008
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 24 06:00:00 CST 2008
    ("due-date-for-entry" "103811" "3 hours")
    ("skipped" "103811")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 17 06:00:00 CST 2008
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 10 06:00:00 CST 2008
    ("due-date-for-entry" "102069" "3 hours")
    ("skipped" "102069")
  • Have manager todo know how much notification is necessary for a goal. Develop goal types.
  • Switch the current manager::Scheduler2 system for monitoring crontab with a inotify or whatever.
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 3 06:00:00 CST 2008
    ("due-date-for-entry" "99534" "3 hours")
    ("skipped" "99534")
  • Fix problem with manager::Scheduler2 asserting things like KBS, MySQL:freekbs:default assert ("due-date-for-entry" "" "5 minutes")
    ("due-date-for-entry" "99181" "3 days")
    ("completed" "99181")
  • General the contact features of manager to any agent... and then use the audience tell told stuff. In fact that is the basis for the AA.
  • manager or verber should have a "keep the airplane flying" mentality in terms of providing a certain service level.
  • If manager requires to contact the user and the user is not available, and sound is not getting a response, trying flashing your screen.
  • I think manager::Records::Context may have some bugs, specifically related to how it calculates the score.
  • Note that in order to determine whether something is working, we look at a few simple things. We know what the work context is from manager, and we know what the current tasks are from score/pse this new thing. So, just ask them from time till time what they got done. Another thing is if a file that is associated with a task is closed, we can queue a question about that task!.
  • Here is a nifty idea, we can merge systems like manager and score, just by moving score stuff into the manager dir and renaming the container variables.
  • manager::Records::Context and manager.el logging mechansism has been completed.
  • Get a basic task manager thing going, and use manager::Context for it?
  • The metadata for session logs for manager Emacs Session stuff is not staying.
  • Have a reset window function in the task manager. The task manager is essentially like a cockpit which indicates various activities and how well they are proceeding.
  • Actually, we should eventually factor out the manual code that is making the classifications, and replace it with manager::Dialog code, so that the whole system is more complex. And, to boot, we should replace manager::Dialog with audience, so that everything is smarter. audience should use theorem proving to determine which context it is operating in.
  • Before releasing akahige, get free exercise information for the personal stretch manager. all systems must be checked for information sources using license management system.
  • manager or diamond should autodetect interaction hardware.
  • Just now I imagined accidentally dying at my computer, and that my computer would say, "Andy, are you there?" and some time later repeat itself. Afterwards it would conclude that I wasn't and try to contact a friend of mine to see where I was, but it would conclude there was no way to access them (no networking etc). That could be how manager/audience work a little bit.
  • I don't have nearly as much done as I want because I'm trying so hard to get this manager thing working. With my new keyboard, as soon as my pinky has more time to heal, I'll start doing typing tests.
  • Actually we should eventually factor out the manual code that is making the classifications, and replace it with manager::Dialog code, so that the whole system is more complex. And, to boot, we should replace manager::Dialog with audience, so that everything is smarter. audience should use theorem proving to determine which context it is operating in.
  • Implement dribble file as part of manager Emacs session
  • Eventually should get meal planner working. I think for starters, only get pgourmet going strong. I could do that as soon as pverber was operating nominally. There is still a lot of work to be done on manager's end to get it working.
  • Then, we can have something that reminds the user, i.e. adjustable autonomy. Obviously this is manager specific.
  • Add features to manager that enable it to issue instructions to the user before they go to sleep about what to think/dream about consistent with their pse.
  • Insert all sorts of hooks for manager/pse to know the current working context.
  • Here are some ideas. all we need now is a simplistic goal system, built from the ground up, _maybe_ with some basic common sense. On the other hand, then, we should get the event logging system working, and write helper functions, EventLog, etc, so that other systems can make use and analyze log data easier. We should generalize the functions found in sinless and manager that make use of the score event system, (moving that of course into the eventlog). problemspace should visualize the eventlog data, using nodebrain type filtering. That stuff has to work inferentially.
  • Let's get manager going by turning him into a unilang agent and allowing him to send messages, or execute programs. For instance, if the daily items haven't been done by the end of the day, manager reports that.
  • Should port the TTS component of clear to manager and have clear operate the manager::Dialog API)
  • Need to agentify manager and have him running. He will conduct verber.
  • manager dribble files are working now
  • The new svrs functionality belongs in manager.
  • If nothing the user has done anything in a while, manager can try to estimate, based on schedules and historical information, whether they have fallen asleep, and set the alarm in that case - especially so they don't miss anything.esh
  • Perhaps the identity manager could automatically fill out accounts.
  • Note that problemspace should not come on if we are in a recording session from manager.
  • Add emotions to manager...
  • The new svrs functionality belongs in manager.
  • Set up manager/memax to record session strokes in dribble file automatically.
  • Have manager alarm check for internet access before running ntpdate.
  • Implement an emacs interface to manager::dialog (subsetselect, etc)
  • Get manager alarm to get gradually louder.
  • From estimating sleeping times, can initiate SBAGEN, as well as other manager things.
  • The metadata for session logs for manager Emacs Session stuff is not staying.
  • Could write a manager::Dialog interface for unilang.
  • Implement dribble file as part of manager Emacs session
  • If manager requires to contact the user and the user is not available, and sound is not getting a response, trying flashing your screen.
  • manager dribble files are working now
  • Get a manager::dialog SRS going
  • manager or verber should have a "keep the airplane flying" mentality in terms of providing a certain service level.
  • Use must switch be able to through various applications, and this activity (through the window manager) must be detected
  • Use manager for polyphasic sleep schedule
  • Get a basic task manager thing going, and use manager::Context for it?
  • Essentially change manager into a kind of robot with sensors, effectors, and reasoning.
  • We will build a flight simulator for problem solving, and use the existing manager and score frameworks for reporting things.
  • Here is a nifty idea, we can merge systems like manager and score, just by moving score stuff into the manager dir and renaming the container variables.
  • I think manager::Records::Context may have some bugs, specifically related to how it calculates the score.
  • manager::Records::Context and manager.el logging mechansism has been completed.
  • Add current buffer detection to manager-check-windows
  • Have to get that manager task logging stuff up and running.
  • Compute formula for changing manager's expectations for check
  • Implement items for manager to select the general type of task, e.g. reading software, reading manuals, writing software, etc.
  • The manager should send messages to pop up the task list when there is a decrease in task joint entropy and it is below acceptable levels.
  • Therefore expand on the event system for manager.
  • Just have to unilang enable manager/Spark
  • We need a data set manager.
  • Every calling point to manager Dialog could have its own ID or something, and that would assist the learning.
  • Fix the close-window hook in manager.el
  • For manager::Records::Contexts, can probably inspect the ttyrec file for content that is useful to establish information.
  • Make sure manager::records::context does not record passwords.
  • The manager program that records what you actually workon (actually maybe part of backwatcher), should record every change it thinks it sees you make, and then try to detect and label insignificant one's, and approve that with the user, for a specific task.
  • There should be an FAQ manager (RTFM) setup to answer these.
  • To speed things up, I could have a dialog manager.
  • manager should see this: http://taint.org/wk/ViaVoiceModernLinux
  • Replace existing manager context system with a more unified, pid file like based system.
  • manager::Context should characterize the work as education, training, etc.
  • Therefore, have a project manager for work that schedules different activities related to work according to the rules inherent.
  • Add to manager::Records::Context timesheet functionality a summarization of the tasks accomplished as referenced to my internal systems.
  • manager should see what people are working on (if task joint entropy is not high enough) - to tell them what they should work on because it has high priority but it is being neglected.
  • Figure out how to automate control of the window manager from Perl, then we are done!
  • manager::Records::Context should be secured.
  • remember /var/lib/myfrdcsa/codebases/releases/manager-0.1/manager-0.1/scripts/normal-form/data.pl
  • For manager::Records::Context lookup-tasks-for-file.pl, doing bayesian classification or something.
  • Fix the problem with manager session record.
  • manager::Records should use Term::TtyRec
  • Write a function to list which files we've been viewing, part of manager.
  • Generate automatic manager::Records::Session overviews.
  • Fix problem with Emacs manager::Record::Session stopping at 140
  • Next I need to improve manager to the point where it can direct me to do certain things at certain times.
  • manager or diamond should autodetect interaction hardware.
  • Humorous facts, I have written so many systems now that there are name conflicts between them, for instance "Cyc-Mode" and "corpus manager" are both abbreviated cm.
  • The manager::Records::Session system can zoom to the nearest complete clear screen in order to begin to reconstruct a given location.
  • audience will be necessary for job-search, and even manager if I recall correctly.
  • /var/lib/myfrdcsa/codebases/internal/unilang/start audience broker clear corpus cso ELog manager OpenCyc pse unilang-Client
  • Insert all sorts of hooks for manager/pse to know the current working context.
  • A clever way to make my system smarter is by using manager::Dialog to record all decisions, per application, in a database.
  • Use rememberance-agent code for manager context classification
  • Have manager::Scheduler2 be able to automatically reload crontab.
    ("completed" "86467")
  • Setup speech recognition for over the phone, so that manager can call me and ask questions.
  • Create a finance manager system, apart from broker
  • do project archeology on the FRDCSA. for instance, manager/scripts/misc-scripts is full of historic scripts
  • Develop a software (part of manager) that displays todo list items after every shell, kind of like the new mail feature. Figure out how to do this.
  • Get manager working reliably contacting user about stuff.
    ("depends" "74494" "74493")
  • pushd /var/lib/myfrdcsa/codebases/internal/manager
  • find a memory manager
    ("depends" "73704" "73995")
  • Lifenet looks good for manager, etc.
    ("critic-unilang-classification" "66434" "deleted")
  • The boycott manager should take websites like the Washington Post into account, who are trying to ban stuff, etc.
  • manager: I'm going to Oberweis Ice Cream to purchase milk and yogurt, and then tonight on to Gaelic lessons.
  • Write inventory manager (for van, etc.)
  • Get radar-queue-system to work differently, instead inserting into freekbs, and then having the system periodically prompt to download these. That task can come up under the task manager frequently
  • Integrate brainleach into manager Records Session
    ("completed" "25348")
  • Grecipe-manager looks pretty good.
    ("unilang-message-classify" "23586" "observation")
  • Make a password manager that assists with changing all passwords, remembers when to do it, and assists with executijng it.
  • Since manager will be in regular contact with the user, a feature should be that if the user does not check in with manager and has not let it know that they will be out of contact, that manager can contact some people letting them know it does not know where the user is.
  • Implement manager::Dialog in emacs i.e. manager-dialog
  • manager should use DBUS
  • Create a system for scheduling user actions. Use manager to contact the user.
  • Add Weather::Com stuff to manager, for knowing when to go outside.
  • Emacs-Client, ps manager: User has departed
  • Emacs-Client, ps manager: User has arrived
  • ps manager: User has departed
  • ps manager: User has arrived
  • For instance, manager could send commands to take over the Emacs screen (preferably waiting for no communications for a while.) Also for instance, when problemspace shows items.
  • Maybe manager could display the estimated user state within Emacs, for instance, just now I was scratching my foot.
  • manager::Record::Session should also monitor other students and I watch them, and we comment on each other's tasks that way.
  • Code monkey could learn from manager - since manager will be tracking high levels goals.
  • I sense the need for a new system - clear determines whether you have read the appropriate stuff - but have you acted on this knowledge? There is a need for a "project manager" that will help with hands on development of various systems. This ties in nicely with our project since we could use this to get people resume valuable experience as well as build us systems we need.
  • manager should start up busroute in the morning.
  • User can report when they first feel that something is due - for instance - my beard is too long, or I have to go to the bathroom, or my nails are too long. Then manager should learn these periods.
  • manager should be able to set alarms - like - I'll work on this project for the next so and so minutes.
  • I finally remembered the idea - manager could use the light of the screen - and maybe make it dark during the night - but start it up again and flash it so as to help wakeup the person.
  • manager could know when the user absolutely needs to get and be sure of it. There was another decent idea about manager but I was too tired to write it down. We need to set up audio recording.
  • Here are some other features that might be of use to manager - wake the user usijg an increasingly load signal. Also, record sleep times.
  • manager may wish to record events instead of RSR.
  • Another idea is that verber::manager should take care to know all the different types of interfaces that the user may be interacting with it, and scale down to these. For instance, there is full computer, bidirection speech, TTS and keybrd entry, yes/no, all the way to none - just memory - etc,etc. verber should have special planning domains for which devices will be used at what times and how the plan data will be transferred.
  • I would very much like manager to record a trace of what work I am accomplishing. This will be useful for the self-assessment purposes of RSR as well.
  • Lastly, getting manager working is important in general.
  • We want to see how often I am being distracted and manager should monitor this.
  • should be able to simply tell manager what time you need to be at work, and using verber, etc, manager schedules the bus, and the wake up time, then wakes you up, does all morning activities, informs you of time critical events (busride, etc), and drives you into work. This is one of the best examples of weak AI growing I've done yet. That's non-trivial, but major issues remain.
  • manager alarm should start quiet first, to give user chance to kill it
  • manager must have hypothesis generation and testing to determine the user's state.
  • manager's alarm should play a test to verify sound before going to bed.
  • If nothing the user has done anything in a while, manager can try to estimate, based on schedules and historical information, whether they have fallen asleep, and set the alarm in that case - especially so they don't miss anything.esh
  • That would be part of manager, I believe, and it can model what you know and use this as a rule to order tasks.
  • Could tell manager to do this.
  • radar needs to be developed so that it can also try to lookup various components. To be honest, why don't I write radar as an NPDDL tonight, perhaps before or after I get manager doing that sleep learning stuff. Justin could use that sleep learning stuff.
  • Hilarious the way everything does fit together, I never liked world manager.
  • have manager use sbagen to attempt to correlate dream stages using binaural beats.
  • We can do a few things - we can study public policy. We can also ask people to head up given project areas - to be the manager of such and such component of the AI.
  • manager can infer from learned network traffic the absense of the user and guess then at where they are, for instance, asleep.
  • Develop a planning domain for manager to be able to do certain things, like, obviously, for instance, when I go to sleep, start all computation intensive processes on my personal machine.
  • We can integrate learning into all the manager::Dialog components, by adding additional information to the arguments, and logging the results :)
  • Fix bug where manager doesn't check whether a camera is attached. Add it to hooks for when the Camera is attached.
  • Add boss detection to manager (dogbert intrusion detection)
  • manager should probably maintain the schedule?
  • Factor out TTS server to be part of manager? Or its own seperate system, and then have it connect to the server. Write standard MAS libraries.
  • Note that opencv face detection and hence manager presence detection does not work at night.
  • Should have several things operational: one of them is that when manager says, work on your typing, should then ask for a WPM? No because, it should actually make them more concerned with not making any errors that with typing fast.
  • The request - can I go to a bathroom, should be translated to a query, and then a plan to do so should be searched for. In addition, various other considerations might apply. Also, a dialog manager should be used to elicit these requests properly. For instance, if I say, "can I go to the bathroom", and the system says "no", and I say "why", this should be programmed so as to give a justification.
  • Use Cyc, eventually logicmoo to model world state. Make sure that we have to ask manager "permission" to do everything, and also all requests. manager, I am hungry. This initiates manager to plan for the world state. This calls the Cyc Agent for world state, which it sends to manager, who then sends the modified domain file to the verber agent, which then generates the plan, which is then returned to the manager agent.
  • manager can use its dialoging in order to gain my attention in order to perform normal chores like burning backup DVDs. Additionally, the sleep information can be used to opportunistically schedule tasks that need to be run whilst I sleep.
  • manager can use GPS information to determine waypoint arrival when guiding plans for verber.
  • It will be nice to go ahead and get this system operational so that Justin can have some good reading. Should assemble a bunch of nice texts for the lad - not ones that focus on survival so much - since he's inclined to abuse that - but one's that aim to build intellectual stamina - he should rate them! He has a fast enough computer to do voice recognition. Seth should provide us with the "Justin Coslor is the master of the universe stuff". To get programming I will work on manager and "fun" stuff as to focus only on gourmet is a mistake - since I dally.
  • (wget http://www.cc.gatech.edu/cpl/projects/objectspaces/ manager http://www.cc.gatech.edu/fce/ahri/ - commune http://www.cc.gatech.edu/cpl/projects/hid/ -)
  • (manager should have: (a) interruption recovery (helping you re-establish your context after an interruption))
  • (all of the sleep-learning stuff belongs with manager)
  • Here are some of the things we need to do next: fix the way pse craps out all the time, get Clairvoyance working and with some basic document management systems, including for instance authorized reports to ensure back to me that various people are learning various things (based on testing), find some way to get those recipes normalized, get shops up and running and taking inventory of everything I have, add this information to verber, get MDR (minimum detection route) planning operational, get new tagsets for AWB/Predator working, fix problem with script determining perl dependencies, make packages of my systems and upload, fix mini-dinstall problem, write tutorial on agentification, agentify or otherwise get command line bugzilla working, fix up manager with sleep learning capabilities, create a sample course for clairvoyance, and run backup. You're such a lazy guy, you know that?
  • Write emacs manager code for resumption of contexts when disturbed via buffers borrowing from existing academic work on this.
  • lockout must be part of disciple or manager, etc.
  • rough system to look back through the unilang logs for features, etc, to be called during development phases. high level prognosis of phases should be executed by boss via a manager module.
  • We are going to want the interactive tutor to use the same dialog-manager as verber, so clearly the dialog-manager is a separate system, it is probably filed under manager.
  • chronic will help with manager - it is very similar to what I was asking Sameer about just a little while ago. http://search.cpan.org/~vipul/Chronic-0.20/docs/chronicd.pod
  • Looking at what was actually programmed with manager, I became sort of distraught. It seemed as though nothing existed, and yet I recall doing all sorts of thought about it. What I suppose I didn't realize immediately is that there is still a huge specification embedded within my system. My exposure to outside forces has delayed my understanding of the system a little. And thus, t seemed to me to not be very imporatnt. It couldn't be further rom the truth.
  • Should create a temporary warez manager.
  • Some things to work on are dialog state managers. Also should have the manager system working soon, although I feel so something, its not a good feeling.
  • With the air conditioner, now I will be able to turn on some more computers. Best is to create the server room. Should first create a prototype of manager that uses "motion" and also a prototype of meeting that uses the microphone.
  • manager must start tracking soon when I awake and fall asleep. I guess the real problem is the data format?
  • manager should be tied into unilang. unilang should run as a server using /etc/init.d. The problem right now is unilang hogs the CPU cause of Event.pm insanity.
  • Some of the design notes for manager. It should be tied to verber, as in verber recommends moves and then these are sometimes acted out through manager. For now, however.
  • must keep in mind, for machiavelli, or manager, that management is not about telling someone what to do, it is about causing them to think in a way that makes the do it automatically.
    ("rejected" "95573")
  • Things remaining for gourmet: Finish XML generation code, clean it up. Find-or-create database standardization system, add to recipe managment. Find-or-create a queryable (XML|RDF) database to store recipeml files and provide utilities for searching. Write interface to SR16, as well as other modules and databases for nutrition calculation. Find-or-create solution to the nutrition management problem. Interface to pse to generate meal plans. Find-or-create reinforcement learning to model users tastes. Interface to manager to know when to review a meal. Look into open system for interactively managing food planning by providing a food preparation library.
  • should capabilities requests through radar automatically be recorded through unilang? I think they will certainly go through it since that is probably how it will communicate with the capabilities manager, etc.
  • Stress management should be part of manager. In fact, the tasks a particular system is designed to fulfull could be implemented as an HTN.
  • The manager systems functions as a goal planning system for persons, much like pse, only that the goals involve satisfying certain properties like getting enough rest, getting a good meal --- haha, we can integrate gourmet and manager here.
  • A natural thing to do is use manager to initiate shifts between fronts and goals that are generated by pse
  • I must say, that I wrote a letter today about becoming an interrogator, all of this when I could have been programming this pse system. This is obviously a problem and again, we must patiently, correctively bear through such mistakes. In general, writing should be avoided, programming should be encouraged. This ought to go in manager.


This page is part of the FWeb package.
Last updated Sat Oct 26 16:53:45 EDT 2019 .