Soldier Name Stats - Revision history

Winterheart at 20:52, 8 May 2013

2013-05-08T20:52:02Z

← Older revision		Revision as of 20:52, 8 May 2013
Line 56:		Line 56:
	*[[Soldiers]]		*[[Soldiers]]
	*[[Hiring/firing]]		*[[Hiring/firing]]

			[[Category:Enemy Unknown/UFO Defense]]

MikeTheRed: Rewrote soldier name page - see the Talk page

2012-09-02T19:21:15Z

Rewrote soldier name page - see the Talk page

Show changes

MikeTheRed: /* Duplicates */ Right, ok ... this page should be edited to take out most of the info on duplicates. Thanks, you two!

2012-08-06T16:22:31Z

Duplicates: Right, ok ... this page should be edited to take out most of the info on duplicates. Thanks, you two!

← Older revision		Revision as of 16:22, 6 August 2012
Line 174:		Line 174:
	While playing a fairly average game (less than 100 soldiers ever generated so far), I manually put stat strings on my soldiers' names. I currently have two Yoko Fujimotos with various stat strings. Considering that duplicate names aren't seen within a single game while testing names, but that I did see a second Yoko Fujimoto get generated after I changed the name of my original to Yoko Fujimoto-xs, I'm going to go ahead and say "The game probably just avoids duplicates by comparing the name it generates to each existing soldier's name". I predict that if you hire a female Russian soldier, and change her name to "Austin Bradley", you will never see another soldier generated with the name "Austin Bradley" but you might see a new soldier with her original name. This would be very tedious to test. --[[User:Sowelu\|Sowelu]] 14:15, 16 September 2008 (PDT)		While playing a fairly average game (less than 100 soldiers ever generated so far), I manually put stat strings on my soldiers' names. I currently have two Yoko Fujimotos with various stat strings. Considering that duplicate names aren't seen within a single game while testing names, but that I did see a second Yoko Fujimoto get generated after I changed the name of my original to Yoko Fujimoto-xs, I'm going to go ahead and say "The game probably just avoids duplicates by comparing the name it generates to each existing soldier's name". I predict that if you hire a female Russian soldier, and change her name to "Austin Bradley", you will never see another soldier generated with the name "Austin Bradley" but you might see a new soldier with her original name. This would be very tedious to test. --[[User:Sowelu\|Sowelu]] 14:15, 16 September 2008 (PDT)
	:Check no further, I had a look at the code and indeed it checks against every entry in [[SOLDIER.DAT]] and will regenerate a new name in case of collision (up to ten times, after that it'll give up and use the duplicate one). There is no check to see if the entry is valid so it should also remember dead soldiers as long as their entries are not overwritten. [[User:Seb76\|Seb76]] 15:22, 16 September 2008 (PDT)		:Check no further, I had a look at the code and indeed it checks against every entry in [[SOLDIER.DAT]] and will regenerate a new name in case of collision (up to ten times, after that it'll give up and use the duplicate one). There is no check to see if the entry is valid so it should also remember dead soldiers as long as their entries are not overwritten. [[User:Seb76\|Seb76]] 15:22, 16 September 2008 (PDT)
			When I made the test batches (above), they all came from the exact same savegame, and then got appended into a database. Which is to say, the fact that I saw duplicates does not conflict with what you two are saying. (X-COM only compared each test batch of 100 against the 150 soldiers existing in that particular savegame, not against the other test batches that I had generated from it.) Now that we know the code, we know my approach was improper for detecting duplicates. I should edit the above to take out mentions of duplicates. Or more precisely, just say what you said, Seb.

			With X-COM checking 10 times, duplicates will be infinitesimally rare. The best chance is if you have a lot of soldiers (250 max); 250/2400 is a 10.42% chance, but raised to the 10th power this becomes 1.5x10<sup>-10</sup> (1 in 7x10<sup>9</sup> times). If, like most folks, you have less than 250 soldiers, duplicates will be even rarer. With the 8 starting soldiers, it only happens 1 in 6x10<sup>24</sup> times. To make a long story short, duplicates are practically impossible.

			-[[User:MikeTheRed\|MikeTheRed]] 12:22, 6 August 2012 (EDT)

	==See Also==		==See Also==

Seb76: /* Duplicates */

2008-09-16T22:22:44Z

Duplicates

← Older revision		Revision as of 22:22, 16 September 2008
Line 173:		Line 173:

	While playing a fairly average game (less than 100 soldiers ever generated so far), I manually put stat strings on my soldiers' names. I currently have two Yoko Fujimotos with various stat strings. Considering that duplicate names aren't seen within a single game while testing names, but that I did see a second Yoko Fujimoto get generated after I changed the name of my original to Yoko Fujimoto-xs, I'm going to go ahead and say "The game probably just avoids duplicates by comparing the name it generates to each existing soldier's name". I predict that if you hire a female Russian soldier, and change her name to "Austin Bradley", you will never see another soldier generated with the name "Austin Bradley" but you might see a new soldier with her original name. This would be very tedious to test. --[[User:Sowelu\|Sowelu]] 14:15, 16 September 2008 (PDT)		While playing a fairly average game (less than 100 soldiers ever generated so far), I manually put stat strings on my soldiers' names. I currently have two Yoko Fujimotos with various stat strings. Considering that duplicate names aren't seen within a single game while testing names, but that I did see a second Yoko Fujimoto get generated after I changed the name of my original to Yoko Fujimoto-xs, I'm going to go ahead and say "The game probably just avoids duplicates by comparing the name it generates to each existing soldier's name". I predict that if you hire a female Russian soldier, and change her name to "Austin Bradley", you will never see another soldier generated with the name "Austin Bradley" but you might see a new soldier with her original name. This would be very tedious to test. --[[User:Sowelu\|Sowelu]] 14:15, 16 September 2008 (PDT)
			:Check no further, I had a look at the code and indeed it checks against every entry in [[SOLDIER.DAT]] and will regenerate a new name in case of collision (up to ten times, after that it'll give up and use the duplicate one). There is no check to see if the entry is valid so it should also remember dead soldiers as long as their entries are not overwritten. [[User:Seb76\|Seb76]] 15:22, 16 September 2008 (PDT)

	==See Also==		==See Also==

Sowelu: Hypothesis on duplicate name checking

2008-09-16T21:15:41Z

Hypothesis on duplicate name checking

← Older revision		Revision as of 21:15, 16 September 2008
Line 169:		Line 169:

	It is not known why many combinations didn't show up, while others showed up multiple times. Also e.g. why there were 284 Japanese and 365 Germans, when the expected value is 333 (2000/6) for each set. Perhaps these results are due to random chance, or perhaps the name sampler has some sort of bias that makes certain combinations or nationalities more likely than others. Or maybe my 20 batches were simply not a big enough sample, particularly if the name selector does something odd when trying to avoid duplicates. For the complete dataset (including counts), see [[Media:X-COM Soldier Names.xls]]. If anyone knows how to do statistical testing for possible biases, feel free. Probably a much larger sample (10,000 recruits?) will give a clearer picture... but it would require 100 recruit batches, bleh. ''-[[User:MikeTheRed\|MTR]]		It is not known why many combinations didn't show up, while others showed up multiple times. Also e.g. why there were 284 Japanese and 365 Germans, when the expected value is 333 (2000/6) for each set. Perhaps these results are due to random chance, or perhaps the name sampler has some sort of bias that makes certain combinations or nationalities more likely than others. Or maybe my 20 batches were simply not a big enough sample, particularly if the name selector does something odd when trying to avoid duplicates. For the complete dataset (including counts), see [[Media:X-COM Soldier Names.xls]]. If anyone knows how to do statistical testing for possible biases, feel free. Probably a much larger sample (10,000 recruits?) will give a clearer picture... but it would require 100 recruit batches, bleh. ''-[[User:MikeTheRed\|MTR]]

			== Duplicates ==

			While playing a fairly average game (less than 100 soldiers ever generated so far), I manually put stat strings on my soldiers' names. I currently have two Yoko Fujimotos with various stat strings. Considering that duplicate names aren't seen within a single game while testing names, but that I did see a second Yoko Fujimoto get generated after I changed the name of my original to Yoko Fujimoto-xs, I'm going to go ahead and say "The game probably just avoids duplicates by comparing the name it generates to each existing soldier's name". I predict that if you hire a female Russian soldier, and change her name to "Austin Bradley", you will never see another soldier generated with the name "Austin Bradley" but you might see a new soldier with her original name. This would be very tedious to test. --[[User:Sowelu\|Sowelu]] 14:15, 16 September 2008 (PDT)

	==See Also==		==See Also==

Arrow Quivershaft: /* Name Sets */ Re-alphabetizing; nothing to see here, move along.

2008-05-01T20:43:26Z

Name Sets: Re-alphabetizing; nothing to see here, move along.

@@ Line 3: / Line 3: @@
 There are six sets of X-COM soldier names, each composed of 20 first names and 20 last names. 5 of the 20 first names in each set are female (based on [[SOLDIER.DAT]] byte 67), denoted by an asterisk:
        '''''<u>British Set</u>
        Adam         Bailey
@@ Line 24: / Line 46: @@
      * Sarah        White
        Scott        Wright
        '''''<u>French Set</u>

Zombie: /* Test Set */ Again, nationality change.

2008-04-30T21:40:51Z

Test Set: Again, nationality change.

← Older revision		Revision as of 21:40, 30 April 2008
Line 162:		Line 162:
	<u>Nationality</u> <u>Frequency</u>		<u>Nationality</u> <u>Frequency</u>
	B1 359		B1 359
	B2 316		A 316
	F 335		F 335
	G 365		G 365

Zombie: /* Name Sets */ Changed nationality of second name set.

2008-04-30T21:39:25Z

Name Sets: Changed nationality of second name set.

← Older revision		Revision as of 21:39, 30 April 2008
Line 3:		Line 3:
	There are six sets of X-COM soldier names, each composed of 20 first names and 20 last names. 5 of the 20 first names in each set are female (based on [[SOLDIER.DAT]] byte 67), denoted by an asterisk:		There are six sets of X-COM soldier names, each composed of 20 first names and 20 last names. 5 of the 20 first names in each set are female (based on [[SOLDIER.DAT]] byte 67), denoted by an asterisk:

	'''''<u>British Set ~~One~~</u>		'''''<u>British Set</u>
	Adam Bailey		Adam Bailey
	Alan Blake		Alan Blake
Line 25:		Line 25:
	Scott Wright		Scott Wright

	'''''<u>~~British~~ Set ~~Two~~</u>		'''''<u>American Set</u>
	Austin Bradley		Austin Bradley
	* Barbara Bryant		* Barbara Bryant

Zombie: /* See Also */ Redirecting.

2007-02-02T00:03:32Z

MikeTheRed at 19:26, 12 June 2006

2006-06-12T19:26:04Z

← Older revision		Revision as of 19:26, 12 June 2006
Line 139:		Line 139:
	== Test Set ==		== Test Set ==

	20 batches of 100 recruits (total N 2,000) were used as a sample. Not all possible 2,400 first and last name combinations appeared, of course, but first and last names were always associated as shown above. Thus you may see an Adam Bailey, but will never see an Adam Bradley.		20 batches of 100 recruits (total N=2,000) were used as a sample. Not all possible 2,400 first and last name combinations appeared, of course, but first and last names were always associated as shown above. Thus you may see an Adam Bailey, but will never see an Adam Bradley.

	510 of 2,000 soldiers were female (25.50%), almost exactly the expected 500 (25%).		510 of 2,000 soldiers were female (25.50%), almost exactly the expected 500 (25%).
Line 169:		Line 169:

	It is not known why many combinations didn't show up, while others showed up multiple times. Also e.g. why there were 284 Japanese and 365 Germans, when the expected value is 333 (2000/6) for each set. Perhaps these results are due to random chance, or perhaps the name sampler has some sort of bias that makes certain combinations or nationalities more likely than others. Or maybe my 20 batches were simply not a big enough sample, particularly if the name selector does something odd when trying to avoid duplicates. For the complete dataset (including counts), see [[Media:X-COM Soldier Names.xls]]. If anyone knows how to do statistical testing for possible biases, feel free. Probably a much larger sample (10,000 recruits?) will give a clearer picture... but it would require 100 recruit batches, bleh. ''-[[User:MikeTheRed\|MTR]]		It is not known why many combinations didn't show up, while others showed up multiple times. Also e.g. why there were 284 Japanese and 365 Germans, when the expected value is 333 (2000/6) for each set. Perhaps these results are due to random chance, or perhaps the name sampler has some sort of bias that makes certain combinations or nationalities more likely than others. Or maybe my 20 batches were simply not a big enough sample, particularly if the name selector does something odd when trying to avoid duplicates. For the complete dataset (including counts), see [[Media:X-COM Soldier Names.xls]]. If anyone knows how to do statistical testing for possible biases, feel free. Probably a much larger sample (10,000 recruits?) will give a clearer picture... but it would require 100 recruit batches, bleh. ''-[[User:MikeTheRed\|MTR]]

			==See Also==
			*[[Raw_recruit_statistical_likelihood\|Recruit Statistics]]
			*[[Soldiers (UFO Defense)\|Soldiers]]
			*[[Hiring/firing]]

← Older revision		Revision as of 00:03, 2 February 2007
Line 172:		Line 172:
	==See Also==		==See Also==
	*[[Raw_recruit_statistical_likelihood\|Recruit Statistics]]		*[[Raw_recruit_statistical_likelihood\|Recruit Statistics]]
	*[[~~Soldiers (UFO Defense)\|~~Soldiers]]		*[[Soldiers]]
	*[[Hiring/firing]]		*[[Hiring/firing]]