Thread: Re: [Rails-devel] 1830 Coalfield bug

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

 Recently I started an 1830 Coalfield PBeM. When I made an analysis of 
 what to do I found that N&W can not operate. It start token is not 
 placed and thus game halts whein it is N&W's turn to operate. See 
 attached save file.

 Best
 Arne Östlund

 On Thu, 11 Aug 2011 16:18:14 +0000, 
 rai...@li... wrote:
> Send Rails-devel mailing list submissions to
> 	rai...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/rails-devel
> or, via email, send a message with subject or body 'help' to
> 	rai...@li...
>
> You can reach the person managing the list at
> 	rai...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Rails-devel digest..."
>
>
> Today's Topics:
>
>    1. Re: How to clean up the Git index? (Erik Vos)
>    2. Re: How to clean up the Git index? (brett lentz)
>    3. Re: How to clean up the Git index? (Erik Vos)
>    4. 18TN revenue calculation (4ba69a) (Stefan Frey)
>    5. Automated test reports without currency identifier	(19de64)
>       (Stefan Frey)
>    6. Re: Automated test reports without currency	identifier
>       (19de64) (Erik Vos)
>    7. Re: Route calculation: Train length heuristic (Stefan Frey)
>
>
> 
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 10 Aug 2011 19:22:42 +0200
> From: "Erik Vos" <eri...@xs...>
> Subject: Re: [Rails-devel] How to clean up the Git index?
> To: "'Development list for Rails: an 18xx game'"
> 	<rai...@li...>
> Message-ID: <002701cc5782$1cb6f8a0$5624e9e0$@xs4all.nl>
> Content-Type: text/plain;	charset="us-ascii"
>
>> Try doing a "git diff" and see what lines it thinks are changed.
>
> None.  That's why I'm baffled.
>
> Erik.
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 10 Aug 2011 10:34:14 -0700
> From: brett lentz <bre...@gm...>
> Subject: Re: [Rails-devel] How to clean up the Git index?
> To: "Development list for Rails: an 18xx game"
> 	<rai...@li...>
> Message-ID:
> 	<CAM...@ma...>
> Content-Type: text/plain; charset=UTF-8
>
> On Wed, Aug 10, 2011 at 10:22 AM, Erik Vos <eri...@xs...> 
> wrote:
>>> Try doing a "git diff" and see what lines it thinks are changed.
>>
>> None. ?That's why I'm baffled.
>>
>> Erik.
>
>
> Strange.
>
> You can always do a "git reset --hard origin/master", but this will
> destroy any local commits you haven't pushed.
>
> A less destructive method is a simple "git reset --hard", which will
> reset any changes back to the state of your local HEAD.
>
> ---Brett.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 10 Aug 2011 20:36:44 +0200
> From: "Erik Vos" <eri...@xs...>
> Subject: Re: [Rails-devel] How to clean up the Git index?
> To: "'Development list for Rails: an 18xx game'"
> 	<rai...@li...>
> Message-ID: <002801cc578c$77845160$668cf420$@xs4all.nl>
> Content-Type: text/plain;	charset="UTF-8"
>
> A hard reset did it.  Thanks.
> Fortunately I had nothing to commit or push, I just wanted a clean
> house.  Now I have.
>
> Erik.
>
>> -----Original Message-----
>> From: brett lentz [mailto:bre...@gm...]
>> Sent: Wednesday, August 10, 2011 7:34 PM
>> To: Development list for Rails: an 18xx game
>> Subject: Re: [Rails-devel] How to clean up the Git index?
>>
>> On Wed, Aug 10, 2011 at 10:22 AM, Erik Vos <eri...@xs...> 
>> wrote:
>> >> Try doing a "git diff" and see what lines it thinks are changed.
>> >
>> > None.  That's why I'm baffled.
>> >
>> > Erik.
>>
>>
>> Strange.
>>
>> You can always do a "git reset --hard origin/master", but this will 
>> destroy any
>> local commits you haven't pushed.
>>
>> A less destructive method is a simple "git reset --hard", which will 
>> reset any
>> changes back to the state of your local HEAD.
>>
>> ---Brett.
>>
>> 
>> ------------------------------------------------------------------------------
>> uberSVN's rich system and user administration capabilities and model
>> configuration take the hassle out of deploying and managing 
>> Subversion and
>> the tools developers use with it. Learn more about uberSVN and get a 
>> free
>> download at:  http://p.sf.net/sfu/wandisco-dev2dev
>> _______________________________________________
>> Rails-devel mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 11 Aug 2011 18:02:34 +0200
> From: Stefan Frey <ste...@we...>
> Subject: [Rails-devel] 18TN revenue calculation (4ba69a)
> To: "Development list for Rails: an 18xx game"
> 	<rai...@li...>
> Message-ID: <201...@we...>
> Content-Type: Text/Plain;  charset="us-ascii"
>
> I have added the civil war revenue modifier (removing the shortest
> train of a
> company at that time), so 18TN should be finished, except for 
> checking if a
> company has no route at the time of civil war. For that case the 
> revenue has
> to be adjusted manually.
>
> To make this more transparent I allow static revenue modifiers now to 
> add a
> comment to the detailed revenue message and did this in a few other 
> cases
> (e.g. if a bonus was active for a company etc.)
>
> Stefan
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 11 Aug 2011 18:11:45 +0200
> From: Stefan Frey <ste...@we...>
> Subject: [Rails-devel] Automated test reports without currency
> 	identifier	(19de64)
> To: "Development list for Rails: an 18xx game"
> 	<rai...@li...>
> Message-ID: <201...@we...>
> Content-Type: Text/Plain;  charset="iso-8859-15"
>
> I agree that it is the better solution to have UTF-8 working all the 
> time
> (maybe Brett could check the setup of the git repo?)
> However it was easy to adjust the test.profile such that the reports 
> do not
> contain the problematic yen and euro currency characters.
>
>
> On Tuesday, August 09, 2011 06:46:06 pm John A. Tamplin wrote:
>> On Tue, Aug 9, 2011 at 12:25 PM, Stefan Frey <ste...@we...> 
>> wrote:
>> > The encoding (at least accoding to my editor) of the report files 
>> is
>> > still UTF-8 and they open up in the editor correctly.
>> > All tests report passed as well.
>> > However to avoid those issues I suggest to remove the currency 
>> indicator
>> > from
>> > the report files used for testing.
>> > I can do the code change tomorrow.
>>
>> It won't be just currency characters -- you would have to avoid all 
>> names
>> in the game as well.
>>
>> Better to make sure everything is always stored as UTF8 and 
>> interpreted as
>> UTF8 and be done with it.
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 11 Aug 2011 18:14:25 +0200
> From: "Erik Vos" <eri...@xs...>
> Subject: Re: [Rails-devel] Automated test reports without currency
> 	identifier	(19de64)
> To: "'Development list for Rails: an 18xx game'"
> 	<rai...@li...>
> Message-ID: <002001cc5841$bd7ff560$387fe020$@xs4all.nl>
> Content-Type: text/plain;	charset="iso-8859-1"
>
> But that doesn't fix the same problem with KK?B in 18EU.
>
> Erik.
>
>> -----Original Message-----
>> From: Stefan Frey [mailto:ste...@we...]
>> Sent: Thursday, August 11, 2011 6:12 PM
>> To: Development list for Rails: an 18xx game
>> Subject: [Rails-devel] Automated test reports without currency 
>> identifier
>> (19de64)
>>
>> I agree that it is the better solution to have UTF-8 working all the 
>> time
>> (maybe Brett could check the setup of the git repo?) However it was 
>> easy
> to
>> adjust the test.profile such that the reports do not contain the
> problematic
>> yen and euro currency characters.
>>
>>
>> On Tuesday, August 09, 2011 06:46:06 pm John A. Tamplin wrote:
>> > On Tue, Aug 9, 2011 at 12:25 PM, Stefan Frey <ste...@we...>
>> wrote:
>> > > The encoding (at least accoding to my editor) of the report 
>> files is
>> > > still UTF-8 and they open up in the editor correctly.
>> > > All tests report passed as well.
>> > > However to avoid those issues I suggest to remove the currency
>> > > indicator from the report files used for testing.
>> > > I can do the code change tomorrow.
>> >
>> > It won't be just currency characters -- you would have to avoid 
>> all
>> > names in the game as well.
>> >
>> > Better to make sure everything is always stored as UTF8 and
>> > interpreted as
>> > UTF8 and be done with it.
>>
>>
> 
> ----------------------------------------------------------------------------
> --
>> Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user
>> administration capabilities and model configuration. Take the hassle 
>> out
> of
>> deploying and managing Subversion and the tools developers use with 
>> it.
>> http://p.sf.net/sfu/wandisco-dev2dev
>> _______________________________________________
>> Rails-devel mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 11 Aug 2011 18:20:44 +0200
> From: Stefan Frey <ste...@we...>
> Subject: Re: [Rails-devel] Route calculation: Train length heuristic
> To: "Development list for Rails: an 18xx game"
> 	<rai...@li...>
> Message-ID: <201...@we...>
> Content-Type: Text/Plain;  charset="iso-8859-1"
>
> Erik,
> it is already implemented (in a local branch, otherwise I would have
> not been
> able to report running times).
>
> However I want to run some more tests before pushing it.
>
> The answer to your question is no:I it does not require a train 
> config
> attribute as the train domination is implemented as a Comparator 
> (method) in
> the NetworkTrain class.
>
> So the train conditions could be checked automatically, however there 
> can be
> certain conditions in specific games that break the heuristic, for 
> example
> bonuses that are only valid for specific trains (e.g. if in 18AL 
> players
> decide to have the director assign the named train themselves).
>
> As the heuristic is only necessary in games with very long trains (as
> in 1830,
> 1856, 1870) I want to be on the safe side and only activate the 
> heuristic in
> those games after some tests by providing a global switch as an 
> attribute to
> the RevenueManager in game.xml.
>
> Stefan
>
>
> On Tuesday, August 09, 2011 11:14:47 am Erik Vos wrote:
>> Stefan,
>>
>> Do you plan to implement this heuristic in Rails?
>> Would it require a new TrainType config attribute, like <TrainType
>> name="6+6" ... dominates="6,5+5"/>?
>>
>> Erik.
>>
>> > -----Original Message-----
>> > From: Stefan Frey [mailto:ste...@we...]
>> > Sent: Tuesday, August 09, 2011 7:03 AM
>> > To: Development list for Rails: an 18xx game
>> > Subject: [Rails-devel] Route calculation: Train length heuristic
>> >
>> > A year ago I suggested another heuristic to improve the speed of 
>> the
>> > revenue calculation.
>> >
>> > The idea is to use what 1830 players automatically do:
>> > If you calculate a run for a 4 and a 3 train, you already know 
>> that you
>>
>> will end
>>
>> > up with a longer route (more stations) for the 4 train and a 
>> shorter
>> > route
>>
>> for
>>
>> > the 3 train. Similar for running a Diesel and a 5 train.
>> >
>> > However this knowledge is not taken into account by the current
>> > algorithm. Things unfortunately are not that easy for all 18xx as 
>> it are
>> > in 1830. For example in 1835 one cannot tell this ex-ante for a
>> > combination of a
>>
>> 5+5
>>
>> > and a 6 train. That in fact is one the reasons why calculating the
>>
>> Preussian
>>
>> > routes is not an easy task.
>> >
>> > Another exceptions are: If trains score differently for the same 
>> route
>> > (Express (xE) and Double (xD) trains) or if hex trains run jointly 
>> with
>>
>> standard
>>
>> > trains.
>> >
>> > ** The formal definition of train domination:
>> >
>> > If the "better" train A can run all routes that the "weaker" train 
>> B and
>>
>> train A
>>
>> > scores identical revenue on all routes as B, then I define that 
>> train A
>> > dominates train B.
>> >
>> > If A dominates B I write this as A>B, otherwise the trains are 
>> either
>>
>> identical
>>
>> > (A=B) or neither dominates (A<>B).
>> >
>> > If train A dominates train B, the length of the route of train A 
>> will
>>
>> always be
>>
>> > longer or at least equally long as that of train B.
>> > (Length of the route is the number of stations scored.)
>> >
>> > ** Examples should make this clearer.
>> >
>> > In 1830 it is easy:  D>6>5>4>3>2
>> >
>> > In 1835 it is
>> > 6+6 > 5+5 > 4+4 > 3+3 > 2+2
>> > 6 > 5 > 4 > 3 > 2
>> > 6+6 > 6, 5+5 > 5, 4 +4 > 4, 3+3 > 3, 2+2 > 2
>> > 6 > 3+3, 4 > 2+2
>> > But for example: 6 <> 5+5, 5 <> 3+3 etc.
>> >
>> > ** Implementation
>> > The implementation is pretty straight forward and only requires a 
>> few
>>
>> lines
>>
>> > of code in the revenue calculator. The major change is to order 
>> the
>> > trains
>>
>> by
>>
>> > the criteria "train domination". Then the calculator assigns the 
>> initial
>>
>> train
>>
>> > length for the dominated train not with the maximum length of that 
>> train,
>> > but with the (current) route length of the dominating train. This 
>> ensures
>>
>> that
>>
>> > the dominating train will always have the longer route assigned.
>> >
>> > ** Speed improvement
>> > I did run the scenarios of Aliza Panitz 1856 triple Diesel of CGR
>>
>> scenarios and
>>
>> > came to the following running times (more statistics on number of 
>> routes
>> > evaluated and when the best solution was found see below).
>> >
>> > For the simpler network (A) running times decrease from around 5 
>> minutes
>> > to
>> > 3.5 minutes (my CPU is more powerful than Alizas ...).
>> > For the extensive network (B) running times decrease from around 1 
>> hour
>> > to around 30 minutes.
>> >
>> > Overall the improvement it seems that the speed is improved by 
>> around 50%
>> > to 200%, so time to wait is down by 33% to 66%, which is not bad.
>> >
>> > But as it can be clearly seen by comparison with a double Diesel
>> > scenarios
>>
>> the
>>
>> > exponential characteristic of the algorithm is still very clear.
>> >
>> > So I still hope that John Tamplin can give some hints on his lost 
>> flow
>>
>> algorithm
>>
>> > for those who want to run triple Diesel more often.
>> >
>> > Stefan
>> >
>> > ** Stats
>> >
>> > => Aliza Scenario 1856 A:
>> > 31 vertices with 41 edges
>> > 10 startvertices
>> >
>> > Values:
>> > Single D: 700
>> > Double D: 920
>> > Triple D: 1120
>> >
>> > Single D: 0 second / 6.2k Evaluations, 6.2k Predictions
>> >
>> > Without dominant trains:
>> > Double D: 3 seconds / 1.3M Evaluations, 1.4M Predictions Triple D: 
>> 290
>> > seconds / 114.9M Evaluations, 129.5M Predictions
>> > (Solution: 25 seconds / 13.4M Evaluations, 14.7M Predictions)
>> >
>> > With dominant trains:
>> > Double D: 1 second / 323k Evaluations, 385k Predictions Triple D: 
>> 206
>>
>> seconds
>>
>> > / 87.4M Evaluations, 98.0M Predictions
>> > (Solution: 20 seconds / 9.1M Evaluations, 10.0M Predictions)
>> >
>> > => Aliza Scenario 1856 B:
>> > 34 vertices with 50 edges
>> > 10 startvertices
>> >
>> > Values:
>> > Single D: 790
>> > Double D: 1280
>> > Triple D: 1440
>> >
>> > Single D: 0 second / 53.3k Evaluations, 53.3k Predictions
>> >
>> > Without dominant trains:
>> > Double D: 12 seconds / 4.8M Evaluations, 5.1M Predictions Triple 
>> D: 3551
>> > seconds / 1473M Evaluations, 1709M Predictions
>> > (Solution: 41 seconds / 16.9M Evaluations, 17.7M Predictions)
>> >
>> > With dominant trains:
>> > Double D: 5 seconds / 1.9M Evaluations, 2.3M Predictions Triple D: 
>> 1926
>> > seconds / 832M Evaluations, 962M Predictions
>> > (Solution: 27 seconds / 11.7M Evaluations, 12.3M Predictions)
>> >
>> > => Scenario 1870:
>> > This is the route network used for testing a year ago,
>> >
>> > 23 vertices with 57 edges
>> > 1 startvertex
>> >
>> > Values:
>> > Single 12: 380
>> > Double 12: 690
>> > Triple 12: 820
>> >
>> > Single 12: 0 second / 11.5k Evaluations, 23.7k Predictions
>> >
>> > Without dominant trains:
>> > Double 12: 4 seconds / 1.4M Evaluations, 1.9M Predictions Triple 
>> 12: 104
>> > seconds / 23.4M Evaluations, 61.6M Predictions
>> > (Solution: 13 seconds / 3.2M Evaluations, 6.2M Predictions)
>> >
>> > With dominant trains:
>> > Double 12: 4 seconds / 1.2M Evaluations, 1.7M Predictions Triple 
>> 12: 49
>> > seconds / 8.1M Evaluations, 30.0M Predictions
>> > (Solution: 16 seconds / 3.0M Evaluations, 9.3M Predictions)
>>
>> 
>> ---------------------------------------------------------------------------
>> - --
>>
>> > uberSVN's rich system and user administration capabilities and 
>> model
>> > configuration take the hassle out of deploying and managing 
>> Subversion
>> > and the tools developers use with it. Learn more about uberSVN and 
>> get a
>> > free download at:  http://p.sf.net/sfu/wandisco-dev2dev
>> > _______________________________________________
>> > Rails-devel mailing list
>> > Rai...@li...
>> > https://lists.sourceforge.net/lists/listinfo/rails-devel
>>
>> 
>> ---------------------------------------------------------------------------
>> --- uberSVN's rich system and user administration capabilities and 
>> model
>> configuration take the hassle out of deploying and managing 
>> Subversion and
>> the tools developers use with it. Learn more about uberSVN and get a 
>> free
>> download at:  http://p.sf.net/sfu/wandisco-dev2dev
>> _______________________________________________
>> Rails-devel mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
>
> ------------------------------
>
> 
> ------------------------------------------------------------------------------
> Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
> user administration capabilities and model configuration. Take
> the hassle out of deploying and managing Subversion and the
> tools developers use with it.
> http://p.sf.net/sfu/wandisco-dev2dev
>
> ------------------------------
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
> End of Rails-devel Digest, Vol 45, Issue 12
> *******************************************