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

Proposal for enhancement in Blocks.Tables.CombiTable1D,1Ds,2D and Blocks.Sources.CombiTimeTable #628

Closed
modelica-trac-importer opened this issue Jan 14, 2017 · 8 comments
Assignees
Labels
enhancement New feature or enhancement L: Blocks Issue addresses Modelica.Blocks
Milestone

Comments

@modelica-trac-importer
Copy link

Reported by gfontanella on 19 Oct 2011 12:43 UTC
Currently the table models in Modelica.Blocks.Tables do not allow the user to set any other interpolation method than the linear and the first derivative coutinuous ones.

I think it might be useful to add a "No interpolation" option, where each sampled value is simply held until the next one occurs.

This could really come in handy whenever the original data is stored by a monitoring system which only logs a value when this is different from the previously registered one.


Migrated-From: https://trac.modelica.org/Modelica/ticket/628

@modelica-trac-importer modelica-trac-importer added this to the MSL3.2.1 milestone Jan 14, 2017
@modelica-trac-importer modelica-trac-importer added enhancement New feature or enhancement L: Blocks Issue addresses Modelica.Blocks labels Jan 14, 2017
@modelica-trac-importer
Copy link
Author

Comment by ahaumer on 19 Oct 2011 17:17 UTC
For Sources.CombiTimeTable this is rather clear, since time is continuously increasing and whenever a new time value of the table definition is reached, the ouput jumps to the new value; this makes sense to model switching behaviour stored in the table.
For Tables.CombiTable1D,1Ds,2D which interpolate with respect to an input which could also decrease this has to be considered carefully.

@modelica-trac-importer modelica-trac-importer changed the title Proposal for enhancement in Modelica.Blocks.Tables.CombiTable1D,1Ds,2D Proposal for enhancement in Blocks.Tables.CombiTable1D,1Ds,2D and Blocks.Sources.CombiTimeTable Jan 14, 2017
@modelica-trac-importer
Copy link
Author

Comment by ahaumer on 19 Oct 2011 17:27 UTC
As a workaround, you would have to define the table in a special way - here is an example:
Instead of table=[0, 0; 2.5, 1; 3, 0] - which defines a triangle for linear interpolation - you have to define steps: table=[0, 0; 2.5, 0; 2.5, 1; 3, 1; 3, 0] - which defines a step 0->1 at time = 2.5 and a step 1->0 at time = 3.

@modelica-trac-importer
Copy link
Author

Modified by ahaumer on 2 Mar 2012 09:08 UTC

@modelica-trac-importer
Copy link
Author

Comment by anonymous on 10 Dec 2012 16:22 UTC
This feature request could also be part of the upcoming call for a quotation.

@modelica-trac-importer
Copy link
Author

Comment by otter on 2 Jan 2013 20:58 UTC
This feature has been included in the call for quotations for an open source implementation of the MSL table blocks and will therefore be included in MSL 3.2.1.

@modelica-trac-importer
Copy link
Author

Changelog removed by otter on 2 Jan 2013 20:58 UTC

@modelica-trac-importer
Copy link
Author

Comment by otter on 20 May 2013 07:32 UTC
Fixed in 8b1c969:

The new open source implementation of block Modelica.Blocks.Sources.CombiTimeTable contains a new option Smoothness.ConstantSegments in order to not interpolate but only hold the last value.

@modelica-trac-importer
Copy link
Author

Changelog modified by otter on 20 May 2013 07:32 UTC
New feature of CombiTimeTable block: Optionally, the table values are not interpolated but the hold during the table points

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or enhancement L: Blocks Issue addresses Modelica.Blocks
Projects
None yet
Development

No branches or pull requests

2 participants