Skip to content

Conversation

@dbeckerAC
Copy link

Reference to a related issue in the repository

Related to PR Comment

Add a description

Add specification for MotionRequest top level message

Mention a member

@kmeids @max-rosin for review

Check the checklist

  • I have performed a self-review of my own code.
  • I have made corresponding changes to the documentation for osi-sensor-model-packaging.
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests / travis ci pass locally with my changes.

see here:
https://github.com/OpenSimulationInterface/osi-sensor-model-packaging/runs/2296152415

@pmai
Copy link
Contributor

pmai commented Jan 16, 2023

CCB 2023-01-16: PR should be updated to new documentation structure, more than one input/output should be allowed (using the general rules).

Signed-off-by: Daniel Becker <danielb.ac@me.com>
@dbeckerAC dbeckerAC force-pushed the feature/tp/SpecMotionRequest branch from 18d7a24 to 155cde9 Compare January 30, 2023 08:36
dbeckerAC and others added 2 commits January 30, 2023 09:38
Signed-off-by: Daniel Becker <daniel.becker4@rwth-aachen.de>
@dbeckerAC dbeckerAC force-pushed the feature/tp/SpecMotionRequest branch from 21da0fe to 174b644 Compare January 30, 2023 08:51
@dbeckerAC
Copy link
Author

CCB 2023-01-16: PR should be updated to new documentation structure, more than one input/output should be allowed (using the general rules).

Done.

Also, I did not see any "must" requirements in other specifications anymore. Do we still use them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants