[cig-commits] [commit] devel, master: Update README_current_conclusions_from_Dimitri_about_the_bug.txt (3887afd)

[cig_noreply at geodynamics.org]

Repository : https://github.com/geodynamics/specfem3d_globe

On branches: devel,master
Link       : https://github.com/geodynamics/specfem3d_globe/compare/bc58e579b3b0838a0968725a076f5904845437ca...be63f20cbb6f462104e949894dbe205d2398cd7f

>---------------------------------------------------------------

commit 3887afd898f0bff29d3bbb9bca37a3077b34cbf9
Author: Dimitri Komatitsch <komatits at users.noreply.github.com>
Date:   Thu Apr 10 13:48:34 2014 +0200

    Update README_current_conclusions_from_Dimitri_about_the_bug.txt


>---------------------------------------------------------------

3887afd898f0bff29d3bbb9bca37a3077b34cbf9
 .../README_current_conclusions_from_Dimitri_about_the_bug.txt           | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/IMPORTANT_BUG_benchmark_Ebru_Par_file/README_current_conclusions_from_Dimitri_about_the_bug.txt b/IMPORTANT_BUG_benchmark_Ebru_Par_file/README_current_conclusions_from_Dimitri_about_the_bug.txt
index c6c2529..7b10a63 100644
--- a/IMPORTANT_BUG_benchmark_Ebru_Par_file/README_current_conclusions_from_Dimitri_about_the_bug.txt
+++ b/IMPORTANT_BUG_benchmark_Ebru_Par_file/README_current_conclusions_from_Dimitri_about_the_bug.txt
@@ -17,6 +17,8 @@ the bug is probably not in the MPI routines, since the 1D attenuation benchmark
 
 the bug is not something obvious such as an array index going out of bounds, because the code does not display any error message for that benchmark when running with full range checking options (as well as stack checking, unassigned variable detection and so on)
 
+the bug is not related to the new UNDO_ATTENUATION option, because the bug is already present in older versions (UNDO_ATTENUATION was added only recently), and in addition UNDO_ATTENUATION is off in the Par_file of this test
+
 Ebru's current runs are highly affected (the example is her Par_file, with a single change: 60 min instead of 100 min for the total duration of the seismograms, just to reduce the cost of the tests)
 
 The bug has been there for at least a year, probably more (my comment about this in the to-do list was from August 2013, back then I thought the switch to Daniel's new version at the end of Aug 2013 would fix it, but unfortunately it is still there); thus it is likely in a part of the code that did not change much when we switched to the new version