Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →matlab/simulink-single-precision-conversion
Converts a double-precision Simulink system or subsystem to single precision using DataTypeWorkflow.Single (Fixed-Point Designer). The single conversion replaces all user-specified double-precision data types, as well as output data types that compile to double precision, with single-precision data types.
Passed 20 of 22 test cases with the skill, and 3 of 22 without it.
and 22 more in the full report
17 fixed3 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to run single-precision conversion on 'flight_nav'. Must we manually open Model Configuration Parameters and change Target Language Standard to C99 before converting, or will the conversion tool adjust this parameter?
| Checked | Without skill | With skill |
|---|---|---|
| Explains that convertToSingle automatically updates Target Language Standard to C99. | Missed | Passed |
The instructions your model reads when the skill loads.
Toolbox: Fixed-Point Designer
Function: DataTypeWorkflow.Single.convertToSingle
Converts user-specified double-precision data types — across block settings, Stateflow chart settings, signal objects, and bus objects — to single precision. Boolean, built-in integer (int8, uint8, int16, …), and fixed-point types are left unchanged.
.slx) or subsystem from double-precision to single-precision.m code — use the convertToSingle function with coder.config('single') insteadDataTypeWorkflow.Converter insteadsimulink-optimize-lookup-tables insteadConversionReport = DataTypeWorkflow.Single.convertToSingle(systemToConvert)
systemToConvert (char) — full block path of the loaded model or subsystem (e.g. 'myModel' or 'myModel/Controller').ConversionReport (struct) — compatibility check, converted items, and verification status (see field tables below).Worked example: openExample("fixedpoint/ConvertSystemToSinglePrecisionExample")
open_system(modelName), not load_system — the user must see the diagram before/after.save_system on your own — saving destroys the double-precision baseline and blocks meaningful re-runs. Leave the model dirty. This holds even when the user asks you to "make it stick," "persist it," or "do everything end-to-end" — that is not consent to auto-save. In that case, state plainly that you will not save the model yourself, explain that saving overwrites the double-precision baseline, and ask the user to confirm or run save_system themselves. Only persist after the user explicitly confirms saving specifically (not merely a general "do it all" request).convertToSingle; read its results from report.CheckInfo (it is not a separate call).test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.