Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A target property for handling downstream next event tag (DNET) signal #2400

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

byeonggiljun
Copy link
Collaborator

@byeonggiljun byeonggiljun commented Aug 13, 2024

This PR adds a target property for the signal downstream next event tag. When the property is true, the federate launcher turns on the option DNET of the RTI.

This PR is a companion PR of reactor-c#349.

There is another companion PR, lf-lang/reactor-ts#296.

@byeonggiljun byeonggiljun added federated enhancement Enhancement of existing feature labels Aug 13, 2024
Copy link
Collaborator

@edwardalee edwardalee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Modulo the open questions, this looks good to me, but merging should wait for the corresponding reactor-c PR. I will review that next.

.github/workflows/ts-tests.yml Outdated Show resolved Hide resolved
Comment on lines 4 to 5
* If true, the RTI sends DNET signals during the execution of federation. The default is ture (for
* now, for testing).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* If true, the RTI sends DNET signals during the execution of federation. The default is ture (for
* now, for testing).
* @brief Target property turning on or off the DNET signal optimization.
*
* If this target property is true, the RTI sends DNET (downstream next event tag) signals to an upstream federate
* to tell the federate that sending LTC and NET signals with tags less than the specified value is unnecessary.
* The default is true.

Note that if we make the default value false, this feature will not be adequately tested. Is there any reason it should not be true by default?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the comment in 83bd58f.

I'm concerned that if every reaction sends a message every time it's triggered, the DNET may be useless. I'm trying to run some applications to see whether the impact is negligible, but I'm struggling to generalize the cases.

I'll make sure to show you a convincing result shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement of existing feature federated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants