# pt exp = pt
$ pt project

$ pt run baselines.yaml
# option 1. create an experiment "baselines" or append jobs to it
# option 2. put in "default" experiment ?

$ pt run baselines.yaml foo
# append to foo, if doesn't exist ask

$ pt run test.yml -n
# create a new experiment with a random ID

$ pt run test.yml -n foo
# create a new experiment with name foo, if it exists overwrite


git push local:remote
git push :remote

$ pt run test.yml :job 
$ pt run test.yaml :job

$ pt move exp :job1 :job2 exp :job3

$ pt move exp:job1,job2 exp:job3

$ pt move exp :job1 [-c] exp2

## description

options:

- we ask description first time experiment is created ?
- always ask, but experiment description only gets updated when we create it, otherwise only job descriptions get updated

what happens with search, do we still append to baselines?
--> baseline-search1232 ?
do you have a "baseline.yml" with a search in it, or do you have a baseline-search.yml? in the latter case we can keep the schema.

## notes

- pt list / pt status too slow if we have too many jobs in the default experiment ?
- runtime document limit of azureml