Difference between revisions of "Analytica model style guide"

Revision as of 02:35, 17 February 2016

The design of Analytica, including influence diagrams and structured model documentation, encourage building models that are much more transparent than other modeling environments, especially spreadsheets. Even so, there are things you can do to improve or destroy transparency with Analytica or any modeling tool! These guidelines help you maintain transparency in Analytica, and other environments too.

Don't embed constants in definitions

Define conversion constants as Constant objects instead of embedding them in definitions. For example, suppose

Revision as of 19:22, 6 August 2015 (view source) Max (talk \| contribs) (stub for an important new page)		Revision as of 02:35, 17 February 2016 (view source) Bbecane (talk \| contribs) Newer edit →
Line 1:		Line 1:
		+	[[Category: Documentation guidelines]]
		+
	The design of Analytica, including influence diagrams and structured model documentation, encourage building models that are much more transparent than other modeling environments, especially spreadsheets. Even so, there are things you can do to improve or destroy transparency with Analytica or any modeling tool! These guidelines help you maintain transparency in Analytica, and other environments too.		The design of Analytica, including influence diagrams and structured model documentation, encourage building models that are much more transparent than other modeling environments, especially spreadsheets. Even so, there are things you can do to improve or destroy transparency with Analytica or any modeling tool! These guidelines help you maintain transparency in Analytica, and other environments too.