Results 1 to 10 of 10

Thread: Kill the "image Reconstruction" verbosity from LWSN

  1. #1
    can't.. re.. member stib's Avatar
    Join Date
    Apr 2003
    Location
    [0,0,0]
    Posts
    963

    Kill the "image Reconstruction" verbosity from LWSN

    When you do a render in LWSN, it's good to be able to keep track of what it's up to. One annoying thing is the way a very minor part of the process, the image reconstruction filter, is so verbose that it takes up 99.9% of the screen space. Could we get rid of it?
    So we'd see

    Code:
    Updating geometry.
    Moving Triceratops.
    Rendering frame 793, segment 1/1, pass 2/2.
    Image Reconstruction: complete
    Writing RGB image to D:\hype\triceratops\triceratops walk_rgb_00793.png.
    Frame completed.
    Last Frame Rendered: 793.
    Rendering Time: 2m 2s (122.8 seconds).
    instead of

    Code:
    Pass: 2/2.
    Updating geometry.
    Moving Triceratops.
    Rendering frame 793, segment 1/1, pass 2/2.
    Image Reconstruction.
    Image Reconstruction : 0%.
    Image Reconstruction : 0%.
    Image Reconstruction : 1%.
    Image Reconstruction : 2%.
    Image Reconstruction : 2%.
    Image Reconstruction : 3%.
    Image Reconstruction : 4%.
    Image Reconstruction : 4%.
    Image Reconstruction : 5%.
    Image Reconstruction : 6%.
    Image Reconstruction : 6%.
    Image Reconstruction : 7%.
    Image Reconstruction : 8%.
    Image Reconstruction : 8%.
    Image Reconstruction : 9%.
    Image Reconstruction : 10%.
    Image Reconstruction : 10%.
    Image Reconstruction : 11%.
    Image Reconstruction : 12%.
    Image Reconstruction : 12%.
    Image Reconstruction : 13%.
    Image Reconstruction : 14%.
    Image Reconstruction : 14%.
    Image Reconstruction : 15%.
    Image Reconstruction : 16%.
    Image Reconstruction : 16%.
    Image Reconstruction : 17%.
    Image Reconstruction : 18%.
    Image Reconstruction : 18%.
    Image Reconstruction : 19%.
    Image Reconstruction : 20%.
    Image Reconstruction : 20%.
    Image Reconstruction : 21%.
    Image Reconstruction : 22%.
    Image Reconstruction : 22%.
    Image Reconstruction : 23%.
    Image Reconstruction : 24%.
    Image Reconstruction : 24%.
    Image Reconstruction : 25%.
    Image Reconstruction : 26%.
    Image Reconstruction : 26%.
    Image Reconstruction : 27%.
    Image Reconstruction : 28%.
    Image Reconstruction : 28%.
    Image Reconstruction : 29%.
    Image Reconstruction : 30%.
    Image Reconstruction : 30%.
    Image Reconstruction : 31%.
    Image Reconstruction : 32%.
    Image Reconstruction : 32%.
    Image Reconstruction : 33%.
    Image Reconstruction : 34%.
    Image Reconstruction : 34%.
    Image Reconstruction : 35%.
    Image Reconstruction : 36%.
    Image Reconstruction : 36%.
    Image Reconstruction : 37%.
    Image Reconstruction : 38%.
    Image Reconstruction : 38%.
    Image Reconstruction : 39%.
    Image Reconstruction : 40%.
    Image Reconstruction : 40%.
    Image Reconstruction : 41%.
    Image Reconstruction : 42%.
    Image Reconstruction : 42%.
    Image Reconstruction : 43%.
    Image Reconstruction : 44%.
    Image Reconstruction : 44%.
    Image Reconstruction : 45%.
    Image Reconstruction : 46%.
    Image Reconstruction : 46%.
    Image Reconstruction : 47%.
    Image Reconstruction : 48%.
    Image Reconstruction : 48%.
    Image Reconstruction : 49%.
    Image Reconstruction : 50%.
    Image Reconstruction : 50%.
    Image Reconstruction : 51%.
    Image Reconstruction : 52%.
    Image Reconstruction : 52%.
    Image Reconstruction : 53%.
    Image Reconstruction : 54%.
    Image Reconstruction : 54%.
    Image Reconstruction : 55%.
    Image Reconstruction : 56%.
    Image Reconstruction : 56%.
    Image Reconstruction : 57%.
    Image Reconstruction : 58%.
    Image Reconstruction : 58%.
    Image Reconstruction : 59%.
    Image Reconstruction : 60%.
    Image Reconstruction : 60%.
    Image Reconstruction : 61%.
    Image Reconstruction : 62%.
    Image Reconstruction : 62%.
    Image Reconstruction : 63%.
    Image Reconstruction : 64%.
    Image Reconstruction : 64%.
    Image Reconstruction : 65%.
    Image Reconstruction : 66%.
    Image Reconstruction : 66%.
    Image Reconstruction : 67%.
    Image Reconstruction : 68%.
    Image Reconstruction : 68%.
    Image Reconstruction : 69%.
    Image Reconstruction : 70%.
    Image Reconstruction : 70%.
    Image Reconstruction : 71%.
    Image Reconstruction : 72%.
    Image Reconstruction : 72%.
    Image Reconstruction : 73%.
    Image Reconstruction : 74%.
    Image Reconstruction : 74%.
    Image Reconstruction : 75%.
    Image Reconstruction : 76%.
    Image Reconstruction : 76%.
    Image Reconstruction : 77%.
    Image Reconstruction : 78%.
    Image Reconstruction : 78%.
    Image Reconstruction : 79%.
    Image Reconstruction : 80%.
    Image Reconstruction : 80%.
    Image Reconstruction : 81%.
    Image Reconstruction : 82%.
    Image Reconstruction : 82%.
    Image Reconstruction : 83%.
    Image Reconstruction : 84%.
    Image Reconstruction : 84%.
    Image Reconstruction : 85%.
    Image Reconstruction : 86%.
    Image Reconstruction : 86%.
    Image Reconstruction : 87%.
    Image Reconstruction : 88%.
    Image Reconstruction : 88%.
    Image Reconstruction : 89%.
    Image Reconstruction : 90%.
    Image Reconstruction : 90%.
    Image Reconstruction : 91%.
    Image Reconstruction : 92%.
    Image Reconstruction : 92%.
    Image Reconstruction : 93%.
    Image Reconstruction : 94%.
    Image Reconstruction : 94%.
    Image Reconstruction : 95%.
    Image Reconstruction : 96%.
    Image Reconstruction : 96%.
    Image Reconstruction : 97%.
    Image Reconstruction : 98%.
    Image Reconstruction : 98%.
    Image Reconstruction : 99%.
    Writing RGB image to D:\hype\triceratops\triceratops walk_rgb_00793.png.
    Frame completed.
    Last Frame Rendered: 793.
    Rendering Time: 2m 2s (122.8 seconds).
    2×Xeon 6140×18 cores×@2.3GHz, 96Gb Ram 2×Quadro p5000
    nerdiness and free stuff at my blob

  2. #2
    Doubt it. It's a dos window; doubt we can expect, and won't get, something that would eliminate those lines as you wish.
    How else would you propose the progress of a render be reported?
    Robert Wilson, MA Deaf Ed.
    Indiana Deaf School
    This e-mail may contain information protected under the Family Educational Rights and Privacy Act.

  3. #3
    Registered User
    Join Date
    May 2012
    Location
    Virginia
    Posts
    535
    Quote Originally Posted by [email protected] View Post
    Doubt it. It's a dos window; doubt we can expect, and won't get, something that would eliminate those lines as you wish.
    How else would you propose the progress of a render be reported?
    count 0-100 % single line

  4. #4
    But it's not a 'count', it's based on lapsed time.
    I think there is a way to make lwsn not so verbose that it reports that.
    Robert Wilson, MA Deaf Ed.
    Indiana Deaf School
    This e-mail may contain information protected under the Family Educational Rights and Privacy Act.

  5. #5
    Registered User
    Join Date
    May 2012
    Location
    Virginia
    Posts
    535
    Quote Originally Posted by [email protected] View Post
    But it's not a 'count', it's based on lapsed time.
    I think there is a way to make lwsn not so verbose that it reports that.
    It is a count... it's already expressing it as a percentage of the logical block data of the image. It just needs to do the percentage count on a single line, just like DOS does when you format a HDD.

    It shows 0-100%... Complete.

  6. #6
    Couldn't think of an example. is that the only example of a dos progress counter on one line? Haven't seen formatting in a dos window in a while.
    There ya go...
    Robert Wilson, MA Deaf Ed.
    Indiana Deaf School
    This e-mail may contain information protected under the Family Educational Rights and Privacy Act.

  7. #7
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,898
    The core issue is that log files aren't intended as "visual UI" and vice versa, they have exclusionary requirements. Unsurprisingly, trying to solve both at once does a poor job of solving either.
    John W.
    LW2015.3UB/2019.1.5 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  8. #8
    can't.. re.. member stib's Avatar
    Join Date
    Apr 2003
    Location
    [0,0,0]
    Posts
    963
    Quote Originally Posted by [email protected] View Post
    Doubt it. It's a dos window; doubt we can expect, and won't get, something that would eliminate those lines as you wish.
    How else would you propose the progress of a render be reported?
    Simple: in the LWSXN code where it goes
    Code:
    while (percentage< 100%){
      print ("Image Reconstruction : " + percentage);
      percentage = doSomeImageReconstructing();
    }
    change it to:
    Code:
    while (percentage< 100%){
      //print ("Image Reconstruction : " + percentage);
      percentage = doSomeImageReconstructing();
    }
    print ("Image Reconstruction : " + percentage);
    Basically get rid of the console logging during the image reconstruction loop. It's usually an insignificant part of the render cycle, but it occupies by far the most room in the log.
    2×Xeon 6140×18 cores×@2.3GHz, 96Gb Ram 2×Quadro p5000
    nerdiness and free stuff at my blob

  9. #9
    Excellent. You have a solution.

  10. #10
    Registered User
    Join Date
    May 2012
    Location
    Virginia
    Posts
    535
    Now just send it in as a feature request using the tool. It should be easy enough to implement.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •