You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
* cleaning up files which are no longer needed
* fixes after removing forking workflow (#322)
* PR to resolve merge issues
* updated main build as well
* added ability to read in git branch name directly
* manually updated the other files
* fixed number of classes for main build tests (#327)
* fixed number of classes for main build tests
* corrected DATASET.ROOT in builds
* added dev build script
* Fixes for development inside the docker container (#335)
* Fix the mound command for the HRNet pretrained model in the docker readme
* Properly catch InvalidGitRepository exception
* make repo paths consistent with non-docker runs -- this way configs paths do not need to be changed
* Properly catch InvalidGitRepository exception in train.py
* Readme update (#337)
* README updates
* Removing user specific path from config
Authored-by: Fatemeh Zamanian <[email protected]>
* Fixing #324 and #325 (#338)
* update colormap to a non-discrete one -- fixes#324
* fix mask_to_disk to normalize by n_classes
* changes to test.py
* Updating data.py
* bug fix
* increased timeout time for main_build
* retrigger build
* retrigger the build
* increase timeout
* fixes 318 (#339)
* finished 318
* increased checkerboard test timeout
* fix 333 (#340)
* added label correction to train gradient
* changing the gradient data generator to take inline/crossline argument conssistent with the patchloader
* changing variable name to be more descriptive
Co-authored-by: maxkazmsft <[email protected]>
* bug fix to model predictions (#345)
* replace hrnet with seresnet in experiments - provides stable default model (#343)
Co-authored-by: yalaudah <[email protected]>
Co-authored-by: Fatemeh <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+11-7Lines changed: 11 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,13 @@
3
3
4
4
This repository shows you how to perform seismic imaging and interpretation on Azure. It empowers geophysicists and data scientists to run seismic experiments using state-of-art DSL-based PDE solvers and segmentation algorithms on Azure.
5
5
6
+
6
7
The repository provides sample notebooks, data loaders for seismic data, utilities, and out-of-the-box ML pipelines, organized as follows:
7
8
-**sample notebooks**: these can be found in the `examples` folder - they are standard Jupyter notebooks which highlight how to use the codebase by walking the user through a set of pre-made examples
8
9
-**experiments**: the goal is to provide runnable Python scripts that train and test (score) our machine learning models in the `experiments` folder. The models themselves are swappable, meaning a single train script can be used to run a different model on the same dataset by simply swapping out the configuration file which defines the model.
9
-
-**pip installable utilities**: we provide `cv_lib` and `deepseismic_interpretation` utilities (more info below) which are used by both sample notebooks and experiments mentioned above
10
+
-**pip installable utilities**: we provide `cv_lib` and `interpretation` utilities (more info below) which are used by both sample notebooks and experiments mentioned above
10
11
11
-
DeepSeismic currently focuses on Seismic Interpretation (3D segmentation aka facies classification) with experimental code provided around Seismic Imaging in the contrib folder.
12
+
DeepSeismic currently focuses on Seismic Interpretation (mainly facies classification) with experimental code provided around Seismic Imaging in the contrib folder.
12
13
13
14
### Quick Start
14
15
@@ -26,7 +27,7 @@ If you run into any problems, chances are your problem has already been solved i
26
27
The notebook is designed to be run in demo mode by default using a pre-trained model in under 5 minutes on any reasonable Deep Learning GPU such as nVidia K80/P40/P100/V100/TitanV.
27
28
28
29
### Azure Machine Learning
29
-
[Azure Machine Learning](https://docs.microsoft.com/en-us/azure/machine-learning/) enables you to train and deploy your machine learning models and pipelines at scale, ane leverage open-source Python frameworks, such as PyTorch, TensorFlow, and scikit-learn. If you are looking at getting started with using the code in this repository with Azure Machine Learning, refer to [Azure Machine Learning How-to](https://github.com/Azure/MachineLearningNotebooks/tree/master/how-to-use-azureml) to get started.
30
+
[Azure Machine Learning](https://docs.microsoft.com/en-us/azure/machine-learning/) enables you to train and deploy your machine learning models and pipelines at scale, and leverage open-source Python frameworks, such as PyTorch, TensorFlow, and scikit-learn. If you are looking at getting started with using the code in this repository with Azure Machine Learning, refer to [Azure Machine Learning How-to](https://github.com/Azure/MachineLearningNotebooks/tree/master/how-to-use-azureml) to get started.
30
31
31
32
## Interpretation
32
33
For seismic interpretation, the repository consists of extensible machine learning pipelines, that shows how you can leverage state-of-the-art segmentation algorithms (UNet, SEResNET, HRNet) for seismic interpretation.
@@ -120,9 +121,12 @@ To prepare the data for the experiments (e.g. split into train/val/test), please
@@ -164,7 +168,7 @@ We use [YACS](https://github.com/rbgirshick/yacs) configuration library to manag
164
168
-__yml config files__ - YAML configuration files under `configs/` are typically created one for each experiment. These are meant to be used for repeatable experiment runs and reproducible settings. Each configuration file only overrides the options that are changing in that experiment (e.g. options loaded from `defaults.py` during an experiment run will be overridden by arguments loaded from the yaml file). As an example, to use yml configuration file with the training script, run:
- __command line__ - Finally, options can be passed in through `options` argument, and those will override arguments loaded from the configuration file. We created CLIs for all our scripts (using Python Fire library), so you can pass these options via command-line arguments, like so:
@@ -229,8 +233,8 @@ This section contains benchmarks of different algorithms for seismic interpretat
229
233
230
234
231
235
#### Reproduce benchmarks
232
-
In order to reproduce the benchmarks, you will need to navigate to the [experiments](experiments) folder. In there, each of the experiments are split into different folders. To run the Netherlands F3 experiment navigate to the [dutchf3_patch/local](experiments/dutchf3_patch/local) folder. In there is a training script [([train.sh](experiments/dutchf3_patch/local/train.sh))
233
-
which will run the training for any configuration you pass in. Once you have run the training you will need to run the [test.sh](experiments/dutchf3_patch/local/test.sh) script. Make sure you specify
236
+
In order to reproduce the benchmarks, you will need to navigate to the [experiments](experiments) folder. In there, each of the experiments are split into different folders. To run the Netherlands F3 experiment navigate to the [dutchf3_patch/local](experiments/interpretation/dutchf3_patch/local) folder. In there is a training script [([train.sh](experiments/interpretation/dutchf3_patch/local/train.sh))
237
+
which will run the training for any configuration you pass in. Once you have run the training you will need to run the [test.sh](experiments/interpretation/dutchf3_patch/local/test.sh) script. Make sure you specify
234
238
the path to the best performing model from your training run, either by passing it in as an argument or altering the YACS config file.
0 commit comments