.
FRDCSA | internal codebases | Score

Score Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

Capabilities

• KBS, MySQL:score:test query ("loves" undef undef)
• KBS, MySQL:score:default query ("depends" nil nil)
• KBS, MySQL:score:default assert ("depends" "This" "That")
• The critic system is almost complete using freekbs, and newly written code currently under score.
• score can have a relation solved X Y that indicates that the condition mentioned in X solved the condition mentioned in Y.
• Write script to iterate over current todo lists and make score entries out of them. Note that it can ask, what type of relation is this, is this is a goal or a comment or a solution, etc.
• Replace fortune with unilang or score messages.
• score should be able to merge the context of the creation to formalize goals.
• Create a score for who is scoring the most without creating competition.
• In order to prevent training of SpamAssassin from being corrupted by the bad training we are seeing, at least in the case of false-positive training, we can determine when something is obviously spam because of a very high score...
• If a message is flagged as a certain type of todo, it can be tagged in the pse or score dbs as completed. There will of course be lots of review to ensure that everything is indeed completed.
• Rework the calculations done by score.
• Could add that as a module to score/problemspace/fieldgoal or something.
• I think manager::Records::Context may have some bugs, specifically related to how it calculates the score.
• The solution to the problem of different databases is pretty simple for score. Allow score to utilize the umesgs under the pretext that they are autoclassified.
• There should be a central FRDCSA page where users have the option of showing their score results and profile.
• 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!.
• Here are some ideas about RSR. RSR should act like a game, where it gives you a multi-dimensional score for the day. You get extra points for coverage for everything you admit. You get penalized for bad things.
• sinless/score is a good system.
• Create web browsing score for how much communication is being done. Model web reading using clear topic visualizer. Penalize bad words, etc.
• Get a simple system going today that tells me what remains to be done for the day, essentially an offshoot of that score thign.
• Can estimate when I am sleeping and such based on score event data for now.
• So, to get that working, should focus on simply building those tools for score, rather than what we are attempting here.
• score or pse should implement critical path and WBS stuff from Schaum's.
• Work on part for classifying tasks into various logics and keeping track of their progress using score/pse, by recording successful completion of tasks.
• Also, get score to pop up agenda if Emacs has been idle.
• In thinking it over, although I want to get verber going, I don't think it is as critical as getting something that determines what the critical path is, i.e., getting pse/score fully operational, to the point where we can assert that things have been done. I don't know that we need to get it to the point where it classifies new items, but that we can specifically annotate existing ones.
• score can complete latest completion time, critical paths, etc.
• Use ACWP,NCWP,SPI,CPI,etc for score.
• Set up a basic thing for score to penalize for certain actions in log files, for instance apt-get install mozilla
• Use the critic system on this score stuff as well, in order to come up with multiple taxonomies.
• My first score: 1.2985370338548
• We can track how effective I am by certain indicators - a score can be computed from the packages.
• The following exercise, and perhaps my recent good discipline, having eaten, as well as clipped my nails, and removed any distractions, followed by attempting to type the entire entry without a single mistake (one was indeed made), resulted in tremendous improvement in typing score.
• We can measure the typing rates and improve people's hacker score - which consists of type rate * LOC * pse rating, etc,etc,et