llnl / llnl/CallFlow

Jupyter Notebook: Can't parse config file

Open
#31 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vue
Stars
37
Forks
4
PR merge metrics
No merged PRs in 30d

Description

The example Jupyter Notebook can't be run as there seems to be an issue reading the example config file:
```
singleConfig = ConfigFileReader(singleConfigPath)
```

Causes the following error:
```
---------------------------------------------------------------------------
KeyError Traceback (most recent call last)
in
1 # Read config file.
----> 2 singleConfig = ConfigFileReader(singleConfigPath)

C:\temp\Anaconda\lib\site-packages\callflow\operations\read_config.py in __init__(self, filepath, config_json)
31
32 self.scheme = self.json["scheme"]
---> 33 self.datasets = self.json["datasets"]
34 self.runName = self.json["run_name"]
35 self.save_path = os.path.join(self.data_path, ".callflow")

KeyError: 'datasets'
```

Config file: hpctoolkit-cpi-database/callflow.config.json
Environment: CallFlow 1.1.1 / Jupyter Notebook 6.0.3 / Anaconda Python 3.7.6 / Win10 64bit

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure using hpctoolkit-cpi-database/callflow.config.json and the example Jupyter Notebook. Start at ConfigFileReader in callflow/operations/read_config.py, where the traceback shows the missing datasets key is read. Done means the example notebook can load the configuration without the KeyError.

Written by the indexing model from the issue text.

Assessment

Tech stack
anaconda, jupyter-notebook, python
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.