-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathReplayServiceConfiguration.xml
More file actions
94 lines (82 loc) · 4.28 KB
/
ReplayServiceConfiguration.xml
File metadata and controls
94 lines (82 loc) · 4.28 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
<?xml version="1.0" encoding="UTF-8"?>
<!-- (c) 2024 Copyright, Real-Time Innovations, Inc. (RTI) All rights reserved.
RTI grants Licensee a license to use, modify, compile, and create derivative
works of the software solely for use with RTI Connext DDS. Licensee may
redistribute copies of the software provided that all such copies are
subject to this license. The software is provided "as is", with no warranty
of any type, including any warranty for fitness for any purpose. RTI is
under no obligation to maintain or support the software. RTI shall not be
liable for any incidental or consequential damages arising out of the use or
inability to use the software. -->
<!-- All of our files start with a dds tag -->
<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://community.rti.com/schema/7.3.0/rti_replay_service.xsd">
<replay_service name="RepServCfg">
<!-- Join domain 99 on Admin Console for more introspection on Replay Service -->
<administration>
<enabled>true</enabled>
<domain_id>99</domain_id>
</administration>
<!-- Storage settings -->
<storage>
<sqlite>
<!-- XCDR_AUTO = serialized format, which is more performant, but not human-readable -->
<!-- JSON_SQLITE = deserialized format, which is less performant, but human readable -->
<storage_format>XCDR_AUTO</storage_format>
<!-- Look for files in this folder in the current working directory -->
<database_dir>or_recording</database_dir>
</sqlite>
</storage>
<!-- Optionally select the begin and end times for the data to be replayed -->
<!-- <data_selection>
<time_range> -->
<!-- Sunday, September 13, 2020 12:26:40 PM -->
<!-- <begin_time>
<sec>1600000000</sec>
<nanosec>0</nanosec>
</begin_time> -->
<!-- Wednesday, May 18, 2033 3:33:20 AM -->
<!-- <end_time>
<sec>2000000000</sec>
<nanosec>0</nanosec>
</end_time>
</time_range>
</data_selection> -->
<!-- Specify playback behavior -->
<playback>
<!-- You can play the recording at 0.5x slower, 2x faster, etc. -->
<rate>1</rate>
<!-- When the recording ends, start over -->
<enable_looping>true</enable_looping>
</playback>
<!-- Replay Service DomainParticipant settings -->
<domain_participant name="reps/dp/OperationalData">
<domain_id>0</domain_id>
<domain_participant_qos base_name="RtiServicesLib::ReplayService"/>
</domain_participant>
<!-- <session> = subscriber -->
<session name="session">
<publisher_qos base_name="BuiltinQosLib::Generic.Common"/>
<!-- <topic> = DataWriter -->
<topic name="t/MotorControl" participant_ref="reps/dp/OperationalData">
<topic_name>t/MotorControl</topic_name>
<registered_type_name>SurgicalRobot::MotorControl</registered_type_name>
<!-- Using the same QoS profile we use in our applications -->
<datawriter_qos base_name="DataFlowLibrary::Command"/>
</topic>
<topic name="t/Vitals" participant_ref="reps/dp/OperationalData">
<topic_name>t/Vitals</topic_name>
<registered_type_name>PatientMonitor::Vitals</registered_type_name>
<!-- Using the same QoS profile we use in our applications -->
<datawriter_qos base_name="DataFlowLibrary::Streaming"/>
</topic>
<!-- This topic group would replay all the topics but the rti/* topics -->
<!-- <topic_group> = group of DataReaders -->
<!-- <topic_group name="ReplayAll" participant_ref="reps/dp/OperationalData">
<allow_topic_name_filter>*</allow_topic_name_filter>
<deny_topic_name_filter>rti/*</deny_topic_name_filter>
<datawriter_qos base_name="BuiltinQosLib::Generic.Common"/>
</topic_group> -->
</session>
</replay_service>
</dds>