Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

KeyError Traceback (most recent call last) /usr/local/lib/python3.6/dist-packages/pandas/core/indexes/base.py in get_loc(self, key, method, tolerance)

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
jupyter-notebook, pandas, python
Domain
data

Research direction

Start by reproducing the Graph Data and Parse and prepare the data code in the workbook with flex.csv and punch.csv in the main and sample_data folders. Inspect the complete traceback and the referenced notebook cells to identify the missing key; done means the cells run without the reported KeyError or the required data/workaround is documented.

Written by the indexing model from the issue text.

Description

When running the Graph Data (optional) code I get the following error message:

"KeyError Traceback (most recent call last) /usr/local/lib/python3.6/dist-packages/pandas/core/indexes/base.py in get_loc(self, key, method, tolerance)"

I get the same message also when running the Parse and prepare the data code.

I believe that I have successfully completed the previous steps in the workbook (setting up the Pyrhon Environment runs OK and I have also uploaded the the flex.csv and punch.csv files to the main folder and also to the sample_data folder).

Näyttökuva 2020-8-2 kello 21 56 26

I was wondering that am I doing something wrong or is there a workaround for the problem?

Dominant language
Jupyter Notebook
Stars
269
Forks
122
PR merge metrics
No merged PRs in 30d

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.

More from arduino/ArduinoTensorFlowLiteTutorials

All issues in arduino/ArduinoTensorFlowLiteTutorials

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.