MersenneTwister Work Item Rss Feed

MersenneTwister Work Item Rss Feedhttp://code.msdn.microsoft.com/MersenneTwister/WorkItem/List.aspxMersenneTwister Work Item Rss DescriptionCLOSED ISSUE: Broken Next()?http://code.msdn.microsoft.com/MersenneTwister/WorkItem/View.aspx?WorkItemId=1I ported the code to VB (used an automated tool followed by minor modifications). As a sanity check I wrote a simple program to compute randoms for a few seconds, count distributions, and then dump to the console.<br /><br />I found that rand.Next(N) will always return half of the results that should be zero as N. This is an error, as Next(N) should always return a number less than N. <br /><br />For example, If I generate 30 randoms using rand.Next(3), then I'll get something like the following.<br />0=5<br />1=10<br />2=10<br />3=5<br /><br />It's always possible that I messed something up in translation from C# to VB, but I couldn't spot anything obvious.<br />codekaizenSat, 26 Apr 2008 04:05:19 GMTCLOSED ISSUE: Broken Next()? 20080426ACOMMENTED ISSUE: Broken Next()?http://code.msdn.microsoft.com/MersenneTwister/WorkItem/View.aspx?WorkItemId=1I ported the code to VB (used an automated tool followed by minor modifications). As a sanity check I wrote a simple program to compute randoms for a few seconds, count distributions, and then dump to the console.<br /><br />I found that rand.Next(N) will always return half of the results that should be zero as N. This is an error, as Next(N) should always return a number less than N. <br /><br />For example, If I generate 30 randoms using rand.Next(3), then I'll get something like the following.<br />0=5<br />1=10<br />2=10<br />3=5<br /><br />It's always possible that I messed something up in translation from C# to VB, but I couldn't spot anything obvious.<br />Comments: Thanks for the translation!codekaizenFri, 18 Apr 2008 07:55:14 GMTCOMMENTED ISSUE: Broken Next()? 20080418ACOMMENTED ISSUE: Broken Next()?http://code.msdn.microsoft.com/MersenneTwister/WorkItem/View.aspx?WorkItemId=1I ported the code to VB (used an automated tool followed by minor modifications). As a sanity check I wrote a simple program to compute randoms for a few seconds, count distributions, and then dump to the console.<br /><br />I found that rand.Next(N) will always return half of the results that should be zero as N. This is an error, as Next(N) should always return a number less than N. <br /><br />For example, If I generate 30 randoms using rand.Next(3), then I'll get something like the following.<br />0=5<br />1=10<br />2=10<br />3=5<br /><br />It's always possible that I messed something up in translation from C# to VB, but I couldn't spot anything obvious.<br />Comments: Well, my background threads finally caught up, and reminded me that VB always uses bankers rounding instead of truncation when converting from floating point to integer. 
Once I fixed the code, it works perfectly.
Sorry for the confusion,
jJustinMichelWed, 16 Apr 2008 17:50:13 GMTCOMMENTED ISSUE: Broken Next()? 20080416PCREATED ISSUE: Broken Next()?http://code.msdn.microsoft.com/MersenneTwister/WorkItem/View.aspx?WorkItemId=1I ported the code to VB (used an automated tool followed by minor modifications). As a sanity check I wrote a simple program to compute randoms for a few seconds, count distributions, and then dump to the console.<br /><br />I found that rand.Next(N) will always return half of the results that should be zero as N. This is an error, as Next(N) should always return a number less than N. <br /><br />For example, If I generate 30 randoms using rand.Next(3), then I'll get something like the following.<br />0=5<br />1=10<br />2=10<br />3=5<br /><br />It's always possible that I messed something up in translation from C# to VB, but I couldn't spot anything obvious.<br />JustinMichelMon, 14 Apr 2008 00:16:06 GMTCREATED ISSUE: Broken Next()? 20080414A