Closed mloubout closed 7 years ago
The warning are an artefact of the current code generation system. They will disappear in a future release. We could temporarily add this option -Wunused-variable
to the compilation line.
Could you tell me a bit more about these wrong results.
First of all, I need instructions on how to reproduce this (branch, command line, etc.)
What is the result that you expect, and what instead are you getting? Maybe tell me just the value of a norm ?
I get that with dse = basic
this works OK ?
First of all, I need instructions on how to reproduce this (branch, command line, etc.)
this is the plots I sent you in slack, mainly, run TTI with and without dse and you'll see the result without is "fine" while the result with is "noisy"
since you're not using the master branch, I need:
And I don't know how to generate the plots.
In these cases, you should write a minimal failing example and output a norm (for example) so that the only thing I have to look at is a number.
Does the problem disappear with dse=basic
? Does it disappear with dse=noop
?
This is master branch.
Does the problem disappear with dse=basic? Does it disappear with dse=noop ?
only tried advanced
and None
OK, so, if you now merge devito3-final
, the problem should just disappear in non-legacy
mode. The segfault in legacy more seems to be still there, but I don't think investing time in fixing it is a good idea.
I rather encourage to progressively move everything to the "new" Devito3 API, and report any other bugs in case you found more. The test_Marmousi
that you provided offline was excellent.
Please confirm that this is now fixed in non-legacy
mode
Once again, everything we run/will run at UBC is gonna stay with Legacy untill we have adjoints and gradients and making changes that forces us to work with 2-3 month old version of devito is gonna be dredfull to update once devito 3.0 is in. SO yes I still need legacy to run properly.
So just switch to dse='basic'
or even dse=None
for now. As you're just developing, you don't need performance ATM. I think it's safe to say that this issue has lower priority; the bug is probably caused by some stupid interaction with the old propagator -- perhaps I'll check this next week. Thoughts, @mlange05 @navjotk ?
This issue is about a few problematic currently encountered with dse. 1- 2D TTI segfault in Legacy mode with
dse=advanced
2- 2D TTI runs with no Legacy anddse=advanced
but produces wrong results and has warnings at compilation