From shawn.nicholson at dnamerican.com Fri Jul 1 15:32:12 2005 From: shawn.nicholson at dnamerican.com (Shawn Nicholson) Date: Fri, 1 Jul 2005 15:32:12 -0400 Subject: [ACT-R-users] Question on new visual objects and accessing in productions Message-ID: Hello, I am trying to scan and encode objects that aren't of the predefined types and which will have different (more) slots describing properties of the visual objects. To accomplish this a new icon-feature subclass was created (called aircraft-icon) and it was given an initial additional slot called direction (indicating the orientation of the aircraft icon with respect to a fixed location). (defclass aircraft-icon (actr:icon-feature) ((actr:direction :accessor actr:direction :initarg :direction :initform 0)) (:default-initargs :kind 'actr:visual-object)) Additionally, build-group-features-for methods were specialized on this new aircraft-icon to compute and fill in the visicon properly (with the new slot). When I run such a system, I can initiate visual-location requests like: +visual-location> isa visual-location kind visual-object value :friendly <-- that slot is set in the build-group-features-for This works, and I can then do a move-attention in the visual module given the retrieved visual-location. However, there is no direction slot in the chunk. If I change the slot setting of, say, :height in build-groups-features-for to the result of computing the aircraft direction, then the chunk will have the direction instead of height specified. But there won't be a direction slot at all. To get the direction slot, I changed my definition of the aircraft-icon class to set the default value for kind to something other than visual-object (defclass aircraft-icon (actr:icon-feature) ((actr:direction :accessor actr:direction :initarg :direction :initform 0)) (:default-initargs :kind 'actr::aircraft-object)) and then, in my model, put (chunk-type (aircraft-object (:include visual-object)) direction) (define-chunks (aircraft-object isa chunk)) With this change I know do visual-requests where the KIND slot is aircraft-object and when I run my model, the visual chunk returned does have the direction slot in it. However, it was always NIL (even though it was set properly in the visicon - inspecting that when all was done had the correct values in the visicon objects). I then proceeded to add a method feat-to-dmo specialized on the aircraft-icon class identical to the default with one exception - I added a direction filler. (defmethod actr::feat-to-dmo ((feat aircraft-icon)) (setf (actr::attended-p feat) t) (actr::make-dme (actr::dmo-id feat) (actr::kind feat) `(actr::screen-pos ,(actr::id (actr::xy-to-dmo (actr::xy-loc feat) t)) actr::value ,(actr::val feat) actr::color ,(actr::color feat) actr::height ,(actr::height feat) actr::width ,(actr::width feat) actr::direction ,(actr::direction feat) ) :obj (actr::screen-obj feat) :where :external)) Now, everything works. But I am wondering if what I have done is the proper method for manipulating specialized icon objects in the vision module. My questions (in summary): 1) Is this the proper way to be adding new visual object types to the system for accessing special slots and such? (ie adding that feat-to-dmo method specialized on aircraft-icon??) 2) Those two lines that I placed in my model seem like they should be somewhere in the code where the aircraft-icon feature is defined. However, unless I put them in the model, anytime (clear-all) is called, the chunk types go away and they no longer exist for use in the productions. I could put and advice function around the function reset-vision-module (which is where all the basic vision chunks are defined) but that doesn't seem to be a clean way to change things. Sorry for the long winded question. I'm new to this and want to know how to do these things properly. Thank you, Shawn Nicholson ======================================= Shawn Nicholson Research Engineer D.N. American shawn.nicholson at dnamerican.com Ph: (304) 363-6757 Public PGP/GPG Key ID: 0x24A58D96 ======================================= -------------- next part -------------- An HTML attachment was scrubbed... URL: From db30 at andrew.cmu.edu Fri Jul 1 16:52:47 2005 From: db30 at andrew.cmu.edu (Dan Bothell) Date: Fri, 01 Jul 2005 16:52:47 -0400 Subject: [ACT-R-users] Question on new visual objects and accessing in productions In-Reply-To: References: Message-ID: <0171667BEEEF99571B863041@whatever.psy.cmu.edu> --On Friday, July 01, 2005 3:32 PM -0400 Shawn Nicholson wrote: > > Now, everything works. But I am wondering if what I have done is the > proper method for manipulating specialized icon objects in the vision > module. My questions (in summary): > > 1) Is this the proper way to be adding new visual object types to the > system for accessing special slots and such? (ie adding that feat-to-dmo > method specialized on aircraft-icon??) > I think you mean build-features-for instead of build-group-features-for, but otherwise, yeah, that's basically how it's done: Write a build-features-for to return a custom icon-feature and then write a feat-to-dmo to convert that icon-feature into a dme/chunk. There are details in the docs at for others that are interested, in particular the device interface and vision module sections. > 2) Those two lines that I placed in my model seem like they should be > somewhere in the code where the aircraft-icon feature is defined. > However, unless I put them in the model, anytime (clear-all) is called, > the chunk types go away and they no longer exist for use in the > productions. I could put and advice function around the function > reset-vision-module (which is where all the basic vision chunks are > defined) but that doesn't seem to be a clean way to change things. > Right, clear-all (or a reset) deletes all chunk-type definitions. The chunk-type should probably stay in the model. Generally, I would advise against modifying or extending the main functions of the vision module (or really any of the modules) unless it's really necessary. The definition of the chunk named aircraft-object isn't really necessary because it will get created automatically. [To those that don't recognize the define-chunks function, it's an ACT-R 6 command for creating chunks without putting them into DM.] I'm assuming you got a warning that there wasn't such a chunk since you use it as the value for kind and then added that to avoid the warning. One general comment is that I would recommend against using keywords as slot values i.e. chunk names. In previous versions of ACT-R it could lead to some really hard to debug code, for example, in ACT-R 5: CG-USER(3): (add-dm (g isa visual-location value foo kind :foo)) (G) CG-USER(4): (dm g) G 0.000 isa VISUAL-LOCATION screen-x nil screen-y nil distance nil attended nil kind Foo color nil value Foo size nil nearest nil note that it doesn't show the difference in the output. While ACT-R 6 will show that correctly in that case I can't guarantee that it will treat them correctly everywhere. Dan From shawn.nicholson at dnamerican.com Fri Jul 1 20:41:38 2005 From: shawn.nicholson at dnamerican.com (Shawn Nicholson) Date: Fri, 1 Jul 2005 20:41:38 -0400 Subject: [ACT-R-users] Question on new visual objects and accessing in productions Message-ID: Great! thanks for the pointers to those docs - exactly what I needed. And as for the feature values being keywords, yes that was actually a typo on my part. In the code they are keywords :friendly, :unfriendly and a couple others, but when I try to access them in productions I found that I could not use the keywords, I had to specify them as non-keywords (and they were found). I will go back and get rid of the keyword specifications though. Thanks, Shawn -----Original Message----- From: Dan Bothell [mailto:db30 at andrew.cmu.edu] Sent: Fri 7/1/2005 4:52 PM To: Shawn Nicholson; act-r-users at act-r.psy.cmu.edu Cc: Subject: Re: [ACT-R-users] Question on new visual objects and accessing in productions --On Friday, July 01, 2005 3:32 PM -0400 Shawn Nicholson wrote: > > Now, everything works. But I am wondering if what I have done is the > proper method for manipulating specialized icon objects in the vision > module. My questions (in summary): > > 1) Is this the proper way to be adding new visual object types to the > system for accessing special slots and such? (ie adding that feat-to-dmo > method specialized on aircraft-icon??) > I think you mean build-features-for instead of build-group-features-for, but otherwise, yeah, that's basically how it's done: Write a build-features-for to return a custom icon-feature and then write a feat-to-dmo to convert that icon-feature into a dme/chunk. There are details in the docs at for others that are interested, in particular the device interface and vision module sections. > 2) Those two lines that I placed in my model seem like they should be > somewhere in the code where the aircraft-icon feature is defined. > However, unless I put them in the model, anytime (clear-all) is called, > the chunk types go away and they no longer exist for use in the > productions. I could put and advice function around the function > reset-vision-module (which is where all the basic vision chunks are > defined) but that doesn't seem to be a clean way to change things. > Right, clear-all (or a reset) deletes all chunk-type definitions. The chunk-type should probably stay in the model. Generally, I would advise against modifying or extending the main functions of the vision module (or really any of the modules) unless it's really necessary. The definition of the chunk named aircraft-object isn't really necessary because it will get created automatically. [To those that don't recognize the define-chunks function, it's an ACT-R 6 command for creating chunks without putting them into DM.] I'm assuming you got a warning that there wasn't such a chunk since you use it as the value for kind and then added that to avoid the warning. One general comment is that I would recommend against using keywords as slot values i.e. chunk names. In previous versions of ACT-R it could lead to some really hard to debug code, for example, in ACT-R 5: CG-USER(3): (add-dm (g isa visual-location value foo kind :foo)) (G) CG-USER(4): (dm g) G 0.000 isa VISUAL-LOCATION screen-x nil screen-y nil distance nil attended nil kind Foo color nil value Foo size nil nearest nil note that it doesn't show the difference in the output. While ACT-R 6 will show that correctly in that case I can't guarantee that it will treat them correctly everywhere. Dan From ja+ at cmu.edu Mon Jul 4 11:59:29 2005 From: ja+ at cmu.edu (John Anderson) Date: Mon, 4 Jul 2005 11:59:29 -0400 Subject: [ACT-R-users] ACTR-05 -- submissions due July 5 Message-ID: Colleagues: To those of us celebrating, happy 4th of July. Danilo Fum reports that things are progressing well for the meetings in Trieste. He allows how, in light of the American holiday, he would accept submissions a day later (July 6). I guess we get to define that in terms of our own time zone. Hope to see many of you shortly. --John -- ========================================================== John R. Anderson Carnegie Mellon University Pittsburgh, PA 15213 Phone: 412-268-2788 Fax: 412-268-2844 email: ja at cmu.edu URL: http://act.psy.cmu.edu/ From ja+ at cmu.edu Wed Jul 6 11:30:41 2005 From: ja+ at cmu.edu (John Anderson) Date: Wed, 6 Jul 2005 11:30:41 -0400 Subject: [ACT-R-users] ACTR-05 -- submissions due ???? Message-ID: Colleagues: I have been told a number of things might not be clear that I have been told I should have made clear. I also have one bit of news: First, there has been some uncertainty about whether submissions have been accepted. In line with the informal operation we run around here, the operative assumption is that your submission is in unless you do not hear otherwise. Equally, there has been some uncertainty about the format of submissions. I have sent in a copy of my slides reduced to 6 pages and that is the default -- although more elaborate 6 page submissions are OK. Maybe we want to revisit the informality about our workshop procedures but that is the way it is now. Finally, the news: There will come a date by the end of this week at which any submissions will be too late to be included in the proceedings. The official word on that date will come from Trieste but I have been told it is later than tomorrow (I am not clear right now if Friday is too late but I would kind of guess it might be unless you send something very early in the European time zone that day). Regards, John -- ========================================================== John R. Anderson Carnegie Mellon University Pittsburgh, PA 15213 Phone: 412-268-2788 Fax: 412-268-2844 email: ja at cmu.edu URL: http://act.psy.cmu.edu/ From cimca at canberra.edu.au Thu Jul 7 08:39:06 2005 From: cimca at canberra.edu.au (cimca) Date: Thu, 7 Jul 2005 22:39:06 +1000 Subject: [ACT-R-users] CFP: IEEE in cooperated International Conference on Computational Intelligence for Modelling, Control and Automation Message-ID: <088D96D6E422174EAABF7B27D94F3EE70102106D@hera.ucstaff.win.canberra.edu.au> CFP: IEEE in cooperated International Conference on Computational Intelligence for Modelling, Control and Automation CALL FOR PAPERS International Conference on Computational Intelligence for Modelling, Control and Automation 28 - 30 November 2005 Vienna, Austria http://www.ise.canberra.edu.au/conferences/cimca05/ In co-operation with: IEEE Computational Intelligence Society Conference Proceedings will be published as books by IEEE in USA Sponsored by: European Society for Fuzzy Logic and Technology - EUFLAT International Association for Fuzzy Set in Management and Economy - SIGEF Japan Society for Fuzzy Theory and Intelligent Informatics - SOFT Taiwan Fuzzy Systems Association - TFSA World Wide Web Business Intelligence - W3BI Hungarian Fuzzy Association - HFA University of Canberra Jointly with International Conference on Intelligent Agents, Web Technologies and Internet Commerce http://www.ise.canberra.edu.au/conferences/iawtic05/ Honorary Chair: Lotfi A. Zadeh, University of California, USA Stephen Grossberg, Boston University, USA The international conference on computational intelligence for modelling, control and automation will be held in Vienna, Austria on 28 to 30 November 2005. The conference provides a medium for the exchange of ideas between theoreticians and practitioners to address the important issues in computational intelligence, modelling, control and automation. The conference will consist of both plenary sessions and contributory sessions, focusing on theory, implementation and applications of computational intelligence techniques to modelling, control and automation. For contributory sessions, papers (4 pages or more) are being solicited. Several well-known keynote speakers will address the conference. Conference Proceedings will be published as books by IEEE (The Institute of Electrical and Electronic Engineering) in USA and will be index world wide. All papers will be peer reviewed by at least two reviewers. Topics of the conference include, but are not limited to, the following areas: Modern and Advanced Control Strategies: Neural Networks Control, Fuzzy Logic Control, Genetic Algorithms and Evolutionary Control, Model-Predictive Control, Adaptive and Optimal Control, Intelligent Control Systems, Robotics and Automation, Fault Diagnosis, Intelligent agents, Industrial Automations Hybrid Systems: Fuzzy Evolutionary Systems, Fuzzy Expert Systems, Fuzzy Neural Systems, Neural Genetic Systems, Neural-Fuzzy-Genetic Systems, Hybrid Systems for Optimisation Data Analysis, Prediction and Model Identification: Signal Processing, Prediction and Time Series Analysis, System Identification, Data Fusion and Mining, Knowledge Discovery, Intelligent Information Systems, Image Processing, and Image Understanding, Parallel Computing applications in Identification & Control, Pattern Recognition, Clustering and Classification Decision Making and Information Retrieval: Case-Based Reasoning, Decision Analysis, Intelligent Databases & Information Retrieval, Dynamic Systems Modelling, Decision Support Systems, Multi-criteria Decision Making, Qualitative and Approximate-Reasoning Paper Submission Papers will be selected based on their originality, significance, correctness, and clarity of presentation. Papers (4 pages or more) should be submitted to the following e-mail or the following address: CIMCA'2005 Secretariat School of Information Sciences and Engineering University of Canberra, Canberra, 2616, ACT, Australia E-mail: cimca at canberra.edu.au Electronic submission of papers (either by E-mail or through conference website) is preferred. Draft papers should present original work, which has not been published or being reviewed for other conferences. Important Dates 31 August 2005 Submission of draft papers 30 September 2005 Notification of acceptance 21 October 2005 Deadline for camera-ready copies of accepted papers 28-30 November 2005 Conference sessions Special Sessions and Tutorials Special sessions and tutorials will be organised at the conference. The conference is calling for special sessions and tutorial proposals. All special session proposals should be sent to the conference chair (by email to: masoud.mohammadian at canberra.edu.au) on or before 5th of August 2005. CIMCA'05 will also include a special poster session devoted to recent work and work-in-progress. Abstracts are solicited for this session. Abstracts (3 pages limit) may be submitted up to 30 days before the conference date. Visits and social events Sightseeing visits will be arranged for the delegates and guests. A separate program will be arranged for companions during the conference. Further Information For further information either contact cimca at ise.canberra.edu.au or see the conference homepage at: http://www.ise.canberra.edu.au/conferences/cimca05/default.htm Organising Committee Chair: Masoud Mohammadian, University of Canberra, Australia International Program Committee: H. Adeli, The Ohio State University, USA W. Pedrycz, University of Manitoba, Canada A. Agah, The University of Kansas, USA T. Fukuda, Nagoya University, Japan J. Bezdek, University of West Florida, USA R. C. Eberhart, Purdue University, USA F. Herrera, University of Granada, Spain T. Furuhashi, Nagoya University, Japan A. Agah, The University of Kansas, US E. Andr?, Universit?t Augsburg, Germany A. Kandel, University of South Florida, USA J. P. Bigus, IBM T. J. Watson Research Center, USA J. Liu, Hong Kong Baptist University, Hong Kong A. Namatame, National Defense Academy, Japan K. Sycara, Carnegie Mellon University, USA B. Kosko, University of Southern California, USA T. Baeck, Informatic Centrum Dortmund, Germany K. Hirota, Tokyo Institute of Technology, Japan E. Oja, Helsinki University of Technology, Finland H. R. Berenji, NASA Ames Research Center, USA H. Liljenstrom, Royal Institute of Technology, Sweden A. Bulsari, AB Nonlinear Solutions OY, Finland J. Fernandez de Ca?ete, University of Malaga, Spain W. Duch, Nicholas Copernicus University, Poland E. Tulunay, Middle East Technical University, Turkey C. Kuroda, Tokyo Institute of Technology, Japan T. Yamakawa, Kyushu Institute of Technology, Japan J. Liu, Hong Kong Baptist University, Hong Kong A. Namatame, National Defense Academy, Japan A. Aamodt, Norwegian University of Science & Technology, Norway International Liaison: Canada and USA Liaison: Robert John, De Montfort University, UK Nasser Jazdi, Institut f?r Automatisierungs- und Softwaretechnik, Germany Europe Liaison: Dr. Eng. Djamel Khadraoui, Centre de Recherche Public, Luxembourg Frank Zimmer, SES ASTRA, Luxembourg Asia Liaison: Renzo Gobbin, University of Canberra, Australia R. Amin Sarker, ADFA, Australia Local Arrangements and Public Relation: Zohreh Pahlavani, AVIP, Austria C Meier, Australia Publicity: C. Meier, Australia Zohreh Pahlavani, AVIP, Austria Publication: Masoud Mohammadian, Australia In cooperation with: IEEE Computational Intelligence Society Conference Proceedings will be published as books by IEEE in USA University of Canberra, (Masoud Mohammadian) Universidad Carlos III de Madrid, (Jos?-Luis Fern?ndez-Villaca?as Mart?n) University of Guelph, (Simon X. Yang) -------------- next part -------------- An HTML attachment was scrubbed... URL: