Waiting for reconstruction?

Answered

Comments

6 comments

  • Avatar
    Wishgranter

    Hi Enrique Castillo

    Some screenshot would be helpfull + your PC spec + img count + img resolution. 

    0
    Comment actions Permalink
  • Avatar
    Götz Echtenacher

    Hi Enrique,

    have you tried it several times with reboot in between?

    0
    Comment actions Permalink
  • Avatar
    Benjamin von Cramon

    I've encountered this issue before, am encountering it presently, yet to make sense of it and poking at solutions with no real pattern or progress emerging. Behavior: during Reconstruction creation of depth maps progresses at normal pace, as does comparing depth maps, then first five parts (of 95) are generated, system goes into highly unresponsive state. Resource Monitor shows RC is flat-lining in CPU, I have to wait many seconds for a mouse move or keyboard command to take effect. I set RC's Priority to the highest level in Task Manager, tried restarting the project, restarting PC, then clearing cache and starting over, ends in the same sluggish state. I'm now trying exporting a .rcalign and running in a new project. 

    If I pause RC, PC returns to fully responsive, then resume brings the sluggishness right back. This particular project only has 392 images, routinely run 3 and 4 times as many. I've also noticed the slow down can happen in different operations, like while creating depth maps. I've tested against memory leaks but nothing comes up. Any thoughts?

     

    Thanks,

    Benjy

    0
    Comment actions Permalink
  • Avatar
    Götz Echtenacher

    Et tu, Benjy?  :-)

    There are way too many cases like this to be explained away.

    I really think that somebody who is concerned should make a bug report and involve somebody from RC.

    0
    Comment actions Permalink
  • Avatar
    Benjamin von Cramon

    Agreed. What's really useful in when apps provide a log file that can be switched on to report everything that goes on including the granular moment by moment functions or dysfunctions meaningful to an engineer. Puleeaze, RC, let us know you hear our cry. The inability to define metrics can kill a project, can threaten the broader reality capture space generally as it applies to work in RC specifically, if left unattended.

    Another thought, useful would be a Save override function while RC is running a Reconstruction that allows user to save whatever level of work RC reached before the bug. I realize cache does save items, but when you have to force End Process, I'm seeing RC having to start over.

    0
    Comment actions Permalink
  • Avatar
    Benjamin von Cramon

    I thought it useful to provide an update, made progress, not that this teaches anything about causes and reliable work arounds, am left to wonder...

    I had suggested I'd next try exporting .rcalign and running in a new project. I did not clear cache, watched the console in the new project (with the imported Component) during Reconstruction, seems RC didn't have to begin from scratch, but using Normal quality the Reconstruction of 392 images took over 24 hours, saw the same sluggish behavior, though just a hair more activity on CPU than what happened (or didn't happen) in four days time prior. When it completed RC reported that 64 parts were missing. How might this particular issue be related to the original issue, RC turns slow like molasses?

    I then wondered if my system may be straining, maybe try a smaller Reconstruction Region. My system has performed fine with way more images (same 42 MP density), so system resources wouldn't seem a likely culprit, but you try anything. Again, I left cache alone, roughly half the image set ran through Reconstruction without a problem in only an hour or so, then same with the remainder.

    What conclusions may one draw from this experience? RC often works, sometimes doesn't? System resources may or may not play a role in how consistently RC functions as expected? Questions like these make folks running a business nervous. You don't want to be forced to throw a percentage in related to an "RC uncertainty cost factor". End users can deal with reality, so if RC engineers could weigh in and simply speak to the reality and share how their top power users work with those issues, this knowledge is most welcome and I'm sure I'm not alone in saying that I'd never use knowledge of a weak spot in RC against Capturing Reality, slinging mud publicly. We all understand this work is nontrivial to say the least. It's amazing this works at all, and RC is the clear leader in this space, so this isn't about and shouldn't be about editorializing the product. We simply want answers to better do our job. 

    In the meanwhile, I think my practise will be to keep an eye on Resource Monitor, and when too much time goes by, End Process Tree, restart PC, don't trash cache, try running a smaller Reconstruction Region, try doing so in a new project based on an imported Component.

    0
    Comment actions Permalink

Please sign in to leave a comment.