MASON-INTEREST-L Archives

April 2007

MASON-INTEREST-L@LISTSERV.GMU.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Date:
Sat, 28 Apr 2007 11:17:29 -0400
Reply-To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Subject:
From:
Gabriel Catalin Balan <[log in to unmask]>
Content-Type:
TEXT/PLAIN; charset=US-ASCII
In-Reply-To:
MIME-Version:
1.0
Comments:
To: MASON Multiagent Simulation Toolkit <[log in to unmask]>
Parts/Attachments:
TEXT/PLAIN (95 lines)
Hello

The string "Exhausted" is printed on the standard error stream
	i.e. System.err.println("Exhausted");
while your printout use the standard output stream.
Printing on the two is not synchronized, so there you go.

As for the fix-up
1. the ugly way: print your messages on err, too (or even try to make
System.out and System.err point to the same thing)
2. the elegant(?) way: redirect one of the streams into a file.
// add '> file' (without quotes) to the command line to print whatever
comes out of the System.out in the file file.
// as for std err, use 2> for windows and >& otherwise

Gabriel



On Sat, 28 Apr 2007, MASON-INTEREST-L automatic digest system wrote:

> There is 1 message totalling 65 lines in this issue.
>
> Topics of the day:
>
>   1. In Main DoLoop Why Does it Return Exhausted?
>
> ----------------------------------------------------------------------
>
> Date:    Fri, 27 Apr 2007 15:23:20 +0100
> From:    Rick <[log in to unmask]>
> Subject: Re: In Main DoLoop Why Does it Return Exhausted?
>
> Hi,
>
> is there any way to extend this as it seems to be printing it/doing it
> at random times and it should not have finished i.e. when I print the
> out put of what its doing:
>
>    NK: 11 Fitness: 0.6491967237334823 Exhausted
> 11,
>    NK: 12 Fitness: 0.5772002334011134 12,
>    NK: 13 Fitness: 0.7174971112923958 13,
>
> then continues?? seems a bit strange, and on each run Exhausted may
> appear in different places!
>
> Does work sometimes correctly without any problems but other I get
> "Exhausted" which causes things to go wrong.
>
> even on just a single run "Exhausted" will appear however others time
> it wont (note this is for the exact same values)
>
> Rick
>
> Sean Luke wrote:
> > You told MASON to run your simulation five times.  Each time the
> > simulation exhausted its schedule.  "Exhausted" means that there was
> > nothing left on the schedule to do and so the simulation terminated.
> >
> > Sean
> >
> > On Apr 26, 2007, at 2:34 PM, Rick wrote:
> >
> >> Hi,
> >>
> >> when running in command line with arg:  - repeat 5
> >>
> >> why does it start running the first sim then print Exhausted in red
> >> continue a bit and then just do this:
> >>
> >> Job: 2 Seed: 1177612251502
> >> Starting sim.app.NK_Model.Model
> >> Exhausted
> >> Job: 3 Seed: 1177612251503
> >> Starting sim.app.NK_Model.Model
> >> Exhausted
> >> Job: 4 Seed: 1177612251504
> >> Starting sim.app.NK_Model.Model
> >> Exhausted
> >>
> >> Any Ideas?
> >>
> >> Sorry this is my last question! :-)
> >>
> >> Thanks
> >>
> >> Rick
>
> ------------------------------
>
> End of MASON-INTEREST-L Digest - 26 Apr 2007 to 27 Apr 2007 (#2007-14)
> **********************************************************************
>

ATOM RSS1 RSS2