Perfil de GaryBack to the sourceBlogListas Herramientas Ayuda

Gary Eric

Ocupación
Ubicación
Intereses
Lost and gain,that's the way

JO

Back to the source

Refreshing.......
10 abril

Knowledge representation

Knowledge representation
From Wikipedia, the free encyclopedia

Knowledge representation is an issue that arises in both cognitive science and artificial intelligence. In cognitive science it is concerned with how people store and process information. In artificial intelligence (AI) the primary aim is to store knowledge so that programs can process it and achieve the verisimilitude of human intelligence. AI researchers have borrowed representation theories from cognitive science.

Overview

There are representation techniques such as frames, rules and semantic networks which have originated from theories of human information processing. Since knowledge is used to achieve intelligent behavior, the fundamental goal of knowledge representation is to represent knowledge in a manner as to facilitate inferencing (i.e. drawing conclusions) from knowledge.

Some issues that arise in knowledge representation from an AI perspective are:

.How do people represent knowledge?
.What is the nature of knowledge and how do we represent it?
.Should a representation scheme deal with a particular domain or should it be general purpose?
.How expressive is a representation scheme?
.Should the scheme be declarative or procedural?

There has been very little top-down discussion of the knowledge representation (KR) issues and research in this area is a well aged quiltwork. There are well known problems such as "spreading activation" (this is a problem in navigating a network of nodes), "subsumption" (this is concerned with selective inheritance; e.g. an ATV can be thought of as a specialization of a car but it inherits only particular characteristics) and "classification." For example a tomato could be classified both as a fruit and a vegetable.

In the field of artificial intelligence, problem solving can be simplified by an appropriate choice of knowledge representation. Representing knowledge in some ways makes certain problems easier to solve. For example, it is easier to divide numbers represented in Hindu-Arabic numerals than numbers represented as Roman numerals.

 

22 septiembre

iRet

Finish my internship in Microsoft.

Larned what is team work, how to write large programs, how to read 30 to 40 mails per day, how to express myself, how to keep smiling when talking. And known what is Indigo, what is designing pattern, what is humor, what is rejection and what is pool.

In fact I think there will be more practices to do with my English and program designing if I choose this way. And then I can be a totally skillful coder.

I decided to attend ACM/ICPC again this year, only for fun. Today's young guys seemed very busy, and have little time to stay at lab, hope there will be someone really enjoy it.

Most of our classmates are busying with their career, master or employee or abroad, life become boring so fast. "Boring it is!" said litmus. Maybe it is boring, or not for the others.

Try to do an exercise of Yoga and make a plan. It is very interesting when I do it, it's full of suffering, but when I finished, I feel my body flying!
 
We should know that, right? From suffering to flying.
 
06 septiembre

Working & ACMing & Examing

Still working on Monday, Tuesday and Wednesday. Turn to part time intern, and be paid by hour. But learned more than before. Now trying to write an Indigo sample program, which is a restaurant online service provider. On the server side, it will be a DLL hosted by IIS, and connected to SQL Server. On the client side, it will be a Windows Dialog Based Appllication written by VB.net. It sounds a excellent plan, but I'm not sure whether I could finished it. After all, I'd like to go back home at late September, and ACM/ICPC is going to start.
 
Hoped to study at lab on Thursday, Friday and Saturday. Data struct and Algorithm are still my favorite, but I even haven't start this year. What a terrible thing. Maybe I could finish reading the algorithm book in a few days, just do what I did before exams.
 
AI and Multimedia still need to be examed, although Shen had promised they wouldn't. I planed to meet Yang and Wang tomorrow. Don't know what to ask. I think these lessons would be easier to pass than compiler, which should had been my favorite too.
 
God give me time...
25 agosto

Learning

No busy work for me recent days. Because I told them I have to attend exams next week.
 
All I am doing now is to try to write a sample application using VB and Indigo. Though Indigo is new and little materials to learn, it is more interesting than writing testplan or automations. After all, I can design the application myself.
 
In my opinion, Indigo is a system support for you to write connected programs efficiently. Without it, we have to handle some connecting configurations in the code. But now, all of these can be write in config files (or use tools to generate) and handled by the system runtime. Programmer can focus on the informations flowed between programs. Not waste time to write connection code.
 
Further thinking. That is what systems due to deal. When progarmmers are always doing the same things, these things can be taken by the system. Programmers will lost flexibility on these low level things, but can have more time to deal with top level, which is more creative.
 
This is what we called evolution, which is also suitable for the human beings.
 
 
24 agosto

coding tools

Recent days in MS, found many tools we hadn't met. Some are internal, some are not. Have you heard or used them?
 
MAUI : Support libraries for writing automation on UI
 
Maddog : Testcase and Tier machine management tool
 
Feature Branch : Product synchronizing tool
 
Reflector : .NET disassembler
 
Product Studio: Testcase and Bug management tool
 
Bugger : Bug management tool
 
......
 
These are what I know. Every team have their own custom. Maybe people in redmond use some other strange things, who knows.
23 agosto

Enhance the code skill

I realised it is very important skill to use keyboard to code instead of mouse . I mean do not use mouse at all.
 
Use the cursor to move around the screen and copy, cut, paste, build, run, debug. All done by keyboard.
 
Necessary to remember some shortcuts. Here are some I can remember in Visual Studio:
 
Ctrl + Arrow : jump
 
Shift + Arrow : select
 
(the following can be combined with Ctrl and Shift to select)
 
Home : line head
 
Ctrl + Home : file head
 
End : line end
 
Ctrl + End : file end
 
F6 : build
 
F5 : run with debug
 
Ctrl + F5 : run
 
F10 : step over
 
F11 : step into
 
Ctrl + F11 : step out
 
F9 : breakpoint
 
F12 : go to definition
 
Ctrl + F : find
 
Ctrl + F3 : find current word
 
F3 : find next
 
Ctrl + - : return to last cursor postion
 
Ctrl + X : cut
 
Ctrl + C : copy
 
Ctrl + V : paste
 
And here are some useful Windows Shortcuts I often use:
 
Win + D : Desktop
 
Win + L : Lock
 
Win + E : My computer
 
Win + Break : System Properties
 
Win + M : Minimize all
 
Win + R : Run
 
Ctrl + Alt + Del : Task Manager

How it will be

Like the title of the space, it will back to the source.