<div> Even though ACT borrowed from EPIC to improve ACT's perceptual modeling, it is my understanding that EPIC (David Kieras, U. Michigan) remains relatively stronger on perception, although certainly weaker on central cognition.</div>
<div> </div>
<div>Susan Chipman<br><br> </div>
<div><span class="gmail_quote">On 6/24/08, <b class="gmail_sendername">Kelley, Troy (Civ,ARL/HRED)</b> <<a href="mailto:tkelley@arl.army.mil">tkelley@arl.army.mil</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Classification: UNCLASSIFIED<br>Caveats: NONE<br><br>Susan,<br><br> We have been looking at using a semantic network as a starting point<br>
for declarative memory chunks. There are two major semantic networks that<br>we are looking at using. ConceptNet from MIT and OpenCYC which is a spin<br>off of Doug Lenat's work at the University of Texas. We are still working<br>
on exactly how to interface a semantic network with declarative memory<br>chunks, but I think the general idea has promise. We are also trying to use<br>a production syntax so that the same general productions don't have to be<br>
developed over and over. Both of these ideas have promise but we are still<br>working on the implementations.<br><br>Troy D. Kelley<br>AMSRD-HR-SE<br>Army Research Laboratory<br>Human Research and Engineering Directorate (HRED)<br>
Aberdeen Proving Ground, Aberdeen MD 21005-5425<br>voice: 410-278-5869<br>fax: 410-278-9523<br><br>-----Original Message-----<br>From: <a href="mailto:act-r-users-bounces@act-r.psy.cmu.edu">act-r-users-bounces@act-r.psy.cmu.edu</a><br>
[mailto:<a href="mailto:act-r-users-bounces@act-r.psy.cmu.edu">act-r-users-bounces@act-r.psy.cmu.edu</a>] On Behalf Of Susan Chipman<br>Sent: Tuesday, June 24, 2008 1:10 PM<br>To: Dan Bothell<br>Cc: <a href="mailto:act-r-users@act-r.psy.cmu.edu">act-r-users@act-r.psy.cmu.edu</a><br>
Subject: Re: [ACT-R-users] ACT-R robot<br><br> As the former sponsor of much of the ACT-R work, I would really like<br>to have seen a cumulative library of model building work in order to avoid<br>duplication of effort and the associated waste of scarce research funding.<br>
In particular, it seemed to me that declarative knowledge should not be<br>built over and over again. I retired, so I am no longer in a position to<br>push this agenda, but I hope the community will come to such a conclusion<br>
soon.<br><br>Susan Chipman<br><br><br>On Tue, Jun 24, 2008 at 12:00 PM, Dan Bothell <<a href="mailto:db30@andrew.cmu.edu">db30@andrew.cmu.edu</a>> wrote:<br><br><br><br><br> --On Tuesday, June 24, 2008 8:04 AM -0700 Bruce J Weimer MD<br>
<br> <<a href="mailto:bjweimer@charter.net">bjweimer@charter.net</a>> wrote:<br><br><br> > Also, I was wondering as I read the papers, is information that's<br>learned<br> > during a session with the robot stored or saved when the robot's<br>
turned<br> > off or is it lost? I'm reading through the ACT-R tutorials and<br>it seems<br> > that each time a model is run, it's reset to run again - there<br>(so far)<br> > hasn't been any mention of a mechanism to save the information in<br>
> declarative memory, weights, latencies, etc.<br> ><br><br><br> There is no mechanism built into ACT-R for saving the internal state<br>of any<br> module or the system in general. However, depending on what you<br>
want to<br> save, it's usually not too difficult to just cache that out and read<br>it<br> back in later.<br><br> For example, here's a function which will create a file with the<br>commands<br> to rebuild the chunks in declarative memory and restore their<br>
parameters<br> (only one of the declarative parameters is included here for<br>brevity):<br><br> (defun save-chunks (file-name)<br> (let ((chunks (no-output (dm)))<br> (params (no-output (sdp :name :reference-count)))<br>
(cmdt (car (no-output (sgp :cmdt)))))<br><br> (sgp-fct (list :cmdt file-name))<br><br> (command-output "(add-dm ")<br><br> (dolist (x chunks)<br> (command-output "(")<br>
(pprint-chunks-fct (list x))<br> (command-output ")"))<br> (command-output ")")<br><br> (dolist (x params)<br> (command-output "(sdp ~A :reference-count ~s)" (first x)<br>
(second x)))<br><br> (sgp-fct (list :cmdt cmdt))))<br><br> The file that writes out could then just be loaded later to restore<br>the<br> model's declarative memory. A similar function could be written to<br>
dump<br> the productions and their parameters (see the reference manual for<br>the<br> relevant commands).<br><br> Depending on how the general parameters for the model are set there<br>may<br> be some other things that would need to be adjusted as well, but<br>
those<br> sorts of things are going to vary from model to model. One example<br>would<br> be either advancing the time to where the "old" model left off or<br>adjusting<br> all of the declarative parameters to reflect the "current" time<br>
being<br> necessary if base-level learning were enabled.<br><br> Dan<br><br> _______________________________________________<br> ACT-R-users mailing list<br> <a href="mailto:ACT-R-users@act-r.psy.cmu.edu">ACT-R-users@act-r.psy.cmu.edu</a><br>
<a href="http://act-r.psy.cmu.edu/mailman/listinfo/act-r-users">http://act-r.psy.cmu.edu/mailman/listinfo/act-r-users</a><br><br><br><br>Classification: UNCLASSIFIED<br>Caveats: NONE<br><br><br></blockquote></div>
<br>