qa: enforce strict SciMLTesting 2.4 checks (#497)

Co-authored-by: ChrisRackauckas-Claude <accounts@chrisrackauckas.com>

Author: ChrisRackauckas-Claude

Project.toml

@@ -1,6 +1,6 @@
 name = "ModelingToolkitStandardLibrary"
 uuid = "16a59e39-deab-5bd0-87e4-056b12336739"
-version = "2.29.5"
+version = "2.29.6"
 authors = ["Chris Rackauckas and Julia Computing"]
 
 [deps]
@@ -34,7 +34,7 @@ SafeTestsets = "0.1"
 SciCompDSL = "1"
 SciMLBase = "2, 3"
 SciMLStructures = "1.7.0"
-SciMLTesting = "2.1"
+SciMLTesting = "2.4"
 SymbolicIndexingInterface = "0.3.39"
 SymbolicUtils = "4.38.1"
 Symbolics = "7.4.1"

docs/make.jl

@@ -21,7 +21,6 @@ makedocs(
     sitename = "ModelingToolkitStandardLibrary.jl",
     authors = "Julia Computing",
     modules = [
-        ModelingToolkit,
         ModelingToolkitStandardLibrary,
         ModelingToolkitStandardLibrary.Blocks,
         ModelingToolkitStandardLibrary.Mechanical,
@@ -33,9 +32,10 @@ makedocs(
         ModelingToolkitStandardLibrary.Hydraulic,
         ModelingToolkitStandardLibrary.Hydraulic.IsothermalCompressible,
     ],
-    clean = true, doctest = false, linkcheck = true,
-    linkcheck_ignore = ["https://www.mathworks.com/help/simscape/ug/basic-principles-of-modeling-physical-networks.html#bq89sba-6"],
-    warnonly = [:docs_block, :missing_docs, :cross_references],
+    clean = true,
+    checkdocs = :exports,
+    doctest = true,
+    linkcheck = true,
     format = Documenter.HTML(
         assets = ["assets/favicon.ico"],
         canonical = "https://docs.sciml.ai/ModelingToolkitStandardLibrary/stable/"

docs/pages.jl

@@ -19,5 +19,7 @@ pages = [
         "Thermal Components" => "API/thermal.md",
         "Hydraulic Components" => "API/hydraulic.md",
         "Linear Analysis" => "API/linear_analysis.md",
+        "API Reference" => "API/reference.md",
+        "Domain API Reference" => "API/domain_reference.md",
     ],
 ]

docs/src/API/domain_reference.md

@@ -0,0 +1,15 @@
+# Domain API Reference
+
+```@autodocs
+Modules = [
+    ModelingToolkitStandardLibrary.Mechanical.Rotational,
+    ModelingToolkitStandardLibrary.Mechanical.Translational,
+    ModelingToolkitStandardLibrary.Mechanical.TranslationalModelica,
+    ModelingToolkitStandardLibrary.Mechanical.TranslationalPosition,
+    ModelingToolkitStandardLibrary.Mechanical.MultiBody2D,
+    ModelingToolkitStandardLibrary.Thermal,
+    ModelingToolkitStandardLibrary.Electrical,
+    ModelingToolkitStandardLibrary.Hydraulic.IsothermalCompressible,
+]
+Private = false
+```

docs/src/API/electrical.md

@@ -32,7 +32,6 @@ Capacitor
 Inductor
 IdealOpAmp
 Diode
-HeatingDiode
 VariableResistor
 NMOS
 PMOS
@@ -56,35 +55,3 @@ MultiSensor
 Voltage
 Current
 ```
-
-## Digital Gates
-
-```@docs
-Not
-And
-Nand
-Or
-Nor
-Xor
-Xnor
-```
-
-## Digital Components
-
-```@docs
-HalfAdder
-FullAdder
-MUX
-DEMUX
-Encoder
-Decoder
-```
-
-## Digital Sources
-
-```@docs
-PulseDiff
-Set
-Reset
-Pulse
-```

docs/src/API/hydraulic.md

@@ -1,5 +1,9 @@
 # [ModelingToolkit Standard Library: Hydraulic Components](@id hydraulic)
 
+```@docs
+ModelingToolkitStandardLibrary.Hydraulic
+```
+
 ```@contents
 Pages = ["hydraulic.md"]
 Depth = 3

docs/src/API/linear_analysis.md

@@ -4,15 +4,15 @@
 
     The interface described here is currently experimental and at any time subject to breaking changes not respecting semantic versioning.
 
-Linear analysis refers to the process of linearizing a nonlinear model and analysing the resulting linear dynamical system. To facilitate linear analysis, ModelingToolkitStandardLibrary provides the concept of an [`AnalysisPoint`](@ref), which can be inserted in-between two causal blocks (such as those from the `Blocks` sub module). Once a model containing analysis points is built, several operations are available:
+Linear analysis refers to the process of linearizing a nonlinear model and analysing the resulting linear dynamical system. To facilitate linear analysis, ModelingToolkitStandardLibrary provides the concept of an `AnalysisPoint`, which can be inserted in-between two causal blocks (such as those from the `Blocks` sub module). Once a model containing analysis points is built, several operations are available:
 
-  - [`get_sensitivity`](@ref) get the [sensitivity function (wiki)](https://en.wikipedia.org/wiki/Sensitivity_(control_systems)), $S(s)$, as defined in the field of control theory.
-  - [`get_comp_sensitivity`](@ref) get the complementary sensitivity function $T(s) : S(s)+T(s)=1$.
-  - [`get_looptransfer`](@ref) get the (open) loop-transfer function where the loop starts and ends in the analysis point. For a typical simple feedback connection with a plant $P(s)$ and a controller $C(s)$, the loop-transfer function at the plant output is $P(s)C(s)$.
-  - [`linearize`](@ref) can be called with two analysis points denoting the input and output of the linearized system.
-  - [`open_loop`](@ref) return a new (nonlinear) system where the loop has been broken in the analysis point, i.e., the connection the analysis point usually implies has been removed.
+  - `get_sensitivity` gets the [sensitivity function (wiki)](https://en.wikipedia.org/wiki/Sensitivity_(control_systems)), $S(s)$, as defined in the field of control theory.
+  - `get_comp_sensitivity` gets the complementary sensitivity function $T(s) : S(s)+T(s)=1$.
+  - `get_looptransfer` gets the (open) loop-transfer function where the loop starts and ends in the analysis point. For a typical simple feedback connection with a plant $P$ and a controller $C$, the loop-transfer function at the plant output is $P(s)C(s)$.
+  - `linearize` can be called with two analysis points denoting the input and output of the linearized system.
+  - `open_loop` returns a new nonlinear system where the loop has been broken at the analysis point.
 
-An analysis point can be created explicitly using the constructor [`AnalysisPoint`](@ref), or automatically when connecting two causal components using `connect`:
+An analysis point can be created explicitly using the `AnalysisPoint` constructor, or automatically when connecting two causal components using `connect`:
 
 ```julia
 connect(comp1.output, :analysis_point_name, comp2.input)
@@ -34,7 +34,7 @@ The directionality of an analysis point can be thought of as an arrow in a block
 
 This is signified by the name being the middle argument to `connect`.
 
-Of the above mentioned functions, all except for [`open_loop`](@ref) return the output of [`ModelingToolkit.linearize`](@ref), which is
+Of the above mentioned functions, all except for `open_loop` return the output of `ModelingToolkit.linearize`, which is
 
 ```julia
 matrices, simplified_sys = linearize(...)
@@ -148,7 +148,3 @@ Pages   = ["Blocks/analysis_points.jl"]
 Order   = [:function, :type]
 Private = false
 ```
-
-```@docs
-ModelingToolkit.linearize
-```

docs/src/API/mechanical.md

@@ -1,5 +1,9 @@
 # ModelingToolkit Standard Library: Mechanical Components
 
+```@docs
+ModelingToolkitStandardLibrary.Mechanical
+```
+
 ```@contents
 Pages = ["mechanical.md"]
 Depth = 3

docs/src/API/reference.md

@@ -0,0 +1,8 @@
+# API Reference
+
+```@autodocs
+Modules = [
+    ModelingToolkitStandardLibrary.Blocks,
+]
+Private = false
+```

docs/src/connectors/connections.md

@@ -3,7 +3,7 @@
 In Physical Network Acausal modeling, each physical domain must define a **connector** to combine model components.  Each physical domain **connector** defines a minimum of 2 variables, one which is called a *Through* variable, and one which is called an *Across* variable.  Both Modelica and SimScape define these variables in the same way:
 
   - [Modelica Connectors](https://mbe.modelica.university/components/connectors/#acausal-connection)
-  - [SimScape Connectors](https://www.mathworks.com/help/simscape/ug/basic-principles-of-modeling-physical-networks.html#bq89sba-6)
+  - Simscape connector documentation
 
 However, the standard libraries differ on the selection of the Across variable for the Mechanical Translation and Rotation libraries, Modelica choosing position and angle and SimScape choosing velocity and angular velocity, respectively for Translation and Rotation.  Modelica describes their decision [here](https://mbe.modelica.university/components/connectors/simple_domains/).  In summary, they would like to provide less integration in the model to avoid lossy numerical behavior, but this decision assumes the lowest order derivative is needed by the model.  Numerically it is possible to define the connector either way, but there are some consequences of this decision, and therefore we will study them in detail here as they relate to ModelingToolkit.