Check for potential ordering issues involving data store access

Look for read/write issues which may cause inaccuracies in the results.

Description

During an Update Diagram, identify potential issues relating to read-before-write, write-after-read, and write-after-write conditions for data store blocks.

Results and Recommended Actions

	Condition	Recommended Action
	Reading and writing	Consider restructuring your model
	(read-before-write or	so that the Data Store Read block
	write-after-read condition) occur out	executes before the Data Store Write
	of order.	block.
	Multiple writes occur within a single	Change the model to write data only
	time step.	once per time step or refer to the
		following Tips section.

Tips

This check performs a static analysis which might not identify every instance of improper usage. Specifically, Function-Call Subsystems, Stateflow Charts, MATLAB for code generation, For Iterator Subsystems, and For Each Subsystems can cause both missed detections and false positives. For a more comprehensive check, consider enabling the following diagnostics on the Diagnostics > Data Validity pane in the Configuration Parameters dialog box: “Detect read before write”, “Detect write after read”, and “Detect write after write”.

Check for potential ordering issues involving data store access

Description

Results and Recommended Actions

Tips

See Also