Repository navigation
Usage of Tables #4743
Description
Is it safe to use the external objects Modelica.Blocks.Types.{ExternalCombiTimeTable, ExternalCombiTable1D, ExternalCombiTable2D} and the functions Modelica.Blocks.Tables.Internal.* in own models without using a Tables-Block?
e.g.
model MyModel
import Modelica.Blocks.Types.ExternalCombiTable1D;
import Modelica.Blocks.Types.Smoothness;
import Modelica.Blocks.Types.Extrapolation;
import Modelica.Blocks.Tables.Internal.getTable1DValue;
parameter Real table[:,2] = ...;
Real x = ...;
Real y = getTable1DValue(tableID, 1, x);
protected
parameter ExternalCombiTable1D tableID=ExternalCombiTable1D(
"NoName", "NoName",
material.table, 2:2,
Smoothness.MonotoneContinuousDerivative2,
Extrapolation.HoldLastPoint,
false, ",", 0) "External table object";
end;
Sometimes it is desired to utilize the same interpolation in an own (text-based / non-graphical) model without workaround:
model MyModel
Modelica.Blocks.Sources.RealExpression realExpression;
Modelica.Blocks.Tables.CombiTable1Ds combiTable1Ds;
equation
connect(realExpression.y, combiTable1Ds.u);
end MyModel;
Activity
AHaumer commentedon Feb 18, 2026
package Internal "Internal external object definitions for table functions that should not be directly utilized by the user"@beutlich @HansOlsson does that mean that usage of these functions is forbidden?
HansOlsson commentedon Feb 19, 2026
The statement indicates that it is discouraged, not forbidden; see https://www.rfc-editor.org/rfc/rfc2119
To me it is related to #4698 - i.e., the compatibility if you use Internal packages. (There's a similar issue with using the C-functions.)