Update for example_4_keys_instances for Python
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with example_4_keys_instances and compare its Python flow with PR #50 and the linked C++ guide, focusing on step 4.5. Trace monitor_lot_state, ChocolateLotState disposal, and the later ChocolateTemperature reader steps; done means the readers, monitors, and displayed output match the guide without temperature-topic output in step 4.5.
Written by the indexing model from the issue text.
Description
While running through the Python examples, I noticed a few updates to example 4 that seem to be more inline with the C++ step-by-step flow at https://community.rti.com/static/documentation/connext-dds/6.0.1/doc/manuals/connext_dds/getting_started/cpp11/intro_keys_instances.html#example-chocolate-factory.
Example edits in https://github.com/rticommunity/rticonnextdds-getting-started/pull/50
There may be some confusion as of step 4.5 when the user starts to learn about ChocolateLotState instance disposal. It looked like monitor_lot_state was being called for temperature topics (which aren't explored until 4.6+), leading to misleading output (e.g., "Received lot update: ").
The example changes above seem to fix this, in that the readers/monitors are hooked up correctly, the output matches the guide and they can see the instance disposal in step 4.5.
The user can still later explore the ChocolateTemperature reader support in steps 4.6+.
- Dominant language
- C++
- Stars
- 32
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rticommunity/rticonnextdds-getting-started
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
rticommunity/rticonnextdds-getting-started#75 · 1 comment ·
-
rticommunity/rticonnextdds-getting-started#69 · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
rticommunity/rticonnextdds-getting-started#63 · 1 comment ·
All issues in rticommunity/rticonnextdds-getting-started
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·