User:Aakash - Revision history

Aakash: /* Summary of work done */

2011-08-20T02:23:56Z

Summary of work done

← Older revision		Revision as of 02:23, 20 August 2011
Line 33:		Line 33:
	* Improved the units of measurement checking in the "Variable Properties" dialog.		* Improved the units of measurement checking in the "Variable Properties" dialog.

	* Fixed some bugs- {{bug\|473}}, {{bug\|\|360}}, {{bug\|515}}, {{bug\|510}}, {{bug\|514}}.		* Fixed some bugs- {{bug\|473}}, {{bug\|360}}, {{bug\|515}}, {{bug\|510}}, {{bug\|514}}, {{bug\|331}}.

	== More that can be done ==		== More that can be done ==

Aakash at 16:35, 19 August 2011

2011-08-19T16:35:25Z

← Older revision		Revision as of 16:35, 19 August 2011
Line 14:		Line 14:
	== Summary of work done ==		== Summary of work done ==

	* Ported the PyGTK GUI from libglade to GTK Builder ({{bug\|493}}		* Ported the PyGTK GUI from libglade to GTK Builder ({{bug\|493}})
	* Improvements to the observer functionality:		* Improvements to the observer functionality:
	*# Added the ability to delete an observer tab.		*# Added the ability to delete an observer tab.
Line 22:		Line 22:
	*# Regarding plotting, the user can now select which columns to plot and whether to leave out points where the solver failed.		*# Regarding plotting, the user can now select which columns to plot and whether to leave out points where the solver failed.

	* Implemented 1D Study ({{bug\|294}} in PyGTK with the following features:		* Implemented 1D Study ({{bug\|294}}) in PyGTK with the following features:
	*# Intuitive units of measurement checking.		*# Intuitive units of measurement checking.
	*# Option of Logarithmic and Linear step distribution		*# Option of Logarithmic and Linear step distribution
Line 37:		Line 37:
	== More that can be done ==		== More that can be done ==

	Every few days, John and I would have a discussion regarding the work I had done and what more I could do. During those, a ~~lot~~ of things were suggested, and I worked on ~~most~~ of them. However, the ~~following~~ are ~~some which~~ still ~~remain untouched by me~~:		Every few days, John and I would have a discussion regarding the work I had done and what more I could do. During those, a number of things were suggested, and I worked on many of them. However for a project like ASCEND, the possibilities are unlimited, and there is a lot that can still be done:

	* In the "Observer Tab",		* In the "Observer Tab",

Aakash at 16:32, 19 August 2011

2011-08-19T16:32:37Z

@@ Line 11: / Line 11: @@
 * Add whatever more that the GTK library has to offer.
 * Check for and fix bugs in my code.
 == Progress reports ==

Aakash: /* Progress reports */

2011-08-19T14:35:45Z

Progress reports

← Older revision		Revision as of 14:35, 19 August 2011
Line 18:		Line 18:
	The work done in the last few days :		The work done in the last few days :

	* Implemented Automatic Weekly Update checking ~~and fixed a~~ .		* Implemented Automatic Weekly Update checking.
	* Implemented better units of measurement checking in the "Variable Properties" dialog box.		* Implemented better units of measurement checking in the "Variable Properties" dialog box.
	** [[File:PyGTK Study - 19.png]]		** [[File:PyGTK Study - 19.png]]
	* Fixed bug 518		* Fixed {{bug\|518}}
	* Fixed bug 473		* Fixed {{bug\|473}}
	* Found some plotting related bugs in my code and fixed them.		* Found some plotting related bugs in my code and fixed them.
	* Tested out the updated trunk on Ubuntu and Windows 7 to ensure that everything was working alright.		* Tested out the updated trunk on Ubuntu and Windows 7 to ensure that everything was working alright.

Aakash at 14:33, 19 August 2011

2011-08-19T14:33:35Z

← Older revision		Revision as of 14:33, 19 August 2011
Line 13:		Line 13:

	== Progress reports ==		== Progress reports ==

			'''19 Aug 2011'''

			The work done in the last few days :

			* Implemented Automatic Weekly Update checking and fixed a .
			* Implemented better units of measurement checking in the "Variable Properties" dialog box.
			** [[File:PyGTK Study - 19.png]]
			* Fixed bug 518
			* Fixed bug 473
			* Found some plotting related bugs in my code and fixed them.
			* Tested out the updated trunk on Ubuntu and Windows 7 to ensure that everything was working alright.

	'''7 Aug 2011'''		'''7 Aug 2011'''

Aakash: /* Progress reports */

2011-08-07T15:21:37Z

Progress reports

← Older revision		Revision as of 15:21, 7 August 2011
Line 41:		Line 41:
	* Add the ability to select line type using matplotlib specifiers like "r-", "b." etc.		* Add the ability to select line type using matplotlib specifiers like "r-", "b." etc.

	''''More that could be done''''		'''More that could be done'''

	The following are suggestions given by John, regarding what more can be done to improve the GUI further.		The following are suggestions given by John, regarding what more can be done to improve the GUI further.

Aakash: /* Progress reports */

2011-08-07T15:17:19Z

Progress reports

← Older revision		Revision as of 15:17, 7 August 2011
Line 13:		Line 13:

	== Progress reports ==		== Progress reports ==

			'''7 Aug 2011'''

			The progress made this week is as follows-

			'''Done'''

			* In the Observer tab,

			*# Multiple rows can now be selected and deleted.
			# [[File:PyGTK Study - 18.png]]
			*# A column can now be preselected as a y-variable (for plotting) by right clicking on it and selecting plot.
			*# Plotting and copy to clipboard were not working properly if used after deleting any column or for columns which had been added to the observer tab late, ie., after addition of some rows. Fixed all of those problems.

			* Did a merge from the current trunk, to make sure that everything was working properly.

			* Updated the URLs in "Report a bug" and the "About" dialog.

			'''To Do'''

			* Implement sorting of columns in the Observer. It would help in making plots work properly.

			* Automatic checking for updates.

			* Extend the plotting interface for (optionally) dual plots, example - http://matplotlib.sourceforge.net/examples/api/two_scales.html#api-two-scales

			* Add the ability to select line type using matplotlib specifiers like "r-", "b." etc.

			''''More that could be done''''

			The following are suggestions given by John, regarding what more can be done to improve the GUI further.

			* Think about ways that we can use NOTES for effective documentation of models as seen in the GUI.

			* In the "incidence matrix" window, we could add coloring of diverged/converged blocks, and light-grey background shading to identify the blocks. This would make it much easier to see where things were going wrong.

			* In the "diagnose" window, we should get rid of (or else improve) the current fairly cryptic colour-scheme for points, and try to improve usability. This window aims to provide similar functionality to the "incidence matrix" window, but with more detail allowing more debugging and investigation to happen.

			*# Values of variables should be shown with the preferred units, if possible, but perhaps when hovering over the value it should show the scaled value as used by the solver.
			*# It should be easy to find which equations are diverging, which variables have gone to their limits or have gone to crazy big values, and the shortest possible name for variables should be used, rather than the first one that ASCEND manages to locate (variables have ALIASES and ARE_THE_SAME relationships which means that there is often a number of different ways of referring to a single solver variable).

	'''30 July 2011'''		'''30 July 2011'''

Jpye at 05:05, 6 August 2011

2011-08-06T05:05:44Z

← Older revision		Revision as of 05:05, 6 August 2011
Line 260:		Line 260:

	[[Category:GSOC2011]]		[[Category:GSOC2011]]
			[[Category:ASCEND Contributors]]

Aakash: /* Progress reports */

2011-07-30T18:10:17Z

Progress reports

← Older revision		Revision as of 18:10, 30 July 2011
Line 23:		Line 23:
	*# Fixed a problem which was happening when you deleted a column, and then added a new column or row.		*# Fixed a problem which was happening when you deleted a column, and then added a new column or row.
	*# Fixed problems regarding the observer tab when different model is loaded, without reloading the file. Also added a dialog to warn the user -- if there are any active Observers -- that they will become inactive after reload.		*# Fixed problems regarding the observer tab when different model is loaded, without reloading the file. Also added a dialog to warn the user -- if there are any active Observers -- that they will become inactive after reload.

	# [[File:PyGTK Study - 14.png]]		# [[File:PyGTK Study - 14.png]]

	*# It is now possible select units of measurement in the Observer tab.		*# It is now possible select units of measurement in the Observer tab.

	# [[File:PyGTK Study - 15.png]]		# [[File:PyGTK Study - 15.png]]

	*# When an observer is inactive (not connected to the simulation, eg after a 'reload') the active row will turn black, have its arrow removed etc.		*# When an observer is inactive (not connected to the simulation, eg after a 'reload') the active row will turn black, have its arrow removed etc.
	*# Implemented tooltips which display solver errors for rows in the Observer's tab		*# Implemented tooltips which display solver errors for rows in the Observer's tab

	# [[File:PyGTK Study - 16.png]]		# [[File:PyGTK Study - 16.png]]

	* Plot button,		* Plot button,
	*# Implemented the following interface to select the columns to be plotted.		*# Implemented the following interface to select the columns to be plotted.

	# [[File:PyGTK Study - 17.png]]		# [[File:PyGTK Study - 17.png]]

	*# As you can see, the user will also be able to leave out points where a solver error occurred.		*# As you can see, the user will also be able to leave out points where a solver error occurred.

Aakash: /* Progress reports */

2011-07-30T18:08:51Z

Progress reports

← Older revision		Revision as of 18:08, 30 July 2011
Line 14:		Line 14:
	== Progress reports ==		== Progress reports ==

	'''24 July 2011'''		'''30 July 2011'''

	~~As per~~ discussions held with John during the last . -		On the basis of discussions held with John during the last week, I have made some progress. The detailed report is as follows-

	'''Done'''		'''Done'''
Line 23:		Line 23:
	*# Fixed a problem which was happening when you deleted a column, and then added a new column or row.		*# Fixed a problem which was happening when you deleted a column, and then added a new column or row.
	*# Fixed problems regarding the observer tab when different model is loaded, without reloading the file. Also added a dialog to warn the user -- if there are any active Observers -- that they will become inactive after reload.		*# Fixed problems regarding the observer tab when different model is loaded, without reloading the file. Also added a dialog to warn the user -- if there are any active Observers -- that they will become inactive after reload.

	# [[File:PyGTK Study - 14.png]]		# [[File:PyGTK Study - 14.png]]

	*# It is now possible select units of measurement in the Observer tab.		*# It is now possible select units of measurement in the Observer tab.

	# [[File:PyGTK Study - 15.png]]		# [[File:PyGTK Study - 15.png]]

	*# When an observer is inactive (not connected to the simulation, eg after a 'reload') the active row will turn black, have its arrow removed etc.		*# When an observer is inactive (not connected to the simulation, eg after a 'reload') the active row will turn black, have its arrow removed etc.
	*# Implemented tooltips which display solver errors for rows in the Observer's tab		*# Implemented tooltips which display solver errors for rows in the Observer's tab

	# [[File:PyGTK Study - 16.png]]		# [[File:PyGTK Study - 16.png]]

	* Plot button,		* Plot button,
	*# Implemented the following interface to select the columns to be plotted.		*# Implemented the following interface to select the columns to be plotted.

	# [[File:PyGTK Study - 17.png]]		# [[File:PyGTK Study - 17.png]]

	*# As you can see, the user will also be able to leave out points where a solver error occurred.		*# As you can see, the user will also be able to leave out points where a solver error occurred.