[DEFECT] Datasets unable to handle multiple values at the same time. (e.g. events in Modelica for example)

[klfrick2]

---

Defect Description

Describe the defect
In the Code Interface for the bouncing ball. The test was created with the values test_Dymola_code_interface_timedep.xml if multiple monte carlo seeds are attempted in the ensemble model.

What did you expect to see happen?

I would expect to be able to collapse a dataset based on the timesteps given out by the code.

What did you see instead?

An error saying the dataset cannot be collapsed along the time variable as

Do you have a suggested fix for the development team?

Not clear. I think Andrea mentioned the possibility of moderately editing the time variable on a relative basis of 1e-4. (e.g. if there are two steps at time 0.1seconds then the first one would be 0.1 and the second would be 0.10001. Not changing the trajectory, but giving the dataset multiple values to pivot along.

Describe how to Reproduce
Steps to reproduce the behavior:

1. Have a running version of Modelica on the machine.
2. Unzip the file.
3. Update the test_Dymola_code_interface_timedep.xml to point to the proper executables.
4. Try and run.

Screenshots and Input Files
Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.

DMInterfaceTestTimedep.zip

Platform (please complete the following information):
Windows 10.

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• 1. Is it tagged with a type: defect or task?
• 2. Is it tagged with a priority: critical, normal or minor?
• 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

---

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• 1. If the issue is a defect, is the defect fixed?
• 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?