Remove aggregate_map and migration_time (#137)

* Remove aggregate_map and migration_time

* Remove Grid3dMigrationTime and Grid3dAggregateMap from forward_models/__init__-py

* Remove Grid3dMigrationTime and Grid3dAggregateMap from forward_models/__init__-py

* forward_models/Restore grid3d_average_map.py

* Remove Grid3dMigrationTime and Grid3dAggregateMap from forward_models/__init__-py

* Update README.md

* Update documentation

---------

Co-authored-by: root <root@NR-JKY93M3>

Author: jorgesicachanr

README.md

@@ -13,8 +13,7 @@ Various scripts for generating maps from 3D grid properties.
 |-------------------------|---------------------|
 | `grid3d_hc_thickness`   | Make Hydrocarbon thickness maps from Eclipse and/or Roff input |
 | `grid3d_average_map`    | Make average maps from a 3D grid parameter, Eclipse or Roff input |
-| `grid3d_aggregate_map`  | Make aggregated maps (min/max/mean/sum) from a 3D grid parameter, Eclipse or Roff input |
-| `grid3d_migration_time` | Make migration time maps aimed at tracking plume migration in CCS applications |
+
 
 ## Features
 

docs/examples.rst

@@ -269,54 +269,3 @@ required for average data, and properties must occur under ``properties:``
 
 .. literalinclude:: ../docs/test_to_docs/avgdataio1a.yml
    :language: yaml
-
-Aggregate example 1
-"""""""""""""""""""
-
-Minimal aggregation example, doing a "maximum" aggregation across all layers
-
-.. literalinclude:: ../tests/yaml/aggregate1.yml
-   :language: yaml
-
-Aggregate example 2
-"""""""""""""""""""
-
-Example using "minimum" aggregation. Zonation is provided in a property file, and ``eclroot:`` is
-used as an alias
-
-.. literalinclude:: ../tests/yaml/aggregate2.yml
-   :language: yaml
-
-Aggregate example 3
-"""""""""""""""""""
-
-Example using "mean" aggregation and explicit map settings
-
-.. literalinclude:: ../tests/yaml/aggregate3.yml
-   :language: yaml
-
-Aggregate example 4
-"""""""""""""""""""
-
-Example using an interval-based zonation
-
-.. literalinclude:: ../tests/yaml/aggregate4.yml
-   :language: yaml
-
-Aggregate example 5
-"""""""""""""""""""
-
-Example using "mean" aggregation, with weights calculated from cell thickness. "folderroot"
-is used as an alias. The map settings are calculated automatically, with resolution
-determined by "pixel_to_cell_ratio".
-
-.. literalinclude:: ../tests/yaml/aggregate5.yml
-   :language: yaml
-
-Aggregate example 6
-"""""""""""""""""""
-
-Example using date and zone filters
-
-.. literalinclude:: ../tests/yaml/aggregate6.yml
-   :language: yaml

docs/howitworks.rst

@@ -14,40 +14,6 @@ sum hc thickness map per zone or by all zones that are spesified.
 
 For average maps, a thickness weighted average is computed.
 
-This is not applicable to `grid3d_aggregate_map` and `grid3d_migration_time`,
-which uses a different approach for aggregating layers.
-
-`grid3d_aggregate_map` and `grid3d_migration_time`
---------------------------------------------------
-
-`grid3d_aggregate_map` and `grid3d_migration_time` uses a different approach
-when aggregating values. In general, the main difference from
-`grid3d_hc_thickness` and `grid3d_average_map` is that the result will be less
-smooth. Secondly, gaps in the grid (typically caused by faults), will not be
-filled.
-
-.. image:: images/grid_aggregation.jpg
-
-Each map node is first connected to all cells whose (approximate) footprint
-overlaps the map node. An artificial set of connections are illustrated by
-colors in the figure above.
-
-Once the connections are established, the value of each map node is calculated
-from all the connected grid cells via one of the specified aggregation
-methods:
-
-- Maximum
-- Minimum
-- Mean
-- Sum
-
-Layer information and lateral distance from map node to grid cell center is
-currently not used. However, filters can be used to apply this per zone etc.
-
-One benefit of this approach is that the map-node-to-grid-cell connection
-information can be re-used across time steps and properties, as long as the
-grid geometry does not change. This is beneficial for performance.
-
 Further details
 ---------------
 

docs/images/grid_aggregation.jpg

@@ -14,8 +14,6 @@ The stable release is on /project/res, so scripts can be run as:
 
     $ grid3d_hc_thickness <options>
     $ grid3d_average_map <options>
-    $ grid3d_aggregate_map <options>
-    $ grid3d_migration_time <options>
 
 
 From sources

docs/installation.rst

@@ -11,11 +11,6 @@ other makes average maps
 
    grid3d_average_map --config myfile_avg.yml
 
-In addition, there are scripts for general aggregation (min/max/mean/sum),
-"grid3d_aggregate_map" and CO2 plume migration time, "grid3d_migration_time".
-These scripts are invoked similarly to the two above, but may not support all
-the features described below.
-
 -------------------------
 Override the Eclipse root
 -------------------------

docs/usage.rst

@@ -85,8 +85,7 @@ Documentation = "https://equinor.github.io/grid3d-maps"
 [project.scripts]
 grid3d_hc_thickness = "grid3d_maps.avghc.grid3d_hc_thickness:main"
 grid3d_average_map = "grid3d_maps.avghc.grid3d_average_map:main"
-grid3d_aggregate_map = "grid3d_maps.aggregate.grid3d_aggregate_map:main"
-grid3d_migration_time = "grid3d_maps.aggregate.grid3d_migration_time:main"
+
 
 [project.entry-points.ert]
 grid3d_maps_jobs = "grid3d_maps.hook_implementations.jobs"