Lunarpedia talk:Autostub1 test 1 - Revision history

Strangelv: /* Source Code */ upgraded to what should be the most recent version

2007-07-10T15:46:18Z

Source Code: upgraded to what should be the most recent version

Show changes

Strangelv: Moved Software Development Plan to autostub1 talk page

2007-01-17T14:47:17Z

Moved Software Development Plan to autostub1 talk page

Strangelv: /* Software Development Plan */

2007-01-17T14:21:40Z

Software Development Plan

Cfrjlr: /* Software Development Plan */ what do you mean by "five or so different areas " ?

2007-01-17T13:02:18Z

Software Development Plan: what do you mean by "five or so different areas " ?

Strangelv: /* Software Development Plan */

2007-01-17T09:41:14Z

Software Development Plan

Cfrjlr: Are we ready to incorporate the equations for sector area into the script?

2007-01-17T04:02:20Z

Are we ready to incorporate the equations for sector area into the script?

Cfrjlr: need detailed requirements

2007-01-17T03:41:01Z

need detailed requirements

Strangelv: Perhaps disappointing answers to questions

2007-01-17T02:38:38Z

Perhaps disappointing answers to questions

Cfrjlr: /* To Do */ questions about ToDo items

2007-01-17T01:53:38Z

To Do: questions about ToDo items

Cfrjlr: /* Bonus Points */ Apollo coordinates

2007-01-17T01:50:22Z

Bonus Points: Apollo coordinates

← Older revision		Revision as of 14:47, 17 January 2007
Line 53:		Line 53:

	==Software Development Plan==		==Software Development Plan==
		+	Moved to [[Lunarpedia_talk:Autostub1#Software_Development_Plan]]

−	Thanks for the responses to my various questions. Essentially what I would like to see here is a detailed requirements specification and/or a detailed design document. that will address your valid concerns that "we need to get it right first time"...
−
−	In my experience, the most common and most devastating problem encountered by software development projects is.... screwed up requirements, ie requirements which are vague, ambiguous, confusing, misleading, impossible, contradictory, meaningless, non-sensical, and/or incomplete, or just plain wrong. So that is why I am asking lots of questions to make sure the requirements are crystal clear, and we know exactly what we are trying to achieve before we go zooming up the wrong road.
−
−	~~Thanks.~~
−
−
−	~~[[User:Cfrjlr\|Charles F. Radley]] 19:41, 16 January 2007 (PST)~~
−
−	:Thank you for pointing out this blazingly obvious point that mysteriously never occurred to me. In my defense, I've been working on an iterative development concept (at least until I got detoured) that is compatible with cranking out something now and getting a clue later (even if it means scrapping or shelving a lot of code in the process).
−
−	~~:How confusing is my internal documentation? A historical complaint is that my commenting has often been less than fully helpful.~~
−
−	~~:This probably requires its own page, as we're moving beyond the first test. How about [[Lunarpedia:Autostub1]] (...which already exists -- I forgot all about it)?~~
−
−	~~:-- [[User:Strangelv\|Strangelv]] 01:41, 17 January 2007 (PST)~~
−
−
−	~~Sector areas code:Set up variables to generate article stub~~
−	~~Are we ready to incorporate the equations for sector area into the script?~~
−	~~[[User:Cfrjlr\|Charles F. Radley]]~~
−
−	:Sector Areas could be precomputed and referenced by latitude, as there's basically only five or so different areas unless we want to get really serious and go by actual complex geometry instead of treating it as a sphere (or for partial bonus credit, a slightly flattened sphere) (for example, I've been told that Earth is slightly pear shaped).
−
−	:Presumably the computation or selection of area could be added to 'Set up variables to generate article stub' and then added to the template graphics below that before '''to_out''' is run through '''tidypipes()''', as required by '''{<B></B>{Circular Feature}<B></B>}'''.
−
−	~~:--[[User:Strangelv\|Strangelv]] 01:41, 17 January 2007 (PST)~~
−
−	~~::James, what do you mean by "five or so different areas " ? Do you mean there are only 5 sectors?~~
−
−	::The solution I posted assumes the Moon is a perfect sphere, for our purposes there is no reason to use more ellaborate models. I believe the equations I provided are adequate. We are not trying to perform a pinpoint landing of a spacecraft, nor make topographic measurements, we are only giving the users some visual experience.
−
−	~~::Please provide the lattitude/longitude boundaries of each sector and I will calculate the area by hand. Where do you want me to put the results?~~
−
−	~~::[[User:Cfrjlr\|Charles F. Radley]] 05:02, 17 January 2007 (PST)~~
−
−	:::24 sectors along the equator have the same area; 2 polar sectors have the same area; all other sectors share the same area with 47 other sectors. Sorry if 'area' is a confusing term to use here. -- [[User:Strangelv\|Strangelv]] 06:21, 17 January 2007 (PST)
−
−	~~==Software Requirements Specification==~~
−
−	~~==Software Design Specification==~~
−
−	~~==Software Test Plan==~~

	==Source Code==		==Source Code==

@@ Line 82: / Line 82: @@
 :--[[User:Strangelv|Strangelv]] 01:41, 17 January 2007 (PST)
-James, what do you mean by "five or so different areas " ?  Do you mean there are only 5 sectors?
+::James, what do you mean by "five or so different areas " ?  Do you mean there are only 5 sectors?
-The solution I posted assumes the Moon is a perfect sphere, for our purposes there is no reason to use more ellaborate models.  I believe the equations I provided are adequate.  We are not trying to perform a pinpoint landing of a spacecraft, nor make topographic measurements, we are only giving the users some visual experience.
+::The solution I posted assumes the Moon is a perfect sphere, for our purposes there is no reason to use more ellaborate models.  I believe the equations I provided are adequate.  We are not trying to perform a pinpoint landing of a spacecraft, nor make topographic measurements, we are only giving the users some visual experience.
-Please provide the lattitude/longitude boundaries of each sector and I will calculate the area by hand.  Where do you want me to put the results?
+::Please provide the lattitude/longitude boundaries of each sector and I will calculate the area by hand.  Where do you want me to put the results?
-[[User:Cfrjlr|Charles F. Radley]] 05:02, 17 January 2007 (PST)
+::[[User:Cfrjlr|Charles F. Radley]] 05:02, 17 January 2007 (PST)
 ==Software Requirements Specification==

← Older revision		Revision as of 13:02, 17 January 2007
Line 81:		Line 81:

	:--[[User:Strangelv\|Strangelv]] 01:41, 17 January 2007 (PST)		:--[[User:Strangelv\|Strangelv]] 01:41, 17 January 2007 (PST)
		+
		+	James, what do you mean by "five or so different areas " ? Do you mean there are only 5 sectors?
		+
		+	The solution I posted assumes the Moon is a perfect sphere, for our purposes there is no reason to use more ellaborate models. I believe the equations I provided are adequate. We are not trying to perform a pinpoint landing of a spacecraft, nor make topographic measurements, we are only giving the users some visual experience.
		+
		+	Please provide the lattitude/longitude boundaries of each sector and I will calculate the area by hand. Where do you want me to put the results?
		+
		+	[[User:Cfrjlr\|Charles F. Radley]] 05:02, 17 January 2007 (PST)
		+
		+
		+	==Software Requirements Specification==
		+
		+	==Software Design Specification==
		+
		+	==Software Test Plan==

	==Source Code==		==Source Code==

@@ Line 59: / Line 59: @@
 Thanks.
 [[User:Cfrjlr|Charles F. Radley]] 19:41, 16 January 2007 (PST)
-Sector areas code:
+:Thank you for pointing out this blazingly obvious point that mysteriously never occurred to me.  In my defense, I've been working on an iterative development concept (at least until I got detoured) that is compatible with cranking out something now and getting a clue later (even if it means scrapping or shelving a lot of code in the process).
 Are we ready to incorporate the equations for sector area into the script?
 [[User:Cfrjlr|Charles F. Radley]]
 ==Source Code==

@@ Line 51: / Line 51: @@
 : Sounds great if it can be found.  I've only seen one database though, and it treats everything as circles whether perfectly appropriate or wildly inappropriate. Manually changing them ourselves at this stage isn't feasible given the sheer number of features in the database. -- [[User:Strangelv|Strangelv]] 18:38, 16 January 2007 (PST)
 Thanks for the responses to my various questions.  Essentially what I would like to see here is a detailed requirements specification and/or a detailed design document.  that will address your valid concerns that "we need to get it right first time"...
@@ Line 59: / Line 61: @@
 [[User:Cfrjlr|Charles F. Radley]] 19:41, 16 January 2007 (PST)

← Older revision		Revision as of 03:41, 17 January 2007
Line 51:		Line 51:

	: Sounds great if it can be found. I've only seen one database though, and it treats everything as circles whether perfectly appropriate or wildly inappropriate. Manually changing them ourselves at this stage isn't feasible given the sheer number of features in the database. -- [[User:Strangelv\|Strangelv]] 18:38, 16 January 2007 (PST)		: Sounds great if it can be found. I've only seen one database though, and it treats everything as circles whether perfectly appropriate or wildly inappropriate. Manually changing them ourselves at this stage isn't feasible given the sheer number of features in the database. -- [[User:Strangelv\|Strangelv]] 18:38, 16 January 2007 (PST)
		+
		+	Thanks for the responses to my various questions. Essentially what I would like to see here is a detailed requirements specification and/or a detailed design document. that will address your valid concerns that "we need to get it right first time"...
		+
		+	In my experience, the most common and most devastating problem encountered by software development projects is.... screwed up requirements, ie requirements which are vague, ambiguous, confusing, misleading, impossible, contradictory, meaningless, non-sensical, and/or incomplete, or just plain wrong. So that is why I am asking lots of questions to make sure the requirements are crystal clear, and we know exactly what we are trying to achieve before we go zooming up the wrong road.
		+
		+	Thanks.
		+
		+	[[User:Cfrjlr\|Charles F. Radley]] 19:41, 16 January 2007 (PST)

@@ Line 22: / Line 22: @@
 * Match sectors and features (not just centers) -- easy to solve, will do on a weekend or snow day [[User:Cfrjlr|Charles F. Radley]] 17:53, 16 January 2007 (PST)
 * Match satellite craters with their central craters - Where is the list of satellite craters? [[User:Cfrjlr|Charles F. Radley]] 17:53, 16 January 2007 (PST)
 * Border case handling for when feature center is on the boundary of two or four sectors -  What do you want it to do in those cases ? [[User:Cfrjlr|Charles F. Radley]] 17:53, 16 January 2007 (PST)
 * Automatically load and parse tab delimited CSV --- Is this done now ?  [[User:Cfrjlr|Charles F. Radley]] 17:53, 16 January 2007 (PST)
 * Automatically output articles in XML for bulk import
 * Automatically generate map files for suitably large features
@@ Line 38: / Line 41: @@
 The precise coordinates of the Apollo sites are available on the web link provided on that page.
 [[User:Cfrjlr|Charles F. Radley]] 17:50, 16 January 2007 (PST)
 * Is there a public domain database that represents non-circular features in a non-circular manner?
@@ Line 45: / Line 49: @@
 How about approximating them to ellipses?  Standard geometry equations.
 [[User:Cfrjlr|Charles F. Radley]] 17:49, 16 January 2007 (PST)
 ==Source Code==
 Warning: this was getting mauled in a few places.  I've tinkered with the formatting to make it work.
-And yes, the code is really rough in a few places (like where reinventing the wheel is faster than rembering where the wheel is).  The language is Python.  2.4 and later should work; earlier may require replacing my '//' division with integer coersion.
+And yes, the code is really rough in a few places (like where reinventing the wheel is faster than remembering where the wheel is).  The language is Python.  2.4 and later should work; earlier may require replacing my '//' division with integer coercion.
    #%#%#%#%#%#%#%#%#%#%#%#%#%#%#%#

← Older revision		Revision as of 01:50, 17 January 2007
Line 37:		Line 37:
	-- [[User:Strangelv\|Strangelv]] 18:13, 4 November 2006 (PST)		-- [[User:Strangelv\|Strangelv]] 18:13, 4 November 2006 (PST)

		+	The precise coordinates of the Apollo sites are available on the web link provided on that page.
		+	[[User:Cfrjlr\|Charles F. Radley]] 17:50, 16 January 2007 (PST)

	* Is there a public domain database that represents non-circular features in a non-circular manner?		* Is there a public domain database that represents non-circular features in a non-circular manner?