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.

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

Config file paths are relative to current working directory instead of config file location #213

Closed
brianray opened this issue Nov 23, 2014 · 2 comments
Labels
Milestone

Comments

@brianray
Copy link
Contributor

These may be windows related. However, two things I ran into so far one small and the other will need more investigation.

a) The path issue

C:\Users\brray\Documents\GitHub\skll\examples>run_experiment titanic/evaluate_tuned.cfg
Traceback (most recent call last):
  File "C:\Users\brray\AppData\Local\Continuum\Anaconda\lib\runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "C:\Users\brray\AppData\Local\Continuum\Anaconda\lib\runpy.py", line 72, in _run_code
    exec code in run_globals
  File "C:\Users\brray\AppData\Local\Continuum\Anaconda\Scripts\run_experiment.exe\__main__.py", line 9, in <module>
  File "C:\Users\brray\AppData\Local\Continuum\Anaconda\lib\site-packages\skll\utilities\run_experiment.py", line 108, in main
    ablation=ablation, resume=args.resume)
  File "C:\Users\brray\AppData\Local\Continuum\Anaconda\lib\site-packages\skll\experiments.py", line 1052, in run_configuration
    custom_learner_path) = _parse_config_file(config_file)
  File "C:\Users\brray\AppData\Local\Continuum\Anaconda\lib\site-packages\skll\experiments.py", line 459, in _parse_config_file
    "config file does not exist"), train_path)
IOError: [Errno 2] The training path specified in the config file does not exist: u'train'

If I 'cd' into the titanic directory, it works.

@dan-blanchard
Copy link
Contributor

You raise a good point. The relative paths in a config file are specified as if they're relative to the config file, but in actuality the paths are relative to your current working directory. We should probably fix that so that they're actually relative to the config file's location.

@dan-blanchard dan-blanchard added this to the 1.1 milestone Nov 23, 2014
@dan-blanchard dan-blanchard changed the title Smoothing out tutorial - a) path issue Config file paths are relative to current working directory instead of config file location Nov 23, 2014
@desilinguist
Copy link
Member

Addressed by #246.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants