Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update doc of examples for Trains fileserver setup #1360

Merged
merged 2 commits into from
Oct 5, 2020
Merged

Update doc of examples for Trains fileserver setup #1360

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cd5a020
update doc for trains fileserver setup
Oct 5, 2020
37d8bce
replace github issue by documentation
Oct 5, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion examples/contrib/cifar10/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,4 +131,14 @@ python -u -m torch.distributed.launch --nproc_per_node=2 --use_env main.py run -
--resume-from=/tmp/output-cifar10/resnet18_backend-nccl-2_stop-on-1000/training_checkpoint_1000.pt
```

Similar commands can be adapted for other cases.
Similar commands can be adapted for other cases.

## Trains fileserver

If `Trains` server is used (i.e. `--with_trains` argument), the configuration to upload artifact must be done by
modifying the `Trains` configuration file `~/trains.config` generated by `trains-init`. According to the
[documentation](https://allegro.ai/docs/examples/reporting/artifacts/), the `output_uri` argument can be
configured in `sdk.development.default_output_uri` to fileserver uri. If server is self-hosted, `Trains` fileserver uri is
`http://localhost:8081`.

For more details, see https://allegro.ai/docs/examples/reporting/artifacts/
10 changes: 10 additions & 0 deletions examples/references/classification/imagenet/NOTES_Trains.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,16 @@ export TRAINS_OUTPUT_PATH=/path/to/output/trains

This environment variable helps to choose Trains as experiment tracking system among all others.

### Trains fileserver setup

The configuration to upload artifact must be done by modifying the `trains` configuration file `~/trains.config`
generated by `trains-init`. According to the
[documentation](https://allegro.ai/docs/examples/reporting/artifacts/), the `output_uri` argument can be
configured in `sdk.development.default_output_uri` to fileserver uri. If server is self-hosted, `Trains` fileserver uri is
`http://localhost:8081`.

For more details, see https://allegro.ai/docs/examples/reporting/artifacts/

### Run the code

#### Training on single node and single GPU
Expand Down
10 changes: 10 additions & 0 deletions examples/references/segmentation/pascal_voc2012/NOTES_Trains.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,16 @@ export TRAINS_OUTPUT_PATH=/path/to/output/trains

This environment variable helps to choose Trains as experiment tracking system among all others.

### Trains fileserver setup

The configuration to upload artifact must be done by modifying the `trains` configuration file `~/trains.config`
generated by `trains-init`. According to the
[documentation](https://allegro.ai/docs/examples/reporting/artifacts/), the `output_uri` argument can be
configured in `sdk.development.default_output_uri` to fileserver uri. If server is self-hosted, `Trains` fileserver uri is
`http://localhost:8081`.

For more details, see https://allegro.ai/docs/examples/reporting/artifacts/

### Run the code

#### Training on single node and single GPU
Expand Down