Describe the bug
Using a data source with umlauts in the column names leads to the Jupyter Notebook with which the suite can be edited throw an error on startup. The Notebook then doesn't load.
This might be a Jupyter Notebook bug, not sure?!

To Reproduce
Steps to reproduce the behavior:

1. Initialize a suite with this xlsx file as a data source (nothing fancy: Just two columns, the

Proposed Behaviour

None of the core VPR algorithms should care if the relevant t_physical_tile is an input / output / IO type.

Current Behaviour

Some behavior is still dependent on whether a tile is an input / output / IO type.

Possible Solution

The relevant code shouldn't need to care. Once all callsites of is_input_type/is_output_type/is_io_type are removed, the

Today i add a license for this repository.