For relative paths, assume well picks and polygon files in CO2Leakage exist in each realization, instead of common file for all realizations
- Lenguaje dominante
- Python
- Estrellas
- 2
- Forks
- 2
- Merge medio
- 5 d 23 h
- PR fusionados (30 d)
- 2
Descripción
Absolute paths for well picks and polygon files should already be handled by CO2Leakage and straight forward to use.
For relative paths:
Some files (maps, CSV-files etc) are unique to each realization, while currently the well picks and polygon files are only extracted from one location. We want to make the logic the same, to avoid confusion. This means that the well picks and polygon files should be placed in each realization folder. Often they will just be similar copies, but this makes it possible at least in theory to have different well picks or polygons per realization.
See comments here: https://github.com/equinor/ccs-scripts/issues/107#issuecomment-2199384068
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.