I have a long-running random simulation that spits out debug messages. I
extrapolated that it would take 20 hours to get 5,000,000 samples, and
let it run for a day. Here's what I saw when I returned:
Welcome to DrRacket, version 5.90.0.9--2013-10-04(876995d5/d) [3m].
Language: typed/racket
Was it black on yellow or red?
Robby
On Mon, Oct 7, 2013 at 10:32 AM, Neil Toronto neil.toro...@gmail.comwrote:
I have a long-running random simulation that spits out debug messages. I
extrapolated that it would take 20 hours to get 5,000,000 samples, and let
it run for a day. Here's what I
Black on yellow.
On 10/07/2013 09:50 AM, Robby Findler wrote:
Was it black on yellow or red?
Robby
On Mon, Oct 7, 2013 at 10:32 AM, Neil Toronto neil.toro...@gmail.com
mailto:neil.toro...@gmail.com wrote:
I have a long-running random simulation that spits out debug
messages. I
Then I think that that means that the message came from
rep.rkt's no-user-evaluation-message function and that you either should
have gotten a dialog with an explanation for why it terminated, or you have
the preference 'drracket:show-killed-dialog set to #f. I think that the
only two explanations
I have that preference set to #f, if this is what it looks like in the
preferences file:
(plt:framework-pref:drracket:show-killed-dialog #f)
Apparently, it got set to #f when I unchecked Show this dialog next
time once after I hit Ctrl-K and DrRacket warned me that I couldn't use
the
Probably the check box should make finer distinctions, yes (altho the
plumbing inside is the same, as it turns out).
And, FWIW setting it to #t will probably only say you ran out of memory.
And at the command line, you don't have drracket hogging all that memory so
probably that's the best thing,
6 matches
Mail list logo
