.
FRDCSA | internal codebases | Manager

Manager Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

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

	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
      

Capabilities

• Fix problem with Emacs manager::Record::Session stopping at 140
• Need to start to schedule things, such as sbagen generations, book readings, etc. Use some kind of scheduling principle. Include meals, add to the manager component
• Write a function to list which files we've been viewing, part of manager.
• Fix the problem with manager session record.
• Generate automatic manager::Records::Session overviews.
• manager::Records should use Term::TtyRec
• 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.
• Add to manager::Records::Context timesheet functionality a summarization of the tasks accomplished as referenced to my internal systems.
• The manager::Records::Session system can zoom to the nearest complete clear screen in order to begin to reconstruct a given location.
• 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!
• It would be possible to setup the interactive execution monitor to function at my desk. Should be able to work with both manager and verber.
• Therefore, have a project manager for work that schedules different activities related to work according to the rules inherent.
• Replace existing manager context system with a more unified, pid file like based system.
• manager::Context should characterize the work as education, training, etc.
• manager should see this: http://taint.org/wk/ViaVoiceModernLinux
• Setup program to page me at a certain time. Add this to manager.
• There should be an FAQ manager (RTFM) setup to answer these.
• Todo issues explicit context switches. Uses manager context among others in order to enhance speed.
• To speed things up, I could have a dialog manager.
• pushd /var/lib/myfrdcsa/codebases/internal/manager
• Make sure manager::records::context does not record passwords.
• The part of manager that records commands and purposes can serve as a vital archive of howto information. Additionally, it should record the position in the file of the various points and be able to jump to the apropriate section to replay that on command.
• 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.
• For manager::Records::Contexts, can probably inspect the ttyrec file for content that is useful to establish information.
• Here are some good ideas. Maybe the manager::records::contexts can look at the stuff in the buffer to determine what is actually being worked on.
• Okay, now that this is working once again, that is good. We can now quickly adapt manager::Records::Context to work with my stuff at work.
• Fix the close-window hook in manager.el
• /var/lib/myfrdcsa/codebases/internal/unilang/start audience broker clear corpus cso ELog manager OpenCyc pse unilang-Client
• Every calling point to manager Dialog could have its own ID or something, and that would assist the learning.
• A clever way to make my system smarter is by using manager::Dialog to record all decisions, per application, in a database.
• One of these systems has to learn from example. It could be in manager, given the extent of related tools, but that's not quite the right idea. I think I need a system that records the script and breaks things into what the user entered as opposed to the program. Maybe use expect?
• We need a data set manager.
• Just have to unilang enable manager/Spark
• Therefore expand on the event system for manager.
• 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.
• Compute formula for changing manager's expectations for check
• 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.
• I think manager::Records::Context may have some bugs, specifically related to how it calculates the score.
• 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::Records::Context and manager.el logging mechansism has been completed.
• Add current buffer detection to manager-check-windows
• 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.
• 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.
• Have to get that manager task logging stuff up and running.
• Then, we can have something that reminds the user, i.e. adjustable autonomy. Obviously this is manager specific.
• 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.
• We will build a flight simulator for problem solving, and use the existing manager and score frameworks for reporting things.
• 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.
• 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!.
• Essentially change manager into a kind of robot with sensors, effectors, and reasoning.
• manager or diamond should autodetect interaction hardware.
• Get a basic task manager thing going, and use manager::Context for it?
• 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
• Use rememberance-agent code for manager context classification
• manager or verber should have a "keep the airplane flying" mentality in terms of providing a certain service level.
• 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.
• 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.
• Get a manager::dialog SRS going
• Insert all sorts of hooks for manager/pse to know the current working context.
• manager dribble files are working now
• Next I need to improve manager to the point where it can direct me to do certain things at certain times.
• If manager requires to contact the user and the user is not available, and sound is not getting a response, trying flashing your screen.
• 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.
• Need to agentify manager and have him running. He will conduct verber.
• From estimating sleeping times, can initiate SBAGEN, as well as other manager things.
• Implement dribble file as part of manager Emacs session
• The metadata for session logs for manager Emacs Session stuff is not staying.
• 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.
• 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.
• Could write a manager::Dialog interface for unilang.
• Implement an emacs interface to manager::dialog (subsetselect, etc)
• Have manager alarm check for internet access before running ntpdate.
• Get manager alarm to get gradually louder.
• Add emotions to manager...
• The new svrs functionality belongs in manager.
• 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.
• manager should test whether GAIM is logged on. Or maybe should automatically log GAIM on for me.
• Set up manager/memax to record session strokes in dribble file automatically.
• Add these features to manager's alarm clock - tell it to wake you in a certain period, like 3 hours. Have it play stuff in the background.
• in order to eliminate emacs sessions recorded by manager in which I looked at pornography, not that it really matters, we can search for porn keywords. I don't like the plain keyword approach - I would prefer nice language models - more accurate. Why don't we right dansguardian about hat.
• Just realized, that some effects propagate before, during and after execution of plan steps. Also, plans are not always serial like this thing seems to think. I don't know how I could have made that mistake. The manager cannot treat it serially.
• Perhaps the identity manager could automatically fill out accounts.
• audience will be necessary for job-search, and even manager if I recall correctly.
• Note that problemspace should not come on if we are in a recording session from manager.
• 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.
• 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.
• 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.
• 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.
• manager can infer from learned network traffic the absense of the user and guess then at where they are, for instance, asleep.
• 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.
• 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.
• (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.