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.

Sign up for GitHub

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

Jump to bottom

optional outputs of lookup tables #10

Open
klausschuch opened this issue May 14, 2024 · 1 comment
Open

optional outputs of lookup tables #10

klausschuch opened this issue May 14, 2024 · 1 comment

Comments

@klausschuch
Copy link
Collaborator

should we have outputs defined or treat outputs just like any other related variable?
if we have outputs, how to represent them and what are the constraints?
@klausschuch
Copy link
Collaborator Author

Meeting 14.5.2024:
we want to have optional outputs as well
variableKind org.fmi-standard.fmi-ls-struct.codomain_output
since we only allow one input per domain, we only allow at most one output per codomain.
for nonscalars, the sizes of the outputs have to be equal to the sizes of the input variable, if input is given.

@chrbertsch chrbertsch linked a pull request May 16, 2024 that will close this issue
Rough outline and first example #3
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rough outline and first example chrbertsch/fmi-ls-struct
1 participant
@klausschuch