You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Feature/con 177 (#38)
* CON-177: Added support/tests for addition sampleinfo fields
* CON-177: Added unit tests for sample/view/instance state
* CON-177: PR Feedback
- Added possible values of the strings to the docs
- Updated unit tests with new possible values
* CON-188: docs + tests (#40)
* CON-188: docs + tests
* CON-188: Functionality changes
- Always return all fields (not None for non-key members)
- updated docs + tests for this
* CON-188: PR feedback
Applied the feedback from the JS review
* CON-188: Fix typo
* Performance tests for Python get/set sequence (#41)
* Performance tests for Python get/set sequence
* Separated tests
* Update test/python/test_rticonnextdds_performance.py
Co-authored-by: Alex Campos <[email protected]>
* You can now set the number of iterations on the command line
* Minor changes
Co-authored-by: Alex Campos <[email protected]>
* Feature/native dd perf (#42)
* Added additional performance tests that use native DD API
* Disable tests by default
* CON-188: Fixed code block in docs (#44)
* Feature/con 209 (#43)
* CON-209: Test support for multiple urls in connector creation
* CON-209: Update docs
* CON-163: Added a unit test for license error (fix is in core) (#46)
* CON-163: Added a (currently failing) unit test for license error
* CON-163: Updated copyright
* CON-163: PR feedback
* CON-212: Added CONTRIBUTING.md file (#45)
* CON-214: Added test for creating Connector with participant_qos (#47)
* CON-211: updating all links to other docs per new doc tree structure, for python connector
* CON-211: fixed a couple of link-related issues in connector-py that I missed in first update
* CON-211: updated title of core GSG to remove "Core Libraries"
* CORE-10744: Update documentation for new default system resources (#50)
* CON-215: Added release notes (#48)
* CON-215: Added release notes
* CON-215: Fixed issue IDs
* CON-215: Fix IDs again
* CON-215: Fix title indentation
* CON-215: Added notes from CON-188
* CON-215: Added more issues
* CON-215: Fix codeblock
* CON-215: Add issue #
* Apply suggestions from code review
* Update docs/release_notes.rst
* CON-215: release notes review and edits, and a few other tweaks to capitalization in other files
* Update docs/release_notes.rst
* CON-215: Reverted LICENSE.pdf
Co-authored-by: rkorte <[email protected]>
* CON-194: added statement and link to Python API doc so users can understand the differences
* CON-188: Updates instance support section of features.rst (#53)
* PLATFORMS-1925. Updated supported platforms to match Hercules PAM.
* PLATFORMS-1925. Added trademark symbols.
* Introduce EOL normalisation (#58)
With this, License.pdf should not longer show up as changed on Windows
* Feature/core 11069 (#59)
* CORE-11069: Replaced deprecated XML tags in documentation and public XML
* CORE-11069: Also update test XML
* Feature/con 174 armv8 (#57)
* CON-174: Handle ARMV8 arch
* CON-174: Minor edit
* Fix string
* CON-174: Handle other arm strings
- Handle all of aarch64, aarch64_be, armv8b, armv8l
- Also load the library for (deprecated) armv6
* GREEN-2058: Fixed string checking when setting invalid my_enum from dict (#61)
* GREEN-2058: Added tests for new functionality in DD Parser (#62)
Co-authored-by: Sam Raeburn <[email protected]>
* Feature/dir renames (#64)
* Updated the loading of native libraries
* - Update common libs
- Remove support for 32 bit Win + Linux
* Updated native libs
* Explicitly load the nddsc and nddscore libraries on Windows
Co-authored-by: Sam Raeburn <[email protected]>
* CON-221: Added docs for ability to load libs (#55)
* CON-221: Added docs for ability to load libs
* PR feedback
* PR Feedback
* working on LICENSE.pdf and gitattributes
Co-authored-by: rkorte <[email protected]>
Co-authored-by: Sam Raeburn <[email protected]>
* Updated platforms in the relaese notes (#65)
* Updated platforms in the relaese notes
* Removed symbol from ARMv7 platform name
Co-authored-by: Sam Raeburn <[email protected]>
* Feature/update version (#66)
* Update README for 1.1.0 preview
* Update setup.py for version 1.1.0 preview
* Updated version in setup.py to 1.1.0.rc2
* Updated submodule to use commit feature/update-libs-internal-rel
Co-authored-by: Sam Raeburn <[email protected]>
* Updated version in documentation to 1.1.0.rc2 (#67)
* Updated version in documentation to 1.1.0.rc2
* - Now possible to do rti.Connector.version() to obtain current version
* - Updated blue colour used in docs
- Updated docs version to 1.1.0
- Removed version() API - needs further thought before implementation
Co-authored-by: Sam Raeburn <[email protected]>
* Update release_notes.rst
Add 16.04 Ubuntu
* Updated the Platforms notes to include Ubuntu 16.04 (x64 + ARMv8) (#68)
* Updated the Platforms notes to include Ubuntu 16.04 (x64 + ARMv8)
* Added support for ARMv8 to whats new 1.1.0
* fix typo
Co-authored-by: Sam Raeburn <[email protected]>
* CON-211: testing all links to core docs, fixing few that were broken - python
* CON-194: python changes: update copyright page and copyright year tagline
* Accept 32-bit archs if libraries are swapped
* HERCULES-186: updates to licenses doc for python
* HERCULES-186: modified lua and json-parser in Connector doc python
* Document dependency on Connext version for dynamic libs (#74)
* Document dependency on Connext version for dynamic libs
* - PR feedback to clarify wording
- Adding missing sentence from release notes about Connext DDS version
* PR feedback
Co-authored-by: Sam Raeburn <[email protected]>
* Update setup.py for version 1.1.0
* Update native libraries to version 6.1.0
Co-authored-by: Alex Campos <[email protected]>
Co-authored-by: rkorte <[email protected]>
Co-authored-by: Adelle Olson <[email protected]>
Co-authored-by: rkorte <[email protected]>
Co-authored-by: Sam Raeburn <[email protected]>
In order to accept your pull request, we need you to sign a Contributor License Agreement (CLA). Complete your CLA here: http://community.rti.com/cla. You only need to do this once, we cross-check your Github username with the list of contributors who have signed the CLA.
The *Connext DDS* C, C++, Java and .NET APIs can also load the same XML files
@@ -77,11 +77,11 @@ and ``shapesize``:
77
77
Types are associated with *Topics*, as explained in the next section, :ref:`Domain Library`.
78
78
79
79
.. hint::
80
-
You can define your types in IDL and convert them to XML with `rtiddsgen <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/code_generator/html_files/RTI_CodeGenerator_UsersManual/index.htm#code_generator/UsersManual/UsersManual_Title.htm>`__.
80
+
You can define your types in IDL and convert them to XML with `rtiddsgen <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/code_generator/users_manual/index.htm>`__.
81
81
For example: ``rtiddsgen -convertToXml MyTypes.idl``
82
82
83
83
For more information about defining types, see
84
-
`Creating User Data Types with XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/Creating_User_Data_Types_with_Extensible.htm>`__
84
+
`Creating User Data Types with XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/Creating_User_Data_Types_with_Extensible.htm>`__
85
85
in the *RTI Connext DDS Core Libraries User's Manual*.
86
86
87
87
For more information about accessing data samples, see :ref:`Accessing the data`.
@@ -91,10 +91,10 @@ Domain library
91
91
92
92
A domain library is a collection of domains. A domain specifies:
93
93
94
-
* A `domain id <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/ChoosingDomainID.htm>`__.
94
+
* A `domain id <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/ChoosingDomainID.htm>`__.
95
95
* A set of registered types (from a subset of the types in ``<types>``).
96
96
A registered type can have a local name.
97
-
* A set of `topics <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm>`__,
97
+
* A set of `topics <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/WorkingWithTopics.htm>`__,
98
98
which are used by *DataReaders* and *DataWriters*.
99
99
100
100
.. code-block:: xml
@@ -108,7 +108,7 @@ A domain library is a collection of domains. A domain specifies:
108
108
</domain_library>
109
109
110
110
For more information about the format of a domain library, see
All DDS entities have an associated `quality of service (QoS) <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/QosPolicies.htm>`__.
150
+
All DDS entities have an associated `quality of service (QoS) <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/QosPolicies.htm>`__.
151
151
There are several ways to configure it.
152
152
153
153
You can define a QoS profile and make it the default. The following example
@@ -181,7 +181,7 @@ You can define the QoS for each individual entity:
Logging can be configured as explained in `Configuring Logging via XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/Configuring_Logging_via_XML1.htm>`__.
242
+
Logging can be configured as explained in `Configuring Logging via XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/Configuring_Logging_via_XML1.htm>`__.
243
243
244
244
For example, to increase the logging verbosity from the default (ERROR) to
245
245
WARNING, define a ``qos_profile`` with the attribute
The XML file defines your types, QoS profiles, and DDS Entities. *Connector*
25
-
uses the XML schema of `RTI's XML-Based Application Creation <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/xml_application_creation/html_files/RTI_ConnextDDS_CoreLibraries_XML_AppCreation_GettingStarted/index.htm#XMLBasedAppCreation/UnderstandingPrototyper/XMLTagsConfigEntities.htm%3FTocPath%3D5.%2520Understanding%2520XML-Based%2520Application%2520Creation%7C5.5%2520XML%2520Tags%2520for%2520Configuring%2520Entities%7C_____0>`__.
25
+
uses the XML schema of `RTI's XML-Based Application Creation <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/XMLTagsConfigEntities.htm>`__.
26
26
27
27
The previous code loads the ``<domain_participant>`` named *MyParticipant* in
28
28
the ``<domain_participant_library>`` named *MyParticipantLibrary*, which is defined in the
@@ -40,7 +40,7 @@ When you create a :class:`Connector`, the DDS *DomainParticipant* that you selec
40
40
and all its contained entities (*Topics*, *Subscribers*, *DataReaders*,
41
41
*Publishers*, *DataWriters*) are created.
42
42
43
-
For more information about the DDS entities, see `Part 2 - Core Concepts <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/PartCoreConcepts.htm#partcoreconcepts_4109331811_915546%3FTocPath%3DPart%25202%253A%2520Core%2520Concepts%7C_____0>`__
43
+
For more information about the DDS entities, see `Core Concepts <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/PartCoreConcepts.htm>`__
44
44
in the *RTI Connext DDS Core Libraries User's Manual*.
Copy file name to clipboardExpand all lines: docs/data.rst
+51-1Lines changed: 51 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -411,7 +411,7 @@ To clear a member, set it to ``None`` explicitly::
411
411
412
412
For more information about optional members in DDS, see the *Getting Started Guide
413
413
Addendum for Extensible Types*,
414
-
`Section 3.2 Optional Members <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/getting_started_extras/html_files/RTI_ConnextDDS_CoreLibraries_GettingStarted_ExtensibleAddendum/index.htm#ExtensibleTypesAddendum/Optional_Members.htm>`__.
414
+
`Optional Members <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/extensible_types_guide/index.htm#extensible_types/Optional_Members.htm>`__.
415
415
416
416
Accessing unions
417
417
^^^^^^^^^^^^^^^^
@@ -448,3 +448,53 @@ The type returned by the operator is a dict for unions.
448
448
The same limitations described in
449
449
:ref:`Accessing basic members (numbers, strings and booleans)`
450
450
about using ``__getitem__`` apply here.
451
+
452
+
Accessing key values of disposed samples
453
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
454
+
455
+
Using :meth:`Output.write`, an :class:`Output` can write data, or dispose or
456
+
unregister an instance.
457
+
Depending on which of these operations is performed, the ``instance_state`` of the
458
+
received sample will be ``'ALIVE'``, ``'NOT_ALIVE_NO_WRITERS'`` or ``'NOT_ALIVE_DISPOSED'``.
459
+
If the instance was disposed, this ``instance_state`` will be ``'NOT_ALIVE_DISPOSED'``.
460
+
In this state, it is possible to access the key fields of the instance that was disposed.
461
+
462
+
.. note::
463
+
:attr:`SampleInfo.valid_data` will be false when the :attr:`SampleInfo.instance_state`
464
+
is ``'NOT_ALIVE_DISPOSED'``. In this situation it's possible to access the
465
+
key fields in the received sample.
466
+
467
+
The key fields can be accessed as follows:
468
+
469
+
.. testcode::
470
+
471
+
# The output and input are using the following type:
472
+
# struct ShapeType {
473
+
# @key string<128> color;
474
+
# long x;
475
+
# long y;
476
+
# long shapesize;
477
+
# }
478
+
479
+
output.instance["x"] = 4
480
+
output.instance["color"] = "Green"
481
+
# Assume that some data associated with this instance has already been sent
482
+
output.write(action="dispose")
483
+
input.wait()
484
+
input.take()
485
+
sample = input.samples[0]
486
+
487
+
if sample.info["instance_state"] == "NOT_ALIVE_DISPOSED":
488
+
# sample.info.get('valid_data') will be false in this situation
489
+
# Only the key-fields should be accessed
490
+
color = sample["color"] # 'Green'
491
+
# The fields 'x','y' and 'shapesize' cannot be retrieved because they're
492
+
# not part of the key
493
+
# You can also call get_dictionary() to get all of the key fields.
494
+
# Again, only the key fields returned within the dictionary should
0 commit comments