Skip to content

Commit

Permalink
Edits to the docs
Browse files Browse the repository at this point in the history
  • Loading branch information
jeipollack committed Nov 6, 2023
1 parent feb172d commit 46af5b3
Show file tree
Hide file tree
Showing 3 changed files with 31 additions and 30 deletions.
6 changes: 3 additions & 3 deletions docs/source/basic_execution.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ To run `WaveDiff`, use the following command:
> wavediff -c /path/to/config/file -r /path/to/wf-psf -o /path/to/output/dir
```

WaveDiff begins with the input/output (i.e. retrieving and parsing the configuration file and creating a set of nested output subdirectories in the main output directory). The name of the top-level subdirectory is a composition of the string `wf-outputs-` and the timestamp of the corresponding run, i.e. `wf-outputs-202310221632`. Each run will produce its own unique subdirectory. Then within this subdirectory, further subdirectories are generated to store the corresponding output.
WaveDiff begins with the input/output (i.e. retrieving and parsing the configuration file and creating a set of nested output of directories within the main output directory). The name of the top-level subdirectory is a composition of the string `wf-outputs-` and a timestamp of the current run, i.e. `wf-outputs-202310221632`. Each run of WaveDiff will produce its own unique subdirectory. Then within this subdirectory, further subdirectories are generated to store the corresponding output.

Below is an example of the set of directories generated during each execution of the WaveDiff pipeline.

Expand All @@ -47,7 +47,7 @@ wf-outputs-202310211641
├── plots
└── psf_model
```
A description of each subdirectory is provided in the table below.
A description of each subdirectory is provided in the following table.

| Sub-directory | Purpose |
|--------------|---------------------------------------------------|
Expand All @@ -57,7 +57,7 @@ A description of each subdirectory is provided in the table below.
| metrics | Stores the metrics results generated during the metrics pipeline task. |
| optim-hist | Stores the training history of the model parameters. |
| plots | Stores metrics plots generated during the plotting pipeline task. |
| psf_models | Stores the final trained psf models generated for each training cycle. |
| psf_models | Stores the final trained PSF models for each training cycle. |


Next, we describe to some detail the configuration file structures and content.
Expand Down
Loading

0 comments on commit 46af5b3

Please sign in to comment.