Developer's Manual - Revision history

Jpye: /* CUnit test suites */

2026-02-07T22:57:18Z

CUnit test suites

← Older revision		Revision as of 22:57, 7 February 2026
Line 403:		Line 403:
	To build a copy of CUnit that works with ASCEND, we suggest you use		To build a copy of CUnit that works with ASCEND, we suggest you use

	<source lang=sh>		<source lang=shellscript>
	sudo apt-get install automake autoconf libtool		sudo apt-get install automake autoconf libtool
	svn co https://svn.code.sf.net/p/cunit/code/branches/mingw64 cunit		svn co https://svn.code.sf.net/p/cunit/code/branches/mingw64 cunit
Line 417:		Line 417:
	Once you have got CUnit installed on your system, you should have a file <tt>/usr/local/lib/libcunit.so</tt> (check that!). Then, you should be able to build and run the test suites using		Once you have got CUnit installed on your system, you should have a file <tt>/usr/local/lib/libcunit.so</tt> (check that!). Then, you should be able to build and run the test suites using

	<source lang=sh>		<source lang=shellscript>
	# enter your ascend 'working directory':		# enter your ascend 'working directory':
	cd ~/ascend		cd ~/ascend

Jpye: /* CUnit test suites */

2018-08-05T07:03:13Z

CUnit test suites

← Older revision		Revision as of 07:03, 5 August 2018
Line 409:		Line 409:
	./bootstrap		./bootstrap
	./configure --prefix=/usr/local --enable-examples --enable-debug		./configure --prefix=/usr/local --enable-examples --enable-debug
	make -j2		make -j4
	sudo make install		sudo make install
	</source>		</source>

Jpye: /* CUnit test suites */

2018-08-05T07:02:34Z

CUnit test suites

← Older revision		Revision as of 07:02, 5 August 2018
Line 405:		Line 405:
	<source lang=sh>		<source lang=sh>
	sudo apt-get install automake autoconf libtool		sudo apt-get install automake autoconf libtool
	svn co https://~~cunit~~.~~svn~~.~~sourceforge~~.net/~~svnroot~~/cunit/branches/mingw64 cunit		svn co https://svn.code.sf.net/p/cunit/code/branches/mingw64 cunit
	cd cunit		cd cunit
	./bootstrap		./bootstrap

Jpye: /* Expressions and relations */

2018-06-18T05:38:02Z

Expressions and relations

← Older revision		Revision as of 05:38, 18 June 2018
Line 99:		Line 99:
	=== Expressions and relations ===		=== Expressions and relations ===

	During parsing, <tt>struct Expr</tt> object trees ({{src\|ascend/compiler/expr_types.h}}) are created using calls to the functions in {{src\|ascend/compiler/exprs.h}}. These expression allow complex mathematical structures to be represented, and also to be evaluated (<tt>EvaluateExpr</tt> (see {{src\|~~ascennd~~/compiler/evaluate.h}}).		During parsing, <tt>struct Expr</tt> object trees ({{src\|ascend/compiler/expr_types.h}}) are created using calls to the functions in {{src\|ascend/compiler/exprs.h}}. These expression allow complex mathematical structures to be represented, and also to be evaluated (<tt>EvaluateExpr</tt> (see {{src\|ascend/compiler/evaluate.h}}).

	However, these structures include references to <tt>struct Name</tt>, which means identifying the instance being referred to still needs to be done (bearing in mind the local naming context). This process is relatively expensive. For the solver, faster methods are required. Each relation is converted into a <tt>struct relation</tt> {{src\|ascend/compiler/relation_type.h}}, in which the relevant variables are kept in an ordered list (<tt>struct gl_list *vars</tt>). This allows much faster evaluation.		However, these structures include references to <tt>struct Name</tt>, which means identifying the instance being referred to still needs to be done (bearing in mind the local naming context). This process is relatively expensive. For the solver, faster methods are required. Each relation is converted into a <tt>struct relation</tt> {{src\|ascend/compiler/relation_type.h}}, in which the relevant variables are kept in an ordered list (<tt>struct gl_list *vars</tt>). This allows much faster evaluation.

Jpye: /* Expressions and relations */

2018-06-18T03:40:09Z

Expressions and relations

← Older revision		Revision as of 03:40, 18 June 2018
Line 99:		Line 99:
	=== Expressions and relations ===		=== Expressions and relations ===

	During parsing, <tt>struct Expr</tt> object trees ({{src\|ascend/compiler/expr_types.h}}) are created~~, which~~ allow complex mathematical structures to be represented, and also evaluated (<tt>EvaluateExpr</tt> (see {{src\|ascennd/compiler/evaluate.h}})		During parsing, <tt>struct Expr</tt> object trees ({{src\|ascend/compiler/expr_types.h}}) are created using calls to the functions in {{src\|ascend/compiler/exprs.h}}. These expression allow complex mathematical structures to be represented, and also to be evaluated (<tt>EvaluateExpr</tt> (see {{src\|ascennd/compiler/evaluate.h}}).

	However, these structures include references to <tt>struct Name</tt>, which means identifying the instance being referred to still needs to be done~~, which~~ is expensive. For the solver, faster methods are required. Each relation is converted into a <tt>struct relation</tt> {{src\|ascend/compiler/relation_type.h}}, in which the relevant variables are kept in an ordered list (<tt>struct gl_list *vars</tt>). This allows much faster evaluation.		However, these structures include references to <tt>struct Name</tt>, which means identifying the instance being referred to still needs to be done (bearing in mind the local naming context). This process is relatively expensive. For the solver, faster methods are required. Each relation is converted into a <tt>struct relation</tt> {{src\|ascend/compiler/relation_type.h}}, in which the relevant variables are kept in an ordered list (<tt>struct gl_list *vars</tt>). This allows much faster evaluation.

	So-called 'token relations' are the normal approach in ASCEND. Such relations can optionally be compiled to C code (<tt>bintoken</tt>, see above). There are also black box relations (external relations) which are created using a different kind of relation syntax. Finally, there are glass box relations, which were implemented by Kirk Abbott but are not fully operational in current ASCEND versions. (see 'RANT' in {{src\|ascend/compiler/relation.h}}).		So-called 'token relations' are the normal approach in ASCEND. Such relations can optionally be compiled to C code (<tt>bintoken</tt>, see above). There are also black box relations (external relations) which are created using a different kind of relation syntax. Finally, there are glass box relations, which were implemented by Kirk Abbott but are not fully operational in current ASCEND versions. (see 'RANT' in {{src\|ascend/compiler/relation.h}}).

Jpye: /* Expressions and relations */

2018-06-18T02:47:14Z

Expressions and relations

← Older revision		Revision as of 02:47, 18 June 2018
Line 99:		Line 99:
	=== Expressions and relations ===		=== Expressions and relations ===

	During parsing, <tt>struct Expr</tt> object trees {{src\|ascend/compiler/expr_types.h}} are created, which allow complex mathematical structures to be represented, and also evaluated (<tt>EvaluateExpr</tt>, see {{src\|ascennd/compiler/evaluate.h}})		During parsing, <tt>struct Expr</tt> object trees ({{src\|ascend/compiler/expr_types.h}}) are created, which allow complex mathematical structures to be represented, and also evaluated (<tt>EvaluateExpr</tt> (see {{src\|ascennd/compiler/evaluate.h}})

	However, these structures include references to <tt>struct Name</tt>, which means identifying the instance being referred to still needs to be done, which is expensive. For the solver, faster methods are required. Each relation is converted into a <tt>struct relation</tt> {{src\|ascend/compiler/relation_type.h}}, in which the relevant variables are kept in an ordered list (<tt>struct gl_list *vars</tt>). This allows much faster evaluation.		However, these structures include references to <tt>struct Name</tt>, which means identifying the instance being referred to still needs to be done, which is expensive. For the solver, faster methods are required. Each relation is converted into a <tt>struct relation</tt> {{src\|ascend/compiler/relation_type.h}}, in which the relevant variables are kept in an ordered list (<tt>struct gl_list *vars</tt>). This allows much faster evaluation.

	So-called 'token relations' are the normal approach in ASCEND. Such relations can optionally be compiled to C code (<tt>bintoken</tt>, see above). There are also black box relations (external relations) which are created using a different kind of relation syntax. Finally, there are glass box relations, which were implemented by Kirk Abbott but are not fully operational in current ASCEND versions. (see 'RANT' in {{src\|ascend/compiler/relation.h}}.		So-called 'token relations' are the normal approach in ASCEND. Such relations can optionally be compiled to C code (<tt>bintoken</tt>, see above). There are also black box relations (external relations) which are created using a different kind of relation syntax. Finally, there are glass box relations, which were implemented by Kirk Abbott but are not fully operational in current ASCEND versions. (see 'RANT' in {{src\|ascend/compiler/relation.h}}).

	=== Bintokens ===		=== Bintokens ===

Jpye: /* Compiler */

2018-06-18T02:46:31Z

Compiler

← Older revision		Revision as of 02:46, 18 June 2018
Line 57:		Line 57:

	Note the 'families' of functions around each statement type, eg, 'run', 'do', 'create'.		Note the 'families' of functions around each statement type, eg, 'run', 'do', 'create'.

			During parsing, equations (eg <tt>y = x^2;</tt>) and expressions (eg in <tt>FIX y := x^2;</tt>) are compiled into expressions with the data type <tt>struct Expr *</tt>. These expressions are not the final form used by solvers, and are further adapted later. However because expressions need to be evaluated by [[METHODS]], there is also code for their evaluation. See [[#Expressions and relations]].

	=== Instantiation ===		=== Instantiation ===
Line 94:		Line 96:

	{{incomplete}}		{{incomplete}}

			=== Expressions and relations ===

			During parsing, <tt>struct Expr</tt> object trees {{src\|ascend/compiler/expr_types.h}} are created, which allow complex mathematical structures to be represented, and also evaluated (<tt>EvaluateExpr</tt>, see {{src\|ascennd/compiler/evaluate.h}})

			However, these structures include references to <tt>struct Name</tt>, which means identifying the instance being referred to still needs to be done, which is expensive. For the solver, faster methods are required. Each relation is converted into a <tt>struct relation</tt> {{src\|ascend/compiler/relation_type.h}}, in which the relevant variables are kept in an ordered list (<tt>struct gl_list *vars</tt>). This allows much faster evaluation.

			So-called 'token relations' are the normal approach in ASCEND. Such relations can optionally be compiled to C code (<tt>bintoken</tt>, see above). There are also black box relations (external relations) which are created using a different kind of relation syntax. Finally, there are glass box relations, which were implemented by Kirk Abbott but are not fully operational in current ASCEND versions. (see 'RANT' in {{src\|ascend/compiler/relation.h}}.

	=== Bintokens ===		=== Bintokens ===

Jpye: /* Our development server */

2017-11-02T06:12:04Z

Our development server

← Older revision		Revision as of 06:12, 2 November 2017
Line 476:		Line 476:
	* <s>We have [http://twitter.com/ascend4 a Twitter feed] generated from all code commit messages. Watch that feed if you want to see the recent code changes.</s>		* <s>We have [http://twitter.com/ascend4 a Twitter feed] generated from all code commit messages. Watch that feed if you want to see the recent code changes.</s>
	* <s>If you commit code with a 'bug XXX' (eg 'bug 513') in the commit message, your commit message will automatically be added as a note to that bug in [http://bugs.ascend4.org our bug tracker].</s>		* <s>If you commit code with a 'bug XXX' (eg 'bug 513') in the commit message, your commit message will automatically be added as a note to that bug in [http://bugs.ascend4.org our bug tracker].</s>
	* URLs like http://ascend4.org/r3000 will redirect you to [http://code.ascend4.org our ViewVC subversion repository browser], showing the content of a particular changeset/revision.		* <s>URLs like http://ascend4.org/r3000 will redirect you to [http://code.ascend4.org our ViewVC subversion repository browser], showing the content of a particular changeset/revision.</s>
	* URLs like http://ascend4.org/b500 will redirect you to [http://bugs.ascend4.org our bug tracker], showing you that particular number bug.		* URLs like http://ascend4.org/b500 will redirect you to [http://bugs.ascend4.org our bug tracker], showing you that particular number bug.

Jpye: /* Our development server */

2017-11-02T06:11:51Z

Our development server

← Older revision		Revision as of 06:11, 2 November 2017
Line 476:		Line 476:
	* <s>We have [http://twitter.com/ascend4 a Twitter feed] generated from all code commit messages. Watch that feed if you want to see the recent code changes.</s>		* <s>We have [http://twitter.com/ascend4 a Twitter feed] generated from all code commit messages. Watch that feed if you want to see the recent code changes.</s>
	* <s>If you commit code with a 'bug XXX' (eg 'bug 513') in the commit message, your commit message will automatically be added as a note to that bug in [http://bugs.ascend4.org our bug tracker].</s>		* <s>If you commit code with a 'bug XXX' (eg 'bug 513') in the commit message, your commit message will automatically be added as a note to that bug in [http://bugs.ascend4.org our bug tracker].</s>
	* ~~<s>~~URLs like http://ascend4.org/r3000 will redirect you to [http://code.ascend4.org our ViewVC subversion repository browser], showing the content of a particular changeset/revision.~~</s>~~		* URLs like http://ascend4.org/r3000 will redirect you to [http://code.ascend4.org our ViewVC subversion repository browser], showing the content of a particular changeset/revision.
	* URLs like http://ascend4.org/b500 will redirect you to [http://bugs.ascend4.org our bug tracker], showing you that particular number bug.		* URLs like http://ascend4.org/b500 will redirect you to [http://bugs.ascend4.org our bug tracker], showing you that particular number bug.

Jpye: /* Our development server */

2017-11-02T06:11:19Z

Our development server

← Older revision		Revision as of 06:11, 2 November 2017
Line 473:		Line 473:
	* There are lots of templates that can make writing in our wiki easier. Check out <tt><nowiki>{{src}}</nowiki></tt>, <tt><nowiki>{{bug}}</nowiki></tt> and others. In general, please avoid using explicit URLs to ASCEND pages. See [[Help:Editing]].		* There are lots of templates that can make writing in our wiki easier. Check out <tt><nowiki>{{src}}</nowiki></tt>, <tt><nowiki>{{bug}}</nowiki></tt> and others. In general, please avoid using explicit URLs to ASCEND pages. See [[Help:Editing]].
	* Our [https://build.ascend4.org buildbot] is triggered by any code commits to the repository.		* Our [https://build.ascend4.org buildbot] is triggered by any code commits to the repository.
	* [https:///build.ascend4.org/lcov/ascend-lcov-latest/ ~~coverage~~ testing results] are automatically updated by our Buildbot.		* [https:///build.ascend4.org/lcov/ascend-lcov-latest/ Coverage testing results] are automatically updated by our Buildbot.
	* <s>We have [http://twitter.com/ascend4 a Twitter feed] generated from all code commit messages. Watch that feed if you want to see the recent code changes.</s>		* <s>We have [http://twitter.com/ascend4 a Twitter feed] generated from all code commit messages. Watch that feed if you want to see the recent code changes.</s>
	* <s>If you commit code with a 'bug XXX' (eg 'bug 513') in the commit message, your commit message will automatically be added as a note to that bug in [http://bugs.ascend4.org our bug tracker].</s>		* <s>If you commit code with a 'bug XXX' (eg 'bug 513') in the commit message, your commit message will automatically be added as a note to that bug in [http://bugs.ascend4.org our bug tracker].</s>
	* <s>URLs like http://ascend4.org/r3000 will redirect you to [http://code.ascend4.org our ViewVC subversion repository browser], showing the content of a particular changeset/revision.</s>		* <s>URLs like http://ascend4.org/r3000 will redirect you to [http://code.ascend4.org our ViewVC subversion repository browser], showing the content of a particular changeset/revision.</s>
	* URLs like http://ascend4.org/b500 will redirect you to [http://bugs.ascend4.org our bug tracker], showing you that particular number bug.		* URLs like http://ascend4.org/b500 will redirect you to [http://bugs.ascend4.org our bug tracker], showing you that particular number bug.