Modelling Task Knowledge Structures in Demos 2000


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Modelling Task Knowledge Structures in Demos 2000
# 1  
Old 08-07-2008
Modelling Task Knowledge Structures in Demos 2000

HPL-2008-94 Modelling Task Knowledge Structures in Demos 2000 - Degabriele, Jean Paul; Pym, David
Keyword(s): Task Knowledge Structures, Demos 2000, Modelling
Abstract: Task Knowledge Structures provide an account of the knowledge structures that people possess and use when performing a task. Such models can be constructed using various techniques, such as direct observation, interviews, questionnaires, and others. TKS models can represent either knowledge structur ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Knowledge

Can somebody explain me the following part within a awk command: awk '{for(i=1;i<=NF;i++) if ($i=="mm")c++} Can somebody please explain me the part (i=1;i<=NF;i++) ????:D:D:D:D (1 Reply)
Discussion started by: RubinPat
1 Replies

2. Shell Programming and Scripting

Parse an XML task list to create each task.xml file

I have an task definition listing xml file that contains a list of tasks such as <TASKLIST <TASK definition="Completion date" id="Taskname1" Some other <CODE name="Code12" <Parameter pname="Dog" input="5.6" units="feet" etc /Parameter> <Parameter... (3 Replies)
Discussion started by: MissI
3 Replies

3. Shell Programming and Scripting

comment and Uncomment single task out of multiple task

I have a file contains TASK gsnmpproxy { CommandLine = $SMCHOME/bin/gsnmpProxy.exe } TASK gsnmpdbgui { CommandLine = $SMCHOME/bin/gsnmpdbgui.exe I would like to comment and than uncomment specific task eg TASK gsnmpproxy Pls suggest how to do in shell script (9 Replies)
Discussion started by: madhusmita
9 Replies

4. AIX

knowledge

Dear All Kindly provide me with a difference between hdiskpower and hdisk regards (2 Replies)
Discussion started by: magasem
2 Replies
Login or Register to Ask a Question
Gearman::Task(3pm)					User Contributed Perl Documentation					Gearman::Task(3pm)

NAME
Gearman::Task - a task in Gearman, from the point of view of a client SYNOPSIS
my $task = Gearman::Task->new("add", "1+2", { ..... }; $taskset->add_task($task); $client->do_task($task); $client->dispatch_background($task); DESCRIPTION
Gearman::Task is a Gearman::Client's representation of a task to be done. USAGE
Gearman::Task->new($func, $arg, \%options) Creates a new Gearman::Task object, and returns the object. $func is the function name to be run. (that you have a worker registered to process) $arg is an opaque scalar or scalarref representing the argument(s) to pass to the distributed function. If you want to pass multiple arguments, you must encode them somehow into this one. That's up to you and your worker. %options can contain: o uniq A key which indicates to the server that other tasks with the same function name and key will be merged into one. That is, the task will be run just once, but all the listeners waiting on that job will get the response multiplexed back to them. Uniq may also contain the magic value "-" (a single hyphen) which means the uniq key is the contents of the args. o on_complete A subroutine reference to be invoked when the task is completed. The subroutine will be passed a reference to the return value from the worker process. o on_fail A subroutine reference to be invoked when the task fails (or fails for the last time, if retries were specified). No arguments are passed to this callback. This callback won't be called after a failure if more retries are still possible. o on_retry A subroutine reference to be invoked when the task fails, but is about to be retried. Is passed one argument, what retry attempt number this is. (starts with 1) o on_status A subroutine reference to be invoked if the task emits status updates. Arguments passed to the subref are ($numerator, $denominator), where those are left up to the client and job to determine. o retry_count Number of times job will be retried if there are failures. Defaults to 0. o high_priority Boolean, whether this job should take priority over other jobs already enqueued. o timeout Automatically fail, calling your on_fail callback, after this many seconds have elapsed without an on_fail or on_complete being called. Defaults to 0, which means never. Bypasses any retry_count remaining. o try_timeout Automatically fail, calling your on_retry callback (or on_fail if out of retries), after this many seconds have elapsed. Defaults to 0, which means never. $task->is_finished Returns bool: whether or not task is totally done (on_failure or on_complete callback has been called) perl v5.10.1 2009-10-05 Gearman::Task(3pm)