manu/mldr-zoomed-100char-total-queries-documents

chunk_id stringlengths 3 9	chunk stringlengths 1 100
84_141	Year 1 The Context by Francesco Rosi Cousin, cousine by Jean-Charles Tacchella
84_142	Dersu Uzala by Akira Kurosawa The Devil's Playground by Fred Schepisi
84_143	L'eau chaude l'eau frette by André Forcier Grey Gardens by Albert Maysles and David Maysles
84_144	Harlan County, USA by Barbara Kopple Kings of the Road by Wim Wenders
84_145	Beckett on Film Act Without Words 1 by Karel Reisz Catastrophe by David Mamet
84_146	Endgame by Conor McPherson Happy Days by Patricia Rozema Krapp's Last Tape by Atom Egoyan
84_147	Not I by Neil Jordan Play by Anthony Minghella Rockaby by Sir Richard Eyre
84_148	Rough For Theatre 1 by Kieron J. Walsh What Where by Damien O'Donnell
84_149	Preludes
84_150	Preludes was a special one-off program of ten short films by Canadian film directors, commissioned
84_151	by TIFF to celebrate its 25th anniversary. The Preludes films were also subsequently screened on
84_152	the web separately from their screenings at TIFF, on a platform funded by Bell Canada.
84_153	Camera by David Cronenberg The Line by Atom Egoyan Congratulations by Mike Jones
84_154	See You in Toronto by Jean Pierre Lefebvre The Heart of the World by Guy Maddin
84_155	A Word from the Management by Don McKellar 24fps by Jeremy Podeswa
84_156	This Might Be Good by Patricia Rozema Prelude by Michael Snow Legs Apart by Anne Wheeler
84_157	Spotlight: Robert Beavers Amor by Robert Beavers From the Notebook of... by Robert Beavers
84_158	The Painting by Robert Beavers Ruskin by Robert Beavers Sotiros by Robert Beavers
84_159	The Stoas by Robert Beavers Wingseed by Robert Beavers Work Done by Robert Beavers
84_160	Canadian Open Vault Tit-Coq by Gratien Gélinas and René Delacroix
84_161	Midnight Madness 6ixtynin9 by Pen-ek Ratanaruang The American Nightmare by Adam Simon
84_162	The City of Lost Souls by Miike Takashi The Foul King by Kim Jeewoon
84_163	The Irrefutable Truth about Demons by Glenn Standring The Mission by Johnnie To Kei-Fung
84_164	Quartered at Dawn by Norbert Keil Tell Me Something by Chang Youn hyun
84_165	Time and Tide by Tsui Hark Wild Zero by Tetsuro Takeuchi
84_166	References External links Official site 2000 Toronto International Film Festival at IMDb
84_167	2000 film festivals 2000 2000 in Toronto 2000 in Canadian cinema 2000 festivals in North America
85_0	OpenRTM-aist is a software platform developed on the basis of the RT middleware standard.
85_1	OpenRTM-aist is developed by National Institute of Advanced Industrial Science and Technology which
85_2	also contributes to definition of the RT-middleware standard.
85_3	Abstract
85_4	In RT middleware, all robotic technological elements, such as actuators and sensors, are regarded
85_5	as RT-components (RTC). Each RTC provides ports to communicate with other RTCs, and developers can
85_6	implement their own robotics technology (RT) systems as RTCs. The RT-middleware can thus be
85_7	considered as a distributed control architecture.
85_8	RT-middleware is originally a platform independent model (PIM). Implementations of this model
85_9	include CORBA, Enterprise JavaBean (EJB), and .NET Framework. OpenRTM-aist is based on the CORBA
85_10	technology and implements the extended RTC specification. Experiences with OpenRTM-aist will be fed
85_11	back to the RT-middleware standardization process.
85_12	Characteristics
85_13	OpenRTM-aist implements some extended RTC features, and it also includes a Manager component to
85_14	help manipulating RTCs. RTCs in OpenRTM-aist can be implemented using many programming languages,
85_15	and RTCs programmed in different languages can communicate with each other. A lot of tools to ease
85_16	RTC manipulations are also released by the National Institute of Advanced Industrial Science and
85_17	Technology and their co-workers (in a strict sense, OpenRTM-aist itself is a library and does not
85_18	include these tools).
85_19	RT-component
85_20	The RT-component is a functional unit which conforms to the RT-component specification defined by
85_21	OMG. In OpenRTM-aist, RTCs have data ports, service ports, and execution context which controls the
85_22	RTC's state.
85_23	State Machine
85_24	In standards of RT-component, RTC must have 4 states such as CREATED, INACTIVE, ACTIVE, and ERROR.
85_25	When the state changes, corresponding event-handlers are called by the execution context which
85_26	manages the RTCs' state machine.
85_27	For example, "on_activated" callback function is called when the RTC is activated (from INACTIVE to
85_28	ACTIVE state). In on_activated callback, initialization codes are implemented.
85_29	On the other hand, "on_deactivated" callback function is called when the RTC is deactivated (from
85_30	ACTIVE to INACTIVE state). In this callback, finalization codes are implemented.
85_31	"on_execute" is periodically called when the RTC is in ACTIVE state. Here, controlling or some
85_32	device management (ex., polling) functions are called.
85_33	These callbacks are called by the "execution context" object. If the special execution context is
85_34	attached to the RTCs, calling method or policy is modified (see execution context section).
85_35	Data port
85_36	A data port is an endpoint to communicate with other RTCs. The data ports have their types. Ports
85_37	with the same type can be connected to each other.
85_38	In OpenRTM-aist, primitive data types (like "TimedLong", "TimedDouble", and so on) are implemented.
85_39	Moreover, from OpenRTM-aist version 1.0, extra data types which are expected to be used commonly in
85_40	robotic systems were released as ExtendedDataType (like "TimedVelocity2D", "TimedPose2D", and so
85_41	on)
85_42	Developers can define their own data types by describing IDL file. Tools can parse the IDL file and
85_43	automatically generate the skeleton and stub file of the original data types.
85_44	Service port
85_45	The service port allows communicating much more flexibly than the data ports. Developers should
85_46	define service port interfaces by making their IDL files.
85_47	Execution contexts
85_48	Execution contexts handle the state-machine operations of RT-components. In OpenRTM-aist, several
85_49	kinds of execution contexts are provided. For example:
85_50	the periodic execution context, one of the most commonly used, provides periodic calls of the
85_51	"on_execute" event-handler (sensor acquisition or actuator control are usually implemented there);
85_52	the real-time execution context, which uses Linux's pre-emptive kernel function, supports
85_53	real-time operation of the RTC;
85_54	the extra trigger execution context is an important characteristic of OpenRTM-aist. It provides
85_55	the synchronization capability with dynamics simulators like OpenHRP-3.
85_56	Configuration
85_57	Configuration is a function which dynamically changes the parameters of the RTCs during run-time.
85_58	Configuration can be numeric and string.
85_59	Supported operating systems
85_60	OpenRTM-aist runs on Windows, Linux and macOS. Furthermore, VxWorks is supported experimentally.
85_61	Supported programming languages
85_62	Since OpenRTM-aist is based on the CORBA technology, it supports several programming languages,
85_63	including:
85_64	C++ Java Python Erlang (unofficial)
85_65	Tools RTC Builder
85_66	RTC Builder is a tool for skeleton-code generation. It is launched in the eclipse developmental
85_67	environment. OpenRTM-aist also supports RTC-template which is a command-line type skeleton-code
85_68	generation tool.
85_69	RT System Editor
85_70	RT System Editor is a tool for handling RTCs. RT system editor provides following services:
85_71	Referring RTCs' states Connecting RTCs' ports Configuring RTCs Activate/deactivate/reset RTCs
85_72	Save/restore the RT-system

84_141

Year 1 The Context by Francesco Rosi Cousin, cousine by Jean-Charles Tacchella

84_142

Dersu Uzala by Akira Kurosawa The Devil's Playground by Fred Schepisi

84_143

L'eau chaude l'eau frette by André Forcier Grey Gardens by Albert Maysles and David Maysles

84_144

Harlan County, USA by Barbara Kopple Kings of the Road by Wim Wenders

84_145

Beckett on Film Act Without Words 1 by Karel Reisz Catastrophe by David Mamet

84_146

Endgame by Conor McPherson Happy Days by Patricia Rozema Krapp's Last Tape by Atom Egoyan

84_147

Not I by Neil Jordan Play by Anthony Minghella Rockaby by Sir Richard Eyre

84_148

Rough For Theatre 1 by Kieron J. Walsh What Where by Damien O'Donnell

84_149

Preludes

84_150

Preludes was a special one-off program of ten short films by Canadian film directors, commissioned

84_151

by TIFF to celebrate its 25th anniversary. The Preludes films were also subsequently screened on

84_152

the web separately from their screenings at TIFF, on a platform funded by Bell Canada.

84_153

Camera by David Cronenberg The Line by Atom Egoyan Congratulations by Mike Jones

84_154

See You in Toronto by Jean Pierre Lefebvre The Heart of the World by Guy Maddin

84_155

A Word from the Management by Don McKellar 24fps by Jeremy Podeswa

84_156

This Might Be Good by Patricia Rozema Prelude by Michael Snow Legs Apart by Anne Wheeler

84_157

Spotlight: Robert Beavers Amor by Robert Beavers From the Notebook of... by Robert Beavers

84_158

The Painting by Robert Beavers Ruskin by Robert Beavers Sotiros by Robert Beavers

84_159

The Stoas by Robert Beavers Wingseed by Robert Beavers Work Done by Robert Beavers

84_160

Canadian Open Vault Tit-Coq by Gratien Gélinas and René Delacroix

84_161

Midnight Madness 6ixtynin9 by Pen-ek Ratanaruang The American Nightmare by Adam Simon

84_162

The City of Lost Souls by Miike Takashi The Foul King by Kim Jeewoon

84_163

The Irrefutable Truth about Demons by Glenn Standring The Mission by Johnnie To Kei-Fung

84_164

Quartered at Dawn by Norbert Keil Tell Me Something by Chang Youn hyun

84_165

Time and Tide by Tsui Hark Wild Zero by Tetsuro Takeuchi

84_166

References External links Official site 2000 Toronto International Film Festival at IMDb

84_167

2000 film festivals 2000 2000 in Toronto 2000 in Canadian cinema 2000 festivals in North America

85_0

OpenRTM-aist is a software platform developed on the basis of the RT middleware standard.

85_1

OpenRTM-aist is developed by National Institute of Advanced Industrial Science and Technology which

85_2

also contributes to definition of the RT-middleware standard.

85_3

Abstract

85_4

In RT middleware, all robotic technological elements, such as actuators and sensors, are regarded

85_5

as RT-components (RTC). Each RTC provides ports to communicate with other RTCs, and developers can

85_6

implement their own robotics technology (RT) systems as RTCs. The RT-middleware can thus be

85_7

considered as a distributed control architecture.

85_8

RT-middleware is originally a platform independent model (PIM). Implementations of this model

85_9

include CORBA, Enterprise JavaBean (EJB), and .NET Framework. OpenRTM-aist is based on the CORBA

85_10

technology and implements the extended RTC specification. Experiences with OpenRTM-aist will be fed

85_11

back to the RT-middleware standardization process.

85_12

Characteristics

85_13

OpenRTM-aist implements some extended RTC features, and it also includes a Manager component to

85_14

help manipulating RTCs. RTCs in OpenRTM-aist can be implemented using many programming languages,

85_15

and RTCs programmed in different languages can communicate with each other. A lot of tools to ease

85_16

RTC manipulations are also released by the National Institute of Advanced Industrial Science and

85_17

Technology and their co-workers (in a strict sense, OpenRTM-aist itself is a library and does not

85_18

include these tools).

85_19

RT-component

85_20

The RT-component is a functional unit which conforms to the RT-component specification defined by

85_21

OMG. In OpenRTM-aist, RTCs have data ports, service ports, and execution context which controls the

85_22

RTC's state.

85_23

State Machine

85_24

In standards of RT-component, RTC must have 4 states such as CREATED, INACTIVE, ACTIVE, and ERROR.

85_25

When the state changes, corresponding event-handlers are called by the execution context which

85_26

manages the RTCs' state machine.

85_27

For example, "on_activated" callback function is called when the RTC is activated (from INACTIVE to

85_28

ACTIVE state). In on_activated callback, initialization codes are implemented.

85_29

On the other hand, "on_deactivated" callback function is called when the RTC is deactivated (from

85_30

ACTIVE to INACTIVE state). In this callback, finalization codes are implemented.

85_31

"on_execute" is periodically called when the RTC is in ACTIVE state. Here, controlling or some

85_32

device management (ex., polling) functions are called.

85_33

These callbacks are called by the "execution context" object. If the special execution context is

85_34

attached to the RTCs, calling method or policy is modified (see execution context section).

85_35

Data port

85_36

A data port is an endpoint to communicate with other RTCs. The data ports have their types. Ports

85_37

with the same type can be connected to each other.

85_38

In OpenRTM-aist, primitive data types (like "TimedLong", "TimedDouble", and so on) are implemented.

85_39

Moreover, from OpenRTM-aist version 1.0, extra data types which are expected to be used commonly in

85_40

robotic systems were released as ExtendedDataType (like "TimedVelocity2D", "TimedPose2D", and so

85_41

on)

85_42

Developers can define their own data types by describing IDL file. Tools can parse the IDL file and

85_43

automatically generate the skeleton and stub file of the original data types.

85_44

Service port

85_45

The service port allows communicating much more flexibly than the data ports. Developers should

85_46

define service port interfaces by making their IDL files.

85_47

Execution contexts

85_48

Execution contexts handle the state-machine operations of RT-components. In OpenRTM-aist, several

85_49

kinds of execution contexts are provided. For example:

85_50

the periodic execution context, one of the most commonly used, provides periodic calls of the

85_51

"on_execute" event-handler (sensor acquisition or actuator control are usually implemented there);

85_52

the real-time execution context, which uses Linux's pre-emptive kernel function, supports

85_53

real-time operation of the RTC;

85_54

the extra trigger execution context is an important characteristic of OpenRTM-aist. It provides

85_55

the synchronization capability with dynamics simulators like OpenHRP-3.

85_56

Configuration

85_57

Configuration is a function which dynamically changes the parameters of the RTCs during run-time.

85_58

Configuration can be numeric and string.

85_59

Supported operating systems

85_60

OpenRTM-aist runs on Windows, Linux and macOS. Furthermore, VxWorks is supported experimentally.

85_61

Supported programming languages

85_62

Since OpenRTM-aist is based on the CORBA technology, it supports several programming languages,

85_63

including:

85_64

C++ Java Python Erlang (unofficial)

85_65

Tools RTC Builder

85_66

RTC Builder is a tool for skeleton-code generation. It is launched in the eclipse developmental

85_67

environment. OpenRTM-aist also supports RTC-template which is a command-line type skeleton-code

85_68

generation tool.

85_69

RT System Editor

85_70

RT System Editor is a tool for handling RTCs. RT system editor provides following services:

85_71

Referring RTCs' states Connecting RTCs' ports Configuring RTCs Activate/deactivate/reset RTCs

85_72

Save/restore the RT-system