User:DanteStroe - Revision history

Jpye at 13:20, 2 August 2010

2010-08-02T13:20:45Z

← Older revision		Revision as of 13:20, 2 August 2010
Line 123:		Line 123:

	[[Category:GSOC2009]]		[[Category:GSOC2009]]
	[[Category:~~ASCEND_Contributors~~]]		[[Category:ASCEND Contributors]]

Jpye: /* By final review: */

2010-05-19T05:59:29Z

By final review:

← Older revision		Revision as of 05:59, 19 May 2010
Line 114:		Line 114:
	** Implement "INDEPENDENT t" type syntax for the independent variable of the derivative chains, with the restriction of having only a single declaration of this type in a model. This implies that the independent variable will no longer have to be declared inside the 'ode'-type LINKs. This would be implemented by using the LINK structure as well.		** Implement "INDEPENDENT t" type syntax for the independent variable of the derivative chains, with the restriction of having only a single declaration of this type in a model. This implies that the independent variable will no longer have to be declared inside the 'ode'-type LINKs. This would be implemented by using the LINK structure as well.
	** Replace the "LINK('ode',dx_dt,x)" type of syntax, with DER(dx_dt,x).(To be agreed if this is smth desirable or LINK is enough for now)		** Replace the "LINK('ode',dx_dt,x)" type of syntax, with DER(dx_dt,x).(To be agreed if this is smth desirable or LINK is enough for now)
	** update: since the latest commit, {{changeset\|~~2750~~}}, the following block of code:		** update: since the latest commit, {{changeset\|2570}}, the following block of code:

	<source lang="a4c">LINK('ode',dx_dt,x,t);</source>		<source lang="a4c">LINK('ode',dx_dt,x,t);</source>

Jpye: /* By final review: */

2010-05-19T05:58:21Z

By final review:

← Older revision		Revision as of 05:58, 19 May 2010
Line 114:		Line 114:
	** Implement "INDEPENDENT t" type syntax for the independent variable of the derivative chains, with the restriction of having only a single declaration of this type in a model. This implies that the independent variable will no longer have to be declared inside the 'ode'-type LINKs. This would be implemented by using the LINK structure as well.		** Implement "INDEPENDENT t" type syntax for the independent variable of the derivative chains, with the restriction of having only a single declaration of this type in a model. This implies that the independent variable will no longer have to be declared inside the 'ode'-type LINKs. This would be implemented by using the LINK structure as well.
	** Replace the "LINK('ode',dx_dt,x)" type of syntax, with DER(dx_dt,x).(To be agreed if this is smth desirable or LINK is enough for now)		** Replace the "LINK('ode',dx_dt,x)" type of syntax, with DER(dx_dt,x).(To be agreed if this is smth desirable or LINK is enough for now)
	** update: since the ~~[http://ascendcode.cheme.cmu.edu/viewvc.cgi?view=rev&revision=2570~~ latest commit] the following block of code:		** update: since the latest commit, {{changeset\|2750}}, the following block of code:

	<source lang="a4c">LINK('ode',dx_dt,x,t);</source>		<source lang="a4c">LINK('ode',dx_dt,x,t);</source>

Jpye: /* By final review: */

2010-05-19T05:57:45Z

By final review:

← Older revision		Revision as of 05:57, 19 May 2010
Line 84:		Line 84:
	** Add functionality to relation classes, to make use of the Link information present for given instances in the case of derivatives. Need		** Add functionality to relation classes, to make use of the Link information present for given instances in the case of derivatives. Need
	** Testing and documentation		** Testing and documentation
	** Modify the DAE solver implementation to make use of the newly implemented "LINK" relationship, however in the form of DERIV(dx_dt,x) . (Note: this implies that "t" is declared as the independent variable in use beforehand, and the compiler should know this until instructed otherwise). This relation would inherit/extend the LINK relationship. See [[Improved DAE syntax]].
	** Add functionality to relation classes, to make use of the Link information present for given instances in the case of derivatives. Need
	** Testing and documentation
	* Modify the DAE solver implementation to make use of the newly implemented "LINK" relationship, however in the form of DERIV(dx_dt,x) . (Note: this implies that "t" is declared as the independent variable in use beforehand, and the compiler should know this until instructed otherwise). This relation would inherit/extend the LINK relationship. See [[Improved DAE syntax]].
	* Add functionality to relation classes, to make use of the Link information present for given instances in the case of derivatives. Need
	* Testing and documentation

	* Update on completed tasks:		* Update on completed tasks:
	** Finished and corrected implementation of testing suite for the LINK syntax (in general) : {{srcbranch\|dante\|models/test/z-link.a4c}}. The file also contains some fail cases and a special LINK type with key 'testSuite' that runs a procedure to test the functions described in [http://ascendwiki.cheme.cmu.edu/LINK_semantics LINK]		** Finished and corrected implementation of testing suite for the LINK syntax (in general) : {{srcbranch\|dante\|models/test/z-link.a4c}}. The file also contains some fail cases and a special LINK type with key 'testSuite' that runs a procedure to test the functions described in [http://ascendwiki.cheme.cmu.edu/LINK_semantics LINK]
	** Created 'ode' type LINKS that are defined by the 'ode' key and a list of instances out of which, currently, the last one is the independent variable, whereas the rest are the differential variable in decreasing order. Ex:		** Created 'ode' type LINKS that are defined by the 'ode' key and a list of instances out of which, currently, the last one is the independent variable, whereas the rest are the differential variable in decreasing order. Ex:
	** Finished and corrected implementation of testing suite for the LINK syntax (in general) ;: {{srcbranch\|dante\|models/test/z-link.a4c}}. The file also contains some fail cases and a special LINK type with key 'testSuite' that runs a procedure to test the functions described in [http://ascendwiki.cheme.cmu.edu/LINK_semantics LINK]
	** Created 'ode' type LINKS that are defined by the 'ode' key and a list of instances out of which, currently, the last one is the independent variable, whereas the rest are the differential variable in decreasing order. Ex:
	* Finished and corrected implementation of testing suite for the LINK syntax (in general) : {{srcbranch\|dante\|models/test/z-link.a4c}}. The file also contains some fail cases and a special LINK type with key 'testSuite' that runs a procedure to test the functions described in [http://ascendwiki.cheme.cmu.edu/LINK_semantics LINK]
	* Created 'ode' type LINKS that are defined by the 'ode' key and a list of instances out of which, currently, the last one is the independent variable, whereas the rest are the differential variable in decreasing order. Ex:
	<source lang="a4c">LINK('ode',dx_dt,x,t);</source>		<source lang="a4c">LINK('ode',dx_dt,x,t);</source>

Line 132:		Line 122:
	* either of the two new statements can be declared in any order and in any part of the model as with LINK; The example models have also been updated with the new syntax.		* either of the two new statements can be declared in any order and in any part of the model as with LINK; The example models have also been updated with the new syntax.

			[[Category:GSOC2009]]

	[[Category:GSOC2009]]
	[[Category:ASCEND_Contributors]]		[[Category:ASCEND_Contributors]]

Jpye: /* Detailed plan */

2010-05-19T05:56:58Z

Detailed plan

Show changes

Jpye: /* By mid-term review: */

2010-05-19T05:53:48Z

By mid-term review:

← Older revision		Revision as of 05:53, 19 May 2010
Line 33:		Line 33:

	}</source>		}</source>

	* This is defined as part of the TypeDescription class. where the "link_table" is declared as an attribute as part of the ModelArgs union element of the TypeDescription:<source lang="a4c">struct ModelArgs {		* This is defined as part of the TypeDescription class. where the "link_table" is declared as an attribute as part of the ModelArgs union element of the TypeDescription:<source lang="a4c">struct ModelArgs {
	struct gl_list_t link_table; /< pointer to the table of "LINK" relationships of the model/		struct gl_list_t link_table; /< pointer to the table of "LINK" relationships of the model/

Jpye: /* Detailed plan */

2010-05-19T05:53:23Z

Detailed plan

← Older revision		Revision as of 05:53, 19 May 2010
Line 37:		Line 37:

	....</source>		....</source>

	===Instantiation and LINK statements===		===Instantiation and LINK statements===
	* Additions to the "instantiate" class can be followed at [http://ascendcode.cheme.cmu.edu/viewvc.cgi/code/branches/dante/ascend/compiler/instantiate.c?sortby=date&r1=2394&r2=2296&pathrev=2394 this rev diff]		* Additions to the "instantiate" class can be followed at [http://ascendcode.cheme.cmu.edu/viewvc.cgi/code/branches/dante/ascend/compiler/instantiate.c?sortby=date&r1=2394&r2=2296&pathrev=2394 this rev diff]

Jpye: /* Instantiation and LINK statements */

2010-05-19T05:52:49Z

Instantiation and LINK statements

Jpye: /* Instantiation and LINK statements */

2010-05-19T05:52:21Z

Instantiation and LINK statements

@@ Line 47: / Line 47: @@
 *** 5. LINK Statements (instantiate LINKS and disregard any other type of statements) - Added
 *** 6. default (visit instance tree once more and if it is the case warn about any un-executed statements).
-*** 1. Models (instantiate models and disregard any other type of statements)
 For the purpose of adding this new "LINK" phase in the instantiation procedure the following functions were added. They were implemented and documented in a similar fashion (if the case) with respect to the other instantiation functions:
 * These functions set the bits such that the following functions only execute the LINK statements, as well as the FORs and select(re-evaluate) statements that contain LINKs.
@@ Line 106: / Line 55: @@
 <br />
-* By now the  pass5pendings was already set by silent visit to the instance tree. (which means we updated the pending instances from the last phase)
+* By now the pass5pendings was already set by silent visit to the instance tree. (which means we updated the pending instances from the last phase)
 <source lang="a4c">void Pass5ProcessPendingInstances(void)</source>
 <br />
@@ Line 126: / Line 75: @@
 ** At this point ascend should be able compile models with "LINK" syntax and store it
 ** Regression testing and making sure committed code is properly documented
 ===By final review:===

Jpye at 05:51, 19 May 2010

2010-05-19T05:51:08Z

← Older revision		Revision as of 05:51, 19 May 2010
Line 24:		Line 24:

	} u;		} u;
	struct gl_list_t instances_cache; /~~<~~ (cache) pointer to the list of instances that are linked/		struct gl_list_t instances_cache; /< (cache) pointer to the list of instances that are linked/

	symchar* key_cache; /*~~<~~ key that defines the linked instances /		symchar* key_cache; /*< key that defines the linked instances /
	unsigned long length; /*~~<~~ Number of instances in the linked_instances list. /		unsigned long length; /*< Number of instances in the linked_instances list. /

	unsigned long capacity; /*~~<~~ Capacity of the link entry, in terms of the number of the instances that can be linked. /		unsigned long capacity; /*< Capacity of the link entry, in terms of the number of the instances that can be linked. /
	unsigned int flags; /*~~<~~ Status flags.used to differentiate between LINK statements in the declarative part(FIXED) and the ones in the methods (not fied). /		unsigned int flags; /*< Status flags.used to differentiate between LINK statements in the declarative part(FIXED) and the ones in the methods (not fied). /

	}</source>		}</source>
	* This is defined as part of the TypeDescription class. where the "link_table" is declared as an attribute as part of the ModelArgs union element of the TypeDescription:<source lang="a4c">struct ModelArgs {		* This is defined as part of the TypeDescription class. where the "link_table" is declared as an attribute as part of the ModelArgs union element of the TypeDescription:<source lang="a4c">struct ModelArgs {
	struct gl_list_t link_table; /~~<~~ pointer to the table of "LINK" relationships of the model/		struct gl_list_t link_table; /< pointer to the table of "LINK" relationships of the model/

	....</source>		....</source>

← Older revision		Revision as of 05:52, 19 May 2010
Line 53:		Line 53:
	<source lang="a4c">void Pass5SetLinkBits(struct Instance *inst)</source>		<source lang="a4c">void Pass5SetLinkBits(struct Instance *inst)</source>
	<source lang="a4c">struct Instance Pass5InstantiateModel(struct Instance result, unsigned long *pcount)</source>		<source lang="a4c">struct Instance Pass5InstantiateModel(struct Instance result, unsigned long *pcount)</source>
	~~<br />~~

	* By now the pass5pendings was already set by silent visit to the instance tree. (which means we updated the pending instances from the last phase)		* By now the pass5pendings was already set by silent visit to the instance tree. (which means we updated the pending instances from the last phase)
	<source lang="a4c">void Pass5ProcessPendingInstances(void)</source>		<source lang="a4c">void Pass5ProcessPendingInstances(void)</source>
	~~<br />~~

	* Try to execute all the LINK statements in instance work. It assumes that work is the top of the pending instance list. Will skip all non-LINK statements. (Note: Only models get here)		* Try to execute all the LINK statements in instance work. It assumes that work is the top of the pending instance list. Will skip all non-LINK statements. (Note: Only models get here)
	<source lang="a4c">static void Pass5ExecuteLinkStatements(struct BitList blist, struct Instance work, int *changed)</source>		<source lang="a4c">static void Pass5ExecuteLinkStatements(struct BitList blist, struct Instance work, int *changed)</source>
	~~<br />~~

	* Statement processing. We are processing just the LINK statements that are stand-alone as well as the ones inside FORs (That's what we should be left with anyway, since this is the last phase of instantiation). This Executes each LINK with "ExecuteLNK(instance,statement)" function and each FOR that contains a LINK with "Pass5ExecuteFOR(instance,statement)" (this only executes the LINKs inside the FOR)		* Statement processing. We are processing just the LINK statements that are stand-alone as well as the ones inside FORs (That's what we should be left with anyway, since this is the last phase of instantiation). This Executes each LINK with "ExecuteLNK(instance,statement)" function and each FOR that contains a LINK with "Pass5ExecuteFOR(instance,statement)" (this only executes the LINKs inside the FOR)
	<source lang="a4c">static int Pass5ExecuteStatement(struct Instance inst,struct Statement statement)</source>		<source lang="a4c">static int Pass5ExecuteStatement(struct Instance inst,struct Statement statement)</source>
	~~<br />~~

	* This is where all the sanity checks are done for the LINK statement and parameters correctness aw well as the addLinkEntry function is called for the given model.		* This is where all the sanity checks are done for the LINK statement and parameters correctness aw well as the addLinkEntry function is called for the given model.
	<source lang="a4c">int ExecuteLNK(struct Instance inst, struct Statement statement)</source>		<source lang="a4c">int ExecuteLNK(struct Instance inst, struct Statement statement)</source>