Unable to open configurations in Mélusine library
MattiasEyh opened this issue · comments
Pull Request Title:
Unable to open configurations in Mélusine library
Pull Request Description:
I am trying to use the Mélusine library to configure a pipeline, but I am unable to open any configuration file. I have tried using the demo_pipeline example, but nothing works.
Here are the steps I have taken:
- I installed the Mélusine library using pip.
- I created a new Python file and imported the Mélusine library.
The error message is:
`KeyError Traceback (most recent call last)
Cell In[869], line 3
1 from melusine.pipeline import MelusinePipeline
----> 3 pipeline = MelusinePipeline.from_config(config_key="demo_pipeline")
File ~/anaconda3/envs/.../lib/python3.8/site-packages/melusine/pipeline.py:195, in MelusinePipeline.from_config(cls, config_key, config_dict, **kwargs)
193 # Get config dict
194 if config_key and not config_dict:
--> 195 raw_config_dict = config[config_key]
196 config_dict = cls.parse_pipeline_config(raw_config_dict)
198 elif config_dict and not config_key:
File ~/anaconda3/envs/....lib/python3.8/site-packages/melusine/config/config.py:104, in getitem(self, key)
KeyError: 'demo_pipeline'`
I am not sure what I am doing wrong. Can you please help me?
Additional Information:
- I am using Python 3.8.18
- I am using the latest version of the Mélusine library.
Actual Behavior:
An error is raised.
Request:
Please help me to troubleshoot this issue.
Hello,
This is surprising, pipeline creation is extensively tested.
The demo_pipeline key is missing from your config (it should be there by default)
Can you try the tutorial on Configurations and check if demo_pipeline is in the default config ?
I'm thinking about either:
- yaml config files missing (packaging problem) you may check if the file https://github.com/MAIF/melusine/blob/master/melusine%2Fconf%2Fpipelines%2Fdemo_pipeline.yaml is present in the melusine folder in your site packages
- configurations setup issue : check which conf files are loaded (conf tutorial could help)
- install problem : could you try to install again in a fresh virtual env ?
Hope this helps
Hugo