Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Stata during computer lock

    On my work station, I usually run some models that take a while to run - at night. I then lock the computer (start+L, windows 7 PC). It seems that after several hours the computer just... stops running the estimations and Stata enters some sort of "sleep" or "light use" mode. when I unlock the computer, the estimation continues.

    I use rmsg to track execution time & current time but unforuantely since the commands are inside a foreach loop, rmsg does not report execution time for each estimation command.
    I checked sleep\hibernate settings on the machine and everything is set to NEVER. also, since Stata is RUNNING, it shouldn't even invoke this. How can I solve this issue? I come back to the station after a couple of days when I hoped it would run all the time consuming commands and come back to see it ran only a couple of e'm...

    Any help would be greatly appreciated

  • #2
    Check the advanced power options, especially the hard disk

    (these steps are from Win 8 laptop, so I don't know if this will work on a desktop running Win 7)
    Control Panel\All Control Panel Items\Power Options
    Click Change Plan Settings
    Click Change Advanced Power Setting
    Stata/MP 14.1 (64-bit x86-64)
    Revision 19 May 2016
    Win 8.1

    Comment


    • #3
      Everything's set to NEVER, and like I already said: shouldn't these settings not be invoked anyway since Stata is running (and thus the computer is not 'idle" for any amount of time)?

      Comment


      • #4
        You'll have to ask your IT person, I guess. I don't know if this is a Stata thing or a PC thing. When I have a long run, I've never tried locking, I only turn off the display.
        Stata/MP 14.1 (64-bit x86-64)
        Revision 19 May 2016
        Win 8.1

        Comment


        • #5
          Sometimes there are additional power settings in the BIOS that are unaffected by settings in Windows. So on next boot, go in there and check.

          Comment


          • #6
            I just encountered the same problem (but only on a new Windows 10 computer, on Windows 7 everything works fine). Any updates/solutions of the previous posters?

            Comment

            Working...
            X