[cig-commits] r20450 - seismo/3D/SPECFEM3D/trunk

[danielpeter at geodynamics.org]

Author: danielpeter
Date: 2012-07-02 12:15:41 -0700 (Mon, 02 Jul 2012)
New Revision: 20450

Modified:
   seismo/3D/SPECFEM3D/trunk/todo_list_please_dont_remove.txt
Log:
in todo list, moved suggestion 27 to DONE section

Modified: seismo/3D/SPECFEM3D/trunk/todo_list_please_dont_remove.txt
===================================================================
--- seismo/3D/SPECFEM3D/trunk/todo_list_please_dont_remove.txt	2012-07-02 19:08:59 UTC (rev 20449)
+++ seismo/3D/SPECFEM3D/trunk/todo_list_please_dont_remove.txt	2012-07-02 19:15:41 UTC (rev 20450)
@@ -443,18 +443,7 @@
 
 (in 2D we could avoid this problem by saving all the timesteps of the forward run to disk and reading them back, but in 3D is it not possible yet because the amount of I/Os would be too big; this should change in 5 to 10 years, but for now we still need to back-propagate when SIMULATION_TYPE = 3 in 3D)
 
-- suggestion 27:
-----------------
 
-For Emanuele and Federica:
-
-I agree that read_external_mesh() with varying parameters (for instance to import external tomographic models) is described on page 13 of the manual, but I think the description could / should be made a bit more precise.
-
-In the current version of page 13 of the manual it seems to be a relatively minor point, while in practice many users will use that feature (many/most applications will use such external models).
-
-I therefore suggest that Federica and you make it a slightly longer paragraph, and probably even make it a separate section or sub-section.
-This way, the item will appear in the table of contents.
-
 - suggestion 28:
 ----------------
 
@@ -595,6 +584,18 @@
 DONE (MOVE ITEMS ABOVE BELOW THIS LINE WHEN THEY ARE DONE):
 -----------------------------------------------------------
 
+- suggestion 27:
+----------------
+
+For Emanuele and Federica:
+
+I agree that read_external_mesh() with varying parameters (for instance to import external tomographic models) is described on page 13 of the manual, but I think the description could / should be made a bit more precise.
+
+In the current version of page 13 of the manual it seems to be a relatively minor point, while in practice many users will use that feature (many/most applications will use such external models).
+
+I therefore suggest that Federica and you make it a slightly longer paragraph, and probably even make it a separate section or sub-section.
+This way, the item will appear in the table of contents.
+
 - suggestion 29:
 ----------------