Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with some frames crashing after 2 iterations #52

Open
TommyKnow opened this issue May 30, 2017 · 1 comment
Open

Issue with some frames crashing after 2 iterations #52

TommyKnow opened this issue May 30, 2017 · 1 comment

Comments

@TommyKnow
Copy link

Hi all,

Apologies if this was fixed elsewhere, but I cannot find it if so. I'm a noob to this type of software and it's a little bewildering.

Some frames (very often the first frame, but usually around 1 in 15 of completed frames) will crash after only going for one or two iterations. The result is that the frame is blurry compared to the ones that completed without issue. The script then carries on and attempts to create the next frame.

No obvious error, but there is a difference between frames which did and didn't crash (in bold):

Reading flow file ".../wavelarge/flow_1280:720/backward_19_18.flo".
Reading flowWeights file ".../wavelarge/flow_1280:720/reliable_19_18.pgm".
Reading flow file ".../wavelarge/flow_1280:720/backward_19_18.flo".
Running optimization with L-BFGS
<optim.lbfgs> creating recyclable direction/step/history buffers
<optim.lbfgs> function value changing less than tolX
Running time: 1s
Iteration 2 / 300
Content 1 loss: 9200722.500000
Temporal 1 loss: 0.000000
Style 1 loss: 812805.512238
Style 2 loss: 266905000.195312
Style 3 loss: 722221992.968750
Style 4 loss: 21909036787.500000
Style 5 loss: 1525010.723877
Total loss: 22909702319.400177
Reading flow file

I've tried setting -tol_loss_relative to 0 but that doesn't change anything. It has also been suggested that lowering the style weight might help but it still occurs with it lowered significantly. Any ideas?

@ChoclateRain
Copy link

@TommyKnow Removing -temporal_weight fixes it for me (you'll just have to use the default temp weight for those frames that are crashing, and make sure not to even enter the default -temporal_weight just run without setting that param)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants