Commit 68654bd4 authored by Mitar's avatar Mitar

Don't use strict resolving anymore.


Former-commit-id: 3a3e25ed
parent 3d1bded0
......@@ -124,7 +124,7 @@ $ ./run_validation.py 'v2017.12.27/Test team/d3m.primitives.test.IncrementPrimit
To validate pipeline description do:
```bash
$ python3 -m d3m.metadata.pipeline --strict-resolving -c <path_to_JSON>
$ python3 -m d3m.metadata.pipeline -c <path_to_JSON>
```
It will print out the pipeline JSON if it succeeds, or an error otherwise. You should probably run it inside
......@@ -133,7 +133,7 @@ a Docker image with all primitives your pipeline references, or have them instal
You can validate your `.meta` file by running:
```bash
$ python3 -m d3m.runtime --strict-resolving -d /path/to/all/datasets fit-score -n scoring.yml -m your-pipeline.meta -p your-pipeline.yml
$ python3 -m d3m.runtime -d /path/to/all/datasets fit-score -n scoring.yml -m your-pipeline.meta -p your-pipeline.yml
```
Where `scoring.yml` pipeline can be [found here](https://gitlab.com/datadrivendiscovery/metalearning/blob/master/UCBerkeley/scoring.yml).
......
......@@ -747,7 +747,6 @@ def validate_installation(primitive_names, interface_version, installation, anno
'python3',
'-m',
'd3m.metadata.pipeline',
'--strict-resolving',
'--check',
'--pipelines-path', '/tmp/pipelines',
'/tmp/pipelines/{pipeline_name}'.format(pipeline_name=pipeline_name),
......@@ -758,7 +757,6 @@ def validate_installation(primitive_names, interface_version, installation, anno
'python3',
'-m',
'd3m.metadata.pipeline',
'--strict-resolving',
'--check',
'--not-standard-pipeline',
'--pipelines-path', '/tmp/pipelines',
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment